Has anyone had problems with the new Cyanogenmod 10.1.3 freezing and crashing periodically?
I did a brand new clean full reinstall (not an upgrade). Still have the problem.
Any thoughts on what might be causing this?
Thank you.
Windstorm1981 said:
Has anyone had problems with the new Cyanogenmod 10.1.3 freezing and crashing periodically?
I did a brand new clean full reinstall (not an upgrade). Still have the problem.
Any thoughts on what might be causing this?
Thank you.
Click to expand...
Click to collapse
Are you under-volting?
... and why not try CM 10.2?
Sent from my SCH-I535 using xda app-developers app
epagib said:
Are you under-volting?
... and why not try CM 10.2?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Not familiar with volting. How do I know/check to see if I'm doing that?
I was running CM 10.2 and it was working. Suppose I could go back. I'd just prefer to stay at 10.3 if I can fix this. Reason is that I would want to do a clean install of 10.2 and that would require all the formatting, app set up etc. Don't want to load up from my nandoid since I simply installed updates from CM 10.1 up through 10.2 and things started to get corrupted.
Thanks.
Chances are you're not undervolting then. Custom kernels allow us to do that.
Sounds like you've been taking the nightly updates and after awhile the problem arise?
I'd try to clean cache, clean dalvik cache, and fix permissions. Then reboot.
Of that doesn't work, then would have to do a clean reinstall
epagib said:
Chances are you're not undervolting then. Custom kernels allow us to do that.
Sounds like you've been taking the nightly updates and after awhile the problem arise?
I'd try to clean cache, clean dalvik cache, and fix permissions. Then reboot.
Of that doesn't work, then would have to do a clean reinstall
Click to expand...
Click to collapse
No - haven't been taking the nightlies. Only the stable versions.
In installed CM 10.1.3 as a clean install twice - including cleaning the cache and the dalvik cache.
I actually saw another mention on the web about another GSIII user seeming to have the same problem.
Related
Hey, so as stated in the title, I have recently flashed Cyanogenmod7. Initially, version 7.2.0 and then the nightly build released on 10/7/12. I can no longer receive mobile data. I realize this is a very common problem and have searched through multiple forum posts here and elsewhere online. I also flashed a new kernel in an attempt to fix it (not sure of the name, found here: http://forum.xda-developers.com/showthread.php?t=1073626).
Mobile data will appear (and work) for the first 10-15 seconds after startup if wifi is disabled but then vanishes afterwards. I have tried changing the mobile network settings and apn settings in a number of ways but no method ever works (most of the ones found online appear to be at least a year old so perhaps I just need more modern entries). Any help would be greatly appreciated.
viveksmother said:
Hey, so as stated in the title, I have recently flashed Cyanogenmod7. Initially, version 7.2.0 and then the nightly build released on 10/7/12. I can no longer receive mobile data. I realize this is a very common problem and have searched through multiple forum posts here and elsewhere online. I also flashed a new kernel in an attempt to fix it (not sure of the name, found here: http://forum.xda-developers.com/showthread.php?t=1073626).
Mobile data will appear (and work) for the first 10-15 seconds after startup if wifi is disabled but then vanishes afterwards. I have tried changing the mobile network settings and apn settings in a number of ways but no method ever works (most of the ones found online appear to be at least a year old so perhaps I just need more modern entries). Any help would be greatly appreciated.
Click to expand...
Click to collapse
The CM team has yet to fix this, and I doubt it ever will be fixed. It's present on all AOSP based ROMS. I guess if they set the modem to reset on bootup, it could fix it, but I have no idea how to do that.
FatalityBoyZahy said:
The CM team has yet to fix this, and I doubt it ever will be fixed. It's present on all AOSP based ROMS. I guess if they set the modem to reset on bootup, it could fix it, but I have no idea how to do that.
Click to expand...
Click to collapse
So, to get my data back should I just reflash stock?
Have you tried hard resets? Holding power and volume up until the phone reboots?
buru898 said:
Have you tried hard resets? Holding power and volume up until the phone reboots?
Click to expand...
Click to collapse
Yeah, I've tried that. Still nothing.
I am using cm7 no problem with data whatsoever you shoud try wiping cache and dalvik cache and after that fix permissions and if u wanna install a custom kernel thats what i do when i flash a rom and works fine
Sent from my LG-P999 using xda app-developers app
ted619 said:
I am using cm7 no problem with data whatsoever you shoud try wiping cache and dalvik cache and after that fix permissions and if u wanna install a custom kernel thats what i do when i flash a rom and works fine
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
I've also tried wiping the cache and dalvik cache with no effect. I have also installed a custom kernel with no effect. I am not entirely sure what you mean by fixing permissions.
Edit: searched and figured it out. Tried fixing permissions in combination with the other two options. Still no effect.
Sorry to bump an old topic but I accidentally reflashed Cyanogen (pressed wrong zip in recovery) and now it's working so if anyone else has this problem, try doing a factory reset and then reflashing old data.
I accidentally installed the 10.1 nightly (it was erroneously offered via auto-update)
Notifications and WiFi tether don't work, so I need to return to 10.0.
Is there any non-destructive way to do this downgrade? I'm getting really sick of wiping and re-installing everything!
z0s0 said:
I accidentally installed the 10.1 nightly (it was erroneously offered via auto-update)
Notifications and WiFi tether don't work, so I need to return to 10.0.
Is there any non-destructive way to do this downgrade? I'm getting really sick of wiping and re-installing everything!
Click to expand...
Click to collapse
Yes, re-install the rom from recovery. Wipe cache + dalvik and re-install JB 4.1.2 gapps if needed. Then fix permissions and reboot.
Don't need to wipe data/factory reset.
I checked my claims because I was curious. You will need to wipe. :/
Hmm.. yeah I suspected as much.
Damn.
z0s0 said:
Hmm.. yeah I suspected as much.
Damn.
Click to expand...
Click to collapse
On the upside, CM10 is sooooo much better than CM10.1. My phone feels new.
polobunny said:
On the upside, CM10 is sooooo much better than CM10.1. My phone feels new.
Click to expand...
Click to collapse
Something is definitely changed after NS lost support from JBQ and his boys. 4.1.2 which is based on actual sources for the NS from Google definitely still runs better than some zomgfastbatterysaving 4.2 ROMs.
Here a how I've dirty flashed ROMs without issues. Of course I make a backup first. Then, I wipe cache, wipe dalvik cache, and format system. Then I flash the ROM, gapps, and reboot. Learned this from the1dynasty. Hope it works.
Sent from my Nexus S 4G using xda app-developers app
PartimusPrime said:
Here a how I've dirty flashed ROMs without issues. Of course I make a backup first. Then, I wipe cache, wipe dalvik cache, and format system. Then I flash the ROM, gapps, and reboot. Learned this from the1dynasty. Hope it works.
Sent from my Nexus S 4G using xda app-developers app
Click to expand...
Click to collapse
This works for most upgrades, but not for most downgrades...
OK thanks for the info
Sent from my Nexus S 4G using xda app-developers app
polobunny said:
On the upside, CM10 is sooooo much better than CM10.1. My phone feels new.
Click to expand...
Click to collapse
10.1 does not run well, glad to know it's not just me.
onehitch said:
10.1 does not run well, glad to know it's not just me.
Click to expand...
Click to collapse
I'm on the last version (I think) of cm10. cm-10-20121220-NIGHTLY-crespo. This had been removed from cm download. only stable remains though.
With marmite v7.2 kernel (no overclock), my nexus s is running without hiccup. Without marmite, I get sporadic ram overran problem with crappy voice calling (in and out calling not working) and sluggishness.
I installed carbon rom and loved the carbon fibers settings, but the rom kept crashing and i had to go back to pa android. i also love pa android but want more tun-ability. Is there an apk or way to install carbon fibers in pa android or something similar?
thank you!
The carbon rom kept crashing because you didn't wipe everything prior to it's installation. Did you wipe data, clear dalvic, format system and then flash the carbon rom and gapps??
vin4yak said:
The carbon rom kept crashing because you didn't wipe everything prior to it's installation. Did you wipe data, clear dalvic, format system and then flash the carbon rom and gapps??
Click to expand...
Click to collapse
I wiped everything. This isnt my first rodeo flashing roms. i have carbon on my nexus 7 with no issues. on my nexus 5 the keyboard keeps crashing.
tysonwald said:
I wiped everything. This isnt my first rodeo flashing roms. i have carbon on my nexus 7 with no issues. on my nexus 5 the keyboard keeps crashing.
Click to expand...
Click to collapse
Since you said the rom kept crashing, I thought you referred to the Android system fcs. Changing the keyboard might have solved it...
About the carbon settings apk... If the carbon settings in integrated to rom, then it won't work on any other roms even if you manage to find its apk and install it.
tysonwald said:
I installed carbon rom and loved the carbon fibers settings, but the rom kept crashing and i had to go back to pa android. i also love pa android but want more tun-ability. Is there an apk or way to install carbon fibers in pa android or something similar?
thank you!
Click to expand...
Click to collapse
vin4yak said:
Since you said the rom kept crashing, I thought you referred to the Android system fcs. Changing the keyboard might have solved it...
About the carbon settings apk... If the carbon settings in integrated to rom, then it won't work on any other roms even if you manage to find its apk and install it.
Click to expand...
Click to collapse
It's integrated within Settings.apk and in the framework itself. "Carbon Fibers" is just the menu in which you toggle/customize your options. Each ROM has it's own "customizations".
Carbon is mostly "stable"; nightly builds but most are daily-driver capable. You probably forgot to wipe or something. I have never experienced instability with the official ROM, only some in my own personal build when experimenting with things.
Just revert back to Carbon, and if your keyboard keeps crashing again, just download Google Keyboard from the play store.Simple as that. I had this issue myself, but upgrading to the next nightly fixed it.
Sent from my Nexus 5 using Tapatalk
Specifically, the bugs associated with encryption, e.g. compass not working properly, twrp backup unable to decrypt (fixed on 38R update). I don't want to go through the process of wiping and starting over again with CM11 snapshots if I don't have too. CM11s offers nothing to me that I can't get on CM11 snapshots. I'm just done waiting for the tremendous amount of bugs on CM11s!
Basically, I want all the funcationality back I had on my Nexus 4 running CM11 snapshots.... which was everything worked with the phone being encrypted!
Thanks.
I'd like to know as well. Is there anyone who can confirm this?
Thanks,
ndy4eva said:
I'd like to know as well. Is there anyone who can confirm this?
Thanks,
Click to expand...
Click to collapse
So I switched to CM11 snapshot. Kept the encryption through the process, so didn't do a full disk wipe, and the compass is still broken.
The last thing to try would be a full data wipe, disk format and reinstall everything from scratch to see if encrypting from CM11 snapshot keeps the compass working.
Sent from my A0001 using XDA Premium HD app
Not sure about the bug(s) BUT i have noticed a huge difference in benchmarking application scores between CM11 Nightlies and CM11s.
On CM11S my OPO scores 46954 (Version 5.1.5) and on the CM11 Nighlies only 41492 (Also version 5.1.5) - AnTuTu
Not sure how that translates into real world performance, but it was enough to persuad me to stick with CM11s
I made a fresh install of cm11 m11 and my compass is not functional. Decrypting from twrp works flawlessly though.
badaeng said:
I made a fresh install of cm11 m11 and my compass is not functional. Decrypting from twrp works flawlessly though.
Click to expand...
Click to collapse
Damn. The issues doesn't seem to be catching much traction through Jira either. For those that are security oriented like myself, this is a problem. I want my phone decryped and I want it to work properly. Granted, a compass doesn't take away the core functionality; however, it is quite annoying when trying to navigate somewhere.
badaeng said:
I made a fresh install of cm11 m11 and my compass is not functional. Decrypting from twrp works flawlessly though.
Click to expand...
Click to collapse
You encrypted after you installed CM11 M11 then?
stewa2jm said:
You encrypted after you installed CM11 M11 then?
Click to expand...
Click to collapse
Fresh install including data and sdcard wipe, encrypted by cm11 m10.
I did install m10 and not m11 as I wrote above. Just upgraded.
badaeng said:
Fresh install including data and sdcard wipe, encrypted by cm11 m10.
I did install m10 and not m11 as I wrote above. Just upgraded.
Click to expand...
Click to collapse
Thanks! Looks like it is a bigger issue than just between CM11 & CM11s.
I was hoping the snapshots didn't have that issue.
Sent from my A0001 using XDA Premium HD app
They have a lot less bugs, and if they do, they get fixes about a month before.
I flashed cyanogenmod 13 and gapps for marshmallow (from 6.12.2015) and it boots fine. All apps are installed, as before the update.
BUT
When I start any of these apps they seem to be reset to default as if they are newly installed. For example Threema starts setup process after start.
App data is still present on internal storage (did not wipe), but apps do not seem to have access to any of this data.
Can anyone help what I can try to get the apps back to work with previous data?
Thankful for any help!
Greets
Daniel
At first, try flashing CM13 after a full wipe or try using another rom since CM13 could be buggy.
Primokorn said:
At first, try flashing CM13 after a full wipe or try using another rom since CM13 could be buggy.
Click to expand...
Click to collapse
Thanks for the reply! But well, the phone is working, just the apps are behaving as if they are newly installed ... So a full wipe would not really help as is only deletes more data. The question is why do the apps "think" they are not already set up?
d-trip said:
Thanks for the reply! But well, the phone is working, just the apps are behaving as if they are newly installed ... So a full wipe would not really help as is only deletes more data. The question is why do the apps "think" they are not already set up?
Click to expand...
Click to collapse
That's why we "always" backup user data before flashing a new rom
Primokorn said:
That's why we "always" backup user data before flashing a new rom
Click to expand...
Click to collapse
Full ACK, but data is still available on the internal storage, but the apps do not notice this?
AND this one here (not allowed ot post links... so a missing w at the beginning ww.cyanogenmod.org/blog/a-marshmallowy-cm) says dirty flash from 12.1 to 13 is okay and if the cyanogenmod updater shows cm13 as availabe for update ...
EDIT: Maybe this was a missing info, but it was "just" a normal update via cyanogenmod updater, not a real flash of a new rom!
d-trip said:
Full ACK, but data is still available on the internal storage, but the apps do not notice this?
AND this one here (not allowed ot post links... so a missing w at the beginning ww.cyanogenmod.org/blog/a-marshmallowy-cm) says dirty flash from 12.1 to 13 is okay and if the cyanogenmod updater shows cm13 as availabe for update ...
EDIT: Maybe this was a missing info, but it was "just" a normal update via cyanogenmod updater, not a real flash of a new rom!
Click to expand...
Click to collapse
What do you want me to say? It's always better to full wipe when upgrading to a new Android version. Period.
Moreover, CM13 nightlies are buggy. There are important bugs and fixes everyday. Make a nandroid backup and try from scratch or try another nightly or another custom rom. There's nothing else to say IMO.
Primokorn said:
What do you want me to say? It's always better to full wipe when upgrading to a new Android version. Period.
Moreover, CM13 nightlies are buggy. There are important bugs and fixes everyday. Make a nandroid backup and try from scratch or try another nightly or another custom rom. There's nothing else to say IMO.
Click to expand...
Click to collapse
Just thought it could be possibly just a permission problem, a missing symlink or anything else that could be fixed manually.
d-trip said:
Just thought it could be possibly just a permission problem, a missing symlink or anything else that could be fixed manually.
Click to expand...
Click to collapse
I flashed the first CM13 nighly and I didn't have to do anything to get working apps. Everything has been restored without any issue.