yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] pinguy1982:
Over all the kernel is great but I do have 2 issues with it. With the carbon ROM it takes ages for the systemUI to kick in when you first boot the tablet. Also if you let the screen turn off/lock screen happen before the systemUI loads, the screen won't wake back up. This only happens with the first boot. After the tablet is fully booted it works fine.

The other issue is with OK Google. It's really hit and miss with this kernel. I am unsure if you have changed any settings for the mic but it just sucks. OK Google is pretty much unusable with this kernel.

Apart from being a bit slow and getting random reboots I don't have these issues with the default CM kernel.
[Nook HD, HD+ Android Development] Jon Lee:
I believe the microphone and systemUI probs are Carbon specific. I haven't tried OK Google, but it could be an ipv6 net issue.

When I tested Carbon 8mos ago, I had issues mainly with the launcher (or lack thereof..) working properly.

I just recently compiled a Replicant JB rom and all of the apps are compatible with CM 10.1.3...

One of those is Launcher2

http://www.mediafire.com/download/7thq9a8mc97s81q/Launcher2.apk

I'm wondering if it would work on Carbon? May help some.
[Nook HD, HD+ Android Development] pinguy1982:
This is the Launcher I am using. https://play.google.com/store/apps/details?id=com.google.android.launcher

Google Now works fine with default CM kernel (Flashable Zip if you want to try it). But when I flash the yellow kernel onto the same ROM the Mic doesn't work all that great. I tried it a few times flashing back and forth between the kernels and the Mic doesn't work very well in the yellow kernel. I am thinking the sensitive on the Mic might be set to high.
[Nook HD, HD+ Android Development] Jon Lee:
If you install com.skvalex.alsamixer

http://xdaforums.com/showthread.php?t=2294008

it will allow you to adjust the volume of the mic with a gui.
[Nook HD, HD+ Android Development] infra_red_dude:
Jon,

I gave 10.1.3 a try with kernel v23. For my setup, somehow it feels unresponsive. I also have weird issues with touchscreen (that of course, is known in the community and varies according to the device. The app that adjusts this somehow doesn't work for me). I'm not sure if it's the ROM or kernel. CM 10.2.1 with Archdroid optimization (http://xdaforums.com/showthread.php?t=2784304) runs very well on my device including the touchscreen response. The stability on my device is exceptional.

With that story told, I want to experiment with CM 10.2.1 from the above link with your Yellow kernel and F2FS. Before I "destroy" my setup (I want to start fresh and not restore anything in TWRP/TBackup), I'd like to ask if this is something that can be done or do we know that this doesn't work? CM10.2.1 uses kernel 3.0.31 (screenshot attached for other details).

I remember you mentioned some GPU driver modules have to be recompiled for this kernel. Are they packaged with the kernel or ROM? If latter can I just drop them off in to 10.2.1?

Thanks for all your work!
[Nook HD, HD+ Android Development] infra_red_dude:
Ok, tried it out and flashing the kernel failed. It errored out with "set_param". Steps I took:

1) Format /system, /data, /cache as F2FS

2) Flash CM10.2.1 from the link above

3) Tried to flash Yellow kernel

Jon, any pointers on how to proceed? Thanks much!
[Nook HD, HD+ Android Development] Monfro:
sorry i posted in wrong thread
[Nook HD, HD+ Android Development] Jon Lee:
It's not that easy. You would need to split the boot.img to get the cm10.2 ramdisk and use that ramdisk to create a new boot.img with the new kernel. It's easier to just prepare a source build and drop the new kernel source into it. (Also default.prop would need to reflect the change to F2FS, and also the updater flash script in the rom.zip...).
[Nook HD, HD+ Android Development] Jon Lee:
Here. Try this out and let me know how it does. I'm hoping it proves to be more stable than KitKat.

ROM: http://www.mediafire.com/download/z4uky6f6zgkls2i/cm-10.2-20150119-UNOFFICIAL-ovation.zip

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

Source:

https://github.com/storm31/android

https://github.com/CyanogenMod

It's a hybrid filesystem, meaning...

system *must* be ext4

data & cache *MUST* be F2FS
[Nook HD, HD+ Android Development] com35:
Great job.

I installed your new hybrid rom.

It's really fast.

But I had some problem.

I got a error message when I installed this rom and gapps at once.

"Unfortunately, ... has stopped."

I used 'YourZgappsXS-4.3-2013.12.01'

But it worked well when I installed gapps after first setting.

And I fount that external SD memory doesn't work after reboot.

It worked only when I inserted SD card first time.

I tried it as exFAT and also as NTFS.
[Nook HD, HD+ Android Development] Jon Lee:
I've noticed I've had to take my card out and put it back in to get it to read also (or maybe try unmount/mount through settings).

I believe it's one of the vagaries of 10.2's vold, and an attempt to support exfat...

By default only vfat & exfat are included.

ntfs is provided as a kernel module (system/lib/modules), but you would have to insmod and mount by hand.

I have no idea which gapps would be the most compatible.

Also, zram can be enabled through the performance settings interface.
[Nook HD, HD+ Android Development] com35:
Thanks to your reply.

The message was 'Unfortunately Setup Wizard has stopped.'

When I installed rom without gapps it worked well...

But it showed homescreen without any setup wizard.

And I surprised that it has many customizing options.

It has tablet UI transform option too.
[Nook HD, HD+ Android Development] FirePsych:
CM 10.1 is probably 4.2 GAPPS.

That might be one your problems.
[Nook HD, HD+ Android Development] infra_red_dude:
[MENTION=5664601]Jon Lee[/MENTION]

Many thanks for the build! I'll try it out as soon as possible.

[MENTION=6292198]com35[/MENTION]

I've always used mini-modular PAGapps with Jon's builds and they've worked flawlessly. You may want to try that out. Here is the link: https://www.androidfilehost.com/?fid=23189362627840912

[MENTION=4617886]FirePsych[/MENTION]

Jon's unofficial build (linked in his post) is for CM10.2, So I guess that may not be the issue.

Edit: corrected micro/nano PAGapps (4.4.x only) to mini-modular PAGapps (4.3).
[Nook HD, HD+ Android Development] infra_red_dude:
[MENTION=5664601]Jon Lee[/MENTION]

I can confirm the behavior mentioned by [MENTION=6292198]com35[/MENTION]. Wiped everything, converted /data and /cache to F2FS, /system still ext4. Flashed ROM and GApps, Setup Wizard FCs continuously. Wiped again, installed without GApps, booted fine, rebooted and installed Gapps, now they install fine. Tried various 4.3 GApps, all have the same issue with Setup Wizard FCs.

ROM is as fluid as ever, thanks for all your work! :)

Update: I can also confirm that external SD card mount is broken. I've tried fat32 formatted sdcard. From previous comment it appears fat32, ntfs and exfat formatted sdcards cannot be mounted in this build.

Update2: I can manually mount external sdcard via terminal. So it appears the fstab.ovation needs some change in device path/mount points. The commands I used to mount external sd in terminal app:

su
mount -o rw -t vfat /dev/block/mmcblk1p1 /storage/sdcard1

Update3: I notice fstab has reference to /devices/... for both SDCARD1 (external SD) and USB0 (OTG, I believe?) however no such paths exist on ovation. I guess USB storage mount is broken too.

Modifying /fstab.ovation as below somehow does not persist across reboots:

# Comment following lines
#/devices/platform/omap/omap_hsmmc.0/mmchost/mmc1 /storage/sdcard1 vfat defaults voldmanaged=ext_sdcard:auto
#/devices/platform/omap/omap_hsmmc.0/mmchost/mmc1 /storage/sdcard1 exfat defaults voldmanaged=ext_sdcard:auto

#Add following lines
/dev/block/mmcblk1p1 /storage/sdcard1 vfat defaults voldmanaged=ext_sdcard:auto
/dev/block/mmcblk1p1 /storage/sdcard1 exfat defaults voldmanaged=ext_sdcard:auto
# I have no clue what the correct blockID is for USB0/1 storage!

Any pointers on how to fix this? Does this change need to go during ROM compile/build stage?
[Nook HD, HD+ Android Development] Jon Lee:
Just wanted to throw this patch "out there", as I incorporated into the 10.2 build...

http://pastebin.com/VbRRp7N5

It may help provide for USB Headset and FM audio routing.
[Nook HD, HD+ Android Development] Jon Lee:
The fstab would have to be modified in the boot.img ramdisk.

I'm liking this build, so I may work on providing an update for it.

FAT32 mounts for me if I take the card out and re-insert it.

If I were to provide an update, should I build it as user rather than userdebug (odexed + not rooted), like I did with CM11? I'm thinking of sticking with this build for awhile, as it seems stable enough for me....
[Nook HD, HD+ Android Development] Monfro:
I think that 4.3 roms are great, since 4.3 is lighter than KitKat.

I suggest userdebug, since odex files make Roms smoother.

TWRP will then root it.
[Nook HD, HD+ Android Development] PMikeP:
I vote "whichever is most stable." If that means unrooted, do we let TWRP unroot it? And would it come w/ an SU binary? If not, please recommend whose is best.

Looking forward to the update and trying this f2fs build.
[Nook HD, HD+ Android Development] infra_red_dude:
Thanks Jon! I vote for "user", I can give it a try like a test-run for you if you like. Don't odex files only help in the first boot and then as time elapses, odex and deodex are all same as Dalvik gets to work? Also for user builds, TWRP will root it for you. If this doesn't work well, we can always go back to userdebug!

This build has been very stable (at least for me) and deserves its own thread :)

Edit: Multi-user seems to suffer for the Gapps Force Close issue as well, even after everything works for primary user.
[Nook HD, HD+ Android Development] Jon Lee:
Here's the update.

fstab should work & odexed, otherwise the same as the last.

ROM: http://www.mediafire.com/download/28corcs81kvhkvd/cm-10.2-20150123-UNOFFICIAL-ovation.zip

MD5: http://www.mediafire.com/download/5s59cuyzfz16y2m/cm-10.2-20150123-UNOFFICIAL-ovation.zip.md5sum

I won't be on the interwebs for awhile, but I will try and check in once in a blue moon.

Oh. If NTFS is needed, a small shell script could be added to /system/etc/init.d to insmod it.

Filesystem is "auto", so it should handle it.

All the pieces are in place to experiment with FM radio/transmitter. I've had difficulties compiling FM TX, but when I have the time, I will work on that some more.
[Nook HD, HD+ Android Development] com35:
Thank you, Jon.

I installed your updated rom.

My external memory problem was fixed.

exFAT SD card works very well.
[Nook HD, HD+ Android Development] PMikeP:
Solved: Can't get my Bluetooth GPS app to install

First the good news: I downgraded from your LS f2fs to this hybrid ROM. It benchmarks 50 AnTuTu points higher. (There's some small shifting of the display during the 2D test, but nothing bad.) All the features I got used to with LS seem to be here.

Update: Fixed. Needed to install GAPPS 4.3 Too bad. That's 48 more apps, even with the modular-mini version of GAPPS.

Unfortunately, my Bluetooth GPS tethering app won't install anymore. I don't know why. (I have unverified sources set.)

Edit: Tried Titanium. No joy. But the problem could be that I haven't installed GAPPS with with ROM. I was hoping to avoid that. But it might be that GAPPS location services are needed for my Bluetooth GPS app.

I'm gonna go back to LS, backup the .apk with Titanium and see if that will force an install.

P.S. At my age, when I say I won't be on the interwebs for a while, it usually means "hospital." If that's the case, hope all is well. I think I speak for everyone in the forum when I say you'll be missed.
[Nook HD, HD+ Android Development] Monfro:
Great work!!

This CM10.2 Hybrid ROM is working really well here!!

No bugs and great performance!!
[Nook HD, HD+ Android Development] infra_red_dude:
Has been the best Nook HD+ build ever for me! No lag, no issues, extreme stability and exceptional battery life. Thanks for this wonderful ROM and all the hard work :)

PS: I still think this ROM deserves its own thread...
[Nook HD, HD+ Android Development] PMikeP:
Total wipe?

Okay, I know this is a real noob question and that the answer is already here, buried in the forums. But I want to do a total wipe of my HD+ and install Jon's CM10.2 hybrid ROM as if new.

That's because I'm having a problem getting my favorite battery monitor to install in CM10.2. (The error is "There was a problem parsing the package.") I've redownloaded it and I've tried restoring from backup. No joy. So I don't think it's a corrupt file. More like either an incompatibility or leftover junk from my LS f2fs days blocking the new install.

I noticed that there are old files from old applications in my sdcard0/data directory and I thought it might be time to clear everything out and start completely fresh.

But I recall that a person can hose their system if they wipe/format the wrong partition. And, IIRC, the HD+'s nomenclature about sdcard is different than standard?

So, in TWRP,, to do a complete wipe after Advanced Wipe and /system wipe, is it

wipe SD Card?

wipe Internal Storage?

wipe both?

(I presume that wipe SD Card is not referring to my external micro-SD?)

IIRC, the separate button for "Format Data" is a no-no? (Requires some kind of rebuild of the structures in /data if you do?)

I'd appreciate hearing from someone who's actually done a complete and total wipe. Again, sorry for such a noob question. Just want to make sure I don't brick myself.

---------- Post added at 05:20 AM ---------- Previous post was at 05:17 AM ----------

You're probably right. But ironically, since it's turning out to be such a trouble-free ROM, what would we post about in a new thread? :)
[Nook HD, HD+ Android Development] infra_red_dude:
[MENTION=5348266]PMikeP[/MENTION]

I've done a complete wipe and here is the procedure I followed. Enter TWRP > Wipe > Advanced Wipe menu. Check Dalvik Cache, System, Data, Cache and Swipe to wipe.

If you want to change the file system of /data and /cache partitions to F2FS then follow on, else skip this paragraph. Select both of them (ensure ONLY these are selected, no other partition is supported). Then select Repair or Change file System option > Change File System > F2FS.

You can also wipe Internal Storage (this is sdcard0 that is EMMC), and SD Card (this is your external microSD, sdcard1) to start with a "virgin" system. Just ensure you have backups of your data.

As for new thread, I think a lot of people might be missing on this excellent ROM due to 10.1.3 title.
[Nook HD, HD+ Android Development] PMikeP:
Thanks for the quick reply!

The TWRP team should make it clear that SD Card is "Ext SD card." After posting my question, I found some horror stories where people unknowingly wiped their ext card and found themselves without zips to flash.

And I'm confused as to why they have a separate button to "Format Data" on the main page, but then a choice to wipe /data in the Advanced menu. (Presumably they do the same thing, since they wipe by format.)

Well, I'll go copy my downloads to my computer and do a full wipe. (Am already f2fs on /data and /cache from Jon's LiquidSmooth f2fs.)

Good point on needing a new thread to broadcast the availability of this new ROM.

I'll report back on my (hopeful) success.

Update: After squeeky clean install. Camera app didn't install itself this time. Unfortunately my GSam battery app still won't install. Solved. I found a previous version (3.12) which installs okay.

Nice to have a fresh start.
[Nook HD, HD+ Android Development] wellersl:
This ROM didn't work for me for several reasons. So I went to the OP and downloaded that ROM. I don't know how I missed it before because I *SWEAR* I've tried them all. I was reaching the point of total disgust with my HD+. Now I'm a happy camper! Not one crash. By now, the stock browser would have almost driven me nuts. Chrome would have just closed inexplicably without any message at all.

Until now, I thought the HD+ crashed regularly as a pheechur.

NOT ONE CRASH! It doesn't *feel* as zippy at 1600MHz as it did at 1500MHz - but NOT ONE CRASH! I turn off all the animations and I run the Performance governor. Those measures seem to make the lack of touch response more acceptable. Is there any benefit from using the NookTouchscreenSensitivityAdjuster-4.apk? I have it installed but there doesn't seem to be any improvement.

Thanks, Jon Lee! You're my newest hero.
[Nook HD, HD+ Android Development] PMikeP:
He doesn't update his Initial Post like most developers do. So you have to read (or better, read backwards) through the forum thread to find the latest. (Still, fascinating reading.) He stopped at v23 for what you're using. AFAIK, it does not require f2fs, but supports it.
[Nook HD, HD+ Android Development] wellersl:
Thanks. I'll backup what I have and try it.
[Nook HD, HD+ Android Development] kokercey:
After two years of fun with just about all the custom roms made for ovation i think i have settled on this one. It has been up since the Jan. 24 without problems. Getting it installed and running took more work than i expected, only because i did not take note of Jon's post #136

"It's a hybrid filesystem, meaning...

system *must* be ext4

data & cache *MUST* be F2FS "

using the latest rom from post #148 I first installed with everything ext4, it loaded okay but would revert to set-up on a re-boot. After re-reading the complete thread i found my error and after reformatting data and cache to F2FS all went well. I have found that my HD+ works best with the cpu capped at 1500.
[Nook HD, HD+ Android Development] PMikeP:
I'm curious. What does "best" mean? Faster? (As sometimes happens on OC'd PC's when clock dividers don't sync.)

I'm trying 1500 now but I don't notice a difference. What should I be looking for?
[Nook HD, HD+ Android Development] kokercey:
Well it is only a subjective observation about my device. With all kernels i have tried that have been overclocked, under heavy use - multiple apps open ( photo app, browser with mult. tabs, email writing and google earth) i have had long hesitations switching between apps and FC's when over clocking. Changing to 1500 max and running the same group of programs i have had no FC's and smoother switching between apps. So now with any oc kernel i automatically limit cpu to 1500. Under lite use i've had no known problems with running at higher clock rates. This is only observed behavior and only for my device and as we know not all HD+'s will react the same.
[Nook HD, HD+ Android Development] FirePsych:
Feeling like a noob here.

I have TWRP 2.7.1.0 and when I go to repair, only EXT 2, 3 5, FAT and exFAT are options.

Do I need a newer version of TWRP or the one from post #95 or am I missing a step?
[Nook HD, HD+ Android Development] FirePsych:
Edit: flashed TWRP from post #95 and everything is great.
[Nook HD, HD+ Android Development] FirePsych:
BT causes Settings to FC. I flashed 4.3 modular mini PA GAPPS. I didn't see anything else in this thread. Any ideas?
[Nook HD, HD+ Android Development] PMikeP:
No problem w/ BT here. Try reflashing the ROM over what you've got.
[Nook HD, HD+ Android Development] FirePsych:
Nice idea, tried it. wiped dalvik and cache. No difference. Click on BT in settings or through Quick Settings and Settings FCs
[Nook HD, HD+ Android Development] PMikeP:
Sorry to hear that. I've been enabling BT from both QS tile and in Settings. Works normally on mine. (I.e., no FC of Settings.)

I did a full wipe (/data and internal) before I installed this ROM. (I wonder where BT pairing info is stored? Wipe that?)

Although I installed GAPPS, I disabled Play, Services & Frameworks and I never let them update.

Perhaps the next step would be to do a full wipe, install the ROM only and see if BT works. If yes, would indicate that GAPPS is causing a problem.
[Nook HD, HD+ Android Development] PMikeP:
my first forced reboot

After about 4 days of heavy web surfing, alternting between 4 different browsers, I finally had to reboot CM 10.2. The problem was that the touch was always on the center of the screen. (I have Show Touches enabled.)
[Nook HD, HD+ Android Development] wellersl:
Hmm...

That's something I need to keep an eye on. My HD+ has always had a touchy touchscreen. It does seem to be worse with this ROM even with the NookTouchscreenSensitivityAdjuster-4.apk (which doesn't seem to do anything for me). Otherwise, I really like the stability of this ROM. Even the crappy stock browser doesn't crash. I may have to go back to a 10.2 ROM...

EDIT: Yup. My touchscreen is definitely touching itself. Damn.
[Nook HD, HD+ Android Development] PMikeP:
Sorry to hear that. I get an occasional ghost touch using Jon's CM 10.2.1 Yellow Kernel, but not nearly as bad as it was with his LS f2fs build.
[Nook HD, HD+ Android Development] wellersl:
If it weren't so aggravating, it would almost be amusing. It goes through three of four phantom touches before it gives up.
[Nook HD, HD+ Android Development] PMikeP:
Could it be an abundace of alpha particles, living at Los Alamos? (I'm half serious.)

Next time I fly there, I'll let you know if my HD+ goes nuts.
[Nook HD, HD+ Android Development] Jon Lee:
I made some changes to the kernel touchscreen driver. Dunno if it will help or not.

Rom: http://www.mediafire.com/download/m4qpd8noj4lgyn5/cm-10.2-20150206-UNOFFICIAL-ovation.zip

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

Kernel source: http://www.mediafire.com/download/z16lyziq05w55id/kernel.tar.gz
[Nook HD, HD+ Android Development] PMikeP:
Trying it now. Fly tomorrow.
[Nook HD, HD+ Android Development] wellersl:
I'm on it now, thanks. I'll give it 24 hours or so...
[Nook HD, HD+ Android Development] PMikeP:
I just installed Jon's 20150206 ROM over my previous version. Bluetooth stopped working. Won't turn on or gives me a FC on Settings.

Had to restore previous version. BT working now..
[Nook HD, HD+ Android Development] FirePsych:
The problem I was having seems to have fixed itself. BT worked fine yesterday.

I haven't flashed the latest build.
[Nook HD, HD+ Android Development] Jon Lee:
Yes, Bluetooth is broken in that last build (unintended consequence of playing with TI FM tools). Will try and post a fixed build by mid to end of the week. Technically, the boot.img could be exchanged out to one of the earlier builds (without a md5 sum).
[Nook HD, HD+ Android Development] Jon Lee:
ROM: http://www.mediafire.com/download/ymdr9fkt82jc6cx/cm-10.2-20150210-UNOFFICIAL-ovation.zip

MD5: http://www.mediafire.com/download/6d9vynpcfojcy5y/cm-10.2-20150210-UNOFFICIAL-ovation.zip.md5sum

It does have at least two bugs that I'm aware of.

1) If you select the bluetooth menu item before turning bluetooth on, settings crashes. (I flashed the original, and it also displayed the same behavior). I spent several days looking into this without finding a solution.

2) If you turn notifications off in the notifications panel and reboot, systemui will crash upon boot. (took me awhile to figure this one out)

Other than that, it's my opinion this is the best out there. SGT7 was a mainstay of the old skool kindle fire roms.

Oh. Touchscreen still isn't 100%, but it is very much improved. I don't believe it will be much of an issue (and should still be better than any other rom). FWIW.
[Huawei Ascend P6, Mate] RicardoA:
Hi,

this is a screenshoot i take when i had stock rom:

P6-U06V100R001C00B606

I think its B606 right?

How can i get that stock ROM?

Many thanks!
[Huawei Ascend P6, Mate] ZuperStyler:
I think that's a Vodafone firmware, they released B606 and B607, anyway, it's an old firmware, you better update to B132

Download LINK -> B132 Official Firmware
[Huawei Ascend P6, Mate] kabirjedi:
Offical voadfone rom here:(B610 lastest)

http://www.huaweidevice.ro/support-software/