M10 snapshot is out. Time to flash 
https://download.cyanogenmod.org/get/jenkins/83780/cm-11-20140916-SNAPSHOT-M10-ovation.zip
https://download.cyanogenmod.org/get/jenkins/83780/cm-11-20140916-SNAPSHOT-M10-ovation.zip
M10 snapshot is out. Time to flash
https://download.cyanogenmod.org/get/jenkins/83780/cm-11-20140916-SNAPSHOT-M10-ovation.zip
I flashed my Nook HD+ with M10 today - from the 831 nightly.
It does feel faster.
I did get this error which pops up continuously:
"Unfortunately, the process android.process.media has stopped"
I did not Factory Reset but did format Cache and Davilak Cache.
Hmmm. Still get "Unfortunately, the process android.process.media has stopped"
I wonder if I have an errant app that does not work well with M10.
Is there a log file with more information?
This fixed that error:
Go to Settings - Apps - Media Storage - Force Close.
If Enabled, then Disable
Yes, that does stop the media scanner, but from then on your MTP connection probably will not not work right.
Sent from my BN NookHD+ using XDA Premium HD app
Using 2014-09-10 nightly w/ Dalvik
I was dealing with some performance issues, and I thought they were related to trim/storage. So I removed a few gigs and manually trimmed, but to no avail. In looking for a fix for one of my friends' phone, I stumbled upon suggestions on how to tweak performance. For CM11, do the following:
1) Enable Developer options
2) Go to the "Drawing" subheading
3) For each of the following, change the value to 0.0x
a) Window animation scale
b) Transition animation scale
c) Animator during scale
4) Reboot
This is the performance I was loving when I first rooted my NOOK. Even some apps that would lock up or f/c before now work smoothly.
Dev's, is there anything that would explain this?
Thank you.
I was dealing with some performance issues, and I thought they were related to trim/storage. So I removed a few gigs and manually trimmed, but to no avail. In looking for a fix for one of my friends' phone, I stumbled upon suggestions on how to tweak performance. For CM11, do the following:
1) Enable Developer options
2) Go to the "Drawing" subheading
3) For each of the following, change the value to 0.0x
a) Window animation scale
b) Transition animation scale
c) Animator during scale
4) Reboot
This is the performance I was loving when I first rooted my NOOK. Even some apps that would lock up or f/c before now work smoothly.
Dev's, is there anything that would explain this?
Thank you.
Revisited this error: "Unfortunately, the process android.process.media has stopped"
and instead of Disabling Media Storage, I cleared its data.
Now it works without the error and Media Storage will run.
Go to Settings - Apps - Media Storage
Clear Data
I am getting a message "android process acore has stopped" I tried Go to Settings - Apps - Media Storage - Force Close.
If Enabled, then Disable but that didn't help....
---------- Post added at 09:03 PM ---------- Previous post was at 09:02 PM ----------
I also tried clearing data as well..
I might edit and add that I was working on nightly 9-08 without any problems with it....
If Enabled, then Disable but that didn't help....
---------- Post added at 09:03 PM ---------- Previous post was at 09:02 PM ----------
I also tried clearing data as well..
I might edit and add that I was working on nightly 9-08 without any problems with it....
Last edited:
Going from a September nightly to M10 requires a full wipe: see the official CM explanation -
http://www.cyanogenmod.org/blog/cm-11-m4-post-release-items
Thanks for the heads up.
Because it states ...
M 11 M# releases are a code path that lags behind nightlies.
This means a few things:
Nightlies have newer code than the M-releases
You should be extra careful flashing an M build on top of a new nightly due to #1
... I think I am going to stay on the "bleeding edge" with the nightlies
Carl
Thanks rhyang for the heads-up!! Just goes to show how little I know about this "stuff"... If it wasn't for Chrome force closing with the nightly, I would not have even tried M10. For now I have gone back to 09-08 nightly, but may have to try the full wipe and give M10 a shot.
D
Deleted member 2092952
Guest
At least its possible to know. Even going from M build to M build seems to need a re-flashing of gapps every time. So it is what it is.
I just recently ran through a build of this (9/17. My second successful android build.. Replicant JB was the first). I added linaro neon compiler optimizations in the boardconfig and a couple of other video codecs...
Anyway, I'm impressed with how well and smooth it runs. It's been about eight months since I last tried KK, and things have improved greatly. The kernel works great. Whoever fixed the touchscreen is a pro.
The only issue I've found so far is that ringtone selection force closes (I use the alarm). Anyone else seeing this with recent builds and/or know how to fix it?
Is there something I could revert?
Anyway, I'm impressed with how well and smooth it runs. It's been about eight months since I last tried KK, and things have improved greatly. The kernel works great. Whoever fixed the touchscreen is a pro.
The only issue I've found so far is that ringtone selection force closes (I use the alarm). Anyone else seeing this with recent builds and/or know how to fix it?
Is there something I could revert?
I had a bit of an issue with my M10 this morning. My nook froze a couple times but when I first opened the nook I had 20% battery. After my second reboot it said 8%.
With a recharge the problem seemed to disappear.
Could a misread of charge still be present?
I'm not presently running KK, so take this for what it's worth, but I seem to recall that the touch screen on our tabs get really *touchy* with a low battery.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
138I see there's this new CM11 going, and thanks to @Hashcode who solved most of the complex problems already, here's my first stab at CM11 on our Nook HDs that installs into internal memory (EMMC).
The install is a lot similar to how it was done in CM10.2 days, but you will need a new recovery image (and a new sdcard image for those doing initial install):
So, For Nook HD+: Initial ovation sdcard image (cwm) | ovation recovery image (CWM)
For Nook HD: hummingbird Initial sdcard image | hummingbird recovery image (CWM)
I did some light testing and things seems to be working for whatever light loads I came up with, but still there are probably tons of problems that I have not yet noticed. Please write in the comments about what's broken and I'll try to fix it. Once it's good enough, I'll try to get official nightlies going for CM11 as well, I guess.
Latest CM11 EMMC images are now available as CM11 nightlies at:
For Nook HD+ get ovation builds
For Nook HD get hummingbird builds
There also might be experimental builds available referenced below in the history section.
(Also for completeness, For Nook HD+ sdcard image cm-11-20141129-UNOFFICIAL-ovation-sdcard.zip, | initial sdcard image for ovation )
For new Installs:
- Download the initial sdcard image
- ungzip and write to sdcard using dd (winimage or whatever for those stuck on Windows)
- Instert the card into your nook and reboot
- Flash the recovery image
- Flash cm11 image
- Flash whatever other extra things you need like gapps
- remove the sdcard
- reboot the nook
For upgrades from CM10.x (the only tested are 10.2 and 10.1). If you have any problems after upgrade - you'll need to do factory reset to clear /data:
- Download recovery zip and CM11 install and place it on the nook
- Reboot into recovery you already have installed
- Flash the recovery zip you just downloaded
- reboot into recovery again (This is important! Failure to do this will botch your upgrade and you'll need to wipe /data) so that the new recovery is started.
- Install CM11, install other stuff you need like gapps
- reboot
- enjoy
Useful apps:
Known problems:
- attempting to reformat external sdcard from android crashes volume manager - seems to be upstream problem of some sort. The sdcard is left in some strange state, so don't do it. (if you did, reformat the sdcard on your PC, all data will be lost either way)
Changelog:
2014/11/297 - Bring sdcard build to current source version:
* cm-11-20141129-UNOFFICIAL-ovation-sdcard.zip
2014/08/17 - Bring sdcard build to current source version:
* cm-11-20140817-UNOFFICIAL-ovation-sdcard.zip
2014/01/18 - Fixed 1080p movie playback on Nook HD+:
* cm-11-20140118-UNOFFICIAL-ovation-emmc.zip
* cm-11-20140118-UNOFFICIAL-ovation-sdcard.zip
2014/01/17 - Fixed headset mic issue
* cm-11-20140117-UNOFFICIAL-ovation-emmc.zip
* cm-11-20140117-UNOFFICIAL-hummingbird-emmc.zip
* cm-11-20140117-UNOFFICIAL-ovation-sdcard.zip
2014/01/15 - Switched to TI wpa supplicant, should fix a bunch of wifi-related issues
* cm-11-20140115-UNOFFICIAL-ovation-emmc.zip
* cm-11-20140115-UNOFFICIAL-hummingbird-emmc.zip
* cm-11-20140115-UNOFFICIAL-ovation-sdcard.zip
2014/01/09 - Fixed inability to write to sdcards.
* cm-11-20140110-UNOFFICIAL-ovation-emmc.zip
* cm-11-20140110-UNOFFICIAL-hummingbird-emmc.zip
* cm-11-20140110-UNOFFICIAL-ovation-sdcard.zip
2014/01/08 - Misc updates: autodetect sdcard format, not just vfat. fuzzy touch patch courtesy of D Marble, bt-pan services that reportedly fix bt tethering for some people.
* cm-11-20140109-UNOFFICIAL-ovation-emmc.zip
* cm-11-20140109-UNOFFICIAL-hummingbird-emmc.zip
2014/01/06 - Initial release
* cm-11-20140106-UNOFFICIAL-ovation-emmc.zip
* cm-11-20140106-UNOFFICIAL-hummingbird-emmc.zip
* cm-11-20140106-UNOFFICIAL-ovation-sdcard.zip22Nightlies are/will be back
My patch finally got merged. Nightly builds for ovation and hummingbird should start again.
Apparently I was just too polite in my efforts to get it merged. Next time we have an important merge I will make more noise to those who can merge it. I think we finally got noiced because our broken builds were preventing translations from getting through.
Anyway. We should be back to our normal nightly selves tomorrow unless someone triggers a build sooner.16It seems the initial release was surprisingly good from the get go. Here's a new one with some loose ends tied:
Enabled sdcard/usbcard filesystem autodetect, so now ntfs and ext4 should work too.
Fuzzy touch patch from D Marble
bt-pan services that reportedly fix bt tethering for some people
* cm-11-20140109-UNOFFICIAL-ovation-emmc.zip
* cm-11-20140109-UNOFFICIAL-hummingbird-emmc.zip15StatusBar brightness on HD+
To those folks who asked why status bar brightness control wasn't present I would like to say "Thank You!".
This was a bug in cyanogenmod. Nobody had noticed it. It was left over from cm-9 and cm-10.0 days when tablets didn't have status bars. Now, they do. I submitted a patch to cm to fix this and it was accepted today. From now on, all tablets will have the option to control brightness from the status bar. It was just an oversight that it hadn't been enabled before when tablets got the status bar forced down their throats with cm-10.1. All tablets will now have this option.
It may not be in tonights nightly but it will be in there afterwards.
