Related
Awesome ROM - thanks for sharing your work!
I flashed the standalone 4.0 followed by the 4.01 update. Now I'm grabbing extras a bit at a time. Some observations/questions:
1. When I boot/reboot, I let the phone settle in (read SD,etc). I unlock, but then Launcher Pro is completely unresponsive. I must long press home button & use task mgr to kill it. When it comes back, all is good until next reboot.
2. I restored downloaded apps using Titanium. Market is not recognizing any as installed. First time I've gone this route. Expected?
3. I can't back out of Contacts; gotta use Home button.
4. Recently edited Memos don't come to the top of the list. Can that be reverted to the 2.1 behavior?
Small stuff in view of super clean, super cool ROM.
Thanks again!
It's disappointing, but I feel certain this post would have gotten a reply or some comments if posted in the Dev section. Here in the General section, it's either remained below the radar or been ignored. Can a mod or admin tell me if there was a more appropriate place for my post? Obviously, I haven't met the 10 post minimum, or I would have popped it in the Dev section in the Blackhole thread where others are posting their observations and feedback of that ROM. Thanks.
upgrade to Blackhole 4.2
Might as well work my way towards the 10-post minimum so I can post to the dev section where discussion actually happens...
I followed this thread to get CWM shaped up:
http://forum.xda-developers.com/showthread.php?t=957132
Trying a backup initiated through ROM Manager resulted in badness, so I repeated the steps for CWM (using Odin). BTW, I had to boot the phone once without the SD card to move past being stuck at the Samsung logo. I then rebooted into CWM (red) and did a backup.
Then I followed SoS's instructions and installed the standalone 4.2:
http://forum.xda-developers.com/showthread.php?t=940456
As long as I was just working within CWM, I was fine. ROM Manager is totally hosed. It really can only be used now to browse the ala carte options. Trying to install through it results in being stuck at the Samsung logo. 3-fingered booting from powered off doesn't even work. Repeat the CWM fix (using Odin) and boot once without the SD card.
To get around ROM Manager Madness, I use it to pick the options I want, then cancel the final step, reboot into recovery from a long press of the power button and use CWM to install the individual zips. Fine.
The original oddities in Blackhole 4.x are still present on my device. The two that are most bothersome: [1] I can't back out of contacts [2] Launcher Pro is unresponsive after booting.
For the contacts issue, create a new link to contacts from the app drawer and use the new one to replace the existing.
good day.
chopper the dog said:
For the contacts issue, create a new link to contacts from the app drawer and use the new one to replace the existing.
good day.
Click to expand...
Click to collapse
Thanks for the reply, I'll try that.
Worked great, thanks!
clock lag persists
Initially I thought that the clock lag I was experiencing in 4.01 was gone in 4.2. Nope, it remains. As others have said, seems to be related to enabling Wi-fi.
I'll go check the threads for updates but, last I checked, a double reboot was the suggested fix. I'm not clear whether people were suggesting that to be some sort of permanent fix. It didn't seem to be for me.
The time would correct after the first reboot and I would reboot again to comply with the posts, but I <think> the problem would return under 4.01. Now under 4.2, I'm sure. Last night, I double-rebooted and this morning the clock was 20 minutes slow.
Like I said, I'll go looking for updates now. Could be that this has already been resolved for real.
voice recorder, car home
Just adding a couple more oddities to the current list: voice recorder force closes and car home doesn't come up automatically when you plug in to the car cradle.
Reloading the voice recorder zip through CWM was about the only tactic I tried with no luck. Then I wanted to grab something for the ROM over-the-air, but the site was down. Checked in here and saw there was a problem with the host. That interruption of being able to download pieces parts OTA was kind of the proverbial straw, so I'm trying a SuperClean.
Pushed it through Odin and the process was smooth. The ROM looks good. None of the same oddities except the clock lag. I'm changing the sleep state of Wi-fi to see if that makes a difference.
SonofSkywalker does amazing work and I'm sure I'll be trying his ROMs again. For now, though, something different.
clock lag fix?
as per a forum suggestion, I changed the Wi-fi sleep setting. So far, it seems to prevent clock lag.
Home Screen | Menu | Settings | Wireless & Network | Wi-Fi settings | Advanced | Wi-Fi sleep policy -> select 'When screen turns off'.
Does anyone know if this has been an issue in the VZW full stock 2.2?
battery life is better
Under Super Clean 2.6, launching Google Maps and exiting has released the wake lock and battery life is much better.
Does a user guide, sticky or FAQ exist for Spare Parts? I could see that "other | running" was 100%, but I wasn't sure how to zero in on what was causing it other than trial and error based on other users' posts.
unread email count
A quick search of the forums didn't turn up much discussion, so I'll throw this out there:
on DL30 leak, the general email icon would increment and not decrement or clear until mail was manipulated on the phone. In other words, if it said 3 unread messages and I used Outlook (or the mail provider's web mail) to deal with them, it would sync and accurately display the message state in the list of emails - but the email icon on the home screen would still show 3. If 3 more came in and again they were dealt with elsewhere, the icon would go to 6. Only if action was taken on the phone itself would the counter "get real".
On Blackhole 4.x and SuperClean 2.x (any custom EB01 ROM?), the email icon on the home screen doesn't show an unread count (fine by me, I don't miss it), but when you pull down the notification bar, the unread count there acts exactly the same way.
Anyone else experiencing this? Devs, can it be fixed?
Did you clear your cache and davlik? I had some issues(when I closed an app none of my apps would show up and overall everything was running really slow). However when I was on superclean 2.6 I cleared my cache and davlik(for the first time) before I upgraded to superclean 2.8 and overall everything is working no problems.
thanks i havent used anything but sc!
Been getting them, more often (or at least it feels like it).
Generic message, so I can't tell which app or system generating them.
How would you troubleshoot this, without phone reset?
Brand new and Bone stock 4.3, haven't had a chance to root yet.
Thanks.
gidal said:
Been getting them, more often (or at least it feels like it).
Generic message, so I can't tell which app or system generating them.
How would you troubleshoot this, without phone reset?
Click to expand...
Click to collapse
One way to solve it isn't nice, but it works:
1. Root, make nandroid backup (subsequent steps are risky), and install Titanium Backup
2. Filter for user apps
3. Disable everything
4. Reboot and confirm that problem is gone.
5. Enable the first 1/2 of the apps. (In the batch operations menu, long press an app in the middle and choose "Select all below".)
If the problem has returned:
- Of the enabled apps, one is bad. Disable half of those enabled apps.
- Go to step 5.
If the problem is still gone:
- One of the still disabled apps is causing the problem. Enable half of the most recently disabled apps.
- Go to step 5.
This method is a little time consuming, but not as bad as it seems. For 125 user apps, it will take 7 iterations to find the culprit. For fewer user apps, it will take less time. If you disable ALL user apps and the problem persists, the issue is with system data and you need to wipe some system app's data or factory reset.
fenstre said:
One way to solve it isn't nice, but it works:
1. Root, make nandroid backup (subsequent steps are risky), and install Titanium Backup
2. Filter for user apps
3. Disable everything
4. Reboot and confirm that problem is gone.
5. Enable the first 1/2 of the apps. (In the batch operations menu, long press an app in the middle and choose "Select all below".)
If the problem has returned:
- Of the enabled apps, one is bad. Disable half of those enabled apps.
- Go to step 5.
If the problem is still gone:
- One of the still disabled apps is causing the problem. Enable half of the most recently disabled apps.
- Go to step 5.
This method is a little time consuming, but not as bad as it seems. For 125 user apps, it will take 7 iterations to find the culprit. For fewer user apps, it will take less time. If you disable ALL user apps and the problem persists, the issue is with system data and you need to wipe some system app's data or factory reset.
Click to expand...
Click to collapse
Thanks - very good troubleshooting technique.
I'll do that this weekend. I'm afraid it's due to some system apps that I disabled. Thing is, I reenabled all and still getting the toasts. I'll probably do a factory reset and install my apps one at a time.
What's weird is, this is what I usually do when I get new Android device. Only this N4 responds differently to my initial set up process.
Found the culprit, it was flip silent. I didn't suspect it at first since I've been using it with my other Android devices, including on CM10.2 (4.3), and never ran into toasts issue like with N4.
I've posted this guide on reddit already, but thought it might be useful here as well. A lot of users promote intense usage of package disablers to reduce battery drain, but this is not required to such an insane extend.
---
After experimenting with my S8 for 2-3 months now, I've collected some data and constructed some basic idea on how to fight wakelocks without having to root your device. I'll try to lay down everything here under a few categories.
First of all, I'll say that I tried using my S8 with a package disabler with hundreds of apps and services disabled, and also tried using it with no package disabler at all. I did not see a significant difference. It's too hard to determine if there is one, but I have to note that disabling TOO MUCH can actually hurt your battery usage.
Finally, I settled on using the device with a disabler again, only this time I disabled things strategically after some investigation with battery stats measurement and wakelock detection.
The apps I used were:
BK Package Disabler + BK Plugin
Better Battery Stats or GSam
These are paid apps, but I am happy with what they can do. BK can be replaced with another disabler (as long as it gives you control over individual package services) and BBS can be replaced with GSam Battery Stats, which is free.
General tips on using these apps:
BBS will require your device to have USB debugging enabled, so that you can connect the phone to your PC and unlock the permission manually. You need an ADB command prompt to do that, and you need to give it the following permission with the following command (read more here).
Code:
adb -d shell pm grant com.gsamlabs.bbm android.permission.BATTERY_STATS
You can use BBS if you do not restart your phone while testing. If you do, it will wipe stats and likely not activate for another few hours, or until you charge again.
You should be using BBS to observe Deep Sleep percentage in the Summary tab (which should be above 95% when the phone is left in idle mode for hours), and Partial Wakelocks to find individual wakelocks that come from apps. Kernel wakelocks are hardly ever something you can do anything about and shouldn't be observed too much, no point in that unless you are rooted. The highest kernel wakelocks should be the ones related to your screen-on time - they are easy to point out as their awake time equals your screen on time.
BK Package disabler, or any other disabler for that matter, WILL require admin privileges to work on your device, so keep that in mind.
BK Package disabler should be used in tandem with BBS, only once you have found wakelocks and/or managed to understand which service is the actual cause. I will give examples below.
---
So, let's start.
Google Play Services battery drain
This one really sucks and it seems to plague any Android device at some point. Most often than not, this problem will occur after you do a system update without doing a factory reset. Last time it occurred on my S8 was right after I did the AQI7 update, after having very good idle drain previous to updating.
What to do in this case?
Log out of your Google account(s).
Enroll for Google Play Services BETA. To enroll, scroll down on this page and find the beta button OR Find Play services in your App list, and do "Uninstall updates", then update it right after that.
Turn off your phone and then boot it in recovery mode (Hold volume up + bixby key, then also hold power button) and select Wipe Cache - This will erase Dalvik cache.
Reboot the phone and delete system cache from the Storage settings
Log back into your Google account(s).
Charge your device and then observe idle drain overnight, or over a few hours.
If this process does not help your problem at all, you might have to do a factory reset to cure the services issue, or the problem might be related to something else, like a google service from some particular app. Use BBS to investigate wakelocks as you check your idle drain.
If this process helps you, but you see the issue again in future without changing anything, try going to the Developer Settings, look for active processes, and find Google Play services. Open them and then hit 'STOP' for each of their sub-services. Don't worry, they will restart on their own. After doing this, you might reboot your phone as well. Last time this little chore helped me out and the drain went away.
---
General Wakelocks
It's normal to get wakelocks even on a perfect system, but BBS will show exact percentages on each of them. Normal wakelocks usually show 0-1% of awake time for a session. If you start seeing numbers like 3%, 7% , 9%, or more, on some specific wakelock, then there is definitely a problem.
Wakelock battery drain will usually appear in your Android System/OS drain stats, so it's impossible to determine without an app.
The most common wakelocks for me are:
- *net_scheduler* wakelock - this one can be related to your WiFi connection. In order to fix it you should have access to the router's settings, and that is not always possible. If you do have access, you can try changing the Wi-Fi channel (choose channel based on Channel Width, for example 40Hz width on 2.4GHz network could use channel 11), and Beacon Interval (set the interval to the highest possible). I found this helped in my case. This wakelock can also be related to google play services - check the previous part of the post on how to possibly resolve the GPS issue. Also, the wakelock can appear under the icons of other apps, when there is little you can do to track down exactly why it happens.
- *com.google.android.gms.measurement* wakelock - this is a VERY common one in my case, and BBS usually shows it comes from Google Services, but always has a specific app icon next to it. In order to resolve this wakelock I had to do the following:
Open my package disabler and go through each app that might be using background data, or the app that is shown next to that wakelock, and then open their lists of individual services. I searched for:
1. AppMeasurementService
2. AppMeasurementJobService
3. Firebase... any service starting with Firebase in its name
These services are related to apps collecting some usage statistics on how you use them and sending them back somewhere, probably the app vendors. You do not need them for any app to be functional, and many apps don't have them. For some reason they can keep your device awake for long periods of time. I disabled them on ALL apps I could find them in and it seemed to resolve a lot of wakelocks after investigating the next following days. This process was probably one of the things that helped me the most with hunting down daily wakelocks as the drain is very stable for me now. For example, today I came back from work with 20 hours of phone usage since charge, almost 1h of SoT and 75% battery left. Other days, I have come back from home with 10 hours of usage, 1.5h of SoT and ~60%. I've seen a lot of improvement lately after doing all of the suggested things and keeping Google services at bay in parallel to that.
---
Bluetooth wakelock
This one was the most inexplicable to me. I never use Bluetooth, or turn it ON for any reason at all. I could not understand why the wakelock occurs.
Ultimately, my solution was to completely disable the Bluetooth System package and all services in it through the BK disabler.
I know this solution doesn't sound good to anyone, but at the same time it might be useful if you also do not use BT at all.
I plan to buy BT headphones in the near future and will be re-enabling this, and at that point I will start observing the behavior of the package once again and maybe turn it on/off at will if the wakelock re-appears too often.
---
Other wakelocks
The general rule here still applies. First, you record your usage with BBS. Then you note down which wakelocks appear on top, and google them as best as you can. Search is your friend here, as the wakelocks are endless and it is impossible for me to list them all and give solutions for even a small percentage of them. Sometimes you might get lucky and find an easy fix. In other times, there will be no easy explanation, or no explanation at all. Such is the nature of Android.
In some cases the wakelocks might be specific services that you can disable for specific apps. In other cases, they will be too general and it will be unclear why they occur. For example, I sometimes get *net_scheduler* wakelock with the Viber app, that can last for 20-30 minutes at random times, and still have not found a way to resolve that, other than uninstalling Viber completely (which is not a bad idea but sadly some of my contacts insist on using that crap. Telegram is your friend).
---
General Tips:
Use an AMOLED black theme. System theme from Samsung Themes (!) and individual app themes / status bar from Substratum. Do not use overlays for the system UNLESS you do not use samsung themes. I found out that Samsung themes do a better job at painting all system apps black, while some substratum overlays miss a few things. It will also be a LOT less painful to update overlays as you uninstall all of them and re-install them, because using Samsung for the system means less packages from Substratum to be installed. REMEMBER to always uninstall system overlays and statusbar overlays (ALL overlays if you want to be super safe) before doing a system update! Otherwise you can soft-brick your device.
Use auto-brightness and make sure to make it as low as you are comfortable with in rooms that you stay often in (like your own room, your office room, etc). Smart auto-brightness will remember you preference and you will hardly ever use more brightness than you need.
Turn off notifications for any apps that are not essential to you. In fact, I have turned off everything except Gmail, because I have a habit of checking my phone very often and do not miss out on anything, while notifications have become a bit annoying to me anyway.
Put almost all of your apps to 'Always Sleeping' in the device optimization app.
Do NOT always sleep apps that you need to be awake, like your Messaging app, Home Launcher, utility stuff like Navbar Apps, Keyboard. Put those in the 'Unmonitored' category instead.
DE-OPTIMIZE your fingerprint scanner from battery optimization settings if you are having issues with waking up the device with it. It is optimized by default if I remember correctly.
If you are feeling BRAVE, you can do your own investigation for each app that you use often to look for any services that might look like Analytics services. Experiment at your own risk, but generally such services are always a benefit to turn OFF for both battery and privacy reasons.
---
Overall, that's it. If I remember something, I will update the thread. Hopefully this can help someone.
In my personal results, I've managed to achieve a 0.3% idle drain per hour with Wi-Fi active during a test of 12 hours of standby. As visible in the screenshot, the Wi-Fi signal is not even perfect.
Here is an example of idle drain with about 1h 10m of SoT at the time it was taken.
---
Feel free to use this guide in conjunction with Neomancr's general battery and performance tuning guide
Thanks!
magarto said:
Thanks!
Click to expand...
Click to collapse
No problem!
This should be on top! Thanks a lot!
The "Service Disabler" functionality has been removed from the latest app version due to Google Play policies.
Fortunately we can find the previous apk version in the developers website.
https://kunkunsoft.wordpress.com/news_2/
Cheers!
hey thanks a ton for this article! My battery is horrible...REALLY. 2 h ost...I've just completed the first part. please explaind better what do you mean with "sign out from Google accounts" step by step. and in my case BBS was not adb enabled...I was not able to see wakelocks. the command explained here https://alexus.org/howto/better-battery-stats-no-root/amp (the google play store version) granted permissions for me. maybe you want to update the guide! I'll let you know how it goes.
cheers
@brokich
Could you please point us exactly to what are the main apps with AppMeasurement and Firebase services?
Until now I have found only the Google play store app.
Thanks for your great guide.
Thanks for the guide. Starting to debug battery issues. Meanwhile tried setting up the black theme. What do you mean by installing only Samsung theme? Do you mean a specific theme made by Samsung electronics or any black theme from Samsung theme market?
Here are the correct adb commands to BBS, as shown in the app in first start:
adb -d shell pm grant com.asksven.betterbatterystats android.permission.BATTERY_STATS
adb -d shell pm grant com.asksven.betterbatterystats android.permission.DUMP
adb -d shell pm grant com.asksven.betterbatterystats android.permission.PACKAGE_USAGE_STATS
There's a lot of threads out there regarding battery saving techniques, but I didn't really see anything that went into a lot of detail on the OP3t. I own both an OP3t and an OP5T, and after running into some issues with the battery I have finally gotten my phone to idle fairly well on the devices and figured I would share my techniques.
Anyone that reads this and finds this useful, I encourage you to let me know the outcome of your battery after following this guide. Also if you have any suggestions/recommendations, please share them with me on here. I can update the original post and include your suggestions so that it can be helpful for other users as well.
The wakelocks category can be pretty intimiating because it's different for all users based on applications they have, but if you have some custom regex wakelocks or just standard wakelocks that you would like to share, please let me know.
Now to the guide...
Phone Specs:
OnePlus 3T - 64Gb
OxygenOS 5.0.3 (stock) & rooted with Magisk
Kernel - Bane Kernel https://forum.xda-developers.com/on...e-development/kernel-bane-kernel-r-1-t3801778
Recovery - https://androidfilehost.com/?fid=890129502657595792
Developer Options:
Developer - On
OEM Unlocking - Enabled
Advanced Reboot - Enabled
* Doze mode * - Disabled
-I need to highlight this, because I usually enable this option, and I know many others do as well. I'm not sure if my situation is an anomaly, however I must highlight if you use 3rd party battery saving apps such as naptime, forcedoze, leandroid, you should disable this mode. If you don't use these apps, then you should be okay to enable the option. I had this option enabled initially while using the 3rd party apps, and they were conflicting with my phone and my battery was draining very rapidly. It wasn't until after I disabled this option that I noticed a significant improvement with the battery.
USB Debugging - Enabled
Verify apps over USB - Enabled
Tools I use:
Amplify - https://forum.xda-developers.com/xposed/modules/mod-nlpunbounce-reduce-nlp-wakelocks-t2853874
Better Battery Stats - https://forum.xda-developers.com/showthread.php?t=1179809
ForceDoze - https://forum.xda-developers.com/android/apps-games/app-forcedoze-force-doze-mode-screen-t3377694
LeanDroid - https://forum.xda-developers.com/showthread.php?t=2743316
Magisk v16.0\5.8.3 - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Nova Launcher - https://forum.xda-developers.com/showthread.php?t=1389071
Xposed Framework v90 beta3 - https://dl-xda.xposed.info/framework/sdk26/arm64/xposed-v90-sdk26-arm64-beta3.zip
OOS Debloater v5 - https://forum.xda-developers.com/on...hemes-apps--mods/aroma-oos-debloater-t3615828
Amplify Settings:
WakeLocks:
Wakelocks(Allow every 900 seconds)
WakefulIntentService[GCoreUlr-LocationReportingService]
NetworkStats
Wakelocks(Allow every 3600 seconds)
WeatherUpdateService
Wakelocks(Allow every 10800 seconds)
SyncLoopWakeLock(delays sync)
*net_scheduler*
GCoreFlp
Icing
Wakeful StateMachine: GeofencerStateMachine
NfcService:mRoutingWakeLock
wake:com.pushbullet.android/.gcm.GcmService
SyncService(Package: Push Bullet)
ai(Package: Push Bullet)
ae(Package: Push Bullet)
AsyncService
Wakelocks(Allow every 41400 seconds)
NlpWakeLock
NlpCollectorWakeLock
LocationManagerService
Config Service Fetch
Wakelock regex:
*gms* 900 seconds
*facebook* 9999999 seconds (if you use facebook)
Alarms:
Alarms(Allow every 600 seconds)
com.android.internal.telephony.data-stall
Alarms(Allow every 1800 seconds)
com.oasisfeng.greenify.CLEAN_NOW (If you use greenify)
Alarms(Allow every 3600 seconds)
android.appwidget.action.APPWIDGET_UPDATE
Alarms(Allow every 7200 seconds)
android.content.syncmanager.SYNC_ALARM(delays sync
Alarms(Allow every 10800 seconds)
android.net.ConnectivityService.action.PKT_CNT_SAM PLE_INTERVAL_ELAPSED
com.facebook.common.executors.WakingExecutorServic e.ACTION.ALARM.com.facebook.katana
com.google.android.apps.hangouts.CLEANUP_DB
com.pushbullet.android/.gcm.GcmFixReceiver
com.android.server.action.NETWORK_STATS_POLL
com.diune.pictures.intent.action.MEDIA_CHECK
LocationManagerService
Alarms[LOCATION](Allow every 41400 seconds)
ALARM_WAKEUP_LOCATOR(com.google.android.gms.nlp.AL ARM_WAKEUP_LOCATOR)
ALARM_WAKEUP_CACHE_UPDATER
ALARM_WAKEUP_BURST_COLLECTOR(com.google.android.gm s.nlp.ALARM_WAKEUP_BURST_COLLECTOR)
com.google.android.gms.location.fused.GPS_ALARM_BA LANCED_ACCURACY
ALARM_WAKEUP_ACTIVE_COLLECTOR
ALARM_WAKEUP_PASSIVE_COLLECTOR
ALARM_WAKEUP_BURST_COLLECTION_TRIGGER
com.google.android.intent.action.SEND_IDLE
ALARM_WAKEUP_ACTIVITY_DETECTION
com.google.android.location.reporting.ACTION_UPDATE_WORLD
Alarms(Allow every 93600 seconds)
android.app.backup.intent.RUN
com.google.android.gms/.checkin.EventLogService$Receiver
com.google.android.gms/.checkinCheckinService%Receiver
Alarms regex:
ALARM_WAKEUP[0-9]+ 9999999 seconds
ForceDoze
These are the options I have checked in Forcedoze settings. Everything else is unchecked.
Turn off while charging - checked
Show persistent notification - checked
Ignore lockscreen timeout - checked
Disable motion sensing for Doze - checked
LeanDroid
DisableWi-Fi - checked
Cellular data - checked
Cellular Radio - unchecked
Bluetooth - checked
Network location - checked
GPS location - checked
SwitchCellular network mode to 2G - unchecked
5 min after screen off except (click except to add exceptions)
The only options I have checked under the exceptions are the following:
Except if tethering - checked
except if charging (AC) - checked
except if charging (USB/wireless) - checked
Disable (Under Exceptions settings)The only options I have checked are
Under (wi-fi, data, network mode)
Except if active: limit 3KB/s - checked
Under Bluetooth
Except if connected - checked
Under Location
Except if GPS in use - checked
Now back to the Leandroid home screen the following settings under "Restore"
I have selected "After screen unlocked"
Every 60 min for 60 seconds after screen off - checked
except 11PM - 6AM - checked
Except below 15% - checked
Magisk
The only module I use in Magisk is "Sysconfig Patcher" - This is supposed to help with optimizing battery for the google services (that are normally exempt from battery optimizations)
Xposed
The modules I have enabled are:
Amplify
ForceDoze
No Device Check (this is a xposed module you can download from the app that helps make SafetyNet check pass)
Now in Android Settings --> Data usage
Click on the cellular data usage as well as the wifi data usage, you can click on an app that shows up in that list that uses up a lot of data and when you click on it, there is an option to toggle off the option "Background data"
I'm not sure if this is really needed, but what I did is I went through the apps that used the most data (including google play store and google play services) and I toggled the background data off
Android Settings --> Battery
Click "Battery Optimization" --> click the ellipses (top right corner) --> Advanced optimization --> turn this on
Android Settings --> Apps --> Special Access --> Usage Access
Turned off for google play store and google play services
Android Settings --> Apps --> Special Access --> Unrestricted data access
All apps are turned off
These are all my custom settings. If you would like to share any, let me know!
Probably you didn't search enough.
There are many helpful topics here or at Oneplus forum for Amplify, Betterbatterystats or with guides for increased battery.
Sent from my ONEPLUS A3003 using Tapatalk
RASTAVIPER said:
Probably you didn't search enough.
There are many helpful topics here or at Oneplus forum for Amplify, Betterbatterystats or with guides for increased battery.
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
There are several very useful posts each individually spread around these forums; the purpose of this thread is to have a unified source so people don't have to look all over like I did. I know you initially posted on my thread when I had terrible battery drain issues; and after I posted the information you requested, I haven't heard anything from anyone so I had to troubleshoot and fix it on my own. I guess what I'm saying is, I just want to help others in case they run into a similar situation because it can be frustrating when you're seeking guidance or help and no one responds.
I use Naptime and also had enabled the Doze mode in the settings, so like you say i disabled doze mode now and kept naptime running , ill update this post with my findings
manohar3787 said:
I use Naptime and also had enabled the Doze mode in the settings, so like you say i disabled doze mode now and kept naptime running , ill update this post with my findings
Click to expand...
Click to collapse
Yeah, keep me posted. I'd be interested to see if your results are similar to mine. Were you also having a lot of battery drain despite using naptime and doze mode?
manohar3787 said:
I use Naptime and also had enabled the Doze mode in the settings, so like you say i disabled doze mode now and kept naptime running , ill update this post with my findings
Click to expand...
Click to collapse
@manohar3787 - curious to hear about your phone after turning off doze. Any updates?
Leandroid app is responsible of a severe wakelock, I think is almost better not to have it? Any opinion?
Also, what about RILJ And RILJ_ACW_WL wakelocks? Are these safe to block?
Sent from my ONEPLUS A3003 using Tapatalk
RILJ was safe to block on nougat and below, but in Oreo+ it will actually cause a lot of trouble with the system. The other wakelock you mentioned "RILJ_ACW_WL", I'm not familiar with. What I woudl recommend is do a full backup in your recovery, then make the change to observe what happens. If it messes things up you can recover from your backup.
Regarding Leandroid, I haven't really heard any concerns with it. There have been some responses of users that didn't find it to help any, but I haven't heard of it having an adverse affect.
Another app I haven't tried, but am tempted to try at some point is called Island: https://play.google.com/store/apps/details?id=com.oasisfeng.island
Also a thread about it here: http://forum.xda-developers.com/android/-t3366295
@xNAPx - how is your SOT and your idle battery like? DO you use any 3rd party apps/tools to help with battery drain?
m0d hipp¥ said:
RILJ was safe to block on nougat and below, but in Oreo+ it will actually cause a lot of trouble with the system. The other wakelock you mentioned "RILJ_ACW_WL", I'm not familiar with. What I woudl recommend is do a full backup in your recovery, then make the change to observe what happens. If it messes things up you can recover from your backup.
Regarding Leandroid, I haven't really heard any concerns with it. There have been some responses of users that didn't find it to help any, but I haven't heard of it having an adverse affect.
Another app I haven't tried, but am tempted to try at some point is called Island: https://play.google.com/store/apps/details?id=com.oasisfeng.island
Also a thread about it here: http://forum.xda-developers.com/android/-t3366295
@xNAPx - how is your SOT and your idle battery like? DO you use any 3rd party apps/tools to help with battery drain?
Click to expand...
Click to collapse
My SoT is dependent on the usage, night drain is less than 1% a hour even 0% sometimes, SoT is between 7 and 5 h
About those wakelock I've heard the same about RILJ on Oreo, about the other one I don't know but is heavy as well.
About Leandroid I'm not very convinced. It messes up with notification and now I have another big wakelock to worry about
Sent from my ONEPLUS A3003 using Tapatalk
Unable to End Google play services
i am unable to doze google play services since am already running doze mode+magisk modules(sysconfig patcher + enable doze moe for gms )
Still i can see play services in Running services
Kind help needed
@xNAPx - do you have any custom settings or tools you use? Do you use Greenify?
What are the big wakelock issues that you have trouble with? Is it the one you mentioned "RILJ_ACW_WL" or other ones?
@Anusha Rao - Are you using doze mode within the Android system or 3rd party tools like I posted?
I don't think you want to use both magisk modules. As I mentioned in my post, I only use the sysconfig patcher. And make sure you reboot the phone after enabling that.
To check and see if google play services is being optimized for battery try going here:
Settings --> Apps --> Application List--> Google Play Services --> Battery
When I look at mine it shows 0m in use
0% battery usage
Battery Optimization:
Optimizing battery use
EDIT:
I'm posting screenshots of my googple play store and the google play services having battery optimization enabled and using 0% battery.
BTW, just so we're on the same page, you shouldn't completely "stop" google play services because it's essentially what drives the OS. Those services are important for letting your phone operate correctly. My thread is about optimizing those services not disabling/stopping them.
If you want to completely "freeze" certain apps and services you can try out that application I posted in my previous post called "Island". I'd be curious to hear how it works out.
That one plus "RILJ" plus "LEANDROID service" (which I un installed) , and also "AudioMix" and "xalarmx"
Sent from my ONEPLUS A3003 using Tapatalk
Amplify tells me I need to root my device but I have Magisk installed...?
I'm not familiar with the rom that you have "Dirty Unicorns". I use the stock ROM.
Most custom roms have root built in though so you might not even need to use magisk or super SU. You can check to see if there are any custom rom settings o maybe go into developer settings and see if you see a "Root" option.
Face unlock is not supported in the "Bane Kernel".
Does Lean Droid caused more battery Drain?
m0d hipp¥ said:
@Anusha Rao - Are you using doze mode within the Android system or 3rd party tools like I posted?
I don't think you want to use both magisk modules. As I mentioned in my post, I only use the sysconfig patcher. And make sure you reboot the phone after enabling that.
To check and see if google play services is being optimized for battery try going here:
Settings --> Apps --> Application List--> Google Play Services --> Battery
When I look at mine it shows 0m in use
0% battery usage
Battery Optimization:
Optimizing battery use
EDIT:
I'm posting screenshots of my googple play store and the google play services having battery optimization enabled and using 0% battery.
BTW, just so we're on the same page, you shouldn't completely "stop" google play services because it's essentially what drives the OS. Those services are important for letting your phone operate correctly. My thread is about optimizing those services not disabling/stopping them.
If you want to completely "freeze" certain apps and services you can try out that application I posted in my previous post called "Island". I'd be curious to hear how it works out.
Click to expand...
Click to collapse
Disable background data in Play Store and Play service will not disabling them right?
@Bintang Ksatria - Leandroid should be using less battery. @Rvl7 - No it won't disable them. I still use them, but it's on manual load, and not in the back ground. At least that has been my experience.
m0d hipp¥ said:
@Bintang Ksatria - Leandroid should be using less battery. @Rvl7 - No it won't disable them. I still use them, but it's on manual load, and not in the back ground. At least that has been my experience.
Click to expand...
Click to collapse
A good post , it helps us a lot .
Hi there,
Since the official update to android 10 the GPS of my Oneplus 6T is not working anymore.
Whichever app I use (Google maps, Uber, citymapper...) the location won't update itself. It seems like the app won't ask the system for the location ?
I've tried clearing the cache of various location related system app, rebooting. I even tried an app mocking the location but even this won't update the position in Google maps...
I've seen a couple of thread of people with the same issue but all they recommend is factory resetting the phone which I don't really want to do.
Has anyone managed to solve this ?
I had this for a while. Nothing will fix it. Have to wipe completely then update to android 10, root, etc. will fix
Auwhel said:
Since the official update to android 10 the GPS of my Oneplus 6T is not working anymore.(...)
Click to expand...
Click to collapse
Same here!
I think it's a good idea to have a dedicated thread for this as it doesn't seem to affect everyone but let's document this a bit more effectively. I've taken the liberty of grabbing a log here and by swiftly browsing through the file, I found this one particularly interesting:
Code:
01-07 12:00:57.917 3951 3951 I LocationEnabler: Location mode has been changed
This 'LocationEnabler' only occurs twice in the entire log, two milliseconds apart. Before this line 'WifiService' is throwing massive amounts of errors and just 407ms before the 'LocationEnabler' line above, this one drops:
Code:
01-07 12:00:57.510 1135 2912 I WifiService: acquireWifiLock uid=10042 lockMode=2
After that, only 6 of the following 35 'WifiService' instances are errors. I think that could indicate the GPS issue is related to the accompanying Wifi lock. I tried turning off Wifi scanning (and rebooting, naturally) but that didn't seem to change anything. Perhaps I should grab another log now.
My actions during this log:
Launch Google Maps
Notice it doesn't get a fix on my location (while in the past this used to happen instantly)
Tap hamburger menu top left, then Settings
Tap 'Google location settings'
Leave that sitting there for a few seconds
Return to Google Maps and GPS is now "fixed" (for a short while)
This is a workaround I've read in the stable discussion thread but is of course no solution.
Tagging @Funk Wizard as he's probably the only one I know that can do something with this log (or at least take it to the right people). I hope this helps!
Did someone try to factory reset using msmtool (version 10)? I m on android 10 and i have no problem
chibi said:
Did someone try to factory reset using msmtool (version 10)? I m on android 10 and i have no problem
Click to expand...
Click to collapse
Flashing clean is very likely a valid solution to this problem but I'd like to get to the root of this issue so OP doesn't need to make the same mistake twice. Or at least have no excuse for it next time
Apart from that I have a very smooth system now with excellent battery performance (maybe because GPS is failing, lol) so if I could solve the only problem I have without any data loss, that would be awesome.
And this is XDA developers. We just need to know, right?
Just a reminder make sure and have location setting to have access all the time..
Just going out of that app temporarily to do something else real quiçk could possibly stop the connection. Could help possibly... I myself have no issues.. I will add more to this as we get further into the Android 10 madness. Lol...
@TENlll423 Android 10 madness, say that again! I have indeed set this setting to 'allow all the time' but even if it were set to 'allow only while using the app', it should at least get a fix on the location when Maps is running.
I've now made a second log with Wi-Fi scanning turned off, see full log here. Notable events:
11:22:00 - opened Google location settings (which activates GPS somehow)
11:22:10 - closed them (back to Maps)
11:23:26 - Signal lost (location dot turns from blue to grey)
Speaking of permissions, we might be on the right track when we see a line like this:
Code:
01-08 11:23:17.690 2851 3241 I LocationAccessPolicy: com.google.android.gms is aware of fine but the app-ops permission is specifically denied.
Even with wifi scanning turned off, the 'WifiService:' pattern remains exactly the same. So I assume this relates to 'Google Location Accuracy', rather than 'Wi-Fi and Bluetooth scanning'. Just before the signal is lost again, this appears:
Code:
01-08 11:23:21.254 1132 4140 E WifiService: Permission violation - getScanResults not allowed for uid=10042, packageName=com.google.android.gms, reason=java.lang.SecurityException: UID 10042 has no location permission
Whatever I try to toggle on or off (ELS, scanning, accuracy...), the result stays the same: after about 1.5 minutes the signal is lost again.
We could really use your help here, @Funk Wizard
I could see somebody building a module in the near future to fix this ridiculous issue... Or we can at least hope.... Wish I had the know how to do something like that.....
I have the exact same issues. Annoying..
I think I managed to find a workaround which doesn't involve a factory reset:
Settings -> System -> Reset options -> Reset app preferences (this doesn't affect apps data)
Settings -> Apps & notifications -> See all XXX apps -> (3 dots in the upper right corner) -> Show system -> Clear storage and cache of the following apps:
Google Maps
Google Play services
Google Services Framework
LocationServices
Phone Services
Fused Location
Google Location History
OPMmsLocation
I wiped Dalvik cache in TWRP.
I'm not sure all steps are necessary but resetting apps preferences is the key one I think. It's going to reset the permissions of all apps but it's a good alternative to reinstall everything from scratch. The issue of the GPS fix in Google Maps hasn't come back for me since.
ptisam said:
I think I managed to find a workaround which doesn't involve a factory reset:
Settings -> System -> Reset options -> Reset app preferences (this doesn't affect apps data)
Settings -> Apps & notifications -> See all XXX apps -> (3 dots in the upper right corner) -> Show system -> Clear storage and cache of the following apps:
Google Maps
Google Play services
Google Services Framework
LocationServices
Phone Services
Fused Location
Google Location History
OPMmsLocation
I wiped Dalvik cache in TWRP.
I'm not sure all steps are necessary but resetting apps preferences is the key one I think. It's going to reset the permissions of all apps but it's a good alternative to reinstall everything from scratch. The issue of the GPS fix in Google Maps hasn't come back for me since.
Click to expand...
Click to collapse
I had this issue and tried this fix. Now my apps are working again. ( I cleared the storage of all mentioned apps).
But after that i had the df dferh 01 playstore bug. After solving that ( some youtube tutorial) everything is OK.
Thanks,
Followed all the steps, seems to be working fine now.
Maybe it's just my imagination, but the device seems more responsive as well..
ptisam said:
I think I managed to find a workaround which doesn't involve a factory reset(...)
Click to expand...
Click to collapse
I think so too! Working fine on my end as well.
Maoden said:
Thanks,
Followed all the steps, seems to be working fine now.
Maybe it's just my imagination, but the device seems more responsive as well..
Click to expand...
Click to collapse
Since all your apps' settings have been reset, that is plausible. And if it's not the case, we can at least enjoy the placebo effect ^_^