You can get it here: http://get.cm/?device=quincytmo&type=RC
Seems stable. Everything working so far.
I guess I need to go check it out. I'm still on the latest monthly.
As far as I can tell, it is caught up with the nightlies as far as features go: Camera timer, stylus gestures, whatever else is new. Everything I've tested so far works, wifi tether, bluetooth etc,
Yeah, so far so good. It seems pretty stable and fluid. Haven't checked battery life. I noticed on the last nightly that it took longer to charge the battery.
Battery life here seems very good. Very smooth, not getting lagginess that was in a couple of nightlies.
Had a couple of instabilities with a couple of apps. Reinstalling them seems to have fixed the problem. Time will tell.
Sent from my SAMSUNG-SGH-T879 using xda app-developers app
Going back to M3. Having too many instabilities, random reboots, lock ups.
srpanadero said:
Going back to M3. Having too many instabilities, random reboots, lock ups.
Click to expand...
Click to collapse
I was about to say that I haven't seen any bugs with this latest release, but then I thought for a second and remembered that I had a weird screen issue where my screen was flickering, and then went black until I restarted the phone. It only happened once, so I didn't think much of it. I expect a few bugs with any ROM no matter how stable/baked it is.
Here is a bug report for graphical issues. Now is the time to report any bugs that you see.
https://jira.cyanogenmod.org/browse/CYAN-1057
Never saw a blue screen until I used this one. Random reboots also, something I never dealt with before.
Now there's an RC2. Trying it now.
fraughtsigewulf said:
Never saw a blue screen until I used this one. Random reboots also, something I never dealt with before.
Click to expand...
Click to collapse
So then could you and anyone else who've seen the issue sign up and vote on the bug report here: https://jira.cyanogenmod.org/plugins/servlet/mobile#issue/CYAN-1125
Either that or add your own comment and log if you have. Hopefully the devs will then see and fix the problem.
My random reboots seem to have gone away, but I still have the issue of where BT won't turn on unless I reboot, or reboot twice.
hogasswild said:
My random reboots seem to have gone away, but I still have the issue of where BT won't turn on unless I reboot, or reboot twice.
Click to expand...
Click to collapse
Now i'm getting freezes and reboots 5-6 times a day. Today I could hardly use my phone. And that was even after doing a full wipe this morning and reinstalling the latest nightly and Gapps. I think i'm gonna roll back to a version from a couple of months ago if I can find one and see if that helps.
I did go to that dev page that was suggested earlier in the thread and signed up and voted up this issue. I hope it gets the ball rolling.
I'm kinda disappointed. I know these are nightlies and aren't supported, but i'm really used to Cyanogenmod putting out solid builds, even for their nightlies. A few bugs I can deal with, but this is unusable.
Well the night lies are getting worse. The RC1 and RC2 for me are usually OK for a day or so, but the more time goes by and the more frequent the random freeze and reboot.
Back on M3 and that's OK.
error when installing
when I try to install the zip file I get this error "assert failed: getprop("ro.product.device)...." this is just the beginning the type is small and its hard to read- any suggestions? Some searches I've done say this error shows when the ROM is for the wrong phone, but don't see how that can be. I have the T-Mobile Galaxy Note for sure. Thanks for any help that I can get. Since it seems like T-Mobil is never going to upgrade OTA to Jelly Bean I really would like to get this ROM.
Just making sure. You have installed the TWRP recovery? Can't do it unless you have installed this first.
#2. You do not want this ROM(s), read the thread, nothing but problems. My suggestion if you want a custom ROM, is to download the M3 CyanogenMod. Here is the links. http://get.cm/?device=quincytmo&type=snapshot
srpanadero said:
Just making sure. You have installed the TWRP recovery? Can't do it unless you have installed this first.
#2. You do not want this ROM(s), read the thread, nothing but problems. My suggestion if you want a custom ROM, is to download the M3 CyanogenMod.
I was using Clockwork MOD. I will admit I'm a bit of a Newb with this custom recovery stuff. I went to install Goomanager on my phone, but when I reboot it reboots it into Clockwork MOD. So do I need to uninstall clockwork MOD somehow? I will try the other ROM you mentioned, but I think I had tried that one as well and got the same error. Of course this was using clockwork MOD.
Thanks,
John
Click to expand...
Click to collapse
This is the twrp page for this phone.
http://teamw.in/project/twrp2/113
It lists several ways to install it. Try them all, one will work.
srpanadero said:
Well the night lies are getting worse. The RC1 and RC2 for me are usually OK for a day or so, but the more time goes by and the more frequent the random freeze and reboot.
Back on M3 and that's OK.
Click to expand...
Click to collapse
So M3 is stable enough to use? I couldn't remember whether it was M2 or M3.
Yes M2 and M3 are stable enough for daily use. Actually any nightly from that time is good too. It wasn't until after M3 that things took a dive, and didn't get any better with RC1 and 2.
Only problem I'm aware of is a bug with the Bluetooth on off toggle that affects some. If it happens reboot or force close Bluetooth share.
Related
No matter what I do and however many times I flash cm7, I seem to have erratic touchscreen behavior.
The nook is BRAND NEW (two days) and I flashed it with cm7 7.0.2 stable (after phiremod's 6.0 & 6.1) and flashed it about four times now.
I have tried it with the OC and without.
It's not the SD - it doesn't matter if it's in or not.
Not the wifi, since I didn't even set it up the third and fourth time - it was too erratic to even try.
Plugged in or not... still the same problem. Doesn't seem similar to the other forums topics about touchscreen issues WHILE charging.
Screen is near spotless... no smudges.
It is important to note, that it waits until I have done a few things to start going crazy. I restart it and it's fine, until I do some cpu intensive stuff - live wallpaper is the simplest activity that causes it.
Any ideas?
I have also tried NSR (screen re calibrator) to no avail.
Would love a quick fix rather than re-installing stock and returning it and convincing them to replace it. I am not sure if it does it with stock... didn't wait long enough to find out before flashing it.
have you tried a screen protector? my screen wasnt the best for precise touches but since i put a screen protector on and clean the screen regularly it has since changed my problems to almost non existant.
Sent from my NookColor using Tapatalk
Others may be able to help you more than I can with exactly when the CM7 may be doing this, but returning to stock to find out is actually not hard at all.
In the development thread there is a post that has the 1.2 stock zips (one keeps CW in place, the other returns it completely to stock). Which ever one you pick it's still just as easy to return to stock as to reflash CM7 again. This is especially true if you used a SD card with CW to flash (which is what I do), since when you want to go back to CM7 you won't have to worry about flashing CW to emmc again.
angelic.pariah said:
No matter what I do and however many times I flash cm7, I seem to have erratic touchscreen behavior.
The nook is BRAND NEW (two days) and I flashed it with cm7 7.0.2 stable (after phiremod's 6.0 & 6.1) and flashed it about four times now.
I have tried it with the OC and without.
It's not the SD - it doesn't matter if it's in or not.
Not the wifi, since I didn't even set it up the third and fourth time - it was too erratic to even try.
Plugged in or not... still the same problem. Doesn't seem similar to the other forums topics about touchscreen issues WHILE charging.
Screen is near spotless... no smudges.
It is important to note, that it waits until I have done a few things to start going crazy. I restart it and it's fine, until I do some cpu intensive stuff - live wallpaper is the simplest activity that causes it.
Any ideas?
I have also tried NSR (screen re calibrator) to no avail.
Would love a quick fix rather than re-installing stock and returning it and convincing them to replace it. I am not sure if it does it with stock... didn't wait long enough to find out before flashing it.
Click to expand...
Click to collapse
Hate to say it but it sounds like it might turn out to be a hardware issue. This is not a CM7 issues that I've seen from anybody.
Can you describe the behavior in more detail?
dalingrin said:
Hate to say it but it sounds like it might turn out to be a hardware issue. This is not a CM7 issues that I've seen from anybody.
Can you describe the behavior in more detail?
Click to expand...
Click to collapse
It seems to start selecting things on its own after I have been using it for a while. It's difficult to describe except that there isn't really a pattern... it selects something different and keeps at it. At one point I almost purchased an app from the market before I had to power down.
I will return it to 1.2 stock and report back. I was mainly wanting to know if these was a commonly reported issue or not. I guess it's not. Thanks for the help everyone!
angelic.pariah said:
It seems to start selecting things on its own after I have been using it for a while. It's difficult to describe except that there isn't really a pattern... it selects something different and keeps at it.
Click to expand...
Click to collapse
So my NC started to do the same thing last night. I have been running CM7 (at 7.0.2 now, but nightlies before then with dal's OC kernal) for quite a while now with no problems. Only thing I did last night was to delete about 1GB of ebooks off of my NC and reload them through Calibre.
I left it alone last night after it started doing it and then this morning it started doing crazy touches again. I was in Aldiko and it was selecting books and turning pages at random. Rebooted and it seems to be fine for now. Little odd though considering it has been running perfect for a few months.
bucketheadmn said:
So my NC started to do the same thing last night. I have been running CM7 (at 7.0.2 now, but nightlies before then with dal's OC kernal) for quite a while now with no problems. Only thing I did last night was to delete about 1GB of ebooks off of my NC and reload them through Calibre.
I left it alone last night after it started doing it and then this morning it started doing crazy touches again. I was in Aldiko and it was selecting books and turning pages at random. Rebooted and it seems to be fine for now. Little odd though considering it has been running perfect for a few months.
Click to expand...
Click to collapse
So now I have installed nook stock 1.2 and NO PROBLEMS. I have run everything trying to get something to happen, and nothing.
Is it possible that I installed something the wrong way with cm7? Could I have used the wrong CWM version (3.0.0.6)?
Should I try cm7 7.0.2 or something else again?
I would try and return it, but I can't recreate the problem... if I could, I would be in their face right now.
Thanks for the help so far.
I think I solved it!
The newest nooks (in the last week or so) have 1.1.0 factory stock. Apparently there is a glitch that has been reported a lot recently about handling the touchscreen AND the SD card. These were fixed in the 1.2 upgrade. SO...
1. I flashed factory stock back on (in this case I went back to 1.0.1)
2. Then turned it off and "restored factory" settings using "Power+N" to turn it on. Repeated that a second time to get B&N's factory reset screen to come up.
3. Pressed N twice to accept restore prompts.
4. Upgraded to 1.2 (no glitches already by this point with touch or SD)
5. Booted CWM 3.0.0.6+
6. Formatted /system & /data
7. Flashed phiremod 6.1
8. OC'd to 1.1Ghz
...and DONE. No problems so far. I still see the "Read Forever" opening screen, but it still works wonders. WAY better than before.
I am still having issues with Wifi, but I can deal with that.
Now to attempt dalingrin's OC to 1.3!
Thanks guys... hope this helps others.
I think they call it "Touchscreen goshting". It started happening to me when I rooted the nook and the keyboard would go crazy. Now in CM7 7.0.2 with latest kernel, it happens more frequently. About 5 minutes in from boot, fast random touches occur. Most of the times this gets fixed by pressing the power button to turn the screen off (sleep), and on again. I guess it could be a hardware issue where some devices are affected. I haven't tried any recalibration apps to try to fix it yet, its kind of annoying when it happens in fast intervals.
I had weird touchscreen issues when using the interactive cpu governor. I later found only performance is supported. Using performance setting, everything works much better.
queseyo said:
I think they call it "Touchscreen goshting". It started happening to me when I rooted the nook and the keyboard would go crazy. Now in CM7 7.0.2 with latest kernel, it happens more frequently. About 5 minutes in from boot, fast random touches occur. Most of the times this gets fixed by pressing the power button to turn the screen off (sleep), and on again. I guess it could be a hardware issue where some devices are affected. I haven't tried any recalibration apps to try to fix it yet, its kind of annoying when it happens in fast intervals.
Click to expand...
Click to collapse
I had the same issue. I exchanged it the other night and now my new one does not have the problem. It probably a hardware issue...i hope you are still under warranty!
Curious about experiences. Right now I'm on the M3 Experimental.
It's really stable.. By far the most stable cm10.1 build I've ever used. Only thing Is the instagram videos come out fuzzed out and you can't see anything. That Sux
Sent from my SAMSUNG-SGH-T879 using xda app-developers app
Only one bluescreen in 24 hours so far. Using its boot image in the newest Slimbean, hope it continues to hold up.
I was just coming to post this exact same question. I had to go back to M3 because there were too many bugs in the subsequent nightlies.
But I think i'll try RC-5 and see what it's about.
I did flash it. Since that time I've had some issued with bluetooth where I've had to reboot the phone to get it to work. Also some "blue screen" and random reboots. Someone suggested I should probably reflash and clear everything (data, cashe, dalvik etc...)
jdekoven said:
I did flash it. Since that time I've had some issued with bluetooth where I've had to reboot the phone to get it to work. Also some "blue screen" and random reboots. Someone suggested I should probably reflash and clear everything (data, cashe, dalvik etc...)
Click to expand...
Click to collapse
The bluetooth issue seems inherent in any of the 4.2.2 roms. I've done clean installs , wiped with Darkside, etc. It doesn't really seem to matter.
I noticed today there was a new release on 6.24.13 under "stable" cm-10.1.0-quincytmo.zip . Could someone explain to me the difference between this and the "release candidate" cm-10.1.0-RC5-quincytmo.zip which was released on 6.16.13? It would seem the former would be the more updated because of the later release date? I already have the RC5 flashed on running. Some issues here and there so just curious.
Thanks,
John
Installed 10.1.0 using the updater and had lots of problems. Audio bad, Bluetooth not working. Installed clean with a factory reset and it is very stable. Only issue is still some camera apps (Google drive scan, latest evernote) require setting Disable HW Overlays. But other than that, seems good
jdekoven said:
I noticed today there was a new release on 6.24.13 under "stable" cm-10.1.0-quincytmo.zip . Could someone explain to me the difference between this and the "release candidate" cm-10.1.0-RC5-quincytmo.zip which was released on 6.16.13? It would seem the former would be the more updated because of the later release date? I already have the RC5 flashed on running. Some issues here and there so just curious.
Thanks,
John
Click to expand...
Click to collapse
Lots of random reboots followed by a blue screen, I have noticed that it happens a lot during or after viewing a video and certain games, it even has happened while texting. No where near stable, battery life is horrible and like I said the reboots are random but often.
I'm using the CM 10.1 stable release as the boot image for PAC-Man rom. So far, no blue screens, reboots or anything. I've messed around with it, adding the Google edition camera and other goodies I found in i717 forum. Flashed in the S-4 launcher and everything is still holding together. Battery life is okay, considering I'm using livewall paper and wifi also. 60% remaining after four hours.
I'll give it a few days to settle in.
10.1.0 (4.2.2), good so far
jdekoven said:
I noticed today there was a new release on 6.24.13 under "stable" cm-10.1.0-quincytmo.zip . Could someone explain to me the difference between this and the "release candidate" cm-10.1.0-RC5-quincytmo.zip which was released on 6.16.13? It would seem the former would be the more updated because of the later release date? I already have the RC5 flashed on running. Some issues here and there so just curious.
Thanks,
John
Click to expand...
Click to collapse
I've been running the 'stable' version for a couple days and only one b.s.o.d. Runs smooth and battery is about the same at RC5. Camera is good as well. Don't use Blu-tooth so can't testify for that. I reboot every morning and that seems to make a world of difference.
Wish stock JB would come to us.
Anyone know how to get stock screen resolution back?
20130804-Nightly stable
Hey all, just thought that since I complained about how buggy the nigthlies were, I should come back and say that I am now on the 20130804 and it is very stable. I have been using it since Monday and i've only have one reboot. I initially had some screen flickering when I had a solid green background (from an MIUI theme), but I switched to another wallpaper and don't have that problem anymore.
Just FYI.
Hi everyone!
I have a strange problem with my Droid 4: sometimes it stops playing sounds (or music, or ringtones), and I can't figure out if there's something in particular that triggers this. Anyway the only fix I could find is rebooting the phone.
There's another problem though: when this happens, if I try to use the phone app or the contacts app, the app itself hangs before I can do anything. If I kill the hanged app and retry a few times, the phone reboots itself.
Any idea on what could be causing this? What could I try to diagnose the problem?
I'm using a Verizon-branded Droid 4 with CM10.1.3, but I had the problem on 10.1.2 too. If it's relevant, I had to install "Tobby's mod" to enable GSM (I'm in Europe)
Many thanks for your attention!
This is the only and the known problem with droid4 on cm10.1 cm10.2 but I have a very good experience with the latest nightlies using buildprop editor to change only the telephony.lteOnCdmaDevice=0. Don't use the patch and se if it helps for you.
Sent from my XT894 using xda app-developers app
I have that property "zeroed" already, do you mean I should try reverting Tobby's mod?
Try the latest nightlies, there are some changes regarding to apns, it's updatable from cm10.1 and make only that change don't apply any patch.
Sent from my XT894 using xda app-developers app
Joril said:
Hi everyone!
I have a strange problem with my Droid 4: sometimes it stops playing sounds (or music, or ringtones), and I can't figure out if there's something in particular that triggers this. Anyway the only fix I could find is rebooting the phone.
There's another problem though: when this happens, if I try to use the phone app or the contacts app, the app itself hangs before I can do anything. If I kill the hanged app and retry a few times, the phone reboots itself.
Any idea on what could be causing this? What could I try to diagnose the problem?
I'm using a Verizon-branded Droid 4 with CM10.1.3, but I had the problem on 10.1.2 too. If it's relevant, I had to install "Tobby's mod" to enable GSM (I'm in Europe)
Many thanks for your attention!
Click to expand...
Click to collapse
I've seen this on stock, and I think it's related to bluetooth - perhaps it's not releasing the audio properly after a device disconnects?
There's an app in the Play Store called "Earpiece", and I can use that to bring the audio back when that happens by switching it on, and then switching it off again.
HTH.
Steve.
I don't use bluetooth at all, but I'll try Earpiece, thanks
the problem is that it will crash before you realize and you will loose the next call, so I don't think it is of some use.
I tried latest nightly and safestrap 3.65 (from 3.63) and I had lots of black screens, several on one day and then I realize that before, I had it working stable on cm10.1 when I found out that noop was the problem, cfq and deadline was ok (after speaking with hashcode it made the default to cfq) but it was on safestrap 3.11, but then newer versions of safestrap appeared and I updated it and from time to time it started to go bad again.
I reverted back to 3.11 and I have it working ok since 17.11.2013 (almost 2 days of stable, finger crossed)
I would ask hascode if safestrap can be a problem, but now he has retired in supporting the d4, of course this can be applied to razr
Regards
lucize said:
I reverted back to 3.11 and I have it working ok since 17.11.2013 (almost 2 days of stable, finger crossed)
Click to expand...
Click to collapse
How is it going?
For me is very good, tried 4.4, now back on cm10.2 nightlies, so
Ss3.11 and only the lteoncdma change, everything else is working fine except tha battery that is shorter than moto default
Regards.
Sent from my XT894 using xda app-developers app
lucize said:
For me is very good, tried 4.4, now back on cm10.2 nightlies, so
Ss3.11 and only the lteoncdma change, everything else is working fine except tha battery that is shorter than moto default
Click to expand...
Click to collapse
Ok, now I'm on a 10.2 nightly, with just the lteoncdma fix... Let's see how it goes
It took a while to connect to the GSM network, did this happen to you too? (The signal strength icon even changed to a question mark at one point)
I first have no sim, then no signal then I get full bars
Sent from my XT894 using xda app-developers app
I had it working nicely for 6 full days, but this morning sound went out again Better than before, but still...
I'm on the 28/11 10.2 nightly, I'll try updating again this evening
Joril said:
I had it working nicely for 6 full days, but this morning sound went out again Better than before, but still...
I'm on the 28/11 10.2 nightly, I'll try updating again this evening
Click to expand...
Click to collapse
I'm on kitkat, I think that I had it too with 28, try 27 or other, maybe stable, anyway is better than 1 or 2 days
Regards
Definitely better, yes So you're using CM11? Any problems?
Joril said:
Definitely better, yes So you're using CM11? Any problems?
Click to expand...
Click to collapse
the 05 fromm stargo is not so ok, the previous was stable, or at least I didn't had problems.
I'll try the 07, I have problems with deep sleep and I don't know why, because for now wakelocks can't be accessed on 4.4, then again is not a new install, is an upgrade from 10.2
the strange thing is that now I have another error in catlog when it goes out of sound compared to the error when it is on the gsm patch, maybe I'll try a test without changing build.prop at all, in the end it doesn't matter if the signal icon is wrong as long as it's stable.
Regards
Hey! Joril! I posted in your other thread, on another forum, about this same topic, but I figure that I'd get comfy here, since the Droid 4 "scene" has seemingly migrated from DroidForums to this website.
Anyway, I haven't been able to fix the problem. In fact, at one point, when the audio died, I went through the typical steps - I turned off Bluetooth, and reset the phone. However, when the phone was "coming back", so to speak, an "Android is upgrading" box popped up. Odd, I thought, since I didn't do anything different. Anyway, it gets through this, and... I get an UID error. Something about the UID being inconsistent with the system, and that the data partition was terribly unstable.
So, my phone was freaking out. Great. I was missing several apps, and the whole device is incredibly unstable - apps are crashing, left and right, as well as background services. It is at this point that I decide to bite the bullet and restore my phone to stock settings.
I do so. I use the Droid 4 Utility, restore the stock ROM, getting rid of Safestrap 3.11 in the process. Everything's back to normal. Stabilized. I commence to rooting the phone, installing the latest version of Safestrap, and installing CyanogenMod 10.1.3. I get it running, and... the problems remain. I still have the same audio issues. MMS is still iffy. GPS is a hit-or-miss process; every once in a while, if the planets align, a system reboot will "fix" GPS.
Anyway, that's my story. I've been doing some research - or, rather, a lot of research - and it seems to me that the audio problem was, perhaps, fixed in the latest CyanogenMod 11 build. Something about the previous code not playing well with the "Audio HAL", whatever that is, and the Audio HAL issue being consistent with other phones with the same processor, I believe - or something to do with an "MSM8660". I believe that "MSM8660" is a Snapdragon processor, but I could be wrong!
To make a long story short: CyanogenMod 10.1.3 seems to be stuck with the audio/crashing issue, but CyanogenMod 11 may fix it. I'm not ready to make the jump to CyanogenMod 11, though, not until it is FULLY stabilized and out of Experimental/Alpha/Nightly status. In that regard, I wonder how open Stargo, Hashcode, or another coder would be to patching up 10.1.3 with the GPS/MMS fixes that have been seen in the later builds? I don't know how to code, but it should be relatively simple to patch the few crippling bugs remaining on 10.1.3, using code from future builds and versions.
Jishkah said:
CyanogenMod 10.1.3 seems to be stuck with the audio/crashing issue, but CyanogenMod 11 may fix it. I'm not ready to make the jump to CyanogenMod 11, though, not until it is FULLY stabilized and out of Experimental/Alpha/Nightly status. In that regard, I wonder how open Stargo, Hashcode, or another coder would be to patching up 10.1.3 with the GPS/MMS fixes that have been seen in the later builds?
Click to expand...
Click to collapse
Right now I'm on a CM10.2 nightly and the audio issue appears a bit less than when on 10.1, I'd say once every 5/6 days instead of once every other day... Anyway I'd like to wait a bit more before trying CM11 too
CM11 has this issue also, but the error will not be the same if the build.prop has only lteoncdma modified, for me, if I apply the full gsm patch the error will appear more often and catlog will show the cpu pegged error.
the problem with CM11 (for me) is no deep sleep, the sound issue is not so important anymore
Hallo,
I am sorry, to post it here, but I cannot post in the related forums below 10 posts.
So I had 4.1.5 and it was great. I flashed 4.2.3 now and it was great until after pretty much one day, when it becomes slow, had the same issues with 4.2.2 (becomes slow after a day until reboot or downgrade to 4.1.5) where I downgraded again, but it is not possible anymore without resetting the launcher3 due to some changes.
It will crash repeatedly.
Any help?
Kind regards
neox
I've been using CM based Mackay ROM for a long time now, updating to every new version as they have been released, and have not experienced anything like what you are describing.
Also, you should have really posted in the Mackay ROM thread...
Sent from my GT-I9000 using Tapatalk
@neox456! I am not sure I understand your problem fully. I have been using the same ROM since it came out for Kit Kat but never had a problem such as yours.
Could it be the no. of apps you have in your phone ? Or maybe because you aren't using low mem option (which was a feature of Kit Kat)?
It'd be good if you could explain your issues a bit briefly.
neox456 said:
Hallo,
I am sorry, to post it here, but I cannot post in the related forums below 10 posts.
So I had 4.1.5 and it was great. I flashed 4.2.3 now and it was great until after pretty much one day, when it becomes slow, had the same issues with 4.2.2 (becomes slow after a day until reboot or downgrade to 4.1.5) where I downgraded again, but it is not possible anymore without resetting the launcher3 due to some changes.
It will crash repeatedly.
Any help?
Kind regards
neox
Click to expand...
Click to collapse
Did you install CM10.2 (stable) or CM11 before Mackay 4.2.3? This increases your partition giving you better performance and is recommended for KK roms. Try again with 3 wipes plus Format System first, then the CM11, 3 wipes and format again then the Mackay Rom. If you get into trouble, go back to GB 2.3.6 with ODIN like you did when you first rooted your phone and back up from there. Hope it works for you.
The difference was between 4.1.5 and 4.2.2/3. But I played around a little and the main difference was, that KSM was on with the later ones and not with 4.1.5 so I am pretty sure that slowed my device down after a while.
I'll try 4.2.3 without KSM now and see if it won't slow down.
I cannot answer on the official Mackay-Thread until I reached 10 posts!
neither can I yet...
Naaah, it did not really help...
But I guess it is the KitKat slow downs... it is not as horrible as 4.3, but still far from well usable.
neox456 said:
Naaah, it did not really help...
But I guess it is the KitKat slow downs... it is not as horrible as 4.3, but still far from well usable.
Click to expand...
Click to collapse
Very strange.. I went all the way back to GB 2.3.6 then CM 10.2 (or 11) then SlimKat and it works really well with no FC or lags. (well maybe say max 2 second delay opening Whatsapp but I can live with that. Plus they all seem to have a 1 or 2 second delay when a call comes in for the screen to register.
Well... I am not sure... Maybe it is too many apps. At least they are not constanlty crashing like in JB4.3.
What about waking up the phone for you? Do you have a 2 seconds delay there, too? Well I sometimes have a more like 10-15 seconds delay. I press the power button and nothing happens and after a while you notice the phone is ready, because the LEDs are glowing and funnily you can already unlock it, although the screen does not show anything yet...
Well and sometimes it is only a few seconds...
I have always used CM or Mackay-CM... not sure, whether the other ROM will make such a big difference...
I had lags with CM in ICS so I went to Liquid smooth by aways .
http://forum.xda-developers.com/showthread.php?t=2223729
I like that one, no problems opening apps or answering phone call. Pkus he uses semaphore and the Nova Launcher which has a nice look and feel. Pluis customisable.
Then after to SlimKat, (after increasing partition using the CM11) which works pretty good. I will flash the mackay rom or the omni this weekend to see how it behaves in comparison.
I am down to CM9 (still Mackay) now and happy with it. :angel:
Some features got lost, but I am happy, because in general it is way more useable.
The M10 build of CM11 just came out, I read the blog post and saw the new version in my OTA updates (I flashed CWM to internal so I can do that and have for a few versions). I know it will probably go smoothly, but the horror stories about boot loops, soft bricks, and Android system process crashes that I've read about in the comments make me really nervous. Nobody's yet posted about the HD+/Ovation, but the first 5 CM11 M updates were all bad, even with a complete wipe, so I don't want to take the risk.
I am aware, though, that there are many users here who literally keep their devices for development and ROM testing purposes and don't have (much) personal date to worry about losing. Not so for me. So, I was wondering, could anyone do a CWM backup to SD, perform the OTA upgrade from the settings panel, and write a review/say what happens? Note that I have the most recent gapps installed, so those should be tested because they may cause issues.
Preferably someone with gapps who was going to do an upgrade anyway, so I don't inconvenience anyone by having them upgrade where they otherwise wouldn't.
You hint, but do not really say, that you already have CM11 installed. If so what version?
Many have already tried M10 and said there are issues with media scanner if you dirty install. See the CM11 thread.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
You hint, but do not really say, that you already have CM11 installed. If so what version?
Many have already tried M10 and said there are issues with media scanner if you dirty install. See the CM11 thread.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
M9, and it works perfectly, which is why I'm wary about updating. Also, the media scanner error can apparently be fixed by wiping the app's data/cache in settings and rebooting.
Seanthedroid said:
M9, and it works perfectly, which is why I'm wary about updating. Also, the media scanner error can apparently be fixed by wiping the app's data/cache in settings and rebooting.
Click to expand...
Click to collapse
I installed M10 over M9, and it went very smooth. The usually two reboots, followed by optimising apps, and everything is up and running again. If anything comes up, I will certainly mention it.
Seanthedroid said:
The M10 build of CM11 just came out, I read the blog post and saw the new version in my OTA updates (I flashed CWM to internal so I can do that and have for a few versions). I know it will probably go smoothly, but the horror stories about boot loops, soft bricks, and Android system process crashes that I've read about in the comments make me really nervous. Nobody's yet posted about the HD+/Ovation, but the first 5 CM11 M updates were all bad, even with a complete wipe, so I don't want to take the risk.
I am aware, though, that there are many users here who literally keep their devices for development and ROM testing purposes and don't have (much) personal date to worry about losing. Not so for me. So, I was wondering, could anyone do a CWM backup to SD, perform the OTA upgrade from the settings panel, and write a review/say what happens? Note that I have the most recent gapps installed, so those should be tested because they may cause issues.
Preferably someone with gapps who was going to do an upgrade anyway, so I don't inconvenience anyone by having them upgrade where they otherwise wouldn't.
Click to expand...
Click to collapse
I went from 10.2.1 to cm 11 nightlies just a few weeks ago and was pleased except for a few glitches like screen flashes between apps. When m10 came out I decided to go for what I understood as a generally more stable rom. Unfortunately I did not wipe first as I had upgraded from previous nghtlies without a problem. I had some issues as mentioned in another thread and realized you must wipe before install and I reinstalled. So far so good and I thank titanium for making restoration so easy. I still see screen flashes and a few random crashes but it seems good.
MrPuddington said:
I installed M10 over M9, and it went very smooth. The usually two reboots, followed by optimising apps, and everything is up and running again. If anything comes up, I will certainly mention it.
Click to expand...
Click to collapse
I've just upgraded to m10, it's smooth and stable
But my device is slow, maybe cpu of nook hd+ is weak
Sent from my C6916 using Tapatalk
USRobotics said:
I've just upgraded to m10, it's smooth and stable
But my device is slow, maybe cpu of nook hd+ is weak
Sent from my C6916 using Tapatalk
Click to expand...
Click to collapse
My HD+ also seems quite slow, especially as I load more apps on the 32GB internal card. My 7" HD has no issues with m10 nightlies, and is quite peppy.
danshane said:
My HD+ also seems quite slow, especially as I load more apps on the 32GB internal card. My 7" HD has no issues with m10 nightlies, and is quite peppy.
Click to expand...
Click to collapse
I had noticed an interesting sort of choppiness or hitching after first flashing M10 but it either has gone away or I'm now adjusted to it. It wasn't much to begin with but it was there. Otherwise, that was all.
My nook is ~138 apps during the cache configuration (art) upon first boot as the best number I can give for app load. Surely the more apps and the more background services running on the device the harder it will be for it to keep everything going as fast as possible. If your not on art, that might help (recovery backup first for safety + be aware of art's hunger for more internal storage).
Otherwise, its also possible to "out grow" the device and need something more powerful at the same screen size. If your needs change, the device may need to be changed. (Or similar). Too many apps and you could find yourself there.
sandsofmyst said:
If your not on art, that might help (recovery backup first for safety + be aware of art's hunger for more internal storage).
Otherwise, its also possible to "out grow" the device and need something more powerful at the same screen size. If your needs change, the device may need to be changed. (Or similar). Too many apps and you could find yourself there.
Click to expand...
Click to collapse
I tried ART with no improvement, so i am just going to experiment with a different build. My wife has an identical, fully loaded HD+ that zips right along on CM 10 with Jelly Bean, and my HD has no lag with KitKat, so I am not worried that the hardware will not handle the job. My son has an old Nook Tablet (pre-HD) that is really peppy on CM11 KitKat. I think all the Nook models are great for modding, and I am sure I will get this one performing as I like once I hit on the right combination.
** UPDATE ** I installed the latest Pac-Man ROM and I am now getting the performance I hoped for.
Installed M10. Did full wipe.
Was running a nightly from 03/2014 that was rock solid and fast (using ART).
All I can say to any one thinking of going to M10 is prepare to be disappointed. Its really laggy, even with other launchers, it looks terrible, the refresh rate/redraws/whatever are really obvious. Uncomfortably obvious. The screen sensitivity is really bad. Not responsive at all. I am looking forward to checking out the battery life over the next few days, because I have a sneaking suspicion it will deliver the trifecta of slower speeds, less responsive screen and worse battery life.
Trebuchet seems to be getting worse and worse. I wish Cyanogenmod would do a deal with one of the proper launchers and stop subjecting us to the substandard experience that is Trebuchet.
Oh yeah, and to top it all, the HD+ will no longer turn off. Selecting power off in the power menu just reboots the device. I now have to reboot into recovery and power off from there.
I am really disappointed. After all that effort backing up, wiping and reinstalling everything and actually took several (so many!) steps backwards.
gandalf_grey91 said:
Installed M10. Did full wipe.
Was running a nightly from 03/2014 that was rock solid and fast (using ART).
All I can say to any one thinking of going to M10 is prepare to be disappointed. Its really laggy, even with other launchers, it looks terrible, the refresh rate/redraws/whatever are really obvious. Uncomfortably obvious. The screen sensitivity is really bad. Not responsive at all. I am looking forward to checking out the battery life over the next few days, because I have a sneaking suspicion it will deliver the trifecta of slower speeds, less responsive screen and worse battery life.
Trebuchet seems to be getting worse and worse. I wish Cyanogenmod would do a deal with one of the proper launchers and stop subjecting us to the substandard experience that is Trebuchet.
Oh yeah, and to top it all, the HD+ will no longer turn off. Selecting power off in the power menu just reboots the device. I now have to reboot into recovery and power off from there.
...
Click to expand...
Click to collapse
I upgraded to M10 from M9 and so far had none of the issues you described. The only and somewhat minor problem is ~25% of Playstore app updates would abort on first try.
FWIW I use the Nova launcher and love it.
digixmax said:
I upgraded to M10 from M9 and so far had none of the issues you described. The only and somewhat minor problem is ~25% of Playstore app updates would abort on first try.
FWIW I use the Nova launcher and love it.
Click to expand...
Click to collapse
I can only report the facts, I was expecting a different experience from M10. Generally, I also choose to use Nova but on M10 it is suddenly jerky, jagged and uncomfortably laggy.
I believe the Play store issue is a google issue, which seems to come and go as they update Play store app. For me, it started in March of this year, was fixed later on and then came back a couple of months later, only to disappear a few weeks later..
Update: the Power Off = Reboot issue cleared up after 3 reboots/power offs. Its now working properly.