ICS RUU inital observations - HTC Vivid, Raider, Velocity

Battery life is excellent.About 40% remaining at the end of the day instead of 10%.
When using the keyboard sometimes they keys vibrate loudly and sometimes only gently.
Certain apps are a little slower eg. task manager can take a full 4 seconds to load the running tasks. Maybe this is one of the reasons for the good battery life? ie. stuff which was running in the background before no longer is?

I've noticed the key glitch(?) Too. I was trying to figure out what I'm doing to cause that, but glad to see its not only me. As for battery, it really hasn't done much for my battery, but I think that's just a battery calibration issue. As for the background processes, it's my understanding that they cut out a lot of the unneeded stuff as ICS is more processor intensive than gingerbread. I run system panel lite, and there's way fewer processes running in the background now than with gingerbread. One of those processes being carrier iq. One of my friends that does some dev work for the captivate was looking through the ota ruu and couldn't find any trace of ciq anywhere.
Sent from my HTC PH39100 using XDA

Yes I can confirm no CIQ.
The key glitch always catches me by surprise while typing a text or email. I am sure it will get sorted out with a subsequent release.

Turning off all vibrations on the keyboard and UI vibrations leaves me with at least 60% left at the end of the day, and I'm a power user! It seems that the motor used for the Vivid is pretty power hungry..

Related

How to have a long abttery life?

Hello guys,
lately my Nexus One abttery consumption gets more and more consumptive. I dunno why, I already reduced the home screen from 7 became 5 and reduce the widgets too. but the battery life now did't even reach one day.
I read that someone has their nexus one running 3 days with browsing and GPS n Sync ON.
any advice how to conserve battery life?
There are plenty of threads discussing that same question. Basically the answer is that there's no perfect formula. Experiment and see what you can achieve.
Personally I tend to turn off most of automatic syncing stuff, but it's not because of battery life, but rather because I want more control.
Also, if your mobile reception is constantly low, your battery life will be significantly shorter.
heres what i did to increase my battery life.
turn off wifi/bluetooth
i leave my screen brightness at 100% (i like my screen bright) and leave gps on since its only used when gps is required
download a battery saving kernal. im using intersectraven 925mv kernal. less power consumption=less battery used. its been shown that 925mv is the best voltage compared to 800mv/1000mv
download "Task Manager" from the market. use it to set all apps to "kill list" so that everything is killed when you put ur phone on lock/sleep. This app helped me save tons of battery. Power doesnt drain at all when your phone is idle and my phone is at constant 250+/- memory.
other then that my phone has all the widgets on the homescreen and battery is good
d0mo said:
download "Task Manager" from the market. use it to set all apps to "kill list" so that everything is killed when you put ur phone on lock/sleep. This app helped me save tons of battery. Power doesnt drain at all when your phone is idle and my phone is at constant 250+/- memory.
Click to expand...
Click to collapse
I don't suggest doing it, since it brings nothing good and no power saved. If you kill widgets that update themselves - you might as well not put them on the screen, since they do nothing. If you kill system services - you might as well uninstall the programs that run them, since they're not working. And for everything else - you're just wasting the CPU time required to kill and then relaunch programs, and the memory that can be used better.
d0mo said:
heres what i did to increase my battery life.
turn off wifi/bluetooth
i leave my screen brightness at 100% (i like my screen bright) and leave gps on since its only used when gps is required
download a battery saving kernal. im using intersectraven 925mv kernal. less power consumption=less battery used. its been shown that 925mv is the best voltage compared to 800mv/1000mv
download "Task Manager" from the market. use it to set all apps to "kill list" so that everything is killed when you put ur phone on lock/sleep. This app helped me save tons of battery. Power doesnt drain at all when your phone is idle and my phone is at constant 250+/- memory.
other then that my phone has all the widgets on the homescreen and battery is good
Click to expand...
Click to collapse
1+2 = Nonsense.
1 - Kernel
2 - Task Killers cause more problems then they help.
Battery life is simply a function of how much CPU time is being used, how much data is being transferred, and how much the screen is on. Poor reception is another thing to consider, in most cases it's one of the three things above. Of course there are other factors, like how much you're talking on the phone, etc, but it boils down to three major things.
CPU time generally is only a problem when using the phone, games, live wallpapers (particularly 3D ones), and sometimes bad processes or badly designed programs. You can evaluate all of this using System Panel in the market.
How much data is being transferred you can control directly by setting your sync settings, or if you want to isolate it completely, disable syncing on all apps and otherwise use the phone normally. If you have Facebook, Twitter, MySpace, GMail, IM (Gtalk/whatever others), Weather, etc all syncing, it's going to be a lot of random traffic. Setting the phone to EDGE-only will reduce some of the battery usage from this, but controlling the syncing itself IMO is a better option than using EDGE.
Screen of course is how much you are playing with the phone, and I think this is the one that most people have problems with. If you're messing with the phone all day long, yes, it's going to "eat battery", and it's going to be caused from all three things above. CPU from you doing stuff, probably network traffic from you doing stuff, and the power to drive the screen. Some people suggest using black themes or backgrounds. Yes, AMOLED uses more power to drive a bright white than an LCD, and much more power to drive bright white vs black or dark, but think about how much you're staring at the background.. Only on the launcher. Do you stare at the launcher all day? But perhaps if you're reading a book for an extended period it's worth it to set it to white on black, vs black on white. Sometimes you can't control this, such as the browser is (generally) a white background.
I'm no expert, but god I'm tired of hearing nonsense around everything "eating battery".
I see, thanks 4 d advice you all
maybe the good way out is the Kernel flashing.
any recommendation maybe? which kernel are the best?
I don't want to downgrade my 1GHz clock though...
and URL is appreciated

[Q] Phone Signal and Battery Drain -- is there a correlation?

Hello Everyone,
I am new to the forum, but not totally new to rooting and flashing ROMs. I have a MT3G (second android phone to come to the market...yes I'm old school ), rooted and flashed CM7-Gingerbread 2.3.3 and it's working very well.
I also managed to buy a NookColor, immediately rooted it and flashed phiremod nook v5.1. and everything is very good. My Quadrant Score is 1485
However, what I've noticed is that if I compare the battery usage on mytouch 3g vs the nookcolor I see something interesting and I think it might have to do with the overall battery drain I've noticed on the nook....I'm hoping someone here can shed some light.
When I go to my settings > about tablet > battery use, I can see a graph on the top. If I click it, it shows a nice relationship between time (x-axis), battery % (y-axis) and underneath it are 5 variables (Phone Signal, Wi-fi, Awake, Screen on, Charging). These variables are key because you can see what is really draining a battery.
See the two attached images. One is from mytouch 3g and the other is the nook. What you can see is that when my nook is sleep, it drains a lot faster than MT3G and in fact what you see is that the PHONE SIGNAL is constantly on, where when my MT3G is sleep, the PHONE SIGNAL IS NOT....
Is there a way to completely remove this 'phone signal'...I suspect we can get more battery life out of our nook if we can just remove this!!!
Thanks for reading.
easy to do if you have adb.. otherwise use terminal.
rename the following files in /system/app
Mms.apk
TelephonyProvider.apk
Phone.apk (phone will keep forceclosing.
reboot.
If you are not using adb, just force power off using the power button.
When it comes up, you will have much better battery life.
Yeah, I saw that posted somewhere, and I've done that. So does the phone signal still appear on yours after you renamed it?
I wonder if this procedure is enough.....
labrazil said:
Yeah, I saw that posted somewhere, and I've done that. So does the phone signal still appear on yours after you renamed it?
I wonder if this procedure is enough.....
Click to expand...
Click to collapse
Enough to remove Phone from being listed in Spare Parts? Yep. It won't change anything.
CM7 is really bad with the battery. It doesn't sleep properly. The phone or lack of phone has nothing to do with it. It doesn't have a cell radio after all ;-)
Apparently there is a bug and it crashes or something? when it sleeps. I read that the devs just disabled sleep until they can get it fixed. I think that will probably happen after video is all working.
It still easily lasts through the day with a fair bit of use though. I just charge every night instead of every third ;-)
ylixir said:
CM7 is really bad with the battery. It doesn't sleep properly. The phone or lack of phone has nothing to do with it. It doesn't have a cell radio after all ;-)
Apparently there is a bug and it crashes or something? when it sleeps. I read that the devs just disabled sleep until they can get it fixed. I think that will probably happen after video is all working.
It still easily lasts through the day with a fair bit of use though. I just charge every night instead of every third ;-)
Click to expand...
Click to collapse
Okay, so it's safe to assume that the devs are working on this for future ROMs/Kernals? I really like my nook even though I just got the wifi-xoom today.
There's already been a 20+ page thread on this, where comparitive testing found no actual diference in battery life by removing those functions. The result is a purely cosmetic change where the power consumed under "cell standby" is shifted to "phone idle" or something else, I forget exactly. Any perceived improvements in battery life are a placebo effect and/or simply the result of the variables in different day-to-day usage.
Removing them also causes Market problems with certain apps not showing up due to "incompatibility" with devices lacking those functions, which I suspect is why they are not removed in the first place.
The NC's "high" power drain on CM7 is because it's not allowed to actually sleep due too a kernal bug which prevents it from reliably waking up. This will get fixed eventually. Right now, "sleep" simply turns off the screen.

[Q] My phone keeps dying!

In the last week or so I have picked up my phone three times and it has been dead.
The power button doesn't turn it on again.
I have to take the battery out and then restart it.
I'm running a rooted 2.35 JVT.
I have nothing untoward running ...
Settings
Sense analogue clock
DRM content
Software update
SnsService
Google Play Store
Samsung keypad
Apart from Angry Birds, there's almost nothing else, and nothing new for months except Bad Piggies.
deanbilly said:
In the last week or so I have picked up my phone three times and it has been dead.
The power button doesn't turn it on again.
I have to take the battery out and then restart it.
I'm running a rooted 2.35 JVT.
I have nothing untoward running ...
Settings
Sense analogue clock
DRM content
Software update
SnsService
Google Play Store
Samsung keypad
Apart from Angry Birds, there's almost nothing else, and nothing new for months except Bad Piggies.
Click to expand...
Click to collapse
Could it be a dead battery?
otherwise, tried to wipe and (re)flash a rom?
The battery is fine, and the ROM has been there for well over a year with no problems.
Finding the root cause of battery drain...
deanbilly said:
In the last week or so I have picked up my phone three times and it has been dead.
Click to expand...
Click to collapse
There are a number of standard steps to run through to find the root cause of battery problems, assuming the drain is caused by the OS or apps and not actually due to a physically failing battery.
I have been tracking a few battery issues myself recently and this is what I have learned from doing some reading on XDA:
There are two free apps on the app market that are typically used to diagnose battery problems:
Better Battery Stats
CPU Spy
I would recommend installing both apps. The third place to look is in the battery details in the system settings...sorry I can't remember what they look like on Gingerbread because upgraded to Jelly Bean a couple months ago, though I do remember there was less information in the stock battery info on Gingerbread.
IF you are not, indeed dealing with a physically dead battery, then the root of your battery drain is most likely caused by a background process or app that is keeping the processor in a partially active state even though the screen is turned off and one would assume the phone should not be using any power.
Android OS will automatically change the running speed of the processor in the phone based on the demand of the system. If only a few background tasks are running and updating information the speed might be 200 or 400 Mhz. If the system is running full out servicing a graphic intensive game the processor will likely be running at the full 1000 MHz speed. The speed of the processor will directly effect the battery drain.
The expectation is that when we turn the display off (not power down, just put the phone to sleep) the processor should need fewer resources and slow down, tending towards a state known as "Deep Sleep". At this point the processor us using very minimal amounts of power. Any app or process that is active in the background will prevent the processor from getting to Deep Sleep. The CPU spy app will allow you to check how much time the phone runs at various speeds. Once you install it and run it, then reset the timers in the menu and turn your screen off for about 10 or 15 minutes. Then 'refresh' the timers. Normally, you should see most of the time accumulated in Deep Sleep. There are standard background tasks such as syncing with the cell tower, updating time, mail, checking alarms etc. That will engage the processor momentarily but they should be relatively short compared to the deep sleep time. In my case, an errand process was keeping my phone at 100Mhz constantly preventing deep sleep.
Once you know that something is keeping the phone awake in the background, you can use Better Battery Stats to narrow down which process or app it is the cause. This app allows you to track the individual processes that are consuming the most time and preventing 'wakelocks'. Wakelocks are essentially an app preventing the sleep state and are very well explained in this post: http://forum.xda-developers.com/showthread.php?t=1827676
The battery info in the system settings can also be used to give clues though again, I can't remember how much detail was included in Gingerbread..
If your problem only started happening recently, then it could be a new app that you installed recently, a feature or setting you changed recently or possibly a recent update to an app that was already installed. Try to think back at any recent events that could have triggered a change in the system.
Common problem apps I have read about are:
- Facebook - seems to be bad at using lots of background processor time. (Don't run this app but reading several posts shows its a processor hog)
- Google Apps that sync - Gmail, Chrome (syncs browser history, tabs etc.), Google location stats.
The wakelocks link goes into a great deal of detail and is hugely valuable in nailing your issue down.
Good Luck, let use know via a post if you find the root cause...
Sorry, maybe I wasn't clear about it being 'dead'.
The battery is 100% or thereabouts, no problems ever with the battery.
The phone looked as though it was turned off, but wouldn't turn on again with the power button.
I have to take the battery out and put it back again, then it starts on the button.
I've cleaned the contacts, and it still happened.
User error.
Sent from my GT-I9100 using xda app-developers app
To me, it sounds more like a rogue process messing up power managing or response, but it's hard to tell what it could actually be.
For instance, you might come a cross a game that leaves your phone locked in max cpu frequency, draining the battery without explanation.
If it was me, I'd re-flash the rom from Odin, perhaps with an sd card wipe too.
Sent from horseback.

Drastically Increase Battery Life -|- Tips and Tricks Everyone Should Know *4/26/13*

I've been revamping this thread for new devices for years hoping to share some of the love with newer users. Over the time I've been on android, I've learned a few simple things that can greatly assist in the battery life of our wonderful smartphones.
If you get anything out of the thread, please don't hesitate to rate it and drop me a thanks!
If you read the thread and like the tips, have a new one to suggest, or have a revision, please post it.
On a similar note, moderators, thanks for the sticky!
General Lithium Ion Battery Information - This link includes stuff about charging, including trickle charging aka SBC (Why NOT to use it, or at your own peril)
My tips for good battery life:
Tips for both Rooted and Non-Rooted users
1.Turn off all radios when not in use.
(Bluetooth, wifi, data, 4G/Wimax/LTE, NFC, etc) Use a widget like the default power widgets, Switchpro, or a similar app from the market. *Many rooted ROMs generally allows users to access these radios and other settings from the notification pulldown menu.* The radios of the phone draw power if on even if the user isn't actually utilizing the radio's functions. A radio searching for signal (if you are in a low-signal area) drains more than a radio with good signal, so again, turn 'em off when you aren't using 'em.
To manually turn off radios without a toggle, go to Settings>wireless & networks. This can be accessed from the notification pulldown and hitting the cog icon.
Wifi uses less battery than 3G, so use wifi when you can. Another important setting to note is more dependent on the user. If you live in an area without 4G LTE coverage (check here to see), then go into Settings>Mobile data>Network Mode and check CDMA Only. This will prevent your phone from unnecessarily searching for LTE coverage, which wastes a ton of battery life.
3. I love live wallpapers, and I’ve always been a fan of pixel zombies, but they are really only good for showing off due to their battery drain.
4. Set your screen timeout/brightness to something that fits you.
The screen is the highest drain of battery power on any smartphone. BY setting the timeout, you can prevent your phone from staying on when you don’t manually turn off the screen. Also, manually turn off your screen when you’re done with your phone.
Another huge tip is to turn on automatic brightness (it is enabled by default). This greatly reduces power consumption by constantly changing the brightness of your display, tailoring it to your needs.
Settings>Display, gestures & buttons>Sleep
I use 30 seconds.
4. Task killers used to be all the rage, but no longer.
Here is the ultimate, in depth, graphically assisted, explanation by the famous Fresh ROM's chef, Flipz. Shortly, in light of recent testing, really don’t do anything but force apps that the android OS needed to be open, and thus didn’t close, to re-open. So try not using them, unless for stuff like trying to figure out why your phone isn’t sleeping with system panel. You really won’t notice a performance difference, and the adverse effects you aren’t seeing will stop
+=+ A good alternative is the application SystemPanel Pro. It has a free version, but I highly reccomend purchasing the paid app. It basically monitors everything going on with your phone's usage both in real time an in terms of usage history. If your battery is draiging fast, it tells you what app was doing it, how much it was doing it, and allows you to stop it.
5. I'm sure you have all heard around that your phone isn't "sleeping".
This is referring to the phone's "awake" time, hence the name. When you go to Settings>Power>History. You can compare the lines from awake to screen on versus time on. "Time on battery" refers to the amount of time since the last reboot. The "awake time" is how long the screen has been active. The problem is, a lot of the time, due to the endless possibilities of inconsistencies between apps/ROMs/kernels/phones, the phone will not go to "sleep", drawing power proportionate to the screen being in use when it reality the phone is sitting idle.
If you compare these times and they are the same, or if you note the difference (turn off the screen for a minute, then re-check and they are the same), then your phone is not sleeping.
One solution is to reboot.
I recommend two apps to help monitor:System Panel and Better Battery Stats. These two apps (explained in their FAQ's and descriptions greatly aid in finding those rogues.
Usually, SystemPanel will show an app that has gone "rogue" and is keeping your phone awake.
-This is done by hitting menu>settings>monitoring enabled. Then after some time has passed, ht menu>monitoring>history>change tab to top apps, and see if anything is above, say, 2-4%.
Uninstall applications/reinstalling them slowly, checking after every install to see what is causing it is one tedious but surefire solution.
Lastly,
Follow these steps that I have discovered almost always work.
1. Reboot phone.
2. Instantly upon reboot, as soon as you gain control, open up some type of monitor/taskkiller
3. "kill all" tasks on startup; about 2 times in quick succession should do the trick.
4. Turn off the screen and leave it for about five minutes.
5. Check the up time v. awake time and see if they are the same.
6. If they are, repeat steps 1-5. If they are different, you are good.
6. Apps and Combinations to watch out for!
-Facebook- Tries to sync live feed all the time, HIGHLY recommend unchecking this box, as it creates a massive draw on data
-Skype- This app reportedly (I've seen it myself) likes to sync random data and open up the network for fun. Sign out of app when not in use to fix
-GTalk- This application keeps you constantly connected to all of our google contacts across of your accounts. I have several accounts that I must maintain, and by default the application had me signed in and maintaining a connection with all of them. Open GTalk, then hit each account and sign out to neutralize this puppy. Unless of course you want to stay signed in.
7. Manage your syncing.
This is a big one, and it differs from person to person. Go to Settings>Accounts and Sync, and take a look at what's going on there. Listed app titles means that there is an account syncing data. I, for example, have four email addresses, facebook, dropbox, box, weather, etc. That is bad. You should go through and turn off syncing for nasty apps you might not have known were accessing the internet, or limit the access of apps and services that you do want to allow.
The problem lies in the way this syncing is handled. Each app/service runs on its own schedule, making it particularly likely that your phone could almost always be establishing a data connection and trying to download data for your various apps. See step 2 regarding the app Juice Defender to handle this problem.
8. Vibrate/Haptic Settings
Vibration and haptic feedback eat up a surprising amount of battery. If you have the haptic feedback enabled, then every time you press anything your phone puts out some juice to make itself dance.
Settings>Sound>Vibrate on touch
Some apps have their own haptic feedback settings, and notifications are their own set entirely.
Tips for Rooted users:
1. Try out custom kernels.
By going to the Sprint HTC One Android Development section of the forums, you can see all of the different kernels being developed. These allow for all kinds of modifications like underclocking the CPU and undervolting, both of which save battery. To see how to use them, read the FAQ's in each thread's OPs.
Here is a great guide to custom kernel's by mroneeyedboh.
2. Use Rom Toolbox Pro, SetCPU, or some CPU clocking app in compliance with whatever your custom kernel allows.
This site will explain the basics of SetCPU: http://www.setcpu.com/
-Profiles from SetCPU should usually involve these for battery life optimization:
-Screen off at the minimum clock speed for both, with the max raised on level if sluggishness is apparent
-A temperature greater than “X”
-General power related profiles that lower cpu speed at lower battery levels
(Note that setcpu has fallen off of the radar, but clocking your cpu to levels that suit your needs is still viable, although many argue that the android system's core management should best be left alone. Read up for yourself and make an educated decision)
------------------------------------------------------------------------------------------------------
NOTES:
*Some apps or processes begin to run at startup and keep the phone awake. These apps are not detected by things like spare parts or system panel, unless sometimes represented in the "system" process, in which case its usage will be unusually high.
This shouldn't take more than three repeats, and if it does, you need to factory reset, and slowly add apps back to see what's causing the problem.
___----When it comes to people claiming 20 plus hours of moderate/heavy use out of their current setup or other ridiculous absurdities, consider my position: No matter what you do, the cellphone battery is the cellphone battery. You can tweak it and customize it with kernels, ROMs, and settings, but none of that will turn it into a car battery. The main problem (besides a false sense of pride) that leads to these reports is the misunderstanding of what the usage levels are, so here’s my best summary:
* *Light usage – Phone screen actually on for maybe 0-2 hours. Things like a few texts, some emails, 20 minutes web browsing, etc.
* *Moderate usage – You watched a few youtube videos or similar apps, sustained web browsing, hundreds of texts, some games. Hours range from about 2-5 of screen on
* *Heavy usage – LOTS of video watching and games, pictures or video recording, or some high def gaming/movie watching for at least an hour to an hour and a half in total, with lots of emails and texts, browsing, and other app shenanigans. 5+ hours
*I’m sure everyone doesn't agree with all these numbers, but this is most likely a good average of what powerusers think. All specific hourage may vary due to differences in phones, batteries, ROMs, and kernels… Which also means that most battery comparisons are pointless; it’s only what you can improve on that counts!
I’ll update this whenever I see good stuff, people remind me, or I remember/come across things I do.
Hope it helps everybody!
Hit the "THANKS" button if I help you!
Good thread, we need more informational threads like this.
Biofall said:
* *Heavy usage – LOTS of video watching and games, 3D pics or video, or some high def gaming/movie watching for at least an hour to an hour and a half in total, with lots of emails and texts, browsing, and other app shenanigans. 5+ hours
Click to expand...
Click to collapse
This isn't the Evo 3d forum Bio . Good to see another 3vo user around these parts haha.
Stickied for the time being
demo27vol1 said:
This isn't the Evo 3d forum Bio . Good to see another 3vo user around these parts haha.
Click to expand...
Click to collapse
Haha yep!
Nice catch though, there was a lot there to change.
Hello Biofall,
I was wondering how effective is the Snapdragon BatteryGuru app from qualcomm vs juice defender if you ever tried that app before? I have used juice defender with my EVO 3D but I didn't liked the that the app was turning off Wimax even tough my phone was charging while using it.
Not only are we fighting the screen. We are fighting the quad core processor. It seems to be very aggressive.
Sent from my HTCONE using Xparent Blue Tapatalk 2
Well done.
treIII said:
Not only are we fighting the screen. We are fighting the quad core processor. It seems to be very aggressive.
Sent from my HTCONE using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
It's aggressive when it feels the need to ramp up. When installing several apps, the damn thing actually gets hot to the point where I put it in the freezer. [edit: this is dumb according to the device's thermal protection] I know that the components shouldn't be reaching those temps....
I'm on the lookout for more info on explicit effects of the quad core on battery life and direct ways to combat it.
eXplicit815 said:
Well done.
Click to expand...
Click to collapse
Thanks! I've been scouring for empirical info for years and I owe a lot of thanks to other people.
Turn off Juice defender. In fact, uninstall it. You will see your battery life is actually improved.
Leave the quad core component alone. If the cores aren't being used, they're offline. Offline is essentially 0 power consumption. The only case I can see improving battery by disabling cores would be for games. Otherwise, its probably detrimental.
Felnarion said:
Turn off Juice defender. In fact, uninstall it. You will see your battery life is actually improved.
Leave the quad core component alone. If the cores aren't being used, they're offline. Offline is essentially 0 power consumption. The only case I can see improving battery by disabling cores would be for games. Otherwise, its probably detrimental.
Click to expand...
Click to collapse
Juice defender has a large multitude of components. If some parts use more power for you, then you should post which of them you believe they were, before and after, possibly with battery graph screenshots.
On the last quad-core device that I had used there was a problem where the cores would ramp up unnecessarily for small tasks, so there is certainly a possibility for improvement.
On an unrelated note, there are other things that I want to add to this thread, including screenshots, so if anyone has anything to add, just tell me.
What I don't get is that a lot people seem to believe they know better than HTC's engineers. Doing things like forcing off cores, how do you know that's really saving power? For all you know, the power loss of enabling an extra core for a small task is insignificant to ramping up an already active core to do the same thing.
Sure there are some things you can do to improve power usage (such as avoiding wakelocks) but if you start changing numbers for how internal software power functions work, you should have some damn good reasons why. Even a graph isn't going to be terribly accurate unless you can substantiate the gains across multiple tests. Many of the improvements people mention often have an impact of less than 1% over the course of an entire charge, and that's nearly impossible to even measure. The battery percentage indicator is only an estimation and not only varies between device, but even varies based on the temperature!
Vincent Law said:
What I don't get is that a lot people seem to believe they know better than HTC's engineers. Doing things like forcing off cores, how do you know that's really saving power? For all you know, the power loss of enabling an extra core for a small task is insignificant to ramping up an already active core to do the same thing.
Sure there are some things you can do to improve power usage (such as avoiding wakelocks) but if you start changing numbers for how internal software power functions work, you should have some damn good reasons why. Even a graph isn't going to be terribly accurate unless you can substantiate the gains across multiple tests. Many of the improvements people mention often have an impact of less than 1% over the course of an entire charge, and that's nearly impossible to even measure. The battery percentage indicator is only an estimation and not only varies between device, but even varies based on the temperature!
Click to expand...
Click to collapse
Sure man, sure. There are surely negatives associated with turning off, down, or generally altering core performance. However, taking the decisions that HTC engineers coupled with HTC software designers implemented for mass consumption as the best option for all users is foolish. The reason we have a development community revolves around that concept.
Several of the things I talk about have an impact in terms of hours the device can function without being plugged into an outlet, which has little to nothing to do with battery percent levels.
Sent from my HTC ONE using xda premium
Edited
Biofall said:
Sure man, sure. There are surely negatives associated with turning off, down, or generally altering core performance. However, taking the decisions that HTC engineers coupled with HTC software designers implemented for mass consumption as the best option for all users is foolish. The reason we have a development community revolves around that concept.
Several of the things I talk about have an impact in terms of hours the device can function without being plugged into an outlet, which has little to nothing to do with battery percent levels.
Click to expand...
Click to collapse
Battery percent or how long the device is on is still a hard comparison to make.
You could do the EXACT SAME THING on the phone twice, from full charge to dead, and you'd get a different length of time. Batteries aren't that consistent.
A couple things that bother me:
1. You stick the phone in the freezer because it gets warm. The phone already has thermal protections that keep it from overheating. The CPU can deal with far greater heat than you know (70C isn't even a problem). Anandtech was able to run it through the entire gauntlet of its tests (which are much harder on the device than just installing apps) without it ever triggering thermal protection. Most thermal protections exist solely for the battery's sake, which in itself can deal with 50C while charging, or even higher when not.
2. In almost all cases, it is better to let the CPU drive itself as fast and as hard as possible in order to finish tasks. Let it turn on all the cores and such. Because once it's done, it can go back into deep sleep, where everything is off. This is why almost all phones, not just HTC ones, are designed to do just that.
I agree with Felnarion's sentiment. Juice Defender is probably wasting more power just measuring your battery usage than it is helping you save.
Edited
Originally Posted by Biofall
Sure man, sure. There are surely negatives associated with turning off, down, or generally altering core performance. However, taking the decisions that HTC engineers coupled with HTC software designers implemented for mass consumption as the best option for all users is foolish. The reason we have a development community revolves around that concept.
Several of the things I talk about have an impact in terms of hours the device can function without being plugged into an outlet, which has little to nothing to do with battery percent levels.
Click to expand...
Click to collapse
Battery percent or how long the device is on is still a hard comparison to make.
You could do the EXACT SAME THING on the phone twice, from full charge to dead, and you'd get a different length of time. Batteries aren't that consistent.
A couple things that bother me:
1. You stick the phone in the freezer because it gets warm. The phone already has thermal protections that keep it from overheating. The CPU can deal with far greater heat than you know (70C isn't even a problem). Anandtech was able to run it through the entire gauntlet of its tests (which are much harder on the device than just installing apps) without it ever triggering thermal protection. Most thermal protections exist solely for the battery's sake, which in itself can deal with 50C while charging, or even higher when not.
2. In almost all cases, it is better to let the CPU drive itself as fast and as hard as possible in order to finish tasks. Let it turn on all the cores and such. Because once it's done, it can go back into deep sleep, where everything is off. This is why almost all phones, not just HTC ones, are designed to do just that.
I agree with Felnarion's sentiment. Juice Defender is probably wasting more power just measuring your battery usage than it is helping you save.
Click to expand...
Click to collapse
You could do the same thing and get different results, but in reality strong trends in usage are reflected in battery life.
As for this the CPU discussion, all that I said was that I'd like to look at more in depth studies or core process handling. So it bothers me too.
In regards to JD, it won't be making it into the next revision of the thread, as I have noticed unnecessary draw. Honestly android implemented most of the vital operations into the OS, so it is mostly useless coupled with the other tips and just general awareness.
Finally, the xda app is acting up, sorry for the clutter.
Sent from my HTCONE using xda premium
Thanks for the write up. I went from being a little unimpressed by battery life to blown away. Biggest saver from stock is dropping all the SYNC stuff. Totally unnecessary IMO. If you aren't consuming the news and updates (you know actually in the app), you probably don't need it refreshing. Still baffles me this is the from-the-factory type setup.
Phone used to eat 5-10% of my charge per hour with light use and barely make it through my "day" (~15hr away from charger). Now, after 6hrs. since it's been off the charger, I'm still at 91%.
Kill LTE and go to CDMA only if you don't have it in your area either, or it's still rolling out. Seemed to help too.
EDIT: And I should note my scores are with never letting the Data Connection completely sleep, so I can still get emails as they come in which I find important.
---------- Post added at 01:44 PM ---------- Previous post was at 01:17 PM ----------
Here's another tip: Go into Google Talk and make sure to sign yourself out if you don't use/care for the service.
Lauski said:
Thanks for the write up. I went from being a little unimpressed by battery life to blown away. Biggest saver from stock is dropping all the SYNC stuff. Totally unnecessary IMO. If you aren't consuming the news and updates (you know actually in the app), you probably don't need it refreshing. Still baffles me this is the from-the-factory type setup.
Phone used to eat 5-10% of my charge per hour with light use and barely make it through my "day" (~15hr away from charger). Now, after 6hrs. since it's been off the charger, I'm still at 91%.
Kill LTE and go to CDMA only if you don't have it in your area either, or it's still rolling out. Seemed to help too.
EDIT: And I should note my scores are with never letting the Data Connection completely sleep, so I can still get emails as they come in which I find important.
---------- Post added at 01:44 PM ---------- Previous post was at 01:17 PM ----------
Here's another tip: Go into Google Talk and make sure to sign yourself out if you don't use/care for the service.
Click to expand...
Click to collapse
Solid tips man. Will update the OP. I always forget to change my mobile data to CDMA only. Also, I had three accounts signed into gtalk, which was unnecessary.
Biofall,
Nice thread.. Very very nice.
The battery issue --
When it comes to people claiming 20 plus hours of moderate/heavy use out of their current setup or other ridiculous absurdities
Click to expand...
Click to collapse
While I actually agree with what you say I do feel a bit different. I base mine on previous usage.
My days really fall into one of three areas. When you get old like me you will see your days are all about the same. :crying: My heavy use is going to be someone else light day.
For me I can judge based on different phones, kernels and roms. The 4g days I needed to have a charger at my desk. There was no way I could get through a whole day regardless of how many calls I made.
Now I am judging verse the LTE I had and and very surprised on how well its holding up even on
my
Click to expand...
Click to collapse
heavy days.
Have you had time to try this yet? http://forum.xda-developers.com/showthread.php?t=2230403
Not sure it works, like you said some of these apps just use more than they save. I am going to see what happens over the next few days and see if I can see differences.
Your Facebook and sync statement, man do those hit home! I still have a few phones at work that these guys don't get it.
Gtalk.. beh turns on when you flash a new rom.. People have to remember to go back and shut that sucker off!
Thanks for your post, I am going to show a few people this, maybe it will open their eyes.

What could cause EXTREME lag? (30-second delays)

My Moto X randomly started lagging heavily. It's unbearable.
It's not just a little bit here and there, the entire system is EXTREMELY LAGGY. It takes 30 seconds for the device to register a touch or perform an action.
I have root + stock ROM + gravitybox + very minimal third-party apps.
What the hell is going on?
Download an app that keeps track of CPU and RAM usage for each app. One of your apps may be keeping one or both of those at close to 100% usage and slowing it way down.
Sent from my XT1049 using Tapatalk
DonDizzurp said:
My Moto X randomly started lagging heavily. It's unbearable.
It's not just a little bit here and there, the entire system is EXTREMELY LAGGY. It takes 30 seconds for the device to register a touch or perform an action.
I have root + stock ROM + gravitybox + very minimal third-party apps.
What the hell is going on?
Click to expand...
Click to collapse
Many things could cause it. Backgrounded app crashing over and over (loop), malware (very unlikely), weird software conflicts, perhaps you froze an app that the system is trying to wake non stop, etc. Might be faster just to backup, RSDlite and restore. Titanium Backup and Ultimate Backup make it very easy with batch backups/restore. 2 key inputs backs up all your apps and 2 restores them lol. It's ridiculously easy
Also make sure you're not running battery saving mode, I imagine that caps your max clock speed to a lower value although it shouldn't cause THAT big of a performance hit.
Apps like BetterBattery stats or GSAM can also show you what's hammering your battery in the background and occupying your CPU cycles. I would take a quick peak at those tools first before I decide how to approach the situation.
What's happening is some app or software conflict is polling (sending commands to) your CPU non stop so when you interact with your phone each key press/swipe/action is put into what is now a long queue for the CPU to process it. Kind of like a lineup at a coffee shop in the morning, you wanna get in and out fast but they gotta serve the people in front of you first.
scorpion667 said:
Many things could cause it. Backgrounded app crashing over and over (loop), malware (very unlikely), weird software conflicts, perhaps you froze an app that the system is trying to wake non stop, etc. Might be faster just to backup, RSDlite and restore. Titanium Backup and Ultimate Backup make it very easy with batch backups/restore. 2 key inputs backs up all your apps and 2 restores them lol. It's ridiculously easy
Also make sure you're not running battery saving mode, I imagine that caps your max clock speed to a lower value although it shouldn't cause THAT big of a performance hit.
Apps like BetterBattery stats or GSAM can also show you what's hammering your battery in the background and occupying your CPU cycles. I would take a quick peak at those tools first before I decide how to approach the situation.
What's happening is some app or software conflict is polling (sending commands to) your CPU non stop so when you interact with your phone each key press/swipe/action is put into what is now a long queue for the CPU to process it. Kind of like a lineup at a coffee shop in the morning, you wanna get in and out fast but they gotta serve the people in front of you first.
Click to expand...
Click to collapse
I've frozen a bunch of apps and it's been fine for months.
I also turned on CPU updates from developer options to see if anything is bogging it down. I don't see anything in battery stats either.
I wiped cache and dalvik cache and now it's fine. I've never had something like cache build-up cause this much of a problem before. Weird.

Categories

Resources