I recently had to get a replacement Evo . I rooted it and installed Myn RLS5 then installed Net 4.3.2 More Havs SBC kernel on the phone . I woke up one morning to find the screen was flickering when I pushed the power button to check the time and weather . When I unplugged from the charger it was fine afterwards . Since then I have unrooted and went back to completely stock . My HW003 never had issues with kernels and Im not even sure if this is a result of a kernel . The flickering I expierenced were long strips going the full length of the screen that flickered as if they werent getting enough power or something like that . I was wondering if anyone else has seen this issue before . But like I said since flashing back to bone stock I have had no issues .........as of yet. Does this sound like a potential hardware issue or more of a software issue ?
Sounds like screen tearing, which is usually (if not always) the result of using an incompatible kernel for the ROM your on.
I had thought maybe that might be another possibility , I had this set up with the HW003 setup . Same kernel same rom and had no issues like this before . Unless Im suffering from the "some phones handle certain software differently then others" even though they are suppose to be the damn same thing . Hmmmm I wonder if Skynet is taking over ROFL !
Also I always though screen tearing occured when moving from one screen to another . This flickering was on the home screen .
I had the same issue with a custom or stock rom. Also, mine had a grey area on the screen that looked like there was water in it. So took it to sprint, it was something with the screen itself. Got a replacement screen in two hours and the same phone under warranty. And now on Myn's RLS5 and Netarchy 4.3.2 CFS- nohavs-nosbc. No issues.
It happens some times, no need to worry until it becomes consistent. If turning the screen on and off solves the problem for the day it is normal. Also, it might be a kernel with too much undervolting.
Sent from my PC36100 using XDA App
Ill reroot tonight and try a less aggressive undervolting kernel . It hasnt done it since I went back to stock so maybe it was the kernel and the undervolting
I have this same issue sometimes running myns with SBC Kernals. I noticed it doesnt happen when I flash and use an HTC kernel. Are these safe to use?
dw3bb10 said:
I have this same issue sometimes running myns with SBC Kernals. I noticed it doesnt happen when I flash and use an HTC kernel. Are these safe to use?
Click to expand...
Click to collapse
I have always ran SBC kernels with no issues . I did switch to a lower undervolting kernel from Net 4.3.1 cfs havs sbc . It fixed the issue , Im going to assume this kernel doesnt undervolt as much as the more havs kernel does .
Kernal for sure
I root phones all the time. After rooting and custom roms I put the most aggressive undervolting HAVS SBC I can find and install. The very first thing I do on the first boot after the new kernal is look for the screen issues you describe.
Sometimes they are wild and obvious and other times it is just a slight flicker and hard to see. Either way, it just means the undervolting is not jiving with the phone. Switching to "less" instead of "more" usually does the trick.
The crazy part it I can have two EVO's with identical hardware, software, Hboot, radios etc. and sometimes one will freak out on the kernal and the other loves it. Its a trip.
Related
I'm running Fresh ROM 3.1.0.2 w/ Netarchy/toast kernal BFS 4.1.9 - ever since yesterday night my phone has just slowed down to a bare crawl. Anyone have any tips/pointers?
NYCHitman1 said:
I'm running Fresh ROM 3.1.0.2 w/ Netarchy/toast kernal BFS 4.1.9 - ever since yesterday night my phone has just slowed down to a bare crawl. Anyone have any tips/pointers?
Click to expand...
Click to collapse
Are you overclocking? If it is set too high, the phone will lag and freeze. 998400 Hz is the normal stock clock speed.
It could also be the HAVS. I had bad lag with first iteration of HAVS in version 4.1.2.0. I have read others have experienced the same. Try flashing version 4.1.8.0 bfs and see if that doesn't help.
Sent from my PC36100 using XDA App
Re: Lag Issue
It could be a runaway IQFD process.
If i had to guess ti is probably the IQFD problem that many people (including myself) are having. currently i ahvent seena permenant fix but i ussually power down remove the battery put it back in and reboot and it seems to take care of it for a few days.
Maybe if more people start aving this problem someone will figure out if there is a way to prevent it.
rocketx86 said:
It could be a runaway IQFD process.
Click to expand...
Click to collapse
It most likely is.. for the time being I switched to Kings #6 and have no issues
yea i have it happen less with Kings #6 but it still happens it just seems to take it a while its weird. At first i thought it might have something to do with all the new fun stuff that was recently introduced (HAVS BFQ BFS SVS) but someone said they are getting this with a stock kernel if this is true then i am at a loss for what it could be. i know i never got this issue until the above was introduced.
Iqfd issues here as well. Sometimes simply killing all processes with SystemPanel works. Sometimes it doesn't so I have to reboot and pull the battery.
What is IQFD anyways??
...in 1943, I killed a drifter.
I had a similar problem with random lag and other unexplanable problems when using any bfs kernel I tried. Finally came to the same conclusion that a lot of others have come to. Bfs doesn't work very well, great for benchmarks, but sucks for everyday use. Since going to Netarchy's 4.1.9.1 cfs kernel I haven't had any of these problems.
felacio said:
Iqfd issues here as well. Sometimes simply killing all processes with SystemPanel works. Sometimes it doesn't so I have to reboot and pull the battery.
What is IQFD anyways??
Click to expand...
Click to collapse
I think it's part of an embedded software package that gathers information for HTC and Sprint on how and where we use our phones.
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.
Yesterday I put the netarchy havs less kernel on my phone and with some stress testing and general testing found that it worked well at 1.15 mhz. I carried it around all day messing with it no problem. Today, the real test came when I ran GPS on my phone in my car. The phone lasted about 3 minutes of GPS before it started rebooting. Then my 4g was broke from it somehow. Anyhow, I restored my phone and all seems well now.
I still want to mod the voltage and clock speed. Any advice on this? The phone always gets hot when I use GPS because it uses a lot of processor, frequently its on the charger and possibly in sunlight. When it was not overclocked or undervolted my phone NEVER reboots not once since I've had it.
Is the problem the undervolting, overclocking or both? Should i give up on this due to the way I use my phone?
Thanks in advance.
Try different kernels. I use netarchy sbc 4.2.2 more havs, works great. I also use his 4.3.4 more havs sbc. They both work for me. Battery life is awesome and gps works good. No prob here. Try those out and see what happens. Hope this helps.
Sent from my HTC EVO Phone, should'nt we all have one?
Okay so is there any danger to this? It seems like every time my phone starts rebooting from overclocking or undervolting apps start disappearing from my phone and stuff stops working.
I use amon RA 2.3 and every time I recover it works again but I was just wondering how dangerous it is for me to experiment they way I have been. I have already recovered my phone 3 times from issues like this that broke it.
Every phone reacts differently to kernels, undervolting, and overclocking so you will have to experiment to find out what works for you and what doesn't. Just make sure that you dont check the "set on boot" box until you know your setup is stable. A reboot shouldn't hurt anything though.
I am running Netarchy 4.3.4 more havs, overclocked to 1190 and it's as stable as can be on my phone. However, if I go over 1190 it immediately locks up and reboots.
Sent from my HTC EVO 4G with Tapatalk
kd0axs said:
Every phone reacts differently to kernels, undervolting, and overclocking so you will have to experiment to find out what works for you and what doesn't. Just make sure that you dont check the "set on boot" box until you know your setup is stable. A reboot shouldn't hurt anything though.
I am running Netarchy 4.3.2 more havs, overclocked to 1190 and it's as stable as can be on my phone.
Sent from my HTC EVO 4G with Tapatalk
Click to expand...
Click to collapse
Yeah but the reboots are hurting my phone! I have to restore it due to the problems the reboots and freezing causes (sometimes I have to battery pull due to full lockup). 2 times when I pulled battery due to full lockup apps went missing from phone memory but the available space on the phone was as if the apps were still there. Another time my 4g wouldn't turn on.
Is that abnormal? Can it mess up my phone in a way that recovering wont be able to fix or is recovering generally a sure shot?
The reboots should not be hurting the hardware, unless you overclock excessively. What the reboots are doing is corrupting your file system because open files do not get closed properly.
Are you after speed or battery life? I think the two are mutually exclusive. If you have great speed (be it governor or because of overclock), you will pay the price in battery life. I think the trick is to find the balance between the two that suits *you*.
gpz1100 said:
The reboots should not be hurting the hardware, unless you overclock excessively. What the reboots are doing is corrupting your file system because open files do not get closed properly.
Are you after speed or battery life? I think the two are mutually exclusive. If you have great speed (be it governor or because of overclock), you will pay the price in battery life. I think the trick is to find the balance between the two that suits *you*.
Click to expand...
Click to collapse
Because I use the 1-1-1 power management system (see sig) my main concern is performance. I love my phone and when I use it I want it to be fast and smooth. I would *prefer* if the extra speed didn't dramatically change my battery life but I'm okay with a small decrease in battery life if the speed gain is reasonable for the tradeoff. Anyhow I thought a lot of people ran HAVS along with overclocking to have both to a degree.
Only time I charge my battery is when I am using it in the car with my car charger. At home I charge all my batteries on an external charger - my phone is a mobile device I prefer to never be bound to a cord. I sleep with my phone next to me off the charger lol.
Okay so my phone is running more HAVS now and it seems the same as before so I guess my friend is HAVS friendly. I will run this for a day to check if any reboots happen and aim for tomorrow to overclock again. It may have been the 1.19 mhz that caused the issue. I will drop it down to 1.15 or 1.1 and see if its stable.
im not sure what to do at this point. the title says it all. i have already reflashed ive tried wiping cache and dalvik. i have tried both tiamat and savaged zen. ive tried different cpu governors. i just dont know what to do. my phone is running like complete crap and it randomly reboots.
a little history, i had the phone overclocked to 1.19ghz for all of 2 days and saw no inrease or decrease in percormance so i went back to 998mhz. the phone still ran just fine. last week i decided to attempt a undervolt. i got as low as 825mv before having issues, so to be safe i kept it @ 850mv. now it ran just fine for a few days but i started having issues with more cpu intese apps so i removed vipermod all together after setting voltage back to stock. thats where i am now. my phone has gotten worse and worse and worse and im just not sure what it is.
You can unroot it and run a RUU on it, taking it completely back to stock. If it's acting up with stock everything, then it must be a hardware problem. I would try that.
Lol I don't mess with over clocking . You can spank your phone. If its still doing that after you flash a regular ROM with the stock kernel then it is spanked. Best thing is wipe everything go to a ROM like cm7 run it stock no over clocking and see.
spencer88 said:
You can unroot it and run a RUU on it, taking it completely back to stock. If it's acting up with stock everything, then it must be a hardware problem. I would try that.
Click to expand...
Click to collapse
i have no idea what that means. ill have to look it up.
as far as the phone being overclocked im not to worried about it causing any damage. simply because increasing the clock freq wont cause damage unless it over heats. and i made sure it got nowhere near overheatig. the only way to damage a cpu by overclocking is to overvolt which i have never done. correct me if im wrong. not only that but the phone ran just fine overclocked and for a week after being set back to stock. i didnt start having issues until i tried undervolting. but that could cause any damage that i know of. however my experience is with overclockig computers not phones.
also i dont want to mislead youguys and make it seems like its worse than it really is. my phone is completely usable, its just sluggish and reboots randomly. im posting this on my phone right now.
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.