Related
Hello All
There is a simple FIX that i can provide you to avoid the Android OS battery drain if you are on GingerBread.
Please use the Latest FUGUMOD Kernel (Version 4 or greater) and your battery drain will vanish. Before flashing the Fugumod Kernel, please make sure that you do READ READ AND READ the thread below:
http://forum.xda-developers.com/showthread.php?t=812836
The latest kernel is build on newest source and has been tested by many users on XDA and none have so far suggested that the BUG has reappeared after testing it for so many hours. May be themakers of the other custome kernels can implement the latest kernel source to see the results.
Thank you!
Thanks for sharing..
Will try it now
Well, i can say the same. I am on fugu 4 bleeding edge since yesterday and the battery drain bug is gone, even on playing games.
Sent from my GT-I9000 using Tapatalk
i can confirm that too.. i have been using fugumod since the 3.8 version and with the 4.0v and bleeding edge the bug is gone for JVH and JVO so far..
Ps. i know its not related to the topic but which rom fo you prefer to use with fugumod 4.0? i am trying to decide between JVH and JVO which are same except their zimage and factory.rfs files..
not for everybody =)
Yesterday, 02:39 PM
Wow. Flashed bleeding edge ultra 1 .5 hours ago. Battery went from 73% to 9! Ha. Not even used It. Think I will stick with stable
Galaxy S - no point in writing rom or kernel constantly changing!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=14331908&postcount=2435
$omator said:
not for everybody =)
http://forum.xda-developers.com/showpost.php?p=14331908&postcount=2435
Click to expand...
Click to collapse
Ok, i am on BE 4 and the battery bug is gone. One more point- if you restore your app+data using titanium , you may see the bug, therefore it is recommended that you restore the app only and perform wipe of whatever rom you are installing. I am running fugumod for 80+ hours and i have not seen the bug at all
I tried Maps, played angry birds, asphalt , ran layers for 2+ hours and the bug did not appreared for me atleast.
thank god youve achived what ive got from first gingerbreak leak =)
I have just flashed SH3.6 and change the kernel to FuguMod
Android OS problem same appear again..
Dunno why
alvissswoo said:
I have just flashed SH3.6 and change the kernel to FuguMod
Android OS problem same appear again..
Dunno why
Click to expand...
Click to collapse
Did you fladh bleeding edge version 4...??? you need to be on be..its a bit complicated to flash if you do not read the instructions properly given in the fugu mod thread
Sent from my GT-I9000 using Tapatalk
zadusimple said:
Did you fladh bleeding edge version 4...??? you need to be on be..its a bit complicated to flash if you do not read the instructions properly given in the fugu mod thread
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Please show this instruction. Or link
Thanks
kalki said:
Please show this instruction. Or link
Thanks
Click to expand...
Click to collapse
Link : (Bleeding Edge)
https://faramir.eriador.org/r/zImage-ultra
A little bit more info:
http://forum.xda-developers.com/showpost.php?p=14367899&postcount=39650
alvissswoo said:
I have just flashed SH3.6 and change the kernel to FuguMod
Android OS problem same appear again..
Dunno why
Click to expand...
Click to collapse
Please install BE 4 or BE Ultra ..
Link : (Bleeding Edge)
https://faramir.eriador.org/r/zImage-ultra
belive thats the flashing process = bat stats reset that you see
best proof is that people still report drain on 4 =)
You love busting people's bubbles don't you $omator? ^_^
rubbish not solution:
>Ficeto_Deodexed_JVH_I9000_ODIN
>[Modem] ZSJPG
>fugu mod ultra and >bleeding edge
runned sacred oddysey for 10m
turned game off
lost 5% over 15 minutes (screen was OFF) again phone is turning screen fast as hell -suspend bug...
(network data off, wifi off, 2G only ON, GPS off, no app in system, no processes running)
Raider0001 said:
rubbish not solution:
>Ficeto_Deodexed_JVH_I9000_ODIN
>[Modem] ZSJPG
>fugu mod ultra and >bleeding edge
runned sacred oddysey for 10m
turned game off
lost 5% over 15 minutes (screen was OFF) again phone is turning screen fast as hell -suspend bug...
(network data off, wifi off, 2G only ON, GPS off, no app in system, no processes running)
Click to expand...
Click to collapse
did u perform the battery calibration?
I had 100% battery after i unplug usb cable
What is the deal with the battery draining? How many of you with battery draining are running on stock Kernel?
I keep reading about it but so far I only read that there is a problem and no one writes when and after which application is used does it happen and which Kernel they are running.
You will no reach far this way, you need to see what is common when the problem is there so you can eliminate assumptions.
wondering if you drainers have somethin like this in logcat every 5 seconds =)
06-02 22:51:35.631 417 417 D FastDormancy: before ======= ENTER DORMANCY =======
06-02 22:51:35.631 417 417 D FastDormancy: [FD] ON default: true
06-02 22:51:35.631 417 417 E FastDormancy: [FD] Dormant flag(false) from key string
06-02 22:51:35.631 417 417 D FastDormancy: Before mDormFlag: false in getCapaDormancy()
06-02 22:51:35.631 417 417 D FastDormancy: After mDormFlag: false in getCapaDormancy()
Click to expand...
Click to collapse
gooodnite
zadusimple said:
Did you fladh bleeding edge version 4...??? you need to be on be..its a bit complicated to flash if you do not read the instructions properly given in the fugu mod thread
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Thanks for ur link and advice..
I have flashed it to BE4 from ur link..
hope everything is fine now =D
I have updated with nightly cm9 for samsung s i900, all day long, and I have time to see some lags:
1. Wi-fi signal is bed and weak
2. restart one or two time by day
3. move slowly than xxjvu
4. After lat update my scree looks green...with nuance. Was missing a color.
I have downgrade to XXJVU, and problems was foxed, for the moment
But when I try to got back to cm9 nightly 19.06.12, the problem appeared again.
The solution was to come back to xxjvu, gone to dark night and after that come back to cm9..very hard problem. I was very afraid.
Have someone sow other problems? Because I want the developer to know all this thins to improve its!
The best!
mishulake said:
1. Wi-fi signal is bed and weak
2. restart one or two time by day
3. move slowly than xxjvu
4. After lat update my scree looks green...with nuance. Was missing a color.
!
Click to expand...
Click to collapse
#1 is something i haven't experienced at all, in fact wifi became faster and better with CM9
#2 happened to me a lot when I ran CM9 with their stock kernel, i use a Semaphore kernel now, and the phone works p much flawlessly. Reboots very rarely while I listen to music (Apollo & Spotify)alltid
#3 is just odd, going from stock 2.3.5 my phone sped up like crazy..
#4 what the hell
Sent from my GT-I9000 using xda premium
Samsung ICS yelow
Hr Kristian said:
#1 is something i haven't experienced at all, in fact wifi became faster and better with CM9
#2 happened to me a lot when I ran CM9 with their stock kernel, i use a Semaphore kernel now, and the phone works p much flawlessly. Reboots very rarely while I listen to music (Apollo & Spotify)alltid
#3 is just odd, going from stock 2.3.5 my phone sped up like crazy..
#4 what the hell
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
I can I do? I cant all ICS that I tried to install made the same, the screen became in yelow shades, darky, and big cotrast, imediately after instaling, with the animation!!!
Any advice will be apreciated!
when you have flashed, have you did all the Wipe ?
Before your flashing, did you a proper base ? (GB 2.3.6 for exmaple ?)
for the color of the lockscreen, i have the same 'problem' but that persist during 1s, so i don't care
mishulake said:
I have updated with nightly cm9 for samsung s i900, all day long, and I have time to see some lags:
1. Wi-fi signal is bed and weak
2. restart one or two time by day
3. move slowly than xxjvu
4. After lat update my scree looks green...with nuance. Was missing a color.
I have downgrade to XXJVU, and problems was foxed, for the moment
But when I try to got back to cm9 nightly 19.06.12, the problem appeared again.
The solution was to come back to xxjvu, gone to dark night and after that come back to cm9..very hard problem. I was very afraid.
Have someone sow other problems? Because I want the developer to know all this thins to improve its!
The best!
Click to expand...
Click to collapse
1. Yeap, I have the same problem with the signal but still I can surf with it in any place at my home + the wifi itself is better (My surfing is smoother and download speed is max)
2. Never happened to me (yet), which kernel are you using? I'm using Semaphore I think it's the best
4. WTF? never heard about this, I didn't update my Rom for two weeks so maybe that's why I don't have this problem, try to go back to 2.3.X Reroot & Semaphore kernel and try again installing that Rom
CM9 color screen problem
mishulake said:
I have updated with nightly cm9 for samsung s i900, all day long, and I have time to see some lags:
1. Wi-fi signal is bed and weak
2. restart one or two time by day
3. move slowly than xxjvu
4. After lat update my scree looks green...with nuance. Was missing a color.
I have downgrade to XXJVU, and problems was foxed, for the moment
But when I try to got back to cm9 nightly 19.06.12, the problem appeared again.
The solution was to come back to xxjvu, gone to dark night and after that come back to cm9..very hard problem. I was very afraid.
Have someone sow other problems? Because I want the developer to know all this thins to improve its!
The best!
Click to expand...
Click to collapse
After first restart, my scree become yellow. I want to put a video but the system cant give access. Right now I'm in cm7, and everything works, fine. No one know what is happen, because I want to install CM9, please!
REefault CM9 samsungs i9000 problems
Can say I have only experienced the restart issue, frequently, sometimes while the phone is sitting idle, and sometimes during calls, while on stock. Currently on July 02 CM9 and to solve the restart/reboot issue, I have been using MNICS kernel, and as of yesterday, the new MACKAY kernel. Hope this helps you with one of your problems. Also use jvu modem.
mishulake said:
Right now I'm in cm7, and everything works, fine. No one know what is happen, because I want to install CM9, please!
Click to expand...
Click to collapse
Stay on CM7 (are you on the latest CM7 build or an old one?) and retry this:
- First please, download the latest available nightly for CM9 link here!
- Then follow the step written by devs:
The thread for CM9 with instructions to flash is here: link !
- Upgrading from CM7?
Do a Nandroid Backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Click to expand...
Click to collapse
Be sure to do all this step and flash the latest nightly.
I already had to update from CM7 to CM9 twice and, each time, I got it working without problem. So please, try again, make sure to follow the steps and tell us if you're experiencing the same troubles again.
GuillaumeVDH said:
Stay on CM7 (are you on the latest CM7 build or an old one?) and retry this:
- First please, download the latest available nightly for CM9 link here!
- Then follow the step written by devs:
The thread for CM9 with instructions to flash is here: link !
Be sure to do all this step and flash the latest nightly.
I already had to update from CM7 to CM9 twice and, each time, I got it working without problem. So please, try again, make sure to follow the steps and tell us if you're experiencing the same troubles again.
Click to expand...
Click to collapse
Hi guys, I have the exact same issue.
updated from MIUI to CM9 and got yellow screen. Tried different ROMs and Kernel but no solution. Eventually I went back to CM7 and yellow gone away.
but when I try to flash CM9 .... here it comes again! I followed step by step flashing instructions.
any suggestion please?
@mishulake did you solve? how? thanks in advance!!
This is a thread for the discussion of the bluesleep fix / deep sleep issue specifically for the Motorola Atrix 4g
There is a known issue with some roms that prevents the device from entering the deep sleep cpu state, which is ultimately responsible for a significant reduction in battery life. This is believed to be caused by a glitch in the Bluetooth permission settings. A fix has been developed (known as the bluesleep fix) which is thought to correct the problem, and allow the device to enter deep sleep. It has been suggested that the bluesleep fix will also correct a glitch that prevents the wifi from sleeping. I have not experienced wifi sleep issues myself, so I can’t provide any first-hand knowledge.
Almost everyone who has experienced deep sleep issues and has used the bluesleep fix agrees that it works. I have corrected the problem on my device on CM7, CM9, and CM10 roms. The increase in battery life was dramatic.
However, the bluesleep fix is not without controversy. Many people, including at least one developer, believe the bluesleep fix works and recommends its use. Another developer submitted his version of a fix to CM. There are others, including one whose opinion I respect, that believe there is no reason the fix should work and don’t believe that it does. There have been many recent discussions on the topic on CM9 and CM10 threads that you can search for yourself.
If you have used the bluesleep fix to successfully correct deep sleep issues, or tried the fix and it didn’t work, or strongly believe one way or the other, please share your knowledge and experiences below for the benefit of the community!
[The bluesleep fix is attached (flash with CWM) along with before and after screenshots for a CM9 rom on my device.]
[FYI, I was involved in some of the linked discussions under my former user name (Atrix_FauxG). I thought I should mention this to avoid any confusion.]
[At the time I posted this thread I was unable to determine who created the bluesleep fix. If anyone knows, please inform me so I can give proper credit.]
______________________________________________
Edit:
1) I got confirmation from Th3bill that he wrote bluesleep_fix based on settings from olegfusion. Please take a moment to thank both of them (here and here). The bluesleep_fix file can also be found here (feel free to click on a few ads while you are there to further show your appreciation).
2) I neglected to mention that I observed the greatest increase in battery life on CM9 and CM10 roms.
Th3bill first brought it to our attention when building miui
Sent from my MB860 using xda premium
upndwn4par said:
[The bluesleep fix is attached (flash with CWM) along with before and after screenshots for a CM9 rom on my device.]
Click to expand...
Click to collapse
Or not?
As for me, my battery life was always very good on the Atrix. At some point I came across this bug and the fix for it and I applied it just to be safe. I know what the fix does (basically it setuids a few bluetooth-related utilities and fixes their ownership) and I guess I can kinda sorta see how it would be possible that that fixes the issue. However I can't say I noticed any big difference in my battery life after applying it.
For the record, I went from stock ROM to CM7-RC3, then to CM7-stable, and am now on ABC.
Not sure!
I posted this in another thread: http://forum.xda-developers.com/showpost.php?p=29854345&postcount=2154
After the full wipe and fresh install without the fix my Atrix is going into deep sleep fine.
I am using CM10 by epinter
Worked for me. I am using CM7 by the way. Before I implemented the fix, my phone never went into deep sleep. Now it does all the time.
Hmm,
Basically, mount /system rw, and chmod 04755 /system/xbin/hci*.
Not sure what the target rom is, but on my bell I don't have a hcidump. I have a dexdump though.
Cheers!
NFHimself said:
Hmm,
Basically, mount /system rw, and chmod 04755 /system/xbin/hci*.
Not sure what the target rom is, but on my bell I don't have a hcidump. I have a dexdump though.
Cheers!
Click to expand...
Click to collapse
Yeah, that's not the one.
I think the primary target would be CM7 and all ROMs based on it. I have a CM7 based ROM and I have all three hci* utilities.
And yeah, that's basically it, like I said in my previous post. It setuids all three and sets their ownership to root:shell (0:2000).
As stevendeb25 mentioned above, the primary target was MIUI (CM9).
ravilov said:
Yeah, that's not the one.
I think the primary target would be CM7 and all the ones based off it. I have a CM7 based ROM and I have all three hci* utilities.
And yeah, that's basically it, like I said in my previous post. It setuids all three and sets their ownership to root:shell (0:2000).
Click to expand...
Click to collapse
I got 17 hours deep sleep without the bluesleep fix file. I'm on Epinter's CM10.
Sent from my Nexus 7
upndwn4par said:
As stevendeb25 mentioned above, the primary target was MIUI (CM9).
Click to expand...
Click to collapse
Ah, I see. Yeah, CM7 (GB) has all the proper drivers to support the Atrix hardware fully, my guess is that that's the reason CM7-powered devices are able to enter deep sleep state regardless of permissions and ownership of the Bluetooth utils.
Here's a screenshot of my current state. This is after applying the patch though, so I don't know if it's relevant really, but here it is anyway.
I never checked while on CM7.0, but for me CM7.2 did not enter deep sleep until I applied the patch.
ravilov said:
Ah, I see. Yeah, CM7 (GB) has all the proper drivers to support the Atrix hardware fully, my guess is that that's the reason CM7-powered devices are able to enter deep sleep state regardless of permissions and ownership of the Bluetooth utils.
Here's a screenshot of my current state. This is after applying the patch though, so I don't know if it's relevant really, but here it is anyway.
Click to expand...
Click to collapse
Epinter's CM10 did not enter deep sleep for me. Though, the last update I applied was 20120729. Maybe he incorporated his own fix I mentioned in the OP in to his rom.
Soldier-2Point0 said:
I got 17 hours deep sleep without the bluesleep fix file. I'm on Epinter's CM10.
Sent from my Nexus 7
Click to expand...
Click to collapse
upndwn4par said:
Epinter's CM10 did not enter deep sleep for me. Though, the last update I applied was 20120729. Maybe he incorporated his own fix I mentioned in the OP in to his rom.
Click to expand...
Click to collapse
You should try 0803 build. No problems here. Epinter did not include any secret fixes to the rom because he did not mention it in the changelog. No sense in fixing something if you're never going to mention it. The blue sleep fix file is listed on his website, but not included on the rom.
This blue sleep fix file may have been useful on other roms, but is not needed on Epinter CM10.
Sent from my MB860 on CM10
I was on Epinter's 0803 build for a few days this week. No deep sleep without bluesleep fix.
Do you use bluetooth? If you don't leave your BT on then there are no deep sleep problems. I don't turn my BT off ever.
I have spent the last few days on Joker's CM10 and same thing - no deep sleep without fix.
Soldier-2Point0 said:
You should try 0803 build. No problems here. Epinter did not include any secret fixes to the rom because he did not mention it in the changelog. No sense in fixing something if you're never going to mention it. The blue sleep fix file is listed on his website, but not included on the rom.
This blue sleep fix file may have been useful on other roms, but is not needed on Epinter CM10.
Sent from my MB860 on CM10
Click to expand...
Click to collapse
My phone goes to deepp sleep without problem, cm7.2 latest nightly.
Sent from my MB860 using xda app-developers app
will this work for the new jelly bean nightly ( 815 ) ...? using darksides new cm10 a07.2
oh and my phone goes into the sleep of death where i can only pull the battery to fix it...will this work for that...?...thanks in advance...
This will fix the bluesleep problem on any CM7 device, but I don't think it will help your SOD problem and it could (in theory) make it worse. I have never experienced the SOD, but many users have said that increasing the minimum clock speed on your kernel to 456 MHz will help.
phordych05 said:
will this work for the new jelly bean nightly ( 815 ) ...? using darksides new cm10 a07.2
oh and my phone goes into the sleep of death where i can only pull the battery to fix it...will this work for that...?...thanks in advance...
Click to expand...
Click to collapse
How can I revert back after flashing the fix?
Restore the backup you should make before flashing anything.
TopDroid said:
How can I revert back after flashing the fix?
Click to expand...
Click to collapse
What I always do before flashing this kind of CWM zip is extract the flashable .zip, see what files it is going to replace or modify, backup my current version of them, replace the modified versions in the folder with my originals (renaming the originals to the modifieds' name, respectively, if necessary), zip it up, and there you have it! That Revert zip almost always works (never failed for me)!
Sent from my MB860 using Tapatalk 2
As some of us run CM10/AOKP/AOSP with Siyah kernel I decided to start a new thread because:
1. reporting issues with CM10 running Siyah kernel in CM10 thread is not good and slows down codeworkx debugging process - SO JUST DON'T
2. in offical Siyah kernel thread there are still more Sammy ROM users and it is not easy to follow.
If any mod, codeworks, teamhacksung and/or gokhanmoral has anything against this thread, oh well just close it.
Some of observations and solutions I have found so far:
1. CM10 (and/or kangs) work best with LF5 modem (some have good results with LG8 modem also) - keep both of CWM flashable files on your sdcard and test (in my case Sammy LG8 ROM works only with LG8 modem and CM10 only with LF5 modem). Also you should have (in most cases) have screenlock sound ON (in sounds) or otherwise the other party cannot hear you (if that is the case turn on screen lock sound via settings/sound and reboot, if it doesn't help, flash other modem, wipe caches and fix permissions - thanks to jnr21). More on modems here (thanks to UpInTheAir).
2. There seems to be some distortion with latest beta6 if audio settings are set at 63 and eq is set to eargasm. thanks to thyttel for pointing it out. Use default values or try playing with settings.
3. For memory leak there are 3 dirty solutions: reboot your phone every once in a while; disable lockscreen (thanks to codeworkx) or apply 'fix' (well its debatable if it's a fix, but..) from this thread (thanks to F1tty).
4. If you have no deep sleep (use CPU spy to check), try rebooting few times and/or disable media scanner on startup (there'ss an app for that - Rescan Media).
Feel free to add your solutions and report your issues.
All credits to Team Hacksung, codeworkx, gokhanmoral and anyone I forgot.
Memory Leak Fix
Thanks for the thread.
Using the memory leak fix on the RR JB Rom with Siyah kernel.
Hard to tell if it's working after two hours of use.
Will give feed back after two days of no restart.
thanks for the feedback. well it's not a fix, but temp measure..
had issues on RR with media scanner preventing deep sleep, but fixed it..
btw. siyah beta6 is out, so is new codeworkx build 0808.
so far so good, only wakelocks I have are from network location cause by google now, but that is expected.
@vels707: this may be good to add to op too: I you don't have on-call sound, turn on screen lock sound via settings/sound and reboot, if it doesn't help, try other modem, wipe caches and fix permissions.
This is known issue/solution, and i need to enable screen lock sound on every cm10 based rom with siyah kernel.
jnr21 said:
@vels707: this may be good to add to op too: I you don't have on-call sound, turn on screen lock sound via settings/sound and reboot, if it doesn't help, try other modem, wipe caches and fix permissions.
This is known issue/solution, and i need to enable screen lock sound on every cm10 based rom with siyah kernel.
Click to expand...
Click to collapse
it's already in there, but i will expand it per your post . thanks.
vels707 said:
it's already in there, but i will expand it per your post . thanks.
Click to expand...
Click to collapse
Oh, you're right, i just read too quickly
all seems to work fine with XXLH1 modem.
thanks to pkoper for posting it http://www.mediafire.com/?zyef8nbdnfnt126
there seems to be some distortion with latest beta6 if audio settings are set at 63 and eq is set to eargasm. thanks to thyttel for pointing it out. at default levels all is good.
Manar Aleryani said:
Thanks for the thread.
Using the memory leak fix on the RR JB Rom with Siyah kernel.
Hard to tell if it's working after two hours of use.
Will give feed back after two days of no restart.
Click to expand...
Click to collapse
The memory fix method suggested in the other thread for the memory leak did not work for me.
I can confirm that the leak is caused by the lockscreen, because after disabling it i didn't notice any leak.
Using a third party locker app is not really that bad
Manar Aleryani said:
The memory fix method suggested in the other thread for the memory leak did not work for me.
I can confirm that the leak is caused by the lockscreen, because after disabling it i didn't notice any leak.
Using a third party locker app is not really that bad
Click to expand...
Click to collapse
and also by notification bar pull downs/ups. will update first post on monday. holiday time
Have you guys extensively used stock cm10 vs with siyah and seen if the memory leak is worse either way? I'm rebooting twice a day sometimes but I haven't run stock cm10 for more than a few hours, is hard to break away haha
Sent from my GT-I9300 using Tapatalk 2
bclark said:
Have you guys extensively used stock cm10 vs with siyah and seen if the memory leak is worse either way? I'm rebooting twice a day sometimes but I haven't run stock cm10 for more than a few hours, is hard to break away haha
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
using both, one day or so cm10 one day or so siyah. memory leak is the same. sometimes i have to reboot once a day, sometimes twice.. depends.
vels707 said:
using both, one day or so cm10 one day or so siyah. memory leak is the same. sometimes i have to reboot once a day, sometimes twice.. depends.
Click to expand...
Click to collapse
Yeah, I just thought of it and figured it might be some conflicting issue but my phone is so smooth the reboot is worth the trouble.
Hi! Could anyone help me figure out why I have such high battery drain? I get about 2,5 hours of screen on time if I'm lucky. This is only on AOSP roms. According to GSMbattery it's "kernel is" that drains the most battery. I also have betterbatterystats installed but I'm not sure how the read that app.
This is the data from GSM -> kernel OS:
GSam Labs - Battery Monitor - Export Data
Kernel (Android OS)
Sep 7, 2017 9:42:54 AM
senny22 said:
Hi! Could anyone help me figure out why I have such high battery drain? I get about 2,5 hours of screen on time if I'm lucky. This is only on AOSP roms. According to GSMbattery it's "kernel is" that drains the most battery. I also have betterbatterystats installed but I'm not sure how the read that app.
This is the data from GSM -> kernel OS:
GSam Labs - Battery Monitor - Export Data
Kernel (Android OS)
Sep 7, 2017 9:42:54 AM
Click to expand...
Click to collapse
Lol kernelOS? That sounds like a custom ROM...
Just reinstall the system
Choose an username... said:
Lol kernelOS? That sounds like a custom ROM...
Just reinstall the system
Click to expand...
Click to collapse
It is a custom rom Lineage OS. What do you mean by reinstall system I've tried wiping everything multiple times but the battery still drains.
senny22 said:
It is a custom rom Lineage OS. What do you mean by reinstall system I've tried wiping everything multiple times but the battery still drains.
Click to expand...
Click to collapse
KernelOS doesn't exist, that's what i mean. every android iteration has something called a kernel, which manages the CPU and stuff. it's a part of the system, and not an OS at all. If you don't know what that is I wouldn't recommend that you poke around, you might slip up and DFU brick your phone...
By reinstall the system I mean:
-go to TWRP
-wipe system, data, cache, dalvik
-flash the A2017X universal bootstack, the modem file for your phone, the ROM, the OpenGApps if you want to have Google stuff, Magisk or SuperSU for root
-Reboot and use
Choose an username... said:
KernelOS doesn't exist, that's what i mean. every android iteration has something called a kernel, which manages the CPU and stuff. it's a part of the system, and not an OS at all. If you don't know what that is I wouldn't recommend that you poke around, you might slip up and DFU brick your phone...
By reinstall the system I mean:
-go to TWRP
-wipe system, data, cache, dalvik
-flash the A2017X universal bootstack, the modem file for your phone, the ROM, the OpenGApps if you want to have Google stuff, Magisk or SuperSU for root
-Reboot and use
Click to expand...
Click to collapse
I have reinstalled that way many times with many different aosp ROMs and kernels. Since reinstalls won't fix it is my only option to stay stock if I want over 4 hours of screen on time?
senny22 said:
I have reinstalled that way many times with many different aosp ROMs and kernels. Since reinstalls won't fix it is my only option to stay stock if I want over 4 hours of screen on time?
Click to expand...
Click to collapse
Try to flash a custom kernel, and if it doesn't do anything then yeah, go back to stock
I would try Wakelock detector or look into alarm section of BBS.
Can you tell us which modem you are using and which device you own?
Choose an username... said:
Try to flash a custom kernel, and if it doesn't do anything then yeah, go back to stock
Click to expand...
Click to collapse
I've tried both llama and radioactive kernel for a few days each. K guess I'll have to go back to stock.
SilentEYE said:
I would try Wakelock detector or look into alarm section of BBS.
Can you tell us which modem you are using and which device you own?
Click to expand...
Click to collapse
I don't think it's got anything to do with wakelocks as it doesn't use barely any battery when the screen is off. Overnight it might use 3-4 percent. Over 2 hours in the day it only drains 1 percent.
I use the modem from the LOS thread and I have the G model of the phone.
senny22 said:
I don't think it's got anything to do with wakelocks as it doesn't use barely any battery when the screen is off. Overnight it might use 3-4 percent. Over 2 hours in the day it only drains 1 percent.
I use the modem from the LOS thread and I have the G model of the phone.
Click to expand...
Click to collapse
You might have the cores always at max speed. Use Kernel Adiutor, and try to use the conservative governor on big and LITTLE cores
senny22 said:
I don't think it's got anything to do with wakelocks as it doesn't use barely any battery when the screen is off. Overnight it might use 3-4 percent. Over 2 hours in the day it only drains 1 percent.
I use the modem from the LOS thread and I have the G model of the phone.
Click to expand...
Click to collapse
Please try b05 modem.
I use it without problems.
Why don't you post screens of battery usage and signal strength timeline?
I've tried the conservative governor now. It didn't help.
QUOTE=Choose an username...;73715509]You might have the cores always at max speed. Use Kernel Adiutor, and try to use the conservative governor on big and LITTLE cores[/QUOTE
I've tried the conservative governor now. It didn't help.
senny22 said:
QUOTE=Choose an username...;73715509]You might have the cores always at max speed. Use Kernel Adiutor, and try to use the conservative governor on big and LITTLE cores
Click to expand...
Click to collapse
I've tried the conservative governor now. It didn't help.[/QUOTE]
senny22 said:
I've tried the conservative governor now. It didn't help.
Click to expand...
Click to collapse
How can I install with the B05 modem? Just flash I stead of the one in the LOS thread?
senny22 said:
How can I install with the B05 modem? Just flash I stead of the one in the LOS thread?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?p=73586271
senny22 said:
Hi! Could anyone help me figure out why I have such high battery drain? I get about 2,5 hours of screen on time if I'm lucky. This is only on AOSP roms. According to GSMbattery it's "kernel is" that drains the most battery. I also have betterbatterystats installed but I'm not sure how the read that app.
This is the data from GSM -> kernel OS:
GSam Labs - Battery Monitor - Export Data
Kernel (Android OS)
Sep 7, 2017 9:42:54 AM
Click to expand...
Click to collapse
Hi Senny22. Were you able to figure it out as I have the same issue with official RR ROM. I also tried to reinstall things from scratch without luck. Thanks
adromn said:
Hi Senny22. Were you able to figure it out as I have the same issue with official RR ROM. I also tried to reinstall things from scratch without luck. Thanks
Click to expand...
Click to collapse
No fix unfortunately ):
adromn said:
Hi Senny22. Were you able to figure it out as I have the same issue with official RR ROM. I also tried to reinstall things from scratch without luck. Thanks
Click to expand...
Click to collapse
senny22 said:
No fix unfortunately ):
Click to expand...
Click to collapse
Without proper screenshots and more precise information about your settings no-one can help you properly.
SilentEYE said:
Without proper screenshots and more precise information about your settings no-one can help you properly.
Click to expand...
Click to collapse
Hi. Since yesterday I run dark room as opposed to RR official. I did factory reset using twrp 3.1.1.0. Before changing roms I tried to install different modems. Currently b06 since I have G version. According to stats phone does sleep yet battery drain is high. I think last night lost like 40% or even more. Not sure when this all started. I've been using RR for months without any issue. The thing is that I was always charging my phone at night so I don't know when exactly this started to happen. Perhaps there is a hardware issue. I will try to get back to stock this weekend if no other solution is found. Cheers