yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] twiztid_:
Have you installed any CM or other builds before, or are you on stock?

If you have, just install Flashify from the Play store, flash amaces TWRP 2.8.6.0 then reboot into recovery.

From there, use TWRP to wipe (or choose system, data, cache, and dalvik cache) and then install whatever build you want, CM10, 11,12, 12.1, they all install the same way.

If there any special steps needed, they will be provided in the post with the download typically.
[Nook HD, HD+ Android Development] agantai:
guys i need help,i'm getting 2 errors & i have tried hard to find solution for them but no success:

when i reboot my nook hd 7 i get this error (Unfortunately the process com.android.phone has stopped) ?

also why some of my apk apps fail to install ?

i'm using the latest rom cm-12.1-20150404-UNOFFICIAL-hummingbird
[Nook HD, HD+ Android Development] king200:
"guys i need help,i'm getting 2 errors & i have tried hard to find solution for them but no success:

when i reboot my nook hd 7 i get this error (Unfortunately the process com.android.phone has stopped) ?

also why some of my apk apps fail to install ?

i'm using the latest rom cm-12.1-20150404-UNOFFICIAL-hummingbird"

======================================================

1) Try running without the MicroSD card.

If that doesn't work

2)Do a Nandroid backup and complete wipe, System, Data, Cache, and Dalvik. If you are running a later version of TWRP, go into the advanced wipe and repair the system partition. Install just the rom and see what happens. If that doesn't work, there may be something wrong with the emmc and you can try an SD only install.
[Nook HD, HD+ Android Development] MossyTC:
[MENTION=5237123]agantai[/MENTION]

Change the Preferred install location setting from Let the system decide to Internal device storage.

See this post for details.
[Nook HD, HD+ Android Development] agantai:
thank you soooo much this has fixed the apk install issue i was having,now i need to find out how to stop this error (Unfortunately the process com.android.phone has stopped) from happening every time i reboot the tablet.
[Nook HD, HD+ Android Development] bhuffman:
WPA2 Hidden not working

I'm running amaces latest 04-04 unofficial (clean wipe) and am still seeing problems with using WPA2 with a hidden SSID. It can not connect at all. It saves the network, tries to authenticate and then just bombs and goes back to saying "saved"

Anyone else seeing this?

Thanks,

Brian
[Nook HD, HD+ Android Development] Korgy:
Go to settings, apps, Mobile data and clear data and cache. Reboot and see if it helped.

If not: Boot into recovery, delete the cache and the dalvik cache. Reboot.
[Nook HD, HD+ Android Development] agantai:
i can't find mobile data in apps on my nook hd 7" tablet & i have already gone to recovery & wiped cache & dalvik cache.
[Nook HD, HD+ Android Development] Korgy:
Does the message only pop up after a reboot?

You could try to reinstall the ROM you currently are on or install the previous released update found here.

https://notredame.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww
[Nook HD, HD+ Android Development] agantai:
yes it only happens once after i reboot the tablet,i even used root explorer & deleted the phone apk from my tablet (phone apk on a tablet !!) but error still the same. if i installed the new rom over the older one which was released on the 4th of april will it delete all the apps i have installed ? also what was changed or fixed in todays release ?
[Nook HD, HD+ Android Development] king200:
If you don't wipe data, you will not lose apps or settings.

The phone app is frequently tied to the contacts app.
[Nook HD, HD+ Android Development] Korgy:
Yeah there may be an app or two that will use the phone app and if it's not there it will give you that error. I recommend trying the reinstall. If you are really worried about it you can always make a backup of everything in your recovery before the install. It will keep all your apps and data so there isn't much to worry about.

Do you have a backup of your tablet that is prior to installing the rom you have now?
[Nook HD, HD+ Android Development] agantai:
the error was happening before i deleted the phone apk so i don't see how installing will fix the error but i will backup all of my apps now & install the new rom which will put the phone apk back on the tablet,no i don't have backup of my nook's stock os but i have downloaded the stock os from a thread on this forum last year.
[Nook HD, HD+ Android Development] agantai:
i have installed cm-12.1-20150408-UNOFFICIAL-hummingbird & the phone error seems to have gone now. :)
[Nook HD, HD+ Android Development] belfastraven:
Also, with the 4/08 hummingbird, the "soounds" settings is working again .

thanks again, amaces.
[Nook HD, HD+ Android Development] Korgy:
Awesome! Glad it worked.

I'd recommend making a backup of your tablet now since you know this is a good working state that you can come back to if needed.
[Nook HD, HD+ Android Development] agantai:
i will do full backup next ,i'm currently installing my apps manually because titanium backup did not backup the data,only apk's were copied so i have to do lots of copy/paste & download all my purchased app's from google play.
[Nook HD, HD+ Android Development] amaces:
Yup, this has been merged a few days ago. Turns out that lack of telephony was causing problems again.

Haven't stumbled upon anything related to this. It is pretty odd, since it was working at some point, and it can't affect only us. I would've expected bugs reported with many other devices; then again, very few people are using this feature compared to just a couple of years ago. Random idea, is the filesystem VFAT, exFAT, or something else?

This one might be due to our device configs, and the changes done for LP bringup, so related to screen casting, and voice recording. It might take a (long) while before it gets sorted out, given the other major issues people are struggling to fix :(
[Nook HD, HD+ Android Development] Dread This Day:
The filesystem is fat32. In tinkering, I think it's a major glitch. It's like the code pointing to where the external SD is, is wrong. When I select move to SD for an app, it tells me immediately there is insufficient space to do so. Now, even if the code was pointing at the emulated SD storage on the internal storage, it should move (I have the space), but it doesn't. If I set apps to install to external SD, nothing will install at all. If I try to move to SD using Link2SD, I get an error. It's perplexing and frustrating. I really wish I had gotten the bigger internal memory. Lol. Folder mount helps, but not as much as I need it to. Trying to play games such as Grand Theft Auto, and I need more free internal space.
[Nook HD, HD+ Android Development] agantai:
i like to share some good news about the latest build 08/04/2015 the apps which did not work for me on the previous builds are working fine on todays build :good: looks like the guy who made the latest build is also using it. :p
[Nook HD, HD+ Android Development] belfastraven:
I''ve run across a couple of sites (don't remember where right now) that seem to claim that you could move apps to external card if at least part of it was formatted ext4.

Perhaps you could search for the info? They seem to claim that the fat32 partition would be seen by your computer and that the apps would get moved to the ext4 partition. I haven't tried this, but thought you might want to.
[Nook HD, HD+ Android Development] Dread This Day:
I've seen it as well. I didn't want to go through the trouble but it looks like it may be my only option.
[Nook HD, HD+ Android Development] norm883:
Nook HD+ 04/08/15 ROM

Have installed the above ROM on Ovation only problem I seem to have is unable to turn off device except on power off in twrp?

Any patch or simple solution?

thanks,

norm883
[Nook HD, HD+ Android Development] Dread This Day:
Hold the power button, the menu that pops will give you the option to "Power Off". But it won't work, there's no patch or simple solution. Just how our devices work with CyanogenMod.
[Nook HD, HD+ Android Development] Korgy:
Interesting that telephony would be attached to the volume settings like that. Glad to see you find the root cause of the problem!

---------- Post added at 02:02 AM ---------- Previous post was at 01:12 AM ----------

Interesting. Does the power menu come up at all when holding the power button? If so, nothing happens when you select power off?

An easy fix for now would be to just add a shortcut to your home screen that links to the power off command in TWRP since you said that was still a working method.

Another option is to download an app like Power Toggles.
[Nook HD, HD+ Android Development] twiztid_:
The power button shuts down the nook, but a few seconds after what looks like it finishes shutting down, it turns back on. Even TWRP's Power Off ends up with the nook restarting.
[Nook HD, HD+ Android Development] wahidx:
Hi, where can i find the 04/08/15 build, I only see the 02/17/15 build on the first page :/

sorry if the question is to dumb :silly:
[Nook HD, HD+ Android Development] Korgy:
Here ya go.

https://notredame.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww

FYI these are uploaded by amaces
[Nook HD, HD+ Android Development] wahidx:
THX mate and thx to amaces.:good::good::good:

btw. is there big differences between hummingbird and ovation build or is that more a matter of taste?
[Nook HD, HD+ Android Development] tebra:
hummingbird build is for Nook HD

ovation build is for Nook HD+
[Nook HD, HD+ Android Development] norm883:
Nook HD+ (Ovation)

It appears that this ROM is a spin off from the original

https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778

norm883

---------- Post added at 01:49 PM ---------- Previous post was at 01:45 PM ----------

Yes the power menu does come up and works fine with reboot, recovery etc but in power off it appears to turn off then goes into reboot.

norm883
[Nook HD, HD+ Android Development] keshabbhattarai126:
[MENTION=4473900]amaces[/MENTION] is doing great job. I was not expecting to see next build within a week. Flashed yesterday's build and most of the problem seems to be fixed except one or two of the minor problems. Performance has boosted by 2000 score in antutu benchmark.

[IMG="Antutu benchmark score"]https://lh3.googleusercontent.com/-O7nrQcJNo_Y/VSaWRh8XR2I/AAAAAAAAAW8/GGhNc1pUcEM/w426-h682/Screenshot_2015-04-09-20-49-49.png[/IMG]
[Nook HD, HD+ Android Development] ST Dog:
You don't happen to have it plugged in for charging do you?

That will cause the Nook HD/+ to turn back on and boot as you describe.
[Nook HD, HD+ Android Development] Dread This Day:
Even not plugged in, it reboots when "Power Off" is selected.
[Nook HD, HD+ Android Development] ST Dog:
It was a thought :(

Many people don't realize that the device powers on and boots when connected/charging.
[Nook HD, HD+ Android Development] Dread This Day:
It was worth mentioning for sure. I tested it a few times, and even when not plugged in it reboots. Not an issue for me, but a few people prefer to be able to turn it off. I don't ever see that even getting looked into, though.
[Nook HD, HD+ Android Development] tebra:
Same problem here on 20150408 build. My Nook HD restart 5 to 10 seconds after shutdown.
[Nook HD, HD+ Android Development] twiztid_:
Its an issue with CM in general, not any specific build. Its happened with all versions I can recall using. I can give 4.3 a shot later and update, but I think the outcome is the same.
[Nook HD, HD+ Android Development] Dread This Day:
Most people don't even consider it a glitch, which is why it still persists. I dare to say that most people don't bother turning their tablets off.
[Nook HD, HD+ Android Development] twiztid_:
I'd like the option to turn it off... But I would use the "feature" so little, it not working probably isn't even in my 'top 100 things I would change/customize'.
[Nook HD, HD+ Android Development] MossyTC:
[MENTION=4473900]amaces[/MENTION] - Can you post a changelog with each release please?

Also your boot images have disappeared from the download site - is this by accident?
[Nook HD, HD+ Android Development] aoleary:
Hi amaces.

I in my humble opinion, it would be a good idea to create your own thread so and reference this one in yours, to give credit to hashcode for the original effort.

I think it would be a lot easier for everyone, as then you can update the main post of that thread
[Nook HD, HD+ Android Development] leapinlar:
I think that is an excellent idea. And I don't think hashcode would mind. Maybe even label it CM12.1
[Nook HD, HD+ Android Development] amaces:
The changelog would basically be the CM12.1 one, as my few changes are static (and mostly utilitarian). I've already submitted some of them to the upstream repositories, hoping that our devices get picked up by the nightly bots, and I can stop my personal builds. The four repositories that are most relevant to us (kernel_bn_omap & device_bn_{common,ovation,hummingbird}) are covered by the log in the OP.

About the ovation kernels, those images were for CM12.0, and while they may work with current builds (for reasons stated above), they don't provide any benefit anymore. Having them around just didn't seem a good idea.

You're right, and I knew this had to be done sooner or later. My intent was never to provide alternative builds, or deviate at all from official CM, but rather to share my interim personal images, until development/maintenance resumes for our devices. During CM12.0, I was simply frustrated with the few major bugs that remain. Based on the earlier pace, and how close it seems we are, I assumed official nightlies would happen very soon. Since that's not the case, I've opened this bare bone thread.

The reasons why I avoided another thread (and still am reluctant) are: 1) my changes, at least through CM12.0, seemed too minor to warrant another place for discussion, and 2) there isn't enough time and energy for both the learning curve and the work to support a proper thread. I'm not a developer, and while things are easier now, making any progress is expensive. That being said, I will stop posting CM12.1-related stuff here, but my unexplained obsession with LP on this Nook will continue on that thread.

No reason why he would; I have emphasized at least a couple of times that I'm simply piggybacking on [MENTION=4243514]Hashcode[/MENTION]'s and [MENTION=3654172]verygreen[/MENTION]'s amazing work (plus countless others). Honestly, the kind of heavy lifting that they did for such niche devices is humbling. The more you look through the logs, the more you realize how much quality work (and planning) they did so far.
[Nook HD, HD+ Android Development] ac-t660:
If I have the 3/24 ROM already installed, should I dirty-flash the 4/8 version or do I need to reset and fresh install it in order to properly get the changes?

And like everybody else has said - thanks amaces and hashcode, incredible job!
[Nook HD, HD+ Android Development] extrem0:
Since it's an upgrade from cm12.0 to cm12.1, a clean flash is recommended.

I tried dirty flashing and got some FCs related to Google Apps. Also, if you use them, you'll need to download an updated gapps (5.1).
[Nook HD, HD+ Android Development] Zippy Dufus:
FYI, I've build my first CM12.1 NookHD+ build and it is working great!

My installation procedure is:

I'm using a (old?) 2014-12-20 version of TWRP

"Repair" (format) all the partitions except external sdcard. (If you see the boot partition in the list,

don't repair it!!

)

Flash the ROM, Gapps, SuperSU in that order.

Wipe cache and dalvik cache (probably redundant as per #2, but for good measure)

However, Hangouts/Dialer is still broken and I am keen to get this fixed:

It force closes (FC) upon attempting to make a phone call. (Orginally on new CM12.0, it sort of worked but with unintelligible sound but after an Hangouts update it started to FC.)

It is broken (FC) on my CM12.0 Nook Tablet (16G). I've built a CM12.1 ROM and will check it if the problem persists.

Does anybody have a non-B&N CM12.1 device to check if working? I believe that it works on the CM12.0 Nexus 4 "mako" and will get the owner to check again with CM12.1. I suspect that the problem is in the common B&N/OMAP components. (Also, can someone double-check the standard build on the NookHD+? I'm running an experimental Linaro build.)

Anyone have any hints as to where to look? kernel? Sound configuration? [MENTION=4473900]amaces[/MENTION], Some time ago I tried tweaking the kernel memory from SLAB to SLUB (or visa versa) as you suggested in a previous post of yours. No effect.)

Anyways, [MENTION=4473900]amaces[/MENTION] thanks for this new thread and your great work!
[Nook HD, HD+ Android Development] dantpe:
First of all, thank you all for your contribution to making this happen, [MENTION=4243514]Hashcode[/MENTION] and [MENTION=3654172]verygreen[/MENTION] have done a great job, but so has [MENTION=4473900]amaces[/MENTION], not to mention everybody's ideas and feedback shared here and in other threads.

Secondly, having CM12.1 running on my ovation is quite a thing! It works pretty well, apart from the obvious problems everybody's noticed and I won't be repeating them here.

Finally, here's my 2p worth that I haven't seen mentioned, or that don't necessarily work the same on my device:

1. The shutdown works properly on my device, it switches off and never reboots on its own unless I turn it on with the power button.

2. After using Flashify to update my device from the Apr. 4th version to the Apr. 8th version something strange happened - the Nook would get stuck at the Cyanoboot screen and wouldn't boot into the system, or at least that's what it seemed. After a few forced shutdowns, formats of the system partition, re-flashes, and reboots, I finally realised that it does boot into the system, but it just get stuck on the Cyanoboot screen for about 1 minute before the Cyanogen logo appears and it proceeds with the normal boot process. Now, every single time it boots the same thing happens, I even tried flashing back the Apr. 4th version and it still gets stuck on the Cyanoboot screen for a minute. What did I break? How can I fix it?

2a. I had to re-flash Google Apps again after flashing the new ROM version, otherwise they kept crashing, including YouTube and Google Play. Now everything's back to normal. Any idea why that would happen?

3. Last, but not least, I have this issue that has haunted my device ever since 4.2 probably. There were more issues, but they slowly got solved and disappeared, and this one has somehow persisted all the way into 5.1. I have problems unlocking the device after it's been sleeping for a while while charging. I'm also using a smart-cover that wakes the device when I open it (not sure if its relevant here, neither whether it's after it's been charging). So I wake the device with either opening the cover, or with either the power- or the nook-button, then slide-up the lock icon, input my password, the regular screen shows for a split-second, and then immediately goes back to sleep. I have to unlock it about 10 times until it finally stays awake without switching off again automatically. Has anybody else noticed this behaviour?

Thank you all again, and if there are any logs I can contribute - I'd be more than willing to, I'd just need to be told which tool to use to get them, I'm not a developer, and correct me if I'm wrong, but it seems a bit more complicated than just fetching them from /var/lib/logs

Peace,

Daniel
[Nook HD, HD+ Android Development] Dread This Day:
The only issue I can say say anything about is unlocking it, that is caused by the smart cover. I encounter it a lot as well. I'll unlock it, it will just lock and the screen shuts off. I simply close the cover, and open it, screen comes on and I unlock it and all is well. If you don't use w smart cover, you'll never seen this issue. Your other issues, I'd bet a clean install would fix, just a suggestion.
[Nook HD, HD+ Android Development] evaporic:
Same issue with smart cover. I had to disable the lockscreen (set the lockscreen to none) in order to get around this issue with the smart cover. The other option is get rid of the magnets in the smart cover.
[Nook HD, HD+ Android Development] asakurato:
The issue with covers has been around for ever

Sent from my C6603
[Nook HD, HD+ Android Development] dantpe:
It was a clean install, certainly not an update/upgrade, when I first got CM12.1 on the device, so this probably isn't the right solution for all the issues.

I'll surely try your method with the cover over the next few days. Thanks!

---------- Post added at 01:39 AM ---------- Previous post was at 01:34 AM ----------

They might be not as smart, as they pretend to be, those covers ;) Well, neither would we be digging up the magnets, I think. Let's hope this gets solved one day hopefully before we decide to move on to other devices. I wish I knew how to help with it, unfortunately I'm not a developer and don't have the experience.
[Nook HD, HD+ Android Development] NookBookLover:
will the gapps work with cm 12.1?

will the gapps work with cm 12.1? Since someone else is making a 12.1 for nook build, but was wondering if a 12.0 gapps would work with it...

And thanks for all of your hard work!
[Nook HD, HD+ Android Development] aoleary:
I dont think so. I use the gapps here, with no issues. I use the these: http://xdaforums.com/showpost.php?p=59691695&postcount=3
[Nook HD, HD+ Android Development] ShowerHandle:
New Boot

Hello. I love this ROM and used the 2/17/15 build of it but had to go back to CM11 due to some glitches, but now I want to get back to the latest ROM. Before I do that though, I want to install the new recovery. I'm a bit of a noob at this and I don't remember how I installed CWM the first time, but could anyone help me figure out how to install this new recovery?
[Nook HD, HD+ Android Development] aoleary:
Use Flashify. You can download it from Google Play. To access TWRP you need to set Advanced Reboot in Developer Options and use the power button to go to Recovery. Using an app such as QuickBoot won't work.

Good luck & enjoy :)
[Nook HD, HD+ Android Development] ieatabiscuit:
I noticed that [MENTION=4473900]amaces[/MENTION] CM12.1 ROM uses a TON of my RAM for the system, where stock CM11 uses about half as much. This makes things bog down any time I have more than 1 thing going on at a time, and I have to constantly go to the task manager to manually close things to recover enough RAM to do anything again. On my phone, I saw that the system uses about 25% of what my tablet used. (Tablet used ~480 MB for system alone with CM12.1, and with CM11 the system and apps total at ~400. Phone uses ~120 for system alone running android 5.0.1). I understand that the kernels are NOT even close to similar, but it leaves me to wander why such a big difference, and is anything similar happening with [MENTION=4243514]Hashcode[/MENTION]'s CM12 ROM? Am I the only one noticing/experiencing this? Aside from that issue, [MENTION=4473900]amaces[/MENTION] CM12.1 ROM ran great, but the RAM issue was too much to stay with for the time being.
[Nook HD, HD+ Android Development] vaughnmr:
Your numbers are vastly different than mine, my Nexus 6 (5.1) is using 440mb and my Nook HD+ (5.1) is using 450mb system memory. Something doesn't sound right on your end...
[Nook HD, HD+ Android Development] ieatabiscuit:
Yeah, just talked to [MENTION=4473900]amaces[/MENTION] on his thread on it too. I'm going to reflash, and see what I could have mucked up. I guess I didn't sweet talk it enough to get what I wanted lol.
[Nook HD, HD+ Android Development] pmt223:
Help!

Hi guys, totally nooby question, but can someone explain how to install this if I have CWM recovery? I'm new to flashing the hummingbird, and I see a lot about using TWRP to install but cant find any good info about it anywhere, or someone just telling what to do to migrate. My story: I tried installing this and 12.1 using CWM. 12.1 wouldnt install but 12.0 does. No gapps package will install however due to error 7. So right now I'm just stuck. Please someone help. Thanks!