Related
Meaning, does the battery life take a dip when you overclock to 1.5ghz. Does it get any hotter? Is heat an issue at all on this thing? Also, any performance or battery changes from installing the tiamet kernel itself? I'm in the wifi xoom btw.
Strangely enough battery life seems to be about the same. Heat has not been an issue mainly due to having the dual core, however its something you always want to keep an eye on.
Battery life is affected most by the screen. Screen> Network connections > CPU > RAM
There was a thread that someone made a while back about the things that affected battery life the most. If I can find It ill send it your way. After seeing the charts I figured Id try changing some settings.
things I did:
1. Set my max cpu freq to 1.19 min to 488 same for all my cpu tunner profiles ( I wanted to have my phone running the same all the time)
2. Lower'd my screen settings. I didnt need a pocket flashlight EVERYTIME I unlocked my phone.
3. Turned off un needed network connections. Its not hard to turn them back on when you need them.
4. I then looked for things that were running but were not needed by anything ( google maps are used by a few apps so dont disable it haha) I used Uninstaller for root users to get rid of some things.
After all these steps my battery life went WAY up. I have been doing the same thing on my Xoom now and my batt lasts the same at 1.5 as it did at 1.
I still get VERY respectable battery life at 1.5ghz, I can easily get through the day with normal usage. Yesterday night in fact, I left the house with maybe 75% battery life, used my tablet quite a lot throughout the evening(left the house around 9, went to sleep around 1am) and used it all morning basically constantly from 7am to around noon and came home with 9% battery left.
No problems here either. Woke up around 8:30 yesterday and used it all day sometimes pretty heavy. Finally had to plug it in around 6:30. I'm home all day with a broken hip and femur, so I've been putting it through the paces. Running @ 1.5ghz with interactive gov.
Chris
+1 on 1.5GHz having little effect on battery life. I didn't have to change anything else, either.
thats all great to hear! I suppose ill start looking into rooting my wifi xoom tomorrow then. Thanks for the help!
Im very happy with the battery life on this thing. I expected 4 hours max after a few weeks of use/charges. I never thought that it would keep up with anything Apple, Lets face it.. Apple knows how to make stuff run forever. But I was plesently suprised. Xoom +1000
yeah, the battery is good, but i won't know any damage to the cpu when overclocked ?
I wouldn't worry about any CPU damage- too many people have reported success (and no reports of failure).
Anyone else notice with the tiamat kernel that their xoom becomes very unstable overclocked at 1.5 using setCPU? Mine was essentially a soft brick at 1.5 constant rebooting and never able get pass the unlock screen, I had to rewipe with bootloader. I can do 1.2 no problem but don't even want to try going higher.
All of our chips have variations, so the overclock isn't universally guaranteed. That being said, I've been using the Tiamat kernel @1.5GHz since it was released with no problems.
Should have stated that mine is the wifi model, but yea thanks for info.
Here was that post I was looking for on this stuff. http://forum.xda-developers.com/forumdisplay.php?f=946
Had my Desire S a couple of months now on o2 in the Uk and really like it ,impressed with the speed so was wondering,would rooting it really make it much better?
Mate is banging on about doing it , but want to weigh up the benefits and possible pitfalls (apart from obviously bricking it) and also the best way of going about it .
I had a friend who just bought it too! He is new to Android and he loves it already..
Anyway, it's really up to you understand if rooting your phone will be useful, if you are happy like this, you could wait until you will be more confident with Android, or until you will need an extra power (by overclock your CPU for example).
In general a rooted phone with a custom ROM is faster that a stock one, and it doesn't have all the bloadware that HTC put on it.
You will be able to update your radio to improve the signal (and maybe fix the famous issues with it), overlock your CPU, install apk that allows you to back up your system, clear cache, customize your android in the deep, and so on...
The downsides could be the lost of your warranty and a small possibility to brick your phone...
But again is entirely up to you, regarding myself, I rooted my phone as soon as I bought it last year, happy since then!
Yes, it's definitely worth it. You can get the impeccable sense 3.0, a blazing fast 1.7 Ghz processor, and a ton of customization. BUT, YOU MUST KNOW WHAT YOU'RE DOING ! If you mess with the wrong stuff,you can permanently brick your device. Also, flashing is a little complicated, so do it only if you're comfortable with hacking.
shrome99 said:
a blazing fast 1.7 Ghz processor
Click to expand...
Click to collapse
Wow, battery must me draining at incredible speed !
sadly though without the xtc clip i don't see much of a chance for rooting becoming available on the desire s.
I was fortunate to have a soff phone. Till now the advantage of root I have take is by installing market enabler which let's me download apps currently not available in my region. Secondly I was able to install titanium backup to back my whole phone.
Now I am looking into roms and how to go around it. I am a total android noob with this one bring my very first experience.
Sent from my HTC Desire S using Tapatalk
JackyJack said:
Wow, battery must me draining at incredible speed !
Click to expand...
Click to collapse
Yes, at 1.7 ghz , battery life is low. But, you dont always need 1.7 ghz. 1.5 ghz or even 1.2 ghz is much faster than stock.
Cheers for the advice but I suppose the point is rather moot until I get S-off
shrome99 said:
a blazing fast 1.7 Ghz processor, and a ton of customization. BUT, YOU MUST KNOW WHAT YOU'RE DOING !
Click to expand...
Click to collapse
As i had to return my Desire (the old one) due to overheating and rebooting under heavy use (for example navigation) without having it overclocked, I surely don't want to force these problems with overclocking.
Does anyone use the Desire S for navigation on a regular base? I am really interested if those reboot problems still exist. I am sure overclocking isn't very good for the hardware on a long term.
If you can use the power only for benchmarks then its only about e-peen comparison How about a watercooling mod
Glibberman said:
As i had to return my Desire (the old one) due to overheating and rebooting under heavy use (for example navigation) without having it overclocked, I surely don't want to force these problems with overclocking.
Does anyone use the Desire S for navigation on a regular base? I am really interested if those reboot problems still exist. I am sure overclocking isn't very good for the hardware on a long term.
If you can use the power only for benchmarks then its only about e-peen comparison How about a watercooling mod
Click to expand...
Click to collapse
I've had it reboot once sure to overheating whilst using navigation. It was on a very hot day though. Several things you can do to stop it too.
Take out out any case.
Have your car air fans on low, and directed at the phone. Just get some air movement around it.
If you have root, underclock when using navigation.
If like me you are on Orange and SICK of the poor 3g service, buy an off line navigation app. I just got copilot and it's very good, and doesn't put half the strain on the phone. Did a two hour journey with it, and it only used 20% battery! That would have flattened it using google.
I think google maps has just updated to be more efficient in navigation and use less power, but haven't put it to the test though.
Sent from my HTC Desire S using XDA Premium App
overheating and rebooting
Glibberman said:
As i had to return my Desire (the old one) due to overheating and rebooting under heavy use (for example navigation) without having it overclocked, I surely don't want to force these problems with overclocking.
Does anyone use the Desire S for navigation on a regular base? I am really interested if those reboot problems still exist. I am sure overclocking isn't very good for the hardware on a long term.
If you can use the power only for benchmarks then its only about e-peen comparison How about a watercooling mod
Click to expand...
Click to collapse
Hello, I have been using the Desire S for just over two months by now and have used navigation extensively for long periods of time (5 to 10 hrs on a row). Here are my observations:
- first of all, the phone required a reboot just once during all this period and it had to do with some stupid automatic download/update from Google. I wanted to stop it but pressed the wrong (and many at the same time) buttons. The phone just resested itself from the blue but came back to life normalul afterwards;
- the reset had to do with Googlemaps but navigation was not on;
- otherwise I use IGO, works flawlessly;
- overheated, under direct sunlight beneath the windshield; solved the problem by positioning the unit next to the air/AC
- at night, the temperature (measured by Battery indicator pro,) never rose above 39 celsius so I say there aren't any overheating issues there.
I'm an Android virgin but i must say, yes.
OK, so I know there has been a lot of b*tching about the Tbolt battery life, especially if you are running Gingerbread and a Sense 2.1 or 3.0 ROM (I am running BAMF 3.0 R4.9). I just may have solved this issue when you can connect to a WiFi access point!
Using a program called Tasker, I have created specific profiles that actually help save my battery as well as do a lot of other things to make life easier. The learning curve is somewhat steep for non-Tech geeks, but it's not too difficult after you get the hang of it. (I think the only version of Tasker in the market is pay for use, but you can get a free trial from the Dev's website directly.)
On to how I can get a 22+ hour standard TBolt battery:
1st new profile:
-Called "WiFi"
-Context = WiFi Connected (Any SSID)
-Task = NET>WiFi Sleep>Never
2nd new profile:
-Called "Dim Screen"
-Context = Power Source Any, click "Invert" button (so when the phone is not charging).
-Task = Display>Display Brightness>Set to "20" and check "Immediate Effect" (you can certainly change it to something higher, but you may not get nearly the same battery life).
On WiFi, I can get almost 23 hours of battery. On 4G, I can get upwards of 8 hours, 3G I have yet to test.
Since LTE was just turned on near where I live, I noticed that my TBolt was making WiFi sleep while it sat in my pocket not in use, therefor switching to 4G/LTE and draining the battery. The brightness obviously helps when I am not plugged in no matter if I am 3G/4G/WiFi.
I have some other useful profiles setup. Like I have the phone screen go to Auto Brightness and into the Sense Dock Mode when the phone is charging. My favorite is the Car Dock Profile... when the phone goes into my Car Dock, the Bluetooth turns on, GPS goes on, and Google Music Starts.
I am a big fan of Tasker now... there are a lot of possibilities with the program!
WorldOfJohnboy said:
OK, so I know there has been a lot of b*tching about the Tbolt battery life, especially if you are running Gingerbread and a Sense 2.1 or 3.0 ROM (I am running BAMF 3.0 R4.9). I just may have solved this issue when you can connect to a WiFi access point!
Using a program called Tasker, I have created specific profiles that actually help save my battery as well as do a lot of other things to make life easier. The learning curve is somewhat steep for non-Tech geeks, but it's not too difficult after you get the hang of it. (I think the only version of Tasker in the market is pay for use, but you can get a free trial from the Dev's website directly.)
On to how I can get a 22+ hour standard TBolt battery:
1st new profile:
-Called "WiFi"
-Context = WiFi Connected (Any SSID)
-Task = NET>WiFi Sleep>Never
2nd new profile:
-Called "Dim Screen"
-Context = Power Source Any, click "Invert" button (so when the phone is not charging).
-Task = Display>Display Brightness>Set to "20" and check "Immediate Effect" (you can certainly change it to something higher, but you may not get nearly the same battery life).
On WiFi, I can get almost 23 hours of battery. On 4G, I can get upwards of 8 hours, 3G I have yet to test.
Since LTE was just turned on near where I live, I noticed that my TBolt was making WiFi sleep while it sat in my pocket not in use, therefor switching to 4G/LTE and draining the battery. The brightness obviously helps when I am not plugged in no matter if I am 3G/4G/WiFi.
I have some other useful profiles setup. Like I have the phone screen go to Auto Brightness and into the Sense Dock Mode when the phone is charging. My favorite is the Car Dock Profile... when the phone goes into my Car Dock, the Bluetooth turns on, GPS goes on, and Google Music Starts.
I am a big fan of Tasker now... there are a lot of possibilities with the program!
Click to expand...
Click to collapse
I'm gonna say you might want to try a MUCH more modern ROM. I'm having very little trouble eeking 18 hours out of mine under moderate use, and well over a day if I'm not messing with it much. It will typically consume around 1.7% per hour unused, LTE on.
WorldOfJohnboy said:
OK, so I know there has been a lot of b*tching about the Tbolt battery life, especially if you are running Gingerbread and a Sense 2.1 or 3.0 ROM (I am running BAMF 3.0 R4.9). I just may have solved this issue when you can connect to a WiFi access point!
Using a program called Tasker, I have created specific profiles that actually help save my battery as well as do a lot of other things to make life easier. The learning curve is somewhat steep for non-Tech geeks, but it's not too difficult after you get the hang of it. (I think the only version of Tasker in the market is pay for use, but you can get a free trial from the Dev's website directly.)
On to how I can get a 22+ hour standard TBolt battery:
1st new profile:
-Called "WiFi"
-Context = WiFi Connected (Any SSID)
-Task = NET>WiFi Sleep>Never
2nd new profile:
-Called "Dim Screen"
-Context = Power Source Any, click "Invert" button (so when the phone is not charging).
-Task = Display>Display Brightness>Set to "20" and check "Immediate Effect" (you can certainly change it to something higher, but you may not get nearly the same battery life).
On WiFi, I can get almost 23 hours of battery. On 4G, I can get upwards of 8 hours, 3G I have yet to test.
Since LTE was just turned on near where I live, I noticed that my TBolt was making WiFi sleep while it sat in my pocket not in use, therefor switching to 4G/LTE and draining the battery. The brightness obviously helps when I am not plugged in no matter if I am 3G/4G/WiFi.
I have some other useful profiles setup. Like I have the phone screen go to Auto Brightness and into the Sense Dock Mode when the phone is charging. My favorite is the Car Dock Profile... when the phone goes into my Car Dock, the Bluetooth turns on, GPS goes on, and Google Music Starts.
I am a big fan of Tasker now... there are a lot of possibilities with the program!
Click to expand...
Click to collapse
how do you get the GPS to enable? I've tried to set up my GPS to come when I open maps, navigation or anything that needs gps enable but I get "sorry that action is unavailable on this device."
Llama also does what Tasker does. And its free. I find that Llama works better too. I can get near 24 hours with everything stock.
loonatik78 said:
I'm gonna say you might want to try a MUCH more modern ROM. I'm having very little trouble eeking 18 hours out of mine under moderate use, and well over a day if I'm not messing with it much. It will typically consume around 1.7% per hour unused, LTE on.
Click to expand...
Click to collapse
Modern? The ROM I have is running Gingerbread and is full Sense 3.0 (which appears to be a big battery hog). When I was on a GB Sense 2.1 ROM from the same Dev, I was getting better battery. The only thing that may improve the battery any more on GB/Sense 3.0 would be a new and improved Kernel, though I think I am on one of the more stable ones.
warmonster said:
how do you get the GPS to enable? I've tried to set up my GPS to come when I open maps, navigation or anything that needs gps enable but I get "sorry that action is unavailable on this device."
Click to expand...
Click to collapse
You are right, my bad... it throws up a disclaimer that GPS enabling is not available on any 2.3 ROM because of the Pop-up. They suggest using Cyanogen (sp) if you want to use the feature on a 2.3 ROM.
andydumi said:
Llama also does what Tasker does. And its free. I find that Llama works better too. I can get near 24 hours with everything stock.
Click to expand...
Click to collapse
Potato, Patahto. I like Tasker and found it really granular once I started playing with it. I don't mind paying for an app that is well Developed and supported. (If you like Llama that much, you should use the donate version to "thank" the Dev team!) The 23hrs is an estimated capacity right now as Battery Left is still calibrating.
WorldOfJohnboy said:
Modern? The ROM I have is running Gingerbread and is full Sense 3.0 (which appears to be a big battery hog). When I was on a GB Sense 2.1 ROM from the same Dev, I was getting better battery. The only thing that may improve the battery any more on GB/Sense 3.0 would be a new and improved Kernel, though I think I am on one of the more stable ones.
Click to expand...
Click to collapse
I think he is refering to roms based off the 2.11 leak. battery life in that Ruu is much better than any other previous ruu. Any roms based off it will give you more life by default. The bamf 4.9 Rom is kinda old when your talking about custom roms and it isn't based on the 2.11 ruu.
Sent from my ADR6400L using xda premium
WorldOfJohnboy said:
Modern? The ROM I have is running Gingerbread and is full Sense 3.0 (which appears to be a big battery hog). When I was on a GB Sense 2.1 ROM from the same Dev, I was getting better battery. The only thing that may improve the battery any more on GB/Sense 3.0 would be a new and improved Kernel, though I think I am on one of the more stable ones.
Click to expand...
Click to collapse
You say BAMF 3.0 R4.9 is your ROM. This ROM is old, based upon the 2.01 GB leak (which is about 4 leaks ago), which was terribly flawed in many ways, and isn't even being developed by BAMF anymore. The newer kernels won't even work right on that ROM because aspects of the WiFi and camera have been changed in later leaks.
You're application of Tasker is probably one of the ONLY rational uses of such an app. Using it for such things as turning GPS on and off is pointless, and redundant, because Android already does that as long as you have GPS enabled. Having it enabled doesn't use any power unless you're using apps that abuse it, such as some of the traffic update apps that constantly update your position.
Power management apps aren't quite as useless as task killer apps, but for the purposes I see people use them for, they're not doing you many favors. I'm generally not a fan of these apps and I strongly recommend against task killers because the result of their use simply increases the amount of NAND reads the CPU must make, which is the most power intensive operation that CPU performs.
Newer ROMs, such as the RUU 2.10 and 2.11 based ROMs, are significantly better on battery life than the older ones, especially when used with the radios from the 1.70 OTA, 2.07 RUU, 2.10 RUU, and 2.11 RUU. I'd make the jump to a more modern ROM before I tried manipulating an older one to perform. Or, move up to a newer one and do the same thing and see what you get. In any event, there's good room for improvement.
I tried several ways to conserve battery and finally decided that it just isn't worth it to me to have to stop running game apps, to have to set the phone up a specific way, to carefully monitor what each app does etcetera. I went out Tuesday and bought a extended battery from a Verizon store. With discount I paid $25.00 for the battery and cover. I am now getting right around twenty five hours total battery life off one charge and I have watched videos, played games, played music, and did whatever else I could think of to kill that battery. I am ecstatic with it. Now when I am out overnight mountain climbing with the missus granted I will undoubtedly kill some apps. Wouldn't do to run into BigFoot, Smokey the Bear, and Jason Vorhies with a dead battery and no chocolate bars ( since she for some reason feels I should diet) now would it?
ps. I made sure it had antennaes on the cover. It has more than my original cover does. And the clerk had no clue why i was even asking about the antenaes on the cover
TDubKong said:
I tried several ways to conserve battery and finally decided that it just isn't worth it to me to have to stop running game apps, to have to set the phone up a specific way, to carefully monitor what each app does etcetera. I went out Tuesday and bought a extended battery from a Verizon store. With discount I paid $25.00 for the battery and cover. I am now getting right around twenty five hours total battery life off one charge and I have watched videos, played games, played music, and did whatever else I could think of to kill that battery. I am ecstatic with it. Now when I am out overnight mountain climbing with the missus granted I will undoubtedly kill some apps. Wouldn't do to run into BigFoot, Smokey the Bear, and Jason Vorhies with a dead battery and no chocolate bars ( since she for some reason feels I should diet) now would it?
ps. I made sure it had antennaes on the cover. It has more than my original cover does. And the clerk had no clue why i was even asking about the antenaes on the cover
Click to expand...
Click to collapse
Reps are pretty clueless, in general. They're sales people and that's about it. That's what cracks me up when I see these goofy "corporate memos" that supposedly when out to stores with stuff like RUU and radio version numbers on them. Like the geek behind the counter actually knows any of that???
loonatik78 said:
Reps are pretty clueless, in general. They're sales people and that's about it. That's what cracks me up when I see these goofy "corporate memos" that supposedly when out to stores with stuff like RUU and radio version numbers on them. Like the geek behind the counter actually knows any of that???
Click to expand...
Click to collapse
Yea tell me about it. At the Verizon kiosk in Costco I actually argued with the guy because he was spouting off about the Specs on AT&T phones being better than what were on the Thunderbolt. Saying how much better AT&T was and all this stuff. I listened for only a few minutes before I realized he was an imbecile. He was just throwing out things that made him sound like he knew what he was talking about. And yea you read that right. This brain fart of a human being was promoting AT&T from a Verizon kiosk
TDubKong said:
Yea tell me about it. At the Verizon kiosk in Costco I actually argued with the guy because he was spouting off about the Specs on AT&T phones being better than what were on the Thunderbolt. Saying how much better AT&T was and all this stuff. I listened for only a few minutes before I realized he was an imbecile. He was just throwing out things that made him sound like he knew what he was talking about. And yea you read that right. This brain fart of a human being was promoting AT&T from a Verizon kiosk
Click to expand...
Click to collapse
Further proving Einstein's point... The difference between genius and stupidity is that genius has it's limits.
loonatik78 said:
You say BAMF 3.0 R4.9 is your ROM. This ROM is old, based upon the 2.01 GB leak (which is about 4 leaks ago), which was terribly flawed in many ways, and isn't even being developed by BAMF anymore. The newer kernels won't even work right on that ROM because aspects of the WiFi and camera have been changed in later leaks.
Click to expand...
Click to collapse
If you can point me to a ROM that has full Sense 3.0 and the latest GB leak, please point me in that direction.
You're application of Tasker is probably one of the ONLY rational uses of such an app. Using it for such things as turning GPS on and off is pointless, and redundant, because Android already does that as long as you have GPS enabled. Having it enabled doesn't use any power unless you're using apps that abuse it, such as some of the traffic update apps that constantly update your position.
Click to expand...
Click to collapse
Considering I do use a bunch of Apps that can use GPS (Foursquare, Weather, and my Car Dock=Car Home) and I don't always need GPS on to do what I do in them, I choose to have GPS inactive as to not chew up more battery than is necessary.
Power management apps aren't quite as useless as task killer apps, but for the purposes I see people use them for, they're not doing you many favors. I'm generally not a fan of these apps and I strongly recommend against task killers because the result of their use simply increases the amount of NAND reads the CPU must make, which is the most power intensive operation that CPU performs.
Click to expand...
Click to collapse
I have never and will never use a task killer. Tasker is basically a way to create a 'macro' or series of them to help do things without having to click 18 different things on your phone. Apples to oranges.
Newer ROMs, such as the RUU 2.10 and 2.11 based ROMs, are significantly better on battery life than the older ones, especially when used with the radios from the 1.70 OTA, 2.07 RUU, 2.10 RUU, and 2.11 RUU. I'd make the jump to a more modern ROM before I tried manipulating an older one to perform. Or, move up to a newer one and do the same thing and see what you get. In any event, there's good room for improvement.
Click to expand...
Click to collapse
As I said, if there is a viable full Sense 3.0 ROM with the latest RUU out there, please let me know what it is. Until that happens, I will use Tasker to fix the flaws that exist in my current RUU/ROM.
loonatik78 said:
You say BAMF 3.0 R4.9 is your ROM. This ROM is old, based upon the 2.01 GB leak (which is about 4 leaks ago), which was terribly flawed in many ways, and isn't even being developed by BAMF anymore. The newer kernels won't even work right on that ROM because aspects of the WiFi and camera have been changed in later leaks.
Click to expand...
Click to collapse
Really...newer kernels don't work with BAMF 3.0 RC4.9??? That's funny because I'm running Ziggy's latest on BAMF 3.0 RC4.9 with working WiFi and camera, front and back.
Out of all the 3.0, 2.1/3.0 ROM's this is the only one that I have never missed a call because I could not answer the phone because of the end only call bug.
It might be an older ROM but it's still one of the best for this phone.
UberBAMF, Adrynalyne's side-project BAMF, both of the Gingeritis ROMs, Th3ory's ROMs, Synergy... Where the Ziggy kernel came from. Maybe I'm wrong and 4.9 uses the 2.07 base. I've used nothing but 2.07 and newer Chingy ROMs for the last 2 months as daily drivers and I've never once seen this "end call only" bug.
Ziggy's kernels aren't freely available so I don't consider it an available custom kernel.
loonatik78 said:
UberBAMF, Adrynalyne's side-project BAMF, both of the Gingeritis ROMs, Th3ory's ROMs, Synergy... Where the Ziggy kernel came from. Maybe I'm wrong and 4.9 uses the 2.07 base. I've used nothing but 2.07 and newer Chingy ROMs for the last 2 months as daily drivers and I've never once seen this "end call only" bug.
Ziggy's kernels aren't freely available so I don't consider it an available custom kernel.
Click to expand...
Click to collapse
Anyone that downloads Gingeritis, or Synergy has full access to Ziggy's kernels. I would call that freely available. Either which way they still work on BAMF 3.0 RC4.9.
As for the ROM's you listed not one of them are a full Sense 3.0 ROM like RC4.9.
If you have never had the end only call bug consider yourself lucky because there are theads on both themikmik and team BAMF about this bug.
Sent from my ADR6400L using XDA App
End-call only bug is real. In 2 months of running bamf (currently on uber 3), I've encountered it once. Others have been plagued with it. Basically, when someone calls, it only displays the large "end call" button.
Sent from my ADR6400L using XDA App
bp328i said:
Anyone that downloads Gingeritis, or Synergy has full access to Ziggy's kernels. I would call that freely available. Either which way they still work on BAMF 3.0 RC4.9.
As for the ROM's you listed not one of them are a full Sense 3.0 ROM like RC4.9.
If you have never had the end only call bug consider yourself lucky because there are theads on both themikmik and team BAMF about this bug.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
I hardly call Ziggy's kernel freely available by any stretch of the imagination. That's like saying iOS is free to anyone to use. Not really if you ONLY get it with this product or that! Ziggy also flouts the GPL like it's no big deal, so obtaining his source is nigh impossible. He's got one of the least available kernels that exists.
Sense 3.0 is eye candy. Like live wallpaper, its cool for a day, that's about it. And Rosie launcher is weak. I mean, if that's your thing, cool. It's your phone. But AOSP roms are far beyond BAMF, and far more stable. Shift B2 is the best rom I've run on my Bolt, hands down. With G+ loaded I get between 18-22 hours moderate use. Without G+ I can get a little over 28 hours. This is all 3G, as our towers havent been upgraded yet here in BFE. I understand the desire for battery life on stock battery. I pocket mine for 8 hours a day, so extended battery is unappealing. I underclock to 768 and my phone is still more responsive than it was with sense at 1.4.
MIT student proves by A + B that T-Mobile G2x has hardware issues related to overheating / shutdown / battery
http://www.lgforum.com/forum/boards/carriers/t-mobile/topics/g2x-g2x-gingerbread-2-dot-3-3-shutdown-requiring-battery-pull-due-to-overheat
Let's share this and be social.
Here are some other references for this same post.
#OccupyLg
LG: http://www.lgforum.com/forum/boards/carriers/t-mobile/topics/g2x-g2x-gingerbread-2-dot-3-3-shutdown-requiring-battery-pull-due-to-overheat
XDA-Developers: http://forum.xda-developers.com/showthread.php?t=1433445
T-Mobile: http://support.t-mobile.com/thread/16431
I would assume a hot reboot would work as well if you don't want to install an app killer
Sent from my LG-P999 using xda premium
If you are having issues you need to post more info. Rom? Kernel? Certain apps can cause issues. If you need help ask. Posting a rumor by a "MIT" kid is not overly impressive to me. Egg heads over think things sometimes.
jcbofkc said:
If you are having issues you need to post more info. Rom? Kernel? Certain apps can cause issues. If you need help ask. Posting a rumor by a "MIT" kid is not overly impressive to me. Egg heads over think things sometimes.
Click to expand...
Click to collapse
RG2X with Faux .47 and on .48 kernal. I am getting exactly what the IT guy described. Overheating during deep sleep while on charger. Non-OC'd with nothing major running in the background. Not even Setcpu or Juice Defender. I will assume this guy isn't on RG2X's rom nor on a MIUI rom. Maybe on Faux but I think it would be better to assume he is probably on 2.3.3/4 stock. Also he stated it was on two different phones that he did both of these tests we can assume it's not a rare thing. Noted it's not with every phone this happens but some for sure are getting dead phones upon wake. Because they die probably about half way during sleep by the time the person wakes up they only notice a dead phone that needs a battery pull. The heat is already gone so they wont notice the over heating. I actually felt my phone overheat on the charger so I can tell you what this guy is saying has some weight to it.
I shouldn't assume I should just read "We both a running stock lg g2x gingerbreads and have not tested it on any other roms"
psychoace said:
RG2X with Faux .47 and on .48 kernal. I am getting exactly what the IT guy described. Overheating during deep sleep while on charger. Non-OC'd with nothing major running in the background. Not even Setcpu or Juice Defender. I will assume this guy isn't on RG2X's rom nor on a MIUI rom. Maybe on Faux but I think it would be better to assume he is probably on 2.3.3/4 stock. Also he stated it was on two different phones that he did both of these tests we can assume it's not a rare thing. Noted it's not with every phone this happens but some for sure are getting dead phones upon wake. Because they die probably about half way during sleep by the time the person wakes up they only notice a dead phone that needs a battery pull. The heat is already gone so they wont notice the over heating. I actually felt my phone overheat on the charger so I can tell you what this guy is saying has some weight to it.
I shouldn't assume I should just read "We both a running stock lg g2x gingerbreads and have not tested it on any other roms"
Click to expand...
Click to collapse
If (big if) the overheating observed is due to heat from the battery charging leaching into the phone, wouldn't a quick and easy fix/test be a piece of aluminum foil between the battery and the phone?
Sent from my LG-P999 using Tapatalk
I have no problems at all. Running CM7 Latest Kang / Faux .48 CM battery. The last few versions of Faux's kernel fixed the SOD. I have never done an exchange. I got my G2X the 1st week it was out. I have never had any problems at all once the phone was rooted. Only thing I have problems with is the screen bleed. I am not OCed at all just UVed. When the phone screen is off setcpu sets the cpu at 389min 503 max. I have no overheating problems. So if you have overheating I would say that your phone is broke, you need to lower the OC if you are OCing, or you have done something wrong with the software.
Prod1702 said:
I have no problems at all. Running CM7 Latest Kang / Faux .48 CM battery. The last few versions of Faux's kernel fixed the SOD. I have never done an exchange. I got my G2X the 1st week it was out. I have never had any problems at all once the phone was rooted. Only thing I have problems with is the screen bleed. I am not OCed at all just UVed. When the phone screen is off setcpu sets the cpu at 389min 503 max. I have no overheating problems. So if you have overheating I would say that your phone is broke, you need to lower the OC if you are OCing, or you have done something wrong with the software.
Click to expand...
Click to collapse
Thanks for the report captain obvious.
I am glad your setup is fine. For those that are in stock configuration and non oc'ed yet experience these problems, they have probably come to realize that there is no support from tmobile or LG.
If the words "restart " or "shut down " during your tech support convo, you will be told to suck it up and wait for a software update. An update which will probably not come considering how many months has passed.
erikikaz said:
Thanks for the report captain obvious.
I am glad your setup is fine. For those that are in stock configuration and non oc'ed yet experience these problems, they have probably come to realize that there is no support from tmobile or LG.
If the words "restart " or "shut down " during your tech support convo, you will be told to suck it up and wait for a software update. An update which will probably not come considering how many months has passed.
Click to expand...
Click to collapse
FYI if it does it on all roms then its a hardware issue and software change wont fix it...
Sent from my LG-P999 using xda premium
I also had the dreaded sod at least once every couple of days.
However, after I installed eb kang with faux oc/uv profile with set cpu, I have had no problems since.
I guess its ymmv...
Sent from my LG-P999 using XDA App
No problems at all here with overheating or SOD. I have over 200 apps installed. And yes, I'm seriously still running stock Froyo.
The only problems I've had are sluggishness and freezing after disconnecting the USB (both computer and wall chargers.) I think it's an automatic sync thing, or possibly something reading my 10GB of music files on the SD.
Got mine the first week out too, but from Amazon.
gggirlgeek said:
No problems at all here with overheating or SOD. I have over 200 apps installed. And yes, I'm seriously still running stock Froyo.
The only problems I've had are sluggishness and freezing after disconnecting the USB (both computer and wall chargers.) I think it's an automatic sync thing, or possibly something reading my 10GB of music files on the SD.
Got mine the first week out too, but from Amazon.
Click to expand...
Click to collapse
I don't think anyone is saying this problem effects everyone. It's just with all the bad units out there with this problem, this is probably why it's happening. Right now I'm trying to run some profiles in setcpu to see if it improves my phones sleep. It's only been one day so I will see by the end of the week how this fares
Sent from my LG-P999 using xda premium
Cm7, morfic Trinity kernel, go launcher ex oc'ed to 1.4 ghz. Perfect! No issues!
Sent from my LG-P999 using xda premium
erikikaz said:
Thanks for the report captain obvious.
I am glad your setup is fine. For those that are in stock configuration and non oc'ed yet experience these problems, they have probably come to realize that there is no support from tmobile or LG.
If the words "restart " or "shut down " during your tech support convo, you will be told to suck it up and wait for a software update. An update which will probably not come considering how many months has passed.
Click to expand...
Click to collapse
Posts like this post is the reason why the devs hate the G2X. Most if not all problems most of the time are with android. If you are not using setcpu to control the cpu by setting up profiles for screen on and off. Then you are missing out on what root gives you access to. My phone might have the same problem yours have with overheating but i will never see if because my phone is UVed and runs at a lower CPU speed when the screen is off. If you want to use my setcpu profile look at my last post.
Prod1702 said:
Things like this post is the reason why the devs hate the G2X. Most if not all problems most of the time are with android. If you are not using setcpu to control the cpu by setting up profiles for screen on and off. Then you are missing out on what root gives you access to. My phone might have the same problem yours have with overheating but i will never see if because my phone is UVed and runs at a lower CPU speed when the screen is off. If you want to use my setcpu profile look at my last post.
Click to expand...
Click to collapse
The overheating is not a Android problem it's a LG doesn't know how to product test problem. All my other Android devices didn't have this problem. One did have an SOD problem that was fixed but I never had to deal with overheating. This is on LG not Google.
psychoace said:
The overheating is not a Android problem it's a LG doesn't know how to product test problem. All my other Android devices didn't have this problem. One did have an SOD problem that was fixed but I never had to deal with overheating. This is on LG not Google.
Click to expand...
Click to collapse
My friends amaze 4g has it friends Samsung fascinate has it galaxy s 4g and my old g1 and mt3g had it...
Sent from my LG-P999 using xda premium
mt3g said:
My friends amaze 4g has it friends Samsung fascinate has it galaxy s 4g and my old g1 and mt3g had it...
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I think the term overheating is thrown around too loosely here without more of a description. There's the type of overheating that causes our phones to shut off and stay off until the battery is pulled. There is also the type of overheating that occurs when you plug in an HDMI cable, which may or may not cause your device to die.
I'd assume those two types of overheating are the same, as they result in the same thing: dead device that won't turn on without a battery pull. And the phone gets hot as fsck. Hot as in you'd be scared to keep it in your pocket because (1) it'll burn your leg and (2) you are scared the battery will explode.
Those two types are overheating are different from your phone merely heating up upon use. I'm talking about charging the phone while navigating via GPS at full brightness or playing a graphically intense gaming. That magnitude of that heat is normal. And I'm guessing that's what all your devices have experienced.
And as all the devices get thinner, that battery's going to sit closer and closer to your hand, which equals more heat. And as the glass technology gets thinner (gorilla glass 2.0), your face will probably feel the heat to a greater degree as well.
---------- Post added at 04:18 PM ---------- Previous post was at 04:13 PM ----------
psychoace said:
The overheating is not a Android problem it's a LG doesn't know how to product test problem. All my other Android devices didn't have this problem. One did have an SOD problem that was fixed but I never had to deal with overheating. This is on LG not Google.
Click to expand...
Click to collapse
It's true, it's not android, it's LG.
And to all the people thinking that undervolting and underclocking your phone will fix everything, it won't. Android already underclocks the CPU when it's not in use. SetCPU does nothing in this instance. The only instance they'll see a difference is if they have some sort of rogue app that's maintaining a wake lock. You just can't beat terrible design (referring to the MIT guy's findings). Sometimes it'll work, sometimes you just lose.
LG majorly screwed up with this and I hope that their mobile efforts in the future fail for their lack of follow through.
I think I've avoided the charging SOD by accident....
I don't like the official LG charger since it uses a microUSB cable which I'd rather have as a spare on my computer..... so most of my charging is done with an old charger I just had laying around, which turns out to be 0.7a instead of 1.0a which the LG charger is, or on USB which goes through about 3 different hubs so probably has little power left by the time it gets to the phone.
Sure, charging is a bit slower, but that probably prevents some of the overheating.
Lesson: If you're having overheating during charging, dig through all your old chargers and find one with a lower output rating. Use the higher output ones only if you're in a hurry to charge.
Just wanted to say that this thread has been really helpful to me. Every time I've flashed a custom kernel, my phone has always, within the first 2 nights of installation, turned off in the middle of the night while on the charger. So I've always been stuck with the stock kernel. But then the suggestion to use SetCPU to lower the speed while the screen is turned off worked for me. So far no SOD and my phone has survived Faux's kernel and charging overnight without a battery pull and without overheating.
Now I can try out custom kernels and find all new ways to destroy my battery by doing things I'm not knowledgable enough to be doing!
lotherius said:
I think I've avoided the charging SOD by accident....
I don't like the official LG charger since it uses a microUSB cable which I'd rather have as a spare on my computer..... so most of my charging is done with an old charger I just had laying around, which turns out to be 0.7a instead of 1.0a which the LG charger is, or on USB which goes through about 3 different hubs so probably has little power left by the time it gets to the phone.
Sure, charging is a bit slower, but that probably prevents some of the overheating.
Lesson: If you're having overheating during charging, dig through all your old chargers and find one with a lower output rating. Use the higher output ones only if you're in a hurry to charge.
Click to expand...
Click to collapse
hmm.. I dont doubt you, but I think doing that would not be any different.
BECAUSE, the charger is not constantly charging at 1A rate. If you notice, the phones ramps down the input current after a certain percentage ~90%, and trickles it up to 100. Once at 100, the charging is supposed to be stopped. I've charged mine with my bluetooth 500ma charger, and I didnt see a difference in heat temps; only charging time took longer.
As far as heat, Lion batteries should be able to handle 1C charge (1 x charge capacity) with no problems in heat. That means even at 1.5A charge, it should be OK.
Regarding overclocking, undervolting and overheating. There is a variation of parameters across every silicon wafer; among the 25 or so wafers in a wafer lot; and from wafer lot to wafer lot. This is referred to as the "spread" and parts at the extremes are called "corner parts". Most parts should be in the middle of things, not all. With newer parts and small silicon process geometries, the margins are typically smaller - hopefully improving as the fab gets experience with the new process.
A hardware developer should get corner parts to check their PCBA layout and FW, to see if they have design margin. In the case of DDR (RAM), the voltage, circuit layout and DDR interface timing (from Tegra, in this case) should be checked across some tolerance and with the corner parts. "Fast" parts can draw more current during operation that nominal parts, possible heating up the voltage regulators nearby.
In a good hardware design, everything should work across part variation and the specified operating temperature for the system. When we start playing with the clocking frequency and voltages, there is the risk of FW crashing and HW flipping out. The symptoms can include system shut down (lost), resets, heating, bad effects on other systems (battery, voltage regulator circuits, etc.).
This is why some of us (like me) have little luck Set CPU and others can change it to extreme. What none of us know is how close to the design limits the G2X is - the system and the components like Tegra, the FW control. If due design diligence was not done, the sensitivity to part variation and our hacking is greater than normal.
Wondering if there's a difference in speed when using Bubby's root method versus the ACE hack kit. I rooted my phone about a year ago, my GF just did hers a couple weeks ago, and I could swear there's a difference between the two handsets, though they're both Inspire 4G's. Just curious to know if there's anything to my observation, or if it's a case of things always taking longer when you're waiting for them, rather than when you're the observer.
What specifically takes longer on one than the other.
Tx Redneck said:
What specifically takes longer on one than the other.
Click to expand...
Click to collapse
Oh, say for example things like opening and closing the app drawer, switching between apps, and general interface operations. I also find that my Favorites dialer widget tends to refresh a lot, particularly after a call - the icons will reload. That might be a different issue, but figured I'd mention it.
Sent from my Inspire 4G using Tapatalk
Probably speed difference due to what's installed on the phones. Number of apps. Type of SD card (maybe) things like that. It seems that the more I flash and change stuf on my pho.e the slower it gets. So I've started doing Full Wipes every few weeks. Even to my SD card taking everything off and only putting back what I actually use. It realmseems to help a lot. Also I've noticed that when a dev makes a full wipe zip for the Rom, that it works better when doing that along with the full wipe option you get with 4ext
Hope I helped
BillTheCat said:
Oh, say for example things like opening and closing the app drawer, switching between apps, and general interface operations. I also find that my Favorites dialer widget tends to refresh a lot, particularly after a call - the icons will reload. That might be a different issue, but figured I'd mention it.
Sent from my Inspire 4G using Tapatalk
Click to expand...
Click to collapse
That different issue may be associated, as it sounds like you may be suffering from a bit of lag. Have you tried running quadrant tests for comparison purposes? Not all Inspires will perform exactly the same. My wife's Inspire has always gotten a slightly better signal than mine, while my GPS has always performed better than hers. There will be variances with processor as well, although it should be minor.
Sent from my HTC Inspire 4G using Tapatalk
Let's not forget about ROMs. They all perform differently, too.
If you config them IDENTICALLY and yours is slower, then the proc/emmc may be inferior to what's in your wife's device. It's not unlike pc parts, you could have two kits of matching ram and one won't oc as well as the other. Same for processors too. Q6600 G0 SLACR will generally oc better than most other Q6600's.
Well, they're the same machine - Inspire 4G's, though I bought mine in March of last year from AT&T, she got hers in red from Target just about three months ago. The idea of variances between CPUs makes sense, though. Just figured I'd ask, since I hacked using Bubby's method and she used ACE, so I thought that might have made a difference.
BillTheCat said:
Well, they're the same machine - Inspire 4G's, though I bought mine in March of last year from AT&T, she got hers in red from Target just about three months ago. The idea of variances between CPUs makes sense, though. Just figured I'd ask, since I hacked using Bubby's method and she used ACE, so I thought that might have made a difference.
Click to expand...
Click to collapse
Also manufacturers make plenty of changes throughout a product's life. Small revision changes that may reduce cost, increase stability, boost performance, sometimes lower performance. As long as it is not running 'poorly' then small differences are expected just with the enormous list of variables. Just take the faster phone and give her the slower one!
BillTheCat said:
Oh, say for example things like opening and closing the app drawer, switching between apps, and general interface operations. I also find that my Favorites dialer widget tends to refresh a lot, particularly after a call - the icons will reload. That might be a different issue, but figured I'd mention it.
Sent from my Inspire 4G using Tapatalk
Click to expand...
Click to collapse
It could always be the rom. To compare better, you both need the same rom and version. With the app drawer, maybe you have the app drawer able to cache, and she doesn't? Just a guess.
Could be updated parts on her phone. I remember when I had my HTC Tilt when it came out then my sister had hers replaced a little bit before it was removed from the market and it was significantly faster than mine flashed with a ligh rom designed for speed.
Not exactly sure about this, but one would have to assume that battery charge levels could have an effect on the speed of the device and it's process speeds. the battery stays at nearly the same voltage during the charge cycle, but does begin to roll off as the battery power declines.
It could be said that decreased battery power would have a forced undervolt effect depending on it's level of charge, thus slowing down the device as it discharges.
Or....It's quite possible I'm full of crap, and have no Idea.
If you agree with the last sentence, please hit the thanks button out of pity....g
gregsarg said:
Not exactly sure about this, but one would have to assume that battery charge levels could have an effect on the speed of the device and it's process speeds. the battery stays at nearly the same voltage during the charge cycle, but does begin to roll off as the battery power declines.
It could be said that decreased battery power would have a forced undervolt effect depending on it's level of charge, thus slowing down the device as it discharges.
Or....It's quite possible I'm full of crap, and have no Idea.
If you agree with the last sentence, please hit the thanks button out of pity....g
Click to expand...
Click to collapse
There's a voltage regulator in there maintaining the supply to the phone. The voltage you read in any battery monitor app is the voltage of the battery. The regulator should be feeding about 3.3-3.5v from that source, so once the battery drops below those levels, things die off. You are right, as supply voltages drop the phone wouldnt function at it's full potential, there is just circuitry providing the proper levels regardless of the battery's voltage.