im running this rom: [ROM] Doc's ROM Modified (Build 19) by Mikey and its been good for the past few weeks, but now the phone will vibrate once or twice...then do it again and then start restarting itself...it randomly does it and i have no idea why..do u have any ideas? the phone is not overclocked either...
I had the same problem and I herd it was a bunch of different things, and apparently a lot of captivates have the same problem, but I got tired of it and went back to original 2.2 and it works perfectly, but I think it is the rom's
Sent from my SAMSUNG-SGH-I897 using XDA App
SiL3nTKiLL said:
im running this rom: [ROM] Doc's ROM Modified (Build 19) by Mikey and its been good for the past few weeks, but now the phone will vibrate once or twice...then do it again and then start restarting itself...it randomly does it and i have no idea why..do u have any ideas? the phone is not overclocked either...
Click to expand...
Click to collapse
I'm having the same problem. It's been fine for about 2 weeks and just started doing this yesterday.
I had a lagfix enable and instead of switch lagfixes, I just disabled it entirely. I'll see how today goes and report back.
Also, check page 77 of the Doc's Rom thread in the Dev section
http://forum.xda-developers.com/showthread.php?p=9391314&highlight=random+restart#post9391314
This was happening on my boss's Captivate. While it's not necessarily the right way to fix it, I removed the external SD card. It was rebooting 2-3 times per day, now it doesn't ever reboot. I've read this problem isn't necessarily tied to a specific ROM though, so maybe it has nothing to do with the problem that you're having.
Related
Hey guys,
I flashed Cognition 2.3b, and also flashed the update, and I am having a couple of issues, and was wondering if anyone could shed some light.
The first issue is that my battery seems to be draining really fast. I unhooked my phone from the charger at 2:00pm this afternoon, and by the time I got to work a little after three, it had already gone down 10% with very little use.
The other issue is that the auto suggestions are not working on the android or samsung keyboards, and the tap space twice to insert a period is not working either, even though the option is checked in the settings. Can anyone offer any insight or suggestions? Please keep in mind I am a noob with roms.
First post this in the Cognition thread. Did you flash on a full charge? Recalibrate your battery http://forum.xda-developers.com/showthread.php?t=765656. Post your other issues in the thread so you can get help there.
Cognition v2.3 Unlocked Samsung Captivate on TMobile
This weekend I installed Cognition v2.3 via ROM Manager on my Samsung Captivate running Eclair 2.1 update1. Once the install was completed and the device booted, every 30 seconds or so my device would vibrate and then be followed by a force close. I also noticed that I would appear to have no radio signal around the same time.
Obviously I did a factory reset which did not help, so I did a reinstall of Cognition v2.3. This time it was fine!! No vibrating and no force closes for a few hours, that is until I realized that I had actually not had my sim in and was on wifi. As soon as I inserted my TMobile simcard back into my device, all the vibrating and force closes started right back up.
Needless to say I am back on 2.1 update1 and hoping some can shed light on this strange issue.
cybrslug said:
This weekend I installed Cognition v2.3 via ROM Manager on my Samsung Captivate running Eclair 2.1 update1. Once the install was completed and the device booted, every 30 seconds or so my device would vibrate and then be followed by a force close. I also noticed that I would appear to have no radio signal around the same time.
Obviously I did a factory reset which did not help, so I did a reinstall of Cognition v2.3. This time it was fine!! No vibrating and no force closes for a few hours, that is until I realized that I had actually not had my sim in and was on wifi. As soon as I inserted my TMobile simcard back into my device, all the vibrating and force closes started right back up.
Needless to say I am back on 2.1 update1 and hoping some can shed light on this strange issue.
Click to expand...
Click to collapse
I encountered this same issue when i first upgraded to v2.3b3. In the Cognition thread people suggested installing v2.3b2 first and then installing v2.3b3. This is what I did and it worked flawlessly.
Where to get 2.3b2? I looked at main site, didn't find a "older versions" link.
Thanks.
I am currently running 2.3b2. Thats weird. I may have to master clear and flash back to stock with Odin.
Sent from my SAMSUNG-SGH-I897 using XDA App
bparkerson04 said:
I am currently running 2.3b2. Thats weird. I may have to master clear and flash back to stock with Odin.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
You don't just flash with rm/cwm.
Sent from my SAMSUNG-SGH-I897 using XDA App
Hello people. I searched for info on this issue, but nothing for the Captivate came up. Intermittently I'll wake my phone up and there will be a little circle with a line through it where there should be network info. Anything I try to do with the network pops up a "Not registered on network" (or something like that) message. Usually rebooting the phone will solve the problem, but last weekend after three reboots it was still doing it. I left my house and an hour later checked it and no circle/line icon. This happens every several days, so not a chronic problem yet. Still very annoying. Any solutions? Thanks.
Stock Captivate.
I would consider warranty return if it were me I havent seen or heard of this before your post. good luck.
I have a stock captivate and let's just say I am incredibly disappointed and annoyed with it and at&t in general I'm tired of all the run around and hold up concerning froyo, but this isn't the thread for that.
My phone has been glitchy since the get go. The newest is the issue with "not registered on network". It has happened off and on, but a couple days ago, after I had turned the phone off for the night and back on, the phone screen blanked out while the bottom touch panel stayed lit and everything became totally unresponsive. After several reboots by removing the battery, my screen finally came up again, but so did that little blue circle and line...voila..."not registered on network"
The guy in tech support from at&t tried to help me out. He stayed on the phone with me for over 2 hrs trying to correct the issue, but even after a factory wipe...nada. Lost all my apps, free and purchased... if we would have froyo like promised, all my apps would have been backed up...UGH...
This is actually my third captivate in as many months. My first phone bricked itself after 2 days. No one could ever figure out why. I am waiting on a replacement as we speak. Of course my "new" phone is being replaced with a refurbished one. I hate that considering my current phone was only 3 months old and didn't have a mark on it, but what can I do?
because you don't mention if you're running stock or a custom ROM, I'm going to assume custom ROM. and if you are, then you must have not searched very hard because this is already a semi-known issue: http://forum.xda-developers.com/showthread.php?t=864903
it happens to me ANY time I use a modem newer than JK3... when I use UGJK3 or older, no problems... but if I use UGJK4 or newer, random "no service" on the lock screen with the "circle with a line through it" in the notification bar. as of right now (I believe) there's no known issue why some modems fail on only some hardware. I have a batch 1006 and it works fine right up until the UGJK3 modem, while some people seem to have absolutely no issues with modems (even the newest ones like UGJL2 and TLJL3). basically, if you're running a JPY based ROM, flash JK3 and see if that helps... if that doesn't, go back to a stock captivate ROM of some sort with a stock modem so you don't have these issues (never happened to be me on JI6/JJ4)
Try changing ur SIM card. That could solve the issue.
In my case, it is original stock all the way. The SIM card is fine because I switched it into two different at&t phones and had no issues at all. Right now my Captivate is a gloried camera and MP3 player.
I forgot to subscribe to my own stinking thread! I know this is stale now, but here goes.
I'm running stock froyo, rooted. At the time of the original post I was using it completely stock on eclair. Shortly after the post, it stopped happening and haven't had issues since. I still don't know what caused it. Thanks for all the input though.
Sent from my SAMSUNG-SGH-I897 using XDA App
NvigR8 said:
I forgot to subscribe to my own stinking thread! I know this is stale now, but here goes.
I'm running stock froyo, rooted. At the time of the original post I was using it completely stock on eclair. Shortly after the post, it stopped happening and haven't had issues since. I still don't know what caused it. Thanks for all the input though.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Happened to me a year or so ago on a different phone. Turned out they were upgrading the tower closest to me with new hardware and were shutting it down intermittently to work on it.
First off I want to start by saying I have flashed my rom to Bamf 1.5 remix. I do not overclock my phone however I have tried limiting my clockspeed hoping to prevent a reboot. The phone did not start the random reboot until I flashed to said rom. I have tried reflashing but no improvements, any ideas?
Sent from my ADR6400L using XDA App
It has happened to me but I believe it just me OCing, flashing back to the kernel that I was using before when my phone was stable and testing it out. If not, I will just go back to 1.5
Also, does anyone know how to edit the power control widgets in the pulldown? I can't find any options. Thanks.
Did you flash the new radio when you loaded up BAMF 1.5?
If so, there's your problem
Happened to me with BAMF 1.6 and leankernel 192X, but only when I set it to ondemandX thru SETCPU. Other than that I've had no reboots.
sent from my BAMF Thunderbolt!
eschelon said:
Did you flash the new radio when you loaded up BAMF 1.5?
If so, there's your problem
Click to expand...
Click to collapse
^^
yeah its pretty common for people who flashed the new radio to have reboots. i have had some of those issues, i found that using different kernels at different clocking speeds made my phone more stable. NOTE: i am not a pro, just something i noticed.
What's really behind all the random reboots?
OK... So I've tried just about every rom on the dev thread, I purchased the TB on launch date and had it rooted as soon as Jcase posted S-off instructions... I am now on the new radio and until today, I haven't had a single random reboot. Then all of a sudden, just about an hour ago, as I'm backing out of Tapatalk, bam... Phone rebooted itself...
Now I've been reading on just about every rom thread where people have been experiencing random reboots. Some think the new radio is the cause, but some people are on the new radio and have not experienced this. Others on the old radio still get random reboots.
Others think its the rom but people have noted this issue on most If not all of the rom threads.
Others think its the kernel that's causing it, but again, there doesn't seem to be any pattern to nail it down to a single kernel. Furthermore, some of these people are not OCing, myself included.
Which leads me to the strangest part of all this. My wife also has the TB. Her phone is totally stock and is not rooted. I got it for her day after launch and for the last few weeks, her phone has also been randomly rebooting. Not constantly, mind you. Just enough to be a nuisance. She has still not updated to OTA... The only suspect to this is that this appears to have started after the 4G outage a few weeks ago... And we are in a 3G only area but there was a day or so we could only connect to 1x...
So what's really causing these random reboots? I'm no expert, never claimed to be one, but is it possible that something going on between our phones and the Verizon network is causing this?
Thoughts... Ideas...?
Sent from my Thunderbolt using Tapatalk
Great post. It's good to know even non rooted users are having reboots.
non-rooted.... Updated yesterday... and got a reboot today.
Sent from my ADR6400L using XDA App
I've had about six lock ups and reboots today since ehrpd has been back up
Sent from my ADR6400L using XDA Premium App
I have had a few reboots across a few different rom, radio, and kernal combos. The only thing that all my reboots have had in common was I had GPS enabled. Ive yet to see a reboot with it off. Could just be a coincidence.
toebee76 said:
I have had a few reboots across a few different rom, radio, and kernal combos. The only thing that all my reboots have had in common was I had GPS enabled. Ive yet to see a reboot with it off. Could just be a coincidence.
Click to expand...
Click to collapse
GPS was also on when my phone rebooted... Google Maps was running.
Sent from my ADR6400L using XDA App
stock rom, not rooted, has had multiple random reboots
I have had no random reboots, or none that I have personally experienced. I figured if my phone was randomly rebooting I would have noticed a considerable battery drain. I have not noticed that yet. I honestly think that this might be an issue for people with little to no 4g coverage. I am bothered that this has not been addressed yet by verizon as I have seen so many people complain about this.
Hopefully I dont get these either, who knows may it is just phones that are may be defective hardware wise.
Well i just wanted to drop my $.02
I am Rooted and have been just about the same time the OP has been rooted.
I USED to have reboots. I install the full RUU and had reboots i also installed just the RADIO file and had reboots. I also reverted back to stock by the RUU provided by JCase. I Then flashed 1.6 followed 1.6.3 and have not had any problems. I assume that those 2 already had the radio file in them and i didn't not have to flash anything additional. Since being on 1.6 then 1.6.3 i have experienced not 1 reboot. Unless i did it myself.
I did notice then before when i did have the reboots (when i manually flashed RUU or just the RADIO file). I had reboots 3 different ways. I would either get a reboot when my phone had been sitting next to me for a while i would notice the white screen and know it was a reboot. Also the 2 other times was backing out of TapaTalk or native browser/dolphin HD.
So i don't know if that is in a way related. I just don't have them anymore.
I noticed that whenever my phone would reboot (on the leaked radio only,) I had a weak 3g signal. I watched this happen several times. My guess would be the people who aren't having reboots are in an area where they constantly have a good signal. Can anyone else corroborate this?
toebee76 said:
I have had a few reboots across a few different rom, radio, and kernal combos. The only thing that all my reboots have had in common was I had GPS enabled. Ive yet to see a reboot with it off. Could just be a coincidence.
Click to expand...
Click to collapse
This is a possibility... But if that's the case this will be the first Android device I've owned that has rebooted itself randomly due to GPS. Even the Samsung Vibrant, which had horrible GPS right out of the box, didn't reboot itself when it was turned on...
However, if this is the case, why has this only become a recent issue.. now my memory isn't so good... But I don't remember seeing much about this issue on rom threads until recently... I.e the past few weeks... Neither my wife's nor my phone randomly rebooted until just a few weeks ago, and we both have our GPS turned on everyday, all day...
Sent from my Thunderbolt using Tapatalk
BotsOne said:
I noticed that whenever my phone would reboot (on the leaked radio only,) I had a weak 3g signal. I watched this happen several times. My guess would be the people who aren't having reboots are in an area where they constantly have a good signal. Can anyone else corroborate this?
Click to expand...
Click to collapse
I live in a strong 3G area and my phone has never re-booted itself as far as I know. I'm doing the update tomorrow and will be interested to see if the problem starts.....I hope not.
BotsOne said:
I noticed that whenever my phone would reboot (on the leaked radio only,) I had a weak 3g signal. I watched this happen several times. My guess would be the people who aren't having reboots are in an area where they constantly have a good signal. Can anyone else corroborate this?
Click to expand...
Click to collapse
Unfortunately, I had a solid signal when my phone rebooted this afternoon. I was a stone's throw from Philadelphia on I-95. I've never had signal issues along I-95 between New York and Philadelphia. I'm running the released update.
BotsOne said:
I noticed that whenever my phone would reboot (on the leaked radio only,) I had a weak 3g signal. I watched this happen several times. My guess would be the people who aren't having reboots are in an area where they constantly have a good signal. Can anyone else corroborate this?
Click to expand...
Click to collapse
This as well is a possibility... Although I am in an area where 3g is strong... I have seen on my and my wife's phone... Even when standing still... That the 3g icon will vanish and come back seconds later...I am in a decent sized college town, population of about 70000... I couldn't say how strong 3g actually is but its everywhere in the city limits... And most of the countryside...
I have traveled to cities with strong 4g but I didnt stand around long enough in a single place to really watch the phone to see if it was dropping data...
Thanks for the constructive input, everyone... Lets keep the corroboration going and see if we can find a pattern..
Sent from my Thunderbolt using Tapatalk
The only time I had reboot was on the leaked ruu which is now the OTA.
Once I went to BAMF 1.5 with new radio and new base no reboot. About a week ago I flashed back to stock radio just to compare after being on the new one for a while. I see nothing different between them really.
Ive tried numerous ROMs and kernals and stuff with my phone, yet none of them seem to solve the reboot issue on my g2x except the stock 2.3.3 update a while back... Is there some secret im missing? why would the 2.3.3 update fix it while nothing else works well?
If all else fails i might have to just replace the phone... im tired of stock!
Lakonikos said:
Ive tried numerous ROMs and kernals and stuff with my phone, yet none of them seem to solve the reboot issue on my g2x except the stock 2.3.3 update a while back... Is there some secret im missing? why would the 2.3.3 update fix it while nothing else works well?
If all else fails i might have to just replace the phone... im tired of stock!
Click to expand...
Click to collapse
I think that might just affect only certain phones. I've noticed that it affects some and never happens to others. i jsut got my G2x and have yet experienced on reboot. And I've tried Weapon, Cm7 and EG.
mackster248 said:
I think that might just affect only certain phones. I've noticed that it affects some and never happens to others. i jsut got my G2x and have yet experienced on reboot. And I've tried Weapon, Cm7 and EG.
Click to expand...
Click to collapse
i hope this isnt the case. not sure how t mobile is on replacing a phone if i claim its faulty- and i would need to unroot and change back to stock recovery and stuff =\ which i guess isnt THAT hard..
Yes but if you have insurance on your sim, card then just say you having difficulty with they should give you another one if not then use the one root method to unroot back.
Sent from my LG-P999 using xda premium
Yeah, I have nothing but problems with these ROMs on my G2X. Going back to stock GB today. I was late to work a couple of times because my phone rebooted itself when my alarm was supposed to go off with Weapon, and now Eagles blood I woke up to my phone being completely off, where I couldn't even turn it on without removing the battery first (cuz that makes sense). I couldn't use A2DP on CM 7 either. As far as I'm concerned all custom ROMs are STUPID.
Tweaken said:
Yeah, I have nothing but problems with these ROMs on my G2X. Going back to stock GB today. I was late to work a couple of times because my phone rebooted itself when my alarm was supposed to go off with Weapon, and now Eagles blood I woke up to my phone being completely off, where I couldn't even turn it on without removing the battery first (cuz that makes sense). I couldn't use A2DP on CM 7 either. As far as I'm concerned all custom ROMs are STUPID.
Click to expand...
Click to collapse
Try
Agreed 100% somephones should need custom ROMs but phones like these shouldn't be cause its already as strong as it can be lin pack status is awesome and quadrant standard so their no point to root them cause its really fast and good already
Sent from my LG-P999 using xda premium
i like the customization of roms like cyanogen, thats the reason i like to rom up my phone
mackster248 said:
I think that might just affect only certain phones. I've noticed that it affects some and never happens to others. i jsut got my G2x and have yet experienced on reboot. And I've tried Weapon, Cm7 and EG.
Click to expand...
Click to collapse
So the only option is to get a replacement from Tmobile? Tried rooting my wifes phone and got the same thing. Using CM7 or MIUI, random reboots, dropped calls, and SOD galore. If this is the only fix I guess I'll be calling Tmobile again...
Ive never had the reboot issue to the extreme like some have. It has happened for me a few times with stock gb, did 2 wipes in a row and then it stopped. Not a guaranteed fix, but it worked for me.
once rooted, I removed almost all the bloat that I didnt use (from xboarders stock rooted rom) and never had an issue.
I did notice a while back with the nightlys that when I put my put my screen to sleep while in the sms app, id have to pull the battery. Issue resolved for me with the currenty nightlys.
Regulus49001 said:
So the only option is to get a replacement from Tmobile? Tried rooting my wifes phone and got the same thing. Using CM7 or MIUI, random reboots, dropped calls, and SOD galore. If this is the only fix I guess I'll be calling Tmobile again...
Click to expand...
Click to collapse
Are you getting these issues right away or after you install apps? It is usually an errant app causing reboots and SOD and not the rom. Add apps one by one and wait a bit before adding the next one. If you add one and you start getting problems you can be pretty sure that is a problem app and uninstall it. There are many bad apps on the Market that can cause loads of problems. Google doesn't do any testing on them so it is definitely buyer beware, even if the app is free.
jboxer said:
Are you getting these issues right away or after you install apps? It is usually an errant app causing reboots and SOD and not the rom. Add apps one by one and wait a bit before adding the next one. If you add one and you start getting problems you can be pretty sure that is a problem app and uninstall it. There are many bad apps on the Market that can cause loads of problems. Google doesn't do any testing on them so it is definitely buyer beware, even if the app is free.
Click to expand...
Click to collapse
but the fact that they dont cause reboots on the stock 2.3.3 rom makes me think it cant be soloely the apps
g2x random reboot fix
I think I have finally found a fix to the SOD and random reboots on the g2x. Obviously the SOD is solved by going to setting>development>stay awake.
I had the same problems with every rom I tried try tsugi no reboots yet after a week I can even use the kernels on his page
Sent from my LG-P999 using xda premium
Hey XDA Forums. So I am having a problem with my Galaxy S2 Skyrocket (i727). I will have it in my pocket, not using it, and when I take it out to try and use it, it will not wake up. I do not know if it is off or what, but I cannot turn it on without pulling out the battery and putting it back in. And it isn't dead, once it comes back on it will have anywhere from %20-100 of battery left. No where near being dead. This isn't just when it is off in my pocket tho, it happens some of the times when I try and restart it, but only sometimes. This was happening before I put a Rom on it but after I had Rooted it. I am running the Slim Bean Rom and I have made sure that it is completely updated and I have returned the device to factory state and reinstalled the Rom following the directions given with the same thing happening. Any help would be greatly appreciated!! Thanks!!
Random freezes and lockups have been an issue with jelly bean from the start. They are much more infrequent now, but they still occur. Be sure your minimum CPU speed is atleast 384. Many have found this to help quite a bit on cutting down on the lockups.
A battery pull shouldn't be necessary by the way. Simply hold the power button for 10 seconds and that should do the trick.
I have only had freezes when rebooting way back in July when I flashed my first ROM Sky ICS. It happened constantly after the initial flash though while yours seems random. I was told to backup the rom, wipe and immediately restore it. Worked like a charm. Can't hurt to try it.
Edit: It could also be a stuck power button. Check the stickies and you should find info on correcting it.
-------------------------------------------------
Sent from my Skyrocket i727 running Slim Bean
-----------Nexus 7 running AOKP M1-----------
http://forum.xda-developers.com/showthread.php?p=31606955
Sent from my SGH-I727 using Tapatalk 2
can u clarify, when you are on stock rom does it do it, or only on custom rom, on stock rom its more important if its doing it as it could be some hardware issue, if its a custom rom, read the devs thread for possible fixes or try another rom
Moved to Q&A
tjc1029 said:
Hey XDA Forums. So I am having a problem with my Galaxy S2 Skyrocket (i727). I will have it in my pocket, not using it, and when I take it out to try and use it, it will not wake up. I do not know if it is off or what, but I cannot turn it on without pulling out the battery and putting it back in. And it isn't dead, once it comes back on it will have anywhere from %20-100 of battery left. No where near being dead. This isn't just when it is off in my pocket tho, it happens some of the times when I try and restart it, but only sometimes. This was happening before I put a Rom on it but after I had Rooted it. I am running the Slim Bean Rom and I have made sure that it is completely updated and I have returned the device to factory state and reinstalled the Rom following the directions given with the same thing happening. Any help would be greatly appreciated!! Thanks!!
Click to expand...
Click to collapse
I had this same issue with my Skyrocket. Granted mine was just rooted and on stock rom. But it still did it, random reboots usually during a call. I got tired of it happening so I contacted AT&T international support (that part was by accidentaly dialing the wrong number), and then a few days later I had a brand new Galaxy S III. Now granted in my case it was that I was on the 3'rd Skyrocket and was not about to go through all that again.