I have a Redmi Note 4 , unrooted, running stock MIUI 8.5.4.0 . I'm having two issues lately , which I've observed for a week now and now finally posting it after failed attempts to fix the issue.
The alarm doesn't ring. There is no issue with the settings. It rings if i test it by setting an alarm for say,1 minute from the current time but it doesn't seem to ring when it's supposed to , for example morning alarm. I don't have any optimizers that would prevent alarm from ringing ( if something like that happens) . It once rang 8 minutes after the set time though.
I'm also having battery drain issues. Losing 20-25% overnight . "Android System" is at the top of battery use . I tried figuring out the reason behind this by using "Better Battery Stats" ( granted permission BATTERY_STATS through adb ) and "deviceidle_maint" is at the top always under the partial wakelocks .
These issues started happening suddenly. I didn't change any settings from the time when it was working fine.
I've already tried doing a factory reset and clearing cache . Tried draining the battery completely and fully charging it in a switched off state ( as it helped me with a similar battery issue on some other device) .
Please help.
I have the same problems. GPS working for you?
Sent from my Moto G (5) Plus using Tapatalk
matrixzone said:
I have the same problems. GPS working for you?
Sent from my Moto G (5) Plus using Tapatalk
Click to expand...
Click to collapse
Yes. No issue in GPS
utkarsh agarwal said:
I have a Redmi Note 4 , unrooted, running stock MIUI 8.5.4.0 . I'm having two issues lately , which I've observed for a week now and now finally posting it after failed attempts to fix the issue.
The alarm doesn't ring. There is no issue with the settings. It rings if i test it by setting an alarm for say,1 minute from the current time but it doesn't seem to ring when it's supposed to , for example morning alarm. I don't have any optimizers that would prevent alarm from ringing ( if something like that happens) . It once rang 8 minutes after the set time though.
I'm also having battery drain issues. Losing 20-25% overnight . "Android System" is at the top of battery use . I tried figuring out the reason behind this by using "Better Battery Stats" ( granted permission BATTERY_STATS through adb ) and "deviceidle_maint" is at the top always under the partial wakelocks .
These issues started happening suddenly. I didn't change any settings from the time when it was working fine.
I've already tried doing a factory reset and clearing cache . Tried draining the battery completely and fully charging it in a switched off state ( as it helped me with a similar battery issue on some other device) .
Please help.
Click to expand...
Click to collapse
Anyone?
I know that stock MIUI 8.5.x.x has various problems and users at MIUI official forums aren't happy of this.
I suggest to check there for any solution if available, but maybe your best move is downgrading to 8.2 or upgrading to the developer version (that will become stable in the next weeks). Or using a custom ROM, like LineageOS or the MIUI from Xiaomi.eu
Related
I've noticed something strange which seems to drain my battery faster when it happens.
Some apps that use sensors seem to leave the sensor active after closing the app itself (even with force close from app manager).
I've first noticed this problem with the app "GPS Essentials", then "GPS Status" the next day, they left the "Magnetic Field" sensor active after manually force closing them.
After a few hours, in Badass Battery Monitor, I could see that the Apps were eating about 75% of the battery, and when looking at the details, "GPS Essentials" was using about 45%, more than the kernel and android system), and it said that it had been using the "Magnetic Field" sensor for more than 5 hours, although the app was manually force closed about 20 minutes after I've started it.
That was in the stock ROM.
Since then, I've installed a custom ROM (CheckROM V2, so it's still based on Samsung's base ROM), and the problem is appearing again.
This time, I've had the same problem with Sygic that left the "Orientation" sensor active, and continued using it according to Badass Battery Monitor, even after force closing Sygic.
Did anyone else notice that or is it a problem with my phone?
Is there a solution besides rebooting every time after using any of these apps?
Thanks!
I've found a similar problem, and explanations on why it's happening, but it says that it appeared in Gingerbread but has been corrected in Honeycomb and ICS.
It does seem like the exact same problem with the same symptoms though, so I wonder if it really is gone...
Here is the page where I found the info :
http://fivasim.pcriot.com/androsensor.html
And here is a quote from that page :
Update: After many months of testing and debugging I haven't found a way to fix the battery issue for good. Perhaps I shouldn't... It's not really my issue but a general android problem (just google for "gingerbread battery drain"). And it happens with EVERY app that makes use of the sensors that are the root of the problem.
The battery leakage comes from android sensors that are not well supported by the kernel or the android OS. Most usually the accelerometer sensor causes the issue but sometimes the light sensor and the proximity sensor can cause this issue as well. Other sensors seem to have nothing to do with battery drain.
However I have found what's causing it and ways to `patch` over it (unfortunately, no way to permanently fix it).
Trying to invoke a sensor with such a problem, will cause the sensor to stay open even after the app is stoped and disposed of memory.
Another common issue is a conflict. Two apps register the same sensor, then one app unregisters but fails because the sensor is in use by the other app. The sensor stays in use by one of the two apps and this will remain even after both apps are killed.
In most cases there is a way to fix this:
- In the first case, you may just find which sensor is misbehaving (strange readings, very slow response or 'Failed to start' error etc.). Go to AndroSensor's settings and disable that sensor. Then reboot, run AndroSensor once and wait to see if the problem persists. Most usually the light and the proximity sensors are to blame for this issue. Sometimes the issue is caused only if both light and proximity are enabled, but disappears after disabling any of the two.
- If you don't have a misbehaving sensor then there is probably some conflict. Conflicts can be caused (usually in Gingerbread) when having auto-rotate (accelerometer use) or auto-brightness on.
Solution: Go to your device's display settings and disable auto-brightness and auto-rotation. Then reboot, run AndroSensor once and wait to see if the battery drain continues. If the problem persists then there is probably a conflict with some hidden/system service. Most usual is the conflict with SGS and SGS2 secret menu ( by dialling "*#0*#" on the dialer ). I have found no way to bypass this and it can only be solved by disabling the accelerometer and orientation sensors in AndroSensor, then reboot (orientation sensor makes seemless use of the accelerometer).
The only good thing about this, is that in HoneyComb and ICS the issue seems to have disappeared for good!
Am I really the only one with the problem?
Mithrandir007 said:
I've noticed something strange which seems to drain my battery faster when it happens.
Some apps that use sensors seem to leave the sensor active after closing the app itself (even with force close from app manager).
I've first noticed this problem with the app "GPS Essentials", then "GPS Status" the next day, they left the "Magnetic Field" sensor active after manually force closing them.
After a few hours, in Badass Battery Monitor, I could see that the Apps were eating about 75% of the battery, and when looking at the details, "GPS Essentials" was using about 45%, more than the kernel and android system), and it said that it had been using the "Magnetic Field" sensor for more than 5 hours, although the app was manually force closed about 20 minutes after I've started it.
That was in the stock ROM.
Since then, I've installed a custom ROM (CheckROM V2, so it's still based on Samsung's base ROM), and the problem is appearing again.
This time, I've had the same problem with Sygic that left the "Orientation" sensor active, and continued using it according to Badass Battery Monitor, even after force closing Sygic.
Did anyone else notice that or is it a problem with my phone?
Is there a solution besides rebooting every time after using any of these apps?
Thanks!
Click to expand...
Click to collapse
Does CPU Spy confirm that problem, showing awake instead of deep sleep?
chamonix said:
Does CPU Spy confirm that problem, showing awake instead of deep sleep?
Click to expand...
Click to collapse
It does seem to go to deep sleep, but I still see a big difference in battery life between when it happens (around 7-10%/hour), and after I reboot (~ 1%/hour).
Before I start applications using those sensors, the battery life is normal as well, so I don't think it's something else.
I've just made a few screenshots to show what's happening.
Last night, before going to bed, I've rebooted the phone, then started Sygic and AndroSensor, exited the apps, then manually force closed them to make sure.
Then I left the phone charging for the night.
This morning, I remove the phone from the charger, and Badass Battery Monitor starts from that point to calculate the battery drain from everything (so I'm sure neither Sygic nor AndroSensor have been running at all since I unplugged the phone).
Since then, a bit less than 2 hours have passed (I've barely used my phone during that period since I was getting ready then driving to work).
There was a 5% discharge (which is strangely not as much as I had yesterday, but still more than the usual 1%/hour when in standby) and we can clearly see what's eating the battery the most in Badass Battery Monitor.
The "Orientation", "Pressure", "Magnetic Field" and "Accelerometer" sensors have been running the whole time since it was unplugged.
What do you think, is this normal behavior?
I've now installed another custom ROM (Omega 8, with the new samsung firmware update), and the problem seems to remain..
If I'm the only one with the problem, I'm starting to think it might be something hardware (or an app I've installed every time maybe), since I've had the problem with every ROM I've installed...
Switching to another kernel didn't seem to help either.. I'm really starting to wonder if this is something I can fix.
Does no one else have the problem?
I think I've found the reason but now I wonder why no one else seems to have the problem (or maybe I'm the only one who actually cares ).
It looks like it's a battery usage reporting bug in the Samsung firmwares, not an actual drain.
Whenever you run an app which uses sensors (like GPS Status, AndroSensors, Sygic, ...), there is a good chance that when quitting the app, Android will not register the sensors as "stopped", even though they are not running anymore.
This means that the current battery life calculation takes those sensors into account as if they were still running, and the battery % drops faster than it should.
Here's a post from the creator of GPS Status, explaining the problem :
http://forum.xda-developers.com/showpost.php?p=23106668&postcount=491
There is also a small explanation from the author on the Google Play page for GPS Status, I'll quote :
"KNOWN FIRMWARE ISSUES (please do not report them):
- Samsung phones: Because of a firmware bug those phones may report extreme battery consumption for GPS Status (and for other programs using sensors) even if it is not running. This is harmless and no power is consumed! Just ignore it and let's hope that a future firmware upgrade will fix this."
So I'm still wondering if this is something we can fix, or if we have to wait for Samsung to correct that bug?
Mithrandir007 said:
I think I've found the reason but now I wonder why no one else seems to have the problem (or maybe I'm the only one who actually cares ).
Click to expand...
Click to collapse
Yes I care. Thanks very much for posting this. I've noticed exactly the same thing and it's been driving me crazy. Good to know it's just a false alarm. With ICS 4.0.4 coming to the Galaxy S2 soon, maybe it will be fix there.
Mithrandir007 said:
I think I've found the reason but now I wonder why no one else seems to have the problem (or maybe I'm the only one who actually cares ).
It looks like it's a battery usage reporting bug in the Samsung firmwares, not an actual drain.
Whenever you run an app which uses sensors (like GPS Status, AndroSensors, Sygic, ...), there is a good chance that when quitting the app, Android will not register the sensors as "stopped", even though they are not running anymore.
This means that the current battery life calculation takes those sensors into account as if they were still running, and the battery % drops faster than it should.
Here's a post from the creator of GPS Status, explaining the problem :
http://forum.xda-developers.com/showpost.php?p=23106668&postcount=491
There is also a small explanation from the author on the Google Play page for GPS Status, I'll quote :
"KNOWN FIRMWARE ISSUES (please do not report them):
- Samsung phones: Because of a firmware bug those phones may report extreme battery consumption for GPS Status (and for other programs using sensors) even if it is not running. This is harmless and no power is consumed! Just ignore it and let's hope that a future firmware upgrade will fix this."
So I'm still wondering if this is something we can fix, or if we have to wait for Samsung to correct that bug?
Click to expand...
Click to collapse
If this is really the problem that would be an deep in Android or between the hardware and android as it is the 'batteryinfo' service reporting sensors data.
Indeed, I don't think there is an easy fix for this one, unless someone has already worked on that part ((un)registration of sensors from the battery measurement service).
Hopefully it'll be fixed in a future version of the firmware, or in Jelly Bean.
XDA-Usr : maybe it'll be fixed in that version, indeed..
It is just a false alarm, although it still leads to inaccuracy of the battery level.
Mithrandir007 said:
I think I've found the reason but now I wonder why no one else seems to have the problem (or maybe I'm the only one who actually cares ).
It looks like it's a battery usage reporting bug in the Samsung firmwares, not an actual drain.
Whenever you run an app which uses sensors (like GPS Status, AndroSensors, Sygic, ...), there is a good chance that when quitting the app, Android will not register the sensors as "stopped", even though they are not running anymore.
This means that the current battery life calculation takes those sensors into account as if they were still running, and the battery % drops faster than it should.
Here's a post from the creator of GPS Status, explaining the problem :
http://forum.xda-developers.com/showpost.php?p=23106668&postcount=491
There is also a small explanation from the author on the Google Play page for GPS Status, I'll quote :
"KNOWN FIRMWARE ISSUES (please do not report them):
- Samsung phones: Because of a firmware bug those phones may report extreme battery consumption for GPS Status (and for other programs using sensors) even if it is not running. This is harmless and no power is consumed! Just ignore it and let's hope that a future firmware upgrade will fix this."
So I'm still wondering if this is something we can fix, or if we have to wait for Samsung to correct that bug?
Click to expand...
Click to collapse
Now 1 year has past since your original post. I'm still experiencing the same problem on my Galaxy Note 2. :silly:
luzok said:
Now 1 year has past since your original post. I'm still experiencing the same problem on my Galaxy Note 2. :silly:
Click to expand...
Click to collapse
On my Galaxy S4, the problem seems to be gone, so hopefully it'll be gone on your device as well once Samsung releases the 4.2.2 update.
Sent from my GT-I9500 using xda app-developers app
When i fall asleep i just place my phone nearby the bed and its on airplane mode,wifi closed,data closed and generally no apps running(i think so).The battery is level (ex)50% and when i wake up,about 7 hours later its always about 15-20%.why this happen?
I checked the battery manager just after i waked up and the first was screen(56%) and after that adobe reader(10%)
Start with Better Battery Stats and read the ten million battery posts on XDA .
jje
chaos748 said:
When i fall asleep i just place my phone nearby the bed and its on airplane mode,wifi closed,data closed and generally no apps running(i think so).The battery is level (ex)50% and when i wake up,about 7 hours later its always about 15-20%.why this happen?
I checked the battery manager just after i waked up and the first was screen(56%) and after that adobe reader(10%)
Click to expand...
Click to collapse
Mine drops about 1.5% every hour whenever it's on standby.
JJEgan said:
Start with Better Battery Stats and read the ten million battery posts on XDA .
jje
Click to expand...
Click to collapse
Better battery stats does not work.dont know why.and i made my own post cause i cannot find the solution of the problem on other posts.try to be more polite to your answers
have you tried downloading the xda version of the better battery stats? if not here it is
http://forum.xda-developers.com/showthread.php?t=1179809
Is your phone rooted? Like others said, try to install the xda-forum version of BBS but it's weird because I did install the one from GPlay.
One of the first lead is the WiFi? Is it always turned on? There's a bug with it. Go into the advanced WiFi settings and set it to 'only if activated' (I don't know the exact spell in English but it's something like that).
But you better have to dl BBS & check the wakelocks.
Sent from my Galaxy S3 with Omega ROM v27.2 / Phenomenal Extreme 4.0 kernel
which rom are you using?
that should be solved flashing another kernel, try it.
dont use a rom...my phone is just rooted
Deleted.
JJEgan said:
Deleted.
Click to expand...
Click to collapse
what?
Underclock when you're not using your phone.
That will save battery.
If ur using stock TW. Put on power saving mode
PM Me if u want to know more.
Try using an app called easy battery saver and only use the cable and plug that came with your galaxy s3 it works for me, today I had eight hours after charge and using internet with 3g nearly continuously.
You would get much more by leaving it on standby.
Also restrict your background data, turn off your automatic updates at play store andturn off WiFi while screen is asleep.
Follow all these for better battery.
Use any battery investigation apk/widget (I'd recommend battery monitor widget) and look what is causing the drain...
may I guess: cell standby or gpsd?
guys i remember you that the cell phone is on flight mode with wifi,gps and data turned off
and, if you have a soft which contains a bug - you'll have such processes running.
It is up to you to install any apk which will contain more detailed statistics what actually is consuming so much juice.
If you do not want - no one would force you.
chaos748 said:
When i fall asleep i just place my phone nearby the bed and its on airplane mode,wifi closed,data closed and generally no apps running(i think so).The battery is level (ex)50% and when i wake up,about 7 hours later its always about 15-20%.why this happen?
I checked the battery manager just after i waked up and the first was screen(56%) and after that adobe reader(10%)
Click to expand...
Click to collapse
I have the exactly same problem,30% drain overnight.That happens after updating to 4.1.1 JellyBean.With ICS never happened.
Go into the battery page, click on the graph and then post a screenshot of the detailed graph here. It is usually an app or process not letting the phone go into standby. Happened to me when I had my phone on ICS out of the box. I fixed that all up through the individual app settings and all was sweet. Then when I went from ICS to JB, the issue came up again and I had to go through the apps again to change the settings back. It seems that by updating from ICS to JB, certain settings get set back to default, which then does not allow the phone to go into standby.
Culprits that I have found are:
Facebook - set to manual refresh interval
Weather (or any weather widget) - manual refresh interval
Google play store - Turn off Google AdMob Ads
Any form of newsreader (I was using Pulse) - Turn off notification when there are new stories
Wifi advanced settings - Set Keep Wifi on during sleep to "Always"
Samsung account - Turn off sync
Samsung app store - Turn off Update Notification, turn off push notification, turn off ad preferences.
chaos748 said:
When i fall asleep i just place my phone nearby the bed and its on airplane mode,wifi closed,data closed and generally no apps running(i think so).The battery is level (ex)50% and when i wake up,about 7 hours later its always about 15-20%.why this happen?
I checked the battery manager just after i waked up and the first was screen(56%) and after that adobe reader(10%)
Click to expand...
Click to collapse
Maybe some apps running in background if you are using *viber* delete it
It makes proximity sensor always on.
Try delete apps like that
Thanks
Sent from my GT-I9300 using xda app-developers app
Guys please keep in mind that keeping the stock os without any custom kernel might be not as effective than using an adequate custom rom...
In addition remember, cooler temperatures cause ur battery to lose its charge faster...
So if ur phone is placed on the window shelf and its getting cold during the night it might cause ur battery to drop fast..
I made this observation with my sgs plus....
Hope i helped.
Hi
My clock app stop working around 8:45PM and also my phone works slow during that period.
everything works well after 4:00 AM ....?
I notice my alarm don't work in between that time and also no time update on any widget or on status bar time..
During that time if i try to install any app from app store than it also not work they will stuck at installing and never finish that installation process...Also my phone get hotter during that period and it use more battery power
like it use 30% battery in 2 hr
Once it pass 8:45 PM it stay that time on status bar unless you reboot phone and after reboot it works for 5 min and then again get Frozen to last state...
I have two android device (One X+ , nexus 7 both root and unlocked bootloader and has stock ROM )both device doing same thing.
I thought it's a malware or virus so I wipe my phone and put custom ROM on it but I still have that Problem in my phone...?
So it might be any app that cause that problem or something else that trigger at certain time
I am totally confuse how can i solve this problem...?
Any one have that problem ...?
i have the same problem on my s3
i use paranoid android 3.99
i think that i hibernated a wrong app with greenify but i am not sure.
same thing, waiting solution..
Hi
My clock app stop working around 8:45PM and also my phone works slow during that period.
everything works well after 4:00 AM ....?
I notice my alarm don't work in between that time and also no time update on any widget or on status bar time..
During that time if i try to install any app from app store than it also not work they will stuck at installing and never
finish that installation process...Also my phone get hotter during that period and it use more battery power
like it use 30% battery in 2 hr
Once it pass 8:45 PM it stay that time on status bar unless you reboot phone and after reboot it works for 5 min
and then again get Frozen to last state...
I have two android device (One X+ , nexus 7 both root and unlocked bootloader and has stock ROM )both device
doing same thing.
I thought it's a malware or virus so I wipe my phone and put custom ROM on it but I still have that Problem in my
phone...?
So it might be any app that cause that problem or something else that trigger at certain time
I am totally confuse how can i solve this problem...?
Any one have that problem ...?
Hi,
I can’t say I’m impressed at all with the SGS2 battery life running CM11 M7 (KitKat 4.4.2). Quite often the battery won’t last through the day (luckily I can charge it at work, otherwise it wouldn’t even be bearable as a phone).
My crappy Sony Xperia J (JB) I had for a couple of weeks as a replacement could easily reach the end of the day with 70% charge still left when I plugged it in at night.
Android battery stats always show Android System and Android OS as the main offenders (around 20% - 25% each), above Screen usage, Voice calls, Mobile standby...
BetterBatteryStats tells me the phone is in the Deep Sleep most of the time, but also that it is awake (mostly at 200 MHz) quite a lot of time as well.
Here’s what I have already tried:
Disabled location services
Disabled Google Now
Disabled Google+ Auto-backup
Opt out of interest-based ads
Disabled back up data to Google servers
Disabled “Android Device Manager” as Device Administrator
Uninstalled all updates to Google Play Services
Disabled automatic updates from the Play Store
Disabled Mobile Data Limit
Disabled Automatic Date/Time updating
Uninstalled Lookout Antivirus
Uninstalled Viber
Uninstalled Skype
Rebooting the phone before connecting the charger
Rebooting the phone immediately after disconnecting the charger
I really don’t want to perform a factory reset specially since I have read some other comments by Galaxy S5 and Nexus 5 owners (KitKat 4.4.2) saying it didn’t work…
So what exactly is going on here?
Thanks!
Sorry
MegaSharkXDA said:
Hi,
I can’t say I’m impressed at all with the SGS2 battery life running CM11 M7 (KitKat 4.4.2). Quite often the battery won’t last through the day (luckily I can charge it at work, otherwise it wouldn’t even be bearable as a phone).
My crappy Sony Xperia J (JB) I had for a couple of weeks as a replacement could easily reach the end of the day with 70% charge still left when I plugged it in at night.
Android battery stats always show Android System and Android OS as the main offenders (around 20% - 25% each), above Screen usage, Voice calls, Mobile standby...
BetterBatteryStats tells me the phone is in the Deep Sleep most of the time, but also that it is awake (mostly at 200 MHz) quite a lot of time as well.
Here’s what I have already tried:
Disabled location services
Disabled Google Now
Disabled Google+ Auto-backup
Opt out of interest-based ads
Disabled back up data to Google servers
Disabled “Android Device Manager” as Device Administrator
Uninstalled all updates to Google Play Services
Disabled automatic updates from the Play Store
Disabled Mobile Data Limit
Disabled Automatic Date/Time updating
Uninstalled Lookout Antivirus
Uninstalled Viber
Uninstalled Skype
Rebooting the phone before connecting the charger
Rebooting the phone immediately after disconnecting the charger
I really don’t want to perform a factory reset specially since I have read some other comments by Galaxy S5 and Nexus 5 owners (KitKat 4.4.2) saying it didn’t work…
So what exactly is going on here?
Thanks!
Click to expand...
Click to collapse
Sorry I cannot help you, however, I am also contemplating installing cm11 on my sgs2 i9100.
I wanted to ask you if you phone came with android version 2 installed on it? (maybe in that case the problem is incapable hardware)
Mine came with 2.3.4 and i do not want to face the same problem as you are now (sorry).
Thanks
It is normal, that non-stock-based roms consume more power because Samsung haven't open-sourced all drivers. And Kitkat drains more than Jellybean. Try Slimsaber Reborn. It has a decent battery life, an very acitve developer, and is nicely customizable.
Any luck?
MegaSharkXDA said:
Hi,
I can’t say I’m impressed at all with the SGS2 battery life running CM11 M7 (KitKat 4.4.2). Quite often the battery won’t last through the day (luckily I can charge it at work, otherwise it wouldn’t even be bearable as a phone).
My crappy Sony Xperia J (JB) I had for a couple of weeks as a replacement could easily reach the end of the day with 70% charge still left when I plugged it in at night.
Android battery stats always show Android System and Android OS as the main offenders (around 20% - 25% each), above Screen usage, Voice calls, Mobile standby...
BetterBatteryStats tells me the phone is in the Deep Sleep most of the time, but also that it is awake (mostly at 200 MHz) quite a lot of time as well.
Here’s what I have already tried:
Disabled location services
Disabled Google Now
Disabled Google+ Auto-backup
Opt out of interest-based ads
Disabled back up data to Google servers
Disabled “Android Device Manager” as Device Administrator
Uninstalled all updates to Google Play Services
Disabled automatic updates from the Play Store
Disabled Mobile Data Limit
Disabled Automatic Date/Time updating
Uninstalled Lookout Antivirus
Uninstalled Viber
Uninstalled Skype
Rebooting the phone before connecting the charger
Rebooting the phone immediately after disconnecting the charger
I really don’t want to perform a factory reset specially since I have read some other comments by Galaxy S5 and Nexus 5 owners (KitKat 4.4.2) saying it didn’t work…
So what exactly is going on here?
Thanks!
Click to expand...
Click to collapse
Hi MegaShark!
I have almost the same issue you have, my device never go to deep sleep... (by "never" I mean 1 minute deep sleep and 1 hour 200MHz)
After months trying, getting help from Better Battery Status thread, flashing, freezing, going crazy, I commited suicide (flashed stock ROM), but it is driving me mad.
The last try I did was with SlimSaber Reborn (Android 4.3.1), but no luck also.
Installed "Unbounce", prevented nlp wakelock, prevented safe alarms and nothing, it only gets worse...
All I get is my device always warm (always running at minimum of 200MHz) and more than 10% battery drain per hour.
Have you found out what is the problem with our S2 on custom ROMs?
Thank you!
First of all, I would advise you to update your rom. CM11 M7 is old now and is filled with bugs (along with versions around that). Update to CM11 M11 Snapshot which will most likely fix many of the problems you are facing but you will need to do a full wipe (factory reset, wipe dalvik and cache partitions). So sorry, the only way to fix is to wipe your data and update.
Will try!
gsstudios said:
First of all, I would advise you to update your rom. CM11 M7 is old now and is filled with bugs (along with versions around that). Update to CM11 M11 Snapshot which will most likely fix many of the problems you are facing but you will need to do a full wipe (factory reset, wipe dalvik and cache partitions). So sorry, the only way to fix is to wipe your data and update.
Click to expand...
Click to collapse
I remember to have hope until CM11 M9... But I'll give M11 a try and report back here!
Drain NOT related to any of the CM version
I have been facing battery draining problem in my sgs2 (i9100) just after installing CM 11.
Then I tried NeatROM without any Luck!
Every time i cleaned data, cache and dalvik to be sure...
at the end I moved back to Stock ROM - everything fine there...
but again then I decided to have just root and custom recovery installed... which required me to Flash Jeboo Kernel v1.2a (which comes with CWM based recovery 6.0.2.7 preloaded)
then it started same problems again... overheating - battery draining ...
It clearly look like ... the battery draining/overheating problem is because of .... Kernel AND/OR CWM 6.XXX
I think, if one want to install CM 11 in sgs2, after installing ROM, he/she need to flash it with some other kernel.
If anybody have tried some other kernel, which doesn't cause battery draining/overheating problem, then pls post here so that other can also try...
Confused
pankhawala said:
I have been facing battery draining problem in my sgs2 (i9100) just after installing CM 11.
Then I tried NeatROM without any Luck!
Every time i cleaned data, cache and dalvik to be sure...
at the end I moved back to Stock ROM - everything fine there...
but again then I decided to have just root and custom recovery installed... which required me to Flash Jeboo Kernel v1.2a (which comes with CWM based recovery 6.0.2.7 preloaded)
then it started same problems again... overheating - battery draining ...
It clearly look like ... the battery draining/overheating problem is because of .... Kernel AND/OR CWM 6.XXX
I think, if one want to install CM 11 in sgs2, after installing ROM, he/she need to flash it with some other kernel.
If anybody have tried some other kernel, which doesn't cause battery draining/overheating problem, then pls post here so that other can also try...
Click to expand...
Click to collapse
pankhawala, I installed the last available SlimSaber Reborn (4.3) (here: http://forum.xda-developers.com/gal...rivatives/rom-slimsaber-reborn-i9100-t2811657) because o lots of positive feedback on this ROM.
It is really a very nice ROM, but my battery drain problem persisted, I was losing more than 10%/hour in idle.
I just tried to "live with it" and after some weeks it mysteriously gone away.
I was happy for a few days and it went back again.
Now, it has been since this Sunday that it is gone again.
I'm being able to have a very acceptable battery life, very good deep sleep times and less than 4%/h when idle (screen off).
I didn't changed anything and it just got better by itself.
I'm sure it will start to drain again, just don't know when or what is triggering it.
My last hope is that when new Lollipop ROMs start coming out for our S2, some holy developer figure out this problem or that the problem is simply gone.