Related
Old info:
Hi, i've a Captivate, with the latest build of CM7.
Today, again, I had an error, which made me FC in all applications (Google Search, Google services, Browser, Angry Birds, background apps) and went on the WiFi automatically.
When I turn off the WiFi, it automatically turns on again.
It's like the fourth time it happens (this is the first time it happens after a full format flash!), with some Builds of CM7, and apparently the only way to fix this is by reinstalling the ROM.
There is nothing in particular that seems to start the bug. It just happen!!
Click to expand...
Click to collapse
New Info!! (Solution?):
Today, i've installed the latest Nightly (kang) from Atinm, dated 29 May.
After a few hours playing with it, the Stock Browser crashed to Home, and again, everything FC!!
Fighting against the constants FC of everyapp, i managed to get into Advanced Task Killer, and i saw that the CM FOTAKill app was open.
Everytime that the FC bug happened, the FOTAKill app was open, so...
I deleted it from /system/app/, rebooted and the problem was solved!!!
Strange indeed. Going into recovery and wiping your data, and caches doesn't seem to fix it?
I've heard the latest build of cm7 is stangely buggy, I suggest "downgrading" to an earlier version.
studacris said:
I've heard the latest build of cm7 is stangely buggy, I suggest "downgrading" to an earlier version.
Click to expand...
Click to collapse
are you talking about build #16?
I stopped upgrading at 13.. They started coming out buggy like you said. haven't tried 16. One user reported it working really well.
Bump for fixed problem!
For about a week now my KFHD running CyanogenMod 10.1 has been powering off randomly. I think each time it has happened, I have been playing or attempting to play audio or video. This is an instant power-off, rather than a proper shutdown -- i.e., the screen goes black, and I have to go through the boot sequence when I power it back on.
This might be a coincidence, but the first time it happened was very shortly after I added a second user account. I was trying to play a podcast with the WTF app, and it suddenly turned off. After the first power-off I booted up the tablet and went straight to the WTF app, and played a couple of seconds of audio before it turned off again; this happened repeatedly, maybe three times in a row.
I removed the second user account, on the chance this was related to the power-offs, but since then it has happened several more times. I believe these other times I was using the Stitcher radio app (audio) and Netflix (video). I noticed the last few times the battery level was pretty low -- i.e., approaching 15% -- but I can't say if this has been the case every time. I think the first time it happened the battery level was higher, but I can't be sure.
I suppose I should look to see if there are any clue in the system logs, but I wanted to know if anyone has encountered this problem before. (Also, I just noticed that when I try to run 'adb' to inspect the logs from my Mac, it says the device is "offline." I haven't seen this before, but I don't know if I've tried to use adb since I installed CM a couple of months ago.) Apart from installing a custom firmware, I haven't done anything else to my device that might make it unstable, like overclocking it.
I'm guessing the kernel is crashing, do you have viper4android installed? I had a similar problem with my cm 10.1 os a few weeks back, when having keyboard sounds on and typing really fast with viper on my kernel was crashing. If you don't have that or acid installed, then try wiping the system partition and reflashing the ROM, you won't lose any data. You might be able to debug it by continuously using your kindle while hooked up to your PC and running adb logcat, and waiting for it to crash and seeing what it said last in the log before it crashes. Idk if kernel errors show up there though, and I dunno how to view a continuous view of the kernel log outside of repeatedly running dmesg.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Several users have been dealing with a similar issue regarding CM10.1. I would suggest upgrading to 10.2 or trying a different ROM altogether to see if you get the same results.
@stunts513: I don't have viper4android or keyboard sounds, but it does seems like the kernel is crashing. I haven't had time to figure out why adb isn't working for me right now, but when I do I'll see if I can make it crash and watch the log.
@soupmagnet: Thanks for the tip. I've been waiting till the next build of 10.2, but maybe I'll give it a try sooner.
stunts513 said:
I'm guessing the kernel is crashing, do you have viper4android installed? I had a similar problem with my cm 10.1 os a few weeks back, when having keyboard sounds on and typing really fast with viper on my kernel was crashing. If you don't have that or acid installed, then try wiping the system partition and reflashing the ROM, you won't lose any data. You might be able to debug it by continuously using your kindle while hooked up to your PC and running adb logcat, and waiting for it to crash and seeing what it said last in the log before it crashes. Idk if kernel errors show up there though, and I dunno how to view a continuous view of the kernel log outside of repeatedly running dmesg.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
soupmagnet said:
Several users have been dealing with a similar issue regarding CM10.1. I would suggest upgrading to 10.2 or trying a different ROM altogether to see if you get the same results.
Click to expand...
Click to collapse
jay-roc said:
@stunts513: I don't have viper4android or keyboard sounds, but it does seems like the kernel is crashing. I haven't had time to figure out why adb isn't working for me right now, but when I do I'll see if I can make it crash and watch the log.
@soupmagnet: Thanks for the tip. I've been waiting till the next build of 10.2, but maybe I'll give it a try sooner.
Click to expand...
Click to collapse
I had the same issue with 10.1. I upgraded to 10.2, same issues. Random shutdowns. Sometimes it doesn't even load CM all the way before crashing when starting up the KFHD. Should I create a new thread or continue here?
GrecoISU said:
I had the same issue with 10.1. I upgraded to 10.2, same issues. Random shutdowns. Sometimes it doesn't even load CM all the way before crashing when starting up the KFHD. Should I create a new thread or continue here?
Click to expand...
Click to collapse
Going from CM10.1 to CM10.2 doesn't really rule much out if they are both from the same developer/device tree/etc. Have you tried installing a completely different ROM like Kinology or PA to see if the results are the same?
soupmagnet said:
Going from CM10.1 to CM10.2 doesn't really rule much out if they are both from the same developer/device tree/etc. Have you tried installing a completely different ROM like Kinology or PA to see if the results are the same?
Click to expand...
Click to collapse
No. I haven't yet. I've been a bit apprehensive about it. Can I just download, move to SD, then wipe and install?
GrecoISU said:
No. I haven't yet. I've been a bit apprehensive about it. Can I just download, move to SD, then wipe and install?
Click to expand...
Click to collapse
I don't see why not
soupmagnet said:
I don't see why not
Click to expand...
Click to collapse
I followed all directions for Kinology but I'm getting crashes every time I try to unlock the lockscreen. Only twice I've seen the setup options (language) and both times it's crashed prior to making a selection.
Edit: Redid everything following directions and I'm still getting a lockscreen crash as I swipe to unlock.
Edit 2: I'm just going to restore completely and try everything fresh.
If I remember right, when going from a amazon os to a cm ROM and vice-versa, you need to do a factory reset before you flash the ROM (kinology), also wipe cache, dalvik cache, and system before the flash.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
If I remember right, when going from a amazon os to a cm ROM and vice-versa, you need to do a factory reset before you flash the ROM (kinology), also wipe cache, dalvik cache, and system before the flash.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
this^^
I recently upgraded to milaqs 4.4 rom and have been plagued with issues since then, some of which include:
no camera
sleep of death (seems to only happen when using Google now launcher, may occur with other custom launchers)
random reboots, mostly when in sleep
google sync errors
getting stuck in a reboot
certain apps like youtube stop working properly after some time
time resets to jan 1st 1970 on every reboot
wallpaper and saved wifi networks reset seamingly at random when rebooting
playstore crashes when trying to install apps often
when restoring and redownloading apps, sometimes apps get stuck on "installing" until rebooting
can mount legacy storage but cannot open, transfer or delete items from it
sliver about 2 pixels wide on right side of screen when in landscape unless changing dpi to 155
This is running on the feb 27th nightly build
Is anybody else having similar issues?
Netflix
Hi for me this is a very stable build. the best I've tried so far.
The only Problems I have are:
No Camera ( I don't use it so not a big deal)
I do get the installing apps issue sometimes but hasn't happen in a week.
Netflix was broken. But I found away to get it working. after searching the web found someone who said to download the older 2.4 or 2.4.1 and it will work. I downloaded it. This worked. Now I have a working Netflix app.
It was quite a hassle to find the 2.4.1 version. Don't forget to turn off auto updates for the apps or it will install the lastet Netflix app which doesn't work for kitkat yet.
The kitkat 4.4.2 builds are new and I expect them to be buggy. But I'm really thankful that they are underdevelopment. They are really really good. The Milaq build in particular is great. I'm now using this for my day to day use. I don't really have to many complaints with it. I'm running the latests build Mar 02 nightly build.
sleep of death
Well I had the sleep of death on the Mar 2 build of CM11 Milaq. This is only the second time its happen to me since I installed this build about 3 weeks ago. had to press the power and the home button to re-boot. its works fine now. will keep you posted
webcam doesnt work
tgg05 said:
Well I had the sleep of death on the Mar 2 build of CM11 Milaq. This is only the second time its happen to me since I installed this build about 3 weeks ago. had to press the power and the home button to re-boot. its works fine now. will keep you posted
Click to expand...
Click to collapse
for me webcam doesnt work reliably
Tried it and cm10.2 back at Christmas, but some important - to me - things were not working - Bluetooth, camera, ... devs have since worked their magic... jcsullins 5/4 build seems v good - e.g. best Skype stability I have ever had.
Sent from my TouchPad using Tapatalk
Everything H/W is working for me on CM11 from milaq
:good: Everything hardware and application is working quite nicely and stable too!
Where I am having some issues is with ROOT access.
For example trying to create the moboot.default file with any of the valid file managers is not working. I have had to use a recovery file to actually get the file created with the default boot image I wanted.
Besides that it is running quite nicely and stable.
Mind you I have done a clean install from scratch (which is usually recommended) since I was running CM10.1 prior to migrating to CM11.
I believe the issue above is based on some modifications GOOGLE has implemented, but even the available fixes are not working for me to gain access to the SD CARD partitions.
A big thank you to milaq for this great still evolving ROM build.
Running the 20140429 nightly at the time of writing this post.
Try Rom Toolbox.
milaq cm11 4.4.4 latest update
sstar said:
Try Rom Toolbox.
Click to expand...
Click to collapse
Running Milaq cm11 4.4.4 latest update. Everything seems to be working fine. Solid ROM.
Hey all, I recently followed all the guides on here to update my TP. Was runningn CM9 for over a year, and needed a change. Decided on Jcsullins snapshot, cm-10.1-20131210-SNAPSHOT-VPN-tenderloin.zip, as I need bluetooth and camera to work, and also wanted low battery drain. Did a complete acme uninstall of android, repartitioned system to 600mb, and then used tptoolbox to install.
Now, the rom was very smooth through setup. However, after I started installing apps, about 30, it became very sluggish. pressing the home button I would have to wait about 10 seconds for it to actually go home. Apps would take 10 seconds to startup. Web/facebook scrolling was horribly choppy. Interesting though, if I rebooted, the tablet would run very smooth for the first few minutes. Only after that did it start to become slow.
So I decided to reflash the rom. Did a full wipe in CWM, and reinstalled. Again, tablet was running fine. I decided to only install a few apps this time, about 6, and everything seemed fine. But after a few minutes again, it got sluggish.
I'm wondering if maybe using tptoolbox messed something up? From everything I read about that rom, nobody has any problems with it being slow.
Also, I don't really want a heavily modified rom, which is why I haven't tried the Schizoid rom. I would like to stay at 10.1 for stability. I see the official CM nightlies here: http://forum.xda-developers.com/showthread.php?t=2290346
However, there are no download links to that rom, the link goes to the 10.2 download page. I didn't really want to get into a DM rom at this point. And it seems that bluetooth isn't working on that rom? Am I correct in saying that besides Schizoid, jcsullins 10.1 is the only 10.1 with bluetooth fully working?
Hum, got the same problem 1 year ago, my cm partition at the time was full, Using the TP Toolbox, try to give some space to the cm partition sacrificing some from the shared partition. There are more than 1 cm named partition, i don't remember exactly which one at the time was the faulty. Maybe it was the media partition.
sitlet said:
Hey all, I recently followed all the guides on here to update my TP. Was runningn CM9 for over a year, and needed a change. Decided on Jcsullins snapshot, cm-10.1-20131210-SNAPSHOT-VPN-tenderloin.zip, as I need bluetooth and camera to work, and also wanted low battery drain. Did a complete acme uninstall of android, repartitioned system to 600mb, and then used tptoolbox to install.
Now, the rom was very smooth through setup. However, after I started installing apps, about 30, it became very sluggish. pressing the home button I would have to wait about 10 seconds for it to actually go home. Apps would take 10 seconds to startup. Web/facebook scrolling was horribly choppy. Interesting though, if I rebooted, the tablet would run very smooth for the first few minutes. Only after that did it start to become slow.
So I decided to reflash the rom. Did a full wipe in CWM, and reinstalled. Again, tablet was running fine. I decided to only install a few apps this time, about 6, and everything seemed fine. But after a few minutes again, it got sluggish.
I'm wondering if maybe using tptoolbox messed something up? From everything I read about that rom, nobody has any problems with it being slow.
Also, I don't really want a heavily modified rom, which is why I haven't tried the Schizoid rom. I would like to stay at 10.1 for stability. I see the official CM nightlies here: http://forum.xda-developers.com/showthread.php?t=2290346
However, there are no download links to that rom, the link goes to the 10.2 download page. I didn't really want to get into a DM rom at this point. And it seems that bluetooth isn't working on that rom? Am I correct in saying that besides Schizoid, jcsullins 10.1 is the only 10.1 with bluetooth fully working?
Click to expand...
Click to collapse
Atari-San said:
Hum, got the same problem 1 year ago, my cm partition at the time was full, Using the TP Toolbox, try to give some space to the cm partition sacrificing some from the shared partition. There are more than 1 cm named partition, i don't remember exactly which one at the time was the faulty. Maybe it was the media partition.
Click to expand...
Click to collapse
You can check the size of your partitions by typing "df" without quotes into terminal emulator.
Hope this helps.
Thanks for the suggestions. I checked the partitions, and they are all good. I ended up reflashing a third time, and I've been running it for two days, and it's been fine 90% of the time. A few slow downs, but nothing like before.
However I do have another problem, and I don't know if it's rom related or not. I have an HP slim bluetooth keyboard that paired successfully with the tablet. Works perfectly, except if I leave the tablet unattended for about 15 minutes or so, it doesn't work. I'm fairly sure the keyboard itself is going to sleep. However, when I wake it and the tablet up, the tablet freezes completely. Tonight it even rebooted itself twice. Once was on it's own after I tried to wake the keyboard up by pressing a few buttons. The other I turned the keyboard off and back on, and when it was connected the tablet rebooted.
Seem related to a rom problem with drivers support for bluetooth accessory. If it was working before with the same roms, try to reflash it, otherwise, try another roms or early/newly build.
I had the Nook HD+ running CyanogenMod for a few years.
I changed nothing, but lately it stopped working, complaining about Trebuchet, so I changed the launcher and it worked again, but giving occasional errors about an app not starting.
In the last few days it also started sporadically rebooting itself. Plunging it in did not seem to change anything. Lowering the max CPU speed from 1.5GHz to 1.1 did not help.
Now, it would not start at all – it would always get stuck at the circling CyanogenMod boot screen. It would still shut down using a long press.
I can start the rescue fine, with no unwanted reboots.
I do have a small amount of data there that I would like to be able to take out, if possible.
I don't care for any specific OS version/mod.
What do you think is the cause of this issue?
How can I fix this? Can I get the Data out?
Btw, in the years it was working, it did have an issue of sometimes restarting instead of shutting down.
I never knew if it was a fault with my device or the with latest CM.
Kov8 said:
I had the Nook HD+ running CyanogenMod for a few years.
I changed nothing, but lately it stopped working, complaining about Trebuchet, so I changed the launcher and it worked again, but giving occasional errors about an app not starting.
In the last few days it also started sporadically rebooting itself. Plunging it in did not seem to change anything. Lowering the max CPU speed from 1.5GHz to 1.1 did not help.
Now, it would not start at all – it would always get stuck at the circling CyanogenMod boot screen. It would still shut down using a long press.
I can start the rescue fine, with no unwanted reboots.
I do have a small amount of data there that I would like to be able to take out, if possible.
I don't care for any specific OS version/mod.
What do you think is the cause of this issue?
How can I fix this? Can I get the Data out?
Click to expand...
Click to collapse
Hi Kov8.
I was running CM 11.1 for ovation and experienced the same thing. My solution was to install a newer version.
To save your data, set up an SD card (be sure you have enough extra room for your data) with the TWRP 3.0.1-0 version here:
https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3332706778
Load TWRP and look for the File Manager. I think it's under "Advanced." You can use that to copy or move your data to the SD card.
After that, consider upgrading to AOSP or LNOS. I can install AOSP without much difficulty, but LNOS doesn't go well. More on that in a later post.
If you need more detailed information, look at this post and download the pdf at the end of the first post:
https://forum.xda-developers.com/nook-hd/general/install-cyanogenmod-12-1-barnes-noble-t3211119
Kov8 said:
Btw, in the years it was working, it did have an issue of sometimes restarting instead of shutting down.
I never knew if it was a fault with my device or the with latest CM.
Click to expand...
Click to collapse
Yes. I've been reading that all the recent ROMs do that.
The solution is to do a standard shutdown followed by a hard shutdown (by holding the power button for 8 seconds).
I suspect that going straight for the hard shutdown caused some file system errors that made installing new ROMs very difficult.
I'm OK now, though.
Thanks for the detailed reply! I will try.
The link for TWRP does not work. Can I install the latest, 3.2.1.0?
Kov8 said:
The link for TWRP does not work. Can I install the latest, 3.2.1.0?
Click to expand...
Click to collapse
That's funny. I just downloaded two copies from that link.
For version 3.2.1-0, it sounds like you're looking at the version from the team win website. I haven't tested that one thoroughly, but I have tried out their version 3.1.1-0. It works pretty well. It gave me some minor error messages here and there, but if I just repeated what resulted in the error, it generally went through on the second attempt without an error.
The link worked for me later. I managed to change to TWRP 3.0.1-0 only after removing the version identifier from the zip file. I later easily upgraded TWRP to the newest.
I also upgraded to the latest AOSP from the same source, without deleting, as I couldn't get the data from one app. I then installed ARM 7.1 pico gapps. Some apps kept crashing, but removing and reinstalling seems to have fixed that.
The only problem, is that now shut down never works, and restart always takes me to recovery. So I just hard shutdown there.
Kov8 said:
The link worked for me later. I managed to change to TWRP 3.0.1-0 only after removing the version identifier from the zip file. I later easily upgraded TWRP to the newest.
I also upgraded to the latest AOSP from the same source, without deleting, as I couldn't get the data from one app. I then installed ARM 7.1 pico gapps. Some apps kept crashing, but removing and reinstalling seems to have fixed that.
The only problem, is that now shut down never works, and restart always takes me to recovery. So I just hard shutdown there.
Click to expand...
Click to collapse
Mind telling how you managed to update twrp from 3.0 1 to the latest? I successfully installed 3.0.1 to my nook hd+, then flashed 3.2.1 img to recovery, now the device stuck at boot.
I simply downloaded to img file from their website (for ovation, my device), placed on the micro-sd, and installed it from TWRP itself. As simple as that.
Are you sure that you got the correct version for your device?
I also always verify the integrity of roms after writing them to a card. I've seen bad cards.