yashsingh1/xdaforums huggingface dataset:
[Nexus 9 Android Development] retiredtab:
Okay, I tried adding livedisplay to the manifest.xml and device.mk and compiled it. However, it doesn't add or change anything to the behaviour as described.

Then, I started looking at https://review.lineageos.org/ and people who are more knowledgeable and with more experience with tegra SoC suggest livedisplay isn't all that well supported.

If the goal of livedisplay is to get blue light filter, there's lots of free no-ad apps that will achieve that. I'm testing one now and it works with 15.1. The hue is definitely reddish.

If you absolutely need livedisplay in LineageOS, try 14.1. If it works in 14.1, then use that. It's not uncommon, as I have experienced building several different roms for different devices over the last 9 months, that what works in the previous version is broken in the next version for whatever reason. And vice versa. What didn't work in the previous version now works in the current version. It's completely frustrating when this happens and it's device specific.
[Nexus 9 Android Development] retiredtab:
I forgot to give a real world and recent example. Having livedisplay in the manifest for some of the devices that run LineageOS 18.1 completely prevents the device from booting. These same devices have livedisplay running fine in 17.1.
[Nexus 9 Android Development] intervention408:
Ok I didn't know that livedisplay is such a complicated thing. I really thank you for explaining the subject and looking into it. But honestly, I don't want you do invest time and effort just for me. I installed cflumen, it does what it is supposed to do. Thanks again!
[Nexus 9 Android Development] retiredtab:
New build called lineage-15.1-20210415-UNOFFICIAL-flounder.zip

April 15, 2021 release notes

1. Incorporates April 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/307722

2. Removed livedisplay option from menu as it doesn't work on Nexus 9 Tegra SoC according to those more knowledgeable and experienced than I.

3. I recommend that you wipe cache/dalvik after you flash new build. Supposedly, the Nexus 9 internal flash file system gets slower over time and that wiping the flash and keeping as much free space available helps avoid the slowdown.
[Nexus 9 Android Development] diegz:
Hello! A question not truly related to your ROM:

I was trying to flash the latest build but everytime I try to format any partition from TWRP the device reboots.

Currently I'm on LOS14.1 and I have tried TWRP 302, 331 and 352.

What can it be? Is there a workaround to clear all the partitions and flash your ROM?

Thanks!
[Nexus 9 Android Development] bigflou:
You can perform a clean reinstall of the last official Google N9F27M ROM (https://developers.google.com/android/images#volantis).

With this method, you are ensure to get a really clean installation base because the installation script erase and reinstall everything including the bootloader, recovery, etc. and recreate all partitions correctly.

Then install a custom recovery, format partitions and install the LineageOS ROM.
[Nexus 9 Android Development] gk1984:
I'm curious if the hdcp from being disconnected is normal (see screenshot). This is regarding DRM support for video. I don't know enough about hdcp to make an assumption,orr even know what's normal for the N9.

I do know some years ago, the Nexus 9 was being dropped from Netflix support for HD streaming and that could be related to hdcp support but I'm not sure. Can you educate me about this a little or look into fixing this if it's not normal? Or perhaps it's just me?

I checked using DRM Info app
[Nexus 9 Android Development] odjinan:
just flashed the latest build, so far so good ;)

updated twrp to the latest version (twrp-3.5.2_9-0-flounder)

the current build (lineage-15.1-20210415-UNOFFICIAL-flounder) with its optional gapps companion (open_gapps-arm64-8.1-nano-20210502)

and a recommended wipe of dalvik/cache...

thanks!
[Nexus 9 Android Development] retiredtab:
Normally, monthly builds for my others roms go smoothly, but every once in a while, the monthly changes break something. This happened with the Nexus 9 for the May 5 security patches.

While compiling, it was giving

"SSL error when connecting to the Jack server."

After some dead ends and research, I found

Rebuild android code with error “SSL error when connecting to the Jack server. Try 'jack-diagnose”

System: ubuntu 18.04 environment：VirtualBox The first time I compiled the AOSP source code on Ubuntu 18.04, it passed, and the second time I compiled it failed. Here is an error message. [ 10% 538/...

stackoverflow.com

To fix this, you need to "Remove TLSv1, TLSv1.1 from jdk.tls.disabledAlgorithms in /etc/java-8-openjdk/security/java.security" file.

I'm adding this to the FAQ for future builders.

New build called lineage-15.1-20210511-UNOFFICIAL-flounder.zip

May 11, 2021 release notes

1. Incorporates May 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/309566

2. Whatever LineageOS changed since April 2021.

3. I recommend that you wipe cache/dalvik after you flash new build. Supposedly, the Nexus 9 internal flash file system gets slower over time and that wiping the flash and keeping as much free space available helps avoid the slowdown.
[Nexus 9 Android Development] euqilobaid:
Installed the ROM on the dusty tablet. It's working better than the first day. Thank you! Now kids have a device to play with. So far it's buttery smooth and stable. Didn't test much, but a few simple games work great.
[Nexus 9 Android Development] traceon:
Thanks for sharing the ROM! Works brilliant (even GPS, which was not working in LOS 14.1 for my device)!

If not mentioned before: the "Google assistant loop" in initial setup wizard can be avoided, if no Google account is added at that time. If you are stuck in that loop, do a factory reset (TWRP default swipe). Skip wizard and add account later, if needed.
[Nexus 9 Android Development] gk1984:
Actually, there's a better way to fix this but I don't recall exactly. I shared the details previously though. I think it's to install the Google Play Service APK from APK mirror instead of what's packaged with gapps. It's something where gapps version or build of Play Services is a little buggy for some reason.
[Nexus 9 Android Development] retiredtab:
New build called lineage-15.1-20210613-UNOFFICIAL-flounder.zip

June 13, 2021 release notes

1. Incorporates June 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/312243

2. Whatever LineageOS changed since May 2021.

3. I recommend that you wipe cache/dalvik after you flash new build. Supposedly, the Nexus 9 internal flash file system gets slower over time and that wiping the flash and keeping as much free space available helps avoid the slowdown.
[Nexus 9 Android Development] codebone:
Installed June 13 ROM! Everything off and running well! Thanks so much for maintaining this device!
[Nexus 9 Android Development] sarana1:
Just wanted to thank you for this. I was using a Magisk rooted stock, unencrypted, and it was always stalling out and/or rebooting mid-use, and sometimes factory resetting on startup lately. So far so good! We'll see over time, though. I appreciate the work!
[Nexus 9 Android Development] retiredtab:
If you were having that many problems with stock, I suggest you use TWRP to wipe everything (all partitions) so all the flash gets erased and format data. Wipe != format.

As I wrote in each release notes, it's reported that the Nexus 9 flash degrades over time and that wiping the flash and keeping as much free space possible helps mitigate the slowdowns. I have no proof of this. It's just based on what I read.
[Nexus 9 Android Development] linckandrea:
hi @retiredtab,

i recently bought a nexus 9

i noticed that lineageos flounder tree lacks some adjustments for oreo

in particular:

- powerHAL is bugged due to a missing initialization of some private field which leads to a broken boostpulse management

Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: Bad file descriptor

(and since nexus 9 doesn't have caf cpu-boost, this leads bad performance due to missing boost)

other thing which you can check here:

Commits · linckandrea/android_device_htc_flounder

Contribute to linckandrea/android_device_htc_flounder development by creating an account on GitHub.

github.com

(the zygote shim is very important)

also thanks a lot for the jack fix
[Nexus 9 Android Development] retiredtab:
@linckandrea, thanks for reaching out and letting me know about your github repo and some commits that I can add to make flounder better for everyone.

These types of posts are what I like to see, but occur very infrequently. I will look at your commits and try some out in a private build before sharing them for the July security patches.
[Nexus 9 Android Development] sarana1:
Yeah, I did all that - clean slate before I installed your OS, as you recommended. I also installed pico gapps, and am experimenting with reducing my google/stock app reliance. Maybe that will help? Already, just changing into a third-party app-sharing app - that always used to hang things - has improved its use. I plan on Ti backing up everything so I can just wipe and reinstall everything should it get laggy again. Still a good machine, especially for this financially underwhelmed dope! Thanks!
[Nexus 9 Android Development] Mr Smile:
Thank you so much, @retiredtab , for sharing the results of your work! I have read your FAQ, but I would still like to ask you to build a ROM for the LTE version.

I have two flounder_lte for my family (and a third test unit with partially broken digitizer) and would love to continue using them with up to date LOS 15.1 AND lte connectivity. I have looked at the build instructions, but unfortunately I lack both the general skills and a powerful computer to do this on my own.

So the only thing left for me is to ask for your help. Could you please make a build for flounder_lte like you do for flounder? I would promise not to make any demands. I would just like to test the lte build and of course share my results. If it works, great! If it bricks my already partially broken test unit, not so bad.

That would really be a great pleasure for me - and if it works most likely also for other flounder_lte owners.

Regards
[Nexus 9 Android Development] SirRGB:
SirRGB ROMs - Browse /Flounder_lte/lineage-15.1-20210706-UNOFFICIAL-flounder_lte at SourceForge.net

sourceforge.net

I have compiled los15.1 for flounder lte, so here you go. I have not tested it, because I have the wifi version. No patches are applied, but I disabled force-encryption.
[Nexus 9 Android Development] retiredtab:
New build called lineage-15.1-20210718-UNOFFICIAL-flounder.zip

July 18 release notes

1. First build to incorporate changes by Andrea as per

Commits · linckandrea/android_device_htc_flounder

Contribute to linckandrea/android_device_htc_flounder development by creating an account on GitHub.

github.com

GitHub - linckandrea/android_kernel_htc_flounder at lineage-15.1

Contribute to linckandrea/android_kernel_htc_flounder development by creating an account on GitHub.

github.com

GitHub - linckandrea/proprietary_vendor_htc

Contribute to linckandrea/proprietary_vendor_htc development by creating an account on GitHub.

github.com

2. Incorporates July 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/313627

3. Whatever LineageOS changed since June 2021.

4. I recommend that you wipe cache/dalvik after you flash new build. Supposedly, the Nexus 9 internal flash file system gets slower over time and that wiping the flash and keeping as much free space available helps avoid the slowdown.

Please note that I have had problems playing Clash Royale with Andrea's repos above including the July 18 build. I can only play 3 or 4 (10 or 15 minutes) games before it lags and completely locks up. I have reported this to Andrea for 15.1 and 16.0 (same problem). I can play Clash Royale on the "stock" builds, like the June 13 build, for 30 minutes with no problems.

If you have problems with the July 18 and didn't have the same problems with the June 13, please post them with adb logs.

To get an adb log, open a terminal

# clear the log first
adb logcat -c
# start log and send output to problem.txt
adb logcat > problem.txt
# reproduce problem
# wait 10 seconds and then stop adb logcat with ctrl-c

Upload the file as zipped (important to zip it and then upload here). For some reason, .txt files are not always visible as attachments here on xda.
[Nexus 9 Android Development] retiredtab:
I reloaded my June 13 build to finish the Clash Roayle tournament as was able to play 25 minutes with no crash, lag or problems. With the July 18 build, it crashed and lagged < 10 minutes so at least for my setup and Clash Royale, the July 18 build has something wrong with it.
[Nexus 9 Android Development] Jadelor:
Thanks for the heads up. Will delay updating.
[Nexus 9 Android Development] retiredtab:
New build called lineage-15.1-20210807-UNOFFICIAL-flounder.zip

Aug 9, 2021 release notes

1. Incorporates Aug 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/314577

2. Whatever LineageOS changed since July 2021.

3. Since there were no complaints about Andrea's branch, this is the continuation of it.

4. I recommend that you wipe cache/dalvik after you flash new build. Supposedly, the Nexus 9 internal flash file system gets slower over time and that wiping the flash and keeping as much free space available helps avoid the slowdown.

I continue to use my June 13 build for Clash Royale.
[Nexus 9 Android Development] AlexanderDG83:
Updated to this rom from the unofficial lineageos 14.1: everything works fine! 👍
[Nexus 9 Android Development] zys52712:
So I just flashed the new lineageos build from august, and it said that the tablet was encrypted, any idea why that would be? Flashed from stock rom with twrp 3.5
[Nexus 9 Android Development] SirRGB:
Well, did you dirty flash from an earlier build? Other roms encrypt by default, but this one has encryption disabled.
[Nexus 9 Android Development] zys52712:
Should've mentioned it, but before flashing this rom the tablet was stock, only flashed with fed-patcher then data format changed twice to get rid of the encryption on the stock rom
[Nexus 9 Android Development] SirRGB:
Well reformatting should get rid of encryption, no need to flash any patch.
[Nexus 9 Android Development] Sharangir:
New here. Made an account because I'm somewhat stuck and was wondering if you could help me out.

I want my Nexus 9 to run Android 8 or newer, so I searched for a working Lineage OS build and stumbled upon yours.

Since I bricked it while trying to get a 16.1 build to work (that probably was never tested on the Nexus 9), I first followed the guide to flash factory Android again. https://xdaforums.com/t/guide-nexus-9-back-to-stock-guide-unbrick-restore-factory-firmware.2975668/

Then I did all those things, flash TWRP, etc. and managed to flash your ROM too.

It starts and it works, looks really nice too. Great job!

I then realised that there's no Playstore. (But I need it because I want to use the Tablet for work, running Nikon Snapbridge or qDSLR dashboard, or anything other that works as a jpg playback app for wifi transfer files from my DSLR. )

So I downloaded the GAPPs 8.1 ARM64 nano build and installed that one in TWRp.

Tablet still boots, but after that, all hell breaks loose. I get literally hundreds of pop-ups telling me that Google play services (and all other kinds of google stuff) stopped working. Canceling the app doesn't help, it just comes back over and over again.

I also couldn't log-in to my Google Account.. it would either just not react when I click on the green "Login" button, or get stuck on the screen for the setup process. I could always go back to the main menu to look at more of those error pop-ups.

Now, I just wiped everything once again and set up factory Android. I'll flash TWRP again and put on the LOS 15.1 again, but am afraid of trying the GAPPs again, because it takes me half an hour to do the whole stuff all over again.

So I have 2 questions:

1. Is it possible to transfer the LineageOS install file onto the tablet after cleansing it? (Because my tablet is recognised as "charging only" as a stock function and does only show data when I actively switch this in the android menu. (And to get there, I have to install factory android and run through setup and all...)

Or is it possible to just install the LineageOS ROM from my adb-fastboot folder like I do with the factory data?

2. Is it possible to only remove the GAPPS and basically revert back to the naked LOS 15.1 if the GAPPs installation doesn't work like it did the first time?

Kind regards and sorry for the long text.

EDIT: I figured it out. Had to format data before the flashing of the GAPPs and sideloaded gapps via twrp sideload in adb.
[Nexus 9 Android Development] gk1984:
Been trying the updated for a while. I wanted to mention the change in July did negatively impact performance. my N9 was more responsive in June and earlier.
[Nexus 9 Android Development] SirRGB:
@retiredtab I think the og lineage trees might be better performance wise...
[Nexus 9 Android Development] retiredtab:
@SirRGB , it's easy enough for me to reverse the manifest back to original. What have you noticed to make you say the original is better?

BTW, the Sept 5 security patches are active, but not yet merged. Once merged, I can make a new build.
[Nexus 9 Android Development] gk1984:
Everything is slower for me and things freeze frequently. They eventually work, but it requires a lot of patience.
[Nexus 9 Android Development] SirRGB:
Well, @gk1984 noticed too and you are using june build too, so ig there must be a difference. I havent really noticed a difference, because I dont use my N9 that much anymore...
[Nexus 9 Android Development] retiredtab:
I compiled the Sept 5 patches into my own build using the "stock" Nexus 9 code found on the LineageOS github and was able to play Clash Royale for 30 minutes with no lag or pauses. Once the Sept 5 patches are officially merged, I will upload the new build. That is, the Sept 5 build will remove all of Andrea's commits.

I'm waiting for these Sept 5 patches to be merged.

https://review.lineageos.org/q/topic:"O_asb_2021-09"+(status:open OR status:merged)
[Nexus 9 Android Development] retiredtab:
The 15.1 Sept 5 patches have finally been merged into github today (Sept 24) so I can do the build. New build called lineage-15.1-20210924-UNOFFICIAL-flounder.zip

Sept 24, 2021 release ntoes

1. Incorporates Sept 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/316179

2. Whatever LineageOS changed since August 2021 (about 1,800 files had to be recompiled).

3. This build is based on "stock" and not using Andrea's repos as it was reported to cause some slowness in operation.

4. I recommend that you wipe cache/dalvik AND cache in TWRP after you flash new build. Supposedly, the Nexus 9 internal flash file system gets

slower over time and that wiping the flash and keeping as much free space available helps avoid the slowdown.

5. During first boot, the Google white logo may display up to 3 minutes. DO NOT PANIC. It will eventually start LineageOS boot animation and the Sept 24 build WILL load (I test ALL my builds to make sure they boot and work as post #1). I don't know why it takes up to 3 minutes now as there's no logcat output during that stage.

PS. With the Sept 24 build, I have no problems playing Clash Royale for 30 minutes straight as there's no lag or freezing.
[Nexus 9 Android Development] belegdol:
I am trying to update but I cannot unlock my phone in TWRP after enabling encryption. Is this a known problem? TWRP says "Password failed, try again".
[Nexus 9 Android Development] gk1984:
Night and day difference in performance. Way better with this update. Thanks!
[Nexus 9 Android Development] retiredtab:
The Oct 5 patches are not yet officially merged as of Oct 11, but I decided to build them early because the Nexus 9 code and another device that I build share the same hard drive and I already built the latter. Thus, I don't have to switch out hard drives again in my "build" server and can set aside this drive until next month.

Oct 11, 2021 release ntoes

1. Incorporates Oct 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/317622

2. Whatever LineageOS changed since September 2021 (about 2,400 files had to be recompiled).

3. This build is based on "stock" and not using Andrea's repos as it was reported to cause some slowness in operation.

4. I recommend that you wipe cache/dalvik AND cache in TWRP after you flash new build. Supposedly, the Nexus 9 internal flash file system gets

slower over time and that wiping the flash and keeping as much free space available helps avoid the slowdown.

5. During first boot, the Google white logo may display up to 3 minutes. DO NOT PANIC. It will eventually start LineageOS boot animation and the Oct 11 build WILL load (I test ALL my builds to make sure they boot and work as post #1). @razorloves, who is making monthly 14.1 Nexus 9 builds, believes the delay when it's showing the Google white logo might be due to fsck running a check on all the storage file systems.

6. With the Oct 11 build, I have no problems playing Clash Royale for 30 minutes straight as there's no lag or freezing.
[Nexus 9 Android Development] zeroxia:
Does this ROM work with `scrcpy`?

GitHub - Genymobile/scrcpy: Display and control your Android device

Display and control your Android device. Contribute to Genymobile/scrcpy development by creating an account on GitHub.

github.com
[Nexus 9 Android Development] FrzHrzn:
I think any rom will work with scrcpy
[Nexus 9 Android Development] zeroxia:
Not necessarily, `scrcpy` seems to have some requirements on the video encoding capability.

My personal experience is with this LineageOS it failed with similar error like this:

Exception on thread Thread[main,5,main] · Issue #947 · Genymobile/scrcpy

Model: MiPad4 Plus OS: LineageOS 17.0 based on Android 10.0 INFO:scrcpy 1.11 <https://github.com/Genymobile/scrcpy> C:\******\scrcpy-win64-v1.11\scrcpy-server: 1 file pushed. 3.9 MB/s (25454 bytes ...

github.com
[Nexus 9 Android Development] FrzHrzn:
Hmm...You're right, scrcpy does fail on this rom, reporting dome video encoder errors.
[Nexus 9 Android Development] retiredtab:
I can't find an official announcement, but it seems that official Android security patches for 8.1 may have ended Nov 2021. The bulletin for Oct 2021 still shows 8.1 at

https://source.android.com/security/bulletin/2021-10-01

while the Nov 2021 shows no 8.1 because this is the first month that 12.0 patches are out.

https://source.android.com/security/bulletin/2021-11-01

If that's the case, we have to rely/wait on LineageOS developers to backport the patches to 8.1. The Nov 2021 patches have already been ported to 7.1 or LineageOS 14.1 by Basil Gello as per

https://review.lineageos.org/q/topic:"n-asb-2021-11"+(status:open OR status:merged)

I monitor

https://review.lineageos.org/q/status:open

daily to see what's changed. Once/if someone volunteers to do the backport to 8.1 and it's merged, then I will make the next 15.1 build.
[Nexus 9 Android Development] SkewedZeppelin:
I backported the 2021-11 ASB to 15.1 for use in DivestOS:

From my emails to Lineage team:
[Nexus 9 Android Development] retiredtab:
@SkewedZeppelin , thanks for sharing your patches.

I was actually going to wait until after the Dec 5 patches for 16.0 and 14.1 were up on gerrit and then try to merge Nov and Dec 5 patches all into one build. I was hoping someone on gerrit would do it, but cherry picking the 16.0 and/or 14.1 Nov and upcoming Dec patches seems doable for 15.1.