yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] aoleary:
Hi.

I installed the AOSP MM build from february 4th (aosp_ovation-ota-MMB29U.160204) on my NookHD+, but did not do GAPPs at the same time.

I installed the AOSP MM build from the CWM bootable SD Card image, however, now I cannot go into recovery anymore via the bootable SD Card image (neither the CWM nor the TWRP images).

How do I get it to go into recovery again?

I cant download anything as the browser crashes as soon as I try to download something.

I cant install apps as the file manager doesnt seem to see the SDCARD nor the internal storage, even though I can navigate to the SDCARD via the notification in the status bar..
[Nook HD, HD+ Android Development] tj2003:
i am having the same problems as you on Cm13.

On the latest CM12 the problem is I can view the movies but they will not download. They appear to start download but never show more than 0%.
[Nook HD, HD+ Android Development] theoneandonlybrooks:
Thanks for the reply. I feel a little better knowing it's not just me. I submitted a bug report on the issue as well. I've tried searching everywhere to see if it's a cm problem but it does not seem to be. I wonder if there's just something missing from these builds that can be flashed in.
[Nook HD, HD+ Android Development] belfastraven:
Before you did this, what internal recovery and rom were you using.? Which sd card image are you booting from? Did you install a twrp internal recovery after you booted from the SD Card? If you tell us exactly what you did we can better assist you.
[Nook HD, HD+ Android Development] aoleary:
Hi. I was using CM12.1 with TWRP 2.8.7.0, but I hadnt used my NookHD+ in a while.

I installed MM via the CWM recovery image. I had tried to install with the TWRP 3.0 image, but I kept getting errors of type 7. Saying that it could not install the ROM over a newer version Once I went back to the CWM recovery image, it installed fine.

I installed TWRP as the local recovery first, but the Nook would not boot into it on the Nook itself. I put the SDcard back in and tried installing MM from the TWRP 3.0 recovery image, but it wouldnt work as I mentioned above. So then I used the CWM recovery image and MM isntalled fine, however now, I cannot enter recovery by any method whatsoever.. :(
[Nook HD, HD+ Android Development] belfastraven:
If you were able to boot from an SD Card before, you should be able to do so again. Are you saying that when you have the SD card inserted that you booted from previously, the system just boots to the built-in rom now? Sometimes these machines are difficult to boot from the cards. You can try making sure the machine is powered off before turning it back on, (I sometimes have to try four or five times before mine will boot from external), try rewriting the sd card ( I would also write the latest TWRP 3 internal zip and the latest CM13 zip on it). If you do get it to boot, I would do a factory reset, then install TWRP internal zip, then CM13 internal. I think part of the problem initially may have been installing the AOSP rom over the cm rom without a factory reset.

The other thing you could try would be to connect the nook to your computer with ADB (which you could even do wirelessly when booted to the rom) and flash the image file from the TWRP 3 internal recovery.

Recovery partition: dd if=<path toTWRP image> of=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery . I have not tried that but think it would work.

I know you wanted an AOSP build--I am just suggesting the cm build because I know that it works with the TWRP 3 recovery. In general, it doesn't work well to just flash an AOSP build over a CM build, or vice versa, btw.
[Nook HD, HD+ Android Development] aoleary:
I did a factory reset before installing MM. I have been flashing ROMs for about 4 years now, so I am not a noobie :)

I will try writing TWRP as you suggested. That was going to be my fallback plan anyway.

Its strange though that the scard image worked fine before installing AOSP MM, and now it wont boot into it at all :(
[Nook HD, HD+ Android Development] belfastraven:
I Didn't know whether you had seen this thread--I imagine you have but just in case: New Nook HD+ will not boot from SD card. by kdb424 :)

It may just be coincidental that the problem started after MM installation, but I suggested rewriting the card ," just in case". Also, One thing that has solved problems for me in the past was totally wiping data (with a sucessfull recovery installed) if you don't have anything on there that you absolutely need and don't have backed up, it provides a really new start. Once you have a working recovery, if you wipe data, cache, and system, there cannot be anything left from previous roms/installs to cause problems. Let us know how you make out: I know it's very frustrating.

Your inability to download from the browser or chrome may be cuased by a permission problem, btw. Check to make sure that browser has storage permissions under settings, apps.
[Nook HD, HD+ Android Development] asakurato:
Flashed Feb 22 build onto Feb 8 build, got bootloop (flashed without wiping data, as always)

---------- Post added at 07:35 PM ---------- Previous post was at 07:15 PM ----------

Flashed and booted with wiping data, but supersu cannot be flashed, it says systemless mode, which requires patched boot image, but it failes at patching it, resulting in failed flash.
[Nook HD, HD+ Android Development] extrem0:
It isn't recommended to flash supersu. It is built it in developer settings.

Dirty flashed today's build fine.
[Nook HD, HD+ Android Development] games906:
But what about aosp
[Nook HD, HD+ Android Development] extrem0:
I don't know since I've only used CM13. Also, the guy I quoted is using CM because there isn't any aosp build released today, only CM ones.

Dirty flashed today's CM build and all went well. Wiped cache/dalvik as always. TWRP 3.0.
[Nook HD, HD+ Android Development] tj2003:
The new 2016-02-22 CM13 fixed Google Play Movies. No more problems with playback or downloading content.
[Nook HD, HD+ Android Development] lavero.burgos:
When i Power Off from menu it reboots, I have to long press power button to shut it down.

Using CM13 Feb 8 build. Is this fixed in new build? I can't seem to find the changelogs.

Enviado desde mi XT1053 mediante Tapatalk
[Nook HD, HD+ Android Development] extrem0:
I dont think so. Mine is rebooting on last build when selecting power off from power menu.
[Nook HD, HD+ Android Development] theoneandonlybrooks:
I've got a problem with the 2-22 and previous build where the nook app won't work. Once logged in, it checks info then reaches the screen where it says it's setting up the account. Then I just get a message from android that unfortunately nook has stopped working. It worked fine though on the previous cm 29T build. Any thoughts on what might've changed? I probably need to be careful what i ask for, movies are now working but I lost my ability to read magazines which is much more important to me.

---------- Post added at 08:11 PM ---------- Previous post was at 08:02 PM ----------

Google play movies app still won't let me play or download. YouTube let's me play my purchased content now however.
[Nook HD, HD+ Android Development] sacto7:
edit: removed the quote as I wasn't intending to do a quote.

Minor quibble(?) on the 2016-02-08 in that it won't go to twrp when the nook hd+ is charging. Or perhaps that is what is supposed to happen? As the battery was "low", I thought I would load the 2016-02-22 while the ovation was being charged; no problem otherwise.
[Nook HD, HD+ Android Development] neutronjeff:
Since TWRP 2875 is still the latest in the Ovation folder, are we OK using it for today's build, or is 3.0 recommend?
[Nook HD, HD+ Android Development] aoleary:
Hi [MENTION=5672278]belfastraven[/MENTION].

I got my nook to boot back into the sdcard. I tried the Power button + Nook button, which turned it off. But then I tried just to turn it on via the power button, and then it booted into the sdcard.

So its a bit more finicky than before, but at least it boots into the card now.

So I tried installing Banks GAPPs, but upon reboot, I kept getting playstore and Setup app errors.

So I restarted the Nook and did the Power button + Nook button, which turned it off so I again tried just to turn it on via the power button, and it again booted into the sdcard.

So after all that, I just said "f**k it" and wiped AOSP and installed CM13.

Now with CM13 I can boot straight into recovery from the Power Menu.

So, after a frustrating week or so, all has ended well :)

Thank you for your help. Even though nothing you specifically stated actually resolved my issue, indirectly I believe that it was crucial. So thank you for your time :)
[Nook HD, HD+ Android Development] asakurato:
How it is not recomended, I have used supersu from the first ever cm13 build for Ovation, never had any problems until yesterday.
[Nook HD, HD+ Android Development] extrem0:
Sorry. I didn't find here anyone saying you shouldn't flash SuperSU, but I follow other device MM build development and it was said it was risky to flash SuperSU because it would conflict with the built-in one.
[Nook HD, HD+ Android Development] TBueno:
RAM Leap

Ovation [CM] 02-22 here. Could barely believe my eyes when I read 840MB total! Really? Is there a catch?

Thanks a lot, AMaces :good:
[Nook HD, HD+ Android Development] belfastraven:
I was going to try to test the nook app for you, but the app in the play store says it can't be installed on my nook HD. I see the app was updated in late January. It's very possible that the problem lies with the app. Can you get a logcat after a reboot and then trying the app? In the past, people on varioius platforms have had the kind of problems you are reporting.

I know how frustrating this is--when I first moved to Marshmallow, I couldn't use the kindle app for a few weeks :). Google play movies did let me download and play, btw.
[Nook HD, HD+ Android Development] Tonto87:
Ovation CM 2016-02-22 is working well for me. Fixes the wifi reconnection bug after airplane mode I had, plus feels smoother! Thank you!

Battery life seems much better too!
[Nook HD, HD+ Android Development] theoneandonlybrooks:
I had to get the app from 1mobilemarket, I can share the apk on Google drive if you want. It worked fine on the 29t build which was also marshmallow. I've tried reinstalling the OS, including wiping everything to no avail. I'm not sure how to get a logcat, I'd be happy to do it if you can point me in the right direction.
[Nook HD, HD+ Android Development] belfastraven:
I've got it and will test later. The easiest way to get logs, in my opinion, is to use the syslog app, which is free on the play store.

Cue up the eery music: I got the app a few minutes ago: it failed for me in the manner you stated. I rebooted and tried again, (because I wanted to get a shorter logcat) and now it seems to be working. Can you try it again? It may be that something on the B&N side has just changed again. If not, If you could use syslog to get logs, it would help. I am running with root enabled, but I don't believe that should make any difference.
[Nook HD, HD+ Android Development] acr123:
I have MM CM 2-8-16 build and all is well. I have SuperSU 2.65 installed and it is granting access like it should. Do I need to remove it for further MM updates even if I dirty flash.

Thanks,

Al
[Nook HD, HD+ Android Development] extrem0:
I'm not sure, but I think you can dirty flash it without flashing SuperSU. I don't know if flashed SuperSU survives a dirty flash.
[Nook HD, HD+ Android Development] acr123:
HELP

I have TWRP 3.0.0.0 By mistake, the play store "updated supersu and then I got the error the binaries needed to be updated. I tried to update supersu to 2.67 using twrp 3.0.0.0 and I lost root. I tried again with twrp and supersu 2.65 and still unsuccessful. The Nook HD+ boots fine just no root.

After some brief reading, I think I need some type of modified boot image or kernel to allow root. Can someone be kind enough to guide me or tell me what file (s) are needed for Nook HD +. Do I need to change TWRP 3.0.0 or is that OK. I already have supersu 2.65, 2.67 or 2.52 in nook

Al

---------- Post added at 10:54 PM ---------- Previous post was at 10:34 PM ----------

Supersu 2.52 to the rescue & I have root again.. I guess the older supersu does things in the older way that is compatable with my Nook HD+. If somoene with more knowledge would explain about the newer method and files needed for root I could try that . I assume there would be advantages.

Thanks,

Al
[Nook HD, HD+ Android Development] theoneandonlybrooks:
Rebooted, uninstalled, rebooted, installed, same issue. When I try to run syslog, it says there is not enough space. Thoughts? I have a twrp backup from 29t, thinking about restoring and then ditry flashing 2-22 as an update. Is there a reason I shouldn't?
[Nook HD, HD+ Android Development] lavero.burgos:
Reflash the ROM. SuperSU is not needed, it's built in and works fine. At least in CM13.

Enviado desde mi XT1053 mediante Tapatalk
[Nook HD, HD+ Android Development] acr123:
I have MM CM 2-8-16. When you say reflash the rom tell me exactly what you mean. Do I remove supersu. Can I dirty flash the same rom by just going to twrp and flash rom and then wipe dalvik cache,etc.

What are the benefits of not using supersu

Thanks again,

Al
[Nook HD, HD+ Android Development] vinceweis:
I also still use 2.52 without problems. To me, I either have root, or not, and this one just works. I suppose there might be newer options to adjust each application for root access or something. For the most part, I don't care, but maybe someone else can enlighten us as to the value of a newer version. The 2.52 makes my apps that require root work.
[Nook HD, HD+ Android Development] theoneandonlybrooks:
Tried restoring an update, it failed at the end, so I'm stuck trying to make this work on the current version.

---------- Post added at 10:57 PM ---------- Previous post was at 10:45 PM ----------

Now suddenly syslog is working. https://app.box.com/s/qjvvvycr6n722fmy7er5fr9kfzieqrkt

https://app.box.com/s/sudo504n8ezhhy655u8iahf9u0slutjz

Let me know if either sheds any light.
[Nook HD, HD+ Android Development] Tonto87:
Bluetooth Keyboard

Okay, I may have a problem.

I have just bought a bluetooth keyboard and mouse (separately). Both pair, and the mouse works, but the keyboard won't show up as an input device and won't let me input text.

Also, the mouse seems to be recognised as a keyboard as has options for its language and other settings, which is strange.

I can, however, get both to work on my phone perfectly, which is Android 5.1.

I'm running CM 2016-02-22.

Am I doing something wrong with Android 6.0?

log cat attached.
[Nook HD, HD+ Android Development] games906:
I was JUST about to say that [emoji23] [emoji23]

I still had an older version of SuperSU and figured that SHOULD still work. So I let the app sit on the nook until Google play recognized it so it could update it to the newest one
[Nook HD, HD+ Android Development] lavero.burgos:
Format system and flash the ROM again, then clean cache and dalvik. As simple as that. Formatting system will remove SuperSU survival flash just in case it has it, no harm, simple, clean and works every time.

Enviado desde mi ghost mediante Tapatalk
[Nook HD, HD+ Android Development] acr123:
Thanks for the info. Is there a benefit to this instead of using supersu??

Al
[Nook HD, HD+ Android Development] lavero.burgos:
It just works. Start using it and if at some point it doesn't work for "x" app or for whatever else you need then flash SuperSU. Don't worry about it.

So far I haven't need it and I have a fair amount of apps that need root.

Enviado desde mi ghost mediante Tapatalk

---------- Post added at 08:47 AM ---------- Previous post was at 08:44 AM ----------

Sorry for the off topic but I really need some help. I started a thread in the Q&A section so if you guys could give it a read and advice I'll be greatly appreciated.

Gotta go for now, long drive ahead.

Enviado desde mi ghost mediante Tapatalk
[Nook HD, HD+ Android Development] mmnspeed:
I found a minor issue while using the default browser in the cm13 ROM...while in landscape mode on YouTube wesbite,if I tried switching to full screen,the screen would freeze with the audio still running in the background..might be a trivial issue considering you can use the YouTube app,but maybe the issue persists on other websites as well.hope someone else can try it and report if it is an issue with the ROM and not just my setup....apart from that the 22/02 build is awesome....
[Nook HD, HD+ Android Development] TBueno:
Yes, Chrome can't properly play full screen videos either. Firefox does the job just fine though.

The developer is aware of it, it has to do with him having to work from very old interfaces (see this post).
[Nook HD, HD+ Android Development] belfastraven:
I just installed a later version of the app( to see if it would fix the problem) from APKdler.com--I think it is the same version available on the play store. I am now having the same issue as you. I looked at your logs and mine and they are at least consistent. Still working on it...
[Nook HD, HD+ Android Development] theoneandonlybrooks:
Maybe an older version would fix it? Although I believe I still have a copy of the apk from my previous 29T install. Maybe I should try that. When I first tried to install on the older 29U, it gave a popup about being over the limit on the number of devices for video, with a popup to manage or deal with later, but whether I clicked or not (through various installs of app and cm) it still locked up on the setting up step. I used the app on my phone to get rid of old versions of my tablet (they showed up as a different devices per different versions of CM), but that didn't fix it. So I'm at a loss. Maybe the problem could be related to BN and how it recognizes the tablet?

Thanks for looking into it.

Do the logs say what happened to create the crash?
[Nook HD, HD+ Android Development] ImeBob:
Battery

I have been installing CM on tablets for years and this is my first major problem. I was running the 208 with only the shutdown problem after dirty installing the 222 everything worked great faster and smoother but when I tried to charge it flashed amber and green. I rolled back to 208 and when I tried to reboot was asked to plugin the charger. It booted but still will not charge. I have two chargers and cables both act the same and the longer the charger is in the lower the battery goes. I'm down to 39% hope someone can help.

Thanks, Bob
[Nook HD, HD+ Android Development] Technoodles:
My battery goes down from 100% to 74% in 5 mins and down to 1% and stays there. I can work for hours even with 1% battery showing. Something wrong but not sure if was because of the update to 02-22.
[Nook HD, HD+ Android Development] michisteiner:
Sorry for the ignorance, supposedly the HD+has 1024MB which means there are 184MB "missing". Is this rest "wasted" because it is overlaid with some memory-mapped devices or alike or is it just hidden being allocated to devices which do not show up in the system number?

On a related note, just having upgraded to CM13, i'm fairly happy with it but i did notice that RAM seems a crunch with some related ANRs. With Feb 8 or 22nd versions and OpenGApps nano installed, i end up with ~460MB System RAM as indicated in the Running services settings immediately after boot and it seems to grow over time to 500 and even 600. Does that seem reasonable? It seems rather high. Does this hide App-related RAM also? What are good ways to lower that to leave more for apps? Seems previous versions offered KSM which should help but i didn't see any option here: is that because it is now always enabled?

In any case, thanks for all the hard work to get the HD+: CM13 gave a great new life to a a-bit-dated device!
[Nook HD, HD+ Android Development] TBueno:
Well there's probably dozens of people on this forum more technically qualified than me to properly answer this, but I guess those 184MB are reserved for the operating system and its incredibly complex subsystems, services, tasks and whatnot. Think of it as the device's basal metabolic rate.

I was celebrating those available 840MB because the most I remember getting with other ROMs is around 790.

The only app crash I currently get is a "AudioFX has stopped" dialog two or three songs into my Deezer listening sessions, and it doesn't even make the current song skip any beat. This is a CyanogenMOD classic bug, dating back to CM 11, but Spotify seems immune to it in current AMaces builds (hooray!). So, as you said yourself, it's incredible how far this old hardware of ours has come.

Your RAM usage doesn't seem high to me. Anyway, when a lot of RAM is in use, that means your hardware is intelligently allocating your most used apps and info on it, reducing disk usage and providing a faster experience. As far as I know, a lot of idle memory means a waste of potential and power, and does not translate to a faster UX, quite the opposite: recurring to disk more often slows things down and requires more energy.
[Nook HD, HD+ Android Development] belfastraven:
see herehttp://xdaforums.com/showpost.php?p=62747907&postcount=967 for the same issue raised a while back by [MENTION=3450613]TBueno[/MENTION] with [MENTION=4473900]amaces[/MENTION] explanation. My (limited) understanding of this is that much of what is used is the Ducati carveout, memory that is pre-allocated for the Ducati image and video processing system.
[Nook HD, HD+ Android Development] michisteiner:
Thanks for digging that out! The explanation there was what i kindof was "fearing". The good news i guess is that amaces managed to carve out 60MB from these reserved RAM :good:
[Nook HD, HD+ Android Development] belfastraven:
The logs certainly say that lots of things happened:) Just for fun, open the logcat file with a text editor, look for the word "FATAL", and you will get some idea of why the app is crashing. I see java is complaining about a missing component, for example. I will submit a bug report about this, perhaps something will standout to [MENTION=4473900]amaces[/MENTION]. 'm pretty sure it will get straightened out in time..I know that doesn't help you now, I know that you've tried restoring a backup and reflashing the 2/22 rom, becuase of the drm problems on the earlier rom. If you restore and don't reflash 2/22, does the nook app work for you?
[Nook HD, HD+ Android Development] belfastraven:
Still not working for me--I think the GMS service is force closing or not running properly. I have been running with 11/15 open gapps.

Setup wizard still closes, so do google play services and at times gapps services.

Interestingly, with the use of both hands :) I can always boot into recovery, but the home button doesn't wake the device--the power button wakes it and turns off screen..

You have fixed the DLheap problems, we now seem to get fatal errors from art with memory allocation. I also see some errors about radio service files. I assume you see these also.

I will try installing a later version of gapps in a couple of days. If there is any particular way you want me to test something , let me know. I am going to pull some logs without any google services installed .

thanks again . I think we will probably have a usable marshmallow on this device very soon.

It still FC's on my hummingbird
[Nook HD, HD+ Android Development] king200:
I did a 'semi clean' install and all works fine. Haven't had a reboot or system freeze. Newsstand will not run. Older version, 4.31, of Gmail works. Location works. Wake with home key works too.

I advanced wiped everything except the storage locations. Installed Rom, OpenGapps Nano, and SuperSU 2.52. Booted into system and there was brief message about something FC but it never appeared again. Configured lockscreeen, SuperSu, developer options, and unknown sources. Entered no account information and did not sign into WiFi.

In TWRP, restored DATA only from the backup 1108 build that was done just prior to this install and wiped cache. Booted into system and the setup wizard flashed but was gone and not seen again.