yashsingh1/xdaforums huggingface dataset:
[Nexus 9 Android Development] retiredtab:
New build called lineage-15.1-20211209-UNOFFICIAL-flounder.zip

Dec 9, 2021 release notes

1. Incorporates Nov 5 and Dec 5 security patches as per https://review.lineageos.org/q/topic:P_asb_2021-11 and https://review.lineageos.org/q/topic:n-asb-2021-12. Specifically

Nov 5th

https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/318648
https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/318649
https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/318650
https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/318651
https://review.lineageos.org/c/LineageOS/android_packages_apps_Contacts/+/318654
https://review.lineageos.org/c/LineageOS/android_packages_apps_Settings/+/318655
https://review.lineageos.org/c/LineageOS/android_build/+/318658

Dec 5th

https://review.lineageos.org/c/LineageOS/android_external_tremolo/+/319986
https://review.lineageos.org/c/LineageOS/android_frameworks_av/+/319987 --> slight problem merging due to 14.1 and 15.1 code differences
https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/319988
https://review.lineageos.org/c/LineageOS/android_packages_apps_Contacts/+/319989
https://review.lineageos.org/c/LineageOS/android_packages_apps_KeyChain/+/319990
https://review.lineageos.org/c/LineageOS/android_packages_apps_Settings/+/319991

2. Whatever LineageOS changed since Oct 2021 (about 4,300 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 build WILL load (I test ALL my builds to make sure they boot and work as post #1).

6. With the Dec 9 build, I have no problems playing Clash Royale for 30 minutes straight as there's no lag or freezing.
[Nexus 9 Android Development] retiredtab:
Looks like another patch got added to the Dec 5th patches. This was added Dec 15th.

https://review.lineageos.org/c/LineageOS/android_system_bt/+/320420

I'll incorporate the above patch into the Jan 5th 2022 build. There's no sense making yet another build only 7 days later.

As of Dec 15th, the Dec 5th patches for Android 9 or LineageOS 16.0 have yet to appear on gerrit.
[Nexus 9 Android Development] retiredtab:
Good news! It looks like Kevin Haggerty is back porting the Android 8 or LineageOS 15.1 patches as per

https://review.lineageos.org/q/topic:O_asb_2021-12

They were just posted today, Dec 17, 2021.

He's combining both the Nov and Dec 5 patches all rolled up into the above. Hopefully, he will continue for January 2022? If yes, I will wait for his January 2022 patches before making the next build.
[Nexus 9 Android Development] SkewedZeppelin:
You should consider integrating these 350+ security patches into your next build.

Just git clone this repo and point $DOS_PATCHES_LINUX_CVES to it.
[Nexus 9 Android Development] retiredtab:
Thank you, I'll keep that in mind for future releases.
[Nexus 9 Android Development] retiredtab:
New development from Kevin. Seems that official patch will stay at Oct 5, 2021 from what I can tell in the comments at

https://review.lineageos.org/c/LineageOS/android_build/+/320334

I don't know what will happen now for Jan 5 patches. They may get unofficially incorporated, but the patch date will stay at Oct 5, 2021.

Quoting Kevin.

"lineage-15.1 is officially discontinued, so this is as good as an official announcement. That aside, it is irresponsible to bump a patch level when there is no more assessment being performed by the group that defines the patch levels. It's entirely possible, certain even, that there are vulnerabilities in <= A8.1 that are reported and unfixed in A8.1 that would be documented in an ASB if Google still maintained the branch. Bottom line, there is no such thing as a set of changes to A8.1 that make up anything beyond 2021-10-05. Bumping the patch level should never have been done in the past on any other branches."
[Nexus 9 Android Development] retiredtab:
Kevin also wrote

"There is no such thing as an assessed 2021-12-05 security patch level for anything less than Android 9.0. There will be no further SPL updates for lineage-15.1."

SPL = security patch level. So I don't know if that means he won't do a Jan 5 patch or not. I will wait to see. If he doesn't do it, then I will attempt to carry on by looking at the 16.0 and 14.1 patches in 2022.
[Nexus 9 Android Development] SirRGB:
Great to see that you still have at least some hope for our device. I had lineage 16.0 as my daily driver for Telegram and very light gaming and it worked, also enforcing, didnt use it that much though. Media consumption e.g. Netflix or YT (Yt vanced) is mediocre, except Newpipe.

Built some A7 roms btw, still untested.
[Nexus 9 Android Development] asuka1523:
I got this issue when I'm trying to sideload this ROM. My device is 32Gb WiFi.
[Nexus 9 Android Development] Captain_Throwback:
What TWRP version? If it's not the latest (3.6.0 as of this post), then try updating.
[Nexus 9 Android Development] asuka1523:
My bad, I didn't read all the FAQ before doing, got an ancient version of TWRP (3.0.2-1). Updated and now it worked. Thank you so much.
[Nexus 9 Android Development] Jadelor:
Love a lot how this ROM gave life to my niner. Using it as a Steam Link device for light gaming now. Thank you, retiredtab.
[Nexus 9 Android Development] ThatDragon:
Hey, just wanted to say that your ROM is working great for me!

I've switched over from razorloves good 14.1 ROM because of the newer lineageos version and newer security updates.

Always wanted to try 15.1, but there wasn't a ROM with working hardware acceleration when I checked a long time ago.

I hope there will be future security updates. There seem to be some issues from what I've read.

Anyways, thanks!
[Nexus 9 Android Development] retiredtab:
New build called lineage-15.1-20220128-UNOFFICIAL-flounder.zip

Jan 28, 2022 release notes

1. Incorporates Jan 5 security patches as per https://review.lineageos.org/q/topic:O_asb_2022-01

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

3. I completely resynced back to stock LineageOS so the security patch will show Oct 5, 2021 as that was the last official Android 8 patches from Google.

4. The security patch string will permanently stay at Oct 5, 2021 as per Kevin's message at

https://review.lineageos.org/c/LineageOS/android_build/+/320334

"lineage-15.1 is officially discontinued, so this is as good as an official announcement.

That aside, it is irresponsible to bump a patch level when there is no more assessment being performed by the group that defines the patch levels. It's entirely possible, certain even, that there are vulnerabilities in <= A8.1 that are reported and unfixed in A8.1 that would be documented in an ASB if Google still maintained the branch. Bottom line, there is no such thing as a set of changes to A8.1 that make up anything beyond 2021-10-05. Bumping the patch level should never have been done in the past on any other branches."

5. So despite what the security string says, this Jan 28th build includes the unofficial Google Nov and Dec 2021 patches in addition to the Jan 5th 2022 patches.

6. 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.

7. 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 build WILL load (I test ALL my builds to make sure they boot and work as post #1).

8. With the Jan 28, 2022 build, I have no problems playing Clash Royale for 30 minutes straight as there's no lag or freezing.

9. For those upgrading from my 15.1 2021 builds, there may be a problem after flashing the 2022 builds with respect to screen password, pattern or pin unlock. Three people have reported that the screen unlock doesn't work when doing the above (i.e. from the Dec 5. 2021 to Jan 5, 2022 security patches).

If you have screen lock enabled, I recommend you remove it first from the current running OS, then boot into TWRP, do the upgrade and then put the screen lock back on after it boots.
[Nexus 9 Android Development] sandemans:
Where could I download the lineage-15.1-20220128-UNOFFICIAL-flounder.zip? Thanks
[Nexus 9 Android Development] Captain_Throwback:
Read the OP.
[Nexus 9 Android Development] retiredtab:
Regarding the CVE kernel patches that @SkewedZeppelin wrote about, I will make another build today or tomorrow and test them out. I looked through some of the CVEs briefly and some of them don't even apply to our platform. For example, there's a CVE for the IBM S390 mainframe.

I think it's because it's "best practice" to merge all the CVE patches regardless if they apply to your platform or not so that future merges of code is more clean. I could be wrong on this, but that's my understanding after seeing

https://wtarreau.blogspot.com/2017/11/look-back-to-end-of-life-lts-kernel-310.html

and some other things I read.

If the CVE kernel build works well for me, I will incorporate them into the Feb 5 security patches.
[Nexus 9 Android Development] sandemans:
Hi there.

Iam watching an episode in hbomax and when in the third episode the tab appear to stop. I have the last lineage 15.1.

What can I do? It is a ram,video problem?

Regards
[Nexus 9 Android Development] gk1984:
Just flashed the January 28th update (is that the correct date?). Finding a bug unlocking the tablet now. Entering my unlock pattern goes to a black screen, then back to the unlock screen. I'm unable to navigate to any other menu. Fortunately, I can switch users from the lock screen and verify everything works. I'm too afraid to turn a lock pattern, pin, or password on for the other user in case that gets locked out. I'm downgrading as I type this. Hoping that fixes things for now.
[Nexus 9 Android Development] retiredtab:
Yes.

I cannot replicate. I add a pattern and have no problems locking and unlocking pattern including a reboot of the Nexus 9. The Jan 28 build is completely "stock" other than the removing the encryption (FAQ9) and the hardware acceleration (FAQ12) + all the security patches up to and including Jan 5, 2022.
[Nexus 9 Android Development] Captain_Throwback:
I had the same problem. I just removed locksettings in TWRP so I could get to the home screen and left the tablet without a lock. It would be nice to get it fixed, I agree.
[Nexus 9 Android Development] retiredtab:
I cannot replicate. Can you be more specific in which grid pattern you used? For example, 3x3, 4x4, 5x5 or 6x6?
[Nexus 9 Android Development] Captain_Throwback:
I don't use pattern. I had a password.
[Nexus 9 Android Development] Captain_Throwback:
I can confirm that adding the password back works fine, so it seems like it was only a problem when upgrading. Not sure why two of us had the same glitch and you didn't, but it's okay now that I deleted the locksettings. I think it may have gotten corrupted during the upgrade.
[Nexus 9 Android Development] retiredtab:
I still can't replicate with either pattern, pin or password. Strange.
[Nexus 9 Android Development] retiredtab:
Well that's good news.

I looked through the Jan 5 security patches and there's nothing obvious to me that any of those patches would affect the lock screen settings.

It's possible. Also, my Nexus 9 has very little apps (no gapps) on it and I always do the wipe dalvik/cache and cache partition after an upgrade.
[Nexus 9 Android Development] retiredtab:
Of course, there could have been some Google AOSP changes to 8.1 or LineageOS 15.1 changes since Dec 5th security patches that would affect the above that I'm not aware of. We will have to see if the problem exists for the Feb 5 security patches or not.
[Nexus 9 Android Development] Jadelor:
Reporting that I had the same problem with a 3x3 pattern. Fixed by removing pattern for update and adding it back.
[Nexus 9 Android Development] retiredtab:
I'll add the following to my Jan 28, 2022 release notes and all other future release notes.

For those upgrading from my 15.1 2021 builds, there may be a problem after flashing the 2022 builds with respect to screen password, pattern or pin unlock. Three people have reported that the screen unlock doesn't work when doing the above (i.e. from the Dec 5. 2021 to Jan 5, 2022 security patches).

If you have screen lock enabled, I recommend you remove it first from the current running OS, then boot into TWRP, do the upgrade and then put the screen lock back on after it boots.
[Nexus 9 Android Development] retiredtab:
Today, Feb 7, 2022, the unofficial security patches for Jan 5, 2022 were merged into the 15.1 repos as per

https://review.lineageos.org/q/topic:O_asb_2022-01

by Kevin around 07:44 AM.

So far, none of the Feb 5 security patches have shown up in gerritt yet for the Google "supported" Android 9, 10, 11 and 12 . Kevin usually does the security patches.
[Nexus 9 Android Development] bonks60:
Hi,

I'm back on my N9 (wifi), and it's really laggy.

Which ROM do you advise to install ?

Is an old battery, certainly damaged by all this time, a reason for this laggy experience ?
[Nexus 9 Android Development] SirRGB:
Id recommend lineage 14.1 or this 15.1, because those are the only one still getting updated rn.

For checking battery health you can install accubattery.
[Nexus 9 Android Development] bonks60:
Thanks for your feedback (y)
[Nexus 9 Android Development] retiredtab:
For those thinking of dropping 14.1 and 15.1 and going to 16.0 because Android 7 and 8 security patches are no longer officially updated by Google, it looks like Android 9 might be now dropped from the February 5 security patches.

Published sometime after post #123 of mine above, I found this today (Feb 8)

https://source.android.com/security/bulletin/2022-02-01

There's no mention of Android 9 (LineageOS 16.0) in the Feb security patches. Either Google dropped 9 or there's no security patches that are applicable to the Android 9 branch which I think is highly unlikely.
[Nexus 9 Android Development] pixelodin:
Hi @retiredtab I was trying to contact you from your profile but it seems you have restricted you profile to viewing which I don't understand why? Please do let know know why is that But anyways I want to tell you I have nexus 9 as well and you mentioned somewhere in your post in anyone is interested in helping out in this project for nexus 9 to contact you so anyways I am interested as I have the same device and would love to work with you to build lineage os and other custom ROMs and fix issues, Please let me know
[Nexus 9 Android Development] retiredtab:
Kevin posted some unofficial 16.0 Feb 5 patches on gerrit today (Feb 13)

https://review.lineageos.org/q/topic:P_asb_2022-02

14.1 unofficial Feb 5 patches are also posted by "L R"

https://review.lineageos.org/q/topic:n-asb-2022-02

Just got wait our turn for 15.1 Feb 5, 2022 patches. I also incorporated the 300+ CVEs from DivestOS into my January build and been using it for the last couple of weeks. So far, no problems with general usage + Clash Royale for 30 minutes, so they will likely make it into the Feb build whenever the Feb 5 patches get uploaded.
[Nexus 9 Android Development] desmayas:
thank a lot
[Nexus 9 Android Development] belegdol:
I hit the lock screen issue as well. I tried deleting locksettings in TWRP but unfortunately I cannot decrypt storage in TWRP either, it says unable to mount storage or failed to decrypt data. Am I hosed, or can this be recovered from?

ETA: I rolled back to the December build, removed the lock screen, rebooted to TWRP and installed the February build again. Unfortunately, after subsequent reboot, the tablet accepted the boot password but said that the filesystem is corrupted and offered to get restored to factory settings, which I did.
[Nexus 9 Android Development] SirRGB:
hm, I found this in the lineage 16.0 branch, maybe it will help with the issues on P too? I might try at some point...

https://review.lineageos.org/c/LineageOS/android_bionic/+/268655
[Nexus 9 Android Development] retiredtab:
I already tried that in my own 16.0 builds last year and it makes no difference with Clash Royale and the lag that follows after about 10 minutes. That repopick is in my 15.1 builds and I have no problems with it and Clash Royale.
[Nexus 9 Android Development] retiredtab:
As you can see, there hasn't been any security patches since Feb 2022 for the 15.1 rom because Google doesn't support Android 8 anymore and LineageOS is not backporting them to gerrit. Since my last 15.1 build almost one year ago, there have been 710 downloads of the Feb 24, 2022 rom.

Unknown to me, DivestOS has been backporting Android 8 patches into it's Nexus 9 builds. I didn't realize that until late Dec 2022. See

https://divestos.org/pages/devices#device-flounder

When working on another LineageOS device where there was some overheating problems in January 2023, I decided to revisit Nexus 9 16.0 and see if I could fix my problem with severe lag after 15 minutes of playing Clash Royale. After looking over the commits and another year of knowledge/experience, I found 3 that I reverted and to my surprise, I could play Clash Royale over 30 minutes with no lag.

I've decided to share this 16.0 build, but it comes with a huge caveat. You can read more about it in the 16.0 thread at

https://xdaforums.com/t/unofficial-alpha-lineageos-16-0-for-nexus-9-wifi-feb-19-2023.4555873/

I'm NOT going to make any more 15.1 builds. If you want an up to date security patch build and don't need any Google services, have a look at DivestOS. If you want to build 15.1 LineageOS with the latest security patches, you can look at DivestOS github for those monthly security patches at

https://github.com/orgs/Divested-Mobile/repositories

and build it yourself.
[Nokia 7 Plus Questions & Answers] 2gg1:
But is it any useful too like glitch oem unlock on it? Or something else?

Edit: i thought they removed it
[General Questions and Answers] Alessiomiccoly:
Hi guys, I'd like to use wifi and LTE simultaneously becouse I need LTE connection when I connect my phone to wifi without internet access. I have a huawei p30 pro New edition. Who can help me?
[General Questions and Answers] galaxys:
Hi, maybe check your phones forum section for assistance, support, guides, etc. here:

Huawei P30 Pro

The Huawei P30 Pro is a 6.47" phone with a 1080x2340p resolution display. The Kirin 980 chipset is paired with 6/8GB of RAM and 128/256GB of storage. The main camera is 40+20+8MP and the selfie camera is 32MP. The battery has a 4200mAh capacity.

xdaforums.com
[Android Head-Units] OrBen:
Hi everyone,

I have the following car head unit:

ProcessorType: QuadCore-T3

Android version: 6.0.1

MCU version: T5.3.19-11-00-453101-180625

System version: V8.2.3_20190615.103055_KED18-0395-i145

DVD version: 2.13.15-860mc-160106

I'm trying to manually install an APK file that I downloaded from the device Chrome browser and it says I need to allow installation from unknown sources.

The problem is when I'm trying to allow it by clicking to the button in the security settings it ask for a password which I don't know.

I tried everything I found to the internet and at this forum but nothing.. :/

Do you have any ideas?

Thanks!
[Android Head-Units] Extrucker11:
maybe try your play store password.....i dont have the unit but ive never had a time when i ve changed setting to allow unknown sourses
[Android Head-Units] OrBen:
Im not logged in to play store / gmail account and didn't set any kind of password on the unit.
[Android Head-Units] Extrucker11:
try another apk and see if it happens again with that one or check the app that your trying to install has that got a password to install it from the site you downloaded it from
[Android Head-Units] ludditefornow:
Try the codes in this thread.

https://xdaforums.com/t/list-of-factory-codes-for-android-head-units.4240053/#post-84571191
[Xiaomi Mi 10 Questions & Answers] horvalos:
Hello everyone,my Mi 10 has very low volume on notifications (calls, notifications,alarms) although I've set it to max..Its too low sometimes i miss calls or messages..anyone else with the same problems?or any solution?
[Xiaomi Mi 10 Questions & Answers] shivadow:
Try a louder ring tone? Have you cleaned the speakers recently? Could be anything.
[Xiaomi Mi 10 Questions & Answers] horvalos:
I've tried everything,louder ringtone, I've played a video from YouTube for cleaning speakers but it's not the speaker its something from the ui because when i see a video from YouTube or gallery its so loud that i have to lower the volume...its like the system volume its low...
[Xiaomi Mi 10 Questions & Answers] shivadow:
Access developer settings and activate "disable absolute volume control".

I have a niggling feeling that'll be it..
[Xiaomi Mi 10 Questions & Answers] horvalos:
Thank you very much for your help, unfortunately can't find this settings in developer options..maybe they delete it in miui12... :/
[Xiaomi Mi 10 Questions & Answers] shivadow:
The option is there. I have it myself. You need to scroll down a bit.
[Xiaomi Mi 10 Questions & Answers] horvalos:
Nope can't find it... I'll attach a screenshot of my developer options
[Xiaomi Mi 10 Questions & Answers] FernanZ:
I don't have that option either. I'm on Global 12.2.1.0 Stable
[Xiaomi Mi 10 Questions & Answers] shivadow:
I concur, it's definitely not there. In older versions it was the first option under the USB section, should have been under Bluetooth as in other phones..

Odd. Very odd. Obviously you've tried setting a known high volume ringtone as a notification and had the same low volume results? The only suggestion I have at the moment is to clear the cache of all apps and reboot.. See if it persists..
[Xiaomi Mi 10 Questions & Answers] horvalos:
Yes...the same sound playing from music app its very loud...when i set it for call/sms/notification its very very low... :/ You suggesting to wipe everything from the boot screen?
[Xiaomi Mi 10 Questions & Answers] shivadow:
If you are on stock rom you can wipe the cache from the security app or via fastboot.

If you are on custom rom you can either download an app to do it or do it via fastboot.

DO NOT WIPE ANYTHING ELSE. ONLY WIPE CACHE.
[Xiaomi Mi 10 Questions & Answers] horvalos:
No im on stock rom,if i wipe the cache I'll loose data from all apps?

Edit:

Sorry for my mistake about loosing data,i cleaned the cache through security app did reboot but nothing...its clearly a bug because its only in system sounds that are low,as i said when playing the ringtone through music app is clearly louder...anyway thanks a lot @shivadow
[Xiaomi Mi 10 Questions & Answers] shivadow:
In all honesty being on a custom rom is probably 99% of the problem. You can always investigate adjusting volume files in root, if at all possible. Some are, some aren't.
[Xiaomi Mi 10 Questions & Answers] akash45:
Hi try this app, This might work for you.

It will increase ringtone volume to 100% before receiving normal call.

P.S tested on galaxy devices.

https://xdaforums.com/t/...olume-increase-before-receiving-call.4277677/
[Xiaomi Mi 10 Questions & Answers] Abdul Rafé:
Just bought Mi 10 from my friend. Its 3 4 months used. I am also facing the same issue. Notification/ringtone volume is too low. Is this normal ? I have factory reset. Tried every thing. Any solution ?