Related
I have been trying on and off for over a year to eliminate these horrible wakelocks without disabling location services all together, and have finally found a solution.
I have tried wakelock terminator, amplify, and various other tweaks without the results I was looking for. I could only stop them by disabling location completely. Even with GPS only enabled the phone will eventually want to find its location and then if you're in a building where there is no GPS single, it will kill your battery trying to find one. So I finally stumbled across SlimLP which is an AOSP rom that has app ops baked into it. I found that if I simply modify the permissions of google play services and not allow it to use location, and also disable its ability to hold a wakelock, the nlp wakelocks (both) are gone forever. However, as soon as nlp is gone, the phone falls back to its backup plan which is RILJ to locate itself. So I then went into the phone apps permissions and disabled location and wakelock for it too. FINALLY these wakelocks are gone forever. My phone now loses 3% over 8 hours without disabling location services. There are literally 10 or less wakelocks system wide over 8 hours while I sleep, which is a huge contrast to the waking once every 25 seconds to check my location (or whatever absurd rate it was doing it). The only thing I can spot thats out of place it that google play services is registering a ton of alarms for location related stuff in better battery stats. I'm happy with this so far but feel it could be even better once I learn more.
What I really want to do is to be able to apply this to any android phone, such as my girlfriends z3. Unfortunately I can only get this to work with AOSP roms that have app ops built into them. I tried adding app ops to google based roms and even aosp roms and it doesnt work the same. If anyone could tell me what is different about roms with app ops built in, that would be great. I think we should look into this more to learn as much as possible because this affects everyone with an android phone. Thanks for reading.
seh6183 said:
I have been trying on and off for over a year to eliminate these horrible wakelocks without disabling location services all together, and have finally found a solution.
I have tried wakelock terminator, amplify, and various other tweaks without the results I was looking for. I could only stop them by disabling location completely. Even with GPS only enabled the phone will eventually want to find its location and then if you're in a building where there is no GPS single, it will kill your battery trying to find one. So I finally stumbled across SlimLP which is an AOSP rom that has app ops baked into it. I found that if I simply modify the permissions of google play services and not allow it to use location, and also disable its ability to hold a wakelock, the nlp wakelocks (both) are gone forever. However, as soon as nlp is gone, the phone falls back to its backup plan which is RILJ to locate itself. So I then went into the phone apps permissions and disabled location and wakelock for it too. FINALLY these wakelocks are gone forever. My phone now loses 3% over 8 hours without disabling location services. There are literally 10 or less wakelocks system wide over 8 hours while I sleep, which is a huge contrast to the waking once every 25 seconds to check my location (or whatever absurd rate it was doing it). The only thing I can spot thats out of place it that google play services is registering a ton of alarms for location related stuff in better battery stats. I'm happy with this so far but feel it could be even better once I learn more.
What I really want to do is to be able to apply this to any android phone, such as my girlfriends z3. Unfortunately I can only get this to work with AOSP roms that have app ops built into them. I tried adding app ops to google based roms and even aosp roms and it doesnt work the same. If anyone could tell me what is different about roms with app ops built in, that would be great. I think we should look into this more to learn as much as possible because this affects everyone with an android phone. Thanks for reading.
Click to expand...
Click to collapse
Wrong section...you might want to try Xposed and Amplify.
EDIT: I just realized I posted wrong section. For some reason, I thought this was Android Dev. Sorry
niral7 said:
Wrong section...you might want to try Xposed and Amplify.
EDIT: I just realized I posted wrong section. For some reason, I thought this was Android Dev. Sorry
Click to expand...
Click to collapse
I've tried amplify as stated in the op. I'm surprised more people aren't bothered by wakelocks. I can't stand them.
seh6183 said:
I've tried amplify as stated in the op. I'm surprised more people aren't bothered by wakelocks. I can't stand them.
Click to expand...
Click to collapse
They're necessary to some degree. Google Now and other location-based/sync programs need them to work. They just get annoying when they're fired up every minute.
niral7 said:
They're necessary to some degree. Google Now and other location-based/sync programs need them to work. They just get annoying when they're fired up every minute.
Click to expand...
Click to collapse
Well I've disabled the wakelocks and every location service including google now still functions as normal. The only benefit is me gaining 50% of my battery back. I just need to figure out what is so special about AOSP ROMs that have app ops baked in so I can apply these techniques to other phones.
So the App Ops Xposed module doesn't work the same way?
hayzooos said:
So the App Ops Xposed module doesn't work the same way?
Click to expand...
Click to collapse
It works exactly the same except for some odd reason the wakelocks won't stop when you start disabling google play services and phone. It will disable other things without any problems. I'm thinking that maybe SlimLp has a different google play services app with different permissions or something. I'm not exactly sure what it is yet but I'm still looking into it on a daily basis. All I know is that 9000 wakelocks at the end of the day from google play services is UNACCEPTABLE and pisses me off. So I set out to find a way to stop them.
seh6183 said:
It works exactly the same except for some odd reason the wakelocks won't stop when you start disabling google play services and phone. It will disable other things without any problems. I'm thinking that maybe SlimLp has a different google play services app with different permissions or something. I'm not exactly sure what it is yet but I'm still looking into it on a daily basis. All I know is that 9000 wakelocks at the end of the day from google play services is UNACCEPTABLE and pisses me off. So I set out to find a way to stop them.
Click to expand...
Click to collapse
Glad you found a way to stop them and more so you decided to post your way to stop them here.
seh6183 said:
It works exactly the same except for some odd reason the wakelocks won't stop when you start disabling google play services and phone. It will disable other things without any problems. I'm thinking that maybe SlimLp has a different google play services app with different permissions or something. I'm not exactly sure what it is yet but I'm still looking into it on a daily basis. All I know is that 9000 wakelocks at the end of the day from google play services is UNACCEPTABLE and pisses me off. So I set out to find a way to stop them.
Click to expand...
Click to collapse
Cataclysm Rom also has a App Ops. So I assume i can get same improvements as you do?
Or am I wrong and thinking the opposite direction?
Zwambo said:
Cataclysm Rom also has a App Ops. So I assume i can get same improvements as you do?
Or am I wrong and thinking the opposite direction?
Click to expand...
Click to collapse
It should work yes. Go into google play services from apps, its in settings, then click modify, then disable location and wake lock. Do the same for phone. There are two phone apps and a dialer making it confusing. You'll want to disable the location and wakelock setting on the phone app which has the location toggle. The other phone app doesn't have a location toggle and you'll know that's not the right one.
After doing this, if you monitor with wake lock detector, you'll see that both NLP wakelocks are stopped completely instead of the 1000 an hour like usual. Same goes for RILJ. Google play services is still generating thousands of alarms each day for location related stuff and I have found a way to fix that as well but it needs more testing.
To put it simply, when my phone goes to sleep, that exactly what I want it to do, not appear as if its asleep and constantly check my location so that it can better offer me ads and places of interest near by.
Doesn't the Phone app NEED to be able to keep the phone awake, so that it doesn't go to sleep mid-call?
setspeed said:
Doesn't the Phone app NEED to be able to keep the phone awake, so that it doesn't go to sleep mid-call?
Click to expand...
Click to collapse
It has no effect on the function of the phone at all except to eliminate the RILJ wakelock. I'm pretty sure this wakelock is the phones radio trying to triangulate your position using cell towers but not sure.
All solutions I've seen or heard about untill now are just workarounds, and I found an elegant solution that allows geoloc to be on all the time.
I detailed it in a battery thread because of the savings it can offer : it consist of an app that replaces nlp with a local db : http://forum.xda-developers.com/showthread.php?p=59184505
I didn't try out with all google goeloc services but maps didn't seem to bother...
Gentaz said:
All solutions I've seen or heard about untill now are just workarounds, and I found an elegant solution that allows geoloc to be on all the time.
I detailed it in a battery thread because of the savings it can offer : it consist of an app that replaces nlp with a local db : http://forum.xda-developers.com/showthread.php?p=59184505
I didn't try out with all google goeloc services but maps didn't seem to bother...
Click to expand...
Click to collapse
My solution has zero impact on location services as well. You're saying that your method totally stops NLP wakelocks and if you were to open maps, it would lock your location precisely?
seh6183 said:
It should work yes. Go into google play services from apps, its in settings, then click modify, then disable location and wake lock. Do the same for phone. There are two phone apps and a dialer making it confusing. You'll want to disable the location and wakelock setting on the phone app which has the location toggle. The other phone app doesn't have a location toggle and you'll know that's not the right one.
After doing this, if you monitor with wake lock detector, you'll see that both NLP wakelocks are stopped completely instead of the 1000 an hour like usual. Same goes for RILJ. Google play services is still generating thousands of alarms each day for location related stuff and I have found a way to fix that as well but it needs more testing.
To put it simply, when my phone goes to sleep, that exactly what I want it to do, not appear as if its asleep and constantly check my location so that it can better offer me ads and places of interest near by.
Click to expand...
Click to collapse
Thx a million!
Will look in to those settings from the phone apps and google play services. Love it when the app ops is included in the ROM!
seh6183 said:
My solution has zero impact on location services as well. You're saying that your method totally stops NLP wakelocks and if you were to open maps, it would lock your location precisely?
Click to expand...
Click to collapse
The fact that the gapps have a mind of their own is not big news, but alternatives exists to avoid dealing with them☺
I didn't say it will stop any wakelock (and I don't want to) : on the contrary, it consist of replacing the stock nlp with a more evolved one that allows to switch to a local db which is far less battery consuming for several reasons.
I didn't say it was "gps precise" either : it will locate you at the nearest antenna if you try a gps app like maps (did you actually read my link ?). Most of the time it has between 500m and 1500m (about a mile) uncertainty reported by the apps.
It just provides precise enough geoloc services for 95% of the apps you're using, even with your screen off like weather, loc. based profile mangers, local news, traffic, job/dating app or whatever... Granted : it won't compete with gps for you navigation or atronomy app but that's the 5% left when you'll switch the gps on ?
There should be a reason why you have so much wakelocks that does not involve blocking calls from a middleware as an answer.
Gentaz said:
The fact that the gapps have a mind of their own is not big news, but alternatives exists to avoid dealing with them
I didn't say it will stop any wakelock (and I don't want to) : on the contrary, it consist of replacing the stock nlp with a more evolved one that allows to switch to a local db which is far less battery consuming for several reasons.
I didn't say it was "gps precise" either : it will locate you at the nearest antenna if you try a gps app like maps (did you actually read my link ?). Most of the time it has between 500m and 1500m (about a mile) uncertainty reported by the apps.
It just provides precise enough geoloc services for 95% of the apps you're using, even with your screen off like weather, loc. based profile mangers, local news, traffic, job/dating app or whatever... Granted : it won't compete with gps for you navigation or atronomy app but that's the 5% left when you'll switch the gps on
There should be a reason why you have so much wakelocks that does not involve blocking calls from a middleware as an answer.
Click to expand...
Click to collapse
If its crippling the phones ability to locate itself accurately then I am not interested as occasionally navigation is important to me. Also of it doesn't stop wakelocks then I am certainly not interested. The way that you word things makes it very difficult to get your point across I might add. I had a hard time following your post.
What I did to get zero battery drain with GPS set on high accuracy:
- Download Disable Service from Google Play: https://play.google.com/store/apps/details?id=cn.wq.disableservice&hl=nl
- Go to System, then Google Play Services and disable everything that has something to do with 'Wear' and 'Fitness' since I don't use any of these features (for me these gave me wakelocks, but I'm not sure if this is the case for everyone), so: BrokeredFitnessService, WearableControlService, WearableService and WearableSyncService.
- Download LBE Security Master (http://forum.xda-developers.com/showthread.php?t=1422479) for its permission manager.
- Disable any location permission of all your apps that you don't want to use GPS (and other permissions to save more battery, but that's another topic).
I have to say I have Google Now disabled, and of course my phone is rooted to be able to use these apps. I run stock rom with stock kernel, and my battery is great with GPS enabled constantly.
seh6183 said:
If its crippling the phones ability to locate itself accurately then I am not interested as occasionally navigation is important to me. Also of it doesn't stop wakelocks then I am certainly not interested. The way that you word things makes it very difficult to get your point across I might add. I had a hard time following your post.
Click to expand...
Click to collapse
I guess you missinterpreted what I said : just enable gps when you need navigation... Gsm based location accuracy is ok for all the rest.
- wakelock issues either came from the way the phone is set up or an uncommon situation causing this (bug, bloat, bad network or gps reception...) : blocking them is not a solution, it's a workaround and, if I undestood you correctly, is only valid for some cases and is fastidious/maintenance intensive. There are already many nexus 5 and other threads dealing with those issues anyway and It would be easier to just disable geoloc when screen is off.
- I suggested a solution less battery draining for 95% of goeloc based needs and is valid for most android phones and roms as long as you have root, not yet another a nlp/wakelock blocking "trick".
It's ok if your girlfriend doesn't mind having her z3 flashed with an ASOP ops enabled rom and learn to block the wakelocks of the new apps she installs, but I prefer not having to explain mine what a wakelock is ☺
- It doesnt cripple your phone at all, it extends its possibilities by adding a gsm based backend to the location provider : your phone was already doing the same except it had to go to a google hosted database to match your location to your antenna or ip when it is set to use network based location.
Gentaz said:
I guess you missinterpreted what I said : just enable gps when you need navigation... Gsm based location accuracy is ok for the all the rest.
- wakelock issues either came from the way the phone is set up or an uncommon situation causing this (bug, bloat, bad network or gps reception...) : blocking them is not a solution, it's a workaround and, if I undestood you correctly, is only valid for some cases and is fastidious/maintenance intensive. There are already many nexus 5 and other threads dealing with those issues anyway and It would be easier to just disable geoloc when screen is off.
- I suggested a solution less battery draining for 95% of goeloc based needs and is valid for most android phones and roms as long as you have root, not yet another a nlp/wakelock blocking "trick".
It's ok if your girlfriend doesn't mind having her z3 flashed with an ASOP ops enabled rom and learn to block the wakelocks of the new apps she's installing, but I prefer not having to explain mine what a wakelock is
- It doesnt cripple your phone at all, it extends its possibilities by adding a gsm based backend to the location provider : your phone was already doing the same except it had to go to a google hosted database to match your location to yourantenna or ip when it is set to use network based location.
Click to expand...
Click to collapse
Your solution is very interesting for sure and something I will try, but my gut feeling is that google play services is still going to look for my location just as often, waking the phone, even though it's communicating with a different database.
Also I'm not sure if you're suggesting that my phone specifically is having NLP wakelocks because it is broken or setup incorrectly, but if so that is totally inaccurate. All android phones are suffering from this wakelock whether the user is aware of it or not. The only ones not having NLP wakelocks are the ones who have disabled location services or somehow turned off the wakelock like I have.
Hi, I'm not looking anything Illegal. I hope someone can point me in the right direction. This would just collect time stamps already shown.
I want a time tracking app for FB.
It can be run off a browser. It would goto a selected friends message and according to the time stamp document their FB time.
Example. Already on FB in the message top it states Active Now, Active 7 minutes ago.... It would just check and log according to the preferences.
It would produce a time log. Active from 12:02 am - 3:am Active from 7:01pm-7:05pm.
Is this already out there?
20GT said:
Hi, I'm not looking anything Illegal. I hope someone can point me in the right direction. This would just collect time stamps already shown.
I want a time tracking app for FB.
It can be run off a browser. It would goto a selected friends message and according to the time stamp document their FB time.
Example. Already on FB in the message top it states Active Now, Active 7 minutes ago.... It would just check and log according to the preferences.
It would produce a time log. Active from 12:02 am - 3:am Active from 7:01pm-7:05pm.
Is this already out there?
Click to expand...
Click to collapse
Hi there, I think I understand what you want but not sure it's possible. Facebook only says the last time you were online / active, so it doesn't record the spaces between old posts.
For example, for the following
Bob : Posts a status update a 8:00 am
Bob : Stays online, just reading and looking at other peoples posts
Bob : Posts a status update at 10:00 am
Bob : Goes offline straight after posting the message
Fred : Posts a status update a 8:00 am
Fred : Goes offline straight after posting the message
Fred : Posts a status update a 10:00 am
Fred : Goes offline straight after posting the message
For both users, if you look at their page it will suggest that they were last active at 10:00 am but it won't tell you that Bob was online the whole time since 8:00 am but Fred wasn't. So all you would be able to assume at best is that the person has been online continually ever since their first post was ever made (or that day, but that assumes they weren't on Facebook prior to midnight until past midnight).
Yes you are correct. They could be online.
I only want to know when they are active.
I almost have a macro for PC written to screen shot that area.
OCR it, and save it in note pad with a time stamp.
But I would rather have an app.
20GT said:
Yes you are correct. They could be online.
I only want to know when they are active.
I almost have a macro for PC written to screen shot that area.
OCR it, and save it in note pad with a time stamp.
But I would rather have an app.
Click to expand...
Click to collapse
Are you wanting this app to work without being visible on screen? Taking a screenshot is the wrong way to go about "screen scraping" the data, you should be getting the raw HTML data and then parsing that to get the information that you want, it would be much more optimal than performing OCR on a screenshot. If you want this app of yours constantly monitoring other users then it would have to work without being visible on screen. I'm new to Android in particular so not sure what class you would need to act as a http client to obtain the data.
But I think you just missed my point, you can't tell how long they have been active. You're making a guess and assuming they haven't gone offline during posts. Just because I posted twice in an hour, doesn't mean I was active on facebook that whole time. All you can tell from the information is,
1. What that have posted and when
2. When they last posted
---------- Post added at 02:24 PM ---------- Previous post was at 02:23 PM ----------
what exactly do you mean by "active"?
---------- Post added at 02:29 PM ---------- Previous post was at 02:24 PM ----------
This article shows how to download an image programatically
http://www.helloandroid.com/tutorials/how-download-fileimage-url-your-device
You'd need to download he page via its URL and then parse the HTML data.
---------- Post added at 02:35 PM ---------- Previous post was at 02:29 PM ----------
Another example of downloading a file programatically,
http://wininterview.blogspot.in/2013/04/download-file-in-android-from-remote.html
byte[] buffer would contain the data you want in the downloadFile method, this would be the raw HTML data for the page (what you see when viewing the source for the page in the browser).
Thanks for the links and advice.
I am not a programmer and was only use the tools that knew how to use.
It's running on my pc. But i would prefer an app to do this.
It doesn't have to be hidden. I am using macro mouse to run my work around.
I don't think you are correct about the FB activity. I am following this person and would know if they posted. So apparently they are either messaging or browsing. They are not very popular so I believe it's browsing for the amount of time that they are active.
From the horses mouth so to speak
https://www.facebook.com/help/community/question/?id=486660488085628
"When you view your conversations in mobile messages, you'll see how recently your friends interacted with Facebook."
Active 10 minutes ago would mean, they interacted with Facebook 10 minutes ago. It doesn't say how long they have been interacting with Facebook for, so if you want to build up a map of when someone is interacting with Facebook, that is not possible. You may be better asking over on the Facebook developers forum to clarify this or maybe find an alternative way to achieve what you want.
https://www.facebook.com/groups/fbdevelopers
niknak75 said:
Active 10 minutes ago would mean, they interacted with Facebook 10 minutes ago. It doesn't say how long they have been interacting with Facebook for, so if you want to build up a map of when someone is interacting with Facebook, that is not possible.
Click to expand...
Click to collapse
correct so"Active 10 minutes ago" would mean, they physically interacted with Facebook 10 minutes ago. They were not asleep they actually picked up there phone or mouse and physically interacted with facebook.
20GT said:
correct so"Active 10 minutes ago" would mean, they physically interacted with Facebook 10 minutes ago. They were not asleep they actually picked up there phone or mouse and physically interacted with Facebook.
Click to expand...
Click to collapse
So I wonder if they are physically interacting with Facebook only every 10 minuets this will always say 10 minutes ago.
when they pause browsing it show be re-starting the counter correct.
so recording the changes in this status depending on Facebooks refresh limit one could document a creepy map of when someone is physically interacting with Facebook.
Short description: A fan-made mobile version of Cards Against Humanity
Full description: This is a card game
Now, my full description used to be a lot more detailed than that, but I cut it down to the bare minimum to try to narrow down why Google keeps rejecting me.
Obviously they don't like "Cards Against Humanity" being in there. This is the email I keep getting:
"Thanks for submitting your app to Google Play. I reviewed <app name here>, and noticed some keyword spam issues that need to be corrected.
Here’s how you can submit your app for another review:
Sign in to your Developer Console and remove any irrelevant keywords from all translations of your store listing.
Review your app to make sure it’s in compliance with the keyword spam policy and all other policies listed in the Developer Program Policies.
Submit your app."
I searched and there are plenty of apps on the play store with multiple mentions of "Cards Against Humanity" throughout their descriptions. Mine used to be one of them. But now, when I update my app, any mention of "Cards Against Humanity" gets rejected.
Google's support has been absolutely horrendous on this matter. I tried their chat support to which they said we don't handle policy issues through chat and their email suggestions have been very vague as you can see above.
Has anyone else run into anything like this? I feel like I'm screwed. I spent a very long time developing this app and now nobody is going to be able to find it because I can't mention the actual game that it's based on.
Our update rejection reason
We got into this loop but our mistake was entirely innocent. In editing the Play Store description we were using cut and paste to move some sections around...problem was we did 'copy and paste' neglecting to remove the original reference and so there was sentence (bullet item actually) that was repeated. The submission was under review for a long, long time...days when the normal time was minutes. When we finally got the rejection the generic description of the problem didn't come close to pointing at the specific issue, just referenced the guidelines. I suppose this looked like keyword stuffing.
Another lesson we learned is when you get into the review cycle just let it finish out; if you resubmit the whole review process starts over in that you are pushed to the back of the line.
Eventually we figured out the problem and we got back to the usual processing times.
Update 09.12.17: The methods below may not fully work on the latest OS versions. There is an ongoing discussion in the last pages so I hope it gets cleared out eventually, sadly I've been busy with my studies and haven't touched my phone since initially making this thread (it's on OOS 4.0.2). I write this just to make sure I don't waste your time accidentally, so please check the latest replies if you're on newer OS versions.
Hello everybody,
*the undermentioned methods and app(s) require root*
I have asked you guys in the AKT thread if you would like to see a small tutorial on how to stop the constant "com.google.android.gms/.measurement.PackageMeasurementService" and "net_scheduler" wakelocks that might or might not be responsible for the device waiting longer than it should before dozing off.
Please keep in mind that this method does work for me, and might or might not work for you, as everybody uses different things/apps so in case you see unwanted behavior, just revert back and sigh that the method has failed you.
I am not responsible for any hardware-/software damage that may occur upon using these settings.
So, now that we've got all the generic stuff out of the way, first few words about why this might bother you:
1) You don't like your device doing stuff you didn't make it do.
2) You want to minimize wakelocks
3) You're here because you just saw the two beforementioned wakelocks and already decided you want to get rid of them.
So, regarding the first one, all I can say is I got the method from this reddit post , which briefly explains which services are doing the waking and what they are. Starting with "At the heart of Firebase is Firebase Analytics, a free and unlimited analytics solution. .." got me raising an eyebrow, as I don't like handling control of my device to other people, without me even knowing.
UPDATE: I have merged the two approaches into just using one app and making the changes on a global level, so you can just do them in like 5 minutes and forget about it, but in case you have problems with disabling package measurement you can also check the hidden text just below for instructions using another app, which was basically "the old way".
So to get rid of the "snooping", as already described in that post, you need to download MyAndroidTools.
Disclaimer: Disabling some services/receivers may "crash" the app. I found it is normal, just go back to where you were and check if you managed to disable the thing you wanted, if yes, then it was successful.
1. Open the app
2. Click on the top left to open the panel, click on Broadcast Receiver.
3. On the menu that opens go to the right column named System. Click search on the top right, type "Play" and choose the Google Play Services option.
4. In the search bar there type at least "ana" and disable the two found results with the names "AnalyticsReceiver" and "AnalyticsSamplerReceiver"
5. Hit x and search again for at least "meas". You will see three results with the names "AppMeasurementInstallReferrerReceiver", "AppMeasurementReceiver" and "PackageMeasurementReceiver*". Disable all three.
****Update 15.02.17*** Apparently this one resets every once in a while, I blame this again on Google's efforts to have their spying on, but anyways. Go to services->system->Google Play Services->search "meas"->disable both "AppMeasurementService" and "MeasurementBrokerService". The third one (PackageMeasurementService) will restart too so don't bother. This should do the trick though.
6. There was discussion about "Campaign Tracking" . I only found it in the same System menu, in Android Pay, by searching at least "cam" you get the result "CampaignTrackingReceiver". Disable it if you feel you want to. I don't use Android Pay and cannot say if it breaks something there, but otherwise have it disabled and haven't noticed any problems so far.
7. Search for Google Play Store in System. In that option, search for at least "app" and disable "AppMeasurementReceiver". Hit x and search for at least "fir", then disable the two results with names "FirebaseInstanceIdInternalReceiver" and "FirebaseInstanceIdReceiver"
8. Done. All the setttings are now global for any sort of app measurements, as far as I know.
This is the "old way" of dealing with app measurement. If you have done the steps above just ignore (hide) this part and continue with disabling net_scheduler below.
So to get rid of the "snooping", as already described in that post, you need to download Root Package Disabler or equivalent alternative.
ATTENTION: As per the last version of the app, I see there might be a bug which reverts some settings when you use the search bar, so please try and find the services by hand in stead of searching, as it is more reliable.
1. Open the app
2. Start with the left-most pane, e.g. "Installed". There you can see all your installed apps
3. Click on the first app on the list, it will display a small menu. Apps that use services will have the bottom-left option named "SERVICES" available, click there. This will take you to the services list that this app uses.
4. Click on the searching icon on the top-right in order to filter the services we need disabling.
5. Write at least "appm" . If the AppMeasurementService is used by this app, it will now be displayed.
6. Tick that off (the switch will turn gray)
7. Hit x, and search again for at least "fireb". This will display all services that use the Firebase SDK. You may also check under the name of the service and see the word is contained in the "executable name", so it might not always have "an official" name that states Firebase, but still use one of their "executables" (sorry for lack of detail)
7.1 Check for any other services that have "analytics" in their description, although I haven't checked if this stops something useful, but I doubt it.
8. When you're done with the current app, it will no longer call these services and cause wakelocks as long as the services remain stopped. To my experience the settings stay after reboot, it's just the above mentioned bug you have to keep in mind since it happened to me now while making the guide, and I know it came with the latest update.
9. Go back to the installed pane and maybe tick on the star next to the app in question. It will be added to the "favourite" list where you can have all those apps and don't bother to search them again if needed.
10. Repeat from step 1 for the next app and go through all your apps. If not you will still get calls to this service from the apps that still have these services on. Also a reminder here, you have to remember and check every new app you install, as most apps do have the service enabled.
11. After you're done with all apps in "Installed", check out bloatware (I think I haven't found anything there, but it's worth checking).
12. "System" apps that I know have some of those services: Calendar, (probably) Chrome (I have that disabled so dunno), Drive, Duo, Gboard, Google Play Services, Google Play Store, Google VR Services.
Here are two pictures how an app's services list looks like, and one with some of the services disabled:
all services on
some services off
After doing these steps, you should charge your battery to 90% to reset the battery statistics and you should see that the "com.google.android.gms/.measurement.PackageMeasurementService" wakelock no longer occurs (or stays really, really low, and not thousands like before). If you still have it after all this, then you probably have an app you haven't disabled the services for.
The second approach will get rid of the "net_scheduler" wakelock. Thanks to @denon480 for the idea, it's post #34 in this thread It involves installing (again) MyAndroidTools or equivalent alternative.
1. Open the app
2. Click on the top left corner to open the menu panel.
3. Click on Broadcast Receiver
4. Navigate to the System pane
5. Click on search on the top right. Search for Google Play Services. Click on them when they show up
6. In the search top right, write at least "sche" and you will see the two receivers responsible for the "net_scheduler" wakelock, "SchedulerInternalReceiver" and "SchedulerReceiver" . Here's a picture how it looks
7. Switch the first one off. The app will quit, don't worry.
8. Go back to where you were (steps 1 to 6) . You will see that you indeed managed to swtich that receiver off.
9. Switch the second one off. The app will quit, again no worries.
10. Check if you managed to switch the second one as well. After that you're done!
I hope I could help you guys out. I know there is nothing fancy in these methods but felt a thread might be useful as I saw a good number of requests when I mentioned it in the AKT thread.
Also sorry for misleading the guys I already told it was going to be a short guide, I honestly thought it would take way less words than it did. But I think it is for the better.
Have fun.
* Reserved *
Going through this guide, I was able to get the services disabled through root package disabler, bit my android tools kept force closing for some reason.
*edit* uninstalled, rebooted, reinstalled, and was able to get the app to stay open, and got them disabled. I'm curious to see what my wake locks are going to look like tomorrow. This is pretty much the nougat answer to amplify, huh? =)
MeggaMortY said:
* Reserved *
Click to expand...
Click to collapse
I think Everything is fine or?
tzbigworm said:
Going through this guide, I was able to get the services disabled through root package disabler, bit my android tools kept force closing for some reason.
*edit* uninstalled, rebooted, reinstalled, and was able to get the app to stay open, and got them disabled. I'm curious to see what my wake locks are going to look like tomorrow. This is pretty much the nougat answer to amplify, huh? =)
Click to expand...
Click to collapse
Hope it gets rid of those for you too. If I remember correctly I noticed the problem since Nougat, but then again I've been on Android since only a few months, coming from a big pause. Last time I was around we were rocking the HTC HD2 and had to deal with very different problems.
1+3_FA said:
I think Everything is fine or?
Click to expand...
Click to collapse
Yup looks great.
MeggaMortY said:
Hope it gets rid of those for you too. If I remember correctly I noticed the problem since Nougat, but then again I've been on Android since only a few months, coming from a big pause. Last time I was around we were rocking the HTC HD2 and had to deal with very different problems.
Click to expand...
Click to collapse
Crazy how much of a beast that phone was. People forget it's actually a windows phone, Android was put on it so much lol!
Thanks for the tips. Works great!
Thank you for your awesome work!
I have two more questions:
1. What about CampaignTrackingService? Could we disable this one as well?
2. In MyAndroidTools under Broadcast Receiver there are lots of receivers like AppMeasurementReceiver or FirebaseInstanceIdReceiver. They also need to be disabled or disabling the corresponding service is sufficient?
Thank you very much
youknownothing said:
Thank you for your awesome work!
I have two more questions:
1. What about CampaignTrackingService? Could we disable this one as well?
2. In MyAndroidTools under Broadcast Receiver there are lots of receivers like AppMeasurementReceiver or FirebaseInstanceIdReceiver. They also need to be disabled or disabling the corresponding service is sufficient?
Thank you very much
Click to expand...
Click to collapse
1. I initally disabled that in a few apps and didn't have problems System-wide or with the apps. So you can give it a go and in case of apps not functioning you can revert those back.
2. No for now it's okay to just use the Package Disabler for that. Like I said both apps have similiar functionality, there's probably a way to find the right service/receiver and disable it globally from MyAndroidTools, then we won't need the Package Disabler. But since it did work for me and I don't install new apps more than like once a week, I just didn't bother figuring it out. I can only say that disabling certain services/activities in MyAndroidTools can brake functionality or even bootloop your device, so be very careful in case you wanna find out if it's possible.
MeggaMortY said:
1. I initally disabled that in a few apps and didn't have problems System-wide or with the apps. So you can give it a go and in case of apps not functioning you can revert those back.
2. No for now it's okay to just use the Package Disabler for that. Like I said both apps have similiar functionality, there's probably a way to find the right service/receiver and disable it globally from MyAndroidTools, then we won't need the Package Disabler. But since it did work for me and I don't install new apps more than like once a week, I just didn't bother figuring it out. I can only say that disabling certain services/activities in MyAndroidTools can brake functionality or even bootloop your device, so be very careful in case you wanna find out if it's possible.
Click to expand...
Click to collapse
Thank you for your quick response. I'll give it a try, if anything goes wrong I'll let you know.
Is there any difference between Package Disabler and Disable Service app? I've tried the former, but it was really buggy. Scrolling was so glitchy and with lots of stutters that I've accidentally disabled few services. So I've used Disable Service with success. Now I only wonder whether both apps have the same functionality. Do you happen to know that?
Thanks in advance
youknownothing said:
Thank you for your quick response. I'll give it a try, if anything goes wrong I'll let you know.
Is there any difference between Package Disabler and Disable Service app? I've tried the former, but it was really buggy. Scrolling was so glitchy and with lots of stutters that I've accidentally disabled few services. So I've used Disable Service with success. Now I only wonder whether both apps have the same functionality. Do you happen to know that?
Thanks in advance
Click to expand...
Click to collapse
Assuming you're disabling services, which we are lol (should've been more obvious for me too I guess), I'd say you should be fine, and even say maybe the same goes for just using MyAndroidTools, just scroll through the Service menu in Table Third-Party and you'll see the same settings you applied with the other app/Package Disabler. I guess I was lazy to realize that since I liked I can favourite the apps I need to keep an eye on in the Package Disabler.
So all in all you should be okay, but even better you may try and just use MyAndroidTools for both. I have some exams coming so I won't be able to test those things but will make sure to update the tutorial if indeed that turns out to be right (for the app you suggested or even just MyAndroidTools).
Give a shout in case you find out something more. And thanks for the info
Followed the guide, thanks for this like said before kind of amplify for nougat. But as I was disabling net.schedule I noticed "my android tool" can do the fire base and app activity. Under service activity and press <...>
I suppose that this two methods doesn't compromise any function of the device right? For example loosing notifications or similar
Sent from my OnePlus 3
Mr.Jay said:
I suppose that this two methods doesn't compromise any function of the device right? For example loosing notifications or similar
Sent from my OnePlus 3
Click to expand...
Click to collapse
Like mentioned, it works fine for me, and probably depends on personal usage. I don't use Google Pay for example, and Chrome, and Google Music.... but besides those I haven't had problems anyway.
Disabled everything that is said to do in this thread and it worked great while I was at home while on wifi. I had drain of .5% an hour at times. However today while at work and on LTE, drain went up to 2.6% an hour, plus wakelocks from play services was waking up the device on average over 3 times a minute. When I looked into it further there was one service under play services where all the alarms were coming from. I do have a screenshot of this. Anyone have any insight to this? For the record, I do keep location off on my device.
Edit: I wonder f it comes from moving around a lot, as I'm always on the move as I manage a restaurant. Its not really a major drain, but still makes me wonder.
NJGSII said:
Disabled everything that is said to do in this thread and it worked great while I was at home while on wifi. I had drain of .5% an hour at times. However today while at work and on LTE, drain went up to 2.6% an hour, plus wakelocks from play services was waking up the device on average over 3 times a minute. When I looked into it further there was one service under play services where all the alarms were coming from. I do have a screenshot of this. Anyone have any insight to this? For the record, I do keep location off on my device.
Edit: I wonder f it comes from moving around a lot, as I'm always on the move as I manage a restaurant. Its not really a major drain, but still makes me wonder.
Click to expand...
Click to collapse
Have you disabled location history in the Google App? The problem is this guide fixes only one concrete aspect of the whole "Google stalking experience" shenanigans. Please check for the thing I mentioned and also in Settings -> Backup & Reset, make sure Back up my data is off if you haven't logged in an account and intend to use that - these two things were also draining battery for me when I was on the go as far as I can remember.
LMcR92 said:
Followed the guide, thanks for this like said before kind of amplify for nougat. But as I was disabling net.schedule I noticed "my android tool" can do the fire base and app activity. Under service activity and press <...>
Click to expand...
Click to collapse
I did some checking on that list and am currently testing a way to only use MyAndroidTools for the whole aproach. If it turns out to be working the whole guide would get reduced to like 10 clicks, since the settings are global. I'll post more info after a day or so to make sure it is working, but as for now I see promising results.
Anyone used Franco's Servicely app to do this?
Up, I have updated the guide to just using MyAndroidTools and disabling the receivers on a global scale. So now you just have to do it once and (hopefully) forget about it.
MeggaMortY said:
Up, I have updated the guide to just using MyAndroidTools and disabling the receivers on a global scale. So now you just have to do it once and (hopefully) forget about it.
Click to expand...
Click to collapse
Will Doing like #1 post notifications from Gmail?
techusthad said:
Will Doing like #1 post notifications from Gmail?
Click to expand...
Click to collapse
Don't know what you mean by #1 - disabling the AppMeasurement stuff, e.g. first set of instructions? I haven't had problems with Gmail and I use it with two accounts on there.
Found the following log in my files last night after a period of issues with my phone such as the notifications being reset, various digital wellbeing entries disappearing and some data loss etc despite me quite literally only using this thing for Facebook and YouTube.
Ignoring additional back story (someone else uses my phone regularly, need to know what's been done before I take issue with it), what on earth is going on in this log, and why/how was it even generated in the first place?
I'm autistic so unfortunately I have found myself both unable to drop this or find answers so I figured I'd look here.
If someone could explain if this is normal everyday behaviour for the phone, and if not what would be needed for this to happen (never seen the log before and it's in a folder with thousands of others, most of which are in an "adlg" folder).
To clarify, I did not request the logs nor do I know how to get them to generate so I am completely at a loss here.
Thanks so much!
This looks like same topic as started by @Baguete2963....
Are you posting under different names?
OnnoJ said:
This looks like same topic as started by @Baguete2963....
Are you posting under different names?
Click to expand...
Click to collapse
Nice catch! I'll take it from here.
Thread closed!