yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] webman2k:
Graphics hiccups issues?

Hello All,

I'd like to first thank Verygreen and the devs for supporting this tablet, and providing such great ROMs and support. I was running CM 10.1.3 stable, and everything was smooth, stable and working fine. I'm running on an 8gig Nook HD - cwm and emmc install.

I did a flash upgrade to the new CM11 presented here (at the time, the Jan 9th version). The upgrade worked without a hitch, but I had some issues with some programs that just felt like OS upgrade issues. So, I did a wipe and fresh install of Verygreen's CM11. Everything works without issue, and the OS operates smooth, meaning things open fast, and the system is very responsive. Easily faster than CM 10.1 in every respect.

However, I'm noticing a global sporadic graphics issue. Hard to explain, but it's a kind of delay that you'd see playing an online game with a little latency. That is, the entire experience is fast and fluid, but with a hiccup every few seconds which causes the animation to pause for a split second and then catch up to where it was supposed to be. I say global because I see this everywhere - scrolling, gaming, playing videos - even the android transition animations. This wasn't there before in 10.1. All of the games and animations ran smoothly without hiccups.

Any ideas?
[Nook HD, HD+ Android Development] LucaToo:
CarbonROM

Thanks for the hard work.

Can I 'upgrade' from an old 10.1 version of CarbonROM - or will I need to wipe evrything and install fresh..?
[Nook HD, HD+ Android Development] tebra:
Hi, you can try to upgrade just by flash over your cm10.1.

I try that but have some bug.

So it's better to make a clean install by wipe data.

You can first make a titanium backup of your apps and restore after cm11 installation

Envoyé de mon BN NookHD+ en utilisant Tapatalk
[Nook HD, HD+ Android Development] episode96:
Yep, I'm having this issue as well. I flashed over CM 10.2. Apart from that, everything seems OK so far.

As always, thanks to Verygreen and the devs for their great work.
[Nook HD, HD+ Android Development] bpaulien:
Quick question. I'm running this on emmc and have had no problems (after the upgrade of the 9th which let me read and write to the SDcard) but I did notice that when I flashed the new ROM and booted back into system, it did the whole "upgrading apps" thing for a few minutes. Is this normal? I have not done a lot of flashing ROMs lately, because I was previously running the SlimBean ROM which wasn't supported so didn't have any updates. Anyway, I thought that would happen when you cleared cache/Dalvik cache, but I didn't do that this time.

If it matters, I have it set to the ART instead of Dalvik, but I don't know how to that has anything to do with it or not.

Basically, my question is, 'is that expected behavior when flashing a upgrade to a ROM? '
[Nook HD, HD+ Android Development] blazingwolf:
In my experience that is the expected behavior. :)
[Nook HD, HD+ Android Development] polymath257:
Is there a manifest or github link for those of us who want to build this ourselves?
[Nook HD, HD+ Android Development] verygreen:
Follow the usual cm11 procedure:

repo init for cm-11.0 branch followed by bruch for either ovation or hummingbird.
[Nook HD, HD+ Android Development] Chomanator:
I'm having the same problem with this ROM as I am succulents ROM.

When I install the app "Line free calls and texts" the app launches and crashes on startup. It will allow me to login after but will not allow me to verify a phone number. Logcat and debug reports show that my device id is null and this is forcing crashes.

Other issues I've been experiencing, the screen will lose all touch response forcing me to lock and unlock it or restart entirely. Also, I am unable to change my default SMS app as the option seems to be missing. Voice+ will not use hangouts.

Otherwise this ROM runs great. I've turned all animation scaling off and it is very smooth for me. Good work. ;)
[Nook HD, HD+ Android Development] laofan:
I guess because nook does not have the cell function built in. It is a tablet, not a phone.
[Nook HD, HD+ Android Development] Chomanator:
Except this problem doesn't exist in CM10.2 builds from any dev. I've only seen it in the KK builds.
[Nook HD, HD+ Android Development] jpisini:
Does the HDMI out work on 11? I was thinking of upgrading this weekend but I do need that.
[Nook HD, HD+ Android Development] laofan:
that is wired. you could sent an logcat to verygreen or post it here so that others could help. Maybe do a full wipe and try install again.

For sceen lost touch response, I experience that both in cm11 and cm10.2. Sometimes you just need to turn off screen and turn it back on again, it would fix that.

Now I go back to cm10.2 for stability and responsiveness. I could not try voice+ for you.

Could anyone just try voice+ and Line free calls and texts in cm11 for Chomanator?
[Nook HD, HD+ Android Development] tebra:
I find another small bug. Lock rotation quick panel don't works. But it may be a CyanogenMod ROM bug.

Envoyé de mon Xperia S en utilisant Tapatalk
[Nook HD, HD+ Android Development] mr72:
Maybe it is Google plus. ?
[Nook HD, HD+ Android Development] Armadillo123:
What's the latest build that doesn't have an issue with the soft/hard HOME buttons not working?
[Nook HD, HD+ Android Development] snoozer854:
Sometimes it will do it just by pulling down the notification window.

Seems to be an issue others are having.

At times it is more of a annoyance, but hoping it gets fixed soon

---------- Post added at 01:12 PM ---------- Previous post was at 01:10 PM ----------

I am running the latest build on my Nook HD and am not having any issues with Home button, just the notification issue.

Sorry can't help you
[Nook HD, HD+ Android Development] sz0pf1:
I have the 327 nightly. It has been very solid. I've have virtually no problems with it. Every thing seems to work including ART. PM me and I will send it to you.
[Nook HD, HD+ Android Development] snoozer854:
Thanks I sent you a pm
[Nook HD, HD+ Android Development] Odenknight:
Two different HD+'s, same CM11, different performance

Question to all of those who may have experienced this:

My friends have seen my HD+ running CM11 nightlies, and bought their own for me to set up for them. I figured that it would be a good time to wipe mine and load the same nightly (2014-05-04) so we all can be on the same build with a fresh install.

There are three HD+'s total. One is mine (purchased 11 months ago) and the other two have been purchased last week and today.

I wiped everything using v6 of the ovation CWM recovery via SD card, then installed recovery, rebooted, then installed 2014-05-04, then gapps kitkat, then rebooted. The other two literally zoomed by on boot times and app installations, while mine was moving at a decent pace. I enabled the Performance menu, set the minimum clock speed to 800MHz, kept the cache as Dalvik, and rebooted.

The performance difference between the two new ones vs my old one is very noticeable. The newer ones are very responsive, no lag time between menu transitions, and the same apps install and open much faster.

Is there anything I can do to improve the response time of my old HD+, or at least identify why this is noticeably slower than the two recently purchased ones?

Thank you.
[Nook HD, HD+ Android Development] leapinlar:
Probably due to lag from being used so much. You should be able to get it going faster by doing trim, but be careful if you have the chip that is vulnerable to bricking with trim. There is a whole thread on trim and lag for the HD+. Look here:

http://xdaforums.com/showthread.php?t=2528009
[Nook HD, HD+ Android Development] Odenknight:
Thank you for the swift response. My understanding was that CM11 had trim enabled by default. Is this not the case?
[Nook HD, HD+ Android Development] brandonhun:
Will we get an M6 build?
[Nook HD, HD+ Android Development] leapinlar:
That is supposed to be true, but might not be working for you. Try it manually.
[Nook HD, HD+ Android Development] Odenknight:
Thank you. I did, and rebooted. I'll monitor its performance over the next few days.
[Nook HD, HD+ Android Development] digixmax:
The M Snapshot builds now supplant the RC/Stable releases, beginning with M6:

http://www.cyanogenmod.org/blog/cyanogenmod-11-0-m6-release

Hope the HD+ will get an M6 build.
[Nook HD, HD+ Android Development] extrem0:
M6 for HD+ is released: https://download.cyanogenmod.org/?device=ovation

or for HD: https://download.cyanogenmod.org/?device=hummingbird
[Nook HD, HD+ Android Development] mr72:
Is it OK to flash the M6 over one of last week's nightlies?
[Nook HD, HD+ Android Development] Darrian:
Running M6 now. A breath of fresh air. I'm so happy to no longer have random force closes for apps that shouldn't even be running at startup and to be able to open my notification tray without systemui crashing. I may just end up sticking to stable releases only at this point.

Update: I spoke too soon. I just had my first systemui crash when pullling down the notification drawer. I guess I will be updating to the first nightly that the bug is verified fixed in.

---------- Post added at 07:42 AM ---------- Previous post was at 07:38 AM ----------

Hypothetically, but you may end up in a boot loop after installing it. I highly recommend a fresh install, backing up your apps with titanium backup and then restoring them afterwards. However, if you want to try the quick and dirty first I would caution you to make a nandroid backup before you install it.
[Nook HD, HD+ Android Development] McGiles:
M4 to M6

I have had a very good experience with M4 on my HD+ and want to keep it that way. What should be the procedure for moving to M6 (which I just put in HD+ memory). Just being careful.
[Nook HD, HD+ Android Development] mr72:
I guess what I am looking for is this: is there a KNOWN incompatibility between last week's nightlies and the M6 as there was with M4, where flashing it over a recent nightly was a recipe for disaster.

I am not going to do a "clean" update. Too much work. I'll just wait for the Mx build that is late enough to flash over the nightly I am running now. FWIW it is very stable and works great for me. I just want to put something on that is more long-term.
[Nook HD, HD+ Android Development] razholio:
M6 so far

I haven't done much, but wanted to use adb to shell in and change the dpi in build.prop. The first problem I see is that adb does not see the device. My workstation sees it attach, and recognizes it as a MTP or PTP device, but no matter which way I configure it, adb will not see it as an adb device. I've not yet had this trouble with any ovation build from 10.1 -> 10.2 -> 11.0.
[Nook HD, HD+ Android Development] manojm:
Upgrding to M6

Just upgraded to M6 from CM11 Nightly. Flashed it after wiping cache, etc. So far working fine! Will post if it gives any trouble.
[Nook HD, HD+ Android Development] tebra:
WiiMote

Hi [MENTION=3654172]verygreen[/MENTION]

WiiMote can now be BT paired with last CM11 nightly. But to works, the kernel needs to have the following option:

CONFIG_HIDRAW=y

CONFIG_HID_WIIMOTE=y

See here http://review.cyanogenmod.org/#/c/63293/

Is it the case for your hummingbird and ovation kernels?

Thanks
[Nook HD, HD+ Android Development] lostnick:
Hi [MENTION=3654172]verygreen[/MENTION]

Would You please add android.hardware.bluetooth_le.xml to /system/etc/permissions and replace old wl1271l bt firmware TIInit_7.6.15.bts with newer version from github.com /TI-ECS/bt-firmware/blob/master/TIInit_7.6.15.bts ?

With this tweaks HD+ can successfully connect to SensorTag ($25 Bluetooth Low Energy device from TI with many sensors) and can receive data from sensors.

PS. I don't know is this modifications are enough or not. Maybe ovation needed something like

#define BLE_INCLUDED TRUE

#define BTA_GATT_INCLUDED TRUE

#define SMP_INCLUDED TRUE

in bdroid_buildcfg.h and other modifications.
[Nook HD, HD+ Android Development] razholio:
have you had any trouble with adb?
[Nook HD, HD+ Android Development] mr72:
BTW I've had all kinds of trouble with ADB on JB and later with all of my devices, regardless of build or hardware. I have never gotten ADB to work on CM11. It's a config thing but I just haven't sorted it out, wind up spending half an hour with it and give up because I have better things to do. Point is, maybe it's not the M6's fault.

---------- Post added at 10:05 PM ---------- Previous post was at 10:04 PM ----------

FWIW I flashed M6 over a 4/28 or so build and it works fine. Just cleared cache and dalvik, no data wipe required.
[Nook HD, HD+ Android Development] digixmax:
To get around the USB driver config hassle entailed in ADB access over USB, you might want to consider ADB access over WiFi using an adbWireless app/widget and enabling "Developer Options->Debugging->ADB over Network".
[Nook HD, HD+ Android Development] naveed.hasan:
+1

It resolves my old enhancement request on JIRA

https://jira.cyanogenmod.org/browse/CYAN-2494
[Nook HD, HD+ Android Development] naveed.hasan:
These do not appear necessary, as I have tested CM11 nightly with only the addition of permissions and an update firmware file and BLE works just fine with no further changes needed.

Thank you!
[Nook HD, HD+ Android Development] huntz:
I have just restored my M4 nandroid backup on HD+.

The notification drawer bug is still present on M6.
[Nook HD, HD+ Android Development] snoozer854:
Wish they would figure this out.

I did find a backup that I had from March 18th build, so restored it & will continue waiting to see if the Notification Drawer Bug gets exterminated.
[Nook HD, HD+ Android Development] rhyang:
I noted this on a different device forum -

http://review.cyanogenmod.org/#/c/63034/

Sounds like a similar culprit, still being worked on.
[Nook HD, HD+ Android Development] mr72:
so FWIW, I tried the M6 for a day or two and it had terrific battery life but was very laggy, so I restored the backup of about a 4/28 nightly. BTW fstrim fails on my HD+ according to the LagFix app. Weird.

I wonder why there is so much difference in performance between the M6 and the nightlies.
[Nook HD, HD+ Android Development] LucaToo:
I have had completely the reverse.

Had horrendous problems since about mid-April nightlies having to completely restore Nook a couple of times as problems reoccured moving back through the nightlies.

Have now gone back to Unofficial 18/01 and then forward through M4 and on to M6 and working better/faster than it has for weeks.

I enable full screen and rarely pull down notifications to know whether that bug exists - but only ocassionally experience a freeze or re-boot (normally associated with a couple of 'problem' apps - Kindle being one of them).

I had previously been updating nightlies once or twice a week but now intend to ignore nightlies and stick with M releases.
[Nook HD, HD+ Android Development] Bossk128:
It's your choice, but that means any free support from this forum will be difficult as there will be lots of reasons it might fail.

So many support replies seem to start with 'Do a clean install'.
[Nook HD, HD+ Android Development] mr72:
This is not my first rodeo.

Those "support" responses are deferral in place of actual troubleshooting. Filters out a lot of requests when you introduce a really painful barrier to continuing the line of questions.

And BTW, there really is no official support for this particular line of builds, at least not on this forum. We are basically a bunch of pre-beta users who report "issues" that get virtually no attention from the devs. It's not as if they don't have their hands full with bugs they know about. Once it gets around to being "stable" or even an RC build, then maybe.

---------- Post added at 04:57 PM ---------- Previous post was at 04:53 PM ----------

That's the thing. I have absolutely no problems with my nightlies. They work great.

I am quite confident most of the problems people are having are highly app-dependent, or at the very least usage-dependent. In this case I am sure there are some builds which will be more stable than others if you are in the user profile that uses the particular apps or features that expose issues.

I was not talking about stability, just SPEED. The M6 was perfectly stable as far as I could tell. But it took forever to load an app or switch an app or for an app to acquire the network resources it needed to work, etc.

Well, I do have one "problem", consistent across all of the builds including the M6, and that is with the charger attached, there is intermittent screen flicker (on-off-on). It's annoying enough that I don't use the tablet with the charger cable connected.
[Nook HD, HD+ Android Development] Bossk128:
Steady Eddie, just making a comment. If this isn't your first rodeo then you'll know from experience my comment was correct.

It sounds like you probably will be able to solve a lot potential issues yourself, especially if this in't your first rodeo, and therefore it's not an issue.

I see a lot of questions/complaints from people admitting they have taken the easy but buggy route, and getting annoyed that it's quicker to wipe and start again than to bugfix and troubleshoot. Just trying to help, and keep the thread decluttered to make it easier to see real issues.
[Nook HD, HD+ Android Development] manojm:
I have not experienced any serious problems yet. I have limited my use of the nook HD+ to web surfing, email, videos, etc.
[Nook HD, HD+ Android Development] LucaToo:
In fact so was I.

M6 has brought back the speed of loading apps etc that I had been missing for some time. They just zip to life.

The charger problem has persisted AFAIK since the initial KitKat builds. Sometimes I can use the Nook fine while on charge other times the flickering makes it too much of a pain to use.
[Nook HD, HD+ Android Development] tebra:
I think the flickering during charge is linked to the kernel of HD+.

Because I have a new HD from 1 month now and never had the flickering bug with CM11 nightly.
[Nook HD, HD+ Android Development] rhyang:
I also saw the flickering while charging. Switched the battery display to Icon portrait instead of Percent (Interface > Status bar), which seems to help.
[Nook HD, HD+ Android Development] razholio:
not sure if adb is included in 'etc', so just to be clear, have you been able to use adb with M6 on your HD+?
[Nook HD, HD+ Android Development] manojm:
Sorry I should have been more clear. I did not use adb as I am a beginner in Android OS (was good at Windows, LOL). M6 does appear to be faster and no more problems than with my 4-22 nightly.
[Nook HD, HD+ Android Development] rholm:
I tried M6 for a while, but was experiencing times when many programs/services were being killed - LMT. Back on 03/27/2014, but it has an bug where I get a hot boot if I share from an app to evernote.

Thinking about doing some debugging. Do I need to build my own install,

Cheers,

Rich
[Nook HD, HD+ Android Development] gale2000:
I have not been able to use adb with M6.
[Nook HD, HD+ Android Development] LucaToo:
Same problem - LMT randomly killed - but it seems less so on M6 than previously. Some days LMT runs fine all day - others it turns off repeatedly. Doesn't seem to be related to any apps that I am consciously using.
[Nook HD, HD+ Android Development] digixmax:
ADB over WiFi (using an adbWireless app/widget and enabling "Developer Options->Debugging->ADB over Network") works on M6.

However I am not able to get ADB over USB to work (after adding VID/PID entry for HD+ to android_winusb.inf in C:\Program Files\Android\android-sdk\extras\google\usb_driver).
[Nook HD, HD+ Android Development] rholm:
On 03/27/2014 nightly, it never happens. I'm back on that release, but will try a new nightly soon. Hopefully, after the status bar is fixed.

Cheers,

Rich
[Nook HD, HD+ Android Development] agantai:
guys where can i find the latest minimal GApps for kitkat ? the one i have is old ((3-22_GApps_Minimal_4.4.2_signed)).

thanks
[Nook HD, HD+ Android Development] TheDannemand:
I use PA Gapps which can be found in the thread linked below. Comes in many different sizes. TKruzze does an amazing job with them.

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

I personally always make a semi-clean install when I update Gapps: Wipe system and bootdata, then flash ROM and Gapps. Most of the problems I read about here, I've never experienced or been able to reproduce. I use ART.
[Nook HD, HD+ Android Development] agantai:
i already have this link,the minimal i currently use is only 20mb but the mini on this link is 131mb. i guess i will just use the 131mb instead.thanks anyway
[Nook HD, HD+ Android Development] TheDannemand:
I use the Mini Modular which fits in the system partition on HD+ with CM11. Saves internal storage to have apps like Maps and YouTube in system which I would otherwise download from Play Store.
[Nook HD, HD+ Android Development] Odenknight:
Anyone having issues w/ the 2014-05-09 nightly? Getting infinite bootloops on two devices, even after re-applying the same nightly in CWM.

For those that may run into this issue, and the device doesn't automatically boot into CWM:

Power down device

Hold down the Power button and the "n" home screen button until you see the "nook" logo, then let go.

CWM should load, and install any previous nightly prior to 2014-05-09. (look for the cmupdater folder)

I am back and operational on mine and my friends' devices.
[Nook HD, HD+ Android Development] old_fart:
same for me.

.

but then i get "Unfortunately, Android Keyboard (AOSP) has stopped."

.

and then i'm hosed... up **** creek without a paddle... :(

. update, format system to get over the kybd glitch.
[Nook HD, HD+ Android Development] Odenknight:
I had something similar happen to me when I ignorantly used one of the M-builds. Did you try to re-flash a previous nightly? If that didn't work, maybe download another keyboard (kii keyboard is my new favorite)?
[Nook HD, HD+ Android Development] stevetrooper:
Same for me. I tried the 5/10 nightly and same problem.
[Nook HD, HD+ Android Development] developerbuzz:
Yep, same for me too. Both 5/9 and 5/10 are causing bootloops. Had to flash 5/8 to get it to boot again.
[Nook HD, HD+ Android Development] dbrickg:
Likewise, 20140510 bootloops. I thought it might be due to ART, so restored to backup, switched to Dalvik, reinstalled 20140510, still bootlooping. Guess I'll go try the 20140508. Good to know I'm not the only one.
[Nook HD, HD+ Android Development] keyodi:
You can copy the boot.img from the 0508 nightly into 0510 to get it to boot or you can wait for tonight's build which has the fix merged: http://review.cyanogenmod.org/#/c/63724/
[Nook HD, HD+ Android Development] riche1:
I had bootloops too. I thought I bricked my Nook, but I went back to the snapshot M6 I had and all is well. I'm a little nervous to flash after that! So the bootloops are fixed now with 5/10 ?
[Nook HD, HD+ Android Development] vinceweis:
No, it is expected to be fixed in 5/11.
[Nook HD, HD+ Android Development] vinceweis:
5/11 boots fine.
[Nook HD, HD+ Android Development] jck_w:
Do location settings work?
[Nook HD, HD+ Android Development] Blenky:
No. And the notification pull down bug is still there.
[Nook HD, HD+ Android Development] jbbandos:
The notification bug is present on the i9305. Until I saw it I thought it was nook specific, but apparently it affects more devices!
[Nook HD, HD+ Android Development] dougsdir:
Does anyone get this when the battery runs out and you start to charge?

{see attachment}

After a few seconds of the charging being plugged in you get the cyanoboot logo then this.

the tablet never gets passed this so i have to hold down the power button to switch it off, unplug the charger and plug it back in and then it normally boots.

Ive noticed it doesn't charge properly either when it is stuck booting at this screen as its been like this overnight with th echarger in and when ive finally managed to get it to boot its saying the battery is only 2 or 3%

But when i get it to boot normally it charges fine.

Bit of a pain as the kids use the tablet a lot and then cant get it to work again after it runs out of battery