yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] NE0HP:
How to upgrade Ovation from CM11 to Naugat (CM/AOSP)?

Greetings!

I've been using CM11 on Ovation since long now. I want to upgrade it to latest Nougat build. But before upgrading, would appreciate if anyone care to answer to some of my questions/queries.

1, Before flashing Nougat build, Do i need to upgrade my boot-able SD card recovery from CWM to latest TWRP 3.0.2.0? or Is it possible to flash newest TWRP from CWM directly and then flash ROM and Gapps?

2, If I need to make an New Boot-able SD card recovery of TWRP, what would be the procedure? will it be the same procedure as like what is instructed in CM11 forum?

3, What is best, Internal Recovery or External Recovery?

4, There is an experimental TWRP 3.0.3.0 recovery available, anyone tested it? and if tested then can it be flash directly using 3.0.2.0? If its possible then boot-able SD card recovery automatically updated to 3.0.3.0 or it will go straight in Internal memory and boot-able SD card recovery will stay on 3.0.2.0?

5, If we ever have to factory reset Nook HD+, will it also wipe Internal recovery?

6, How stable is the latest ovation Nougat build?

look forward to the answers.

Thanks in advance
[Nook HD, HD+ Android Development] digixmax:
AFAIK there is no SD-based image for TWRP 3.x, so you should use your current SD-based CWM to flash the internal TWRP zip then reboot into the newly installed internal TWRP to install the new ROM and GApps zip.
[Nook HD, HD+ Android Development] NE0HP:
Thank you for responding. I will give it a try. One more thing, you must have read news articles about CyanogenMod shut down its services from 31st Dec'2016 and LineageOS will be a continuation of what CyanogenMod was....so any chance this unofficial ovation CM build merged in to LineageOS?
[Nook HD, HD+ Android Development] hemeboy:
Wifi continues to drop immediately after connection with password using today's Nougat ROM builds for ovation.
[Nook HD, HD+ Android Development] cjpicci:
Well, there is the multi-recovery SD image which includes TWRP 3.0.0.0, but no higher:

https://xdaforums.com/showthread.php?t=3314870

Is 3.0.0.0 sufficient for the Nougat builds?
[Nook HD, HD+ Android Development] lmore377:
How does download!?!?

Someone please tell me how to download this. I feel like a blind and brain dead horse trying to figure out how to internet.
[Nook HD, HD+ Android Development] snoozer854:
Just flashed lnos_hummingbird-ota-NMF26Q.170104 after wiping everything & got it up an going, enabled developer options have root set for Apps and ADB, but when I try to use Titanium Backup message pops up "Please verify this rom is rooted"

Am I missing a step here, maybe?

Thank you,

Mark
[Nook HD, HD+ Android Development] mikeataol:
Hi, I think that these are only partially rooted. The system partition isn't mounted writeable

to read write to the system partition , before trying deep rooted activities....

connect to PC.

I usually restart adb with "adb root"

then issue an "adb remount" command.....

Then , you oughta be able to do fully rooted operations.
[Nook HD, HD+ Android Development] snoozer854:
I know when I was running Marshmallow there was SuperSu that needed to be flashed & this gave root, but I haven't seen anything about doing that with this new version .

Not sure how to do the stuff when connected to computer, will have to do some searching on how to do this with the commands.

Thank you for your time, I really appreciate it
[Nook HD, HD+ Android Development] mikeataol:
Been thinking about it, The CM / Lineage versions should have everything needed for root.

The AOSP based recent ones needed the PHHSuperSU flashed for the interface.

There's been a long standing bug in CM versions regarding root

go into developer options

change root access from apps and adb to something else,

then go back in and change it back , see if that fixes the problem.

I don't have a hummingbird to test it with, sorry. worth a try anyway
[Nook HD, HD+ Android Development] snoozer854:
That did the trick.

Thank you very, very much
[Nook HD, HD+ Android Development] Zippy Dufus:
Say good-bye Cyanogen, hello LineageOS!

Hello,

I saw that there are LineageOS builds so I deleted my .repo and resynced EVERYTHING.

Dumb question, what is the "lunch ????-ovation-userdebug" command? :o

== EDIT ==

Never mind. Found my answer here.

Building away ... :cowboy:

== ANOTHER EDIT ==

Built, installed, runs like a charm.

Thank you [MENTION=4473900]amaces[/MENTION] !!
[Nook HD, HD+ Android Development] SoundZombie:
Flashed the nougat aosp ovation build and can't seem to regain root even with phh su zip from recovery. I get a ramdisk decompression failed error and it quits. Any new solutions?
[Nook HD, HD+ Android Development] belfastraven:
Root is built into the rom. In order to manage it, you just need to install the phh.apk superuser app from the playstore (don't install the zip). I am running the new rom on hummingbird and root is fine. I imagine it is ok for ovation, also. Perhaps someone can confirm?
[Nook HD, HD+ Android Development] SoundZombie:
Can confirm this works. Thank you so damn much. I've been trying for days to get superuser back.
[Nook HD, HD+ Android Development] neutronjeff:
How's the Ovation performance on the N Asop?
[Nook HD, HD+ Android Development] TeutonJon78:
Is a dirty flash for LOS from CM14.1 going to be fine, or if that too much of a mess? I had just done a clean install of CM14.1, so it's still pretty fresh.
[Nook HD, HD+ Android Development] mikeataol:
I think if you installed a GAPPS, you will have to wipe /data and reapply GAPPS, or Google Play Services will FC non-stop with a dirty flash.

If you didn't apply GAPPS, I think it will be okay.
[Nook HD, HD+ Android Development] BultoPaco:
I dirty flashed the LOS ROM over the most recent CM14.1 with GAPPS installed on my hummingbird yesterday. The tablet is running great and battery usage seems good?
[Nook HD, HD+ Android Development] digixmax:
Does it have to be this specific phh SuperUser app, or some others SuperUser apps such as Chainfire's would also do?
[Nook HD, HD+ Android Development] belfastraven:
I'm not positive of the answer. I know that the code originally built into the AOSP rom for superuser was phh's code. I don't know if that is still the case.. As long as you don't try to install any of the other binaries, probably the worst that could happen is that the app would not work.
[Nook HD, HD+ Android Development] digixmax:
Thanks.

Does the same hold true for CM14/LN14? It used to be that one needs to flash UPDATE-SuperSU-v2.46.zip, but not anymore?

---------- Post added at 11:24 PM ---------- Previous post was at 10:25 PM ----------

OK, I just tried it out on my freshly installed LN14 (lnos_ovation-ota-NMF26Q.170104) -- simply enabling Root in Developer Options would suffice (not sure why my first attempt before posting the above questions didn't work), no flashing UpdateSuperSU and no SuperSU app is needed.
[Nook HD, HD+ Android Development] belfastraven:
There is still a "bug" I believe, in that when the cm/ln rom is first installed on a device with a clean data partition (after a wipe or factory reset), even though developer options will say you have root, you actually don't. Changing the root selection to something else and then changing it back causes the necessary system file to be created. As long as you don't wipe data, you will not have to do this again on dirty flashes. What is new in the last few months is that, accessible through developer options, there is a rudimentary root manager available in the rom, where you can determine how root requests from various applications should be handled and see which apps have requested root access.
[Nook HD, HD+ Android Development] digixmax:
I think (although not 100% sure) that was what happened to me. :)
[Nook HD, HD+ Android Development] Goggles2114:
An I the only person that installed on hummingbird and the screen was upside down?
[Nook HD, HD+ Android Development] DominoPhreak:
I think that's been happening since the Nov builds. It's a known issue, and at this point the consensus is "just deal with it".
[Nook HD, HD+ Android Development] digixmax:
Is the "Unlock System Tuner UI" hidden feature -- swipe down the Quick Settings and press and hold the settings cog at the top next to the battery (described at http://www.pocket-lint.com/news/138...s-get-your-teeth-into-google-s-gooey-goodness) supported in lnos_ovation-ota-NMF26Q.170104?
[Nook HD, HD+ Android Development] mikeataol:
Whats available in System Tuner UI varies widely by rom....

Yes, its available in these AOSP builds, but it has limited selections.

-Turn on or off various status bar notification icons

-a couple of Do Not Disturb settings

-Power Notification Control

I've used "Custom Quick Settings" from the play store more often than not....
[Nook HD, HD+ Android Development] dbrickg:
Just dirty flashed the 20170104 LOS ovation build over a recent cm14.1 and it worked just fine. No problems so far ... oh, I keep getting a "calendar app has stopped" alert during the first few minutes after a reboot, but when I actually open the calendar, everything seems to be fine. And wifi works without issue. Youtube casts to my old chromecast, both using youtube's built-in casting and using the generic screen casting. I couldn't get Netflix to cast but didn't try very hard. In short, everything seems to be working quite well, better than in cm14.1. I just downloaded twrp 3.03-0-ovation from the op and will try installing it.

Yup, twrp 3.03-0 seems to be good, too....

Edit: and I just tried casting again, and Netflix DOES work! Everything I tested casts perfectly! Not sure why Netflix wasn't working for me earlier. Very cool.
[Nook HD, HD+ Android Development] acr123:
For clarification, are you saying the Inos CM14.1 ovation build - not aosp build- is able to screen cast ( actual mirroring of screen w/o having to use app or chrome).

Thanks,

Al
[Nook HD, HD+ Android Development] mikeataol:
*delete* mis-read the question, sorry
[Nook HD, HD+ Android Development] acr123:
I thought that in the CM builds, going back at least to CM 13, had some type of "bug" that did not allow video when mirroring the screen. I have chromecast & can cast from Chrome using the extension & also the apps such as

youtube. However when I have tried to mirror the screen I only get audio but never video.. I am using somewhat recent CM14 ovation build from early Dec and several before this & never was able to get screen mirroring to work.

Are you 100% sure that the CM builds mirror. I know the AOSP builds mirror but I prefer CM builds.
[Nook HD, HD+ Android Development] mikeataol:
sorry I didn't read properly...

It wouldn't surprise me if its working in the LOS version by now, but I cant say for sure as I only load the AOSP versions.
[Nook HD, HD+ Android Development] dbrickg:
Well, for clarification, it's not lnos CM14.1, it's just lnos 14.1. CM doesn't exist any more :) But yes, it casts everything on the Nook HD+ to my big screen. But the only thing I have to cast to is an old Chromecast on my receiver, connected to my projector. So, I don't know if it'll cast to any other sort of smart tv or monitor. And, as I said, Netflix won't cast. The Nook all by itself does play movies just fine, but as soon as I turn on casting, it stops: it doesn't play on either the nook or on the projector, no video and no audio.

And, I take it back: Even Netflix casts perfectly! Yeehaw! Don't know why I thought it didn't earlier. Maybe I was trying to use the casting built in to Netflix? Anyway, using the OS's built in casting icon in the quick pull down menus in the upper right, everything I thought to try casts perfectly, both video and audio

---------- Post added at 09:06 PM ---------- Previous post was at 08:59 PM ----------

I just tried casting from the LnOS 14.1 ovation to my Chromecast, which is attached to my multimedia receiver, which is attached to a video projector, and everything on the Nook shows up and is audible on the big screen... except Netflix. Netflix plays on the Nook HD+ running the LnOS 14.1 just fine, but as soon as I turn on casting, it freezes, both on the Nook and on the big screen. There may be other apps that won't cast, I haven't tried everything :) I'm going to go try it again now, check a few other things. And I'll get back to the group in a few minutes ....

See above: Netflix DOES work perfectly. And everything else I thought to try has both video and audio: poweramp plays audio, Sibley birds plays bird calls, Youtube works, Acuweather plays time-lapse weather maps and videos. I'm really impressed!
[Nook HD, HD+ Android Development] acr123:
I wonder if the problem is either my samsung or vizio TV that I am unable to mirror from Nook HD+. Is there anyone that has chromecast attached directly to a TV and is able to mirror from Nook HD +. using CM 14 or newer Ions 14.1

I am happy with CM14 & am reluctant to upgrade to Ions 14.1 unless it will mirror from Nook HD+ to TV.

Al
[Nook HD, HD+ Android Development] mikeataol:
https://xdaforums.com/showpost.php?p=70257908&postcount=1513

"ovation, as stupid as this is changing my wifi from channel 1 to 11 made casting suddenly start working."
[Nook HD, HD+ Android Development] acr123:
Thanks. I had previously tried switching channels when I read this initially. I do not think this is a problem since the router is right next to 1 of the TVs I tried. However, I have still not read that anyone recently with CM 14 or Ions ovations builds could mirror the screen to a TV with video and audio. I believe there is probably some problem with the video resolution being synced up between the 2 devices but I am not smart enough to fix this.
[Nook HD, HD+ Android Development] digixmax:
I am running lnos_ovation-ota-NMF26Q.170104 on my HD+ and can mirror the Nook screen (audio+video) to my Chromecast using the "Cast" button in Quick Settings (note that the "Cast" button is not included by default and needs to be added by editing the Quick Settings).

With some apps like Netflix and YouTube I can choose between the Chromecast or directly to the Panasonic TV ("Viera 60"). With native casting and some other apps like NBC Media the only choice is Chromecast.
[Nook HD, HD+ Android Development] Tonto87:
I running cm_ovation-ota-NMF26Q.161222 and for the most part it runs very smoothly, but I have one problem:

- GIFs within Reddit sync and videos in YouTube don't play. (EDIT: Now working on experimental lnos_ovation-ota-NMF26Q.170104 build)

One very minor problem is that the task manager has stretched tiles.
[Nook HD, HD+ Android Development] acr123:
Updated HD+ to same Inos version and screen mirroring works perfectly like you said. I had been waiting until someone confirmed that it works. It had always been working for me with apps & Chrome browser with Chromecast but never just to mirror the screen until now.

thanks,

Al
[Nook HD, HD+ Android Development] shadabt:
Just clean flashed 20170104 LOS ovation. Have a weird wifi issue. Wifi doesn't reconnect after wifi is turned off and on. It gets stuck at searching wifi forever. It however reconnects after device restart. Let me know if there is any workaround. Sorry if the answer is already posted.
[Nook HD, HD+ Android Development] digixmax:
Did you do a "factory reset" prior to flashing the new ROM & GApps?
[Nook HD, HD+ Android Development] acr123:
If you have a separate battery saver app turn it off. Also under wifi advanced try changing settings for wifi on during sleep.
[Nook HD, HD+ Android Development] dermk4:
Kudos to the OP and all devs who got this working for us, you guys rock! My trusty Ovation is running butter smooth with a clean install of LNOS and Open Gapps Pico. You guys was like giving it new life again
[Nook HD, HD+ Android Development] Uldiniad:
after repo syncing about a week ago, I started getting a build error concerning files in android_hardware_ti_wlan:

http://pastebin.com/f8SRCKYu [MENTION=4473900]amaces[/MENTION] I was looking at the files to try to fix them and upload to gerrit. The if statement in the 17th line (I think) of the .h file (which is autogenerated) seems to be what is breaking everything. It is missing a binary operator before "(". And then the #endif statements probably break due to the if statement being broken. I don't mind helping but I am a little lost on the issue (have checked on Google for similar issues and haven't found much helpful) so some tips would be appreciated. Otherwise, you might already be working on it and that is fine too.
[Nook HD, HD+ Android Development] belfastraven:
I believe this error is coming from the script that generates the autoconf file, hardware/ti/wlan/compat_wl12xx.sh/gen-compat/autoconf.sh Two of the sed lines have in them [ ^:space:]. when they need [[^:space:]]. that is they need double brackets...
[Nook HD, HD+ Android Development] Uldiniad:
Will give a look at that and report back if that solves the issue. Can try uploading the patch to Gerrit if it works well
[Nook HD, HD+ Android Development] Uldiniad:
so, to anyone having the wlan-related build errors:

cherrypick this:

lnos-13.0 https://review.lineageos.org/#/c/158165/

lnos-14.1 https://review.lineageos.org/#/c/158164/

---------- Post added at 02:23 AM ---------- Previous post was at 02:07 AM ----------

@amaces [MENTION=5672278]belfastraven[/MENTION] wow, just got the build to work but I did not realize that the new logo was going to look horrible when booting. is it because it is picking the wrong resolution for the nook devices? what files need to be looked at?
[Nook HD, HD+ Android Development] belfastraven:
Um-- what does it look like. I have been building with a different kernel, but other than being upside down as usual on hummingbird, the logo looks the way it is supposed to--a circel moveing long a curve, with the word lineage coming up at the end of the boot animationm....

---------- Post added at 03:28 AM ---------- Previous post was at 03:25 AM ----------

Um-- what does it look like. I have been building with a different kernel, but other than being upside down as usual on hummingbird, the logo looks the way it is supposed to--a circle moving along a curve, with the word lineage coming up at the end of the boot animation....
[Nook HD, HD+ Android Development] Uldiniad:
The arc is off-center for me and bending to the side where the circle originates. This is on ovation
[Nook HD, HD+ Android Development] Goggles2114:
Just grabbed the latest hummingbird from the experimental folder. I got the upside down screen, android logo, but everything else works fine. Right now I would rather xposed working ahead of the screen fix even though I have a few apps that refuse to reorientated.

But if the screen fix is simpler that is fine too.

On an odd note speaker crackling from 10.2/11 has gone away.

7/Linkage has baked in a lot of nice features in terms of memory management split screen and such. So far mostly good.
[Nook HD, HD+ Android Development] Uldiniad:
[MENTION=4473900]amaces[/MENTION] [MENTION=5672278]belfastraven[/MENTION] New error. Simple to patch but not sure if we should add resource as it says to do or if it is not ready to be added.

Suggestions?

device/bn/common/overlay/cm/frameworks/base/packages/SettingsProvider/res/values/defaults.xml:26: error: Resource at def_accelerometer_rotation_angles appears in overlay but not in the base package; use <add-resource> to add.

Seems to be related to this merge: https://review.lineageos.org/#/c/158181/
[Nook HD, HD+ Android Development] belfastraven:
I have a feeling the repo updater wasn't talking about our devices, since we are not "official". Hopefully [MENTION=4473900]amaces[/MENTION] will weigh in here-- at least on Hummingbird we do need the resource in the overlay (valued at 15, actually (i.e. all rotations enabled by default)) . I don't know whether for ovation it is a requirement or not. What I mean is, I think, at least for Hummingbird, we can't get rid of the overlay, so we would need to have the resource added back in, or find some other way to enable all rotation angles.
[Nook HD, HD+ Android Development] Uldiniad:
good to know all this. I ran into the error with ovation. amaces is looking into it
[Nook HD, HD+ Android Development] belfastraven:
The boot animation generation code which is in vendor/cm/bootanimation determines resolution (see the generate-bootanimation.sh file) from three variables defined in thedevice/bn/hummingbird or ovation/cm.mk file:

target_screen_width, target_screen_height, and target_bootanimation_half_res. It doesn't seem to which dimension is specified as height vs width--lineage will always use the smaller dimention as width and calculate the height of the logo from that.

I tried implementing target_bootanimation_half_res=true, which helps the system generated less dense png files for the bootanimation.zip, and that improved the looks of my logo. Perhaps you could try that, and also make sure that the width and height humbers are correct: I don't know what they should be for ovation. If that works, perhapswe can ask [MENTION=4473900]amaces[/MENTION] to make the change in his repository.
[Nook HD, HD+ Android Development] Uldiniad:
ok will try giving that a look in the upcoming days
[Nook HD, HD+ Android Development] Uldiniad:
sadly, it did not seem to help. wondering if others have the bootanimation problem or if it's only on my clean builds for ovation
[Nook HD, HD+ Android Development] BacktotheFuji:
Just popping by to say thanks for the recent builds :)

I've flashed the cm13 build from 26 Nov on my Nook HD+ and it's never run so well! One question though, is it possible to get our devices running DRM protected content e.g. Google Play Movies and TV?

Cheers!
[Nook HD, HD+ Android Development] mmnspeed:
Tried the latest build,but got error while installing gapps due to low space.Error 70 if I remember correctly.Really busy currently,tried browsing through the pages,but Can't seem to find a working way to use the config-gapps file.Any help is appreciated.If I had more time,would go through all the pages.Thanks.

P.S.:typed exclude in the text file,then some apps.Was using Pico gapps.Didn't work.Placed the file where wiki said to place it.
[Nook HD, HD+ Android Development] mikeataol:
here's the low tech method I've used to install gapps lately

you need to know how to use the TWRP file manager.

in TWRP, after the rom install, I move folder /system/media/audio/ringtones off somewhere out of system.... data is fine.

install gapps

then move the ringtones back

has worked a few times.
[Nook HD, HD+ Android Development] mmnspeed:
Man you are awesome...The solution isn't low tech,but the simplest and most effective...It worked...Wasted a lot of time with other methods..Thanks..
[Nook HD, HD+ Android Development] andtron:
Beside requiring root privilege to access the sd card (hence is invisible), another issue is that the card is named as a number xxxx_xxxx under the \storage folder, making alot of apps that use the sd card folder non-functioning anymore.
[Nook HD, HD+ Android Development] belfastraven:
From [MENTION=4473900]amaces[/MENTION] 12/13 cm13 humminbird build, my numbers as shown by trickster mod:

over 12 hours:

Deep sleep: 58%

396MHz 24%

800MHz 14%

1100MHz 0%

1300MHz 0%

1500Mhz 1%

Hope that helps..

P.S. do you by any chance have some kind of misbehaving app running that is not allowing system to "doze" ?
[Nook HD, HD+ Android Development] Zippy Dufus:
Thanks, I will install the posted ovation build and check again overnight.

Meanwhile, I'll reboot and test again. The two culprits for battery usage are Mediaserver(24%) and Media(24%). It also shows Over-counted(18%) - what is that?

== UPDATE ==

Never mind.

I flashed the posted builds (aosp_ovation-ota-MMB29M.151208.zip and aosp-kernel-ovation.zip) and it is now deep-sleeping after leaving it idle overnight. :good:

I also disabled my corporate Exchange email account using the gmail app. Still investigating though because it initially didn't appear that the posted ROM would deep sleep.
[Nook HD, HD+ Android Development] Monfro:
CM13 works well on my Ovation, maybe is placebo but memory management seems even a little bit better than AOSP
[Nook HD, HD+ Android Development] adagiov:
Amazing job. Really appreciate your work.