this happens after i overclocked my xperia arc s to 1.8ghz., 2.3,4 arconium rom, doom kernel v22, now after booting the device and when the menu shows up my phone turns to black and then restart. i already flashed the 2.3.4 rom. i dont know what to do. -_- please help.
and when i run sus it says the phone contains modified software that cannot be updated.
Too high OC.
1.8 GHz is obviously way too high for our phones, excessive clock setting causes the restart. Be happy, that it only started to do restarts. Otherwise the CPU could have melted and the phone would have been hard bricked due to hardware damage.
Flash stock kernel, should make the OC impossible, thereby no restart should occur.
I already flashed stock rom. but everytime the menu shows my phone restarts. -_- this sucks
yeah.. i think the oc was too high.. maybe it's the hardware issue..
i fixed it. i think the battery was loose a little so i tried putting paper to make it tighter. now it doesnt reboot everytime i open the phone, but i still experience random reboots. maybe 5-10x a day. -_- this phone sucks
bruts12 said:
i fixed it. i think the battery was loose a little so i tried putting paper to make it tighter. now it doesnt reboot everytime i open the phone, but i still experience random reboots. maybe 5-10x a day. -_- this phone sucks
Click to expand...
Click to collapse
This phone doesn't suks, your way to do things suks ! How could you think to maintain a stable overclock so high! Our phone cpu max tollerance in overclock is 1,6ghz stable. At least you could try to undervolt a little bit before to do that. Thinking mind is always the most important requisite.
^^ He's right
Maybe you didnt do a propper flash (wipe everything) and still are some scripts running and overclocking it again every boot
If not, then yes, you had probably damaged your phone.
my phone doesnt reboot now, putting paper on the battery fixed it. no more random reboot. running 1.7ghz stable oc.
Related
Hey guys,
i got stable hung ups in 3D intense games (asphalt5, dungeon hunter 3D, crusade of destiny)
some 3-10 mins of play and bang! you got complete stall - have to plug out the battery to reboot.
all other games (2D arcades, tetrises, arcanoids, pacmans) are working quite stable.
i've already tried almost all available ROMS (except stock non rooted one, btw - i dont want to update HBOOT to 0.8, full reset with wiping all the caches inc. dalvik and ext3 part before each ROM.)
pays ROM (several vers)
MCR r2-r3.1 (with richard's kernel either with OCUV or with OC only or without any UVOC and with original MCK 1.1 kernel)
amer_mod des final
all are behaving the same....
what the heck? My phone is generic and certified for Russia (PCT) and it's from white shipment.
the only idea i have is slow SD, cause i use the one which was with the phone - 4GB class2 SD.
please ideas? i wanna play some time not only tetris!
just noticed one moment. it happenes not only in 3D games, it also happenes when using the phone intensively, i.e. now I got stable instant reboot when using internal browser (even with pictures and flash turned off) and opera beta for android. the most interesting part is that just before reboot the back bottom part of the phone becomes noticeable warmer, let's say about 40°c and then instant reboot. (just as it is in 3d games) I use Richards OC only (no UV) kernel v14 with Max freq. set to 998 and MCR r3.1 (everything was wiped upon flash)
Re: Stable HangUPs in 3D CPU intense games on all ROMs
Maybe its some kind of thermal protection of the cpu?
-------------------------------------
Sent via the XDA Tapatalk App
i thought so too...
does any one knows some king of CPU thermal monitoring tool with logs for android?
Happens to me as well. The phone heats up like crazy particularly on badly coded games like the ones gameloft released. For example polarbit's armaggedon squadron runs perfectly well for any amount of time but realfootball for example causes the phone to overheat.
They really botched their ports.
just did a thermal monitoring with tempmonitor lite - but on Desite it only monitors BATTERY temp - it's about 32-33 degrees - so far i found no CPU temp mon which works. and still phone reboots during hard flash playing in about 10 mins with battery temp about 32-33 degrees. i also noticed an infinite boot loop when turning on the phone with AC plugged in. (it starting to load sense and just after SD card preparing notification STABLE instant reboot, though it may not be related)
will try to use stock ROM today (i still have the very first nandroid backup)
Try to uv without oc...should get the temps down.
Any of you guys still experiencing these problems? Have an untouched desire (sim free) that hasnt been unlocked or rooted and sometimes (although rarely) the phone just restarts itself.
Prema999 said:
Try to uv without oc...should get the temps down.
Click to expand...
Click to collapse
UV only kernel reported to have some stability probs....
when u use OC only kernel and, as in my case, set up max. freq to 998 it literally means that you just dont user any OC. so overclocking is not the issue...
jaymit said:
Any of you guys still experiencing these problems? Have an untouched desire (sim free) that hasnt been unlocked or rooted and sometimes (although rarely) the phone just restarts itself.
Click to expand...
Click to collapse
My phone reboots when I'm playing robo wars, when the battery is LOWish and Im charging the phone at the same time. No battery warning, just reboots. If I have a good charge on the phone, and am charging then it seems fine. This is NOT a lock up, like the original thread starter, but a straight old reboot... Annoying, but I dont play robowars when there is low charge from now on!
gunja99 said:
This is NOT a lock up, like the original thread starter, but a straight old reboot... Annoying, but I dont play robowars when there is low charge from now on!
Click to expand...
Click to collapse
i got complete lock ups with only one game (heard rumors about it's bad coding style) the rest issues just reboots the phone. also i noticed that it reboots more frequent when using the phone and it's connected to charger simultaneously.
!!!UPDATE!!! 27.06.10
got back my Desire from the service after 10 days. They've changed motherboard (IMEI also changed) and no more overheating problems!!! HOORAAAY!!!!!!
It's working now even under high load!!!!
Problem with the phone, when i go to unlock it sometimes, the screen will stay black and then just suddenly do a hard boot quite annoying! Sometimes it happens once a day or sometimes everytime you unlock it.
Any suggestions?
Using cyangen 7 mod
Thanks
Well these problems are always hard to solve, but I have a few suggestions. First of all, try running 1 GHz with performance governor for a while. It is not good for daily use because of big battery drain, but if it solves your problem, then the issue is in your kernel.
Transitions from low power state to fully awake state in a CPU require good stability, as the voltage jumps nearly at the same time as frequency. If your CPU struggles when you use your current voltages, it might just be unstable enough to cause a fatal error when you unlock your device.
Hi guys,
Hoping you all can help me. I installed Vipermod and undervolted 50mV. Running MIUI 1.7.22 with Tiamat 3.3.7 SBC. Also have SetCPU runnings with various profiles. Whenever I turn my phone on it'll work for a little bit and then freeze or restart itself. Should I just nand backup to without the vipermod, or is there a way for me to edit a script with the settings to remove the undervolt setting. I'm afraid of running a nand backup and the phone freezing in the middle. Thanks, appreciate any help.
As long as you have a full charge, a nand restore is usually a pretty fool proof way to fix any problems.
That vipermod is something most kernel devs don't mess with because of exactly what you are saying. There is some benefit if you can get it to work flawlessly, but it's hard to get it to do that.
I recommend a complete wipe, then restore your last nand. Again, just make sure you have plenty of battery whenever you restore a nand backup. The only thing that can really completely brick your phone is if it dies in the middle of doing something like that.
Here's Viperboys BSM_PSM_reset script, flash this in recovery if you get stuck in a bootloop.
Also, if you have the updated setCPU, goto the main screen and press menu, you'll see an option to download their "safe mode" zip file which you also flash in recovery
The BSM_PSM_RESET zip restores your kernel to its default settings, the setCPU zip you download restores setCPU to default settings as well
Viperboys BSM_PSM_RESET zip:
http://db.tt/5sHGbaY
Sent from my PC36100 using Tapatalk
I believe this is heat related!!! I am getting intermittent, but daily reboots and every time the phone feels hot. Usually I get the reboots whenever the phone is working hard, playing a game or using google maps. I always wipe EVERYTHING when flashing roms and the last two day I decided to do some fresh installs of AOSP and quality Sense roms(all GB) and I didn't load any new apps after install. Guess what!?!?! Still getting reboots and the phone is hot when it reboots. I then pull the battery cover and put it on a cool spot or in front of the AC and it boots and runs great as long as it is being cooled. I've been a huge HTC and Android supporter since day one, but at 13 months old I shouldn't have to deal with this especially when I baby the phone. I hate to say it but I may have to switch to the evil empire. Their phones just work and keep working, oh and their battery last all day, maybe two days on one a single charge.
If you read this post because you are having the issue please make note if the phone is hot when it reboots. Allot of people believe this is software related, I on the other hand believe it is heat and hardware related. Unfortunately I refuse to lose root and go return mine... UGH!!!
No offense, really, but I do NOT understand SetCPU. People use it to overclock, for what reason?? Are you planning on Playing COD BO on your phone?? Or do rocket science?
Is anybody else having issues with their ET going to sleep and you have to pull the battery to get it come back up? I thought it might have been my setcpu settings. So I cleared them and uninstalled it. I tried the midnight rom and the starburst rom. I tried the stable and exp LosKernel. None of these got rid of this issue for me. Randomly through out the day I can try to wake the phone up to use it and nothing happens. After a minute or two I have to pull the battery. I am currently testing the stock kernel.
Thats weird, the only time that happened to me was when i had setcpu, and i tried putting "screen off" value to 200/200.
You should install setcpu again, and make screen off value 500/500, and if you dont have the issue, then try making the value 200/500, if you dont have the issue at this value, then leave it as is.
Sent from my SPH-D710 using xda premium
I agree it is weird and I am not sure why it is happening. If it stays okay with the stock kernel then I may wipe and try the viperrom.
Yep happened twice the other day... Im on stock rom with lost kernel..roooted i put setcpu to 200/1200 after waking my screen for a minute used google came back 3 min later and phone was either off or wouldnt wake .. I had to pull battery twice.
I setcpu up to 1200/1200 never happened again.
This is a nice phone but very touchy.. Seems alot weird things goin on for some Et users.
Worst of all for this phone is Los or just weak /radio signal in general ..which is a samsung issue.
Sent from my SPH-D710 using XDA Premium App
Why people still insist on screen off profiles amazes me. When you hit the power button to wake it - the phone is stuck at 200MHz, you do realize this? If snything else is going on while it's stuck at 200 or SetCPU doesn't sample the phones state fast enough, it never gets out of 200MHz and locks up. Just like any other processor does when you overload it.
All the background processes going on even when the screen is off and somebody thinks setting the CPU max to 200MHz is a good idea? That's just asking for it. Not to mention the screen off profile is known to cause this issue. Notice how Virtuous, Viper, Cyanogen, and many other developers don't use one in their native OC daemons? There's a reason why. The phone sleeps just fine without it, just let it do it's thing.
Don't use offscreen profiles (the kernel is smart enough) and avoid using task killers, as those are likely to be the second leading issue.
I am having the issue even with setcpu uninstalled. I still have not found out what is causing it.
ElAguila said:
I am having the issue even with setcpu uninstalled. I still have not found out what is causing it.
Click to expand...
Click to collapse
Just wanted to throw this out there: beware mislabeling this problem. The setcpu issue causing the phone the permanently lock up and require a bat pull is one issue, yes; slow screen wake up is a different issue. Sometimes if you hit the power button, the screen will not wake up on the first try. If you wait a few seconds and push in the button again for a second or so, the screen almost always will come after. Coming from a mo-pho, I actually had the stupid no-wake problem requiring bat pulls, so I'm extremely paranoid about by e4gt doing this -- but it really has been good about eventually waking up every single time...just try my instructions and see if it works for you, too.
Again, though -- setcpu issues may be a different problem entirely.
did you reinstall a rom and try it again or did you simply just unistall setcpu and try it. I say this because I had an issue when testing setcpu and my system still kept my cpu setting even after I unistalled the app. I had to reinstall the rom after wiping to get it to run properly again.
I think I have found the issue. I did a factory reset and installed the rom but I am getting an error now that is basically saying it can't read the internal storage card. So I think there are some actual hardware issues going on that need to be looked at by sprint.
how often has the sod been happening? I think i got it yesterday, but not sure.
Do you use setcpu?
Sent from my SPH-D710 using Tapatalk
This thread seems a little slow- has there been a solution found or are we isolated cases?
I reflashed the phone back to rooted stock and then flashed Blazer 4.1.
Got 2 SODs in the past week- one just a few minutes ago.
I tried calling the phone from another line, it rings but the screen is black and thus I couldn't answer it.
Power button and vol buttons work fine.
I had to powerdown and reboot.
Getting kinda frustating.
I've been having this problem for some time now and let me tell you, it is so god damn annoying.
For some reason at least once a day the phone just constantly reboots by itself in a loop until the battery is pulled out and put back in, then the next day it just does the same old thing.
I know for a fact it is not kernel related because I've tried Franco, AK, and Lean Kernel, all have the same issue.
I've also tried stock rom and Xylon rom.
I turned off SR and the problem is still there, no underclocking no undervolting, completely stock rom/kernel.
Does anyone know how I can fix this? Is this app related?
Any help would be appreciated.
Thanks
I can see how that would be very irritating. There are a lot of possibilities for the cause, but I think the first thing I would do is use Trickster app or equivalent to set my cpu frequency down to about 1000 MHz and see if that makes it stop rebooting for a few days. If so, then you might have a device that can't tolerate a normal level of heat. In that case I'd try to get it replaced, or just live with a lower maximum frequency. Or you could try turning up the voltage for 1200 MHz a little, maybe 10 mV, and see if that makes it stop.
If neither of those worked, I would start looking for a rogue app or leftover script from a previous installation. Try wiping /system as well as cache, dalvik, and factory reset next time you install a ROM.
I guess I figured out the problem.
This only happens if I restart the phone while it is connected to the charger.
Sent from my Galaxy Nexus using Tapatalk 2