Fix excessive CPU usage caused by motion sensor updates

[viatearz]

It was confirmed that some games suffer from excessive CPU usage.
This is caused by CMMotionManager setting the default update interval to 0, which results in extremely frequent updates.

You can verify the update frequency using the following code:

// NSObject+Swizzle.mm

@implementation NSObject (Swizzle)
- (void)hook_UINSVirtualMotionDevice_scanAccelerometer {
    NSLog(@"[PlayTools] hook_UINSVirtualMotionDevice_scanAccelerometer");
    [self hook_UINSVirtualMotionDevice_scanAccelerometer];
}
@end

@implementation PTSwizzleLoader
+ (void)load {
    [objc_getClass("UINSVirtualMotionDevice") swizzleInstanceMethod:NSSelectorFromString(@"_scanAccelerometer") withMethod:@selector(hook_UINSVirtualMotionDevice_scanAccelerometer)];
}
@end

As shown below, the actual update interval can be as short as 0.0001 seconds.

Some other games explicitly set the update interval to 0.01 or 0.02 seconds via [CMMotionManager setAccelerometerUpdateInterval:], so they do not have excessive CPU usage.

How to Fix
Hook [CMMotionManager init] and change the default update interval to 0.01 seconds.

[viatearz]

Related Games:
#189 Yu-Gi-Oh! Master Duel
PlayCover/PlayCover#1600 Princess Connect Re:Dive(CN)
PlayCover/PlayCover#1832 Ensemble Stars
PlayCover/PlayCover#456 Star Wars: Galaxy of Heroes
GODDESS OF VICTORY: NIKKE
Brown Dust 2
Shadowverse: Worlds Beyond
MementoMori
Solo Leveling: Arise
and many others.

[TheMoonThatRises]

If some games explicitly set the update interval, wouldn't it be safer to set this swizzle behind a settings flag?

[viatearz]

If some games explicitly set the update interval, wouldn't it be safer to set this swizzle behind a settings flag?

Yes, that would be safer. I will push the changes later.

[viatearz]

All changes submitted.