Related
Hi,
I'm posting this in return for all the information I found about the HD2 and poor battery performance. I read every thread I could find and every single post in them. I learned a lot and that allowed me to solve my problem.
I got no more than about 10 hours of use out of my battery with average use. Initially I thought this was the norm, reading a number of threads on this issue. I could however not believe that the performance was so poor, even taking the large screen into account.
I decided to try and determine exactly what it was that caused the battery to drain to quickly. I loaded BattLog and found it invaluable (see http://forum.xda-developers.com/showthread.php?t=444920).
I immediately noticed that my phone was drawing 85 mA even when it was in standby (or what I thought was standby). Based on what I was reading, the current draw should not be more than 5 mA while the phone is in standby.
I noticed in one of the threads that there were complaints about G-Profile causing battery drain. Since I had it on my phone I thought that might be a logical place to look. I uninstalled it a lo and behold... the current draw fell to below 5 mA when the phone was in standby!
In addition I loaded Bandswitch which switches off my 3G connection after it has not been used for 60 seconds.
Now I have about 48+ hours of battery life. When not using the phone a lot it extends to a lot more than 48 hours.
The long and short of it is that if you get poor battery performance, chances are it is because of some software that is installed on your phone.
Here are a couple of usefull things I have found in helping resolve my battery issues:
1) Use Batlog (http://forum.xda-developers.com/showthread.php?t=444920) to log the current your phone draws. If it draws more than 5 mA during standby you have a problem, most probably related to a piece of software on your phone
2) Your phone should not be drawing much more than about 150 mA when in 'active' mode with the screen at 40% brightness.
3) If you are running G-Profile, uninstall it and recheck your current draw. Chances are that it is the culprit.
4) Having an active data connection does draw power from the battery. In my case this is about an additional 130 mA. Load something like Bandswitch to disable the data connection when it is not needed.
I hope this information helps somebody. I realise that the situation is different for everybody out there because of all the variants such as age of the battery, sofware loaded and use. However, the reality is that the battery issues are most probably not because of a bad battery or the hardware but rather because of software on the phone.
BTW I am running:
OS Version: 5.2.21869
Manilla version: 2.5.19211619.0
ROM version: 1.48.421.2 (71294) WWE
Radio version: 2.05.51.05_2
Regards
gerhardvr said:
Hi,
I'm posting this in return for all the information I found about the HD2 and poor battery performance. I read every thread I could find and every single post in them. I learned a lot and that allowed me to solve my problem.
I got no more than about 10 hours of use out of my battery with average use. Initially I thought this was the norm, reading a number of threads on this issue. I could however not believe that the performance was so poor, even taking the large screen into account.
I decided to try and determine exactly what it was that caused the battery to drain to quickly. I loaded BattLog and found it invaluable.
I immediately noticed that my phone was drawing 85 mA even when it was in standby (or what I thought was standby). Based on what I was reading, the current draw should not be more than 5 mA while the phone is in standby.
I noticed in one of the threads that there were complaints about G-Profile causing battery drain. Since I had it on my phone I thought that might be a logical place to look. I uninstalled it a lo and behold... the current draw fell to below 5 mA when the phone was in standby!
In addition I loaded Bandswitch which switches off my 3G connection after it has not been used for 60 seconds.
Now I have about 48+ hours of battery life. When not using the phone a lot it extends to a lot more than 48 hours.
The long and short of it is that if you get poor battery performance, chances are it is because of some software that is installed on your phone.
Here are a couple of usefull things I have found in helping resolve my battery issues:
1) Use Batlog to log the current your phone draws. If it draws more than 5 mA during standby you have a problem, most probably related to a piece of software on your phone
2) Your phone should not be drawing much more than about 150 mA when in 'active' mode with the screen at 40% brightness.
3) If you are running G-Profile, uninstall it and recheck your current draw. Chances are that it is the culprit.
4) Having an active data connection does draw power from the battery. In my case this is about an additional 130 mA. Load something like Bandswitch to disable the data connection when it is not needed.
I hope this information helps somebody. I realise that the situation is different for everybody out there because of all the variants such as age of the battery, sofware loaded and use. However, the reality is that the battery issues are most probably not because of a bad battery or the hardware but rather because of software on the phone.
BTW I am running:
OS Version: 5.2.21869
Manilla version: 2.5.19211619.0
ROM version: 1.48.421.2 (71294) WWE
Radio version: 2.05.51.05_2
Regards
Click to expand...
Click to collapse
and imagine that your rom version is accused of massive batt draining!
an upgrade to 1.66 / 1.72 should make a difference..or a custom rom
batlog?
Hi Gerhardvr,
What is the batlog software you used?
I'm very interested about your post.
Thanks.
J6B.
Very useful findings, gerhardvr. Thanks!
found BattLog
ok, I found BattLog
It's just in showthread.php?t=444920
Have a nice day guys.
cu
J6B.
When I ran the Test, it said that I was using up 242mA in standby! I dont believe I have G-Profile installed, unless it was pre installed on the device. I have the latest versions of the ROM, Radio, Manila, and OS version, so I know the culprit cant be the ROM version... Any ideas? I bought this phone from T-Mobile US.... Sooo yeah
Folks, I've been trying to get to the bottom of this as well. I have a number of cab files which do seem to help a little. One of the bigest culprits I've found is the screen lockers. Disable them and see how you fair!
soopahsteve said:
When I ran the Test, it said that I was using up 242mA in standby! I dont believe I have G-Profile installed, unless it was pre installed on the device. I have the latest versions of the ROM, Radio, Manila, and OS version, so I know the culprit cant be the ROM version... Any ideas? I bought this phone from T-Mobile US.... Sooo yeah
Click to expand...
Click to collapse
Soopahsteve,
I suggest you use Battlog to log to file. This is very useful as it will log the time stamp, the current temp of the battery and the current draw at the point in time. In addition it logs arious events on the phone, in particular the startup and shut down of applications, data connectivity, when you make or receive a call, whether you are talking or receiving on the call, etc. This can be opened in Excel and then analysed and if you are very lucky, you will pick up some patterns allowing you to link some programs to the battery drain.
However, the situation is typically slightly more complex to resolve since the culprit software are usually software that is loaded as TSR application at reboot. The result of this is that Battlog will not show the startup of these applications in the log file since they are already running at the time you are starting Battlog.
You should look at programs that manage phone profiles, screen lockers, screen calls or SMS messages, etc. In other words, any program that does work behind the scenes.
The reason you are seeing 242 mA in "standby" is because your phone is not really in standby. Although the screen is blank, something is preventing your phone from going into true standby, the processor is still active. The trick is to find what this is.
Sometimes the only approach is to uninstall the applications you suspect one by one and see if it makes a difference until you either find the culprit or can prove that none of the them are an issue. Then reinstall the ones you think are "safe" one by one and check whether the probelm pops up again. unfortunately you have to do the double sided approach because there could be more than one application that cuases your issue.
Painful I know but worh it when you have two days worth of battery time with some to spare.
Regards
See no reason to upgrade to the latest ROM
chris2busy said:
and imagine that your rom version is accused of massive batt draining!
an upgrade to 1.66 / 1.72 should make a difference..or a custom rom
Click to expand...
Click to collapse
You know it. In reality I would love to upgrade to the latest and greatest but I've customised my phone to the Nth degree (did obviously not upgrade the ROM) by installing all the little apps I find useful, Cookies Home tab (best thing since sliced bread), etc. My phone is now just the way I like it.
It would take me quite some time to upgrade the ROM and to customise it again from scratch and I really don't see the benefit. I might be force to do it when I get to a stage where there are software that I would like to load that only works on the later ROMs but until such time I'm not gonna try to fix that that ain't broke.
Regards
is this the bandswitch u are using? if not, can i check where to get the program?
http://forum.xda-developers.com/showthread.php?t=286844
gerhardvr said:
It would take me quite some time to upgrade the ROM and to customise it again from scratch
Click to expand...
Click to collapse
I just upgraded my ROM and did a Level 1 restore with Sprite Backup ... everything comes back except (I think) for wifi passwords.
i am drawing 180mA on standby..
im using custom rom, energy rom so thats very strange, but i have to agree that my battery life is terrible.. so i got to find a way to cut down on the 180mA drain..
I've always had good battery life on stock 1.66 rom losing 3% overnight with wifi and bluetooth turned off. Had to do a hard reset and started losing 15% overnight with the same everything. Did further resets and got nowhere. Ended up giving up on 1.66 although it had been fine previously after numerous hard resets - makes no sense but this is what happened. Just flashed to 1.72 and back to losing 3% overnight what it should be. And that is out of the box, to be honest all the battery saving registry tweaks are not worth the time installing and I leave 3G on all the time with updates coming through.
So it's all a bit random and shame on HTC for not sorting it out. My advice is do a hard reset, switch the wifi and bluetooth off and see in the morning if you have a reasonable battery life (or use the batt consumption program to verify standby consumption is sensible). Do this first before installing everything, getting frustrated and starting over again like I did when you discover that you're still experiencing high battery drain. This ensures that your starting point is a good flash and the phone is getting good life before adding any apps that could be causing a problem.
i have found my hd2 really does not like being in a poor or no coverage area. other phones i've owned have normally coped pretty well with no or very little signal. but not the hd2.
also noticed more drain in areas where there is only poor 3g coverage and its switching between 'g' and 'h' coverage.
fi3ry_icy said:
i am drawing 180mA on standby..
im using custom rom, energy rom so thats very strange, but i have to agree that my battery life is terrible.. so i got to find a way to cut down on the 180mA drain..
Click to expand...
Click to collapse
Energy ROMs, just like the name goes, use a lot of Energy
They are baked in with a lot of performance tweaks so it's not unusual to get lower battery life per charge compared to other more down to earth vanilla ROMs.
Thanks for this thread, a lot of interesting information about the battery life of my HD2.
Just to mention: battconfig shows the power consumption directly in the task bar, a good way to find power guzzlers while they are active.
It's a pity we have no central place in this forum with a list of background applications that are known to drain the battery faster.
Or, also a needed information, a list of applications that are known not to do this (like PhoneAlarm, PocketShield).
I'm using the official rom only and have non fancy apps running or installed while I'm using the test bat program. As I speak the SD card is removed and celular radio is turned off.
Acording to program there is an indicator which is switching from -229ma to +78ma is that what its drawing of power?
Euroman28 said:
Acording to program there is an indicator which is switching from -229ma to +78ma is that what its drawing of power?
Click to expand...
Click to collapse
+78ma??? That must mean you are charging the battery. The best way to test current draw is when it is only on the battery.
I get about -5ma draw on standby and it tops out at around 180ma when I have the screen on, but usually hovers around 130 - 150ma. I have my screen brightness at the lowest setting possible.
@OP, I wanted to say this earlier... great topic, very insightful.
I have a few suggestions for everyone posting in this thread. Let's try and get some common data together that is more tangible in order to give us a more similar & common perspective for these discussions.
I suggest the following
1) Soft Reset. Once the device is on, do not run ANY applications. In fact don't do anything except for following the below instructions.
2) Turn your screen brightness all the way DOWN! (Turn off Auto Backlight and manually set it to the lowest setting)
3) Check your power settings and make sure that while your phone is on battery, that it is set to dim the backlight after 30 seconds and turn off after 1 minute
*** I have attached 2 REG files below for both Backlight and Power. Please use them instad of doing it manually.***
4) Turn off all the radios (Phone, Wi-Fi, Bluetooth). Let's make our first round of tests with the Radio's off. Radio ON complicates things a bit as there are several applications to keep track of that use the Data Connection. I'll come up with a more comphrehensive list later so we can do the Radio ON tests.
Screenshots
Use a program like Shave&Save and get the following screenshots
1) Use any Task manager and get a screenshot of all the processes running. Sometimes the number of processes displayed is longer than the screen size can accomodate. Take 2 screenshots in this case making sure that you capture all processes. Edit the image with MS Paint or some other Image Program and attach it here as one image. See the example in the post below this one.
2) Goto \Windows\Startup and get a screenshot of the folder contents
3) If you are using Sense, drag the slider all the way to the end (settings) and goto About Phone. Goto Software Information and get a screenshot of that.
Monitoring the Battery
1) Make sure your phone is not connected to the charger or to the computer.
2) Open BattLog (can be found here), set the refresh rate to 1 second and Start Logging.
3) After you start the logging process do not touch the screen / the phone again for exactly 2 minutes.
TIME THIS with a stop watch. As soon as the 2 minutes it complete, turn the phone back on and stop the logging.
Information to post here
1) All the screenshots from above.
2) The current draw (both on standby and while active). Also, please attach the file that logged all the information in this format: Forum ID - BattLog - dd-mmm-yy.txt
3) ROM - Whose ROM? Release Date? Does it have Cookie's Home Tab Installed or any other MAJOR Sense Modifications.
Click to expand...
Click to collapse
SAMPLE POST
HTC HD2 (T8585)
OS: WM 6.5
ROM: Energy * Build 21907 * Release 01.JULY.10 * CHT v1.8.5 - Dinik Edition
RADIO: 2.07.50.27_2
Current Draw (mA)
Idle: -3 to -7
Screen On (w/o Radios): -83 to -117
Those figures look normal to me. You should be getting about as good a battery life as a device like this can achieve.
No matter how much SE can piss me off, I have to say they did a good job with the last update R2BA020 .
I did fully charge my battery, did not use any task killer or such only kept adw launcher. With a normal use the battery last me a little over 48 hours I was at 10% when i devided to recharge it again.
-Around 2 hours of video
-4 hours of reading with Aldiko
-1 hours of internet
-Around 50 txt msg
-20 call 5-15 min each
-3 Pictures
-4 Hour of music while reading
-Email and weather widget run to update every hour
-Fancy widget running
-Bluetooth on all the time
-Gps and wifi was off all the time
Bottom line it’s impressive, now I really can enjoy my device without carrying a charger and searching for an outlet all the time .
I completely agree, the 020 firmware is fantastic. My usage differs slightly but even using Bluetooth to listen to Spotify all day didn't drain my battery. Neither did using my phone as a wireless 3G modem with Wifi tethering.
Well, yes, nice improvements but the WIFI is still using a lot of juice
wifi is confirmed using alot.
the phonebook is now kind of stupid...
when you click a person's name, their contact shows up, and when you tap their phone #...instead of calling that person directly it would bring you to the dialer screen with the # entered in and you need to press "call" to call the person...
i mean..if im in someones contact page and i tap their #..im pretty sure i want or need to call them....i really dont understand the point of bringing the dialer screen up again..pretty stupid on SE's part in my opinion
Well a quicker step would be to long hold their name and call them
Sent from my X10i using XDA App
Well, I've rooted my device yesterday, started using it massively around 3 or 4 am to reconfigure everything and now its battery is at 8%:
throughout all the process wifi was used for internet (when needed, of course), 3g/gps/bluetooth turned off.
* Installed a lot of apps, some using barcode scanner, some using appbrain.
* Synced with google
* Restored a backup
* Reconfigured a lot of apps
* around 6 sms
* tweeted 2 or 3 times
* 5 to 10 calls 10m~ each
* listened to music through the day (around 2 hours of music, simple last fm scrobbler was used to cache the data, didn't scrobbled yet)
* read a pdf book around 1 hour
* some random usage through the day, like checking online stuff.
* Since I go to work using the subway, the signal reception is quite poor, so the phone prolly was searching for signal during the day.
Even wifi draining a lot of battery, the phone battery was quite good for everything that I've done today.
Apart from the battery the whole system feels better, all the UI customizations done by SE are faster (timescape, mediascape, dialer and so on).
I can say, like all of you, SE did a good job on this update. I can't wait for the Q3 2.1 release. Seriously, I want 720p video recording so much
Greetings guys,
Whats the difference R2BA020 and B2FA020.
Thanks for your kind reply.
Vatis
has anyone noticed any difference in call quality - in call volume especially
this was the thing i looked forward to getting the most out of this upgrade but no much difference i notice, still can't hear very well in any outside environment
i hope this issue becomes resolved...
I usually use headphones while outdoors, so I can't help here. Indoors it's been quite good, at least for me.
dpk0875 said:
has anyone noticed any difference in call quality - in call volume especially
this was the thing i looked forward to getting the most out of this upgrade but no much difference i notice, still can't hear very well in any outside environment
i hope this issue becomes resolved...
Click to expand...
Click to collapse
I was on fw 16 and it was a litter bit low but still fine, didn't notice any difference between 16 and 20 tho.
never heard of B2FA020 - Think it might have been a typo on someone's part?
Screen off while in call.
Not to start a new thread, I'll pin my question to this one. I've updated to R2BA020 (O2 Irl branded) and noticed that whenever in call the screen is not turning off, as it used to before. Did anyone else experienced this problem?
Regards, masterofp.
check your screen time out settings in the settings/ display/ screen timeout section.. it may be that it's reverted to a longer timeout period or to not time out at all.
im_iceman said:
check your screen time out settings in the settings/ display/ screen timeout section.. it may be that it's reverted to a longer timeout period or to not time out at all.
Click to expand...
Click to collapse
Nope, still @ 15 seconds...
Though overall battery usage seems to be better with R2BA020 (Rogers), I've run into an odd issue:
When tethering via PdaNet, my battery drains at an alarming rate. It dropped 20% in the past hour. This wasn't the case before I upgraded (was using stock Rogers firmware before) - it would drain, but much more slowly, going from 100% to maybe 55% over the course of the 8 hours I was at work tethered. It's almost as if it's not charging at all via USB (or is charging much more slowly than before).
I checked, and the phone does register as charging while tethered. So I'm not sure what exactly the issue is. Nothing else has changed.
-edit-
Turned off PdaNet during a meeting I had today just to make sure my X10 is charging properly via USB, and sure enough it is (gained 12% charge over the hour).
after updating into R2BA020, my sim tool kit and play now were gone. Now, I want them back (especially STK). Does anyone know how to do it? My X10 is not rooted yet.
I'm pretty happy with the new Facebook app. It got rid of the "Camera" icon on the mainscreen and replaced it with "Inbox", which makes so much more sense.
My ringtones got reset, and I noticed that Astro File Manager lost a few file associations. I'm prompted for all sorts of default apps etc now, but it's just a minor annoyance.
I did the update through the Sony Ericsson PC Software. The first boot after update took a very long time on the Rogers splash screen. I was afraid the device was bricked for a couple of minutes. I guess it was just the first boot, and the Xperia was restoring all my user data.
Does anyone have comparison between R2BA020 and R2BA023? appreciate if it includes benchmarking between them.
masterofp said:
Not to start a new thread, I'll pin my question to this one. I've updated to R2BA020 (O2 Irl branded) and noticed that whenever in call the screen is not turning off, as it used to before. Did anyone else experienced this problem?
Regards, masterofp.
Click to expand...
Click to collapse
yes, Am also facing the same problem
New firmware for our devices I5800DTLKDA (2.2)
jonathantng said:
New firmware for our devices I5800DTLKDA (2.2)
Click to expand...
Click to collapse
What's the difference? What's new in this ROM?
It's just a US based firmware I think.
Its for Canadian users of I5800L. Probably Latin American countries too....
Anyone know if this rom is for the 3 galaxy i5800L of Brazil, if there is any blockage in this rom is yes or any other kind, since I'm using the European Roma JPF, and I'm scared to update this with my phone and brik
was very grateful for whoever can help
Thanks Clarkkov, the rom works perfectly, improved GPS, WIFI, the speed of app, and did not change my programs do not run a hard reset. The only catch is that for anyone in Brazil there is no language PT-PT or PT-BR.
Wdconta said:
Thanks Clarkkov, the rom works perfectly, improved GPS, WIFI, the speed of app, and did not change my programs do not run a hard reset. The only catch is that for anyone in Brazil there is no language PT-PT or PT-BR.
Click to expand...
Click to collapse
Yes, the rom is fine , the menus are in english, but you can install swype beta for pt-pt
Sent from my GT-I5800D using XDA App
Hello, sorry is my question is trivial, but i tested many other roms but i can flash this one, afeter oding reboots my phone, there's a recovery mode screen saying E:Can't mount /dev/block/mmcblk0p2 and i tried 3 times, same results, so i'd like ask how you flashed correctly, thank you very much
I used this ROM in my GT-i5800L (from Vivo In Brazil) and my experience was not one of the best.
For starters, lots of the bugs I have seen in other Froyo releases are still there:
The alarm clock bug (if say it is 7:00PM and you want to set an alarm clock for the next day at 8:00AM, it automatically sets it for 8:00AM on the current day of the week, in other words it sets the alarm for 6 days and 13 hours, rather than in 13 hours) this becomes a problem because you have to manually change the days.
During a call, if you use the sensor the screen turns off, but when the screen turns back on after you apart it from your ear, the notification bar lights up green. This isn't a problematic bug, but it just shows an unfinished look and feel.
Rooting is a problem (z4Root does not work) and after rooting with SuperOneClick, the phone becomes slow, and even after installing busybox, there are noticeable differences.
GPS still takes forever to get a lock, when it actually does.
The camera can take only one photo. If you try to take a second shot without first leaving the camera, 80% of the times, the camera will lock up, show a green screen and/or force close.
The supposedly improved memory management of Froyo also doesn't become apparent. The included task manager doesn't show you running first party programs, just third party... Although clearing the memory is a bad thing for Android (you should only kill active programs if they are really slowing the phone down. Killing programs kills the battery life), you cannot do a thing to control it. The only option you are left with is wiping Level 1 and Level 2 memory, killing ALL active programs. If you want to SELECT which programs you want to kill, they have to be third-party programs.
Downloadable task managers seem to have little effect, since Froyo changes the way you can kill apps belonging to Android (first-party).
Because of the poor management, listening through Bluetooth is impossible, since the audio fades every 10 - 20 seconds because the phone neeeds to think. I first thought it was an AudioTuning issue, but then I tried launching a heavy app while playing music via BT, and the problem becomes evident.
Also, whenever I connect to bluetooth in my car, my in call volume gets dropped down to 50%. That's okay, because there would be too much noise coming from the car speakers, but when I disconnect my bluetooth, I expect my volume to be taken back up where it originally was. Eclair did not solve this, Froyo promised to solve it, but in any of the firmwares I've tried, have they actually done anything about it.
I previously had installed JPF and JPM with similar issues as listed above. By installing an American version I thought battery life would be greater, since it wouldn't have to be searching for 3G on frequencies of 3G not used in American countries. Although my battery life was better than JPF and JPM, my original firmware (streamlined with only actual useful apps and etc. - if you want to take a look at streamlining look for my post Streamlined Apps for 2.1 / 2.2) works better than any other firmware I have used (including Kyrillos and Apocalypse).
I miss the GPS button on the notification drop bar, and the Google groups in my contacts. But rather than that, I see no way where Froyo beats Eclair...
Mind you I don't use tethering, VPN, do not play heavy games (as I feel consoles and computers are there for that kind of thing - I just have light games installed like Air Control, Zuma, Labyrinth, etc.. to pass the time), turn off my wifi and bluetooth when not in use, leave my brightness to a minimum unless I can't see (then i turn brightness up), but have 3G running all the time, bluetooth whenever I am in the car, and Wi-Fi whenever I need to use the web and am near a known wi-fi antenna.
Battery Life (with indications above):
I5800LVIJG7 (2.1 Vivo) - 60 Hours
I5800LVIJG8 (2.1 TICO?) - 56 Hours
I5800DTLKDA (2.2 Free) - 35 Hours
JPM /JPF / Kyrillos / Apocalypse / Lestatious - 18 to 25 Hours
Hope that helps...
My advice.. stick with what you have...
Good morning, I tried other rom tb's but found this the best, my battery lasts around 2 days using wifi and 3G, I liked this rom, my GPS was fast after I turn on my GPS the following, the squeegee GPSFIXS with 1 minute and it fixed my location from GPS point of 100% with 3 to 18 meters of accuracy.
I would like to return to the rom VIVO because I believe that new skirt rom soon
I Flashed this rom, but the apks: gpssetup2 and fmradio aren't in the rom.
I copied fmradio.apk from I5800XXJPS and worked, but the gpssetup.apk didn't work. Because this my GPS don't work.
Anyone help me to solve my GPS problem in this rom?
hello, I would like to know if I'm alone on this issue, right now I'm running stock 2.3.6 on my i9100 and I have found an issue.
When Power saving mode is activated (the default one), if I open the camera app and turn off the screen for 1 minute, the phone dies and I have to reset it to make it work again.
Some friends told me that on ICS it doesn't happen so I was wondering if I got a faulty unit or this OS has this bug.
I would like some feedback from you guys with gingerbread onboard, thanks.
ellokomen said:
hello, I would like to know if I'm alone on this issue, right now I'm running stock 2.3.6 on my i9100 and I have found an issue.
When Power saving mode is activated (the default one), if I open the camera app and turn off the screen for 1 minute, the phone dies and I have to reset it to make it work again.
Some friends told me that on ICS it doesn't happen so I was wondering if I got a faulty unit or this OS has this bug.
I would like some feedback from you guys with gingerbread onboard, thanks.
Click to expand...
Click to collapse
This has never happened to me, but maybe try to turn off the device and take the battery out, leave it for a minute and reinsert the battery and restart. Then try to reproduce the problem.
Never happened to me or even heard of it
Sent from my GT-I9100
have you tried to see if this bug would occur without power saver mode on?,i never had this issue before nor heard of it
thanks everyone for your answers and concerns, the problem has been isolated:
It was a bug caused by a underclock that I did have that so far only occurs on the circumstances that I had on my phone.
When your phone turns off the screen, it will go to sleep mode or deep sleep mode depending on the running apps you have in that moment, these modes allow the CPU to low the frequencies (CPU Clock) in order to preserve battery life.
Comes to public interest that when using the camera app, the phone uses a high frequency clock to process photos and videos taken with the camera.
As because I did have a custom kernel that tweaks the CPU in order to gain more battery life, when battery saver option (which slow the max freq. clock of the CPU) was ON in my phone, the phone couldn't jump directly from sleep mode to max freq mode to keep camera app running and the CPU kept "slept"
If serves as interest of anyone, the kernel I was using was Siyah Kernel (don't remember which version, just check out the date this thread was posted and compare it with siyah kernel log to know by that date which was).
Uhh, I cannot post this in development as I am still a newby :-(
However:
Hello,
I came from Symbian (Nokia C7-00) and liked the phone very much. Everything worked the way it should. (I was especially interested in office functionality.)
Now I bought a Galaxy Note and I really love the hardware.
But I discovered that it uses much energy and it doesn't like to sleep as often as it could. (I already returned to Android GB, which gives a better experience, but there still is room for improvement.)
1. Sometimes even though the phone simply lies around and does nothing, the last app that I forgot to close is hindering the CPU from sleeping. Why? The is no need.
2. At night I am used to turn the phone into flight mode. However I found out that this isn't the best thing for Android. In the morning, when the email app goes to push phase, the phone leaves sleep mode and seems to excitedly wait for the flight mode to get switched off. This uses *quite* a bit of battery!
These things seem strange to me. My impression is that Android is not really optimised for cell phones. If the screen is off, there is no need for CPU time, doesn't it? There is nothing urgent to do; everything could be done slowly; no hurry.
I guess the battery could last *much* longer if this would be improved.
Greetings,
corcov
corcovo said:
Uhh, I cannot post this in development as I am still a newby :-(
However:
Click to expand...
Click to collapse
Which is handy, because this thread has nothing to do with development and thus saved you from some abuse!
Regards,
Dave
Sent from my GT-N7000 using Tapatalk 2
But I already know how to click the "thanks" button
corcovo said:
But I already know how to click the "thanks" button
Click to expand...
Click to collapse
Doesn't matter.
Development, if you did not create IT, then it does not belong in development. Remember that. Otherwise you will get flamed.
Android is a mobile OS, so of course it is optimised for smart phones - not ordinary cell phones. Android acts like a computer and, if you keep a computer running Crysis 2 for example, it would burn more power than a computer just playing some music off of iTunes.
In terms of improving your battery, check your brightness. You can download widgets to adjust the brightness right from the home screens. I use these to set my brightness to its lowest whilst at home (perfectly adequate for night and indoor use away from sunlight) and turn it onto automatic when I go outside. This has saved my a bunch of battery.
If you are running a stock Samsung ROM, turn on power saving mode. I always leave it on and, frankly, I have no idea as to what it actually does. I haven't noticed a performance drop in the slightest, but if it saves a bit of battery it is worth it. Also, you could try Juice Defender or some other battery saving apps which work for some people - others not.
Finally, ensure you haven't left GPS, Bluetooth or WiFi on when not needed. Try downloading CPU Spy to check your phone deep sleeps, yet mine even without it ever deep sleeping gets around 16 hours of battery life which is still the best I have ever gotten on a smart phone. Bettery Battery Stats can show you wake-locks (apps that are keeping your phone active) also.
Brad387 said:
Android is a mobile OS, so of course it is optimised for smart phones - not ordinary cell phones.
Click to expand...
Click to collapse
I see. Well it might be a nice feature if one could add an "now be a cell phone"-option for energy enhancement, which means: if screen if off, sleep.
c.
corcovo said:
1. Sometimes even though the phone simply lies around and does nothing, the last app that I forgot to close is hindering the CPU from sleeping. Why? The is no need.
Click to expand...
Click to collapse
There are some legitimate needs for keeping the CPU from sleeping for a short period of time - such as finishing a sync operation (otherwise, the radio power spent beginning the sync is wasted). Unfortunately, some poorly written applications (Facebook for example) abuse the wakelock mechanisms and hold wakelocks when it is not justified.
2. At night I am used to turn the phone into flight mode. However I found out that this isn't the best thing for Android. In the morning, when the email app goes to push phase, the phone leaves sleep mode and seems to excitedly wait for the flight mode to get switched off. This uses *quite* a bit of battery!
Click to expand...
Click to collapse
This is not something I have ever encountered myself. "push" relies on the server to trigger something - in airplane mode, this trigger can't happen.
These things seem strange to me. My impression is that Android is not really optimised for cell phones. If the screen is off, there is no need for CPU time, doesn't it? There is nothing urgent to do; everything could be done slowly; no hurry.
I guess the battery could last *much* longer if this would be improved.
Greetings,
corcov
Click to expand...
Click to collapse
Android is well optimized for cell phones - However, it assumes that third-party applications follow Google's recommendations for power management. Unfortunately, many of them do not. The number of IM applications which choose to use their own proprietary and poorly optimized network protocols (such as Skype, it's atrocious) as opposed to Google C2DM (optimized and efficient) is astonishing.
An interesting note was that I believe much of the focus at Google I/O was on reminding app developers that they need to play nice with the system and other apps.
There are some cases where there are device-specific nonoptimalities. Compared to most Nexus devices, Exynos devices have an absurdly long time to resume from wake (1000 milliseconds), and during that resume cycle CPU frequency is locked to 800 MHz and cpuidle is disabled. This is one of the #1 causes of power drain on our device. This is also exclusively a Samsung kernel/hardware architecture problem that does not affect the Nexus S (similar CPU, but completely different modem interface) or the Galaxy Nexus (different CPU/modem interface).
In the case of our device, the modem is hung off of the CPU on a USB bus - this makes for very long resume times.
Here are obvious reasons the CPU should occasionally turn on when the screen is off:
1) MP3 playback in the background
2) Handling of background syncs - e.g. when an email or Google Talk IM comes in, wake the CPU, handle it, and pop a notification sound, then go back to sleep. Normally, this means the CPU sleeps while waiting for an interrupt from the WLAN chipset or the cellular radio. Unfortunately, some apps drive incoming data to the device far too frequently. (See my above rant about Skype's network protocols being crap compared to Google's C2DM protocol.)
3) Handling of scheduled wakeups (alarms, calendar events, etc) - these are rare and almost never consume power
Most power drain is from item 2, with third-party apps frequently behaving extremely poorly compared to Google's own application suite and sync protocols.
Now this an extensive answer which is very informative and helpful for me since insights are always soothing. Love it. Thanks!
not much to add after Entropy, but if you feel the need to get some control over battery usage you could try betterbatterystats app (and the thread) to identify battery eaters, besides that, there are few apps to check what is going on with your system when it sleeps:
- CPU Spy to show cpu states time
- Autorun Manager or Autostarts to disable triggers causing apps like FB to run without reason (those which you will find with betterbatterystats)
- Battery Monitor Widget, to check battery current consumption (mA) - this app is generally not recommended, because Note's hardware does not report the actual current, so the readings are highly estimated and because when poorly configured it can drain your battery faster, BUT otoh with refresh rate set at 5 minutes or more, it can give you some approximate orientation on how much battery you lose (better than counting %/hour by yourself) at negligible battery usage
- also, if you feel the need to disable net and sync during night, you could automate it using "lama", which is free, and in my experience does not eat much battery by itself
- and last but not least, avoid taskillers, those apps may have adverse effect, i.e. self restarting apps (by the triggers mentioned above), will get killed then restarted and so on and so on, leading to much higher battery drain