I am running Fresh 3.4.0.1 with the netarchy 4.1.9.1 cfs universal kernel. Other info is as follows:
Software number: 3.30.651.2
PRI: 1.77_003
PRL: 60662
Radio: 2.15.00.09.01
When using internet for any length of time under any signal strength conditions, 4G included where applicable, my Evo will reboot itself out of nowhere. This issue occurs most frequently when using wireless tethering. I have noticed the temperature reading on the wireless tether app in the high 30s before reboot, and the phone will just continue to reboot unless I remove the battery and let it sit for a while.
Could this be something with the kernel/another software related issue? Or should I flash it back to stock and utilize the warranty/insurance option? Any help would be greatly appreciated.
Bumping this, still having issue
captaincrunch said:
I am running Fresh 3.4.0.1 with the netarchy 4.1.9.1 cfs universal kernel. Other info is as follows:
Software number: 3.30.651.2
PRI: 1.77_003
PRL: 60662
Radio: 2.15.00.09.01
When using internet for any length of time under any signal strength conditions, 4G included where applicable, my Evo will reboot itself out of nowhere. This issue occurs most frequently when using wireless tethering. I have noticed the temperature reading on the wireless tether app in the high 30s before reboot, and the phone will just continue to reboot unless I remove the battery and let it sit for a while.
Could this be something with the kernel/another software related issue? Or should I flash it back to stock and utilize the warranty/insurance option? Any help would be greatly appreciated.
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
I wouldn't consider high 30's overheating at all. When I tether with 4g my evo gets to high 40s, if I have it charging, low 40s otherwise. Never had a reboot. I've read around here of people saying that some of nets kernels have caused reboots, but that's just what I've read, I've used nets with mo issues. I would suggest trying a different kernel ( not sure what to recommend, as I've never used Fresh Rom, so don't know what works well) just keep in mind that what works for one evo might be terrible on yours. They all react differently. So try a few out, see why works well. Always make sure to have a good nandroid backup before flashing, and always wipe davlik and cache prior to any kernel flashing you may try. Oh yea, some evos seem to have rebooting issues regardless of what Rom or kernel you use. My girlfriends reboots randomly, and hers isn't even rooted. Hopefully this helps you a little.
Is happening with me too, I used to use my evo a lot and never felt the phone before get hot even with slingbox for three hours but now I dont want to use it bc gets hot and reboots, I have tried most of the roms and kernels and the same. When I install a rom works fine for two days and start rebooting every hour until I flash another kernel and wipe cache, I tried stock ruu and the same.. . I am going to flash back the old radio a see if that helps..... or any idea?
update: I have tested this with the latest cyanogenmod, as well as damagecontrol and ava froyo. Multiple versions of wireless tether, as well. Stock kernels for each of those mods, respectively. The issue remains.
I believe I am going to un-root my Evo and take it to my local repair/service center. In the past, they replaced my rooted Palm Pre free of charge when it was having touchscreen issues and they were generally pleasant to deal with overall. I left it rooted, even!
My EVO just recently started rebooting when the battery temperature gets into the high 30C range. It doesn't take much to get it that high, just simple web browsing is enough. Depending on how hot it is, sometimes it will start to boot loop and require the battery to be taken out until it cools down before it can properly start again. I know in the past it would run perfectly fine up to and even over 50C. It has the problem on all the roms I've tried, even unrooted stock with no apps installed other than a battery temp meter. If I keep the temperature down below about 35C it never reboots ever, although doing that is kind of a pain because it can go above it with only 5 minutes of active use.
I suspect the problem could be the battery itself, I'm getting a third party replacement in the mail soon and I'll see if that helps. Otherwise I guess I'm at Sprint's mercy, kinda wish that I didn't take TEP off my account a month ago :/ . That and there's no corporate stores that do repairs nearby, so I have to deal with a auth. retailer store, ugh...
The worst thing is... I can't play Angry Birds anymore- that thing heats up the EVO fast :<
BTW my hardware version is 0003 and it's a launch day EVO for anyone who may be tracking these things.
has anyone found a fix for this? my evo heats up to mid 30's just from having the screen on, and i can play with it for about 30 mins before it starts a reboot loop and i have to pull the battery and let it cool down.
this has been going on since mid February, really annoying. switching kernals doesnt help, neither does switching roms.
currently running:
cm7 rc4, savagedzen 1.0.1 cfs nosbc
I'd try a different kernel. I had random reboots when I was using ziggy's kernel (sense). Disabled all the undervolting and other battery saving scripts... The issue continued. Switched to net's kernel and haven't had a reboot since. Because these are tweaked excessively, some phones work better with one kernel than another.
captaincrunch said:
update: I have tested this with the latest cyanogenmod, as well as damagecontrol and ava froyo. Multiple versions of wireless tether, as well. Stock kernels for each of those mods, respectively. The issue remains.
I believe I am going to un-root my Evo and take it to my local repair/service center. In the past, they replaced my rooted Palm Pre free of charge when it was having touchscreen issues and they were generally pleasant to deal with overall. I left it rooted, even!
Click to expand...
Click to collapse
There seems to be two separate reboot issues going on here. One is the heat reboot at about 38 degrees (which I have not experienced) and the other is the GPS/Phone combo reboot which may be hardware related since it's independent from rom or kernel. I had this happen a lot running fresh on my 002 phone and figured it was the rom, but I got a refurb 003 and it does the same thing stock
I've had this problem for about two months now, even though I have a launch-day Evo, hardware version 0003. When it first started happening, I had no idea what was causing it, though heat was my first guess, as the phone was getting hot. Then I installed the Clarus Battery widget on one of my homescreens so that I could monitor it. When the phone got to about 42-43°C is when it would reboot (and possibly bootloop). The more it happened, the lower the temperature threshold got, until it would start acting up at as low as 36°C.
After more investigation, I noticed that the phone would only reboot when it was using 3G. When I'm at home, I use my wi-fi, and though heavy usage would still cause the phone to get hot, it wouldn't reboot. Turn off the wi-fi and switch over to 3G, and poof! reboot.
I'm fairly convinced that the problem lies in the 3G radio. It's almost as if the heat at some point fouled a solder connection.
My device is rooted, I've used various radio baseband versions, ROMs, and kernels, and nothing made any difference. Expecting to return the phone to Sprint for a replacement, I unrooted and factory-reset the phone and still had the problem.
I took the phone to a Sprint store yesterday. After an hour of waiting, the tech told me that he factory-reset it, and installed and executed some sort of "stress test" application on the phone, and it passed with flying colors. It's some sort of graphic intensive application and to the best of my knowledge, doesn't use 3G - which I think is what the triggers the reboot. He gave it back to me, and the Market was auto-updating a few applications, which I canceled (leaving icons in the notification area). I opened the browser and after a minute or so, it reached 36°C and rebooted before his eyes. He tried to tell me that I had "lots of stuff running in the background" (i.e., the Market updates in the notification area) and that's why it was happening - because I'm "not using the phone correctly". I told him that I knew he was going to try to tell me that there was nothing wrong with my phone and push me out the front door as quickly as possible. To tell me that there's no problem with my phone and I'm using it incorrectly is completely outrageous and unacceptable. After "pulling rank" as a 12-year-long Sprint Premier customer that has never been late on a single payment, pays the $7 TEP every month, and has never returned a phone before, I made it quite clear that I would not be leaving the store without a new Evo in my hands. Begrudgingly, he finally gave me a new one.
Based upon other threads I've read on this subject and my own experience, getting a new phone is the only resolution to the problem.
Related
Well, ill start off by saying "Im james! "
I recently made the switch to android because i absolutely love the capabilities and the functionality. I got myself an Incredible. Rooted and and installed Redemptive revolution and got sucky battery life. Then yesterday it starts raining and gets really cloudy. I lose my 3g coverage about an hour into the storm. Im guessing this is normal? Well i decide to install Myn's two point two, with kinxklick's LV kernel in an attempt to get better battery life.
My current standing: Im running Myn's 2.2 with LV kernel and my 3G is still timing out and crappy. My brother's Dx gets Fair signal during the storm, should i be worried about my phone? Ive wiped several times and i still get like 60 kbps down while he gets above 400 kbps.
So my questions are:
1. Is there something wrong with my incredible? Or is the X's signal generally better then the HTC's?
2. What ROM and kernel combination would give me the best battery life?
Its at :
Android System: 70 %
Display: 16%
Cell Standby: 14%
During the time writing this, my 3G has dropped at least 6 times. Is it normally like this during cloudy rainy weather?
Thank you in advance, and i Love the site by the way!
jamespweb1503 said:
Well, ill start off by saying "Im james! "
I recently made the switch to android because i absolutely love the capabilities and the functionality. I got myself an Incredible. Rooted and and installed Redemptive revolution and got sucky battery life. Then yesterday it starts raining and gets really cloudy. I lose my 3g coverage about an hour into the storm. Im guessing this is normal? Well i decide to install Myn's two point two, with kinxklick's LV kernel in an attempt to get better battery life.
My current standing: Im running Myn's 2.2 with LV kernel and my 3G is still timing out and crappy. My brother's Dx gets Fair signal during the storm, should i be worried about my phone? Ive wiped several times and i still get like 60 kbps down while he gets above 400 kbps.
So my questions are:
1. Is there something wrong with my incredible? Or is the X's signal generally better then the HTC's?
2. What ROM and kernel combination would give me the best battery life?
Its at :
Android System: 70 %
Display: 16%
Cell Standby: 14%
During the time writing this, my 3G has dropped at least 6 times. Is it normally like this during cloudy rainy weather?
Thank you in advance, and i Love the site by the way!
Click to expand...
Click to collapse
Lou's #4 is kicking ass with both his and warm.... fast and smooth, battery seems to be killer also.
Your going to heat this 50 times, but this is in the wrong place.
Nothing is (probably) wrong with your phone and its best to try several combinations. I am using MIUI to great success.
Sent from my ADR6300 using XDA App
Oh, one more thing. The X has 2 antennas. The incredible has only one.
Sent from my ADR6300 using XDA App
0) This forum is for discussion of development issues, not "which is right for me" or "how to use" issues... this should probably be posted in Q&A or General.
However, I hate leaving a question unanswered, so:
1) Signal strength is not related to which ROM you are using, and rather which radio. Look in settings->about phone->Software Info->Baseband version. The 3 current radios are 2.15.00.07.28, 2.15.00.09.01, and 2.15.00.11.19. Depending on your location, one of these three is the version you should use. BE CAREFUL - FLASHING ROMS IS VERY SAFE, BUT AN ERROR FLASHING THE RADIO WILL BRICK YOUR PHONE.
You could also try *228 to update your roaming as well.
2) This is constantly debated. Typically, horrible battery life is the result of an app running constantly or keeping the phone from sleeping. How does your awake time compare to your up time? Personally, I find that CyanogenMod 6.1 with incredibleK's kernel #18 gives me best battery life... I usually charge it every night to be safe, but can comfortably go two days of moderate use without draining the battery.
igknighted said:
0) This forum is for discussion of development issues, not "which is right for me" or "how to use" issues... this should probably be posted in Q&A or General.
However, I hate leaving a question unanswered, so:
1) Signal strength is not related to which ROM you are using, and rather which radio. Look in settings->about phone->Software Info->Baseband version. The 3 current radios are 2.15.00.07.28, 2.15.00.09.01, and 2.15.00.11.19. Depending on your location, one of these three is the version you should use. BE CAREFUL - FLASHING ROMS IS VERY SAFE, BUT AN ERROR FLASHING THE RADIO WILL BRICK YOUR PHONE.
You could also try *228 to update your roaming as well.
2) This is constantly debated. Typically, horrible battery life is the result of an app running constantly or keeping the phone from sleeping. How does your awake time compare to your up time? Personally, I find that CyanogenMod 6.1 with incredibleK's kernel #18 gives me best battery life... I usually charge it every night to be safe, but can comfortably go two days of moderate use without draining the battery.
Click to expand...
Click to collapse
Sorry about the wrong forum, but im in the middle of flashing skyraider (3.5?) with King klicks #6. As for awake time and uptime, it used to be roughly the same. Give or take a few min. Ive speed tested on warm, and it still hasnt passed the 100 kbps mark Hows Cyanogen running for everything else?
Also, i cant get passed 1x on skyraider, it stays on "Turning on"
My radio is 2.15.00.07.38
Double check, my awake time is exactly the same as my up time.(Edit: Nevermind, i locked it and now the uptime is 2 min more than the awake time.)
jamespweb1503 said:
Sorry about the wrong forum, but im in the middle of flashing skyraider (3.5?) with King klicks #6. As for awake time and uptime, it used to be roughly the same. Give or take a few min. Ive speed tested on warm, and it still hasnt passed the 100 kbps mark Hows Cyanogen running for everything else?
Also, i cant get passed 1x on skyraider, it stays on "Turning on"
My radio is 2.15.00.07.38
Double check, my awake time is exactly the same as my up time.
Click to expand...
Click to collapse
That is a sign that either (a) you are literally using your phone 100% of the time, which will indeed suck batteries down very quickly, or (b) you have some app that is constantly asking for attention and wont let the phone sleep. By comparison, my uptime is 11+ hrs, and my awake time is about 3 hours. It's awake when I am using it, but it sleeps other times (can still receive calls/email/sms in this state). If your phone isn't sleeping when you're not using it, battery wil suffer.
EDIT: If you just rebooted, then it will of course be equal. You should check after you have been booted and running on battery (not plugged in) for a few hours.
igknighted said:
That is a sign that either (a) you are literally using your phone 100% of the time, which will indeed suck batteries down very quickly, or (b) you have some app that is constantly asking for attention and wont let the phone sleep. By comparison, my uptime is 11+ hrs, and my awake time is about 3 hours. It's awake when I am using it, but it sleeps other times (can still receive calls/email/sms in this state). If your phone isn't sleeping when you're not using it, battery wil suffer.
EDIT: If you just rebooted, then it will of course be equal. You should check after you have been booted and running on battery (not plugged in) for a few hours.
Click to expand...
Click to collapse
Yeah i figured, but battery seems to be normal now The thing thats killing me is not being able to get good internet! I cant download a small app over the mobile network because it lags out and just doesn't go! It shouldve gotten better since the sky is more clear, but it hasnt.
*228
*228 will update your towers and roaming capabilities definatly try this first
pdqauto01 said:
*228 will update your towers and roaming capabilities definatly try this first
Click to expand...
Click to collapse
No that doesnt work
Try a new radio. Legit, it will probably help a lot.
Research how to check an md5 sum before you actually flash it through hboot, but past that you're set. If the md5's don't match, redownload.
I suggest the 11.19 radio (The new EVO radio). 9.01 also worked well for me, but the EVO one works wonders. I also have a wannabEVO phone, so that might just be me.
Sent from my ADR6300 using XDA App
ever since I updated to 2.2, no matter what rom I'm using..performance has been so poor compared to 2.1. I wish I never updated. My battery runs out quick, temperature goes up to 100F even when idle and my phone hangs every time I turn on wifi. Hopefully I find out a solution soon, i've been flashing and uninstalling roms all day these past two days. I love the phone though don't get me wrong =\
That sounds quite odd.
Are you using an unmodified SBF, or are you using a release where the author/publisher has made a lot of changes? When having problems, it may be best to stick to one release and try to narrow down your problems, instead of trying many different releases and introducing new variables into the mix.
Are you overclocking your phone - perhaps it's causing the rise in temperature? Or are you running a lot of widgets? There may be some widgets that use the system too aggressively, causing too much strain/heat.
Hi! Did you do "wipe" before and after flashing?
That is very odd. I am on Froyo and performance has been phenomenal ever since the flash.
I agree with naenee, check the ROM you're flashing...
i flashed the UK 3.4.2-117 and right now using Pay's 2.1 rom. I remember that I did wipe data/cache before flashing and after flashing. IDK, im just not having problem's with this particular rom..it seems like it happens on all the other ones im trying. I get random freezes and especially when I toggle on wifi. I recently installed setVEL and will see if battery improves, this means i don't need milestone right? I'm also using setCPU.
I might try to flash 3.4.2_131-003 PL version. Will it cause any trouble and can I go back down to UK 3.4.2-117?
Seeing as it uses the same kernel, you should be able to do so...
bkuu said:
I might try to flash 3.4.2_131-003 PL version. Will it cause any trouble and can I go back down to UK 3.4.2-117?
Click to expand...
Click to collapse
I have been using the orange 2.2 for several days and no specific problem is noted.
well I reinstalled pays rom first and everything is working good. No more hang ups or freezes but I still can't get the battery to last as long.My phone is mostly idled, running on 2G, just one widget, and everything in settings turned down to the least minimal settings..im talking about battery saver, screen brightness all the way down..everything off! 6 hours in and im already on 70%. I can live with that but I'm using setVsel and I know it could do better. Anyone know another way I can make my battery last longer?
I'm running Pays latest rom based on the UK 3.4.2 and it runs great. I'm also using setvsel (as every defy user should) and optimized all my vsels ([email protected], [email protected], [email protected]) using stability test. I haven't had a 'normal' day of use yet, but with heavy use (installing apps, web browsing, flashing rom) I've gotten at least a full day (~15 hrs) out of a charge.
I recommend minimizing your vsels using setvsel, then judging your battery life. Check out the setvsel thread for more help.
Sent from my MB525 using XDA App
And remember this is a smart phone, some people report getting 2 to 3 days of use out of it. That's basically idle time tho. These new smart phones are just that, and use much more battery than the Dumbphone.
Dewman4life said:
And remember this is a smart phone, some people report getting 2 to 3 days of use out of it. That's basically idle time tho. These new smart phones are just that, and use much more battery than the Dumbphone.
Click to expand...
Click to collapse
Even if that's the case (and I dispute it, I use my phone a fair amount in the ~3 days the battery averages), it still doesn't explain why the OP's phone is dropping 30% in 6 hours while idling.
When I updated to froyo, my battery life went from about 15 hours of use to 21 hours between charges. So I'm thinking the op has an app doing the draining.
Sent from my MB525 using XDA App
Unfortunately, this is a characteristic of Android.... Ridiculously inconsistent in the battery department.
Wife's phone is on official froyo, has been amazing since updated (a few weeks ago) but since yesterday some weird reason it's been super glitchy and freezing up. Not sure why...haven't changed anything to it and she's only downloaded an app or two (such as pandora) in the last couple days...I was playing around with it trying to figure out what was up...can't figure it out. I went into titanium backup to freeze some apps thinking maybe some blur crap was freezing it up but TB froze up so I can't even get in there. Also, same as OP, the battery has been heating up really quick lately, especially when on wifi.
Not sure what's up here...but I'm hoping nothing serious! Will keep you all updated on this...we'll see if there is a trend going on here.
bkuu said:
ever since I updated to 2.2, no matter what rom I'm using..performance has been so poor compared to 2.1. I wish I never updated. My battery runs out quick, temperature goes up to 100F even when idle and my phone hangs every time I turn on wifi. Hopefully I find out a solution soon, i've been flashing and uninstalling roms all day these past two days. I love the phone though don't get me wrong =\
Click to expand...
Click to collapse
check your cpu usage... if it's constantly arround 99%, you may experience the "usb-plug/unplug"-bug.
try enabling usb debug and restart your phone.
hah2110 said:
Unfortunately, this is a characteristic of Android.... Ridiculously inconsistent in the battery department.
Click to expand...
Click to collapse
I would rather say it is a characteristic of people using android, to have widely different usage patterns, causing differences in how long a charge lasts for each.
Hi there. Have you tried to recalibrate the battery? There is an app on the marke called Battery Calibrator. From what I understand if you play with roms the battery can give you problems so it need to be calibrated again. I hope this can help.
For those interested... I'm having a problem, I don't know yet if it's a bug or a hardware defect.
My phones wastes A LOT of battery while it should be suspended.
I've tracked the problem to, apparently, Motorola's SIM driver. From what I've discovered so far, the SIM isn't accepting the suspend state and therefore the "suspend" process uses too much CPU time... all of this when the phone is, supposedly, saving battery.
As I can't get a motorola engineer involved, I can't say for sure if this is the true cause... but it's the closer I've got to a diagnostic, so far.
Your problem might or not be related to this, but if you're interested about what I've found or what my kernel log looks like so you can compare with your own problem... this is the thread at motorola's owner forum:
https://supportforums.motorola.com/thread/47721
I got my 3rd, brand new Desire today.
The 1st one would get really hot and reboot on me when i played angry birds or movies or used the GPS. It stared out 3 months after i got the phone.
I had the 2nd lasted 2 weeks before the GPS just would not lock at all, no matter what i did. The GPS was dead. The phone also got very, very hot not long after opening google maps or gps status.
The new one, Desire the III shell be its name, also gets very hot when i use the gps or play games. How long will this one last
This one is also PVT4, the other where both PVT1. What does this mean? also how do i tell what screen i have?
UPDATE: 07/03/2011
so after trying almost every ROM and kernel for the Desire i have found that i still have issues with the phone. I can not use setcpu and, like my original desire, i have random reboots when using the GPS.
Setcpu
I can not install the app at all. As soon as its installed i have app crashes.
I am not trying to OC here. A few 100Mhz is not a great deal anyway and with most ROMs Quadrant scores around 1100-1250 at stock, what ever that means. I wanted to use setcpu to take the min clock down to 1xxMhz when the phone is not used to save battery.
GPS
Same as the 1st phone. It get very, very hot and randomly reboots. This can happen in as little as 3min or xxmin.
I have a brand new htc battery, came with the phone, and no gel/hard/cover.
Can i really be this unlucky
The ship with the following
Baseband: 32.49.00.32U_5.11.05.27
Kernel: [email protected] #2
Build:2.33.161.2 CL284385 release-keys
Software: 2.33.161.2
Bravo PVT4
HBOOT-0.93.0001
MICROP-051d
Touch Panel-SYNW0101
RADIO-5.11.05.27
Aug 10 2010
Do you have any case or cover on your phone that might causing heat to get trapped between the layers? Both soft and hard silicone cases can cause your phone to get overly hot. Also are you using a stock rom or a custom one? Since it may be the kernel or a overclocking tool causing the cpu to run faster and hotter than it should be, led to your phone rebooting when it gets too hot. On average how long does your phone last from full charge to dead, when not in use, could be a duff battery.
The more you use it the hotter it will get, this is normal. So long a it doesn't reboot you'll be fine
Sent from my HTC Desire using XDA App
nope, had no cover/case/gel thing on the 1st two, only screen protectors.
i only found out about ROMs when i started to have the problem with the 1st one. It was stock standard for almost 5 months. I only began using a ROMs to underclock the CPU to see if that was the problem. Ran it at 600Mhz/700Mhz for 2 months before i had had enough and took it back to a vodafone store. With original RUU
The 2nd was only ROMed on the 3rd of march. I kept it stock 1st because i was studding and did not have time to play with ROMs and 2nd because i wanted to make sure it was working. So i just used the phone while running around normally.
The day before i started looking for a ROM i had issues getting a GPS lock. The following day i could not get the gps to work no matter what i did. So again turned to a ROM/Radio to see if it could solve the problem. No luck.
Had a go at Vodafone and they said because i had an issue within two weeks of getting the phone i could change it. Luckily a store near me had stock. So here i go again, round 3.
This phone is supposed to be for my sister I have a Desire HD
mrjonnyrock said:
nope, had no cover/case/gel thing on the 1st two, only screen protectors.
i only found out about ROMs when i started to have the problem with the 1st one. It was stock standard for almost 5 months. I only began using a ROMs to underclock the CPU to see if that was the problem. Ran it at 600Mhz/700Mhz for 2 months before i had had enough and took it back to a vodafone store. With original RUU
The 2nd was only ROMed on the 3rd of march. I kept it stock 1st because i was studding and did not have time to play with ROMs and 2nd because i wanted to make sure it was working. So i just used the phone while running around normally.
The day before i started looking for a ROM i had issues getting a GPS lock. The following day i could not get the gps to work no matter what i did. So again turned to a ROM/Radio to see if it could solve the problem. No luck.
Had a go at Vodafone and they said because i had an issue within two weeks of getting the phone i could change it. Luckily a store near me had stock. So here i go again, round 3.
This phone is supposed to be for my sister I have a Desire HD
Click to expand...
Click to collapse
Although in the past you might have got a GPS signal inside, I can normally only ever get a GPS signal outside, and I mean outside. I have heard about lost of problems with the Desire and GPS. The new Desire that you have is the latest release. Also the Desire always get's hot, you could boil an egg on mine, however mine has never Re-Booted due to heat...
jaaystott said:
Although in the past you might have got a GPS signal inside, I can normally only ever get a GPS signal outside, and I mean outside. I have heard about lost of problems with the Desire and GPS. The new Desire that you have is the latest release. Also the Desire always get's hot, you could boil an egg on mine, however mine has never Re-Booted due to heat...
Click to expand...
Click to collapse
I always test the GPS outside/out doors for at least 20min.
Sounds like you got some really ****ty Desire's and a really run of bad luck. Luckily I have never had these issues at all. As for the PVT4 business and your screen, most likely you will have an SLCD screen and PVT4 I guess is the security for the hboot, just a guess like.
I've always thought that my Desire was really cool, like if it is just running with checking emails, using the phone, light stuff really, it never gets hot at all or what I consider hot (where you can tell the difference on the back of the phone). The only time it gets hot is when I play a game for a really long amount of time, but even still, it never gets as hot as when it's charging. I have overclocked my phone to 1190MHz and it is fine. Also my GPS is fine and works when ever, inside or out.
I guess I got a really lucky Desire or you guys are really unlucky?
I can relate to the GPS issues. When the GPS didn't reboot my phone, it took a good 15 minutes to lock.
Took it back. No smartphone for 3 weeks
*I am not a happy HTC Desire user*
UPDATE: 07/03/2011
so after trying almost every ROM and kernel for the Desire i have found that i still have issues with the phone. I can not use setcpu and, like my original desire, i have random reboots when using the GPS.
Setcpu
I can not install the app at all. As soon as its installed i have app crashes.
I am not trying to OC here. A few 100Mhz is not a great deal anyway and with most ROMs Quadrant scores around 1100-1250 at stock, what ever that means. I wanted to use setcpu to take the min clock down to 1xxMhz when the phone is not used to save battery.
GPS
Same as the 1st phone. It get very, very hot and randomly reboots. This can happen in as little as 3min or xxmin.
I have a brand new htc battery, came with the phone, and no gel/hard/cover.
Can i really be this unlucky
The ship with the following
Baseband: 32.49.00.32U_5.11.05.27
Kernel: [email protected] #2
Build:2.33.161.2 CL284385 release-keys
Software: 2.33.161.2
Bravo PVT4
HBOOT-0.93.0001
MICROP-051d
Touch Panel-SYNW0101
RADIO-5.11.05.27
Aug 10 2010
I have just discovered I have this GPS reboot problem... For the first time on the weekend I decided to use the Google Maps GPS navigation. I bought a nice windscreen dock and everything...
First time it worked for about 3 minutes and then rebooted. From that point on I would only get a maximum of 30 seconds GPS navigation and then a reboot... I've tried everything I could find online about the problem including a full wipe but the problem remains...
So freakin' annoying! I guess it's going back to HTC....
Same problem here.
when using GPS for 1-xx.min the phone reboot.
Have tried every romes, radio, wipe all, formatet sdcard..
tried to caught the problem in LogCat.
I just cant find the problem!
it makes me crazy.
I think it's probably a temperature problem.
If I remove the battery and let the phone down for a while, navagitionen will work for about 10-20 minutes. if I open the navigation with the same after the reboot it will only works for 1 or 2 minutes.
OP, you are either a complete idiot and don't know how to use your phone or you are very unlucky. I think it may be the first option. I know at least 20 people with desires who have NEVER had a problem. Use it what it's meant for and stop ****ing with it.
Blert.
Sent from my HTC Desire using Tapatalk
john014 said:
OP, you are either a complete idiot and don't know how to use your phone or you are very unlucky. I think it may be the first option. I know at least 20 people with desires who have NEVER had a problem. Use it what it's meant for and stop ****ing with it.
Blert.
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Thanks for your awesome solution! You complete IDIOT! what a nice tone you choose to write in at this forum - really mature! start helping people instead of asuming the worst of them. This is NOT my first smartphone and I do in fact know how to use it. As a matter of fact I work with developing programs for phones and other microprocessing units, and have never heard of or experienced this problem before.
Instead of complaining why don't you start HELPING people!?
Same poblem here dudes but i csj live with it. I have seen Desires that restarts themselves when surfing on internet or when calling.
Sent from my HTC Desire using XDA Premium App
I've been trying to figure this out for months and have had no luck so I wanted to see if any of you had any recommendations.
I used to run Sense roms like the stock one and the sense 2.1 mctwist rom and they had no issues.
When CM9 came out, I decided to switch over to that. It functioned fine except I would get random reboots about 1-2 times each day. Tried clean installs, etc but nothing work.
Then CM10 came out and I upgraded. Once again, it works excellent except I still get random reboots once or twice a day.
And just recently I tried the AOKP Jelly Bean ROM, hoping it was a CM issue, but I also got the random reboots on AOKP.
What could be causing this? Occasionally I can go through the day without a reboot, but 9 out of 10 times, I get at least one reboot each day. Sometimes it happens while it's in my pocket and I don't even notice for a few hours.
These reboots are basically the phone starts showing the boot animation, but with a very dim screen and it just stays stuck with the spinning boot animation. It won't reboot until I pull the battery or do the 3 button reset.
Any advice? Should I try a different radio or...? I don't even know. I love JB so much so I'd hate to have to go back to a sense rom, but I can't take these reboots anymore.
Thanks
jpzsports said:
I've been trying to figure this out for months and have had no luck so I wanted to see if any of you had any recommendations.
I used to run Sense roms like the stock one and the sense 2.1 mctwist rom and they had no issues.
When CM9 came out, I decided to switch over to that. It functioned fine except I would get random reboots about 1-2 times each day. Tried clean installs, etc but nothing work.
Then CM10 came out and I upgraded. Once again, it works excellent except I still get random reboots once or twice a day.
And just recently I tried the AOKP Jelly Bean ROM, hoping it was a CM issue, but I also got the random reboots on AOKP.
What could be causing this? Occasionally I can go through the day without a reboot, but 9 out of 10 times, I get at least one reboot each day. Sometimes it happens while it's in my pocket and I don't even notice for a few hours.
These reboots are basically the phone starts showing the boot animation, but with a very dim screen and it just stays stuck with the spinning boot animation. It won't reboot until I pull the battery or do the 3 button reset.
Any advice? Should I try a different radio or...? I don't even know. I love JB so much so I'd hate to have to go back to a sense rom, but I can't take these reboots anymore.
Thanks
Click to expand...
Click to collapse
It could be an app causing it, or overheating. Do you over/under clock/volt? You may want to try underclocking a little, or raising the voltage a little. You may also want to check the system and kernel logs to see if they reveal the issue.
cmlusco said:
It could be an app causing it, or overheating. Do you over/under clock/volt? You may want to try underclocking a little, or raising the voltage a little. You may also want to check the system and kernel logs to see if they reveal the issue.
Click to expand...
Click to collapse
I used to overclock on my sense roms with no issue. But on CM10 I just have it set to stock speeds with no overclocking or adjusting the voltage. Could my phone be getting old and so even stock speed is causing overheating? My phone doesn't feel noticeably hot, unless it gets stuck in one of these reboots. Then it feels rather warm. What would you recommend I change my voltage to?
And I tried doing logs but they get wiped when I restart
EDIT: Odd thing I just discovered. I borrowed my friend's seido extended battery for the dinc and popped it in my phone. After charging it up for a bit, I used the phone and within 10 minutes it started acting weird and rebooted. And after restarting, it rebooted again a few minutes later. So basically it was even worse. Any correlation here? Does the extended battery = more heat = that's why my phone is rebooting?
It's hard to even guess unless you can get a log. If you give one of the stock based ROMs another trial for a few days, and the phone does not reboot, then it is safe to say it is not hardware. I'd start by at least ruling out the hardware possibility.
Do not use Titanium or some other app to restore any sort of data from one ROM to another. That often seems to cause a lot of people problems.
If your phone isn't that hot, I agree that heat isn't likely the problem. Mine absolutely roasts while navigating (while charging, screen on, gps and 3g antennas on, music playing, overclocked, weak original stock battery, otterbox case so it can't breathe, etc.) and it doesn't ever reboot from heat.
Everyone uses their phones differently. So what may be stable for one person might not be for others. I've come to the conclusion that there is only one person who can determine if a ROM is stable... that is the one person who uses it everyday. Just because some other people are using a ROM and getting good results, it doesn't mean that you ever will (even with you wiping/flashing/installing apps by the book).
CM9, CM10, or any and all ICS and JB roms are going to have things that aren't working right for some time still. It's just the nature of the beast. App compatibility, especially, is just one of those things. It's a testament to how good those awesome devs are that anything works on our Dinc running JB and ICS.
I never ran the ICS and JB ports for long (in fact only very short periods of time) because my problems far outweighed the benefits. There is no shame in GB working better for you. I run a variant of CM7 (which is gingerbread)... it is definitely different than stock-sense. Then I use alternate launchers (Go launcher is my favorite) to change it up even more. You can do so much customization that isn't dependent on the ROM. Then I can use something like ROM TOOLBOX PRO for even more customization.
Software is not fashion. What actually works never goes out of style (despite what the hipster kids on xda might be saying ...get off my lawn... grumble...)
jpzsports said:
I used to overclock on my sense roms with no issue. But on CM10 I just have it set to stock speeds with no overclocking or adjusting the voltage. Could my phone be getting old and so even stock speed is causing overheating? My phone doesn't feel noticeably hot, unless it gets stuck in one of these reboots. Then it feels rather warm. What would you recommend I change my voltage to?
And I tried doing logs but they get wiped when I restart
Click to expand...
Click to collapse
I would use incredicontrol and raise all max voltages by 25 or one push of the plus button. Sometimes as phones get older the processors get worn , and have issues with not enough power or even with the stock max frequencie of 998mhz. If raising the max voltage dosent help, i would underclock down from max 998.
Thank you both for the replies. I really appreciate it. I'll try overvolting and see how it goes tomorrow. If I still get reboots, I'll try running a stock rom for a few days and see how it performs.
jpzsports said:
Thank you both for the replies. I really appreciate it. I'll try overvolting and see how it goes tomorrow. If I still get reboots, I'll try running a stock rom for a few days and see how it performs.
Click to expand...
Click to collapse
Pardon me harping on my pet issue, but my phone does that if I underclock the CPU minimum to 128MHz. If I leave it at 245 I can go for days on end (I've seen uptimes of over 200 hours). For whatever that's worth...
musical_chairs said:
Pardon me harping on my pet issue, but my phone does that if I underclock the CPU minimum to 128MHz. If I leave it at 245 I can go for days on end (I've seen uptimes of over 200 hours). For whatever that's worth...
Click to expand...
Click to collapse
That is true, if i go down to 128 i have screen on freezing issues, and random reboots.
EDIT: Odd thing I just discovered. I borrowed my friend's seido extended battery for the dinc and popped it in my phone. After charging it up for a bit, I used the phone and within 10 minutes it started acting weird and rebooted. And after restarting, it rebooted again a few minutes later. So basically it was even worse. Any correlation here? Does the extended battery = more heat = that's why my phone is rebooting?
Click to expand...
Click to collapse
This is certainly a clue... but I don't know what it means...
I would not think the the extended battery would produce more heat. Since both batteries should be discharging at the same rates the heat output should be the same (just that the bigger one would take longer since it has more reserve). I've ran across stories of people who had phones that went completely wonky when they tried swapping batteries or getting a new one. I really don't know anything about it, I'm still on my stock battery.
It certainly couldn't hurt to try wiping your battery stats in clockwork. There is apparently some magic methodology to do it "correctly". I don't know about that either... here is a thread.
http://forum.xda-developers.com/showthread.php?t=1359395
Well just as an update, I tried the overvolting and clearing the battery stats but still got the reboots. I installed one of the Stock Sense ROMs and it's been running great with no reboots. Apparently my phone just doesn't like non-Sense ROMs for some reason. Oh well. At least I have a working phone. Pretty amazing how fast the stock rom runs!
Well, I guess it's good to hear the hardware is ok.
You still could try out the CM10s (or other JB roms) by starting off without installing your apps (if you can live without them). App compatibility might be your problem. Let it run for a while with no additional apps added. Then, add them back slowly (one or two a day or every couple of days) from the market only. If the reboots start up later on... you will probably recognize the one that is the source of trouble.
Of course you still have plenty of options in the gingerbread family to choose from. If you've never tried out some GB AOSP/CM roms, that would be worth a try. You've got stock roms, stock roms with sense removed, and the whole variety of AOSP/CM7 (official and unofficial) to choose from. Launchers...themes... mods... etc... all kinds of ways to change from whatever you start with. The only GB roms that I ever had problems with were the official "stable" CM7.0 and CM7.1 ROMs. I've been running one unofficial CM7 build (about 99.99% of the time...except to test drive newer stuff) for almost a year. Its been the best thing that's ever happened to my phone.
There is something going on with my phone, Samsung Galaxy S3, V4.3 where occasionally, lately it has been once a day the power draw from the battery will spike as high as 2,000ma (2 amps). This last long enough to drop the charge 10 - 20% and creates excessive battery heat. It happens on charge or off charge. I have tried viewing the running processes with System Tuner and nothing shows up in the list using an excessive amount of CPU. Better Battery Staus also doesn't pinpoint the problem. I have most everything Greenified accept Google stuff of course and useful stuff like email, etc. I now believe it could be connected with GPS since I turned off the GPS I have not had another event other than a 800ma spikes that quickly go away. Need more time to confirm it is GPS related. Are there any programs that will log which applications are using GPS? Any other ideas what could be the problem? I don't understand why System Tuner doesn't show me which process is eating the battery? Can anyone point me in the right direction.
I thonk it may be the radio itself. I have recently noticed similar issues on mine but its usually when streaming videos. I rarely use gps so i cant speak on that right now.
If i have it plugged in while doing this, it gets hot enough to trigger a shutdown due to thermal event....it crashes!
DocHoliday77 said:
I thonk it may be the radio itself. I have recently noticed similar issues on mine but its usually when streaming videos. I rarely use gps so i cant speak on that right now.
If i have it plugged in while doing this, it gets hot enough to trigger a shutdown due to thermal event....it crashes!
Click to expand...
Click to collapse
Same here, I also noticed with System Tuner that several applications that normally use 1% or less of CPU seem to spike to 8 - 30%. This all seem very odd. Now I am wondering if the background radio steals CPU cycles and leaves no time for normal applications. Anyway, the issues are reduced with GPS off although the battery does get warm sometimes without any reason I can fine. I'll try streaming audio and see if it triggers.
I would be willing to try a different radio. My current software is Model Number SGH-T999, Android version 4.3, BaseBand version T999UVUENC2, Kernel 3.0.31-1962493, Build number JSS15J.T999UVUENC2.
Unfortunately, no other radio will work. You can try one just to be sure about it. It wont brick, but just wont function. Youll have unknown imei and baseband until you flash the NC2 modem back.
Im currently running my port of S3Rx 4.0, but ill flash back to NC2 in a couple if days to test more on mine. Im also using a case/housing not meant for the T999 so theres a good chance that is contributing to my problems though.
DocHoliday77 said:
Unfortunately, no other radio will work. You can try one just to be sure about it. It wont brick, but just wont function. Youll have unknown imei and baseband until you flash the NC2 modem back.
Im currently running my port of S3Rx 4.0, but ill flash back to NC2 in a couple if days to test more on mine. Im also using a case/housing not meant for the T999 so theres a good chance that is contributing to my problems though.
Click to expand...
Click to collapse
Okay, thank you for the replies. Please stop by if you learn anything new. Velis Auto Brightness is up to 64% CPU usage, grrr. I posted on developers forum maybe troubleshooting that will lead to a fix. The 2 amp spikes haven't occurred since I disabled GPS, so I am guess you are correct about the radio.
The problem returned so turning off GPS isn't a complete fix, seems to reduce the frequency is all. It looks like Android System is the problem. If I shut down pull the battery reboot the bad behaviour continues, only fix seems to wait it out. My next phone most likely will not be a sammy.
Im not really sure what to suggest at this point. I can say that what we are experiencing isnt typical though.
Out of curiosity, have you given any of the ported kk roms a try? I think my Sprint port is probably the most stable/bug free, but they are all good and ive had pretty good battery on each one compared stock. (Ive always had good battery life even on stock though, aside from a few recent issues that I believe are more my own fault). TMS3KK is a solid rom with very few issues. S3Rx 4.0 is as well, but ill be posting an update to it hopefully later today, so I cant say its really been thoroughly vetted yet. Still worth a look though, imo.
DocHoliday77 said:
Im not really sure what to suggest at this point. I can say that what we are experiencing isnt typical though.
Out of curiosity, have you given any of the ported kk roms a try? I think my Sprint port is probably the most stable/bug free, but they are all good and ive had pretty good battery on each one compared stock. (Ive always had good battery life even on stock though, aside from a few recent issues that I believe are more my own fault). TMS3KK is a solid rom with very few issues. S3Rx 4.0 is as well, but ill be posting an update to it hopefully later today, so I cant say its really been thoroughly vetted yet. Still worth a look though, imo.
Click to expand...
Click to collapse
No time to try a different ROM yet. I should have time the weekend after next. Thank you for all your suggestions.
I tried replacing the battery. After the first charge the phone lasted for 2 days before the battery dropped to 5%. It took 6 hours to charge back to 100%. No problems until later, it seems to dislike being unplugged moved to a new location and plugged in again. This appears to be when the problem occurs. I usually just leave the phone plugged in all the time. I'll test further with the power before I make up my mind. I think this will be the last Sammy phone for me?
Is it a non stock battery? I've always had issues with those reporting correctly.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
DocHoliday77 said:
Is it a non stock battery? I've always had issues with those reporting correctly.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Usually I would buy a non stock battery however since this phone lays next to me in bed to wake me in the mornings I am a little concerned with a fire so it is a Samsung battery from Samsung. Leaving it unplugged for a bit and plugging it back in didn't work stop the battery drain. There are no processes eating the battery according to System Tuner so got to change the ROM.
Should I try a ROM first or kernel or both? Could it be an Xposed module, thinking about turning all of those hacks off?
I just remembered, this only happens if the screen is on and the phone is plugged into the charger. And rebooting doesn't clear the problem.
I would start with a stock based ROM. If it were me I'd go full stock rooted. But yeah I'd ditch xposed for now. You might even try reflashing your current ROM, factory resetting and this time don't use any exposed mods. If it still has problems, then try a different ROM.
It wouldn't surprise me at all to find xposed was the culprit. Its really cool, and the dev is amazing, but I prefer not to use it at all. IMO, it's much better to have the mods coded into the ROM itself.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
DocHoliday77 said:
I would start with a stock based ROM. If it were me I'd go full stock rooted. But yeah I'd ditch xposed for now. You might even try reflashing your current ROM, factory resetting and this time don't use any exposed mods. If it still has problems, then try a different ROM.
It wouldn't surprise me at all to find xposed was the culprit. Its really cool, and the dev is amazing, but I prefer not to use it at all. IMO, it's much better to have the mods coded into the ROM itself.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Thank you Doc, will do so and report back here the results.
My phone does the same thing now. My phone never did this when I first got it a couple years ago. I use GPS a lot because son plays on a travel hockey team. I could drive 3 - 4 hours away with the phone on and plugged in using the GPS without any issues. Now, my phone gets so hot in about an hour of the same type of use and it shuts down.
I thought that maybe there was something wrong with the phone because of age but now I see it could be something different.
It very well could be age related, or it could be partially due to that too. But I'd do as I suggested above and run stock for a bit to test. If on a custom rom, and especially kernel, you could run into issues like that too.
If you have the same problem on stock, (and you're sure its not an app acting up), there's a very good possibility that its more of a hardware related issue.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
And it is not the battery. I can't load stock until next weekend, need my phone for work.
You can always use better battery stats to investigate while you use it normally. Let it log all wakelocks, including kernel wakelocks for a full cycle.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
DocHoliday77 said:
You can always use better battery stats to investigate while you use it normally. Let it log all wakelocks, including kernel wakelocks for a full cycle.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Tried that, been there, odd thing is nothing shows there. I'm gonna reload with stock per your suggestion next weekend and if that doesn't work I'll try a custom kernel.
Try remove greenify app and see what happens. Cuz with my case the latest version (2.4.x.x) of greenify driving my phone nuts. That app used to be great.
I'm back. Loaded stock 4.3 ROM / kernel, radio is at newest versions, I am going to say the problem is gone. The battery heats up to about 32-33 degrees Celsius however the phone isn't hot like it is burning up so I believe the problem is like Doc suggested earlier with the radio. Which would explain why the process monitors never see any rouge application using to much CPU. So after some pondering, this doesn't stop a rouge application from using to much bandwidth and cooking the radio so to type. If I had to pin it down I am going to suggest it maybe one of these two applications: FCC speedtest and or Opensignal or some other application. Both of the listed applications periodically test the network bandwidth and report back to a central server. I suspect that this maybe trigger the heat problem from the extend radio usage. No proof at this time just conjecture.
I am considering jumping to an AOSP ROM to be free of the Samsung bloat, NOT CM, don't care for CM, does anyone have any good suggestions to try?