Develop Bugs

T989 Nexus Rom battery drainage issue plus more

so I flashed the Nexus Rom as well as the newly updated 3.8 version with the battery % feature flashed on my phone. The entire procedure was done as instructed (restore/clear 3+ times on everything as instructed) and I waited well over 10 minutes upon a reboot. So all is set and almost everything is working flawlessly.
There are few issues, however, which I'm curious to know if I'm the only one experiencing this:
1. Battery Drain: Fully Charged at 100%, unplugged the cable at 6AM this morning. The phone has been on its battery power for roughly 7.5 hours now handling a total of 5 minutes of calls, roughly 30 text messages, 5 minutes of non-wifi internet usage, email is being pushed, and flashed 3.8. My display is set slightly below the mid section and I have zero widgets on my main screen except for the search bar. A total of 6 icons on my menu and that's it (only 1 page). My battery is at 40% right now. It's only been a day since I've had this flash and I just flashed on the 3.8 just few minutes ago.
2. From the Status Bar pull down menu, Shutdown and Reboot, Recovery option would hang and freeze the phone until I pull out the battery. I can only enter the Recovery mode manually by holding both +/- volume, power on, and releasing both once the 'samsung' logo appears.
3. Mobile HotSpot freezes for good 1-2 minutes. I cannot use my phone as a Hotspot at the moment.
I absolutely love the Nexus Rom from the looks, performance, looks to looks, but few of the glitches I've mentioned are quite irritating. If I'm the only person experiencing this, I'd want to continue on the search to remedy this issue. Please share some experience, ideas, or resolution if you have any!

1.) That's about right for battery. It's a leak so the battery life is still wanting compared to gb. If you thinks that's bad though, you should have seen uclc4
2.) Known bug. Even though its ucld2 the shutdown bug is still present for a few, and especially manifests itself as soon as you run fix permissions. Although the shutdown hang is "reportedly fixed" on ucld2 i'm running seanscreamz sky ics 4.2D-8 with ucld2 base and i have the same problem as well.
Suggestions, either use quickboot from google play, or reflash following op instructions and DO NOT fix permissions
3.) Hotspot doesn't really work all that well, even with the ultracfg fix. I recommend the "WiFi Tether 3.1-beta12" app, i'm using this instead and it works well.

icenight89 said:
1.) That's about right for battery. It's a leak so the battery life is still wanting compared to gb. If you thinks that's bad though, you should have seen uclc4
2.) Known bug. Even though its ucld2 the shutdown bug is still present for a few, and especially manifests itself as soon as you run fix permissions. Although the shutdown hang is "reportedly fixed" on ucld2 i'm running seanscreamz sky ics 4.2D-8 with ucld2 base and i have the same problem as well.
Suggestions, either use quickboot from google play, or reflash following op instructions and DO NOT fix permissions
3.) Hotspot doesn't really work all that well, even with the ultracfg fix. I recommend the "WiFi Tether 3.1-beta12" app, i'm using this instead and it works well.
Click to expand...
Click to collapse
Thanks for the input. I wish the battery life was better. I'll let it sink in for a few days to see if it'll improve. If not, I'll just have to keep searching for a rom with a better battery life. I've tried Beastmod, Juggnaut and many others which have yet to last for over 12 hours.
I read that the hotspot issue was fixed and with the 3.8 update, I presumed it to be completely polished. The shutdown bug, I can live with - hoping there's an upcoming fix in the works.
This ROM is the sickest looking ROM I've tried so far. I wouldn't call it the smoothest due to it's intermittent force closures and freezes, but when things improve down the road, I think this one will stay on my phone for awhile!

I've been using this rom for about a week and the battery has been working great, better than any stock rom I've had. I'll unplug it in the morning around 745 and it'll last until I go to bed around 11.
Sent from my SAMSUNG-SGH-T989 using xda premium

You should try Mr X' s tweaked Telus stock ROM. This ROM has the best battery life among T989 ROMs period. It is Canadian but works great on T-mobile network. It also does not have much bloatwares as T mobiles stock one. Just Make sure you have wifi sharing, wifi sharing manager and social hub frozen through titanium backup.
As for wireless hotspot, the stock one from Telus works well.
I get about 16 hours use. It may vary for you but battery lasts longest with this ROM.
Sent from my SGH-T989D using XDA

[Q] S3 - Cyanogenmod 10.1.3-RC2-d2att - Using Google Maps causes major battery drain

I noticed lately that my battery has been draining quite a bit when using Google Maps for navigation. It's gotten to the point where 30 mins of continuous use for navigation has completely drained my battery. Now this has happened at least 5 times in the last few weeks now and it has rendered my phone completely useless for Navigation. I did have the Cyanogenmod 10.1.2 ROM installed but recently installed 10.1.3-RC2-d2att and the problem still seems to persist.
I've ready many posts talking about turning off GPS, Location Services etc. but I can't obviously turn off GPS when I need to use my phone for navigation. I also noticed that using a car charger didn't do much as the battery was draining much much faster then the battery was charging. Also , the phone seems to very very hot.

Same hear. I just moved from Rogers's stock image. Battery life on 10.1.3-RC2-d2att is terrible comparing to stock image.
theproman23 said:
I noticed lately that my battery has been draining quite a bit when using Google Maps for navigation. It's gotten to the point where 30 mins of continuous use for navigation has completely drained my battery. Now this has happened at least 5 times in the last few weeks now and it has rendered my phone completely useless for Navigation. I did have the Cyanogenmod 10.1.2 ROM installed but recently installed 10.1.3-RC2-d2att and the problem still seems to persist.
I've ready many posts talking about turning off GPS, Location Services etc. but I can't obviously turn off GPS when I need to use my phone for navigation. I also noticed that using a car charger didn't do much as the battery was draining much much faster then the battery was charging. Also , the phone seems to very very hot.
Click to expand...
Click to collapse

theproman23 said:
I noticed lately that my battery has been draining quite a bit when using Google Maps for navigation. It's gotten to the point where 30 mins of continuous use for navigation has completely drained my battery. Now this has happened at least 5 times in the last few weeks now and it has rendered my phone completely useless for Navigation. I did have the Cyanogenmod 10.1.2 ROM installed but recently installed 10.1.3-RC2-d2att and the problem still seems to persist.
I've ready many posts talking about turning off GPS, Location Services etc. but I can't obviously turn off GPS when I need to use my phone for navigation. I also noticed that using a car charger didn't do much as the battery was draining much much faster then the battery was charging. Also , the phone seems to very very hot.
Click to expand...
Click to collapse
go back to CM 10.1.2 Aka 4.2.2 plus you do know that you expect bugs and all kind of issues with nightlies, am not a fan of nightlies that for sure I PREFER STABLE AND NOT HAVING TO UPDATE OR FLASH A NEW ROM OR UPDATE EVERY SINGLE DAY........I HAVE TO MUCH IMPORTANT THINGS TO KEEP DELETING AND RESTORING AND I GOT BETTER THINGS THAN PLAY WITH ROMS ALL DAY
anywz try AOKP, CARBON OR PARANOID even Slim beam 4.3 nightlies and maybe you will get your problems fixed if it doesnt work it doesnt hurt or kill to go back to stock Touchwiz iknow yu can hate me forever but thats the last thing i wanna do before i give up it always fixes all the problems i get with custom roms

What you may lose when migrating to non stock ROM

This is the list of problems i faced when tried cm-based/stock-based roms
all CM-based, CM itself (10.2+):
1. ear-speaker: you won't hear in skype, viber csipsimple etc.
2. ear-speaker: you won't hear a caller (regular gsm line) if headphones are plugged in.
3. Battery life: each hour consumed about 6%-8% doing only background sync with display turned off. That's very-very bad.
stock-based (V5)
1. Knock-on feature. Sometimes works, sometimes doesn't. You can't rely on it at 100%.
2. GSM signal issue: phone may lose gsm conection during normal usage (crossmark appears near gsm-signal level) My device loses it for about 30sec, several times a day.

Quick memo
Sent from my LG-E988 using xda app-developers app

Had same issue with signal. In the v5 thread someone posted apn to change to and since have not list signal once
Sent from my LG-E980 using xda app-developers app

I haven't had any of the problems you described lol. In fact, just about all 4.4 ROMs I've tried have almost as good of battery life as stock with MIUI (4.2.2) having even better battery life than stock. :3
Sent from my Carbon LG-E980

Neroga said:
I haven't had any of the problems you described lol. In fact, just about all 4.4 ROMs I've tried have almost as good of battery life as stock with MIUI (4.2.2) having even better battery life than stock. :3
Sent from my Carbon LG-E980
Click to expand...
Click to collapse
Lol exactly I don't know what the OP is on.....its probably because he is only using CM 10.2 and not CM11.........I don't know why he would even post since many are not even using CM10 anymore.......CM11 is so much nicer
Sent from my LG-E980 using Tapatalk

Neroga said:
I haven't had any of the problems you described lol. In fact, just about all 4.4 ROMs I've tried have almost as good of battery life as stock with MIUI (4.2.2) having even better battery life than stock. :3
Sent from my Carbon LG-E980
Click to expand...
Click to collapse
I've absolutely had every problem the OP posted including poor GPS tracking as well. Performance on the 4.4 ROMS is greatly improved compared to stock, but I certainly get horrid screen on battery drain and lack of signal quality. I also struggle with obscure wakelocks with 4.4 ROMS, and that includes CM11, Commitio, Vanir, Candy Kat and Beanstalk. I've tried several. Not trying to dispute what you're saying, just confirming that the OP's statements are legit.
Hence the reason I personally keep going back to rooted, de-bloated, stock and using ROM Manager to set my governor. That has given me the best battery life, stability and relatively decent performance.
Logic

Logic717 said:
I've absolutely had every problem the OP posted including poor GPS tracking as well. Performance on the 4.4 ROMS is greatly improved compared to stock, but I certainly get horrid screen on battery drain and lack of signal quality. I also struggle with obscure wakelocks with 4.4 ROMS, and that includes CM11, Commitio, Vanir, Candy Kat and Beanstalk. I've tried several. Not trying to dispute what you're saying, just confirming that the OP's statements are legit.
Hence the reason I personally keep going back to rooted, de-bloated, stock and using ROM Manager to set my governor. That has given me the best battery life, stability and relatively decent performance.
Logic
Click to expand...
Click to collapse
Give Carbon a shot. It's my daily driver now that Oblikas updated it. As for the bad battery, give the OC'd kernel that uppon2 posted here in the general section a shot. Besides OC, the kernel has definitely improved overall performance and battery life on my device since I started using it.
To fix the GPS tracking, flash the EFS backup you should've made on stock when you used freegee. My GPS locks on instantly.
As for the "low signal," stock ROMs display higher signal than what you're actually getting. When you use an AOSP ROM, it shows what you're actually getting. If you pull up the hidden menu and check the dBm, that's your actual signal strength. I get the same dBm on AOSP and stock, yet stock shows full bars and AOSP shows 3 and my speeds are exactly the same.
Sent from my Carbon LG-E980

I've seen some threads on QuickRemote on the apps forum, but have you guys successfully ported QuickRemote onto non-stock ROMs without issues?

The only issue I've had on custom roms is that my mp3s skip and stutter while playing them. I've tried about 4 different roms and they all do it. The only way for me to listen to my music was to go back to stock.

UvarovG said:
This is the list of problems i faced when tried cm-based/stock-based roms
all CM-based, CM itself (10.2+):
1. ear-speaker: you won't hear in skype, viber csipsimple etc.
2. ear-speaker: you won't hear a caller (regular gsm line) if headphones are plugged in.
3. Battery life: each hour consumed about 6%-8% doing only background sync with display turned off. That's very-very bad.
stock-based (V5)
1. Knock-on feature. Sometimes works, sometimes doesn't. You can't rely on it at 100%.
2. GSM signal issue: phone may lose gsm conection during normal usage (crossmark appears near gsm-signal level) My device loses it for about 30sec, several times a day.
Click to expand...
Click to collapse
I get same problem using Google voice voicemail. Is there a fix for ear speaker?
Sent from my ME302KL using Tapatalk

Do yourself a favor OP and get a zero lemon battery and then try the CPU quiet kernel in the general section.....I'm getting 3-4 days on it with medium use......I use titanium backup widgets to freeze apps that have annoying wakelocks and greenify as well.....I'm currently running the Beanstalk 4.4 ROM and it is better than any ROM I have ever used
Sent from my LG-E980 using Tapatalk

To be honest, I recently tried vanir again. Was not disappointed by the speed at first. Then I was, and disappointed by battery drain, connection issues, NFC would stay on, and a lot of other stuff. And yeah, I've gotten quick remote to work flawlessly on vanir. All you have to do is flash it
Sent from my LG-E980 using Tapatalk
---------- Post added at 12:24 PM ---------- Previous post was at 12:23 PM ----------
I just finished switching back to stock. I disabled animation scales to increase speed lol but I'm glad to be back
Sent from my LG-E980 using Tapatalk

rey031 said:
I've seen some threads on QuickRemote on the apps forum, but have you guys successfully ported QuickRemote onto non-stock ROMs without issues?
Click to expand...
Click to collapse
yes this has been ported do a search
---------- Post added at 01:34 AM ---------- Previous post was at 01:29 AM ----------
UvarovG said:
This is the list of problems i faced when tried cm-based/stock-based roms
all CM-based, CM itself (10.2+):
1. ear-speaker: you won't hear in skype, viber csipsimple etc.
2. ear-speaker: you won't hear a caller (regular gsm line) if headphones are plugged in.
3. Battery life: each hour consumed about 6%-8% doing only background sync with display turned off. That's very-very bad.
stock-based (V5)
1. Knock-on feature. Sometimes works, sometimes doesn't. You can't rely on it at 100%.
2. GSM signal issue: phone may lose gsm conection during normal usage (crossmark appears near gsm-signal level) My device loses it for about 30sec, several times a day.
Click to expand...
Click to collapse
most of this issues you have discribe were a result of dirty flashing. people not clearing all data before flashing because they didnt want to reinstall app. battery life on all 4.4.2 rom is almost as good as stock and i have had no issue with hearing people while talking, dont use skype so not sure their. call waiting ringer is only calling issue i had but turning on call waiting vibrate would let me know i had a second call and worked for me.

[Q] Cyanogenmod 11 battery time

Everytime I flash the latest build of cm11 I get no problems at all with the rom, no glitches. It works perfectly for me, except for the battery time.
When I use my phone for simple texting or tweeting or anything of that form, my battery seems to be drained in a short period of time. The battery time in standby is still the same as stock rom.
I am currently using cm11-20140429 for the E975 model
I have tried changing kernels, I am currently using the 4.4.2 cyanokernel from this thread http://forum.xda-developers.com/showthread.php?t=2572380
I have tried turning of Google Now Launcher and i switched back to the stock cm11 trebuchet, but the problem remained.
the problem is not battery-related or charger-related since the battery worked perfectly on stock rom(more than 24 hours of listening to music on standby)
So I was wondering if any of you had the same problem or if there's any solution that you guys have found?

[SETUP] Share your Current Rom Status Honestly?

This is a general discussion thread. You can share your Current setup of Robin, it would be helpful for us to know which ROM can be used as Our daily driver.
_____________________________________________________________
I'm currently using OmniRom's last build with Magisk module cross-breeder lite edition.
It's giving me Quite decent performance and Battery life.
Normally on continuous usage, it lasts almost 5-6 hrs on single charge.
_____________________________________________________________
If anyone getting a better Battery life, don't hesitate to post below.?
Post-Credit: @me ?

Thanks for sharing, I cannot give screenshots for everything here. I might have them but have to dig into the folder of screenshots but for now here is my battery experience over all.
I have used PA, Carbon and Omni extensively. So everything below is not a ROM review but its battery usage over all with them.
P.S. : For all ROMs, I use Greenify and Doze mode (within ROM, if not available then via NapTime).
PA for me has always been close to stock nothing great maybe a bit better. But because of its roaming issue I stopped using it. And switched to carbon.
Carbon is far better than PA and has very little standby/idle drain but it started giving me a weird 20-25% battery cut off issue and device used to shut down randomly anytime below 25% so I switched to Omni.
Omni has fared pretty well for me. Unlike other ROMs I get consistent battery life i.e. 3-4hrs SOT over a period of 10-15hrs. The ROM seems far more stable and there aren't any random battery drains. Omni sometimes behaves a bit erratic when using new camera apps i.e. first few times it would drain battery a lot but later it works fine. Its the device or ROM I don't know.
For Duo video calls it isn't so great after 30-40mins of call the battery is down by 30% maybe. But that is fine I guess the video call is on data too. So Robin isn't so great for that sort of heavy use in general I guess.
Here is my most heavy use day (on all ROMs) for which 10-12hrs is most the device can sustain.
Morning (for the device) starts at about 6:30-7am.
Its day starts with 96-100%; no matter how much juice it has I make sure I unplug anywhere above 95%.
My usage isn't heavy but I use data(3G/4G) 90% of the time,
Location/GPS is ON for about 40-80mins,
Voice calls ~30-90mins in total, (Most are cellular, 5-10mins VoIP calls)
60-90mins podcast/music, Podcasts which I listen are downloaded before but music is streamed via NewPipe ,
Mail, Twitter, Excel, Pocket app, Camera is used in between randomly.
I don't watch much YouTube on the device maybe a couple of 2-3mins clips, I mostly scroll YouTube to add them to watch later for watching on desktop,
SOT ~3hrs
I have to plug the device by 6-7pm with all that usage. Because by that time its about 15%. And for me Robin at 15% means about 10-15mins of use.
For not so heavy use days the device lasts from 7am to 9pm with SOT of ~3-3.5hrs + voice calls of 30-60mins + 40-60mins GPS/location.
Since Android N I haven't touched 4hrs+ SOT over a period of 10-15hrs of usage sadly.
That only happens if I unplug the device and use it continuously for 4-5hrs reading maybe with no waste in idle drain or data or wifi or push notifs etc. But that isn't a case of regular use for me so I will disregard that.
I have recently started using interactive governors like GlassFish and FairPark but can't say they have helped much. Standby/Idle drain is as low as 1-2% over 4-5hrs.
If you are getting 4hrs+ SOT over a longer charge time of 10-12hrs, I am all ears and want to know what different do you do.

I use Omni with Unicornblood kernel and Hawktail profile in Ex Kernel manager. I also use greenify and naptime. I'd say on average I can get between 3 and 4 hours SOT. On the lower end will be days where I'm out and about a lot so I'm on data, lots of idling, random browsing, reddit, messenger, etc. Usually have spotify running in my car through bluetooth. On the higher end will be days where I'm playing on my phone most of the day, with little screen off time, I can probably push over 4 hours on those days.
Today I've been off the charger for 10 1/2 hours, I have 1 1/2 hours of SOT. I spoke on the phone for about 15 minutes, browsed the internet a bit, some instagram, messaging, etc. and I still have 54% left.

I've tried Paranoid Android and LOS.
With PA the battery on my Robin drains like crazy and I noticed some heat problems as well.
As for LOS, it gives me quite decent battery life but had issues with the power button, the phone struggles to wake sometimes.
Should I try Omni then?

Luisalejandroqi said:
I've tried Paranoid Android and LOS.
With PA the battery on my Robin drains like crazy and I noticed some heat problems as well.
As for LOS, it gives me quite decent battery life but had issues with the power button, the phone struggles to wake sometimes.
Should I try Omni then?
Click to expand...
Click to collapse
Sadly there is no perfect ROM every ROM has some issue. The only question is if you can live with that issue.
The only reason for me to stop using PA was it won't work on roaming. But if PA has been stable and battery drain was the only issue try using Greenify and Naptime. The combination of both can drastically bring down your battery drain. And then use some interactive cpu governors aimed for battery life it should bring down drain to as low as 1-2%.
If you are looking for a different better ROM to try then surely try omni, Omni has been great for me so far and has no major issues as such.

/root said:
Sadly there is no perfect ROM every ROM has some issue. The only question is if you can live with that issue.
The only reason for me to stop using PA was it won't work on roaming. But if PA has been stable and battery drain was the only issue try using Greenify and Naptime. The combination of both can drastically bring down your battery drain. And then use some interactive cpu governors aimed for battery life it should bring down drain to as low as 1-2%.
If you are looking for a different better ROM to try then surely try omni, Omni has been great for me so far and has no major issues as such.
Click to expand...
Click to collapse
Omni, however, doesn't have Qualcomm's hotplugging solution, so both big cores are always on all the time and draining battery whenever your screen is on. Gandalf also messed something up with the kernel sources and broke NFC, requiring you to flash a kernel from an Omni weekly from around June-ish or July-ish to restore that functionality.
If you're patient enough, javelinanddart and Sultanxda will soon figure out how to fix the wake-on-plug lag in LineageOS. Hopefully, they'll also start on figuring out the power-button-not-waking-device issue afterwards.
EDIT: oops. Though javelinanddart proooobably found what might be causing the power-button-not-waking-device issue? Haven't had it happen on his LOS 15.1 unofficials yet so...

I am currently using Lineage 14.1-14.1-20180321 and eagerly awaiting the 'official' release of 15.1. I typically do not update to every weekly build. I usually watch the change logs and update only when the new security patches are released. Provided that update is stable (i.e. fast, everything works, no crashes) I will continue on with that build until the next security patch is released. More often than not, there are no issues, as I have found Lineage to be stable and fast.
I am running non-rooted, and I re-locked my bootloader. As a result, Google Pay is working well, without the use of Magisk.
I run Nova Prime launcher, and do not have a vast amount of apps installed:
Music - Google Play Music, Spotify, Amazon Music
Email and Calendar - Outlook, GMail, Google Calendar
Assistant - Google Assistant
Office Suite - Docs, Sheets, Drive, MS One Drive, Word, Excel, Google Keep, One Note
Camera - Stock lineage OS camera, Snapseed (editing)
Messaging - stock AOSP / Lineage OS messaging app
Video - YouTube, Netflix, Hulu (I only use YouTube to be honest... have the other two because of Chromecasting)
Misc - Google Home, Amazon Kindle
I list all those apps to say that given the relative few apps I use, I have all day battery life, for the most part. I am not a heavy user, but I check email multiple times a day, as well send/receive a LOT of MMS/SMS messages throughout the day. I generally only watch video on my phone (YouTube mostly) at home, and I generally cast it to my TV so that the Chromecast does the heavy lifting.
Overall, I have been very happy with Lineage. I finally settled on Lineage after growing disgruntled with AOSPA. The stock ROM (I gave it a good, honest shot at one point) could not cut it because of the lack of stability, heat issues, Bluetooth issues, and no updates.
I have only run into one issue (on a previous build) where by no doing of my own, the screen went blank on a full battery and would not turn on. I though the phone was essentially bricked. Held down power + volume down for 60 seconds (actually had to do this a few different times) and all was resolved. Still do not know why this happened.
Hopefully this helps someone...

@sfbest23
Thank you for replying with so much detail. But a bit of numbers would help in terms of battery life you get from your usage and setup.
Typical phone idle time and SOT. Gives a rough idea of the battery drain in standby.
I am running non-rooted, and I re-locked my bootloader.
Click to expand...
Click to collapse
I am more curious about this. So after flashing LOS you flash back the stock recovery and lock the bootloader? But when you flash back TWRP to install the updated LOS do you lose all your data again or what? Can you tell me the process you follow, I would love to do it but I find backing up and restoring everything for every update is tiresome and a little annoying. Even if one opts to only update for major releases once a month or few months I am not a fan of backup and restore process quite often.

/root said:
@sfbest23
Thank you for replying with so much detail. But a bit of numbers would help in terms of battery life you get from your usage and setup.
Typical phone idle time and SOT. Gives a rough idea of the battery drain in standby.
I am more curious about this. So after flashing LOS you flash back the stock recovery and lock the bootloader? But when you flash back TWRP to install the updated LOS do you lose all your data again or what? Can you tell me the process you follow, I would love to do it but I find backing up and restoring everything for every update is tiresome and a little annoying. Even if one opts to only update for major releases once a month or few months I am not a fan of backup and restore process quite often.
Click to expand...
Click to collapse
I do not have any detailed battery metrics, but I will start tracking this and get back to you.
Regarding your question about re-locking the bootloader... I am still running TWRP, just with a locked bootloader. I did not flash back to the stock recovery. After unlocking the bootloader, installing TWRP and ROM of choice, it is simply a 'fastboot oem lock' command. I cannot remember off hand, but I do believe that the OS was reset when I did that.

My setup. Works very well. I think omni is the best ROM available.

EAT_CHICKEN said:
My setup. Works very well. I think omni is the best ROM available.
Click to expand...
Click to collapse
Same ROM version, same Magisk version but I still get the SafetyNet API Error.

/root said:
Same ROM version, same Magisk version but I still get the SafetyNet API Error.
Click to expand...
Click to collapse
Do you have /system modified? Or xposed installed? Those will cause safetynet to fail.

EAT_CHICKEN said:
Do you have /system modified? Or xposed installed? Those will cause safetynet to fail.
Click to expand...
Click to collapse
Not using xposed.
Does using EXKM for CPU governors constitute to being a /system modification? Then I guess that would be the cause.