yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] Zippy Dufus:
HDMI working?

Any news on this?

It doesn't seem to work on my DIY build and I'm wondering if this is still an issue before I try installing the official build.

Output of logcat when I plug in the HDMI cable:

04-03 13:46:58.664 431 505 V WiredAccessoryManager: Headset UEVENT: {SUBSYSTEM=switch, SEQNUM=2232, SWITCH_TIME=5475497650702, ACTION=change, SWITCH_STATE=1, SWITCH_NAME=hdmi, DEVPATH=/devices/virtual/switch/hdmi}

04-03 13:46:58.664 431 505 V WiredAccessoryManager: newName=hdmi newState=16 headsetState=16 prev headsetState=0

04-03 13:46:58.665 431 505 I WiredAccessoryManager: MSG_NEW_DEVICE_STATE

04-03 13:46:58.665 431 431 V WiredAccessoryManager: headsetName: connected

04-03 13:46:58.666 174 174 I AudioFlinger: openOutput(), module 5 Device 400, SamplingRate 48000, Format 0x000001, Channels 3, flags 0

04-03 13:46:58.666 174 174 I AudioFlinger: AudioStreamOut:: open(), mHalFormatIsLinearPcm = 1

04-03 13:46:58.666 174 174 I AudioFlinger: HAL output buffer size 1920 frames, normal sink buffer size 1920 frames

04-03 13:46:58.669 174 174 I AudioFlinger: HAL output buffer size 1920 frames, normal sink buffer size 1920 frames

04-03 13:46:58.670 174 5075 I AudioFlinger: AudioFlinger's thread 0x44980000 ready to run

04-03 13:46:58.673 174 5076 I AudioFlinger: AudioFlinger's thread 0x44880000 ready to run

04-03 13:46:58.680 174 174 I AudioFlinger: openOutput(), module 5 Device 400, SamplingRate 44100, Format 0x000001, Channels 0, flags 1

04-03 13:46:58.680 174 174 E hdmi_audio_hw: HDMI setting a default channel_mask 0 -> 8

04-03 13:46:58.680 174 174 I AudioFlinger: AudioStreamOut:: open(), mHalFormatIsLinearPcm = 1

04-03 13:46:58.680 174 174 I AudioFlinger: HAL output buffer size 1920 frames, normal sink buffer size 1920 frames

04-03 13:46:58.681 174 174 W APM::AudioPolicyManager: checkOutputsForDevice() missing param

04-03 13:46:58.684 174 5077 I AudioFlinger: AudioFlinger's thread 0x42695000 ready to run

04-03 13:46:58.684 174 174 W APM::AudioPolicyManager: checkOutputsForDevice() could not open output for device 400

04-03 13:46:58.684 174 229 D audio_hw_primary: adev_set_parameters::kvpairs == connect=1024

04-03 13:46:58.684 174 229 E bt_a2dp_hw: adev_set_parameters: ERROR: set param called even when stream out is null

04-03 13:46:58.689 955 955 I HeadsetService: Headset=false; Bluetooth=false ; USB=false; Speaker=false

04-03 13:46:58.690 955 955 I HeadsetService: Preferences updated.

04-03 13:46:58.700 153 184 I ti_hwc : ion handle[0][0xed163380]

04-03 13:46:58.735 153 184 I ti_hwc : ion handle[1][0xed163f00]

04-03 13:46:58.735 153 184 I ti_hwc : external display changed (state=1, mirror={disabled tform=180deg}, dock={enabled tform=0deg}, tv=0

​
[Nook HD, HD+ Android Development] Uldiniad:
Stuck at cyanoboot again

Title says it. I made a build today (ovation) and it seems this bug is back again. Anyone else having this issue? Suggestions? [MENTION=3651088]Zippy Dufus[/MENTION] can you let me know if you've made any builds since 03/04 that get past the cyanoboot screen on ovation?
[Nook HD, HD+ Android Development] TeutonJon78:
Um, is the new 4-1 build actually based on the 4-1 MOD joke code, or is it actually from before that?
[Nook HD, HD+ Android Development] tincup7:
root nook hd+

I installed AOSP with TWRP but now is no longer root . Can I root my nook? Van Simeone help?
[Nook HD, HD+ Android Development] Tight Git:
Flash SuperSU after ROM and Gapps
[Nook HD, HD+ Android Development] belfastraven:
Not sure if it was from before, but it is Safe--no joke code. (at least on hummingbird).
[Nook HD, HD+ Android Development] belfastraven:
I don't have an hdmi attachment for my nook so can't help test, but I found this re CM13 on a kindle fire (I think):

"I connected a bluetooth speaker and was able to successfully play a video while connected to an HDMI monitor. It appears the problem is that the audio stream is not routed via HDMI, and that the video won't play without a valid audio output path.

I'm running the "unofficial" CM13.0 build for the KFHD7. "

Someone else said it worked with as long as a headphone was in the nook.

Even if those things work (it might be interesting if you could confirm) it sure seems like the misrouting of audio is a bug. Maybe you should should file a bug report?
[Nook HD, HD+ Android Development] ipdev:
Unrelated but, has anyone tried to build a ResurrectionRemix build for ovation?

Only asking since I hope to be about a week away from starting to make my own builds. (In general.)

I would like to start with rr since I prefer it on other devices. cm seems to be the easy jumping board though.

I have read as much as I can. Only waiting on new hd for an older computer. (My new linux box. Haven't had one since I got my Sony ps2. Yes it has been that long since I was in the world of command line. ?)
[Nook HD, HD+ Android Development] rholm:
I'll test it. I like RR on other devices, usually very stable.

Cheers,

Rich
[Nook HD, HD+ Android Development] tincup7:
I get erros with supersu stable and beta

Decompressing ramdisk
Failure, aborting
[Nook HD, HD+ Android Development] acr123:
If still having problems, try SuperSu v 2.52 zip. This older version has worked for me in the past.
[Nook HD, HD+ Android Development] williamlaw:
Will possible to apply below mod to speed Nood HD+ ?

Thanks

http://xdaforums.com/nexus-7/orig-development/parrotmod-speed-2012-nexus-7-emmc-fix-t3300416
[Nook HD, HD+ Android Development] tincup7:
Working with SuperSu 2.52 ;) Many thanks
[Nook HD, HD+ Android Development] thewarm:
I just discovered this forum. I blindly stumbled thru youtube videos and webpages before coming here. I seem to have 'lucked out' on my Nook HD!

I used CWM to install cm_hummingbird-ota-MHC19J.160401. I did not use twrp or gapps. I have access to the playstore and installed Netflix, Crackle, Kore Remote. Netflix did not want to play a video, Crackle does. Kore remote controls my Kodi Media Center.

About tablet shows Android version 6.0.1, CyanogenMod version 13.0.20160401-UNOFFICIAL-hummingbird.

Did I luck out? Should I do someting else? Install twrp?

BTW, I didn't pull out the last of my hair getting to this point... :D
[Nook HD, HD+ Android Development] Uldiniad:
Still stuck on cyanoboot

I have been trying my daily builds for ovation and am still stuck on cyanoboot screen. It is strange because this is an old bug that has come back because they fixed it and it came back a few days ago (31/03?). Anyone else having this issue? Suggestions? Possible to mention this to [MENTION=4473900]amaces[/MENTION]
[MENTION=5672278]belfastraven[/MENTION] and [MENTION=3651088]Zippy Dufus[/MENTION] , I'm tagging you in because you've helped with this issue before

Thanks
[Nook HD, HD+ Android Development] belfastraven:
I have been building frequently ( but not for the past day or so) and have not had this problem. I'll try again today and let you know what happens. Are you able to boot if you reflash a rom that did boot before ? Can you boot with [MENTION=4473900]amaces[/MENTION] rom latest rom?
[Nook HD, HD+ Android Development] Uldiniad:
I haven't kept a copy of an old build anywhere, so I'll try [MENTION=4473900]amaces[/MENTION] latest build and see. And thanks for trying on your side, will be good to see if the issue is just on mine or if it's common.

Will be waiting to hear back and will report back the results of flashing his build.

---------- Post added at 04:35 PM ---------- Previous post was at 04:19 PM ----------

[/COLOR [MENTION=4473900]amaces[/MENTION] 01/04 build of CM13 gets past cyanoboot. I'll make a backup with it and then try my builds every day and restore this one if they keep failing.

Thanks for the suggestion [MENTION=5672278]belfastraven[/MENTION]

Hopefully, my builds will start working again soon. I'm still curious to know if your build will have the same issue as I or not.
[Nook HD, HD+ Android Development] belfastraven:
My build 2016/04/05 which just completed boots fine on hummingbird. I just dirtied flashed it over a 4/2 build that I made. We haven't heard from zippy yet--he's on ovation, but I can't imagine that one build would boot if the other wouldn't. You might want delete .ccache, if you are using it, and make clobber or make clean before you build again. I know that make is supposed to be smart enough to recompile everything that needs to be recompiled, but every once in a while there seems to be an issue with it. I assuming your are syncing before you build: if that is the case, and you are still having problems, I would try re-initing, without deleting your entire directory and then, if you STILL have problems, deleting your entire build directory and re-initing.

You can always submit a bug report, btw. Having already made a mistake once where I submitted a bug report when the problem was my fault, I try hard not to do that anymore :)
[Nook HD, HD+ Android Development] Uldiniad:
thanks for your help [MENTION=5672278]belfastraven[/MENTION]

For now I'll be keeping amaces' build. When time comes that I feel like trying one of my builds again, I'll follow your suggestions since they make a lot of sense (and not only for this specific bug scenario either).

I wish to everyone a happy future in modding and building CM13 for BN tablets :p
[Nook HD, HD+ Android Development] sepehr@teh:
Hi , for my Nook HD+ , there is 2 AOSP files in the Ovation folder .

Which is right file ?

BR.

Esfandyar
[Nook HD, HD+ Android Development] Tight Git:
I'm using the 160314 one and it works well
[Nook HD, HD+ Android Development] Zippy Dufus:
Enema time?

Try giving your working directory an enema with the (misnamed) attached script.

I created this script years ago before I understood what I was doing but still run it before my builds to this day. It may attempt to delete things which don't exist anymore. Remove the .txt extension and edit the cd (change directory) to your build directory.

Also edit accordingly or remove the specific deletes from your .repo directory at the end of the script. (These

don't

delete the actual 10GB+ git repo, btw.)

Perhaps you have "touched" (changed the timestamp) on some bad object in your working directory and it is not getting overwritten during the sync. This script will cause all your files to be checked out again from your local git repo again into your working directory when you sync.
[Nook HD, HD+ Android Development] sepehr@teh:
Hi , I'm trying to install AOSP . But can not boot from SD .

Devise is Nook HD+.

It's only a black screen , nothing happens .

What's wrong in the procedure ?

BR
[Nook HD, HD+ Android Development] belfastraven:
What is on the sd card? Is the nook even turning on? What is running on the nook now? Tell us exactly what you have done so far.
[Nook HD, HD+ Android Development] belfastraven:
thank you for reminding/clarifying procedure.

If a new rom is coming tonight or tomorrow, I'll install and get you logs/tombstones from the new build, if necessary :). I'm pretty plugged in to the amazon eco-system right now.... Not Youtube-- The tombstone files are rather large, btw.

Thanks again for everything [MENTION=4473900]amaces[/MENTION].

On another note, has anyone tried to build this using docker? I think for now that would be my only option for building on my pc.
[Nook HD, HD+ Android Development] belfastraven:
[MENTION=4473900]amaces[/MENTION]--please find attached a logcat and 4 tombstones which are the results of my having installed 11/22 rom and nano gaps, let ting google install a bunch of my apps(which also caused some errors in log but did install ) , and trying to use the kindle app. You can see that it has memory problems.. I've been curious: what are all the netlink errors concerning parameters time_NS and UID from? I've been seeing them alot--
[Nook HD, HD+ Android Development] FirePsych:
Short version: Follow [MENTION=4473900]amaces[/MENTION]'s instructions

Coming from [MENTION=4473900]amaces[/MENTION]'s 12.1

Have a backup of [MENTION=4473900]amaces[/MENTION] 6.0

Downloaded: [MENTION=4473900]amaces[/MENTION] 11.22.2015-6.0

Open Gapps latest (11.22.2015 I think) 6.0 Nano GAPPS

Already had latest TWRP and SuperSU

Booted into TWRP, backed up my 12.1

Rebooted into TWRP

FDR 3x, 'cause that's how I do it.DID NOT WIPE OR FORMAT ANYTHING ELSE

Flashed: In this order, at one time: [MENTION=4473900]amaces[/MENTION] 11.22.2015 6.0

Open GAPS 6.0 Nano

SuperSu

reboot

Booted fine.

Did not sign into anything.

reboot

Sign into Wifi

Reboot into Recovery/TWRP

Restore DATA from my last [MENTION=4473900]amaces[/MENTION] Nandroid (I usually don't do this, but I was curious, so I tried it.)

Wipe dalvik/cache (this is the 1st time I did this)

reboot

Got some Google errors

Signed back into Google.

Have some Google based errors here and there

A handful of reboots and some updates through Google Play

Working fine, Except:

Kindle Reader is not cooperating

Systems is just simply SLOW

It's like asking the kids to poop scoop the litter box. It might happen, but I have to wait for it.

But, like the kids, it eventually, usually does what I ask it to do.
[Nook HD, HD+ Android Development] belfastraven:
Memory calculation?

[MENTION=4473900]amaces[/MENTION], In developer options, under running services, sometimes I get quite normal memory statistics but often I get numbers like those in the attached screen shots. I know I often feel like I, personally ,have negative amounts of memory, but didn't realize my nook HD felt the same way.:)

memory reported in "memory" setting is always showing normal....
[Nook HD, HD+ Android Development] FirePsych:
I'm getting the negative memory too.

My Ovation is crawling.

Suggestions?

---------- Post added at 04:42 PM ---------- Previous post was at 04:08 PM ----------

Installed Kernel Adiutor and with some tweaks, got the memory free for running processes in the + range. Still in the - range for cached processes
[Nook HD, HD+ Android Development] extrem0:
If you install it without gapps you'll be able to use your nook.
[Nook HD, HD+ Android Development] FirePsych:
That might be a fun experiment
[Nook HD, HD+ Android Development] leswgnr:
That is exactly what I experienced. A factory reset did not work. Formatting /data did.
[Nook HD, HD+ Android Development] FirePsych:
FDR 3x and installed just ROM and SU. Still have negative memory issue.
[Nook HD, HD+ Android Development] starbright_:
[MENTION=4473900]amaces[/MENTION]:

Thanks for your great work here. May I ask you to update the initial post with current state (so whats the biggest issues left).

Every once a while (weekly) would be nice, so that interested people easily can see the progress.
[Nook HD, HD+ Android Development] smileyint:
I think there is memory issues as apps performance is considerably slower than compared to experience with cm12. Still thanks to Amaces that breathe life into a rather old device. :)
[Nook HD, HD+ Android Development] pavlos46:
New biult, any info on whats changed.

Pavlos
[Nook HD, HD+ Android Development] pavlos46:
Sorry for my original post was definitely misleading, so for better or worse tried to dirty flash over cm12 and system crashed on me, for some reason I even couldn't get into recovery.

Flashed back to stock and will retry M on a clean system.

Pavlos
[Nook HD, HD+ Android Development] Tschumi:
I don't think is generally advisable to dirty flash, especially from lollipop to Marshmallow. A full wipe is always recommended. Btw, I am using verygreens cm 4.2.2 and it's very smooth, even running from the sdcard. You should try it.
[Nook HD, HD+ Android Development] belfastraven:
11/27 rom and gapps nano.

Running on Hummingbird with 11/27 rom and 11/27 open gapps nano, superSU 2.52.

So far this rom is quite a very smooth and quick once apps load for the first time--and, yea!, [MENTION=4473900]amaces[/MENTION], kindle app is working . (was it a webview problem ?)

I notice that the time in the righthand corner of my status bar is reading 6:00, no matter what time it is, but everything else on nook hd has the correct time. Don't know whether the time freeze happened before or after I enabled System UI tuner--not important, just interesting. Memory under running/cached services still seems not to be calculated properly-- I'll see what it looks like after 24 hours. perhaps this has something to do with the 100th anniversary of "general relativity"--something is causing memory "black hole" :)
[Nook HD, HD+ Android Development] amaces:
Please do stay on stock. I understand that you're not a native speaker, but please read the last couple of paragraphs in the OP. No idea how a select few people manage to run into these issues; I must have flashed hundreds of test builds, AOSP, CM, etc, without running into these basic issues.

Otherwise, the current builds should fix a few major memory allocation issues (e.g., Kindle, YouTube), and are at least as usable as the previous batch.

Thanks for those; I looked and looked and found nothing more explicit beyond the threatening allocation failures. It's been a month that I've been working on the YouTube issue, and although the Kindle memory allocation tombstones were different, they seemed related. In the end, they were due to dlmalloc, the userland allocator that's supposed to help on low RAM devices (a setting inherited from the early Lollipop porting days). Anyway, I switched to jemalloc, the current default, and at least on ovation, things are fixed. The problem is this newer allocator was devised for devices with plenty of RAM, is more complex, and has a lot more overhead (people claim >50 MB more bookkeeping overhead compared to dlmalloc). I for one didn't notice additional memory issues, but obviously this is a major change that needs testing.

Either way, dlmalloc seems to have fallen into disrepair upstream, so not many choices left.

I'm not convinced that reporting negative memory is an intentional feature; clearly the system wouldn't run with actual negative memory. The tool may get confused by zRAM. Also, lots of UI bits at the edges of AOSP are half-baked… The numbers themselves don't correlate directly with dumpsys meminfo output, a tool that I trust a lot more.

Reporting and reality are two different things; read above.

;)… :(

Yes, I'd like that too, but at this point the choice is between directing my energy (and hundreds of hours so far) working on what needs urgently fixed, versus writing about broken stuff (which cannot be totally avoided despite my best attempts). Given that I'm pushing new builds every week or so, you can bet enough fixes have accumulated, and I often describe them on the thread. People who make an effort to provide usable testing feedback certainly get my best attempt at explaining and solving issues.

As described in the OP, the purpose of these builds, at least in theory, was to aid development, and that kind of help has only happened a handful of times. Once we get to something resembling beta, my goal is to list all my changes. At the end of the day, all this information is easily available in my GitHub repositories. As of now, it seems more important to have these, and supporting manifests, in good shape.
[Nook HD, HD+ Android Development] pavlos46:
My apologies to Amaces and my gratitude for his efforts.

But please do understand that English is my second language, so I take full responsibility for an ill advised post. Which I have updated to exactly reflect my thoughts.

Nevertheless I am greatly disappointed to be characterized as a select few or even trouble maker, have been on xda for many years, since nook color, and in my time have helped people on simple issues ( I am neither a developer or beta tester).

So please do accept my apology and please go ahead and continue your amazing builts.

Regards

Pavlos
[Nook HD, HD+ Android Development] amaces:
No worries, I also am sorry for reacting; your post happened to provide the trigger for the frustration accumulated here, and on the CM12 thread… As mentioned a few times, thanks or gratitude are not terribly important, but constructive, thoughtful feedback is. I will help with most issues, as I did with your compatriot, but making forceful claims beyond the limits of personal knowledge bugs me a lot. I also have to keep myself in check, otherwise these threads would be a mess… So yeah, keep reporting when specific things break, but it's useful to check the usual culprits first (e.g., did I wipe cache, have I checked if a clean install fixes things, etc).
[Nook HD, HD+ Android Development] pavlos46:
Great thanks, you are right, will try to provide more accurate and constructive feedback.

Pavlos
[Nook HD, HD+ Android Development] Minshter:
I am using the Ovation build from the same date, with the same open gapps, but my time is correct in the right hand corner.

Since you mentioned it might have occurred after you enabled System UI Tuner, I enabled that to test, and the time was still being reported correctly.

I wonder if its an issue specific to the Hummingbird build?

If there was some other setting you changed, or app you added, that you think might have led to that, I'd be willing to test it here to see if I can repeat what you are seeing (if that would help).

For those who are missing the advanced power menu, you might want to give Simple Reboot on the playstore a look. It lets me boot into recovery rather nicely.

Here is a link for those interested.

https://play.google.com/store/apps/details?id=simple.reboot.com
[Nook HD, HD+ Android Development] sepehr@teh:
Thanks for response.

The size of SD , doesn't allow the display work. My SD is 32 GB.

I created a lower size partition and now it works. A size below 15 GB .
[Nook HD, HD+ Android Development] sepehr@teh:
Just installed AOSP , successfully.

Device : Nook HD+

WiFi has problem, turning on takes time , nothing happens ; any solution?

Also gapps is not complete ; which file is right & complete?
[Nook HD, HD+ Android Development] sepehr@teh:
Installing AOSP is , Ok and WiFi worked ;using another version.

But gapps still remained not installed !

I used the file : open_gapps-arm-6.0-stock-20160408.zip

Installer says : insufficient storage space available in system partition . . .

.

.

.

Error code : 70
[Nook HD, HD+ Android Development] vinceweis:
From the OP: "Open GApps nano should install without issues on both AOSP and CM, although initial flashing needs to be done before first boot (wiped data)." Note the word nano. A search of this thread will give you additional info.
[Nook HD, HD+ Android Development] belfastraven:
4/07 hummingbird in device folder on box running well.
[Nook HD, HD+ Android Development] pchc_lx:
finally got TWRP 3.0.1 and yesterday's OVATION build flashed & installed correctly... wow! works great. thanks so much
[Nook HD, HD+ Android Development] mikeataol:
I also installed cm_ovation-ota-MHC19Q.160407.zip and the TWRP twrp-3.0.1-0-ovation.zip.... very happy with it so far. Thanks for making it available.