Database Info

Looking for proven and tested higher capacity battery for HTC Desire

As above, anyone using higher capacity battery for their HTC Desire and it is tested and proven to last longer than the original batter? Can post the link to purchase the battery?
Thanks!

Before you buy another battery, have you read this thread about calibrating your battery?

And have you installed a rom that allows underclocking? It makes a massive difference.
I am now getting 20+ hours from my phone where as before underclocking I was getting 8 hours.
Same amount of usage, just underclocking when screen is off.

Erm.. I will go read about it, but because I want to retain as it is now, thats why I'm looking for an extended battery.
Sent from my Milestone using XDA App

bryant_16 said:
Erm.. I will go read about it, but because I want to retain as it is now, thats why I'm looking for an extended battery.
Click to expand...
Click to collapse
What kind of battery life do you currently get? Before (accidentally) calibrating my battery I was getting around 10-12 hours, now I'm getting around 36-42 hours.

I'm looking for one that can last me more than 1 day.

Lennyuk said:
And have you installed a rom that allows underclocking? It makes a massive difference.
I am now getting 20+ hours from my phone where as before underclocking I was getting 8 hours.
Same amount of usage, just underclocking when screen is off.
Click to expand...
Click to collapse
Hey buddy, which app do you use for underclocking? Cheers,

bryant_16 said:
I'm looking for one that can last me more than 1 day.
Click to expand...
Click to collapse
Well, I'm using the standard battery and have 26% remaining with "1d 10h" since unplugged (admittedly I haven't used the phone for that much in that time, just some internet usage, a couple of calls, but it's been constantly on WiFi or 3G to sync GMail).

Use SetCPU for underclocking, and use JuiceDefender to automatically turn off your data connection while the screen's off/locked.
It will still reconnect every 15 minutes to sync, and will remain connected as long as there's any continuing 3G traffic while the screen's off. Basically what it means is you're running one of the most power-consuming parts of your device only 1/15th of the time, which make a big difference. Text messages and voice calls come through instantly still - only things requiring a data connection like facebook, weather, twitter, etc will have any delay, and even then it'll only be 15 minutes at the most.
You can also try setting your phone to WCDMA-only, which means it won't be constantly trying to connect and maintain two radios simultaneously. GSM-only would be even better but depending on your carrier it might not work at all or might only work for voice.
With SetCPU try making a profile to automatically go into "powersave" mode when the screen's off, which will ensure the CPU never clocks up past its minimum speed during that time. It's still over 200 mhz, more than enough for anything you might want to do in the background. For normal operation, between 499 and 768 mhz as the maximum clock, depending on your preference, should be adequate and will save you a little bit of battery life as well all the time.
Also, download a widget to allow you to manually set screen brightness when you're indoors and the auto setting is useless. I have my screen brightness set to 15% while indoors and it's still plenty bright. I have the SLCD model, I don't know if that makes any difference.
My phone has been off the charger for 17 hours and 10 minutes. During that time, the screen was on for 2 hours and 29 minutes. I'm at 79% battery life with the standard battery.

Mugen 3200mah. Mine lasts a day with ease and heavy use.

paprkut said:
Mugen 3200mah. Mine lasts a day with ease and heavy use.
Click to expand...
Click to collapse
Yours able to charge it properly?

A small update to my previous post... I'm now at 32 hours, 38 minutes uptime, 4 hours 44 minutes awake time (screen on). Battery just reached 60 percent. Stock battery.
Remember when you made the choice to buy an Android, you were in effect saying you wanted to have a highly customizable miniature computer. Just like when you customize [insert your desktop OS of choice] to suit your taste, you need to configure your phone in order to get what you want out of it - namely, better battery life than with the standard settings.
HTC's goal with the Desire was to have a showpiece, it runs very fast and it looks good doing it. But they designed it with frequent charging in mind. Since most of us here, I imagine, would prefer to charge less often, we just need to configure the phone appropriately.
If you want a guaranteed solution, try this:
- Install NextSense rom (it's free, latest version right now is 5.3 AFAIK, I'm currently using 5.2 still)
- Install JuiceDefender - it's free on the market and its default settings are, for a change, very intelligent and effective.
- Install SetCPU - You can get it free on this forum. Set it to "interactive" mode with a bottom speed of 245 and a top speed of 806 to start with. The default is 998 at the top, but 200 mhz doesn't make a big difference in this case except to help battery life a bit. Once installed, add a profile for "screen off" which sets the phone to "powersave" mode. This will keep it running at the minimum clock any time you're not using it. Nothing running in the background while you're not even using the phone requires more than the minimum CPU speed.
- Install the Brightness Widget by Curvefish. It's free on the market. Put its widget on your desktop and keep your screen brightness at 25% while you're indoors. 15% is what I use, but 25% is one of the presets so it's a bit easier. I have an SLCD display so the brightness I get on auto might just be different from what OLED gets on auto, I don't know, but in any case for me it's way brighter than it needs to be.
- Set your screen timeout to no more than 2 minutes
- Make sure any apps that sync data do so in a reasonable interval. +/- 15 minutes won't ruin your day for most things.
- Under Wireless & Networks, set your phone's connection to WCDMA-only (3G-only). For many people this results in an increase to both signal quality and battery life, since it allows your phone to only run one radio at a time, making a significant difference. If it doesn't work for you, it's as simple as turning it back to the default setting.
- Disable haptic feedback and see if you mind the difference. Making all those little vibrations takes power too.
- Finally (obviously) don't run a live background, but you probably already know that.
Doing all of the above takes an hour or maybe two at most to set up and the difference in battery life is tremendous. It's simple to do, I worked out all of the above on my own and I've literally only had the phone for 4 days now I think, never touched a smartphone before in my life let alone an Android.
Give it a try, you have nothing to lose, and it will probably save you needing to buy a battery. Or, if you still buy a double-capacity battery, it'll mean you can run for like a week on a charge.
edit: also make sure to get the latest version of the radio driver, I don't have a frame of reference for comparison since I updated mine right away, but apparently it makes a fair bit of difference and probably gives you a more reliable cell signal in the process.
In case you think I'm exaggerating, here are some pics I just took.

What's the ideal settings for juice defender? Cos my phone is not rooted so I'm not going to use the SetCPU application.

What do you mean charge properly ??

Is it able to charge?

bryant_16 said:
What's the ideal settings for juice defender? Cos my phone is not rooted so I'm not going to use the SetCPU application.
Click to expand...
Click to collapse
"Ideal" settings are basically the way it's configured by default. You can't improve upon them much even by getting the "premium" upgrade unless your phone is rooted... but SetCPU is a better choice in that case anyway.
Just install it, hit "enable" after it's done auto-detecting your phone's capabilities, and you're done. It's really that simple.
Be sure to add it to your task killer exclusion list if you use one.

You saying the default option is for SetCPU or Juicedefender?
So just download the free juicedefender is good enough for me already since the pro version is more for rooted phones? (mine is not rooted)

Can somebody pls. post the link to SetCPU?

cyron_at said:
Can somebody pls. post the link to SetCPU?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=505419

bryant_16 said:
So just download the free juicedefender is good enough for me already since the pro version is more for rooted phones? (mine is not rooted)
Click to expand...
Click to collapse
Yes exactly. The pro version unlocks some more customization but ultimately won't add a whole lot to your battery life no matter how it's set up. I mean, beyond what the "regular" version does.

[Q] Auto Screen Brightness uses CPU (and effects performance)?

Is it true that setting the Screen Brightness to AUTO means more CPU-usage?
This might bot be significant, but interesting non-the-less
thx

benyben123 said:
Is it true that setting the Screen Brightness to AUTO means more CPU-usage?
This might bot be significant, but interesting non-the-less
thx
Click to expand...
Click to collapse
I would imagine it would use a little more CPU, but I leave it on all the time and I never notice a dip in performance.
Sent from my Bionix G2x

From what I've read the auto brightness only effects(negatively) your battery life. But I haven't tested so I don't know for sure. Mine isn't on because most of the time it can't decide between bright or not, which is really annoying

[Q] Brightness changes (even though auto-brightness is off)

Hi all
I am having a strange issue with my Nexus 5, so I was wondering if anyone else has experienced this:
Auto-brightness is off, brightness is set to maximum. Every now and then, as I am using the phone, the brightness would change. It would go slightly darker, and then sometimes after some time (minutes) slightly brighter again (back to maximum). When this happens, the actual brightness settings slider does not change, it's always saying 100%. I've tried to notice some pattern in the occurrences of this issue, but so far cannot identify any steps to reproduce it. It is easily spotted when the screen has a big area of a solid colour, e.g. on a web-page's white space. So most often I see it while scrolling a news website. Note that during these brightness changes, my environment's lightning does not change (auto-brightness is off anyway, so this should not matter).
I don't even know if this could be down to a software or hardware issue.
So, anyone had similar problems?
Thanks,
Nik

It's throttling (overheating)

Found a related thread
Thanks supersain08 for your answer. Now using this term, I found this thread:
http://forum.xda-developers.com/showthread.php?t=2516915

sovata said:
Thanks supersain08 for your answer. Now using this term, I found this thread:
http://forum.xda-developers.com/showthread.php?t=2516915
Click to expand...
Click to collapse
How can you use the brightness at maximum on this phone? This phone has one of the brightest displays I've ever seen. At 30% or so it's brighter than most phones on full.

Synyster06Gates said:
How can you use the brightness at maximum on this phone? This phone has one of the brightest displays I've ever seen. At 30% or so it's brighter than most phones on full.
Click to expand...
Click to collapse
Well I think that's beside the point, but let's say it's a personal preference.
And also it is possible that one would like to have a 100% brightness in light/sunny conditions, so then this issue could become relevant for anyone.

Last time I used 100% brightness on a phone screen was on the first days of my gnex.
Displays are in indoor situation much too bright on 100%, brigther doesn't look better all the time. I am going with Auto-Brightness (to have it at 100% in outdoor situations) but it is still to bright in low light situations. I have to wait for a customrom to adjust this like I did with the gnex.
Can not understand how people can use it at 100% all the time.

Why do you feel it's necessary to argue whether 100% brightness is useful or not?
That's not the point of the original question.

supersain08 said:
It's throttling (overheating)
Click to expand...
Click to collapse
I've been having the same issue; glad to know it isn't a defect, and that it's supposed to do that. Thanks for the information

Do any custom ROMs/Kernels allow you to have full control over screen brightness?

Regardless of ambient light, is there a way to set full brightness on the S6?
Running the stock ROM/kernel, even on full britghtness, the screen can go brighter unless the light sensor detects a high ambient light. I am wondering if its possible to change this.
Currently means PWM is still active on the screen even on full brightness. Same with the note 4 but this was not the case with previous samsung devices. PWM on full brightness is a deal breaker for me so I need to know now or this phone is being sold.

I think it's not really advisable to keep the screen on "extended brightness" mode for longer periods of time, because AMOLED panels wear out over time and this would be a definite way to make it wear out faster. Also it generates a lot of heat. There's a reason why Samsung implemented this adaptive mechanism.

mindfever91 said:
I think it's not really advisable to keep the screen on "extended brightness" mode for longer periods of time, because AMOLED panels wear out over time and this would be a definite way to make it wear out faster. Also it generates a lot of heat. There's a reason why Samsung implemented this adaptive mechanism.
Click to expand...
Click to collapse
Thankyou for replying but you did not answer the question at all. I specifically stated this is a deal breaker for me, and that it means that I have to sell this $1000 phone for great effort at a reduced price because of it.
If something is this important to me then I clearly do not care about wearing it out over time. My galaxy s1+s2 has been running on modified AMOLED gamma values for 6 years and they are still fine so I dont care if the displays wears out in 10 years time.
I cannot use the phone becuase the PWM effect means the screen flickers like crazy. It gives me a headache after 1 minute of use. The phone is worthless to me in this state. If i can increase the brightness to full hopefuly the PWM effect stops and I can use a screen filter to lower the brightness, so it will not wear our the display as well.
Lastly why was this moved to Help and Troubleshooting, it is a very important question about the phone. All previous SGS phones have been fine, this is a game changer for the worst.

Yuge said:
Thankyou for replying but you did not answer the question at all. I specifically stated this is a deal breaker for me, and that it means that I have to sell this $1000 phone for great effort at a reduced price because of it.
If something is this important to me then I clearly do not care about wearing it out over time. My galaxy s1+s2 has been running on modified AMOLED gamma values for 6 years and they are still fine so I dont care if the displays wears out in 10 years time.
I cannot use the phone becuase the PWM effect means the screen flickers like crazy. It gives me a headache after 1 minute of use. The phone is worthless to me in this state. If i can increase the brightness to full hopefuly the PWM effect stops and I can use a screen filter to lower the brightness, so it will not wear our the display as well.
Lastly why was this moved to Help and Troubleshooting, it is a very important question about the phone. All previous SGS phones have been fine, this is a game changer for the worst.
Click to expand...
Click to collapse
Not really sure where the issue is at, are you stating that when the brightness is reduced you can visibly see the phone flicker? I use an app called Velis Auto Brightness, it gives you way more customization to the brightness level. I like it because it mathematically calculates based off the luminescence (in the environment) of how bright the display should be to show accurate color perception, rather than focusing on batter life as much.
The extra brightness mode on the phone is just a high contrast feature, I haven't found a way to force it on as of yet. I know the phone goes up to 700 nits in sunlight, but the biggest difference is the contrast feature on it.

Brittany_Menton said:
Not really sure where the issue is at, are you stating that when the brightness is reduced you can visibly see the phone flicker? I use an app called Velis Auto Brightness, it gives you way more customization to the brightness level. I like it because it mathematically calculates based off the luminescence (in the environment) of how bright the display should be to show accurate color perception, rather than focusing on batter life as much.
The extra brightness mode on the phone is just a high contrast feature, I haven't found a way to force it on as of yet. I know the phone goes up to 700 nits in sunlight, but the biggest difference is the contrast feature on it.
Click to expand...
Click to collapse
I can see the phone flicker even when the brightness is on max setting, because it is not truly the the max brightness of the screen hardware. All the galaxy phones after the s2 did this, except when you turned them to max they stopped flickering. The s6 is the first device that does not allow you manual control over brightness, so I just want to know if custom roms have done this.
IF you don't know what I mean this is how they flicker.
https://www.youtube.com/watch?v=D2f0TZtpRA4
Also you are wrong that the extra brightness is just contrast, it increase the lumens as well as reduces or stops the flicker PWM effect. This is how phones using PWM reduce brightness, by making the screen flicker on and off, whereas in phones like the S2 the actual display dimmed. Some people can see this and are sensitive to it, some people are sensitive to to it but they don't know it, and some people dont see it and aren't affected by it.
But it doesn't look like anyone has made a Kernel that allows for full control over the AMOLED in the S6 so I plan on selling the phone soon.
Lastly I hope someone moves this to a more appropriate section where a DEV can see it, not the basic QA section like how do i change wallpaper.

Yuge said:
I can see the phone flicker even when the brightness is on max setting, because it is not truly the the max brightness of the screen hardware. All the galaxy phones after the s2 did this, except when you turned them to max they stopped flickering. The s6 is the first device that does not allow you manual control over brightness, so I just want to know if custom roms have done this.
IF you don't know what I mean this is how they flicker.
https://www.youtube.com/watch?v=D2f0TZtpRA4
Also you are wrong that the extra brightness is just contrast, it increase the lumens as well as reduces or stops the flicker PWM effect. This is how phones using PWM reduce brightness, by making the screen flicker on and off, whereas in phones like the S2 the actual display dimmed. Some people can see this and are sensitive to it, some people are sensitive to to it but they don't know it, and some people dont see it and aren't affected by it.
But it doesn't look like anyone has made a Kernel that allows for full control over the AMOLED in the S6 so I plan on selling the phone soon.
Lastly I hope someone moves this to a more appropriate section where a DEV can see it, not the basic QA section like how do i change wallpaper.
Click to expand...
Click to collapse
I really don't see the problem. All of the phones today flicker, that's how they show images on the screen. You're not going to find custom roms on this device because AOSP is not working on the phone yet, so if its a deal breaker go ahead and return it and get a new phone.

Yuge said:
I can see the phone flicker even when the brightness is on max setting, because it is not truly the the max brightness of the screen hardware. All the galaxy phones after the s2 did this, except when you turned them to max they stopped flickering. The s6 is the first device that does not allow you manual control over brightness, so I just want to know if custom roms have done this.
IF you don't know what I mean this is how they flicker.
https://www.youtube.com/watch?v=D2f0TZtpRA4
Also you are wrong that the extra brightness is just contrast, it increase the lumens as well as reduces or stops the flicker PWM effect. This is how phones using PWM reduce brightness, by making the screen flicker on and off, whereas in phones like the S2 the actual display dimmed. Some people can see this and are sensitive to it, some people are sensitive to to it but they don't know it, and some people dont see it and aren't affected by it.
But it doesn't look like anyone has made a Kernel that allows for full control over the AMOLED in the S6 so I plan on selling the phone soon.
Lastly I hope someone moves this to a more appropriate section where a DEV can see it, not the basic QA section like how do i change wallpaper.
Click to expand...
Click to collapse
Questions do not belong into Development. It will be clear once you read the respective section rules.. I'm afraid that you'll have to live with the thread in Q&A

All Browsers destroy my battery

I am currently on stock Android 12. I flashed the unlocked stock image (non-verizon) a few weeks back. With Android 11, Android 12, LineageOS, etc. every browser I have tried including Chrome, Brave, Via, etc. all drain the battery way faster than browsers did on my previous Moto G5 plus. i would say when I am surfing the net on my browser (usually just reading forums, no video), the battery drains about 1% every 5 minutes or less. I have tried 2.4Ghz wifi, LTE, etc. and data connection type doesn't seem to impact anything.
Is this normal for this phone? anything to do to reduce browser battery drain?

If you go into battery usage graph, is the browser the only app listed as using up the battery (and not the screen brightness, or another app that may be contributing to the heavy usage)

JohnC said:
If you go into battery usage graph, is the browser the only app listed as using up the battery (and not the screen brightness, or another app that may be contributing to the heavy usage)
Click to expand...
Click to collapse
correct. if I am using other apps the battery drain isn't near as severe. I keep the display setting "extra dim" enabled all the time and I keep it down as low as I can tolerate. I use a pitch black wallpaper use dark mode in browsers so they have mostly black background with white text.
Phone idle is the only other thing that seems to use a sizeable amount of battery according to the battery usage data in settings.

Sounds about right. Came from a Moto G7 Play (15 months back) and saw similar drain rates. All three devices have similar battery specs which plays into the units being used to assess drain. Is what it is.
FWIW - Opera

DB126 said:
Sounds about right. Came from a Moto G7 Play (15 months back) and saw similar drain rates. All three devices have similar battery specs which plays into the units being used to assess drain. Is what it is.
FWIW - Opera
Click to expand...
Click to collapse
Not gonna lie, it makes me want to go back to Motorola when this Pixel bites the dust.

badtlc said:
Not gonna lie, it makes me want to go back to Motorola when this Pixel bites the dust.
Click to expand...
Click to collapse
Many Moto's bring a nice package with unique tricks. Gotta do your homework on what features are most important when the time comes.

DB126 said:
Many Moto's bring a nice package with unique tricks. Gotta do your homework on what features are most important when the time comes.
Click to expand...
Click to collapse
I definitely did that. I only got the 4a because it was the perfect size and had a headphone jack. I assumed with a newer hardware set and similar sized battery compared to my old phone batter life "should" be better. Nope.

Na, it's more complicated. 4a sports more sensors, brighter/denser display, faster processors, etc. System and personal apps clearly play a role in longevity (behind screen brightness); you'd need to do a detail study to understand what's drawing when and why.
I use to fuss over such matters but find the device lasts a full day for my use case which is all that really matters. Charges up quick from a modest size battery pack when camping/traveling. Just like past Motos.
Not sure who I'll partner with in the next dance. Love Pixel cameras (especially in challenging conditions) and routine updates. Miss some of Moto's innovations, like active display and actions. Needs to be close to AOSP; no Samsung UX butchery. In the end form factor will likely be the deciding factor once non-contenders are ruled out.

badtlc said:
I assumed with a newer hardware set and similar sized battery compared to my old phone batter life "should" be better.
Click to expand...
Click to collapse
I don't know what CPU you came from, but if the Moto only had "small" cores then of course it used less battery. "Big" cores use more power. They go faster too, but if you have a constant load, then they'll eat battery faster.
I don't know if there's a non-root way to disable the big cores, but I suspect you can do it with root (but don't know for sure).
Otherwise, you gotta get your browser to stop running JavaScript. If you're watching video you need to make sure the browser is offloading all the decoding to the hardware codecs rather than doing it on the CPU.
And if the screen is on, it might help to try and get it "more black" (eg. Use night mode) or turn down the brightness. The screen is often the primary user of power when a device is being used.

a1291762 said:
I don't know what CPU you came from, but if the Moto only had "small" cores then of course it used less battery. "Big" cores use more power. They go faster too, but if you have a constant load, then they'll eat battery faster.
I don't know if there's a non-root way to disable the big cores, but I suspect you can do it with root (but don't know for sure).
Otherwise, you gotta get your browser to stop running JavaScript. If you're watching video you need to make sure the browser is offloading all the decoding to the hardware codecs rather than doing it on the CPU.
And if the screen is on, it might help to try and get it "more black" (eg. Use night mode) or turn down the brightness. The screen is often the primary user of power when a device is being used.
Click to expand...
Click to collapse
Thanks for the suggestions. My power complaints are just limited to the browser so I dont think it is just the larger CPUs. I think my standby consumption issues are related to Stock Android as I am now running GrapheneOS and my standby power consumption now matches my old Moto G5 Plus.
As for browser usage consumption, I have tried everything but disabling Javascript. I will try that and see if it breaks anything I use regularly. Thanks for the idea.
tangent back to general power consumption, I typically disable just about everything behind the scenes as I can. I keep the theme on pitch black. I use the extra dim setting to keep screen brightness as low as I can tolerate. I use night mode in browser to keep as much black background as possible. I disable all tap-to-wake or sensor based features. When I was trying to run Android 12, I disabled all the smart services and removed all the google apps I could. I removed all permissions I could. I restricted all apps I could. I disabled adaptive settings, etc. There is a bunch of stuff running in the background on Android 12 and I just could not

Welcome to the future. Older phones had better battery life

Locklear308 said:
Welcome to the future. Older phones had better battery life
Click to expand...
Click to collapse
I dont think it is all the phone. GrapheneOS has 40% better standby battery usage than stock android 12. On graphene, it matches my old Moto G5 Plus. It is either lazy programmers with inefficient coding these days or it is google having the stock OS do waaaay too much by default with no way to disable it.
I'm trying to figure that out now.

badtlc said:
I dont think it is all the phone. GrapheneOS has 40% better standby battery usage than stock android 12. On graphene, it matches my old Moto G5 Plus. It is either lazy programmers with inefficient coding these days or it is google having the stock OS do waaaay too much by default with no way to disable it.
I'm trying to figure that out now.
Click to expand...
Click to collapse
I totally agree on the lazy thing. So many devs now days are so lazy. I develope QuickBase databases and constantly run into extremely poorly setup realms/apps. Just basic stuff. Lol