yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] PMikeP:
Okay, coming to you from Pinguy's 10.1 ROM.

A few questions:

Where are the slide punctuation marks on the Lollipop keyboard? (I don't know what to call 'em, but like the apostrophe on long tap on the ”c" key?)

I don't see a way to change grid size, add screens, change Home screen etc. on the launcher. It's not in my settings when I click the 3 vertical dots.

Similarly, I don't see a way to disable the Search bar/disable Search.

I've installed this ROM three times now (clean), just to learn about the hot reboot and stuff. I notce that there's no bullet set on the radio button for zRAM, altough "free" command shows it's working, as pinguy said.

Update: Link2SD doesn't work for me on this ROM. (Hangs on boot when I try to relink the apk's.) I have a lot of apps linked to my ext SD card, so this is a concern.

And importing my current wpa_supplicant file didn't work for wi-fi.
[Nook HD, HD+ Android Development] FirePsych:
Hey Mike,

To keep things clean, I'm gonna offer my discounted $.02 in PinGuy's original thread for this rom.
[Nook HD, HD+ Android Development] PMikeP:
Gotcha. I posted over on pinguy's thread.
[Nook HD, HD+ Android Development] PMikeP:
The freezing problem seems to follow the kernel. I've back on the .31 kernel for a week and it's been trouble free.

BTW, there was a Chrome update along the way. Don't know what they changed, but I've been able to run 25 tabs in Chrome & switch between 3 aviation apps & not skip a beat. (Running LMK in kernel tweaker.)
[Nook HD, HD+ Android Development] Jon Lee:
Updated the ROM. It's a lot smoother now.

:D

ROM: http://www.mediafire.com/download/ikwmpn1ppxb3dwi/cm-10.2-20150622-UNOFFICIAL-ovation.zip

MD5: http://www.mediafire.com/download/cyx7bvm0wrjuso5/cm-10.2-20150622-UNOFFICIAL-ovation.zip.md5sum

Kernel Source: http://www.mediafire.com/download/afoflqd4bh8jgf3/kernel-20150622.tar.gz

Also added some TI Audio HAL glue... (Doesn't seem to break anything. Relies on TI's Tinyalsa lib).

Source: http://www.mediafire.com/download/un8l1aa5zk4a281/audio_bn.tar.gz

(I've had some of my highest benchmarks ever recently...)
[Nook HD, HD+ Android Development] PMikeP:
Is it still the 3.0.72 kernel?

The Interplanetary Magnetic Field is high to the South. Perhaps that explains the high benchmark too? :)
[Nook HD, HD+ Android Development] Jon Lee:
Could very well be. Have you seen the Venus/Jupiter conjunction recently?

:cool:

Actually I think it was mainly Samsung's ION changes mostly responsible. A little to do with a domx "upgrade" to (well, actually, jb-mr1 source).

(I also fixed ROW IO sched. Comp.)
[Nook HD, HD+ Android Development] dk1keith:
does this rom have to be installed using TWRP? or will CWM work
[Nook HD, HD+ Android Development] Jon Lee:
Data and cache have to be converted to f2fs, which requires twrp (pg 20, I think??...).
[Nook HD, HD+ Android Development] Jon Lee:
Ya know, unless you need/use bookmark syncing, the stock browser works very well.

It is an app bug which I have very little control over.

(And more than likely involves "broken" ipv6 tunnels/backdoors because of the ipv6 options sys path changes.)

https://www.privateinternetaccess.c...s-the-importance-of-privacy-defense-in-depth/

The very same OK Google/Google now uses....
[Nook HD, HD+ Android Development] twiztid_:
There's a BookmarksSyncAdapter.apk that let's browser use Chrome/Google bookmarks.

PAgapps has it for 4.4, and I had one for 4.2 but don't recall where I got it from. Its not perfect, and I've had some minor issues (android added bookmarks don't sync up to desktop, but seem to be added to other android devices? And bookmark names/titles aren't saved), but stock beats the crap out of Chrome in terms of stability and speed.
[Nook HD, HD+ Android Development] PMikeP:
I don't know what it is with me and Chrome. (That was a scary article abt Google eavesdropping, but I think I'm safe, since I have Framework disabled.)

I did a dirty flash, just to get running quick & dirty. As w/ my last attempt w/ 3.0.72, Chrome hangs until it finishes loading pages or drawing. I tried the stock browser and it flashes over & over again when I open twitter. (I've played w/ page settings. N/C.)

I'll try a clean flash later, but I'm not hopeful that the stock browser will work any better. What changed in the .72 kernel that would cause this? I can't tell if it's a video problem or memory/zRAM.

Otherwise, the ROM does seem smoother.
[Nook HD, HD+ Android Development] Jon Lee:
I don't experience that problem. Anyone else have issues?

I would say something in your setup, MTL.

Start clean and fresh before installing Chrome...
[Nook HD, HD+ Android Development] PMikeP:
Yeah, I'll try that. Chrome freezes/crashes w/ this ROM on web pages like this one (forum), with lots of screen elements. (That's why I think it's a video or mem problem.)

Update: I can feel the CPU getting hot in Chrome. Am thinking it's a gov problem? Lowered max speed to 1500. Am trying a diff gov now.
[Nook HD, HD+ Android Development] Jon Lee:
Chances are if it were a kernel,mem, or video problem, at least one other person would experience it. I mean maybe you have some odd chipset... ya never know.
[Nook HD, HD+ Android Development] PMikeP:
My aviation app gave me an "out of memory" error for the first time ever. So that's a clue. Perhaps I've got bad RAM and the .72 ROM stresses it? (Trim problem?) Or, perhaps I have an odd chipset. IIRC, the 16GB HD+ is different from the 32GB. (I have the 16.)
[Nook HD, HD+ Android Development] Jon Lee:
I'll keep it in mind. I don't see me reverting right yet, nor putting out too many other versions. I'm perfectly comfortable with how the .31 version operates. Makes no difference to me- your choice.
[Nook HD, HD+ Android Development] PMikeP:
I agree. No complaints w/ your .31 version.

Update: IIRC, in the interval between 3.0.31 and 3.0.72 is when you lost your backup copy? If correct, I wonder if there's a setting that didn't get restored for the .72 compile? Altho if that were the case, then I wouldn't be the only one who's having trouble.

Another update: I tried accessing Twitter w/ the stock browser in 3.0.31. I set the browser for desktop agent. I can see why it flickers in .72. I get the white right section of my Twitter home page painting in large video blocks from upper left to bottom right. I'll try to record it w/ my camera and upload a video later. Doesn't paint this way in Chrome.
[Nook HD, HD+ Android Development] PMikeP:
I did Jon's "really clean the /system partition" trick by formatting /system to f2fs then bact to ext4. That, and a factory reset, allowed me to install the 621 ROM w/ the 3.0.72 kernel.

Everything seems to run fine, but my tabet still freezes occassionally during memory intense operations, like when installing an apk thru Link2sd. (Whereas it didn't freeze w/ the .31 kernel.) I remember that Jon found a bug in the previous zRAM implementation. I wonder aloud if the updated kernel broke some memory management feature?
[Nook HD, HD+ Android Development] xknobi:
I am using TWRP 2.7.1.0 with CM 10.1-20130708 (3.0.31-green+ kernel). Tried to install the ROM with yellow kernel. But tablet stays at boot animation forever. Guess I have to format system to f2fs manually at first?

I can't find this option in TWRP, which recovery should I use?

Is there any separated kernel to install other than install the whole ROM?
[Nook HD, HD+ Android Development] PMikeP:
This is a "hybrid" ROM. /data and /cache are f2fs. /system stays ext4. The option is in "Advanced" (IIRC), under "change file system" in TWRP.

See http://xdaforums.com/showpost.php?p=59112482&postcount=189

The ROM is complete w/ kernel. The only thing to watch for is that you have to let the ROM boot first before you flash GAPPS.
[Nook HD, HD+ Android Development] xknobi:
Thanks, with the right TWRP I have been able to install the ROM and now play with it. :good:
[Nook HD, HD+ Android Development] PMikeP:
More thinking aloud - could anything in the 3.0.72 kernel have changed writing to the extSDcard? Different i/o scheduler for extSD?
[Nook HD, HD+ Android Development] Jon Lee:
No. But I do have a potential fix for ya. (Importing our kernel headers into bionic libc).

I'm working on some other things right now... but I'll get to it.
[Nook HD, HD+ Android Development] sutty86:
Sorry to be a pain what's the major differences with this ROM/kernal then cm11

Looking for good SOT and only use for reading,movies and chrome
[Nook HD, HD+ Android Development] PMikeP:
This one doesn't crash.

I came from CM 11 when development was slowing down due to CM12. So I don't know if it ever got better or if they ever incorporated drmable's zRAM implementation.

Whatever, this ROM is like having an iPad. It just works. (As I've mentioned in earlier posts, I use Chrome and typically have 15 to 20 tabs open. The 3.0.31 version of Jon's ROM worked better with Chrome, but Jon thinks he has a fix coming for this 3.0.72 version.)
[Nook HD, HD+ Android Development] PMikeP:
Oops. Stupid me. I never moved Chrome to the extSD. It's been running in RAM. So false alarm on that aspect - whatever causes my occassional freezes in Chrome, it's not related to the ext card. Having said that, I do get quite a freeze when I install to extSD via Link2SD. (Whereas I didn't get that before.)
[Nook HD, HD+ Android Development] Jon Lee:
--- ../sgt7-10.2/system/core/toolbox/nandread.c	2015-01-14 08:15:24.781556874 -0500
+++ system/core/toolbox/nandread.c	2015-06-28 16:37:36.401260057 -0400
@@ -5,6 +5,7 @@
#include <errno.h>
#include <fcntl.h>
#include <unistd.h>
+#include <inttypes.h>

#include <mtd/mtd-user.h>
#include <sys/ioctl.h>
@@ -44,7 +45,7 @@
struct mtd_info_user mtdinfo;
struct mtd_ecc_stats initial_ecc, last_ecc, ecc;
struct mtd_oob_buf oobbuf;
- struct nand_ecclayout ecclayout;
+ nand_ecclayout_t ecclayout;

do {
c = getopt(argc, argv, "d:f:s:S:L:Rhv");

ROM: http://www.mediafire.com/download/i5czxe52m7jio6h/cm-10.2-20150630-UNOFFICIAL-ovation.zip

MD5: http://www.mediafire.com/download/0b1jy00qnkdb0z9/cm-10.2-20150630-UNOFFICIAL-ovation.zip.md5sum

Kernel Source: http://www.mediafire.com/download/f08epvdtbf9f45d/kernel-20150630.tar.gz
[Nook HD, HD+ Android Development] PMikeP:
I don't understand the greek, but it seems to be working so far! Everything loads faster. (Dirty flash.) If this holds, I think you're done.
[Nook HD, HD+ Android Development] mizu12:
Hi Jon, the upgrade (I have the 0622 ver. and very satisfied with it so far) goes just through wipecache+install over the previous version? Thanks.
[Nook HD, HD+ Android Development] sutty86:
Guys what's battery life like
[Nook HD, HD+ Android Development] bibikalka:
Jon, I am running 10.2-20150516 version of yours. Can this latest one be installed via a dirty flash? Or would it have to be done from scratch?

Overall, 20150516 works very well. The only issue I've observed is that youtube would freeze the tablet every few hours, and I have to reboot it by holding the power button (my son tests this by watching youtube cartoons :D ). I don't recall such as an issue when I was running stock 10.2 back in the days. Is there anything I can look at to figure out what might be happening?
[Nook HD, HD+ Android Development] twiztid_:
You should be able to wipe /system, /cache, and /dalvik, then install the new ROM and gapps (may need to boot to home screen before gapps).

That's my standard update method, and I haven't run into any issues. Sure a full clean install is better, but a lot of work getting g things set up again.

Edit: I meant /cache, not /data.

Wiping /data will get rid of your apps (but keep your user files on /sdcard), which is not what I intended.
[Nook HD, HD+ Android Development] ajislav:
Are you sure about wiping /data ? I thought that this is the place where user data reside...

I.e. wiping data is basically a factory reset
[Nook HD, HD+ Android Development] twiztid_:
A normal wipe of /data will only wipe your apps. Your user data (internal storage, /sdcard) will be preserved, unless you change the file system of /data which forces a format of the /data partition and includes /sdcard. I found that out the hard way.

But yes, re-rearing my post, I did not mean /data for an update. Wiping /system should be good enough for updating within the same ROM, and of course /cache and /dalvik.
[Nook HD, HD+ Android Development] Jon Lee:
I added some code to our pvr-source, pulled from Jacinto's 1.12 DDK.

http://pastebin.com/j0z3ZLxa

This mainly changers compiling options, but also raises our API level a few points.

I also enabled Link Time Optimizations.

make -j2 -C $(COMMON_FOLDER)/pvr-source/eurasiacon/build/linux2/omap4430_android ARCH=arm CROSS_COMPILE=$(ANDROID_BUILD_TOP)/prebuilt/linux-x86/toolchain/$(TARGET_KERNEL_CUSTOM_TOOLCHAIN) KERNELDIR=$(KERNEL_OUT) BUILD=release TARGET_SGX=544sc PLATFORM_VERSION=4.3 USE_LTO=1

Overall this reduces benchmark scores slightly, but graphics transitions have never been smoother.

It didn't really do what I wanted for Lollipop, but it may be helpful for KitKat...

Kernel and system remain unchanged.

ROM: http://www.mediafire.com/download/tt1ys6eachjvatl/cm-10.2-20150706-UNOFFICIAL-ovation.zip

MD5: http://www.mediafire.com/download/4718lhvd78aglti/cm-10.2-20150706-UNOFFICIAL-ovation.zip.md5sum

PVR Source: http://www.mediafire.com/download/etrzigl6ufn8aa6/pvr-source.tar.gz

Edit: I was wrong, it totally does what I wanted for Lollipop! IOW, the graphics quality of this build is exactly what can be had in LP! That took me awhile.
[Nook HD, HD+ Android Development] infra_red_dude:
Thanks Jon! I can attest the snappiness of this build on the graphics side. So far everything works great. This has been the best build so far on my device...

What new API versions are supported in this build?
[Nook HD, HD+ Android Development] Jon Lee:
The PVR API level went from 16 to 18. What that really means, I don't know, but I imagine it's in the ducati somewhere.

I know it makes a difference because it impairs benchmarks and the time it takes domx to retrieve video album art.

For this reason, I've thought about dropping it a notch. But, then, I would lose some jbmr2 specific configs, so I dunno. I'm not real sure if the ducati properly supports anything higher than 16 or 17.

I do know I have successfully used it catch a proper framebuffer from our original JB HWC on lollipop (old kernel style)... Compiled at platform_version=5.0, API 20. I'm still working on portions of that, but it's certainly promising.
[Nook HD, HD+ Android Development] FirePsych:
I have no idea what any of that means, but I gave it a thumbs up
[Nook HD, HD+ Android Development] twiztid_:
I'm unsure myself, but I think it's a fix (or start of one) for the frame buffer underflows which cause flickers, especially on Lollipop.
[Nook HD, HD+ Android Development] Jon Lee:
Yep. Although I can't seem to switch it to the proper forum.

http://xdaforums.com/nook-hd/general/rom-slim-ovation-5-1-alpha-0-1-t3154141

lemme know how it works
[Nook HD, HD+ Android Development] Soul0Reaper:
flashing the latest build, my HD+ is stuck trying to turn WiFi on. Did I do something wrong?
[Nook HD, HD+ Android Development] Jon Lee:
An initial reboot should take care of it. Let me know if it doesn't.
[Nook HD, HD+ Android Development] Soul0Reaper:
Yeah it's working now, thanks!
[Nook HD, HD+ Android Development] Jon Lee:
If anyone payed attention, Hashcode fixed the issue with domx retrieving video album art in his lollipop video HAL.

(A first for any Nook rom I believe, certainly any of the official CM builds.)

Basically this:

BOARD_USE_TI_DOMX_LOW_SECURE_HEAP := true

in BoardConfigCommon.mk

and

LOCAL_CFLAGS += -D_Android -DENABLE_GRALLOC_BUFFERS -DUSE_ENHANCED_PORTRECONFIG -DANDROID_QUIRK_LOCK_BUFFER -DUSE_ION
ifdef BOARD_USE_TI_DOMX_LOW_SECURE_HEAP
LOCAL_CFLAGS += -DDOMX_LOW_SECURE_HEAP
endif

in domx/domx/Android.mk

No one knows how long this had been bothering me, and it's too good not to apply here.

A huge thanks for that!

ROM: http://www.mediafire.com/download/3qo9gcnnm9x8mfp/cm-10.2-20150715-UNOFFICIAL-ovation.zip

MD5: http://www.mediafire.com/download/c1cclkga9jlxkjv/cm-10.2-20150715-UNOFFICIAL-ovation.zip.md5sum
[Nook HD, HD+ Android Development] mizu12:
Bluetooth problem

Unfortunately I'm not able to connect to my JBL Fllip 2 on Bluetooth. Tried WiFi turned off, but no success.

Can you give me some advice how I can make it work (or debug...)?

Thanks

PS: running the latest ROM version.
[Nook HD, HD+ Android Development] Jon Lee:
Bluetooth with 10.2 is finicky at best, at least the initial pairing with some devices.

The two tricks I have learned.

1). Exit the bluetooth menu and then re-enter into it.

2). Reboot the tablet with bluetooth turned on.

There's been a few times I have spent 15-20 minutes trying to pair a device, cursing towards the end, and then other times it has paired immediately.

Good luck is all I can say.
[Nook HD, HD+ Android Development] PMikeP:
Do we need to fear Stagefright vunerability?

Jon?
[Nook HD, HD+ Android Development] Jon Lee:
Since we don't have the ability to accept MMS messages, I would say no.

That said, the underlying video vulnerabilities are probably there for a reason.

There's always been a thing with "malformed" videos/images.

(Have you ever seen the list of flash vulnerabilities...?)
[Nook HD, HD+ Android Development] PMikeP:
Thx. I figured we were safe from the primary attack vector, since we can't do MMS. Was concerned aby secondary vector, as you noted w/ Flash. I read that G came out w/ a fix for this - can it be folded in to your build and would it break anything?
[Nook HD, HD+ Android Development] Jon Lee:
I'll look into it if you have a link to a suitable patch.
[Nook HD, HD+ Android Development] PMikeP:
This is as close as I can get.

http://www.androidpolice.com/2015/0...my48i-factory-images-for-seven-nexus-devices/

I presume you've already seen this.
[Nook HD, HD+ Android Development] bibikalka:
The 10.1 version is golden!

My main use for this tablet is to have the kid watch Youtube. /data is formatted as f2fs. So far I had the following issues with 10.2 :

stock 10.2 worked OK, no crashes, but got very slow over time and laggy interface

10.2-20150516 worked mostly OK, but youtube would freeze the tablet every 2-4 hours, with stuttering sound

10.2-20150715 crashed every hour or sooner, video would freeze, but sound continued as if youtube was still playing. I tried a factory reset, no help

10.2-20150630 same as 0715 above, crashed every hour, even an ancient version of youtube crashed the same, so it's does not seem to be a Youtube issue, but the newer kernel in this later batch of 10.2s

10.2-20150526 this one is the last with the prior kernel version, I have not tried, but suspect it'll be similar to 0516

Finally, I bit the bullet and downgraded to 10.1-20150527 (it was a bit rough, needed a factory reset, and SuperSu zip had to be old, the last working is 1.43).

10.1 already crashed a few times with Youtube (sound continues, but video freezes, spoke too soon in the original post...). I underclocked it to 1.3Ghz, it's still crashing. So it does not seem to be any kind of overheating ... It looks that the youtube battery life is better with this 10.1 than 10.2 (could also be the newer youtube verson).

Because 10.1 has better battery life, I am keeping it for now.
[Nook HD, HD+ Android Development] PMikeP:
I hope Jon is okay. He hasn't posted since August. (Perhaps there's nothing more to say?)
[Nook HD, HD+ Android Development] twiztid_:
I'd like to think he's just working -REALLY- hard on the new KitKat ROM he mentioned thinking about in his Lollipop thread.
[Nook HD, HD+ Android Development] lavero.burgos:
Is anyone still using this ROM? If so which build?.

I'm looking for a stable BUGS FREE, light and with good WiFi ROM that JUST WORKS.

I've been recommended CM 10.1.3 but I see Jon continued development up to 10.2

Enviado desde mi ghost mediante Tapatalk
[Nook HD, HD+ Android Development] leapinlar:
I used it for a while and it was fast, but crashed on me a few times and reverted back to plain.
[Nook HD, HD+ Android Development] lavero.burgos:
Thanks, I was wondering because I read he made some improvements in the graphics part and someone mentioned it then loaded faster.

Ill definitely install official 10.1.3, but I guess that build doesn't have that improvement.

Just curious. Don't really care of major changes while stock feels snappy, responsive and stays like that after using the tablet for a long time.

Enviado desde mi ghost mediante Tapatalk
[Nook HD, HD+ Android Development] bibikalka:
Jon's 10.1.3 is reasonably decent. A few freezes (crashes) here and there (mostly with Youtube), but otherwise nice and fast!
[Nook HD, HD+ Android Development] Nolfer:
I'm currently using 10.1 from http://xdaforums.com/showthread.php?p=61004989&nocache=1#post61004989

Really snappy and optimized. Crashed a couple of times the first day, but it's smooth and stable now. I think I will keep this as my main HD+ ROM.

Also using dirty_ratio=90, dirty_background_ratio=55, swappiness 60, vfs_cache_pressure=50 (don't want to force the ram too much, as it's only 768MB), overcommit_ratio=50. Currently using aggressive kernel adiutor LMK values and deadline scheduler (the most stable imho) with 2048 readahead. It's snappy and responsive like butter. Should test it with swappiness 0 and report.

I only use it to read pdfs, watch some netflix and browse, and I think it's really fast and smooth. Imho smoother than pinguy's optimized roms (his carbon rom crashed and had problems, and the 4.2.2 became unresponsive as hell) and stock CM roms, even though I still have to try the new L by amaces (not really wanting to dive in right now and become a tester, as I want stability and smoothness).
[Nook HD, HD+ Android Development] twiztid_:
I think amaces' Lollipop builds are (mostly/completely?) discontinued in favor of the Marshmallow builds, which are surprisingly fast as well as stable. I'm personally not a big fan of the AOSP builds, due to a lack of what I consider basic options/features that CM has by default, and haven't really noticed any improvements in AOSP over CM. There are some 'quirks' with the builds however:

Like needing to delete something from the System folder to get even the smallest (Open) GApps package to install (I personally just delete the Bootanimation.zip from /system/media, as I enjoy the simple and sleek looking boot)

Keeping Wifi on prevents the device from entering deep sleep, so it drains the battery considerably faster. You can turn it off in the Wifi options.

And the last one that I've noticed is the most odd... When the screen turns off, sometimes it won't wake from Sleep when you press Power/Home. But if you have the option to turn screen on when the device is plugged in/unplugged, you can wake it that way, but the screen behaves oddly. The problem seems to go away on it's own and doesn't return, I think rebooting and/or wiping cache helps resolve it.

Overall, I think Jon's builds tend to be slightly faster, but I've noticed a bit more instability pop up every now and again. I made the switch from Jon's Yellow kernel to amaces' L/M builds when the majority of the screen flickering (due to pulldown and ducati?) issues were solved. It's come a long way since then, and I'm mostly happy and would recommend the Marshmallow builds for daily use.
[Nook HD, HD+ Android Development] Nolfer:
Yes, sorry, I meant the actual MM builds, not the L ones. I will definitely try them in the future, when these issues are solved.
[Nook HD, HD+ Android Development] Jon Lee:
I believe the benchmark speaks for itself on this one. To give an idea, the Asus Transformer Prime is a quad core.

(Also seems to be running much cooler.)

Flashable kernel:

http://www.mediafire.com/download/4714a0o4zp317tx/ovation-kernel-cm10.1.3_v12.zip

Kernel source:

http://www.mediafire.com/download/dz436froyofdv2z/android_kernel_bn_omap-cm-10.1_v7.tar.gz
[Nook HD, HD+ Android Development] Maromi:
What commits did you use for this update?