kaputnikGo / PilferShushJammer

Light Android AOSP application to test microphone jamming techniques to combat Cross-Device Tracking (XDT)

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

cpu doesn't go in deep sleep mode

35609902357 opened this issue · comments

When the jammer is active, the cpu doesn't go into deep sleep and the battery gets drained

Correct, thats the background service part of the OS running.

This means the jammer can't be on all the time, defeating its purpose

When the passive jammer is on it does no work for the cpu. the only cpu use is from the system background service and this implementation is dependent on the OS version and build. below is an image of the nominal profile showing the jammer using a background service for 1 day 19 hours, the percentage used is comparable to the basic OS use.

Battery_usage_test

It is a lot, especially for older devices. If you check with an app like CPU Spy you will notice the phone never sleeps, even with battery optimization enabled. So is there no way to keep the jammer on while allowing deep sleep?

To keep a running jammer hold on the microphone then a background service needs to run. If the phone went into deep sleep then that would mean there are no background services running. It is a problem and i have tried to keep all the cpu use to the barest minimum but as far as I know there arent any alternative methods on android.

If you are legitimately concerned about an app recording via the microphone then you could minimise the running time of the jammer to when you are using the phone and/or when a good quality audio recording is possible, ie not when your phone is in a pocket or a bag.

Research into this area has shown most record audio apps will tend to do so only when the screen is on as it means the phone is probably being used. Also this means that any activity by these apps can be covered by whatever the user is doing at the time. Some other apps just periodically wake up a record audio function, analyse and measure the quality of recording to determine if it is a suitable level and clarity and proceed from there or go back to sleep for some time.

Also this site https://reports.exodus-privacy.eu.org/en/ may help you determine a good course of action.

Thanks for your explanation. Do you think a toggle named "Battery saving" could be implemented? Its function, when enabled, would be to suspend the jamming when the phone is idle with the screen off, and resume it when the phone is awaken. When disabled it would behave as it does currently, preventing the cpu to go in deep sleep. Would it be feasible?