Has anyone else had this phone overheat a lot and reboot?
Ever since I've upgraded to DK28, the phone seems to be overheating with sustained gameplay of games like Pocket Legends or the Sims 3. I've tried multiple ROMs, Epic Experience, Viper, Quantum, and Nebula (so far the best stability of the ROMs that I've tried). The phone basically freezes and reboots. I've tried to mitigate this by putting my phone by the window and opening it (it's below freezing here in Canada), but with only limited success.
Notes: Syndicate ROM v1.02 with Xtreme Kernel 1.01 did not have this problem in Android 2.1, despite me overclocking the CPU.
My Epic gets up to 105 (F) sometimes but it's never rebooted on me like that.
I received a replacement phone from Asurion, which kept overheating, locking up, and turning itself off. Every time I had to pull the battery just to the phone to function. Even though I called Asurion 10 days after receiving the phone, they gave me a brand new replacement. The defective phone that they gave me had two stickers under the battery. One stated Remanufactured by Asurion and the other was a white square dot/sticker.
The rep stated that there is a small scale known issue about the phones overheating even when not being used.
I hope this helps.
Take care
sauron0101 said:
Has anyone else had this phone overheat a lot and reboot?
Ever since I've upgraded to DK28, the phone seems to be overheating with sustained gameplay of games like Pocket Legends or the Sims 3. I've tried multiple ROMs, Epic Experience, Viper, Quantum, and Nebula (so far the best stability of the ROMs that I've tried). The phone basically freezes and reboots. I've tried to mitigate this by putting my phone by the window and opening it (it's below freezing here in Canada), but with only limited success.
Notes: Syndicate ROM v1.02 with Xtreme Kernel 1.01 did not have this problem in Android 2.1, despite me overclocking the CPU.
Click to expand...
Click to collapse
Occasionally when I am tethering my phone gets above 40 C (104 F) but I have found that leaving it with the keyboard open really helps cool it off. When I'm not tethering it rarely gets above 30 C. I am running a relatively unmodified Dk28.
richse said:
Occasionally when I am tethering my phone gets above 40 C (104 F) but I have found that leaving it with the keyboard open really helps cool it off. When I'm not tethering it rarely gets above 30 C. I am running a relatively unmodified Dk28.
Click to expand...
Click to collapse
I suppose I will give this one a try.
Mine gets really hot, when browsing dolphin hd on low batt while charging.
My gfs phone is much more buggy. Hers force closes then sometimes reboots
While impractical for actual phone use, if you are tethering and the phone is getting hot, put a plastic zip-lock bag of water about 1/2 full (do your best to get out all the air) underneath it. Used that with my TP2 and it works like a charm. Just be careful with it!
Related
From time to time (signal strength low, graphic intensive game, or just being too hot in general) my Incredible gets too hot, and, as a result, it reboots. When it reboots under heat, it may reboot a few times in a row, before booting up.
I know some people have resorted to the undervolt; are there any less intrusive ideas to keep the phone from overheating?
jdmba said:
From time to time (signal strength low, graphic intensive game, or just being too hot in general) my Incredible gets too hot, and, as a result, it reboots. When it reboots under heat, it may reboot a few times in a row, before booting up.
I know some people have resorted to the undervolt; are there any less intrusive ideas to keep the phone from overheating?
Click to expand...
Click to collapse
Maybe yours is messed, call verizon support think its *611, then talk to them about it, they prob send you a new phone, well new as in refurbed replacement.
Why not undervolt with a hydra kernal. Will also oc it and give you a boost in speed if that one will work for you. I dunno just saying
I may
I may just do that, but would like to get FroYo on the phone and then see what Kernels work with it. I have no intention of sending it back in for a refurb because it doesn't happen that often and I certainly know a refurb may have far more issues. I am also trying to remember if it happened less with my 2150mah (I went back to my 1750).
Thanks!!
For some reason my EVO keeps restarting randomly on me, and all the time too.
I'm running CM7 7.0.3.1 and savaged zen 2.2.0, and I have an extended battery and I rum juicedefender.
Now I don't think its the battery because I've had it for month
Its most like savagedzen 2.2.0 but idk maybe its CM7 too.
I think this started after I started playing words with friends. Doesn't seem like a memory intense app and I never had this happen but lately its been rebooting randomly, like I'm download from the market. Internet, and even posting this thread!
Basically I'm thinking of switching to either virusrom or Mik, which is better?
Sent from my dope fly fresh EVO
my chick is having the same issue. hers just reboots at random after starting to use her pandora app about a week ago.
her evo is running:
Mod version: CyanogenMod-7.0.3.1-Supersonic
Kernel version: [email protected]#1
Ditto
I have same problem, and have tried various ROM's, most recently a complete wipe as per Mikroms instructions. Only pattern I can make out is it tends to start when the CPU is stretched a little, such as running Tango over 3G, or even Angry Birds for over ten minutes. Once it starts though, it reboots several times before it finally quits.
There was another thread on this, but no solutions, instead it turned into an argument over whether it is CM7 fault; not very constructive. I have tried different batteries and changed up CPU speeds, still to no benefit.
Like I said, if I don't tax the system I have no problems, and that so far has been my only solution, but a disappointing experience with my Evo.
My dad's kept rebooting too even after the gingerbread OTA. He is running a bone stock phone(not even rooted)
Wife is having the same issue on her stock EVO with the new OTA
same issue here, playing WWF,stupid zombies or surfing the web. on decks rom and on the gingerbread 2.3 stock.
Apparently, this is a common problem with the EVO. Mine started as soon as I accepted the recent OTA update. There is an XDA thread somewhere. Just do a Google search.
Same here & 2 of my other friends. I am on my 3 or 4 EVO (lost count) & everyone does it. This is only one I rooted as well. I noticed it does it less (once every few weeks to a month) with a custom non cm rom. Also restart your phone at least every couple of days (usually I did every day). It works out pretty well. What I tell my friends don't hesitate to tell sprint you have a issue so it gets documented. So you have proof to fall back on when you had enough. It's not like you pulling one over on them. They see if you have all these issues for so long why just now saying so. I have found that for some reason phone resets in middle of calls multiple times same day with certain Bluetooths. I drive truck for living so I on phone alot with customers/work/friends/family/etc. Always Bluetooth, and did up to 5 times a day. Then bought one top of line (jawbone icon &now Bose) and doesn't do it like that anymore. Hope this helps any of you. & again any issues you get tell sprint. Last time I got a new EVO in box, & they let me keep my old one. So gave it to my mother. Then had it replaced under her #.
Sent from my EVO using Tapatalk
Mine started out with a reboot
every so often. It finally got so bad it would reboot over and over until I pulled the battery for a few. Somewhere in the process, my GPS crapped out as well. It would work for a few minutes and then freeze. Not a good thing when you are not from Boston and trying to navigate 8am traffic to get somewhere.
I got a refurb as a replacement. It was in perfect shape and only had like 111 minutes of talk time. No telling why it was sent back but I've had no issues with it.
Mine is doing this too.. its annoying Ive restored backups and it just keeps rebooting, i dont know whats wrong. Im on avaFroyo 2.2
I don't remember where but there is a thread about this very topic. From what I read this was attributed to a corrupt data partition. My gf phone is starting to have this problem. Only fix I have read so far is to reroot phone and take it to sprint. I am waiting til they can root the ota. Then I will unroot her phone and get a new one.
Tim
Sent from my PC36100 using Tapatalk
I've been seeing a LOT of posts to the effect of "all Vibrants vary", etc... I'm not talking about Vibrant 3G vs 4G or Bell Vibrant, we all know those differences.
What I'm referring to is how phones that are supposed to be identical act and perform vastly different. This leads frequently to claims of "LIAR" and flames, etc. I for one admit I find myself unable to believe for a second anyone that claims to get more than 10 hours of battery life on a GOOD day with a Gingerbread ROM, but people have posted screenshots of 16-25 hours with supposedly stock batteries.
The things I've noticed that are "different" about everyone's phones:
1) Some wipe the SD Card frequently on updating. Others never do.
2) Some came with no hardware access to download mode, some had it.
3) Some have awesome GPS, others have terrible GPS, which leads to #4
4) GPS fixes that improve one phone actually make the next phone WORSE. This is illogical unless there are actual differences in the GPS Radio...
5) Some get decent battery life on Gingerbread, while others are completely unusable, starting to visibly drain the moment you pull them off the charger. And this has no relation to battery life on Froyo, eliminating possible actual battery or user differences.
I did not include overclocking ability, because that's normal with the tight tolerances on CPU production runs. This other stuff, it's just not normal if everything internally is the same.
It just seems too much to be quality tolerances. As I said, people are coming to blows over some of this stuff. When I see someone claim they get good battery life on Gingerbread, and that all it takes is calibrating your battery, I want to bludgeon them over the head with my phone that drains 65% of its battery just sitting there idle for 8 hours, or 40% drain if I'm using my extended battery... when with Froyo, I get 1 or 2% drain in the same time period. But certainly people are getting "decent" battery life.
Even more strangely, it seems like when the phone was manufactured doesn't seem to matter. But the differences, especially in claimed battery life on Gingerbread, and the tendency to have GPS fixes work on one phone and actually 100% fail on the next, makes me wonder if there isn't some issue that hasn't been identified. Are there perhaps 2 different parts suppliers for some component in the phone, that perhaps Samsung is aware of and has written around, or compromised to, which would explain mediocre stock GPS performance, or what is going on?
Are there other differences people have noticed? I'm wondering that if maybe we can somehow identify the actual differences or some pattern, maybe it will clue in the more experienced developers as to what it will take to fix these issues. Currently though, as each developer typically only has 1 or 2 phones, their own, to test on, they can't easily test on both the "good" and the "bad" vibrants.
For example, if you've swapped a Vibrant on warranty, have you gotten one back before that had markedly different characteristics? Notably faster or more laggy than before, drastically different battery life, etc?
What do y'all think?
I have switched out 3 vibrants and this last one is a bit faster but the gps seams more lagging than my last one also I have noticed screen color and brightness differences as well which in part could be responciple for the battery drain. You would think a company such as samsung would have there stuff together.
Sent from my Vibrant running toxic blue
Well mine is odd i can say that. My stock gps never worked. Once i rooted and started using sgps fix i had no issues. I get great battery life on gingerbread (24hours plus on moderate use) but cannot get a gps lock no matter the fix. I cannot run cm7 either it will drain an entire battery in 3 hours if i do. I can run a stable overclock on gb or froyo at 1.6+all day long with no issues.
My wifes vibrant is about the exact opposite of mine i can run the same roms and kernels but hers will not handle overclock or compare similar in quadrant or running 3d games. So yeah its not just you there is something oddly different in these so called same devices.
Sent from my GT-I9000 using XDA App
I get 22+ hours on every rom I have ever tried and I have tried almost all of them. My gps has also worked well on every rom including gingerbread. I'm using trigger right now and it easily gives me 20 plus hours with screen on over 4 hours...not that battery matters much. Every one should have an extra battery even if it's a cheapy one and there arter ton of those around.
Sent from samsung vibrant
You also have to take into account that the parts of the phone can be slightly or vastly different.
Just from a manufacturing stand point in general I can say with utmost certainty that no matter what steps are taken to ensure identical parts across a line of anything there will always be differences. The time my circuit board went through quality control may have been the end of a shift and the person may have cared about their job a lot. The line stops next shift comes on and a slacker who just got dumped by his girl checks the very next board that may not quite meet spec. This is just one example.
My other example is that of processor chips. As far as computers go, and I'm sure its the same here, the chips are made from a large wafer. Toward the center is higher quality and the edges are lower quality. All these chips meet the minimum requirements but the ones from the center could probably be meet the minimum requirements of the next level chips.
This doesn't even take into account all the outside factors after manufacturing. Yours goes to Tulsa with Mr. UPS and mine comes to Florida with some temp Meth head that managed to fake his way into a job and decides that since its the basketball playoffs he wants to be Lebron with my package.
I hope some of that makes sense. You and I can take the exact same steps to wipe and flash but because of the far too many factors that can make our phones different we may or may not get the same results. All we can do is try to get everything to an optimal place that it works across the majority of phones.
Sent from my SGH-T959 using XDA Premium App
i think it also depends on when and where u bought your phone from can effect your device, for example on froyo i had good battery life 15 hours with moderate use and great gps, but with gingerbread i get about 18-19 hours on moderate with cm7, my gps barley works and any gps fix has no effect on it, my phone can handle slight UV but anything under -100 it gets unstable but i can clock up to 1.7ghz stable i tried 1.8 but that made it crash, so i guess its also based on luck
I had great results with the s.gps.2.zip file flashed on top of Bionix 1.3.1 on BOTH of my Vibrants (mfg. on 10/10 and 1/11). I've been lucky that they both mirror each other in anything I do to them.
Now you gotta take in consideration that you can't go by what everyone claims here regarding their battery life. I'm not calling everyone liars but there are some that you just gotta throw the bull**** flag on them. I seen post claiming that they got 50 hours of battery life (maybe on standby) but I don't see that happening with "regular" use.
Now wtf would you consider "regular" or "moderate" use? Nobody knows cuz every one's use would be different.That's why I feel you can't go by that claim. I can't tell you how many hours I get on a full charge because I can't clone what I do with my phone everyday to give you a number. There are weekdays I have 70% from 5am-4pm and others I'm changing my battery at 4pm cuz I'm on red. I know for sure though that its a hell lot better that when I was on stock.
Alex9090 said:
I get 22+ hours on every rom I have ever tried and I have tried almost all of them. My gps has also worked well on every rom including gingerbread. I'm using trigger right now and it easily gives me 20 plus hours with screen on over 4 hours...not that battery matters much. Every one should have an extra battery even if it's a cheapy one and there arter ton of those around.
Sent from samsung vibrant
Click to expand...
Click to collapse
If I was able to get 22+ hours on JVP/Q/R GB *or* CM7 I'd be there in a heartbeat. Unfortunately although I can easily get 30 hours on Froyo with my light usage and the STOCK battery (we won't even talk about my Momax), I am lucky to get 10 hours on any GB...
The thing is, these differences are not "minor", they're HUGE differences that people are experiencing. When I say I'm lucky to get 10 hours on GB, I'm saying I can put my phone onto 2G mode only, lay it on the nightstand, and wake up 8 hours later to find 50% of the battery drained - without having done ANYTHING. And then do the same with Froyo and only drain a couple of % - with the same installed apps.
On the CM7 threads and the JVP/Q/R threads it's typically "Well you won't get as good as FROYO but it's acceptable", and that's just not the case with a good portion of users.
I don't blame the developers, of course... what I'm saying is there's SOMETHING, given all these differences, not just battery drain, that is different about these phones that hasn't been discovered. It's enough to make me want to exchange my phone before the warranty is up in September "just to see" if a different phone would be better.
I think mine is the most "common variation" of the Vibrant
- Received the contract through an authorized reseller first week of October
- Not hardware locked
- Never had mysterious sd wipe issues
- GPS worked (locked anywhere from 2 minutes to 5 seconds depending on settings) but will suffer occasionally from horrible, horrible drifting issues (too afraid to perform hardware fix). Interesting to note, s.gps.zip worked wonders but s.gps.2.zip (or whatever it was called) completely broke my gps.
- Never bothered to test if I could overclock or not, but my phone has had the freeze of death when underclocking to 100 or 200 mhz.
- Everything else worked as it should: odin (never had a failed flash), voodoo (never had the not enough space error), etc. etc..
regarding battery life
- pretty standard, custom rom or not, I was able to go through the day with 1 charge (eclair and froyo). Best was Axura 2.x with JK2 modem (around 26 hours I believe).
- GB. It hasnt been as nice as froyo but I believe the devs have done their best without a Vibrant-specific leak. It could last a day, but thats being very generous with screen on time and usage. I believe the GB roms will be on par with froyo if we recieved a leak of our own..
-
Good day everyone. I have a problem with my evo 4g. I'll try to keep my post detailed as much as possible,tho I'm a newbie.
anyway, I got this evo 4g 2ndhand. since it's cdma it's priced here in Asia way cheaper than the phones with sim slots. I noticed the battery life is somewhat short, and the phone was warming up. I don't know if this should be labeled as "warming" or "heating", or this might be normal, since these phones host 1ghz processors, not to mention a gpu without heatsinks.
I tried turning on airplane mode to disconnect all connections. since I have read in an article that I should avoid task killers, I didn't install such. I notice that whenever I am playing simple games, like doodle dash, after a while, the phone begins to become a little warm. also when playing videos 1% will be immediately decreased from the battery.
I would like to know if the heating or warming up is normal for an android phone, (since I have come from playing the psp and the nintendo ds, and as far as I could recall I haven't encountered warming issues such as this, but then those devices have thicker casings and have less components running them) I haven't encountered the blinking green orange lights yet, but afaik that'll only show up when it's charging. Also i've tried some battery temperature sensing apps the other day, but something must be wrong since it's been reading the temp, stuck at 29C. I'll try to install another one, and I'll update the results.
What would be the solution to my problem? any other settings here that should be tweaked? i tried factory resets, reformatting the sd. my android version is 2.3.3.
Thanks xda-developers.
Could be in my opinion your charging port that's making your phone warm up than usual. To know for a fact is when its starts boot looping numerous times. This has happen to me once before. Can u give us phone details? Hboot, version stuff like that would be helpful.
Sent from my PC36100 using xda premium
It's normal for the Evo to get warm and even a bit hot when used heavily. Playing graphics-intensive games will definitely get your phone warm. Basically it's nothing to worry about. If the phone gets too hot it will automatically shut itself down.
Does anyone's phone turn off when it gets just a little warm? I left it in the car for a couple minutes and it had shut itself off. This only happens with custom ROMs, never on stock.
I can confirm on my Essential running AOSiP Build 8.1-Official-mata-20180211 I get at least one shut down a day due to it overheating very quickly when driving home. I though it was a phone malfunction but am not going to revert to stock and see if it stops. Love this phone but the overheating has become unbearable.
Ya I've been getting this more recently. Running remix. Seems to happen also when doing more intense things with phone.
UN5EEN said:
I can confirm on my Essential running AOSiP Build 8.1-Official-mata-20180211 I get at least one shut down a day due to it overheating very quickly when driving home. I though it was a phone malfunction but am not going to revert to stock and see if it stops. Love this phone but the overheating has become unbearable.
Click to expand...
Click to collapse
I don't think it's overheating per se. It's more like it just decides to shut off rather than throttle to cool down, like it's supposed to do. I went back to stock because of this issue.
UN5EEN said:
I can confirm on my Essential running AOSiP Build 8.1-Official-mata-20180211 I get at least one shut down a day due to it overheating very quickly when driving home. I though it was a phone malfunction but am not going to revert to stock and see if it stops. Love this phone but the overheating has become unbearable.
Click to expand...
Click to collapse
This happened to me with the stock ROM when I drive using a normal USB car charger where it gets very hot and battery barely charges in my trip. Changing to a USBC PD charger seems to fix it for me. Phone runs much cooler and actually charges fine