Related
I bought an Xperia Mini two days ago, and successfully flashed a recent build of FXP (the popular CyanogenMod 7 fork for this phone) onto it. Everything is working quite well, but the battery drain is truly astounding: even when the phone is doing absolutely nothing but idling in its 3G network, a fully charged battery lasts for about 10 hours, which of course is totally unacceptable. The battery consumption overview lists "Cell standby" and "Phone idle" as the main battery consumers (both at nearly 50%), with "Display being a distant third with ~3%.
I was wondering if that could be because of my phone's baseband firmware: it is at a release ending in "-56", which I believe to be quite old. My questions now are:
1.) Is it possible that my battery drain problems are baseband-firmware related?
2.) Is it possible to upgrade the baseband firmware image alone, leaving the rest of the phone's firmware unaltered?
3.) Is there anything I need to take into account before flashing a baseband image of my choice? Do certain baseband firmware images, for example, do not work with certain kernels, or anything like that?
4.) Is "flashtool" the only way to flash a baseband image onto my Smultron?
5.) Which baseband firmware would you recommend, and where can I get it from?
6.) (Slightly OT) Why is all the Xperia Mini/FXP related stuff hosted on crappy one-click-hosters' websites? That's driving me _insane_.
Thanks in advance for your input!
The stock 4.0.2.A.0.42 build's baseband ends with -56, so I believe it's not that old.
If the baseband version is the problem it should cause the problem with the stock ROM, too.
Baseband
1. they could be.
2. yes. you can get the baseband here http://forum.xda-developers.com/showthread.php?t=1445821
3. there shouldn't be any problems, just make sure you choose the corect baseband, baseband controls the radio(wireless communication hardware) it should be kernel independent, the baseband in the second answer works perfectly with FXP. Bad baseband version could result in low signal strength, or even inability to make calls.
4. it may not be the only tool, but it is the best one currently
5. second answer
6. there are some pretty big files that don't fit in the upload limit on theese forums
Instructions to reduce battery consumption:
drain the battery completely(0%-unable to turn on)
charge it to 100%
go to recovery and find the option "Wipe battery stats"
repeat the first two steps
Your battery should now last much longer
nidzo732 said:
Instructions to reduce battery consumption:
drain the battery completely(0%-unable to turn on)
charge it to 100%
go to recovery and find the option "Wipe battery stats"
repeat the first two steps
Your battery should now last much longer
Click to expand...
Click to collapse
Incorrect, it doesn't help at all.
Xperia's have Li-Ion or Li-Po batteries, which means no memory effect and battery capacity does not change. Also these battery stats are wiped after every full charging anyway, so your action doesn't change anything.
Thanks so much everyone for answering my questions. It's really hard for me to get to the gist of the myriads of threads on these forums and to dig up the information I seek, so that was a very pleasant experience for a change
Is there a specific combination of baseband firmware, kernel image and ROM image that you can recommend that works well with the Smultron line of devices?
On the other hand, I must say I think I'd be really happy with the FreeXperia-fork of CyanogenMod (but would prefer the "vanilla", upstream version of it really, to be honest) if it weren't featsing on my battery so relentlessly. If you could give me a few pointers on how to start debugging the high battery drain, I'd be happy to give my shot at tracking down the cause...
For completeness' sake: Upgrading the baseband did not influence battery consumption at all. I reflashed the stock firmware (using Flashtool - a very handy program) in order to try reproducing the problem on the vanilla setup of the phone, but failed to do so - it lost about 6% of its charge level over the past 8 hours.
I'll try flashing FXP111 (or a later release) some time in the future, and see if the problem persists.
jtru said:
For completeness' sake: Upgrading the baseband did not influence battery consumption at all. I reflashed the stock firmware (using Flashtool - a very handy program) in order to try reproducing the problem on the vanilla setup of the phone, but failed to do so - it lost about 6% of its charge level over the past 8 hours.
I'll try flashing FXP111 (or a later release) some time in the future, and see if the problem persists.
Click to expand...
Click to collapse
6% in idle in 8 hours isn't bad.
Yeah, I'm well aware of that. What I'd like to have is that kind of battery drain with a CM-based ROM image. I'm not sure what it takes to get there, but I sure hope it's doable - I don't very much like the stock firmware, and it includes so many (to me) absolutely useless applications that cannot be removed.
jtru said:
Yeah, I'm well aware of that. What I'd like to have is that kind of battery drain with a CM-based ROM image. I'm not sure what it takes to get there, but I sure hope it's doable - I don't very much like the stock firmware, and it includes so many (to me) absolutely useless applications that cannot be removed.
Click to expand...
Click to collapse
1. Root you phone (downgrade to 42, root, update over the air to 62)
2. Unlock bootloader
3. Install custom kernel
4. Remove bloatware (can send you a list with what i removed)
5. Enable init.d and install scripts like v6 supercharger KAK and more
6. Use an app like setcpu or antutu to change min cpu speed to lowest possible
and make profiles for cpu speed on various situations eg. when screen is off
cpu speed 122-368
7. Make various tweaks for battery saving and performance
Enjoy a much faster and responsive phone with better battery savings and most important learn a lot in the process and be proud of your custom made phone
A while ago I have a weird problem. When my phone is on charge and I turn on 3G it keeps turning off like I would removed the battery. Everything fine until I start an app which uses internet, but when I do it turns off almost immediately. Wi-Fi works fine just the 3G is the problem. I got this problem on two different ROMs (FXP 115, FeraLab v14) and two different kernels (basic FXP115, DoomKernel v6 - medium overclocked), so it must be hardware related, am I right? If not hardware, what else could it be?
Sent from my Xperia X10 using Tapatalk
I had the same exact problem with my Motorola Backflip stock. In fact, if I moved locations where 3G wasn't available to where 3G was broadcasted, it would reboot. I could not fix it with any rom I installed (even tried CM7 which made the phone excellent except for the 3G reboots). I tried full wipes, stock Motorola Motoblur kernel, and everything else. I'm no dev so I didn't try tweaking anything myself and ended up getting rid of it and going with the X10. You can try the SEUS method but it can very well be hardware unfortunately. I hope you have more luck than I!!
If your phone is overclocked that could be a problem. Have a good search though sure I seen this before and think u have to either change something in build-prop or alter/remove a certain process (don't quote me though)
Sent from my X10S using XDA
laneyofdeath said:
If your phone is overclocked that could be a problem. Have a good search though sure I seen this before and think u have to either change something in build-prop or alter/remove a certain process (don't quote me though)
Sent from my X10S using XDA
Click to expand...
Click to collapse
My phone has been overclocked since months, but I've never got this problem earlier, so I don't think that causes it, but I'll give it a try. And I'll search again maybe this time I find the answer. Thank you
Hi, I got a similar problem. Since a few weeks ago, flashed a ROM and when I've tried to use the phone, it keeps turning off randomly, sometimes after a few minutes, sometimes after hours. So, I tried to take it back to the clean original 2.3.3 ROM, but it keeps happening. ¿Any idea? ¿Any solution? Please, help me. Oh, something else, it only happens when the phone's used with the battery, when it's attached to my laptop as modem, the problem doesn't appear.
Greetings from (cloudy) Germany. Many battery problem threats exist in this forum and the world wide web. Unfortunately most of them reach hundreds of pages and after the 3rd or 4th page it slides away from any technical discussion and becomes very emotional. This is the reason why i´m going to open another one, which hopefully helps me. So here is my ....
... frame what happened:
I own a SGS2 GT-I9100, branding free. It´s almost half a year old. When i bourght it, it came with GB 2.3.4 which worked fine for me. At the beginning of this month i recived ICS via Kies. As a result of this update my phone became super slow. Almost all applications hung and chrashed. So i decited to manually go back to an older FW. I´ve choosen GB 2.3.5, as the look and feel was better for me, then 2.3.4.
... Problem:
Since i did the update to 4.0.3 my battery performance is 10 times worse in ->standby<- as it was with 2.3.4.
... what i did so for, to isolate the problem:
Many threads talk about an Android OS bug. After a long search it is still not clear to me, what this bug excatly means!?!? Apps, which drain the battery are not installed (there are no special Apps installed, except the ones which come with the FW). I have no widgets running and the phone is in Airplane mode. If is switch off the phones display i loose about 30% battery during one night (8 - 9 hours). With 2.3.4 it was about 3% per night. If i use my phone during the day (SMS, Calls, Wireless, 3G and music) it does not increase the battery usage very much. maybe 40% per 8 - 9 hours. I did a factory reset to my phone, installed cpu spy and switched the display off. Analysis show 99% Deep Sleep. nevertheless it uses 30% battery during this time.
In summary:
- German GB 2.3.4 got an update from K.I.E.S. to ICS 4.0.3 -> bad phone performance and battery drained
- Downgrade from German ICS 4.0.3 to German GB 2.3.5 following a procedure and firmware from android-galaxy dot info
- With GB 2.3.5 the performance returned back to normal but battery was still bad.
- Installed German GB following a procedure and firmware from android-galaxy dot info
- Performance was still good, but battery drained.
- Installed netherlands GB 2.3.5 and battery was still draining.
- Received ICS 4.0.3 via software update. Fortunately the phones performance is still very good but the battery drains anyway.
All test where performed without any app installed and in flight mode.
Questions:
1. what ist the so called Android OS bug in connection with battery problems?
2. does anybody have the same problem and solved it?
3. is there any way to recive the stock rom, which came with my phone?
-> a friend of mine have the same SGS2 with GB 2.3.4 and without any battery problem.
Thanks for constructive, helpfull and unemotional technical feedback. If you have further question, send me a PN. I´ll summarize them, and add them to this post. It will keep it clearly and in coherence.
Why not rename General forum Q&A then users wont break the rules .
1. what ist the so called Android OS bug in connection with battery problems?
No search ???? read the Android OS Bug Post .
2. does anybody have the same problem and solved it?
Long time ago Android 2.3.6 .
3. is there any way to recive the stock rom, which came with my phone?
YES if you know what it was and can search for it .
BASICS
FAQ
http://forum.xda-developers.com/showthread.php?t=1065995
NEW HERE
http://forum.xda-developers.com/showthread.php?t=1134290
bible
http://forum.xda-developers.com/showthread.php?t=1473577
Guide
http://forum.xda-developers.com/showthread.php?t=1125282
Stock Roms .and csc
http://forum.xda-developers.com/showthread.php?t=1075278
Thanks for your quick reply. I found many things for "Android OS Bug", also solutions. For example: "Disable widgets" or "stop wireless sharing". Unfortunately nothing helped me.
If you kow about the same problem with the battery and how to solve it, please tell me. I searched for it and was not successful.
I know the page for Stock Roms and how to apply them. As you can read in my initial post i did some up- and downgrades. I went back to official 2.3.4 with existing battery problem.
Maybe this was a missunderstanding. I need to know if ther is any "smart" way, without rooting etc., to get a rom out of an existing phone, without the battery drain.
Regards, ... ibmuser2
theres a zip file for os drain prblm thts for ,wen the phone dosnt charge uptill 100..but still every android user faces a batt prblm,,but android phones r more like a pc..so it s power hungry
rocky23 said:
theres a zip file for os drain prblm thts for ,wen the phone dosnt charge uptill 100..but still every android user faces a batt prblm,,but android phones r more like a pc..so it s power hungry
Click to expand...
Click to collapse
Thx for your information.
My phone charges up to 100% (as far as it does not lie to me). ;-)
I do not complain about the power consumption. I complain about the difference between stock 2.3.4 and any ohter stock ROM / update i installed.
Regards, ibmuser2
ibmuser2 said:
Thx for your information.
My phone charges up to 100% (as far as it does not lie to me). ;-)
I do not complain about the power consumption. I complain about the difference between stock 2.3.4 and any ohter stock ROM / update i installed.
Regards, ibmuser2
Click to expand...
Click to collapse
Have you tried any custom roms?
Or contacted the retailer about this?
Maybe it is a hw problem.
It would suggest a battery fault tbh.
Flashing repeatedly can put strain on the battery (from my own experience), also as far as I am aware, the official update via KIES did cause battery related issues; I never experienced, but my friends did, and Samsung UK where troubleshooting by, removing the battery for 10 minutes, letting it drain out when put back in the phone, then performing a full charge when switched off. If not resolved > factory reset - which did help one of my friends surprise, surprise lol.
If you are still in first 6 months I would advise contacting Samsung Germany for a replacement battery to see if any improvement. Otherwise you can buy cheap online.
Hey superthug & T__. Thx for your good comments. I´ll give it a try. One of my friends have a SGS2 without any problem. I´m going to x-change it with him.
Cheers.
Hey Guys. I made some further testing, but it´s getting more ande more worse.
1. I x-changed the battery with another SGS2. My battery is draining and the other SGS2 is good. -> No battery fault.
2. I did many factory resets, installed betterybatterystats, but it shows no wake locks. all values are below 4%
3. I installed cpu spy, and it shows 98% Deep sleep, when not using it <---- as expected!
4. I changed my FW to:
I9100XWLP7_I9100XXLPS_I9100XEULP5
ICS 4.0.3
Base: I9100XXLPS
Kernel: 3.0.15-i9100XWLP7-CL340913
[email protected]#3
Build: IML74K.XWLP7
All was downloaded from this Forum. I9100XWLP7_I9100XXLPS_I9100XEULP5 is the default, which came with KIES. I verified this with another SGS2, running this FW trouble free!
5. When i charging my SGS2 now, it heats up extremly. The CPU is running at 1Ghz while external power is connected (not only during charging)
Any ideas?
Hi,
I am seeing the same issue. I noticed after upgrading to ICS that the phone was working well for a few days and battery life was good, then after I plugged it in to charge overnight (as I always do) I found that the battery had decreased and the phone was hot to touch near where the camera is located on the back the following morning.
I reset the phone to defaults and I was able to charge a couple of times but this didn't fix the problem and it started happening again.
I have tried charging from my laptop, and 2 separate USB chargers with different cables and the same fault has occured.
A reset of the phone seems to temporarily fix the issue and I can charge the phone again but when I plug in again to charge I see the battery decreasing.
It seems as if something is screwing up and causing the CPU to run at 100% when the charger is attached which would explain why the phone is warm/hot to touch.
I'm just testing at the moment to see if I can get the phone to a state where the charger is connected and the battery is decreasing to try to identify the cause. I suspect that it may have something to do with when the phone goes to sleep and the screen turns off so I will try to set the timeout to 10 mintues to see if this helps and the battery starts to charge again.
Suspend Mode bug + linux power management regressions: flight/airplane drains battery
Hi, I experienced a similar issue with GS2 i9100G. I also haven't found a clear and definite answer in the various forums I have been digging into.
To sum it up here's what I found:
Android 2.3.4 worked perfectly fine with GS2, but upgrade to 2.3.6 introduced a suspend mode bug. Basically Suspend mode would cause the system to enter a loop, thus the battery drain while in flight mode.
The best solution would be to downgrade/stay with Android 2.3.4 (when it ain't broke don't fix it).
Possible workarounds if you'd rather not fiddle with your OS version:
Wifi settings > advanced settings > Policy: Wifi always on (so as not to trigger suspend mode with wifi), then (optional) use a Battery Manager App to fine-tune the wifi activation. Wifi always on drains your battery, but less than the system loop if you're not constantly on the move.
Don't use flight mode, shut you phone at night and use a good old clock) (and redirect calls to your landline if you must)
Try and find the apps that require regular sync thru wifi and might be the sole culprit causing the system to enter the loop
Note that Android 2.3.4 is based on Linux kernel 2.6.32 and that Android 2.3.6 is based on kernel 2.6.35 which introduced a major power management regression.
The fix for this regression has not been fixed before current kernel 3.3 (although some developer may have backported the fix into 3.2), so I would advise to stay away from current Android 4.0.3 ICS which is based on kernel 3.0 (later versions will be based on kernel 3.2 though)
I am not sure if this is the root for the suspend mode bug or if both issues are independent, but in the meantime 2.3.4 works perfectly fine.
EDIT: upgrade to 2.3.6 then 4.0.3 really stand as blunders from Samsung on such high-end Smarphones. Regardless of the device, waiting for the upcoming Android version 4.0.5 seems the better choice if you want to enjoy ICS and not regret iOS...
Android 4.0.3, a version with well-documented problems, including the battery problem, rather than 4.0.5, which solves many of those problems?
Probably not. Probably, the slow nature of Android updates is to blame. It took six months for version 4.0.3 to wend its way through the system, meaning it could yet be months more before the updated update, version 4.0.5, reaches users.
Right now, it seems their only option is to go back to 2.3.6, just like they’re asking.
from Samsung users bitten by upgrade bug (May 7th, afr.com)
Click to expand...
Click to collapse
Suspend Mode bug causing flight/airplane mode to drain battery
After trying different things I came to the conclusion that it all comes down to apps who force themselves to run in the background when you install them and request frequent syncs (free apps will do whatever it takes to boost their ad revenue).
To me it's still a bug in the suspend mode (Apps shouldn't be allowed to request a connection while in Airplane mode, doing it triggers a loop of failed attempts) and Samsung overlooked it.
In the meantime the previous solutions I mentioned do work:
n°1 (lazy fast) - Wifi settings > advanced settings > Policy: Wifi always on (so as not to trigger suspend mode with wifi), then (optional) use a Battery Manager App to fine-tune the wifi activation. Wifi always on drains your battery, but less than the system loop if you're not constantly on the move.
n°2 (depends on the number of apps) - Try and find the apps that require regular sync thru wifi and might be the sole culprit causing the system to enter the loop
n°3 (last resort) - Don't use flight mode, try to turn off data instead or shut you phone at night and use a good old clock) (and redirect calls to your landline if you must)
Click to expand...
Click to collapse
A battery calibration shouldn't be of much help.
Eventually I read someone, with Android ICS 4.0.3 installed, who mentioned DTIM and explained that changing the default 5ms to 1ms solved his battery life problem (note that you usually set this parameter to the highest possible latency to save your battery on mobile devices)
this is by far the most interesting battery problem thread i have found in the past 2 weeks. this exactly describes the problem I've been having.
initially nothing was wrong for me either. straight out of the box went ok for months. i'm not sure, but i think it was 2.3.4. shortly after the stock official update (unbranded) update to android 4.0.3 i noticed the battery died in about a day, instead of 2 days.
things i tried thus far:
- flash 2.3.6 back. same problem.
- flash 2.3.4 back, same problem.
- since it sucks either way, i flashed the stock 4.0.3 again.
- disabled a whole ****load of apps i normally use. same problem.
- decided to root and flash dragonICS 4.0.4 with default siyah kernel
- swapped battery with a colleague who does not have this problem. same problem.
- reset battery thingy in extweaks, battery % reporting sucks big time since then, but essentially: same problem
- tried a lot of suggested tweaks in extweaks which are supposedly better. same problem.
- set syncing at a longer interval (even though it worked fine out of the box). same problem.
- disabling all the sensors i could (including rotation for the apps), wifi, data traffic in general. same problem.
- cut the light sensor polling interval in half (from 1sec to 2sec). same problem
- removed the SD-card, because god knows what conflict it could cause. same problem.
- removed sim card, since problems were reported between this phone, android4 and my provider. same problem.
- full battery drain and charge cycle. same problem
problem verification:
- battery monitor widget, which logs an obvious higher battery usage than my colleagues phone.
- badass battery monitor which clearly shows "kernel" and "android system" way up there, where it should never be.
- "system tuner" in the "task manager" section which shows "android system" and "/system/bin/surfaceflinger" using the most cpu time by far
- "cpu spy" shows the cpu most of the time in deep sleep, which looks pretty good to me.
i can see the android system is using a lot of time reading 2 sensors, which seem required by basic functioning of the device. screen rotating and brightness.
i am unable to find out what the kernel is doing with all it's time. but whatever the rom, it's doing something.
ps: not all tests were in this order or seperated as they are described.
better battery stats shows a few processes on top:
kworker/0:3
kworker/0:1
kworker/0:0
kworker/0:2
in this order
It was a hardware fault! Samsung replaced the planar, ... now it´s fine. Thanks to all replys and your help.
while i'm happy there is a solution i am wondering about the following:
how can software introduce a hardware fault?
Greetings, I tell them I've tried most ROMs for the x10 mini pro with Stock kernel, Android 2.3.7 has the problem but all of the lights (in a not ignite and other passes on all the time) another problem is the not wifi stays connected as in stock ROM and off at times, and the biggest problem, the battery does not last normal barely lasts 8 hours with average use and other applications when installing the system gradually becomes slow , I can not prove to Custom ROMs kernel since s1tool me: Not reconozigned Certificate
For I am looking for I recommend a ROM that is good, the battery last normal or near normal, no matter if it's Froyo or Gingerbread, how important is it to stock kernel and go smoothly, the keyboard lights work or not ignite (it would consume battery and a minor detail) and that he can put themechoose topics
I hope I can help, thanks!
No matter if the ROM is current or old, and if they can stop the link, they are greatly appreciate
00DSoul00 said:
Greetings, I tell them I've tried most ROMs for the x10 mini pro with Stock kernel, Android 2.3.7 has the problem but all of the lights (in a not ignite and other passes on all the time) another problem is the not wifi stays connected as in stock ROM and off at times, and the biggest problem, the battery does not last normal barely lasts 8 hours with average use and other applications when installing the system gradually becomes slow , I can not prove to Custom ROMs kernel since s1tool me: Not reconozigned Certificate
For I am looking for I recommend a ROM that is good, the battery last normal or near normal, no matter if it's Froyo or Gingerbread, how important is it to stock kernel and go smoothly, the keyboard lights work or not ignite (it would consume battery and a minor detail) and that he can put themechoose topics
I hope I can help, thanks!
No matter if the ROM is current or old, and if they can stop the link, they are greatly appreciate
Click to expand...
Click to collapse
Try this: Froyobread
It is very smooth and the battery performance is awesome! This was the first custom ROM I ever used, and it was perfect!
Here is the link for X10 Mini Pro version: http://forum.xda-developers.com/showthread.php?t=1190037&highlight=froyobread
Hope it helped
Hello,
I got XPERIA Mini Pro a couple weeks ago. It was on stock firmware with android 4.0.4. It's warranty ended a long time ago but the phone was still in a very good shape. I really like trying custom ROMs from different developers as I did on my previous XPERIA X10i. So I chose Unofficial CM11 from LegacyXperia with KitKat for start. I unlocked bootloader without any problems. Flashed kernel with flashtool, then flashed ROM with kernel's build-in recovery. It worked fine although sometimes It hung when I wanted to wake my phone and I had to pull battery out. It happend occasionaly and I though I can live with that. But after a couple days proximity sensor as well as front camera gone. I tried whiping cache, factory reset, pulling battery out for about 20 seconds, flashing ROM again, even flashing stock firmware again. Nothing helped. I did research and it appeared that this is common problem with mango after android 4.2. I think. OK, I thought I can live with that. I returned to CM11 but after a while problem with hungs on wake up started to annoy me. I decided to try the highest cyanogenmod for mango on stable stage of development, not nightly like CM11. It was CM9.1. Again, it worked fine and in fact, it was stable. But after a while I noticed that not only front camera and proximity sensor are gone but ALL OF MY SENSORS died. I tried a couple of things like before (whipe, reset, flash etc.). Tried going back on stock. Tried apps from market which test and reset sensors. Every one I tried said my phone does not support sensors. Accelerometer is crucial for me as I use SleepAsDroid app every day. I flashed CRDROID (based on CM11 but much much more stable) which I use till now. Tried doing research on Internet but I found nothing. Tried hitting my phone and dropping It (that helped a lot of people), tried heating battery by overloading processor (that helped a lot of people too). Nothing helped. Tried repleacing files responsible for sensors with the ones from stock firmware. Now test programs show that I have working light sensor but it does not change it's values at all. I accepted the fact that I won't restore my sensors but I must ask:
Is there anything more I can do? Did I missed something?
Is the only way to fix my problem buying a new motherboard? It appears strict hardware problem, right?
Please help, any suggestion will be much appreciated.
Best regards