Related
I'm experiencing avery annoying problem with my phone. It's been happening for some time now, and I've tried all sorts of different things to fix it.
The phone completely randomly restarts, or just powers off totally. This happens at least a few times a day on average, and sometimes has a crazy spurt where it restarts itself like, 5 times in an hour. This is very annoying when I get my phone out to check if I have any texts, and it's totally dead or sat on the ChuckyDroid Winmo screen. People text me 3 hours later, asking why I didn't reply to their messages, or they have been trying to ring me!
I have tried everything I can think of. I have tried at least 10 different Android ROMS, and a few different Winmo ROMS. I have tried every radio from 2.08.x to 2.15.x and I have also Task29'd the phone, then started afresh. It still does it.
Any got any ideas what could be causing it? Is it possible it's a faulty battery? I am beginning to think this as it never seems to do it if I have the phone plugged into charge, either from USB or mains. If people think the battery is probably knackered, I'll go onto Fleabay and buy a new one, but I don't want to do this if people don't think that's the issue.
Thanks in advance... I hope people can help, as this issue is totally unworkable for me.
Cheers
That doesn't seem like a battery issue to me, rather SD related.
As you have already tried about everything: full formatting your SD card should fix it. There are some more advanced ways of formatting, in case the Windows (full! not the default quick) format still doesn't do the trick.
Hm.. I'm pretty sure I've run a full format of the SD card before, but I'll certainly do it again when I get in and test out the theory.
Thanks for your reply mate
I also had this problem(s) with Froyo... suddenly my phone rebooted...
However.. since i'm on Gingerbread... the problem didn't occur anymore..
Maybe you can try a Gingerbread build to see if the problems still occur...
I can give that a try too. I know there's a lot still to be worked on the Gingerbread build, but if it's more stable then that's good.
The MDJ Gingerbread build is pretty stable.
Well, thanks for your efforts guys, but no joy. I full formatted the SD, flashed 2.15.50 to my phone, then ran MDJ Gingerbread... I think it lasted about 4-5 hours before it started restarting itself again. So screw this, I'm going back to Winmo until NAND is ready. Winmo might be crap, but at least it's reliable. Totally pissed off now, to be honest.
After a few issues I was able to get Nebula ROM 1.0.7 up and running on my EPIC. I really like it so far. It is much faster then the other ROM I tried out, plus it doesn't have any of the cheesey sound efffects.
I have used it for a day with no problems. My battery was getting a bit low so I shut the phone down to change batteries. I put the new battery in and when I booted it up it just went into a loop with the Nebula animation, then the 1.0.7 screen would come up and then it would just loop.
I took the battery back out, reinstalled it, and this time it boots into the phone but everything FC's. Took the battery out again and booted it back up and now this time it loads up, some things run, but others FC...
I did the clearing of all caches and user data three times along with a dalevic wipe three times... What gives??
I consider myself a computer geek, but am definately new to the rooting/custom rom thing, so I am a Noob, be gentle!!
socos25 said:
After a few issues I was able to get Nebula ROM 1.0.7 up and running on my EPIC. I really like it so far. It is much faster then the other ROM I tried out, plus it doesn't have any of the cheesey sound efffects.
I have used it for a day with no problems. My battery was getting a bit low so I shut the phone down to change batteries. I put the new battery in and when I booted it up it just went into a loop with the Nebula animation, then the 1.0.7 screen would come up and then it would just loop.
I took the battery back out, reinstalled it, and this time it boots into the phone but everything FC's. Took the battery out again and booted it back up and now this time it loads up, some things run, but others FC...
I did the clearing of all caches and user data three times along with a dalevic wipe three times... What gives??
I consider myself a computer geek, but am definately new to the rooting/custom rom thing, so I am a Noob, be gentle!!
Click to expand...
Click to collapse
Firstly, I'm sorry for your troubles and welcome you to the ROM scene. But I would say posting this (or looking through) the Nebula ROM thread or posting this in the Q&A section would likely end up with better results.
Secondly, I also had experienced issues with Nebula ROM 1.0.7. My recommendation is to Odin all the way back to DK28, then work your way back up to Nebula. Also, try flashing Nebula twice onto the device to try to remedy any problems.
Another tip, it seems that if you are using things like Titanium Backup that there are instances of people running into problems of backed up apps causing problems. Starting new is probably the best bet.
Hope this was of some use!
Thank you for the help.. I posted this in General because every other day I see people getting ripped into for not posting in General, so to be honest I have been scared to post anywhere else... But I have read the Nebula thread, not all 110+ pages, but quite a few of them. I am going to Odin back to DK28, format my SD card, and start from scratch, then try reinstalling all of my Apps.
I just think it is wierd that it worked flawlessly for a whole day without one FC and then when I changed my battery it went to hell.
The even stranger thing is some apps work fine, and then others FC everytime. Seems to be no rhyme or reason..
Only other thing I am thinking is I installed a bunch of new apps today and wondered if that could be part of the problem...
Oh well, it has made me more aware of what is going on behind the scenes with my phone.
I could be totally wrong, but I think that's due to it being an ext4 with no journaling rom. Without that safety net its possble for data to be corrupted. sinse I switched to ext4 with no journaling I started letting the phone turn off instead of just pulling out the battery.
Like I said tho I could be wrong on this. Back when I was on the moment I had ext2 which doesn't have journaling either and if the data became currupted somehow, it would cause the symptoms you are explaining.
Sent from my SPH-D700 using Tapatalk
socos25 said:
Thank you for the help.. I posted this in General because every other day I see people getting ripped into for not posting in General, so to be honest I have been scared to post anywhere else... But I have read the Nebula thread, not all 110+ pages, but quite a few of them. I am going to Odin back to DK28, format my SD card, and start from scratch, then try reinstalling all of my Apps.
I just think it is wierd that it worked flawlessly for a whole day without one FC and then when I changed my battery it went to hell.
The even stranger thing is some apps work fine, and then others FC everytime. Seems to be no rhyme or reason..
Only other thing I am thinking is I installed a bunch of new apps today and wondered if that could be part of the problem...
Oh well, it has made me more aware of what is going on behind the scenes with my phone.
Click to expand...
Click to collapse
Ah, alright. I'm not too certain as I'm unaware of a good deal of the inner workings of Android, but I do hope things get straightened out for you. My phone still has some apps that act up sometimes, mostly JuicePlotter it seems.
Hanging arround... I forgot my last un and passwd(I had an htc tilt a while ago... now I can't post on dev forum...) to use 1.0.7 I think you need ext4 (at least I'm using it) some apps are giving troubles with ext4. So try one by one, and use the cwm3 backup system. At least for me is easier and safer than tit or backup pro.
Sent from my SPH-D700 using Tapatalk
I am so glad I didn't update to 1.0.7!
socos25 said:
After a few issues I was able to get Nebula ROM 1.0.7 up and running on my EPIC. I really like it so far. It is much faster then the other ROM I tried out, plus it doesn't have any of the cheesey sound efffects.
I have used it for a day with no problems. My battery was getting a bit low so I shut the phone down to change batteries. I put the new battery in and when I booted it up it just went into a loop with the Nebula animation, then the 1.0.7 screen would come up and then it would just loop.
I took the battery back out, reinstalled it, and this time it boots into the phone but everything FC's. Took the battery out again and booted it back up and now this time it loads up, some things run, but others FC...
I did the clearing of all caches and user data three times along with a dalevic wipe three times... What gives??
I consider myself a computer geek, but am definately new to the rooting/custom rom thing, so I am a Noob, be gentle!!
Click to expand...
Click to collapse
Sorry I missed this yesterday, but I wanted to say that I had the same problem updating to 1.07 and I had already gone back to DK28 stock w/ CWM3 before the upgrade. I also restored some apps and settings selectively using titanium. One thing that we may have in common is that I ran my battery ALL the way down accidentally after this upgrade, tried turning it on a couple times (and it would shut down right away) and when I plugged the phone back in I got the repetitive force closes when I tried to turn it on.
Anyhow, I recharged completely, started from stock DK28 again (and wiped the battery stats) and even with restoring the same settings from Titanium I have been running it for about a week now and it is rock solid. So, give it another shot and see how it goes...
The short version is I got everything working!! And Nebula 1.0.7 is the fastest rom I have used yet... But don't get too excited because this is only the third I've tried, and one of the other two is stock DK28.
What I ended up doing was Odin'ing back to DK28, installing CW3, and then doing the 3x3 clears. Then I also formated everything I could find in CW. Installed the Nebula Rom and still had an issue. Rebooted back into CW3 and then reinstalled the ROM again, and whalla.. It works.
I think for some reason you have to install it twice.. Strange I know..
I had force close issues as well, and all I did to fix it was go into CWM, and format/clear cache partition, and format/clear the dalvik-cache. Did this cache clear and dalvik clear 3 times.
coryshad said:
I could be totally wrong, but I think that's due to it being an ext4 with no journaling rom. Without that safety net its possble for data to be corrupted. sinse I switched to ext4 with no journaling I started letting the phone turn off instead of just pulling out the battery.
Like I said tho I could be wrong on this. Back when I was on the moment I had ext2 which doesn't have journaling either and if the data became currupted somehow, it would cause the symptoms you are explaining.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I second this as a possible problem. Shut the phone off 100% before removing the battery. On the moment that I also had if you removed the battery or used quick boot with ext2 you faced possible data corruption, but there were kernels that would check and fix data. You'd end up in a boot loop though if it didn't repair.
Sent from my SPH-D700 using XDA App
I've been making sure to shut it off before removing the battery, so far so good. I'm really liking this much better than stock.
Want to try a speedtest with the wifi tethering while going down th road.
I did a speedtest yesterday in my house and got 1.5mb DL, .5mb up. That was on my airrave though.
Sent from my SPH-D700 using XDA App
I have this weird problem, and I can't figure out the cause.
Whenever I use my phone lately, it will randomly freeze/force close certain apps. It's super laggy. If I drag my hand/palm across the touch screen, it will stop lagging and perform all the touch commands that I had "queued" up. This seems to persist even though I just wiped+flashed my phone again.
I've got nandroid backups for my stock hero, CM6.1.0, and now I just wiped and flashed to CM7.0.2. Sitting in the CM7.0.2 setup wizard as I type this, and it's lagging like crazy. Is it possible my Hero is internally damaged somehow and that's causing the problems, or does it sound like software? My Hero has been through a LOT of bumps, some harder than any phone should have to endure.
Still, I'm strapped for cash and making the best of what I've got. Anyone got any ideas? Is it possible that I screwed something up using the adb shell when I was a little nooblet? And that said, is there anyway to wipe everything and start with a completely clean slate?
rjhall said:
I have this weird problem, and I can't figure out the cause.
And that said, is there anyway to wipe everything and start with a completely clean slate?
Click to expand...
Click to collapse
I'm new here but I've had a lot of different problems also. What I do is RUU and start over. It fixes a lot of screwups on my part... if you have the problems after RUU with stock s/w then I'd have to say its your phone. Good Luck.
rjhall said:
I have this weird problem, and I can't figure out the cause.
Whenever I use my phone lately, it will randomly freeze/force close certain apps. It's super laggy. If I drag my hand/palm across the touch screen, it will stop lagging and perform all the touch commands that I had "queued" up. This seems to persist even though I just wiped+flashed my phone again.
I've got nandroid backups for my stock hero, CM6.1.0, and now I just wiped and flashed to CM7.0.2. Sitting in the CM7.0.2 setup wizard as I type this, and it's lagging like crazy. Is it possible my Hero is internally damaged somehow and that's causing the problems, or does it sound like software? My Hero has been through a LOT of bumps, some harder than any phone should have to endure.
Still, I'm strapped for cash and making the best of what I've got. Anyone got any ideas? Is it possible that I screwed something up using the adb shell when I was a little nooblet? And that said, is there anyway to wipe everything and start with a completely clean slate?
Click to expand...
Click to collapse
First when a rom is starting up, it's likely to be SLOW, for 2 reasons, kernels need to "warm up" and the market is probably downloading a crapload of apps (this is a new feature). Second, it sounds like maybe you're device is running low on RAM, I would suggest you get an app from the market called "autokiller" and set the preset called "optimum". Third, go into settings/cm settings/performance and then set your governor to interactive 352-691 or ondemand 264-691. Fourth, go read a LOT of the threads in here and learn some stuff that will help you. Fifth, what recovery are you using and what exactly did you "wipe". Sixth, what do you mean could you have messed something up with adb shell?
il Duce said:
First when a rom is starting up, it's likely to be SLOW, for 2 reasons, kernels need to "warm up" and the market is probably downloading a crapload of apps (this is a new feature). Second, it sounds like maybe you're device is running low on RAM, I would suggest you get an app from the market called "autokiller" and set the preset called "optimum". Third, go into settings/cm settings/performance and then set your governor to interactive 352-691 or ondemand 264-691. Fourth, go read a LOT of the threads in here and learn some stuff that will help you. Fifth, what recovery are you using and what exactly did you "wipe". Sixth, what do you mean could you have messed something up with adb shell?
Click to expand...
Click to collapse
1. Yeah I know that. I hadn't had this problem until the last couple months. Until then, it was more or less okay. The problem is, it really is a completely fresh rom.
2. The Hero is kind of a low memory phone to begin with, so that's certainly a possibility. 2.2 and 2.3 aren't exactly kind on old hardware.
3. I don't have those settings in 6.1.0. I was using SetCPU for awhile with it at 480-7XX (Can't remember, I think 791, as that was max) and OnDemand. I had some screen off, temperature, and battery profiles too.
4. Any specific threads I should read you can suggest? I was lurking on the forums for awhile before I did anything to my phone (didn't want to brick it).
5. I'm currently using Amon RA 1.6.2. I considered clockwork, but some people said it has more problems. I've heard complaints that Amon RA requires signed packages, but frankly it hasn't been a problem thus far. It actually saved me from bricking my phone when I was new to this whole thing. As for what I wiped, I simply went through Amon RA and wiped data, dalvik, battery stats and rotation. Don't know what battery stats/rotation are, but I am familiar with the Dalvik cache.
6. As for saying I could have messed something up, when I was flashing my phone, it was something I'd never done before. It's certainly possible I mistyped something or screwed something up.
I was hoping someone could help me to completely wipe it and start fresh, since I'm sure it's had its share of problems.
I would suggest flashing clockwork. You can wipe more areas of the system then the one you have. And it has more features. I personally made the switch.
As for your lag, it might be your hardware. If you did a clean install and wiped boot, system, cache, data, and dalvik, and installed the latest stable release and it's still laggy? Then things are not looking good brother.
You experience the same thing on a sense base ROM?
also it could be cpu govenors because usually by default most roms have it set to ondemand witch has always caused problems for me and as soon as i set it to performance its fine.
Bierce22 said:
also it could be cpu govenors because usually by default most roms have it set to ondemand witch has always caused problems for me and as soon as i set it to performance its fine.
Click to expand...
Click to collapse
Are you aware that the performance governor runs at the MAX CPU speed all the time? Seriously. Your battery life must suck.
sent from a series of tubes.
yea but otherwise my performance sucks lol.
most of the time on aosp and cm7 i cant even stream music without it freezing unless i set it to performance.
Houndog101 said:
I'm new here but I've had a lot of different problems also. What I do is RUU and start over. It fixes a lot of screwups on my part... if you have the problems after RUU with stock s/w then I'd have to say its your phone. Good Luck.
Click to expand...
Click to collapse
What is RUU? How do I do this? I tried to search the forums but it said search was unavailable. Would this return the phone to 100% stock, no recovery software or anything? That's really what I'd like to do now, to make sure there's not a trace of rooting or flashing left, that way I can start from scratch.
oohaylima said:
I would suggest flashing clockwork. You can wipe more areas of the system then the one you have. And it has more features. I personally made the switch.
As for your lag, it might be your hardware. If you did a clean install and wiped boot, system, cache, data, and dalvik, and installed the latest stable release and it's still laggy? Then things are not looking good brother.
You experience the same thing on a sense base ROM?
Click to expand...
Click to collapse
I tried using RomManager to flash Clockwork, and it still booted to Amon RA recovery. I'm going to try to use ADB to do it, but I don't know that I'll be able to.
EDIT: Manually pushed ClockworkMod Recovery v2.5.0.7 onto my Hero.
Before I touch any of these settings, what will format boot, format system, formata data, and format cache do? Can it brick my phone, or will it let me flash a ROM onto a completely clean phone?
hmm thats very weird thats just about the only thing rom manager is good for now adays is installing cmr
rjhall said:
Before I touch any of these settings, what will format boot, format system, formata data, and format cache do? Can it brick my phone, or will it let me flash a ROM onto a completely clean phone?
Click to expand...
Click to collapse
You will not brick, that is how you wipe. You should also wipe dalvik cache. Go to this site for really good instructions :
www.romrepo.info/wiki
But please note when u wipe u "wipe" lol you will loose all your market apps and anything else installed just make sure you dont wipe sd card then youll loose all your photos and music backups exc...
rjhall said:
What is RUU? How do I do this? I tried to search the forums but it said search was unavailable. Would this return the phone to 100% stock, no recovery software or anything? That's really what I'd like to do now, to make sure there's not a trace of rooting or flashing left, that way I can start from scratch.
Click to expand...
Click to collapse
So I downloaded the 2.1 update from the HTC website, ran it, and it completed with no problems. Phone booted up, and now I'm trying to go through the tutorial, lagging all the while. It's almost impossible to type.
Does this mean it's hardware related?
sorry for not posting sooner but lagg isnt usually caused by hardware the kernal probably has to worm up also is it the 2.27 software update or 2.3 because 2.27 lagged pretty bad anyway and if your typing with vibrate on keypress try turning that of it always helped me.
Bierce22 said:
sorry for not posting sooner but lagg isnt usually caused by hardware the kernal probably has to worm up also is it the 2.27 software update or 2.3 because 2.27 lagged pretty bad anyway and if your typing with vibrate on keypress try turning that of it always helped me.
Click to expand...
Click to collapse
I had to start from scratch several times and my phone was pretty snappy when I first started it up after RUU. Also you stated your phone was fine and then just started running slow for no reason, was this after it took a bump?
are you talking to me or rjhall lol
Bierce22 said:
are you talking to me or rjhall lol
Click to expand...
Click to collapse
sorry, RJhall..
I don't recall it taking any bumps before it just stopped working like it has.
However, I have found how to "fix" the problem. If I squeeze the sides of the phone in, it stops lagging and works. Any touch motions of queued up will then immediately execute. Any idea what in the phone is physically broken?
rjhall said:
I don't recall it taking any bumps before it just stopped working like it has.
However, I have found how to "fix" the problem. If I squeeze the sides of the phone in, it stops lagging and works. Any touch motions of queued up will then immediately execute. Any idea what in the phone is physically broken?
Click to expand...
Click to collapse
Never had mine apart, maybe someone has and can help..
Okay so things have gotten increasingly weird. It used to be that squeezing the sides of the phone allowed the touch screen to work. Yesterday that stopped working altogether. Today, the screen stopped turning on at all. The LCD simply doesn't turn on. Pressing the red button turns on the phone (it vibrates when turning it on) and when the phone is on, pressing the red button lights up the keys (so I know it's waking the phone up). I took the phone apart (much simpler than I thought it would be) but I was unable to find anything that seemed out of place or broken. Does anyone have any ideas?
A Little History: :silly:
I have been running i9220ZCLP1...known bad kernel since whenever it was first available, April I think. Anyways, acquired that through flashing Rocketrom v5, according to the instructions provided at the time. Everything worked fine, other than contacts crashing and the wlan some times not enabling until reboot...common issues, as far as I've seen on these forums. One thing to note, is that unless the instructions at the time asked for a full wipe after flashing 5 (I'm almost certain they did not), then there has not been a full wipe performed while in this kernel.
The current issue:
The other day my phone froze on me...months after flashing and having used this kernel, waiting for something more solid to come out. After it froze...holding the power button turned it off, but the phone would not boot afterwards...to ics, to recovery, to download mode, nothing.
After some fiddling, I realized that it will charge and once it buzzes and the screen comes on showing a full battery, I can turn the phone on and it will boot...then freeze after getting past unlock screen. Or freeze and go black in download mode...didn't try recovery, wasn't interested in it at the time, but I'd imagine the same.
After removing the battery for a few days, then plugging it in til full charge notification, I was able to get it to boot again, where it froze at the boot screen, but went dark. After one more full charge...oddly, like a minute later, it booted to ICS fine and worked for 24 hours or so.
Now:
With a mind to flashing away from the bad kernel, I restarted the phone tonight from the menu in ics... it booted fine, so I left it plugged in to get a full charge and came back to a phone, screen still on, that shows same battery % as when I left it. And I'm back to where I started with this problem, powered off after holding power button a few seconds and now nothing.
Waiting for a full charge again, to see what happens...I'm guessing/hoping I'll be able to get it to boot again, with some more fiddling...
My question is whether this sounds like it's hardware (battery etc) or software (bad kernel etc) that is causing the problem.
If I can get it into download mode...plugged in, obviously, should I try OdinPC to a safe kernel?
Thoughts would be awesome. :fingers-crossed:
How about flashing stock GB via pc odin first and getting safe?
apurvapatel said:
How about flashing stock GB via pc odin first and getting safe?
Click to expand...
Click to collapse
+1 I've read a few people on ICS having charging/battery related issues over time. Worth seeing if it still happens on a gb kernel.
Sent from my GT-N7000 using xda premium
apurvapatel said:
How about flashing stock GB via pc odin first and getting safe?
Click to expand...
Click to collapse
OK, that's one vote for flash if I can get it running again. Thx, glad you read my post.
SpyderTracks said:
+1 I've read a few people on ICS having charging/battery related issues over time. Worth seeing if it still happens on a gb kernel.
Click to expand...
Click to collapse
Hmm, but how to get there...GB and all.
So now the vote is software. Any idea why this would happen much much later? No battery issues at all, just suddenly.
Maybe I'll buy a battery.
nebreprah said:
Hmm, but how to get there...GB and all.
Click to expand...
Click to collapse
A little searching would show you DrKentan's guide @ http://forum.xda-developers.com/showthread.php?t=1424997
I'm have troubles with my HD2 randomly rebooting itself for apparently no reason. Initially I had a barebone CM7 ROM, and it seemed to reboot much more frequently when I came home from university. As soon as I got home for this break, sure enough, it began rebooting again. I then switched to a CM10 ROM, thinking it was just the previous ROM messing up, yet the problem persisted.
If it's not a ROM causing it, what could it be? It's really annoying having the phone shut off randomly while I'm doing something, and I'm worried it'll end up worse just because of how frequently it reboots.
overheating? failing touch screen? dodgy battery? failing hardware? faulty/fake copy SD card? old/wearing out sim card? some app that doesnt play nice on the hd2?
they can all cause reboots on multiple roms, along with another half a dozen reasons, i'm sure.
If the phone did reboot from any of those, it still wouldn't explain why it doesn't happen when I'm at school. I'm not exaggerating; once I go back (about ~126 miles away from home), it never reboots like this. At this point, you may be thinking, "Why not just wait to go back?" I have only two semesters left, and I want to get this fixed prior to me moving back here.
But nonetheless:
overheating?
Click to expand...
Click to collapse
I've held my phone in front of an AC to test if it's overheating, and it still rebooted. I had the back cover off and the air blowing into the battery.
failing touch screen?
Click to expand...
Click to collapse
My 'End' button is failing, but my touch screen seems to work just fine. Is there a way I can test if it's the touch screen causing the reboots?
dodgy battery?
Click to expand...
Click to collapse
I have two batteries, one original and a new from Amazon. Reboots occur using either of those.
failing hardware?
Click to expand...
Click to collapse
Quite possible, it's an old phone, but I feel that it would reboot regardless of where I'm at if this was the case.
old/wearing out sim card?
Click to expand...
Click to collapse
Same as above.
some app that doesnt play nice on the hd2?
Click to expand...
Click to collapse
I thought this was the case at first as well, but I uninstalled all my apps on the barebone CM7 ROM, and reboots still occurred. Even after doing a fresh install of this CM10 ROM, the phone rebooted before I even began installing apps to it.
Are there any files that don't get changed by flashing a new ROM? I was thinking that it could possibly be the modem I have flashed to my phone, but I wasn't sure if flashing a new ROM automatically changes the modem as well. Can I get some insight on this?
By modem do you mean the radio? It's unlikely to be the radio itself, however it could be something like the phone struggling to switch between 2g and 3g,,try it with the phone in only 2g mode,, perhaps you have a faulty cell tower in your area,,unlikely but not unknown.
Yeah, sorry about the terminology haha. But thank you, I'll try that and report back!
So disabling the 3G didn't change anything, but I noticed a drop in the frequency of reboots when I disable my wifi. Could some of my router settings be messing with the phone? I tried deleting the network on the phone and re-adding it, but the reboots remained consistent.
adobrakic said:
So disabling the 3G didn't change anything, but I noticed a drop in the frequency of reboots when I disable my wifi. Could some of my router settings be messing with the phone? I tried deleting the network on the phone and re-adding it, but the reboots remained consistent.
Click to expand...
Click to collapse
still sounds like hardware really, as suggested.
does it reboot even with the phone in airplane mode?
But the phone doesn't reboot when I'm in the city where my university is located, only when I come back home. That doesn't really lead me to believe that it's the hardware.
I have the same problem with the
[1.Dec.2012][All in One] EvoHD2v10 ICS 4.0.4-full HWA "Fastest ICS ever"
it reboots more than 3x a week!!!!!!!
For me, it can literally get up to 10 reboots per day, when I'm in this particular city. It gets very aggravating, and I'm worried about the stress it's putting on the hardware by constantly booting back up.
Anyway, I decided to say **** it and start from scratch. I don't think it's a hardware problem, so I decided to go back to the beginning. I formatted and re-partitioned my SD card for Native SD-compatibility. I flashed Xylo's 4.1.2 PA ROM. Now it's time to use it like I would normally.
If anyone is experiencing the same problem as me, or reads this in the future with the same issue, I'll try to keep the post up-to-date with what stopped the reboots for me.
dont forget to clear out your sd card, , leftovers from previous roms can cause issues. Easiest way is to flash teh new rom, then immediately in CWM do a wipe data/factory reset, as this clears out both fat32 and ext folders.
AW: [Q] Can reboots be caused by location?
I had the same problem with my fathers HD2. I installed clK before and it rebooted the last time quite often.
So I reinstalled everything. I started installing the official HTC WinMo 6.5 Rom.
Then I've done Task29 and installed MagLdr and then a Radio which Supports 576 MB Ram. (I think it was 2.15.xx) , repartitioned it for BlueOrange Mix Rom 1.2 (The best I ever installed so far) and flashed it in CWM.
So the HD2 is running since 150 Hours without any Problems.
P.S.: Task29, MagLdr, Radio Installation and Repartition has been done in HD2 All in one Toolkit.
Greetings by Myself5 and I hope I could help you.
Sent from my GT-I9100 using xda premium