Database Info

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]

[Q] Constant Reboots with Synergy

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.

[Q] Gapps Stops Working and Persistant Activation

I just flashed my first ROM so I'm not used to this whole thing. I figured that I would have some trouble along the way.
I own a VZW GS3, now running LiquidSmooth 4.2.2. I downloaded the ROM and the gapps that they linked (I didn't install the nightly builds, just the official). However, every time I attempt to sync my contacts, gapps crashes. I haven't really found a good answer via the search bar. I need sync to work, so disabling it isn't an option (plus, half of my contacts are missing). Should I re-flash gapps, or was that not the correct version to use anyways? GooManager is saying that the latest version of gapps for this device is the "20121011" version.
Also, every time I reboot my phone, it goes into this perpetual "Activation is required". That's weird because my IMEI is fine, and I can call/text/surf once I home out of that screen. Has anyone experienced this before?
EDIT: It looks like the sync issue ONLY happens when turning on the "browser" sync option. I've disabled that for now, but I have a new problem.
My "People" app is populated will all of my contacts, however that has not transferred over to my phone's contact list (used for phone and messages). How can I get those contacts names and information moved over?

Regarding the activation on every reboot, do you live in an area with poor reception? Also it seems as that issue only happens to me on certain roms I've tried.

That is not the latest gapps package. Try flashing 20130301.
Sent from my SCH-I535 using xda app-developers app

mr_cj said:
That is not the latest gapps package. Try flashing 20130301.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
That's the one I did flash.
I think I've fixed my issues. I cleared the Cache/Dalvick, flashed the new nightly, and re-cleared. That solved all the gapps problems. As for the activation issues, it still happens intermittently. I'll give Verizon a call if there are still issues.
Thanks everyone!

GPS problem cm10.2 8/7 nightly

Hello
I have issues using Waze as GPS. The GPS appears working But when I start to navigate it works for 5 minutes then GPS doesnt work anymore until a fresh boot on any other APP or WAZE....
is anyone experiencing this problems??
Thanks
Sent from my XT925 using xda app-developers app

Today going to work i made a test using google mapa. I start to navigate GPS works OK, but when it go for 5 minutes the GPS icon on the bar status desapear and the GPS goês stuck. I tried cm 10.1 and I have same problema.
Sent from my XT925 using xda app-developers app

Hi mate,
I've been using CM10.1 since beginning. I only tested 10.2 but it's not my DD cause I like Acid Audio with Noozxoide and it's not compatible with 4.3 yet.
Since July builds I'm noting strange behavior related to GPS... Maybe this apply to your case too using 10.2...
I realised that when I charge through any USB port, GPS brakes. Running Waze for a feel minutes and hangs phone completely. I have to reboot, wipe cache, dalvik and fix permissions. This procedure brings Waze back to life. I run Waze about 3hrs a day, every day, together with bluetooth audio in my car. Everything runs perfect until due to any reason I need to connect phone to a PC USB port again. It only occurs when connected to a PC USB port. With wall charger or car charger, always fine.
Despite dirty flash or clean rom install, this pattern occurs. I flashed official 09/08 CM10.1 yesterday and got the same issue. Maybe it's something with kernel Razrteam didn't passed through yet.
It took me days to perceive that, as everything was fine for 5...6 days and suddenly and without messing with anything the issue started from sudden. I realised the only different thing I've been doing before the hang was charging phone at work through PC.
Hope this experience can help you detect something there!

I tried to use the latest nightly from cm site and it didn't stuck in google maps but it still stuck the GPS in waze and i need to do a fresh boot. Im doing another tests i post in advance
Thanks for tour reply
Sent from my XT925 using xda app-developers app

vini81 said:
I tried to use the latest nightly from cm site and it didn't stuck in google mapa bit it still stuck the GPS in waze and i nerd to do a fresh boot. Im doing another tests i post in advance
Thanks for tour reply
Sent from my XT925 using xda app-developers app
Click to expand...
Click to collapse
NP! If nothing fix it, if you have a nandroid backup of a Motorola 4.1.2 flash it and get a GPS lock using your preferred app then do a fresh install of a CM10.1. (with a factory reset wipe). GPS will work fine. But if you do this, don't forget to backup everything as you 'll loose data.

I don´t know how to do this gps lock with nandroid, but i tried others nightlys roms, and the problems still remains!!!
I saw in the CM10.2 post thread, and other users have the same problem.
THanks again!!
flight666 said:
NP! If nothing fix it, if you have a nandroid backup of a Motorola 4.1.2 flash it and get a GPS lock using your preferred app then do a fresh install of a CM10.1. (with a factory reset wipe). GPS will work fine. But if you do this, don't forget to backup everything as you 'll loose data.
Click to expand...
Click to collapse

Strange boot loop with CM 10.1.3 RC2 and stable

My phone will on occasion go into a bootloop where the phone boots to the lock screen but instead of the lock screen it will display the camera widget that I have activated right of the lock screen. The phone will promptly reboot son after displaying the strange lock screen widget.
This happens in both the RC and stable versions. Has anyone else encountered this?
I am using Snap camera as an FYI.
[UPDATE]
Widget does not seem to drive this issue any longer. I've disabled the widget and the phone will continue to bootloop as described below.
Sent from my One S using xda app-developers app

abracadabra11 said:
My phone will on occasion go into a bootloop where the phone boots to the lock screen but instead of the lock screen it will display the camera widget that I have activated right of the lock screen. The phone will promptly reboot son after displaying the strange lock screen widget.
This happens in both the RC and stable versions. Has anyone else encountered this?
I am using Snap camera as an FYI.
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Wiped system.
Did clean install of CM 10.1.3 stable (was previously running off a CM 10.0 stable release that was upgraded to 10.1.3 RC2, then 10.1.3 stable).
Bootloop doesn't seem to occur anymore (though it's only been two days) and battery life is significantly improved. Was getting about 16 hours on previous install, now getting over 48 hours (mostly standby time).

So apparently I was wrong. Same problem in 10.1.3 even after clean install. Phone will go into crazy bootloop aster which battery consumption will be insane. Screenshots attached. Not sure what's going on, but may be radio driven after boot loop. No change in location so signal shouldn't be crazy like this. Thoughts?
Sent from my One S using xda app-developers app

abracadabra11 said:
So apparently I was wrong. Same problem in 10.1.3 even after clean install. Phone will go into crazy bootloop aster which battery consumption will be insane. Screenshots attached. Not sure what's going on, but may be radio driven after boot loop. No change in location so signal shouldn't be crazy like this. Thoughts?
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Were you ever able to solve this problem? I'm having a similar one...

rnick1976 said:
Were you ever able to solve this problem? I'm having a similar one...
Click to expand...
Click to collapse
Nope. Not a damn clue what to do at this point. I'm thinking about reverting to CM 10.0 stable.
10.1.3 stable is not in fact stable.
Although I originally thought it was the camera widget driving the reboots, it definitely is not. My phone will go into boot loops (it just did so while charging) periodically. The one thing I do notice is that the battery temp generally starts going up and then reaches a point at which the phone starts to boot loop and won't stop unless manually forced to shutdown. It will continue the bootloop until drained.

I'm having this issue also on 10.1.3 'stable', I did solve it temporarily by re-flashing boot.img and turning it off at night to charge, hasn't happened for two days now.
Has anyone opened a support ticket with CM?
also quoting my previous thread -
Hi guys,
So yesterday I updating my HTC One to CM10.1.3 Stable release from some older 10.1.1 nightly, using the OTA updater, it flashed fine, then I put it into fast boot in order to manually flash boot.img uing adb. That worked, it booted no issues.
A couple of hours later, the phone just turned off, it was sitting in my desk, I saw the screen flash, it then rebooted, and bootlooped on the CM start up screen. I thought okay maybe the boot.img didn't flash right, so flashed again (note the boot.img used was extracted from the update zip file, so I am assuming is the correct one)
After flashing the boot.img again, starts up fine.
Then again at like 3am, the bright startup screen woke me up, and it was bootlooping again while on charge. I have no idea what's going on, it works fine besides that, I'm posting from my phone as well.
Anyone else having this issue? Or any way to solve it?
Click to expand...
Click to collapse
---------- Post added at 09:44 AM ---------- Previous post was at 09:29 AM ----------
Possibly found one of the potential issues - https://jira.cyanogenmod.org/browse/QSDB-71

arono7342 said:
I'm having this issue also on 10.1.3 'stable', I did solve it temporarily by re-flashing boot.img and turning it off at night to charge, hasn't happened for two days now.
Has anyone opened a support ticket with CM?
also quoting my previous thread -
---------- Post added at 09:44 AM ---------- Previous post was at 09:29 AM ----------
Possibly found one of the potential issues - https://jira.cyanogenmod.org/browse/QSDB-71
Click to expand...
Click to collapse
Haven't opened a support ticket because the boot loops seem to happen when I'm away from home and can't run a logcat. Not entirely sure what I need to open a ticket either. Any guidance?

abracadabra11 said:
Haven't opened a support ticket because the boot loops seem to happen when I'm away from home and can't run a logcat. Not entirely sure what I need to open a ticket either. Any guidance?
Click to expand...
Click to collapse
If anyone else could run a locgat on this it would be great. But I'm unsure if anything will be done because there's a code freeze on 10.1.3
This is the Cyanogenmod forum, where others are reporting the same issues, apparently it's a kernal update issue - http://forum.cyanogenmod.com/forum/763-htc-one-s-stablercm-release/
I updated to the 10.2 nightlies - which I wouldn't advise because my now wifi is broken and my touchscreen calibration is inverted on the x axis :crying:

Reverted to CM 10 stable today. 10.1.3 has some nice features, but nothing too special. Couldn't deal with the instability and random reboots. CM for One S hasn't been decent since 10.0
Sent from my HTC One S using xda app-developers app

I dont seem to be facing any problem with cm 10.1.3 up to now. I think its pretty stable.
Sent from my One S using xda app-developers app