Related
I have seen a few threads posted about random reboots and v3.1. However, my wife's Transformer will go into a cycle where it will reboot, then a minute later or less will reboot again, and keep this up for a while (not sure how long exactly).
Don't know if this is related to an incompatible app/setting or something with the OS (3.1). Is there anything I can check/do to try and prevent this?
**Edit......Forgot to mention device is unrooted running stock 3.1.
I'm facing the Sleep of Death on this TF. It was there even on Stock and is there on other ROM's also. My Transformer reboots when in sleep mode
Srikar_NBK said:
I'm facing the Sleep of Death on this TF. It was there even on Stock and is there on other ROM's also. My Transformer reboots when in sleep mode
Click to expand...
Click to collapse
Yep....pretty much the same problem as I'm trying to fix.
*Bump*
Sent from my PC36100 using XDA App
The workaround I posted here has worked thus far for me.
http://forum.xda-developers.com/showthread.php?t=1120185
Though I haven't tried it without root privilege
sassafras
Mine was rebooting like every 10 minutes, running 3.0.1 stock non-rooted. All I did was reset it to factory settings and the problem went away.
kovla said:
Mine was rebooting like every 10 minutes, running 3.0.1 stock non-rooted. All I did was reset it to factory settings and the problem went away.
Click to expand...
Click to collapse
Why are you running 3.0.1? Upgrade to Android 3.1. It's more stable and reliable.
kovla said:
Mine was rebooting like every 10 minutes, running 3.0.1 stock non-rooted. All I did was reset it to factory settings and the problem went away.
Click to expand...
Click to collapse
If I set it to factory is it going to take it back to 3.0? Or just change all the settings back?
factory reset won't rollback the firmware, it just clear all installed apps, caches and set everything to default
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.
Ok so it is like this:
I bought my galaxy r here in sweden 1 year and 3 months ago, it was working perfectly for around 1 year.
At the one year mark i started to have some problems with the touchscreen where the phone would feel a pressure in the middle of the screen, to get rid of this i simply locked and unlocked the phone or rubbed a bit with a cloth on the screen.
Recently when I saw there was a cm10.1 rom with nightlies I rooted my phone and later installed the cm10.1 rom. Now the most anoying thing. I have a problem with my battery where the phone just shuts down randomly (mostly when playing games) even though it sometimes have up too 80% battery remaining. Then when I restart the phone it usually have 0% battery left and therefore shuts itself down again, sometimes it restarts with just a 20-30% batteryloss. This have occured more often recently and it shuts itself of 3-4 times a day. I can't remember if it was like this when i was on stock, before I started to flash and root, but i think it was.
A few days ago i flashed stock ics from odin and I confirmed that both of these problems still were there, so i have hard to belive that it is the modding of the software that have caused this.
Do you guys have any suggestions to how i can be able to use my phone normally again?
Im just a poor student so i don't want to waste money on a new phone after just 1 year :/
wipe data and cache..i think after flashing u restore ur data back.
Sent from my GT-I9103 using Tapatalk 4 Beta
Will this help with the battery?
kataria.vikesh said:
wipe data and cache..i think after flashing u restore ur data back.
Sent from my GT-I9103 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Will this help the crashing/battery?
DippN said:
Will this help the crashing/battery?
Click to expand...
Click to collapse
It may be help you but first tell me, are you restoring data from titanium backup or something related to that..??
Also if you want to take backup then take it using Super backup application.
kataria.vikesh said:
It may be help you but first tell me, are you restoring data from titanium backup or something related to that..??
Also if you want to take backup then take it using Super backup application.
Click to expand...
Click to collapse
Nope, im not takeing backup of anything.
And one other thing i forgot to mention earlier, the phone now also thinks it is charging itself evrn when it is not. It think the usb cable is still connected.
I hope OP doesn't mind that I'm joining his thread, I'm experiencing the same problems on my gfs phone and don't know what to do.
I just installed the fresh CM 10.1 nightlies (did Cache/Data/Dalvik Wipe) and she is experiencing pretty much the same problems:
After 1 or 2 hours of unplugging the phone gets stuck and shuts down. After restarting the battery percentage is pretty low and the phone shuts down again (even if the battery says ~10%). The battery percentage then changes every restart, but is always between 0 and 20%. The phone is barely usable in this state :/
I couldn't wipe the SD card (.android_secure) because the swapped paths, could this be related?
Thank you in advance!
paKS7 said:
I hope OP doesn't mind that I'm joining his thread, I'm experiencing the same problems on my gfs phone and don't know what to do.
I just installed the fresh CM 10.1 nightlies (did Cache/Data/Dalvik Wipe) and she is experiencing pretty much the same problems:
After 1 or 2 hours of unplugging the phone gets stuck and shuts down. After restarting the battery percentage is pretty low and the phone shuts down again (even if the battery says ~10%). The battery percentage then changes every restart, but is always between 0 and 20%. The phone is barely usable in this state :/
I couldn't wipe the SD card (.android_secure) because the swapped paths, could this be related?
Thank you in advance!
Click to expand...
Click to collapse
Im just glad im not alone with this problem, and as you said, its barely unusable without having it plugged in.
DippN said:
Im just glad im not alone with this problem, and as you said, its barely unusable without having it plugged in.
Click to expand...
Click to collapse
paKS7 said:
I hope OP doesn't mind that I'm joining his thread, I'm experiencing the same problems on my gfs phone and don't know what to do.
I just installed the fresh CM 10.1 nightlies (did Cache/Data/Dalvik Wipe) and she is experiencing pretty much the same problems:
After 1 or 2 hours of unplugging the phone gets stuck and shuts down. After restarting the battery percentage is pretty low and the phone shuts down again (even if the battery says ~10%). The battery percentage then changes every restart, but is always between 0 and 20%. The phone is barely usable in this state :/
I couldn't wipe the SD card (.android_secure) because the swapped paths, could this be related?
Thank you in advance!
Click to expand...
Click to collapse
Both of you install CM10.1 using Procedure no 2 from OP.
kataria.vikesh said:
Both of you install CM10.1 using Procedure no 2 from OP.
Click to expand...
Click to collapse
Will try that when i get home, thx.
kataria.vikesh said:
Both of you install CM10.1 using Procedure no 2 from OP.
Click to expand...
Click to collapse
Thank you, vikesh! I'll be able to try Procedure II tomorrow afternoon.
paKS7 said:
Thank you, vikesh! I'll be able to try Procedure II tomorrow afternoon.
Click to expand...
Click to collapse
Sadly, I can confirm that this did not change anything.
The problems are still there :/
DippN said:
Sadly, I can confirm that this did not change anything.
The problems are still there :/
Click to expand...
Click to collapse
It shouldn't be happened. But if u are feeling so, just flash any stock GB using odin v1.87. Then just wipe all data and cache. Install cm10.1 over that using method 2.
Sent from my GT-I9103 using xda premium
kataria.vikesh said:
It shouldn't be happened. But if u are feeling so, just flash any stock GB using odin v1.87. Then just wipe all data and cache. Install cm10.1 over that using method 2.
Sent from my GT-I9103 using xda premium
Click to expand...
Click to collapse
I'm definitely going to try this, but as it seems now i think it is more about a faulty battery/hardware that software?
Or have these kind of problems been fixed software before?
One other thing, if i have rooted my device, does the root dissappear when i flash stockrom using odin?
DippN said:
I'm definitely going to try this, but as it seems now i think it is more about a faulty battery/hardware that software?
Or have these kind of problems been fixed software before?
One other thing, if i have rooted my device, does the root dissappear when i flash stockrom using odin?
Click to expand...
Click to collapse
May be hardware or software too..when you will vanish all data & cache then Software issue may be gone but if problem still persist, means you have hardware problem.
Also, root will be lost after flashing Stock ROM from ODIN.
I'm able to also confirm, that Procedure II didn't help the problem. I really doubt it is a hardware fault, because of us two having the exact same problem after flashing the same rom.
@Dippn: Do you know which nightly build you used? In my case it was the nightly build "20130405". Also could you check which baseband you are on? (Under About Phone -> Baseband Version) Over here we have i9103NEKI1
The only special thing we did I can think of is flashing a modem file (when we were still on the unofficial cm10.1 without these kind of problems, but massive battery drain), because there was a call problem going on for customers of the austrian provider 3 and CM10.1.
I could analyse the problem a bit more today: It seems as soon as the phone gets busy (for example from the browser loading pages or in DippN's case processing a game), the touch screen gets unresponsive and everything starts to lag and delay or freezes completely until it shuts down the phone. Could be either CPU or RAM related, I guess. I just wonder what caused this, even if the nightly had a faulty kernel, this should be fixed as soon as we flash another ROM, right?
I will be able to try a different ROM on monday. It would be great, if you could report, if the downgrade to GB helped the issue. I'd like to try a different baseband, if you are on the same right now too.
Greetings and thank you so much for trying to help us, vikesh!
paKS7 said:
I'm able to also confirm, that Procedure II didn't help the problem. I really doubt it is a hardware fault, because of us two having the exact same problem after flashing the same rom.
@Dippn: Do you know which nightly build you used? In my case it was the nightly build "20130405". Also could you check which baseband you are on? (Under About Phone -> Baseband Version) Over here we have i9103NEKI1
The only special thing we did I can think of is flashing a modem file (when we were still on the unofficial cm10.1 without these kind of problems, but massive battery drain), because there was a call problem going on for customers of the austrian provider 3 and CM10.1.
I could analyse the problem a bit more today: It seems as soon as the phone gets busy (for example from the browser loading pages or in DippN's case processing a game), the touch screen gets unresponsive and everything starts to lag and delay or freezes completely until it shuts down the phone. Could be either CPU or RAM related, I guess. I just wonder what caused this, even if the nightly had a faulty kernel, this should be fixed as soon as we flash another ROM, right?
I will be able to try a different ROM on monday. It would be great, if you could report, if the downgrade to GB helped the issue. I'd like to try a different baseband, if you are on the same right now too.
Greetings and thank you so much for trying to help us, vikesh!
Click to expand...
Click to collapse
Well, we are not on the same baseband. I'm on I9103XXLQ3.
About the cm verison im not quiet sure, the latest i flashed was "20130406" but since the problem were there the time before that when i flashed cm I cant answer exacly but i have a cm version "20130305" on my desktop and it could be that one that I used.
I never used cm before it was on nightlies so the modem file flashing i dont know anything about.
The thing you mention about that it shuts of when the phone gets busy and touchscreen gets unresponsive I can kind of confirm too.
I will flash GB now, will report back in an hour how it went.
kataria.vikesh said:
It shouldn't be happened. But if u are feeling so, just flash any stock GB using odin v1.87. Then just wipe all data and cache. Install cm10.1 over that using method 2.
Sent from my GT-I9103 using xda premium
Click to expand...
Click to collapse
Are you sure i should do it using v1.87?
I'm having problems finding it and v1.85 seems to be in everyones links.
DippN said:
Are you sure i should do it using v1.87?
I'm having problems finding it and v1.85 seems to be in everyones links.
Click to expand...
Click to collapse
Flashed GB using v1.85 and now I am stuck in bootloop, after 10 sec at the samsung logo it restarts and repeat. >.>
When the phone restarted after the flash and after it says "-updating application" it says:
Installing Multi-CSC
Can't access to '/system/csc/NEE/system/'.
Successfully applied multi-CSC.
I have no idea what this means but could it mean anything?
EDIT: I got it to start by wipe cache and data. (thought i should do that when cwm was installed)
Unfortunately already in the startup options when u write wifi password the touchscreen became very unresponsive and when i after a few min had succeded writing the password the phone shut of when it tried to connect to it! :,(
I can also confirm that it still thinks it is charing when it is not becuase the symbol in the statusbar flicked from battery to charging symbol.
Is there anything else softwarerelated that I can do?
DippN said:
Flashed GB using v1.85 and now I am stuck in bootloop, after 10 sec at the samsung logo it restarts and repeat. >.>
When the phone restarted after the flash and after it says "-updating application" it says:
Installing Multi-CSC
Can't access to '/system/csc/NEE/system/'.
Successfully applied multi-CSC.
I have no idea what this means but could it mean anything?
EDIT: I got it to start by wipe cache and data. (thought i should do that when cwm was installed)
Unfortunately already in the startup options when u write wifi password the touchscreen became very unresponsive and when i after a few min had succeded writing the password the phone shut of when it tried to connect to it! :,(
I can also confirm that it still thinks it is charing when it is not becuase the symbol in the statusbar flicked from battery to charging symbol.
Is there anything else softwarerelated that I can do?
Click to expand...
Click to collapse
Wipe data again.. If possible after wiping data Just reflash the GB.
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Jst flash a newer modem in recovery
mugoftee said:
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
Click to expand...
Click to collapse
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
PivotMasterNM said:
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Click to expand...
Click to collapse
That won't help, flashing an older build than what was previously installed without wiping properly will cause problems.
KURDKiNG said:
Jst flash a newer modem in recovery
Click to expand...
Click to collapse
Modem has nothing to do with this.
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
KURDKiNG said:
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
Click to expand...
Click to collapse
Most likely pure coincidence.
Thanks your reply!
Heisenberg said:
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
Click to expand...
Click to collapse
Actually this is what I did in the very first beginning but I encountered the same rebooting symptoms like after the OTA update. Since it didn't seem to change anything I didn't mention it. I used cm-12.1-YOG4PAS1N0-bacon-signed.
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
mugoftee said:
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
Click to expand...
Click to collapse
I don't think you have any other option unfortunately.
So... This is kind of a rant, but it might as well be a valid question: How do you get Marshmallow working?
I've been struggling to get Lollipop to be stable, but this is even worse. I've been using Cataclysm for a while, and it was fine. Then my alarms stopped working. I said OK, I just reflash. Didn't help.
Flashed Chroma, used it for a while, it was fine, until a decided to clean flash an update. It just doesn't work. And if I flash any other MM ROM, the same thing happens. It just doesn't work. Setup wizard force close. Reflash, retry. Activating data connection, stuck for half an hour, I pressed skip. After that, I tried logging in to my Google account, play services force close, try again. No way to press back, not even after reboot, so reflash AGAIN. This time logging in worked, then I pressed restore apps, guess what, no error message, it decided to throw me back a screen, got into a loop, unfixable by reboot, REFLASH ****ING AGAIN. This time I only flashed it AFTER the first boot, play services and setup wizard force close loop.
Decided the gapps package was at fault, except I've been using the same package for a year, so not really. But I downloaded Banks 6.0. Same problems. Downloaded Open Gapps, SAME.
After that, I deleted the setup wizard from the gapps package, since there is no other way to skip it. Booted fine, but couldn't pull down the quick toggles, home button only worked half the time, the usual "when you skip the setup wizard" issues. I was angry decided to flash Lollipop, because that usually works, now I'm stuck at the ****ing Google logo.
I've been flashing **** for years, I know how to do it. I'm also a patient person. If something doesn't work for the first time, I try again, and again, and again. But this is stupid. KitKat is THE last version of Android that works. Of course all the new features are missing from it, so what are you gonna do? Use the newer. What do you do when you can't use the newer? You buy an iPhone? I'm not that stupid, so what's next? Aside from flashing CM13? Half the setting don't work or crash, including GPS, but at least it boots and you can install gapps on it.
Any other ways to get this piece of garbage working?
Have you tried stock? Since mm I've been running rooted stock or close to it on three older devices and haven't had problems. I'll use xposed or a custom kernel if I want an improvement over stock, or a minimalist rom.
lynnux said:
Have you tried stock? Since mm I've been running rooted stock or close to it on three older devices and haven't had problems. I'll use xposed or a custom kernel if I want an improvement over stock, or a minimalist rom.
Click to expand...
Click to collapse
I never use stock, but Chroma is close enough. And these issues are not connected to the ROM itself. It's Google being stupid.
Take a complete backup and do flash all with Google image.
Sent from my Nexus 5 using XDA Free mobile app