[Q] Constant Reboots with Synergy - Verizon Samsung Galaxy S III

This started occurring last night when I was using Winamp to sync music files to my phone. Every 10% or so the phone would reboot itself and I'd have to start the entire process over. Since then, I've been getting random reboots while doing anything from typing an e-mail to closing an app and haven't been able to narrow it down to anything specific.
So far I've tried
1) Removing my external sd card
2) Uninstalling numerous apps to try an pinpoint one causing an issue
3) Underclock from the 1.9 ghz the rom comes with
4) Removing the battery
5) Reflashing the latest nightly, clearing cashe and dalvik
Anyone have any idea on how I can try to resolve this? I love the phone and the ROM, but I can't deal with random reboots while just using my phone normally.
Thanks in advance.

jdubsss said:
This started occurring last night when I was using Winamp to sync music files to my phone. Every 10% or so the phone would reboot itself and I'd have to start the entire process over. Since then, I've been getting random reboots while doing anything from typing an e-mail to closing an app and haven't been able to narrow it down to anything specific.
So far I've tried
1) Removing my external sd card
2) Uninstalling numerous apps to try an pinpoint one causing an issue
3) Underclock from the 1.9 ghz the rom comes with
4) Removing the battery
5) Reflashing the latest nightly, clearing cashe and dalvik
Anyone have any idea on how I can try to resolve this? I love the phone and the ROM, but I can't deal with random reboots while just using my phone normally.
Thanks in advance.
Click to expand...
Click to collapse
I had this problem too with the latest release, even after reflashing it, and it even popped up randomly like your issue after using the ROM for a while. All of the sudden random reboots all the time. I went back to R64. I think there is a different kernel in some of the newer releases or some change, I don't really know, but R64 has been running perfect all around and hasn't rebooted once on me. You may be able to dirty flash back to 64, I don't know if it will work because I didn't try it, but I do know a clean flash fixed it for me. If it's just kernel issues then dirty flash should work as usual.

adoublearonn said:
I had this problem too with the latest release, even after reflashing it, and it even popped up randomly like your issue after using the ROM for a while. All of the sudden random reboots all the time. I went back to R64. I think there is a different kernel in some of the newer releases or some change, I don't really know, but R64 has been running perfect all around and hasn't rebooted once on me. You may be able to dirty flash back to 64, I don't know if it will work because I didn't try it, but I do know a clean flash fixed it for me. If it's just kernel issues then dirty flash should work as usual.
Click to expand...
Click to collapse
Thanks for the reply. I flashed leankernel tonight and so far so good... time will tell though.

Related

[Q] sensation 4g randomly turning off and rebooting

Is anyone else experienceing this problem and is there a solution to fix this?
sxyshotta said:
Is anyone else experienceing this problem and is there a solution to fix this?
Click to expand...
Click to collapse
Factory Reset, you messed something up in your rom most likely. If you are s-off'd I would recommend flashing another rom, or reflashing a the same rom.
Which ROM are you running?
Sent from my Sensation using XDA App
kslen said:
Which ROM are you running?
Sent from my Sensation using XDA App
Click to expand...
Click to collapse
im using ARHD, but im used many other rom and the samething keeps happening, i even got another sensation and its the samething
I too have run across this issue. I found if I use more than one Widget it happens. This is happening on the past two roms I have used.
COMPLETELY wipe your phone, flash a stable ROM you know that works, and then make a nandroid backup so this doesn't happen again. Normally I would suspect a faulty kernel, but if it's happening on every ROM idk what to say.
Sent from my HTC Sensation
I am going to flash another rom , for testing purpose...while looking into it I fund this comment.....
Set CPU clock back to 1.2 GHz.... fi you don't want your CPU to be overclocked or you had boot-loop or random reboots ---
Not sure if this is the answer, but I'll try it, if it continues , and will report back
I've been running into this same issue, but it only happens in the middle of the night. The phone wakes me up with its little vibrate when rebooting over and over. The only way I can stop the rebooting is to unplug and plug the charging cable back in. Plus the phone gets really hot until I unplug it. Running the latest NRG rom with stock kernel.
This happens to me whenever I play music, and alternate between texting and surfing the web...stock rom...
j3.cole said:
I am going to flash another rom , for testing purpose...while looking into it I fund this comment.....
Set CPU clock back to 1.2 GHz.... fi you don't want your CPU to be overclocked or you had boot-loop or random reboots ---
Not sure if this is the answer, but I'll try it, if it continues , and will report back
Click to expand...
Click to collapse
Thanks will try that
I'm having the same problem now. Phone was fine then started rebooting. wiped and restored from backup of when it was fine and still reboots.
i have the same problem i installed the bad recovery awhile back when it forst came out now on the good one but i think it messed up the phone cause i have random reboots like crazy i have s-off and everything just since that day it started but the phone works perfect on the charger i got a s2 since then but would like to revive my old phone if possible

CM7.2 RC1 endless reboots

So today CM 7.2 RC1 was released for all supported devices. Here are some links
http://www.cyanogenmod.com/blog/cyan...rc1-is-upon-us
http://get.cm/?device=speedy
So I wiped my device clean and flashed the zip, and after booting up successfully (shows the screen that says "Touch the Android to begin") it just reboots on its own, and the process repeats. I double checked that the md5 was clean, and I tried wiping and flashing several times with the same results. Is this happening to anyone else?
Same for me here.
Probly a stupid question but if I'm going from 7.1 to 7.2 do I NEED to do a full wipe? Can't I just wipe dalvik, cache and flash?
Sent from my PG06100 using XDA
THEsunnypiglets said:
Probly a stupid question but if I'm going from 7.1 to 7.2 do I NEED to do a full wipe? Can't I just wipe dalvik, cache and flash?
Sent from my PG06100 using XDA
Click to expand...
Click to collapse
Usually you could but had risk of error, with me, it just made the reboots happen at 5 minutes intervals instead of 10.
Not sure if this is coincidence or not, but after about 5-6 reboots, I skipped the sign in, then quickly turned off the GPS. The phone stopped rebooting, even after turning the GPS back on. I have no clue what fixed this, but it has stopped rebooting now.
cloverdale said:
Not sure if this is coincidence or not, but after about 5-6 reboots, I skipped the sign in, then quickly turned off the GPS. The phone stopped rebooting, even after turning the GPS back on. I have no clue what fixed this, but it has stopped rebooting now.
Click to expand...
Click to collapse
Cool but is audio working? And why is every single RC release for speedy by CM unstable? This GPS reboot thing has been a issue before but they don't seem to fix it lol.
sparksco said:
Cool but is audio working? And why is every single RC release for speedy by CM unstable? This GPS reboot thing has been a issue before but they don't seem to fix it lol.
Click to expand...
Click to collapse
Audio is working fine for me.
cloverdale said:
Audio is working fine for me.
Click to expand...
Click to collapse
I see, I'm thinking the reboot issue has to do with the kernel. Try a different kernel and that should fix it.
sparksco said:
I see, I'm thinking the reboot issue has to do with the kernel. Try a different kernel and that should fix it.
Click to expand...
Click to collapse
Since this discussion is going in two threads, I will let everyone know that using one of Sparksco's kernel ports fixes the reboot issue.
Edit: Though the kernel ports fix the GPS reboot, they take away all audio.
cloverdale said:
Since this discussion is going in two threads, I will let everyone know that using one of Sparksco's kernel ports fixes the reboot issue.
Edit: Though the kernel ports fix the GPS reboot, they take away all audio.
Click to expand...
Click to collapse
Agreed. I have tried just about every kernel I can get my hands on. The ones that boot have no audio, the rest simply don't boot or bootloop or reboot after a moment or two (haven't tried the default kernel and turning GPS off/on yet).
I fail to understand how they let 7.2 out for the Shift when it isn't booting up reliably for the majority of users. At what point did it become safe to say it is a Release Candidate? I'm beginning to think it more a Return To Your Previous ROM Candidate.
[edit]
I just flashed back the default kernel with GPS disabled and it booted without issue. Enabled GPS after boot and it works without reboot. Rebooting phone with GPS enabled still results in bootlooping, tho.
So, here's my proposed solution to those still having problems, want audio, and can live without GPS being enabled all the time (since no audio also means no call audio, this should be the majority of you):
1. Flash the 7.2 zip.
2. Immediately flash pershoot kernel (the ones that boot without audio, like v14 port).
3. Boot and immediately disable GPS.
4. Reboot into recovery and reflash the 7.2 zip. (NO NEED TO WIPE ANYTHING BUT DALVIK CACHE, for those who are already setup on 7.2 or coming from 7.1)
5. Boot normally.
NOTES:
A. If you attempt to boot or reboot with GPS enabled, you will get caught in a bootloop again. Simply follow the steps above again to turn it back off.
B. You CAN turn GPS on after boot and use it without issue. But you MUST disable before powering off or rebooting, else you'll have to do the above steps again.
C. Even if you can live without audio, I advise AGAINST using the pershoot ports on 7.2 for daily use. Something is causing that kernel to drain battery at about 3-5 times the normal rate (may have to do with the audio issue), regardless of CPU speed.
Hope this helps until this gets officially fixed somehow.
[/edit]

[Solved] Phone issues, need help please!

Posted this in the CM10 dev thread, but decided I may get some better help by posting here, and here's my OP from the thread:
so yesterday my phone randomly shut off and it seemed to completely reset my phone. It booted up fine with two or three apps missing and all of my settings lost. I didn't think much of it until today when I tried to fix it. I did a fully wipe because some apps had disappeared and wouldn't download from the play store and wouldn't restore from TiBu. I went ahead and did the full wipe, flashed latest gapps and my device started up. I began trying to restore my apps and what not, but at I was navigating the phone my app switch soft key and home key would not function. They vibrate when pressed but don't do anything; only the back key works. I went to settings and remapped the soft keys to see if it was just a glitch and nothing changed. Still no function, only vibration. I then rebooted to recovery and did yet another full wipe and this time tried to install aokp just to see if it was a bug with cm (yes I know aokp i built from cm but I had just downloaded the latest nightly to my phone and deleted the old one so this was a test of the new nightly). Still no cheese. I was then thinking to myself, screw it and at least try to restore some apps, but after configuring my google account and opening he play store i get a constant no connection, retry button. Most of the stock apps will not even open. I flashed a TiBu.zip to restore the app and great, that worked but restoring from in TiBu doesn't work now. I tried reflashing cm and essentially repeated the above steps without any luck. Any ideas? I can't test my data/phone connection other than the fact that after setting up my google account, my email synced and I was able to make a call because the browser won't even open. MY [email protected]$s didn't do a nandroid either
Help a desperate guy in need, please!!
PS redownloading cm and gapps right now on my computer in case of a corrupted download, but to have the issue on cm and aokp is suspicious. I'll have to wait for an hour or two because my internet speed is that slow...
Click to expand...
Click to collapse
Now I redownloaded CM10 fresh from the get.cm page and even did a md5 check and everything matched up, yet still no luck. another strange thing I've noticed is that my power menu, when I verified in the setting that all options for my power menu were selected, the only options that show up are power off, reboot and screenshot. I checked to be sure app permissions were correct and even fixed permissions from recovery. All apps that do open force close upon any activity, for example upon receiving an email in gmail, the gmail app force closes. I don't know if providing a logcat would be beneficial to anyone because I don't know how to read them.
I am currently waiting on a sense rom to finish downloading to verify that it isn't just aosp based roms, but my internet connection is terrible so the 600+mb file still has 2+hrs left. I am also downloading an ruu if nothing else works, but again with a 500+mb file it will take 2+hrs
Any help is much appreciated and I can provide more info if needed.
SOLVED
Sounds like it might be a kernel issue. Try flashing a different one.
If nothing else works, relock and RUU.
iElvis said:
Sounds like it might be a kernel issue. Try flashing a different one.
If nothing else works, relock and RUU.
Click to expand...
Click to collapse
Even if it's the stock cm kernel? i never had issues with it before, but I'll flash one now because luckily I have a couple on my phone already
Edit: flashed a different kernel and nothing changed, but thanks for the suggestion

I'm having random reboots.

Hi,
I'm having trouble with my OpO since I rootet it. Here is the history:
-Day One: Just stock 25R, installed all Apps via google play, no problems whatsoever.
-Update 30O still no problems.
-Then I rootet the phone and flashed TWRP recovery to install the Titanium Backups of my old Nexus 4. Thats when I had the first random reboots. Some while Browsing in Chrome, Some on Youtube, Some while listening Music on Hedphones.
Since I have no Sim-Pincode activated a reboot just means, that I'm Offline for about 20 seconds but having that about 5 times a day just isn't acceptable.
-Then I got the 33R OTA update, which made my root and TWRP recovery disappear because I forgot to make a check in the developper settings, but that did not make the reboots disappear
-Today I flashed the 25R stock Image of the Firmware via Fastboot to set my One to real Factory status. I only installed apps via google play and recovered the app data of 2-3 apps via helium backup without root. I got the two OTA updates, and another reboot.
-Then I rootet the thing again, to use a logcat app, and now I have two logcats ending with a reboot.
I really hope that you can help me since I allready sold my old phone and expect that it will take really long until I get a new OpO here in Germany.
The next thing I will do is flash the 25R Image again and install the apps without using helium at all and leave out the goolors icon pack that I used before. But after that I'm absolutely out of ideas.
UPDATE: Yeah so it's definitely a HW defekt or something I cannot solve. I just wiped everything via TWRP, then flashed the factory image 25R without root and just installed some apps via google play. But after one hour I read an email and it rebooted....
Unfortunately I cant post the links to the logcats due to my low post count.
Logcats don't help you when it comes to finding out what is causing your phone to reboot. It is last_kmsg that is responsible for debugging reboots.
A hardware defect would not be causing your phone to reboot, its something to do with the way your phone is configured / set up.
I would highly recommend you to start from scratch completely and do the following,
- Flash XNPH33R http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH33R-bacon-signed-fastboot.zip from scratch. Make sure you do wipe.
(OR.. flash a custom ROM after wiping)
- List all of the apps that you currently have installed.
- Are you using Xposed?
- Whats your set up? ROM/Kernel/Gapps/etc.
I am not using any custom Rom, root, custom kernel or xposed module.
I just wiped everything in TWRP and flashed the 25R factory image. After about one hour of installing apps in Google play and loging into account i got the first reboot.
I can try flashing the image that you postet tomorrow but thats the same Rom that Im using now
Ord3r66 said:
I am not using any custom Rom, root, custom kernel or xposed module.
I just wiped everything in TWRP and flashed the 25R factory image. After about one hour of installing apps in Google play and loging into account i got the first reboot.
I can try flashing the image that you postet tomorrow but thats the same Rom that Im using now
Click to expand...
Click to collapse
I meant, you can try a custom ROM and see if you can reproduce the problem. Custom ROMs are running on code that is much newer than CM11S.
Ensure you're on XNPH33R when it comes to OTAs.
I just wanted to add my frightful experience. I've had the OPO for two weeks now without problems and no random reboots. Had my first reboot today and just now my phone powered off and wouldn't turn back on. I plugged it back into the wall charger and it turned itself back on but was stuck on the boot logo. I tried holding down the power button to turn it off but nothing. Pressing the power button only turned the display on and off but still stuck on boot logo. Eventually I held down the power button and volume down and the phone buzzed and went to recovery. I'm on stock 33R and Franco's kernel. Haven't tweaked anything. Now I'm afraid my phone is going to brick itself.
Sent from my A0001
Yeah so this is definitely getting worse. At first I had 1-2 reboots a day but today after unplugging I already had 3 reboots in one hour.
I think I am definitely going to send it back when I'm back home next Week.
I already flashed stock Firmware 3 times and did what feels like 10 full wipes in one Week.
This cant be normal. Apps that I installed that arent in the top 50 in the play store are: Dailyme, yatse for xbmc, line, Wolfram aplha and ogyoutube.
That really sucks. I already sold my nexus 4 and have no other phone left
Btw: I'm on 33R for the third time this Werk. Everytime via OTA
Try a different Rom like crDroid + AK Kernel. Running this 2 things since 2 weeks and i only got one reboot just because my camera stopped working because in undervolted my phone ^^
THX but I just want a functioning phone. And since I have errors that nobody else has I think that it is a Hardware issue. At the Moment I am waiting for a answer from one plus so i can send it back
Ord3r66 said:
THX but I just want a functioning phone. And since I have errors that nobody else has I think that it is a Hardware issue. At the Moment I am waiting for a answer from one plus so i can send it back
Click to expand...
Click to collapse
ok I understand your frustration but to fully test your phone you will need to run stock and stock only with no outside apps loaded. Try and do this for a day or half a day or so and see what your results may be. Its your phone and of course do what you like but testing your phone and doing the same thing every time as in reloading your apps is not a good way of fully testing.
also did you do a last_kmsg report as recommended.
Okay will do that. Is there a tutorial to do a last_kmsg report? Do i need root?
Ord3r66 said:
Okay will do that. Is there a tutorial to do a last_kmsg report? Do i need root?
Click to expand...
Click to collapse
Yes you need root. After a reboot just pull the last_kmsg file from /proc/ using adb, file Explorer of your choice, etc.
Sent from my One A0001 using Tapatalk
Ord3r66 said:
Okay will do that. Is there a tutorial to do a last_kmsg report? Do i need root?
Click to expand...
Click to collapse
of course there is a tutorial there is a tutorial for everything.... Got to utilize google my friend.
OKay it's me again. Meanwhile the Oneplus support answered my mails and told me to flash custom Kernels to resolve the issue.
Since Yesterday I tried three Kernels (Franco, Heeroluca and AK) and nothing changed, so now I start to gather some Last_kmsg files name it after the APP where the reboot occured and upload it here. Ofcourse I'm also sending those files to the Oneplus Support
Here is the first one:
https://dl.dropboxusercontent.com/u/43103242/1_Line_Messenger_last_kmsg
https://dl.dropboxusercontent.com/u/43103242/2_standby_screenoff_last_kmsg
Have the same problem. Using wi-fi -> reboot. Don't know how to fix this defect. I hope a solution will be found
Had a random reboot while browsing chrome. I was scrolling down the page and received a text at the same time when my screen froze. After freezing for a few seconds, it rebooted itself. I tried getting the last_kmsg but it tells me that it isn't found. The code I used was: "su" followed with "cat /proc/last_kmsg > /sdcard/last_kmsg.txt" in terminal emulator. Let me know if there is anything else I can do. Thanks!
I have also problems with chome beta browser. I get freezes. Is this issus only with chrome or with all browers?
Gesendet von meinem A0001 mit Tapatalk

Random Reboots?

Past couple of weeks (~2 weeks), I've had my opo randomly reboot, can happen just about anytime. Middle of a call, browsing the web, etc. I did a clean install but that didnt do anything what so ever. Anyone else have this issue and resolve it?
Need some information on what are you running on your phone
Cos11, cos12, cm, etc
Also can you remember the last thing you did on your phone before the reboots
903tex said:
Need some information on what are you running on your phone
Cos11, cos12, cm, etc
Also can you remember the last thing you did on your phone before the reboots
Click to expand...
Click to collapse
I was running Stock Cm12 when the issues started, don't remember the exact reason for the original reboot, it was just random. I wiped and clean flashed temasek's 12.1 but the problem still persists.

Categories

Resources