yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] swaaye:
[MENTION=4473900]amaces[/MENTION]

I've noticed something maybe related to the VPN issue. There are Time Warner Cable public access points for their customers called Passpoints that use 802.1x EAP. My phone will connect but the Nook will not. It can not get an IP for some reason. It reminds me of the VPN problem because again the connection is established but communication then stops. Maybe an encryption problem? OpenSSL?
[Nook HD, HD+ Android Development] TBueno:
I pretty much followed this tutorial and TWRP wouldn't prompt me to reinstate SU after all things flashed (even tried a couple of button-forced "recovery reboots"). So I rebooted to system, waited for it to rebuild cache and start, then rebooted back to TWRP and flashed SuperSU-2.46.zip, but apps requiring root would just hang until android asked to shut them down.

I rebooted the tablet thinking I'd hit the same wall as before, but this time root permission dialogs started to pop magically :o. I guess wiping /system did the trick since I'd rebooted more than once on my previous attempt. So for anyone having trouble rooting 0921: don't give up!

Everything is running smooth as expected under ovation-0921. "Interf sist" only crashes systemUI when I press it soon enough after a reboot, probably before things finish to load. It might've been the same in previous builds and I just didn't notice it. Power off and TWRP 2.8.7.4 "reboot recovery" don't work, but they didn't before.

Once again I must express my gratitude to our considerate and tenacious developer: thanks a lot AMaces!

[Edit] power off works after root is consolidated, maybe using SuperSU instead of built-il SU was the key since the beginning
[Nook HD, HD+ Android Development] pastordl:
9/23 rom

Running great. Smooth, fast and cool. Netflix runs fine as do all other video apps and types I tried. Tremendous work [MENTION=4473900]amaces[/MENTION].
[Nook HD, HD+ Android Development] js290:
Sideloaded the SuperSU zip file. Could not get TWRP 2.8.7.4 to bring up the dialog to install the su binary. Anyway, the side effect of using SuperSU seems to be that I can now boot into recovery using the power button menu using the 20150921 build, which has SELinux enforcing.
[Nook HD, HD+ Android Development] belfastraven:
Using 9/21 hummingbird and latest kernel in experimental folder, things are running well. I can boot to recovery from power menu, video is fine, and I can (almost) type with two hands.;) I did notice that after backing up system,boot,data with twrp, nook hd got very hot and starting "flashing" (like they sometimes do when compiling apps after new rom installation) while calculating the md5 for data. It did finish the backup, but then froze. it's ok now.

thnx
[Nook HD, HD+ Android Development] amaces:
That extended hashing is very CPU-intensive, and must lock it at 1.5 GHz (overclocked state), which the hummingbird silicon is not supposed to do… I gave in, but now I wonder if this will fry some people's HDs.
[Nook HD, HD+ Android Development] belfastraven:
I think for now, I'll just use the option not to generate an md5. I can always just reflash the rom, if there is a problem restoring. I had previously backed up the 9/21 boot,system,data before installing the latest kernel and the system did not get so hot, btw
[Nook HD, HD+ Android Development] swaaye:
[MENTION=4473900]amaces[/MENTION]

Set the CPU default speed to 1300 MHz and let those who desire to overclock configure the 1500 MHz speed on their own.

Though frankly I've spent a lot of time with it at 1500 MHz, doing lots of web browsing, and it doesn't seem to get hot doing this. It's nothing compared to a Tegra Note 7 that's for sure.
[Nook HD, HD+ Android Development] twiztid_:
Kind of confused about some things, like why the built-in(?) root was removed, was it a decision? Or something attempted as a fix? Also, is there any reason the zip from chainfire's site won't work? I get the Play install does not work, it needs root in order to install, but I'm kind of hesitant to use a file from a hosting site I can't verify the account of.

Also, has anyone noticed the keyboard doing some weird stuff, like eating words and messing up autocorrect? It just started doing it about 2 days ago for me on 9/17, but has happened in other recent builds after a few days (I think).
[Nook HD, HD+ Android Development] TBueno:
I guess the built-in SU code hasn't been actually removed, but the developer likes SuperSU better. Because it actually is a better, feature-richer SU manager.

The zip from chainfire's site does work, although it's been giving some of us a hard time. AMaces has put together a checklist to make sure it's properly installed. I've described my attempt to follow it and how I eventually managed to get SuperSU working with the latest builds here.
[Nook HD, HD+ Android Development] reflecx:
I didn't have any of the problems using SuperSU 2.49 beta. Just flashed from TWRP and it worked, no workarounds needed. For those who are (rightly) paranoid, here's the link from chainfire's site.

https://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip?retrieve_file=1
[Nook HD, HD+ Android Development] steavis00:
921 Rev / Netflix works fine / Google Play Store stopped

No clue otherwise
[Nook HD, HD+ Android Development] ieatabiscuit:
Perhaps a bad GApps flash? Everything works fine here. Maybe a smaller GApps package would do better? It's kinown that the smaller GApps work better on out toys.
[Nook HD, HD+ Android Development] hajkan:
Hey guys

I installed 921 and I lost twrp :( The flashing wiped my twrp :( What da heck

It is either the recovery partition is lost or the booting to recovery does not work.

Can anyone please tell me how I can get my TWRP back?

edit:

Ok it looks like menu way of starting in recovery is broken. Using ower button and home to boot to twrp works.
[Nook HD, HD+ Android Development] TBueno:
Installing SuperSU will probably make boot to recovery from power menu work again.
[Nook HD, HD+ Android Development] neutronjeff:
Is the 0924 kernal recommended with the 0921 Ovation build? What is the normal use / stable set up now?
[Nook HD, HD+ Android Development] vinceweis:
Isn't it still in the experimental folder? I wouldn't consider it "stable" if it's in that location.
[Nook HD, HD+ Android Development] miserly:
0921 installed, lost recovery via power and gapps has stopped

I keep getting Unfortunately, the process com.google.process.gapps has stopped message. AND i can't get into recovery from the power button. i was able to get into recovery but took a long time...
[Nook HD, HD+ Android Development] dxxvi:
My HD+ has the EMMC CWM-based recovery v6.0.4.6. I installed flashify and then flash the twrp.zip in the op but the recovery is still the same. What can be wrong in my case?
[Nook HD, HD+ Android Development] reflecx:
Flash the TWRP that's downloaded from Flashify, not the one from OP. After that, boot to TWRP, then flash the TWRP from the OP.
[Nook HD, HD+ Android Development] js290:
Just installed 20150927 out of the experimental folder. Cmupdater from 20150921 failed. Also, SuperSU got wiped out; so reboot into recovery from power menu failed. Had to reinstall SuperSU.
[Nook HD, HD+ Android Development] ieatabiscuit:
Try the pico gapps from opengapps. Sometimes gapps just likes to act weird.

---------- Post added at 12:18 AM ---------- Previous post was at 12:12 AM ----------

There are 2 flashify options in play store. You want the one that specifies for root users. Make sure to flash recovery image, not zip file.

---------- Post added at 12:22 AM ---------- Previous post was at 12:18 AM ----------

Cmupdater will not work until we get official releases. As for SuperSU, it gets replaced when you flash new releases by the sock sudo app which is being wonky. This is normal.
[Nook HD, HD+ Android Development] miserly:
thanks OP et al

i was able to install SU and get root again. so i added TWRP and installed a handful of gapps from the play store going back to 0906. i may venture back out to more recent, but this ROM totally smokes! super buttery smooth and does everything . thanks for keeping this tablet alive.

m
[Nook HD, HD+ Android Development] Mac Hosehead:
Greetings, I am new here and I own a HD. I started with 0906 and went to 0921 with the experimental kernel. Reboot-to-recovery works and power-off works intermittently. Everything else, including Play Store, appears to work although I'm a relatively light user. Installation was pretty straightforward. I had to install SuperSU binary but no problems. I just tried the 0927 experimental and I don't notice anything different from what I was running previously. All-in-all it seems stable and in good shape to use daily but it would be nice to have more user experiences.
[Nook HD, HD+ Android Development] belfastraven:
Updated hummingbird a few hours ago to 9/27 build. Everything is running well. No ppoblems with superSU, boot to recovery from power menu, video...

thnx, [MENTION=4473900]amaces[/MENTION]
[Nook HD, HD+ Android Development] asakurato:
Reboot to recovery always used to work for me, but as of 09/27, it no longer works.

There also seems to be some problem with supersu. It dorsn't give permission to any app, flashed latest 2.49 beta version, still same.
[Nook HD, HD+ Android Development] snoozer854:
Everything is working fine on both HD's that I just updated to 9/27 too.

Actually stayed turned off a few times too, not every time, but more than it has in quite awhile.

Runs nice & smooth, seems pretty responsive.

Thank you

Mark
[Nook HD, HD+ Android Development] js290:
Actually, cmupdater worked going from 20150906 to 20150921. It's kind of a known issue with TWRP.
[Nook HD, HD+ Android Development] TBueno:
Ran ovation-0928 for a while, flashed over 0921 and SuperSU "persisted" just fine.

Performance seems really solid, responsiveness and ram management-wise.

However, Chrome (latest stable version) is flickering and producing the same weird rectangular artifacts from a few months ago... so I had to revert to my backup.
[Nook HD, HD+ Android Development] smileyint:
Hi,

I using hummingbird with the lastest cm12.1 but the root option in developer option is missing since last week release. I read cm comes pre root on another thread. Anyone with the same issue?
[Nook HD, HD+ Android Development] ieatabiscuit:
Then I stand corrected. Thanks for that little tidbit there, I did not know.
[Nook HD, HD+ Android Development] thchipmunk:
I saw somewhere in this thread that the dev prefers SuperSu. That seemed to work for me.
[Nook HD, HD+ Android Development] smileyint:
Hi thechipmunk

I also did that already. Thought that is just a work around because latest 2 build of CM12.1 humming seems to loose root. Not sure the usb host switcher malfunct had anything to do with that. Thanks. I thought my hummingbird is the only one with this problem.
[Nook HD, HD+ Android Development] amaces:
Yeah, that makes me sad, since general memory management was great… Basically, I tried again some of Google's low RAM flags described here: https://source.android.com/devices/tech/config/low-ram.html#flag. Things work well, except some of Google's mainstay apps (e.g., Chrome, YouTube), which is boggling to me.

Oh well, it's a simple build.prop change to revert, and I updated the current builds without the ro.config.low_ram flag, and added the edited build.prop. You don't need to download the whole ZIP again; either overwrite /system/build.prop, or delete/comment out lines 63 & 64.
[Nook HD, HD+ Android Development] Mac Hosehead:
So far I have been unable to replicate flickering or artifacts with Chrome and YouTube on my HD. Does this just concern HD+ or a low memory condition?
[Nook HD, HD+ Android Development] TBueno:
Artifacts only show in specific websites. Try AMaces' Box locker or NYT full (desktop) site.
[Nook HD, HD+ Android Development] Mac Hosehead:
Chrome is not so smooth but I have not noticed any graphical anomalies at either site.
[Nook HD, HD+ Android Development] TBueno:
Then it's probably a HD+ privilege too... [emoji19]
[Nook HD, HD+ Android Development] brenyoka:
coming from CM 10.3 stable, I updated my HD+ to CM 12.1 a few weeks ago. Just a couple quick comments:

1. starting with the 09/21 build, the device properly shuts down, at least more frequently. Not each time, but still the difference is very noticeable. Reboot to twrp recovery also works.

2. chrome indeed flickers slightly on sites, and this was something new to the 09/28 build. I will apply the new fix and report later.

3. previously people mentioned having problem with superSu and loosing root. I never had that problem.

I don't know if it matters, but I always flashed the latest opengapps nano package, because it includes that "extra functionality which is not available from the play store". Only then I installed chrome from store.

[MENTION=4473900]amaces[/MENTION]: thanks a lot for all the hard work, much appreciated!
[Nook HD, HD+ Android Development] mmnspeed:
deleted

---------- Post added at 12:23 PM ---------- Previous post was at 12:20 PM ----------

did you install the older version through flashify first?you have to install the version from op through an older version of twrp.you can't do that through cwm.
[Nook HD, HD+ Android Development] brenyoka:
So I applied the latest ovation fix, but chrome still flickers. Haven't tried other browsers though.

***** edit: Have done a bit of comparisons among browsers. Opera flickers like Chrome, but interestingly, Firefox is quite smooth. Just saying, maybe the developers can do something with this info.

For the 'testing', I loaded a few media-heavy, desktop sites, like New York Times, Yahoo News, etc.
[Nook HD, HD+ Android Development] asakurato:
Hd video playback is still not working on youtube, haven't checked other hd videos.
[Nook HD, HD+ Android Development] amaces:
The VPN issue is unlikely to be about encryption since the connection is established; cyphers are negotiated during the initial handshake, and the server has already OKed that part. Few chances that your .1X EAP connection problem is related to this. The WPA supplicant is in charge of that, and there could be many reasons why it fails. EAP is a very large spec, and although I thought our TI supplicant is pretty capable, it may not support that particular authentication flavor. You'd need to give me more information to have that fixed.

Maybe it does, but I thought those are system functions handled by init, which should't care about su. At any rate, CM's root solution is based on koush's Superuser app; once they gobbled it up, SuperSU remained the only independent options (well, things have become fuzzy recently, since Chainfire transferred ownership…).

Anyway, there are millions upon millions of Nexus devices that use SuperSU; that 2.46 ZIP remained unchanged for many months now because it works very well on Lollipop. Reading through posts recently, I almost get depressed… I'm either taking crazy pill, or have the luckiest device ever… The good thing is there's much good, even verbose information on this thread, as well as on the web, so everyone will hopefully solve their root issues.

I tried to explain the difference between userdebug and user build templates, and how that change didn't happen on a whim, or for jerk reasons ;) I mean, I am one, but it wasn't my intent to frustrate people…

Would totally do that, if I knew how. As of now, the interactive governor caps max frequency at screen off, then ups it to hardware max at screen on. Even if I control scaling parameters, they will be quickly reverted, and have yet to find a sysfs node, or command that users could use to control it. Short of changing more things inside the kernel, there isn't a trivial solution, but it may not be such a problem if I'm careful when I compile new recovery images.

Following on the above, I don't think the latest hummingbird recovery was compiled with the 1.5 GHz hack, so your overheating may be due to something else. The one time I hashed a backup, I also compressed it, so MD5 had an easier job, plus saved quite a bit of time.

Did you wipe caches after flashing the new build? Also, the quality of the GApps package matter a lot; people have been moving onto opengapps.org.

You can always flash recoveries in one step. Just extract the recovery.img inside the ZIP, then follow the OP instructions, which work anywhere (e.g., CWM, TWRP, regular ROM, either using adb shell, or the Terminal app).

As above, you really don't need to complicate your life. Just extract the recovery.img, and have Flashify write it. Official TWRP (which is the image Flashify will download automatically) does not have support for flashing CM12.1 builds since mid August.

Then, you likely haven't changed things properly. Either adb pull /system/build.prop, or look through that file on the device; ro.config.low_ram=true should be commented or taken out, then reboot.

Read post #1105…
[Nook HD, HD+ Android Development] brenyoka:
Actually I did a full wipe with the updated zip which has that "build.prop" inside.
[Nook HD, HD+ Android Development] amaces:
Just in case I messed up freshening the original ZIPs, can you check unzip cm-*.zip system/build.prop? Or look through the current version installed on device.
[Nook HD, HD+ Android Development] brenyoka:
You did not mess up. I did a hash comparison before flashing, and the 'build.prop' inside the new zip is the same as the one you uploaded to the Ovation folder.
[Nook HD, HD+ Android Development] asakurato:
Replaced build.prop from ovation folder, still hd video has no picture, just sound. I also checked checksum beforehand, it was different
[Nook HD, HD+ Android Development] Mac Hosehead:
The app for my VPN service will say it is connected to a remote server and will also continue to give stats but traffic never routes through. I can turn off encryption but that doesn't make any difference.
[Nook HD, HD+ Android Development] amaces:
Pretty odd, since editing build.prop on device is exactly what I did on mine, and things went back to normal upon reboot. Just in case, I recompiled and replaced the images again, without any manual modifications.
[Nook HD, HD+ Android Development] asakurato:
Hmm, it seems that just 60fps hd videos are affected, normal hd videos work fine (60fps worked normally before).
[Nook HD, HD+ Android Development] DarkWolffe:
A couple things I've noticed on the September 30th build:

1. Task switching is still pretty slow. This may be simply a hardware limitation.

2. The Calculator app puts the "i" button over sin, "%" over cos, and "X" over tan.
[Nook HD, HD+ Android Development] twiztid_:
The sluggishness seems to have made a return somewhere after the 9/17 build. I noticed it too on a completely fresh install.

I think this is an AOSP/CM bug, and a fairly long standing one (been there as long as Lollipop has been running on the Nook IIRC).
[Nook HD, HD+ Android Development] TBueno:
Sluggishness can be very subjective. In my experience, task switcher's performance varies a lot depending on current tasks, number of thumbnails, current load at system resources etc. Although it's not as quick as smaller devices, it has improved a lot since older builds.

About garbled buttons in calculator: I'd recommend Calculator L from store (identical to stock), CM doesn't seem to squash bugs as they used to...
[Nook HD, HD+ Android Development] g002ahe:
on latest build there is not root option under developer. supersu doesnt work (no root).

can anyone point me in the right direction

did a clean install.
[Nook HD, HD+ Android Development] twiztid_:
Flash SuperSU , or another lollipop SuperUser zip if you can find one, in TWRP.
[Nook HD, HD+ Android Development] sutty86:
Do I need to flash gapps as I've just flashed new Version clean flash and just hit with forced errors can't get on anything
[Nook HD, HD+ Android Development] twiztid_:
If you wipe system and/or data, then yes. If you "dirty" flash (update without wiping system), then no you shouldn't need to.
[Nook HD, HD+ Android Development] swaaye:
Userinit.sh doesn't work anymore. I looked in the init.d directory and saw no script to call it so I put one in there. But that doesn't work because SELINUX doesn't allow that. Security error in system log.
[Nook HD, HD+ Android Development] Zippy Dufus:
Strange build issue

[MENTION=4473900]amaces[/MENTION],

Any idea what may have caused the error below?

I'm using the Linaro compiler and I got this error on my active virtual machine for building this ROM. So I used a backup virtual machine which hasn't been updated or tampered with for over a month and still got this error so I believe that something changed which was not caused by me.

Before I try to do a straight build (with the standard toolchain), I'm wondering if you may know something?

CC fs/proc/proc_sysctl.o

CC block/blk-sysfs.o

../../../../../../kernel/bn/omap/fs/nfs/idmap.c: In function 'nfs_idmap_id':

../../../../../../kernel/bn/omap/fs/nfs/idmap.c:468:1: internal compiler error: Segmentation fault

nfs_idmap_id(struct idmap *idmap, struct idmap_hashtable *h,

^

Please submit a full bug report,

with preprocessed source if appropriate.

See <http://gcc.gnu.org/bugs.html> for instructions.

/home/android/kernel/bn/omap/scripts/Makefile.build:305: recipe for target 'fs/nfs/idmap.o' failed

make[4]: *** [fs/nfs/idmap.o] Error 1

/home/android/kernel/bn/omap/scripts/Makefile.build:441: recipe for target 'fs/nfs' failed

make[3]: *** [fs/nfs] Error 2

make[3]: *** Waiting for unfinished jobs....
[Nook HD, HD+ Android Development] netguru76:
Hi,

coming from cm11 it is only flashing trwp and the cm12 version from the folder (op)?

The build.prop is for?

Cheers

Gesendet von meinem SM-T805 mit Tapatalk 4
[Nook HD, HD+ Android Development] danj88:
A

Tried this, but still getting ''There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device'' when I try to open SuperSU

:(

Edit: the v2.46 ZIP worked instead http://download.chainfire.eu/supersu
[Nook HD, HD+ Android Development] amaces:
Sudden ICEs are likely due to new CFLAGS. If you're using my repositories, I've added aggressive optimization flags for ROM and kernel; these are probably due to the kernel Graphite optimizations, which don't seem to work well with less than GCC 5. For the past couple of weeks, I've been using UBER's GCC 5.2.x EABI for kernel (ROM needs to stay on GCC 4.x).

Executing userinit.sh (and setting proper permissions) is likely a userdebug thing; user builds would need a different mechanism. What do you need to put in there? If it makes sense, I may add it to the normal init scripts.

Addendum to a previous September 28th build; if you didn't have Chrome/YouTube issues, you didn't need it.

Yes, I definitely remember 60 fps working fine a few months ago… Likely an upstream CM12.1 bug, but I'll check.
[Nook HD, HD+ Android Development] twiztid_:
Sorry about the bad link. No clue how I got the older version.
[Nook HD, HD+ Android Development] jackonod:
Is there any chance in the near future to take this rom possible to boot from SDCard? Anybody interesting about we can try the lollipop not just from EMMC-boot (many people, like me, want to keep stock system in the Internal Card)? Earlier CM versions ported to SDCard boot almost immediately, lollipop now long time out, but still we don't see any port to SD (cm12), why? I will be very happy to see that, I have both HD and HD+....Can I hope, is there any chance for a cm12.1 SDCard image????
[Nook HD, HD+ Android Development] brenyoka:
quick feedback on latest ovation build:

- chrome flickering is gone, browsing is fine; it does not feel fast but at least contents render nicely. Patching that "build.prop" did not fix things for me previously.

- boot into recovery (then shut down) as well as proper shut down seem a bit more reliable in comparison to around pre 21/09 or so builds