I am getting random reboots and I am unable to figure out what is causing the problem and I have not found any thread about random reboots with the Captivate.
haojan said:
I am getting random reboots and I am unable to figure out what is causing the problem and I have not found any thread about random reboots with the Captivate.
Click to expand...
Click to collapse
Provide us with more information. Is your phone rooted, on a custom ROM maybe, what have you been doing to your phone, when did this start happening, etc.
History
I started with stock, rooted, non-market apps, unhelpful kernel v1.2, removed AT&T bloatware. LCD density @ 180. Tried One Click Lag Fix v1.0 and v2.2 and uninstalled. Juice Defender to manage 3G. Juice Plotter to track battery.
After messing around with it, I encountered a reset of the default launcher selection each time I long pressed the home button to bring up the recently used programs. I then did a hard reset and that fixed that problem. After the hard reset, my Captivate ran great! I found it responsive and fast enough without the need to try and apply any lagfix.
I then reinstalled my selected applications. My phone started to randomly reboot about once a day. I noticed Juice Plotter's data would be lost and it had to rebuild. It also happened to reboot on me once while I was using it. Other than that, it has not really affected my usability.
If it hasn't affected your usability, do you want to fix it?
If you do want to fix it, then the best way is to restore to Stock and add things slowly until you determine the problem. If you return to Stock and it still reboots, then you have a hardware issue.
It doesn't "quite" affect usability but it is not working "normally" either.
Was hoping to see if anyone else have experienced random reboots and how to troubleshoot it. If not, I will try out Odin one-click flash to stock...
I've been searching this form for an hour or two now and still haven't found my issue, so here goes.
Just got an HTC Inspire 4G off of ebay and it arrived today.
The seller had mentioned that the phone was freezing / rebooting, but I figured.. that's because he's not running cm7, right?
Charged and booted up the phone and it turns out that the problem was a little worse than I first expected. I only experienced occasional freezing, and it only rebooted once, but there is a worse problem.
The phone loaded up fine, looked good, but tapping around on the home screen I got messages alerting me that system apps (htc sense, launcher, and even com.android.phone) had stopped responding or had shut down.
I hit the menu and go to settings. I scroll down the list and the entire list goes black. I hit home and it goes to a home screen, but with no launcher or icons. Basically, every few taps, the interface goes out. If you are on a menu it blacks out, if you are at home or press home after the menu blacks out you will get anywhere from pieces of icons / widgets to just a blank desktop. The live wallpaper even keeps going, but all of the interactive stuff quits. The disappearing menus didn't usually give app closed messages, they just went black. The home screen only gave app closed messages sometimes.
I thought this was a software problem, so I managed to root the phone and flash cm7. Everything booted good, but it still had the same problem of weird disappearing menus and home interfaces. I went ahead and flashed gapps and got the little intro thing about setting up my Inspire 4g that starts when you first boot your phone. I clicked through that but when it gets to connect wifi, the phone entirely freezes and I have to pull the battery.
I flashed inspiremod and nothing changed, tho that's for something else, so I'm not sure that's entirely relevant, but I was trying everything I could think of.
I'm definitely no expert on hardware, but it almost sounds like a ram problem, like it doesn't have enough to keep all of the interface going all the time and shuts it down or shuts parts of it down to work.. but I don't want to believe that. I'm really hoping that it's a software problem.
I got the phone at a good price and it came with an otterbox, so I won't be too disappointed if I can't get it fully functional, but it would still be a bummer.
Any help / advice / suggestions appreciated. Thanks, guys!
EDIT: I cleared the cache / dalvik cache before flashing / reflashing cm7, which I did once or twice
EDIT 2: Now if I leave it on the intro screen where it freezes it reboots after a minute or so. Gonna try flashing a different mod.. see if that helps.
That was a long post. But it was good, you gave a lot of info.
The cm7 zip that you downloaded, check the md5 checksum, make sureit matches whatever is in the op (first page) or wherever the md5 is, maybe where you downloaded it from. If it doesn't, download again.
Then,
from recovery,
Wipe data/factory reset.
Wipe dalvik
Format all partitions(except sd card)
Flash zip/rom.
Check if it works. If not, try using it without the sd card. If not, come back and report.
Sent from a dream.
Thanks for the reply and suggestions.
I check the md5, and it's good. I just did a factory reset and wiped cache and dalvik.. I'm unsure what you mean by format all partitions except sd card. I don't think I know how to do this with clockworkmod.
Started up without sd card and it still has the same problem. Looks great until I touch the screen, then everything disappears except the wallpaper.
Reboot in recovery and do it from there. You'll find format all partitions at the bottom... well, maybe. Cwm has an option to reboot in recovery, and I think if you press and hold the power button, select reboot and it will also ask you if you wantto boot into recovery. Cant remember if cm7 has it, it should.
After you wiped those, flash the rom. Stay in recovery and search for fix.permissions. Reboot.
Sent from a dream.
Just did that and re-flashed cm7, but the phone was still having the same problems.
I then repeated the process with a MIUI ICS rom and it seemingly worked for a little bit. I got a "Maps has stopped working" message, but I was able to slide back and forth through the home screens, and the menu came up. After I tapped though the menu a bit it started being weird again, but with MIUI the weirdness is different. It looked like the screen was divided up into 20 something smaller screens tiled across the display with messed up looking bits of screen in them.. weird..
If you are wiping correctly then I am out of ideas. I would say try a GB rom, however that is a strange issue and just might be a hardware problem. Tough, Im not sure.
Sent from a dream.
I've tried cm7, which is 2.3, and I've tried a 4.0.4 MIUI build and one other sense rom that didn't work well at all.
I'm wiping and flashing the same as I did on my LG p509, which works beautifully with cm7.
If it is hardware, hopefully it's something simple like the battery, and not bad RAM or anything serious..
Maybe if I keep at it I'll get it.
Thanks for all the suggestions!
Np. Keep us updated.
Sent from a dream.
I ordered a new battery for it, and that fixed the random reboots, which had been occurring more frequently, but the other problems were still there.
I flashed and re flashed and formatted and reinstalled a bunch, but still no luck. I then decided that I might take it by the local cell phone repair shop and see if they could fix it.
In preparation, I used aahk to flash the stock ruu with everything how it was when I got it. After booting it up, it seemed to be working ok.
I still get the occasional menu glitch, but it's so infrequent it's not an issue.
The phone still freezes up quite a bit when I'm using it, but it's nearly a useable device now!
awkwardcheesecake said:
I ordered a new battery for it, and that fixed the random reboots, which had been occurring more frequently, but the other problems were still there.
I flashed and re flashed and formatted and reinstalled a bunch, but still no luck. I then decided that I might take it by the local cell phone repair shop and see if they could fix it.
In preparation, I used aahk to flash the stock ruu with everything how it was when I got it. After booting it up, it seemed to be working ok.
I still get the occasional menu glitch, but it's so infrequent it's not an issue.
The phone still freezes up quite a bit when I'm using it, but it's nearly a useable device now!
Click to expand...
Click to collapse
Have you tried changing out the sd card? Having a bad sd card can cause all inds of odd issues
I booted it without an sd card before and couldn't tell the difference, but it had a lot more issues than just freezing then.
I haven't tried it since those other issues have stopped. I'll try that when I get home from work.
First thank you for reading my long post. Any help would be appreciated.
I have random reboots issue,
I updated to Jelly Bean the first day my tablet arrived, so i do not know if this is because of Jelly Bean or hardware problem. I need to know the cause so i can decide whether return it and get a replacement or not.
Sometimes it does not reboot at all, but sometimes (or usually i'd say) it reboots a lot, like every 2 minutes. Sometimes it reboots every 30 minutes. Well it's just random.
After doing factory resets and cold boots with no luck, I figured out why it reboots: If it's doing something "heavy" (like loading a webpage, syncing emails, loading games, installing apps,...) and I touch the screen many times (say 5 times) while it's doing these "heavy" things it will reboot.
Why do i need to touch the screen many times while it's loading,... Because for example: you load a webpage, while loading you scroll down to see the content of the webpage, but because the browser is slow, you feel like you need to touch again, and that causes it to reboot automatically. I also do another test: It was installing Amazon Appstore, while installing, i touch the screen many times, and the reboot happened.
Factory resets or cold boots will not help. it's just like that, i think it's supposed to force close or something, but it doesn't, it just reboots. I tried to treat it "gently" (i wait until the loading is finished, then i scroll down webpage,... and i don't touch the screen when it's loading), it did not reboot. But sometimes it do what i expect too (show force close, wait message).
Is this a jelly bean problem or hardware problem? Can anyone test this? Should I return my tablet and get a replacement? (I guess if i get a replacement i won't install JB, that would be safer lol)
Agree with the above. Replace it asap. I cant remember my tablet ever rebooting
ok since yesterday it "only" rebooted 4 times, probably because i "treated gently" most of the time, and of course the times it rebooted were the times i touched the screen a lot.
so i'm returning it. now there's a question in my head: should i return it and get a refund, then buy another tablet, (or maybe wait until another tablet come out) or just get a replacement? i'm just thinking this is a $400 tablet, is it too expensive NOW? (looks like everything in tech is getting cheaper lol [like the nexus 7 or kindle fire hd, maybe ipad mini too])
I've recently been having all apps on my phone close frequently. No error messages or anything, just close back to the home app (which happens to be repopulating widgets and such suggesting that it was closed too). For the life of me I can't figure out what is wrong. Once I see it happens I know my phone is unusable except for the basics until I reset it. At first it was mildly annoying, but it has been happening faster and faster after each reset. First a reset grabbed me a few days, now only about 4 hours. I tried a factory reset but it was only mildly better. Finally in desperation I tried using mattlgroff's "DROID RAZR HD Utility" to reflash stock, but that only bought me a week and a half.
Does anyone know what might have caused this? The only significant mod I made to my phone was rooting it while it was new to use Titanium, then I unrooted it and it was fine for several months after. I can't think of anything I had done outside my normal use before it started. I tried looking at logcat but I wasn't very good at sorting though it. Found the lines stating the apps were closed/services were restarting, but nothing else looked abnormal to me.
Sounds like a hardware issue.
Try a safe boot
Power up
At the appearance of the bootlogo, big m or warning, press & hold the vol down all the way home.
Hello,
I have a new AT&T H900 not rooted for past 5 months. It was working fine until the MM forced update. It started to shut down (apps stopped responding) some of my apps. I read that I needed to reboot fresh, so I did. Even directly after reboot, apps still kept shutting down (stock apps like Google, messaging, just to name a few) at different times, even before adding my old apps. I decided to reboot a 2nd time with the addition of clearing the cache every time ( I read somewhere that this should help). It seems that the apps seem stable, but now my device keeps rebooting at a moments notice (specifically when it is computing multi tasks). It has become very unstable. How can I fix this? Should I try a 3rd reboot? Thanks.
jzt116 said:
Hello,
I have a new AT&T H900 not rooted for past 5 months. It was working fine until the MM forced update. It started to shut down (apps stopped responding) some of my apps. I read that I needed to reboot fresh, so I did. Even directly after reboot, apps still kept shutting down (stock apps like Google, messaging, just to name a few) at different times, even before adding my old apps. I decided to reboot a 2nd time with the addition of clearing the cache every time ( I read somewhere that this should help). It seems that the apps seem stable, but now my device keeps rebooting at a moments notice (specifically when it is computing multi tasks). It has become very unstable. How can I fix this? Should I try a 3rd reboot? Thanks.
Click to expand...
Click to collapse
This is very odd. Usally apps closing like that mems theirs a compatibility issue. For now lets focus on your rebooting.
Try leaving your phone with the battery pulles for atleast 10 minutes. If that doeant solve your problem, see if it randomly reboots when you have it charging. My G3 did that if i ran more than one thig with it off the charger. And my case was a bad battery. So it may be your problem aswell