Related
Presenting CM13 unofficial. Built from mostly pure CyanogenMod sources, with a few tweaks that I try to keep updated on my github. This is only possible due to the work of Ziyan and MWisBest.
Instructions
First time flashing CM13 to your toroplus (or coming from another ROM)?
Unlock & install a recovery
Wipe data & cache partitions
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Updating from a previous build?
Just install the latest ROM zip. If you had Google Apps installed, they will be reinstalled automatically.
Click to expand...
Click to collapse
Downloads
Latest cm-13.0 build: https://www.androidfilehost.com/?fid=24588212152305191
Final cm-12.1 build: https://www.androidfilehost.com/?fid=24438995911970260
All builds: https://www.androidfilehost.com/?w=files&flid=23531
Unofficial TWRP recovery: https://www.androidfilehost.com/?fid=24459283995311440
Google Apps: http://opengapps.org/
- Platform: ARM
- Android: 6.0
- Variant: pico (recommended), or nano
Bugs
LTE Data does not work. (3G works)
XDA:DevDB Information
UNOFFICIAL CyanogenMod 13.0 (DDK 1.9), ROM for the Samsung Galaxy Nexus
Contributors
musical_chairs
Source Code: https://github.com/CyanogenMod
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Beta
Created 2014-09-25
Last Updated 2016-07-15
now with Marshmallow!
Will this be updated to work with the new GPU drivers? Thank you!
Sent from my LG-LS980 using XDA Free mobile app
illinoissparks18 said:
Will this be updated to work with the new GPU drivers? Thank you!
Sent from my LG-LS980 using XDA Free mobile app
Click to expand...
Click to collapse
Short answer: yes. I'm going to try grabbing the relevant code from MWisBest's githib. If it turns out to be too involved for my limited skills, it will have to wait until Ziyan submits the changes to CM.
musical_chairs said:
Short answer: yes. I'm going to try grabbing the relevant code from MWisBest's githib. If it turns out to be too involved for my limited skills, it will have to wait until Ziyan submits the changes to CM.
Click to expand...
Click to collapse
OK I am going to be on board with testing for sure. I left a post in the now no longer current official thread that I flashed the last official build yesterday and I had perfect 3G to LTE to 3G handoff, rock solid WiFi strength, basically everything seemed to work very well. I am looking forward to seeing how things progress. I haven't been able to keep any of the official CM builds from bootlooping until now. Hopefully you stick with it because I am getting better performance from this device than I have seen in a long while
Sent from my Galaxy Nexus using Xparent Gray Tapatalk 2
musical_chairs said:
Short answer: yes. I'm going to try grabbing the relevant code from MWisBest's githib. If it turns out to be too involved for my limited skills, it will have to wait until Ziyan submits the changes to CM.
Click to expand...
Click to collapse
Awesome!! Thank you!!
Sent from my LG-LS980 using XDA Free mobile app
I should've had a machete to hack through the jungle of build errors from pulling a modified OmniROM device tree into a CyanogenMod build. Looks like the build is rolling now though, with any luck it might just complete successfully - who knows, it might even boot.
The only thing slower around here than me is my poor old computer.
Its kind of ironic that the Galaxy Nexus was the first official LTE device for Sprint and I am only just recently starting to get LTE on a semi regular basis.
@musical_chairs, take your time with your builds. I assure you that they are appreciated. Now that this device is actually getting decent (for Sprint) signal and still has current builds makes it more enjoyable to use than just about any time I can remember....I just miss Imoseyon's Lean kernels. I got GREAT battery on those. They were compiled in the now deceased (I think) CMRemix ROMs but the LTE is definitely a plus
Update: For now, I have stopped working on building CyanogenMod with the DDK 1.9 drivers. I was ending up with a completely unsustainable mess of a device tree, and was still running into build errors. If new drivers are what you want, use FML. I'll focus on keeping the regular CM builds updated for the time being.
musical_chairs said:
Update: For now, I have stopped working on building CyanogenMod with the DDK 1.9 drivers. I was ending up with a completely unsustainable mess of a device tree, and was still running into build errors. If new drivers are what you want, use FML. I'll focus on keeping the regular CM builds updated for the time being.
Click to expand...
Click to collapse
Link to toroplus build for fml?
Zeinzu said:
Link to toroplus build for fml?
Click to expand...
Click to collapse
I'm following its developements, but haven't had time to try it personally yet.
http://forum.xda-developers.com/galaxy-nexus/sprint-develop/rom-fml-fork-life-10-13-2014-t2903695
Thanks for trying anyhow. I'm glad cm11 still has a fighting chance with the GNex, thanks to you, and all the others who are able to help out.
We're all waiting for cm12 to get to a buildable state. In the meantime, I've been working on upgrading my build box. My old machine was just barely capable of building android, the 'new' one isn't new but it was a real beast in its day. Time for a clean build has dropped from a day and a half to two and a half hours. I'm happy...
jd14771 said:
just curious, how difficult is it to compile roms? Do you need to know how to write your own code or is it over glorified copy and pasting with packages and stuff?
Click to expand...
Click to collapse
I do a lot of copying and pasting, a lot of reading guides, and a whole lot of google-ing. I don't know how to write my own code, but I have lots of experience with applying patches. Compiling roms is not that hard if you're a Linux user, have a working knowledge of the command line, and have a basic understanding of git. Take away any one of those things and it becomes a whole lot harder.
jd14771 said:
Yeah i haven't gotten to play with linux, nor do i know what git's are (i think they are large batch's of code posted in plain text?) . always wanted to try but don't have the time.
Click to expand...
Click to collapse
git is the software the devs use to keep track of changes in the code. Most Android devs have their git repositories on Github, those are probably what you are thinking of. Every little change (called a 'commit') has its own unique hash number. It's pretty amazing, you can look through somebody else's commits and find one that fixes a bug you are working on, or split tens of thousands of changes in half, then in half again, then in half again, etc., and pinpoint the exact commit that causes a bug on your system - though that's more useful in Linux kernel development than in Android.
I don't really have the time either, but it's such a fun hobby...
Using quickboot?
Coming from Vanir. Really like the facility quickboot gives. Anyone "enabled" it? I can't seem actually show the field to turn it on. Settings search finds it, but that's it... Noticed Dev options is hidden also. What's up?
Props for keeping CM11 updated. Really like I can actually use SMS in Hangouts.
I haven't been following the nightly changes since toroplus went dark, but I ran a build today--nothing special, just the latest cm...whatever changes they are. I could post it but don't know if I should make another thread or just link to it in here.
Anything substantial get added to general cm in the last few months?
I tried to run a build of cm12 but it looks like things still aren't ready for building yet, either that or I'm not sure how to switch back and forth between the cm11 repo and cm12 without getting repo update errors.
yotvb531 said:
I tried to run a build of cm12 but it looks like things still aren't ready for building yet, either that or I'm not sure how to switch back and forth between the cm11 repo and cm12 without getting repo update errors.
Click to expand...
Click to collapse
I got cm12 built and booting for toro for the first time today. I'm trying to get mobile data working on that, then I'll give toroplus a shot. Looks like it shouldn't be too much trouble. Feel free to post any of your builds here, or start your own thread if you prefer.
Here's my cm11 build from yesterday--equivalent to a plain nightly. It's been running fine since I dirty flashed it last night. Md5sum is linked as well and noted below.
https://www.dropbox.com/s/lp4j3yayuktmlot/cm-11-20141227-UNOFFICIAL-toroplus.zip?dl=1
https://www.dropbox.com/s/z1b72j7oh70eg5w/cm-11-20141227-UNOFFICIAL-toroplus.zip.md5sum?dl=1
MD5 Sum: e6c265c57e00b4949362d6ff53c9a799
Well I got cm12 built and booting on toroplus, unfortunately the RIL is completely borked, so no cell service at all at this point. I'll keep working on that, in the mean time check out the updated cm11 build in the post right above this one.
So... CyanogenMod is dead. LineageOS is taking it's place. The ROM is basically CyanogenMod but with changes to the name.
This is completely 'stock' from their source code, so this will encrypt your tablet, and will be prerooted (under Developer options in Settings)
Changelog is available at LineageOS Gerrit
There are no apparent bugs, but any bug reports will be welcome.
Gapps are available at opengapps.org.
Installation
Flash the latest 7.1.1 vendor image in fastboot (fastboot flash vendor vendor.img)
Download latest release from here
Install it in TWRP recovery
Install the downloaded opengapps package
XDA:DevDB Information
Unofficial CyanogenMod/LineageOS 14.1 for Nexus 9, ROM for the Nexus 9
Contributors
hazzer
Source Code: https://github.com/LineageOS/
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: 7.1.1 (NMF26F) vendor, latest bootloader
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2016-12-04
Last Updated 2016-12-29
Not quite the first CM14.1 for the Nexus 9, but appreciated you taking the time and effort to compile it in any case.
lmulli said:
Not quite the first CM14.1 for the Nexus 9, but appreciated you taking the time and effort to compile it in any case.
Click to expand...
Click to collapse
I hunted for ages trying to find one that had periodical builds, and I couldn't find any here. Do you mind linking me to the thread?
hazzer said:
I hunted for ages trying to find one that had periodical builds, and I couldn't find any here. Do you mind linking me to the thread?
Click to expand...
Click to collapse
Check hashbang's cm14.1 builds on Android file host.
Can you please post the 7.1.1 vendor image?
Sent from my Nexus 9 using Tapatalk
hazzer said:
I hunted for ages trying to find one that had periodical builds, and I couldn't find any here. Do you mind linking me to the thread?
Click to expand...
Click to collapse
Just go on Androidfilehost and type in flounder
hazzer said:
I hunted for ages trying to find one that had periodical builds, and I couldn't find any here. Do you mind linking me to the thread?
Click to expand...
Click to collapse
https://androidfilehost.com/?w=profile&uid=95897840722645866
Right hand side.
@hazzer Root is broken on latest 12/05 build. It disappeared from the developer settings. It was functioning in 12/04 build.
tibere86 said:
@hazzer Root is broken on latest 12/05 build. It disappeared from the developer settings. It was functioning in 12/04 build.
Click to expand...
Click to collapse
Hi,
Sorry there was no note attached to the build about this. I purposely removed this so that I could pass safety net by default on the ROM.
If you would like root instead of Android Pay, you can try either SuperSU or Magisk with phh's superuser. If you use Magisk hide, you should be able to get root while passing safety net.
Again, sorry about not noting this, I'll make sure I do later today.
Hi,
If you take a look at the download page, I've now added the reason root was and still will be removed. I've also posted a link to the vendor image and latest bootloader. I would recommend downloading the bootloader from Google themselves if possible. The newest source code for the Nexus 9 device tree has been merged into my GitHub however hasn't made it's way into the latest build (20161205). It will be in 06's build.
Sorry about the poor communication regarding root and the likes
hazzer said:
Hi,
If you take a look at the download page, I've now added the reason root was and still will be removed. I've also posted a link to the vendor image and latest bootloader. I would recommend downloading the bootloader from Google themselves if possible. The newest source code for the Nexus 9 device tree has been merged into my GitHub however hasn't made it's way into the latest build (20161205). It will be in 06's build.
Sorry about the poor communication regarding root and the likes
Click to expand...
Click to collapse
Thanks for the info. Just wanted to let you know :good:
Rom is working great!! But i have one problem: I don't have a mobile signal. It just says "no carrier" (in german "Kein Dienst") and i can't set up mobile settings. What to do?
McFlypants said:
Rom is working great!! But i have one problem: I don't have a mobile signal. It just says "no carrier" (in german "Kein Dienst") and i can't set up mobile settings. What to do?
Click to expand...
Click to collapse
That's probably because this is built for the non-LTE version of the Nexus 9. I'm gonna try and add flounder_lte to my build system tonight. I'll post a build sometime tonight or tomorrow if that's okay?
hazzer said:
That's probably because this is built for the non-LTE version of the Nexus 9. I'm gonna try and add flounder_lte to my build system tonight. I'll post a build sometime tonight or tomorrow if that's okay?
Click to expand...
Click to collapse
Yeah, great!! I'll flash it immediately when it's online. Going to try the stock rom now to prove that it's your rom and not the device. We'll stay in contact
McFlypants said:
Yeah, great!! I'll flash it immediately when it's online. Going to try the stock rom now to prove that it's your rom and not the device. We'll stay in contact
Click to expand...
Click to collapse
Hi,
I'm a little late actually successfully getting an LTE version built, as the device tree hasn't been updated for CM14.1 yet. I'll make sure to mention you here when I've got one ready. Sorry for taking so long
Harry
hazzer said:
Hi,
I'm a little late actually successfully getting an LTE version built, as the device tree hasn't been updated for CM14.1 yet. I'll make sure to mention you here when I've got one ready. Sorry for taking so long
Harry
Click to expand...
Click to collapse
No problem, i am aware that it's your freetime you are spending here.
Btw LTE works on CM13 and stock rom, so it's definately not the device. I'm looking forward for your build but i don't need LTE on my nexus 9 the next 4 days. So don't stress yourself :good:
McFlypants said:
No problem, i am aware that it's your freetime you are spending here.
Btw LTE works on CM13 and stock rom, so it's definately not the device. I'm looking forward for your build but i don't need LTE on my nexus 9 the next 4 days. So don't stress yourself :good:
Click to expand...
Click to collapse
I've actually managed to get one built, if you want to take a look. It's below the flounder section. I don't have an LTE Nexus 9 to test, so you'll to let me know how it goes
hazzer said:
I've actually managed to get one built, if you want to take a look. It's below the flounder section. I don't have an LTE Nexus 9 to test, so you'll to let me know how it goes
Click to expand...
Click to collapse
It's fine! Runs smooth like the non-LTE-version but LTE works! Nice
I tried your builds for 13th and 14th of December (WITH LTE) and they all don't get a LTE signal. Also no sim-toolkit installed and no APN-Settings.
I stay with your first LTE-Build, it's fine!
@hazzer: Thanks for your work on the Nexus 9. Any plans to support the official flounder builds?
BEFORE YOU decide to try this rom, please read all of post 1, 2 and 3.
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this ROM.
BACKUP YOUR DATA AND OLD ROM BEFORE trying this rom.
What works
I only test what I use. There could be other things that work or don't work. Let me be clear since there are people who don't seem to understand this. I cannot test things that I don't have like paid streaming/gaming, NFC, miracast or apps that I don't use. They may work or they may not work.
If you want to know if something works that's not listed here, then you need to try it for yourself. If that's not an acceptable or reasonable answer, then stop reading and find another rom that meets your requirements. I built this rom for myself to use and thought that some in the community might benefit by sharing it. If this rom doesn't meet your requirements, then delete it and use whatever does.
1. audio over bluetooth
2. wifi
3. brightness
4. external audio
5. GPS - a bit slow to get a fix/lock
6. audio through headphone jack
7. camera
What doesn't work
1. screen recorder. The current sepolicy doesn't allow screen recorder to work. While adding code to allow sepolicy to work
Code:
#============= mediacodec ==============
allow mediacodec camera_device:chr_file { ioctl open read write };
The [email protected] crashes. A mp4 file is created, but it doesn't seem to be in the correct format? Possibly related to ??
https://review.lineageos.org/c/LineageOS/android_device_htc_flounder/+/210609
FAQ
Q1) Does the build work on Nexus 9 LTE?
A1) I have no idea. I only have the Nexus 9 wifi so I don't know if it will work on LTE. If you have the LTE, you can build your own LTE rom. If you try the wifi build on the LTE, you may end up with a bricked device. Questions regarding LTE will go unanswered.
Q2) Application xyz doesnt' work. Can you fix it?
A2) I only fix what I use. If you use app xyz and it doesn't work, then try 14.1 or going back to the last rom that worked for you. In addition, some of the code is not open source and in proprietary blob format so it's not possible to make changes.
Q3) My tablet hangs or crashes with 15.1. This build is slow and buggy. Can you fix it?
A3) Go back to the last working stable rom for you. 15.1 is a work in progress and will have bugs and frequent changes. In addition, some of the code is not open source and in proprietary blob format so it's not possible to make changes.
Q4) Do you plan to update the rom?
A4) Yes as long as I have high speed Internet, I wil try to release the rom monthly to incorporate the security patches.
Q5) What TWRP should I use?
A6) TWRP 3.3.1 or higher. Get it from
Download TWRP for flounder
Download TWRP Open Recovery for flounder
dl.twrp.me
Q6) What is the difference between this rom and variants?
A6) Use whatever fits your needs. This is a stock LineageOS build with no modifications. I only offer this as an option for those who want or need a new rom and can't build it themselves.
Q7) Will there be a 16.0, 17.1 or 18.1 build?
A7) I tried building 16.0, but the rom get's stuck at the very begining of the boot process and I haven't investigated too much. Do not ask if there is progress on this. I'm an unpaid volunteer building this on my own time. Any questions regarding ETAs will go unanswered.
I suspect that one or two LineageOS developers have a working 16.0 build, but they are not ready to share their code? The repos have been updated to 16.0 at
LineageOS
A free and open-source operating system for various devices, based on the Android mobile platform. This is a mirror of https://review.lineageos.org/ - LineageOS
github.com
on Nov 4, 2020.
If you are a rom builder or developer and want to help get 16.0 going, please contact me.
Q8) Should I upgrade from stock or 14.1 to 15.1?
A8) It's entirely up to you. If you do upgrade, you will need to backup your data, wipe dalvik/art cache, system, data and internal storage in TWRP. You must also format data in TWRP. You cannot dirty flash from stock or 14.1 to 15.1, it must be a completely clean fresh install.
Q9) Can I build this rom myself? Where can I find the source and/or kernel source code?
A9) This is one of the few roms where it required no edits or changes to make it work. Follow the instructions at
Flounder
Build for flounder | LineageOS Wiki
wiki.lineageos.org
Flounder_lte
Build for flounder_lte | LineageOS Wiki
wiki.lineageos.org
and you will get a working 15.1 image. You will need to apply (hw video patch)
https://review.lineageos.org/268654
The roomservice.xml only consists of 3 repos. The roomservice.xml points to all the source code including the kernel source code. That is,
GitHub - LineageOS/android_kernel_htc_flounder
Contribute to LineageOS/android_kernel_htc_flounder development by creating an account on GitHub.
github.com
GitHub - LineageOS/android_device_htc_flounder
Contribute to LineageOS/android_device_htc_flounder development by creating an account on GitHub.
github.com
GitHub - TheMuppets/proprietary_vendor_htc
Contribute to TheMuppets/proprietary_vendor_htc development by creating an account on GitHub.
github.com
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_device_htc_flounder" path="device/htc/flounder" remote="github" revision="lineage-15.1" />
<project name="LineageOS/android_kernel_htc_flounder" path="kernel/htc/flounder" remote="github" revision="lineage-15.1" />
<project name="TheMuppets/proprietary_vendor_htc" path="vendor/htc" remote="github" revision="lineage-15.1" />
</manifest>
I changed the fstab.flounder from forceencrypt to encryptable.
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data f2fs noatime,nosuid,nodev,errors=panic wait,check,latemount,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,check,latemount,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
Normally, monthly builds 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.
Q10) Why is my question not answered?
A10) It's likely because it's in the FAQ or it's off topic or you are asking something that I cannot answer for the reasons stated in this FAQ.
Q11) How is this 15.1 build different from the ones already on XDA?
A11) The 15.1 roms built before Nov 4, 2020 didn't include this patch
flounder: Patch libraries that rely on arm libm intrinsics · LineageOS/[email protected]
* Force-pick https://review.lineageos.org/268655, build "libm" target, rename "libm.so" to "libw.so", and then: `sed -i 's/libm.so/libw.so/g' libw.so...
github.com
Also, some of the 15.1 roms may not have included the hw video patch. It's not part of the repository and requires the builder to pick and apply that patch manually.
For some, depending on how the device is used, having the hw video patch isn't necessary and will work fine without it.
Q12) Is the video hardware accelerated in 15.1?
A12) Yes. The March 9, 2021 and all future builds include this patch
https://review.lineageos.org/268654
for video hardware acceleration.
Q13) Is encryption enabled by default?
A13) Some people say the Nexus 9 lags over time and supposedly removing encryption improves performance. The Nexus 9 is not a daily driver for me so I don't know, but reading the older 14.1 and 15.1 threads, I decided to change the default behavior starting with the March 13, 2021 build so that encryption is disabled by default.
If you want encryption enabled, goto settings, security and privacy, encryption and credentials, encrypt tablet and follow instructions.
Q14) Can you build a variant like slimrom, crDroid, etc?
A14) No, but you can following the instructions and source code above that has been provided.
Q15) What gapps should I use?
A15) I personally am moving away from all google apps and technology. If you must use gapps, pick the smallest one which is pico ARM64.
Q16) Where can I download this rom?
A16) See
retiredtab - Browse /Nexus 9/15.1 at SourceForge.net
sourceforge.net
Feb 24, 2022 release notes
1. Incorporates UNOFFICIAL Feb 5 security patches as per https://review.lineageos.org/q/topic:O_asb_2022-02
2. Whatever LineageOS changed since Jan 5, 2022 (about 2,900 files had to be recompiled).
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).
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
Code:
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
Code:
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.
Oct 11, 2021 release notes
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.
Sept 24, 2021 release notes
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.
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. This is the second build using Andrea's repos.
July 18 release notes
1. First build to incorporate changes by Andrea.
2. Incorporates July 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/313627
3. Whatever LineageOS changed since June 2021.
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.
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.
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.
Release notes for March 13, 2021
1. Changed encryption to be disabled by default.
Release notes for March 9, 2021
1. Initial build for 15.1 Nexus 9 wifi only.
2. March 5, 2021 security patches
3. Built from LineageOS 15.1 repos with no changes or edits and includes the hw video patch.
4. Please be patient on first bootup.
For those that downloaded the March 8 build, please delete it. While it works, there was a problem with the build missing a hw video patch that I didn't notice at first. I will upload a March 9 build. Sorry for the trouble.
Reserved
For those that downloaded the March 8 build, please delete it. While it works, there was a problem with the build missing a hw video patch that I didn't notice at first. When I did a clean repo sync, I forgot to apply the hw video patch at
https://review.lineageos.org/268655
in the March 8 build. The March 8 build works as I tested it, but it wasn't until a few hours later that I realized I forgot to reapply the hw video patch.
The March 9 build includes the above hw patch. Sorry for the inconvenience.
I did notice a weird behaviour of voice match (the "ok google" service)
It keeps trying to update the voice model, shows a notification, then goes away for a bit.
Opening the voice match settings on google settings causes flickering on the window, as if it fails and restarts repeatedly. It also failed to initialize during the first boot, so I skipped it.
All other google apps seem to work fine. I've tried both Micro and Stock Gapps
AgentCain said:
I did notice a weird behaviour of voice match (the "ok google" service)
It keeps trying to update the voice model, shows a notification, then goes away for a bit.
Opening the voice match settings on google settings causes flickering on the window, as if it fails and restarts repeatedly. It also failed to initialize during the first boot, so I skipped it.
All other google apps seem to work fine. I've tried both Micro and Stock Gapps
Click to expand...
Click to collapse
Me too
I don't use or load gapps and I never use ok google. I'm degoogling everything in 2021.
New build lineage-15.1-20210313-UNOFFICIAL-flounder.zip has force encryption disabled by default.
Some people say the Nexus 9 lags over time and supposedly removing encryption improves performance. The Nexus 9 is not a daily driver for me so I don't know, but reading the older 14.1 and 15.1 threads, I decided to change the default behavior.
Since 15.1 will never be official, I changed the fstab.flounder from forceencrypt to encryptable.
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data f2fs noatime,nosuid,nodev,errors=panic wait,check,latemount,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,check,latemount,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
If you want encryption enabled, goto settings, security and privacy, encryption and credentials, encrypt tablet and follow instructions.
If you want encryption disabled, backup all your data, goto TWRP, wipe dalvik/art cache, system, data and internal storage in TWRP. You must also format data in TWRP. Then install the March 13 build and encryption will be disabled by default. You can also change the cache and data to f2fs if you want for potentially better performance.
Going forward, all monthly security builds will have encryption disabled unless you enable it.
PS. That's the only change from the March 9 build. The above has been added to the FAQ now.
bought a nexus9 yesterday, went the noob path (outdated toolkit to unlock bootloader/ root+twrp... updated twrp to 3.5.9.0) then flashed your current rom... (9march) feel smooth and nice!
thanks for continuing working on this device! its a real upgrade from my previous tab (8" tab 3).. we cant all spend money on fancy device, nexus9 is still relevant today with this nice custom rom!
edit2: stupid me of course... now build 2021.03.13 is working well without encryption problem! (was trying to remove encryption following your tutorial with the previous rom)
I think there is a problem with accout registration. Ok google not working but it's impossible to register some account. I try microsoft one for word. It say internet connection is not present. Maybe this can help to solve the problem
Wow! Thanks for this! Since the new XDA update, it has been so awful I stopped using it. I just popped back on after 2 months away from XDA and found this rom! Going to try it soon.
One problem I had was with stadia not working. I don't mean to ask if it does now, but it does seem that the chrome browser version works now (vatrom's version). Can you at least take an educated guess if the new hardware acceleration patch in the repo might help get stadia working properly? I suspected it was either an unsupported codec or an issue with hardware acceleration being the culprit. Thanks
gk1984 said:
One problem I had was with stadia not working.
Click to expand...
Click to collapse
Never heard of stadia and I don't use google chrome browser.
Google Stadia is Google's cloud gaming platform. And no, I didn't ask about Chrome. I simply was trying to ask some clarity about Lineage's hardware acceleration patch vs Barron's, but included context to my situation. I clear8 stated I wasn't exactly asking if Stadia was working, but if the new hardware acceleration patch could impact it and why.
It's pretty unprofessional to blanket statement "I don't use x" and ignore the question. It also hurts your credibility as a developer if you can't explain what's being parched into the code if you directly mention it in the OP. You could simply respond with "I'm not an experienced developer and can't articulate X or Y, I'm just capable of building from source and distributing." We don't know you, we don't know your skill level or knowledge. I'm used to ROM developers or at least those building them to know what they're working on. But your. Blanket statement suggests otherwise.
back again.. and it fixed now! of course, i've downloaded the 20210309 build and couldnt figure a proper way to remove encryption on data partition... I've managed to flash gapps (use an old 16go usb key with microusb connector)..and come back to read CORRECTLY your post and understood my mistake... it was an old build!
Did a clean flash and flashed 0313 build, no more encryped data now! (flashed some nano gapps + magisk) setting up the device, so far so good!
It's great to see some people still have this tablet! They are under $50 used now, but it's a shame about stock performance...
Just some personal screenshoot...
AgentCain said:
I did notice a weird behaviour of voice match (the "ok google" service)
It keeps trying to update the voice model, shows a notification, then goes away for a bit.
Opening the voice match settings on google settings causes flickering on the window, as if it fails and restarts repeatedly. It also failed to initialize during the first boot, so I skipped it.
All other google apps seem to work fine. I've tried both Micro and Stock Gapps
Click to expand...
Click to collapse
I found a solution. Install the Google app from ApkMirror.com and restart the tablet. Should work after that. Looks like it's a common problem with open gapps I. General.
Hey thanks for sharing your rom
Can I dirty flash this rom from the other lineage os 15.1 build?
I'm not the developer, but I wouldn't recommend it. That usually leads to Android being unable to boot. Best to factory reset.
gk1984 said:
I found a solution. Install the Google app from ApkMirror.com and restart the tablet. Should work after that. Looks like it's a common problem with open gapps I. General.
Click to expand...
Click to collapse
Thanks it work for me
I'm just curious whether anyone has already compiled the AOSP for A13 and booted it. I noticed it had already been done/tested on OP5/5T, but wasn't sure if it had been done for P6P. I plan on trying my hand at it, but wanting to know what others may have experienced before I commit my slower internet connection to downloading the Repo.
GrapheneOS has test builds up for A13, which should be buildable using the normal approach. Also hardened with some extra security features.
Yes, on ArrowOS, temp issues however that was same day arrow started updating to 13, have not run a build since. Evolution X reboot a few seconds after setup screen loads, does not boot without gapps either.
I have tried for several days, but I'm missing something
It's a custom rom for personal use. A12.1 booted and worked perfectly but 13 reboots to bootloader
RealSchnedi - Repositories
RealSchnedi has 15 repositories available. Follow their code on GitHub.
github.com
Schnedi said:
I have tried for several days, but I'm missing something
It's a custom rom for personal use. A12.1 booted and worked perfectly but 13 reboots to bootloader
RealSchnedi - Repositories
RealSchnedi has 15 repositories available. Follow their code on GitHub.
github.com
Click to expand...
Click to collapse
Stupid question have you flashed both slots with 13 as I know boot loader won't load of you have 12 version and not updated to 13 but also it has an anti roll back in it sorry not much help
liggerz87 said:
Stupid question have you flashed both slots with 13 as I know boot loader won't load of you have 12 version and not updated to 13 but also it has an anti roll back in it sorry not much help
Click to expand...
Click to collapse
I flashed the bootloader and radio on both slots but haven't tried to change the current slot and flash the rom
But if I flash the official 13 release (only in the current slot) it boots, so, not sure if that's the problem. Anyway, I'll try it
Schnedi said:
I flashed the bootloader and radio on both slots but haven't tried to change the current slot and flash the rom
But if I flash the official 13 release (only in the current slot) it boots, so, not sure if that's the problem. Anyway, I'll try it
Click to expand...
Click to collapse
Been looking at our github, you are using anayw2001 repo for your vendor files, remove the below from Android.bp. I had Restless nights with a poop load of testing thinking it was something with a missing lib file or so when i test anay's vendor files with lots of comparison to lineage extract tools that worked. Well if your getting bootonce-bootloader error that is as reason for bootloader load.
prebuilt_apex {
name: "com.google.android.compos",
owner: "google_devices",
src: "system_ext/apex/com.google.android.compos.apex",
prefer: true,
system_ext_specific: true,
}
prebuilt_apex {
name: "com.google.android.virt",
owner: "google_devices",
src: "system_ext/apex/com.google.android.virt.apex",
prefer: true,
system_ext_specific: true,
}
alvin14 said:
Yes, on ArrowOS, temp issues however that was same day arrow started updating to 13, have not run a build since. Evolution X reboot a few seconds after setup screen loads, does not boot without gapps either.
Click to expand...
Click to collapse
Update on this for ArrowOS. After removing connectivitythernmalmanager that fixed the issue as i am getting selinux denials with it, everything works, been testing for a few days.
alvin14 said:
Been looking at our github, you are using anayw2001 repo for your vendor files, remove the below from Android.bp. I had Restless nights with a poop load of testing thinking it was something with a missing lib file or so when i test anay's vendor files with lots of comparison to lineage extract tools that worked. Well if your getting bootonce-bootloader error that is as reason for bootloader load.
prebuilt_apex {
name: "com.google.android.compos",
owner: "google_devices",
src: "system_ext/apex/com.google.android.compos.apex",
prefer: true,
system_ext_specific: true,
}
prebuilt_apex {
name: "com.google.android.virt",
owner: "google_devices",
src: "system_ext/apex/com.google.android.virt.apex",
prefer: true,
system_ext_specific: true,
}
Click to expand...
Click to collapse
I was already using your vendor from gitlab (arrow branch). It did the trick, bootloader not triggered anymore
Still not booting but it must be related to rom sources, will take a look
Thanks a lot
Schnedi said:
I was already using your vendor from gitlab (arrow branch). It did the trick, bootloader not triggered anymore
Still not booting but it must be related to rom sources, will take a look
Thanks a lot
Click to expand...
Click to collapse
Do a logcat during boot, will definitely help with that.
card13 said:
I'm just curious whether anyone has already compiled the AOSP for A13 and booted it. I noticed it had already been done/tested on OP5/5T, but wasn't sure if it had been done for P6P. I plan on trying my hand at it, but wanting to know what others may have experienced before I commit my slower internet connection to downloading the Repo.
Click to expand...
Click to collapse
There is a build of Hentai which is very good. You can even dirty flash from stock
alvin14 said:
Do a logcat during boot, will definitely help with that.
Click to expand...
Click to collapse
Thanks, I'm making some tests, not so sure it's the rom sources
Question, to build Evo and Arrow, are you using your adevtool vendor or the other one?
Schnedi said:
Thanks, I'm making some tests, not so sure it's the rom sources
Question, to build Evo and Arrow, are you using your adevtool vendor or the other one?
Click to expand...
Click to collapse
Adevtool. The other one works as well however i need to clean it up a bit.
hi guys,
@Schnedi what gapps package are you using for prime?
And does udfps work on your raven with your prime base?
Well, after a dozen of test builds, I finally made it work
Still have to fix things tho
Schnedi said:
Well, after a dozen of test builds, I finally made it work
Still have to fix things tho
Click to expand...
Click to collapse
Cool. I got oriole too boot prime yesterday too. Nice work!
What gapps package do you use? Is it on gitlab somewhere?
ny-hardcore said:
Cool. I got oriole too boot prime yesterday too. Nice work!
What gapps package do you use? Is it on gitlab somewhere?
Click to expand...
Click to collapse
I'm using this one: https://gitlab.com/spkal01/android_vendor_gms/-/tree/pyro
But removed some apps that can be installed from the store (drive, youtube, gmail, photos...)
Also, latest commit from fw/b fixes udfps
There's just a few features, I just pick the ones I use, didn't build prime to share it, so I'm not picking all of them. You can always fork the project and pick some features you use, PM me if you need any help with it
Schnedi said:
I'm using this one: https://gitlab.com/spkal01/android_vendor_gms/-/tree/pyro
But removed some apps that can be installed from the store (drive, youtube, gmail, photos...)
Also, latest commit from fw/b fixes udfps
There's just a few features, I just pick the ones I use, didn't build prime to share it, so I'm not picking all of them. You can always fork the project and pick some features you use, PM me if you need any help with it
Click to expand...
Click to collapse
Thanks for the reply, i spark gapps too by the way haha
i picked udfps myself so had it working already
i like your vendor /vendor/extras very clean setup.
i know how to fork, but no need for now
This is a BETA build for NEW Lineage 20, Android 13. Possible bugs may be present. Let me know!!
MSM to Android 11 if you want to start clean, then flash either CrDroid or Nameless c63 firmware to begin.
This is based on the Android Open Source Project. It can be used without any need to have any Google application installed. It does still include various proprietary hardware-specific code.
Gapps must be flashed separately and are not included in this ROM.
All the source code is available in the Github repo here.
Thanks go to Github and LineageOS for their source code and device specific code. I couldn't have built this without it!!!
The ROM uses the LineageOS source code, device specific code and proprietary blobs. I made other minor changes and used compression to lower the file size of the ROM, creating more space in the internal storage with minor reduction in performance. Updated daily with minor changes.
You may use another recovery however you will receive a signature verification error. You can simply ignore and choose yes and flash it anyway. You will need to do this with gapps and magisk.apk to root.
DOWNLOAD ROM & GAPPS HERE
#1 REBOOT TO BOOTLOADER
#2 FACTORY RESET: fastboot -w
#3 REBOOT TO RECOVERY
#4 SIDELOAD ROM IN RECOVERY
adb sideload lineage-20-20221112-UNOFFICIAL-lemonadep.zip
reboot recovery
adb sideload lineage-20-20221112-UNOFFICIAL-lemonadep.zip
reboot recovery
#5 SIDELOAD GAPPS: NikGapps-core-arm64-13-20221109-signed.zip
#6 REBOOT TO SYSTEM
#7 REBOOT TO LINEAGE RECOVERY IF YOU WISH TO ROOT
SIDELOAD MAGISK.APK
adb sideload magisk.apk
#8 REBOOT TO SYSTEM
Updates available in built in updater. settings, system, updater.
You can change preferences to check for updates daily.
Sounds interesting......even though I love stock, this is tempting!
TheGhost1951 said:
Sounds interesting......even though I love stock, this is tempting!
Click to expand...
Click to collapse
I'm with you man. I'm on stock too and Lineage is my least favorite ROM. I'm just trying to help others who like it and diagnose and fix a annoying bluetooth bug.
Is possible to post screen shots. plz
OOS camera included. And Oneplus setting
break.cold said:
Is possible to post screen shots. plz
OOS camera included. And Oneplus setting
Click to expand...
Click to collapse
Come-on guy, do your research like the rest of us here.....Google, bing, xda....search. put forth the effort and the reward is greater
What (and where) are the changes you made to Bluetooth connectivity? Does this solve the longstanding problem of "stuttering" audio on Bluetooth phone calls?
MJPollard said:
What (and where) are the changes you made to Bluetooth connectivity? Does this solve the longstanding problem of "stuttering" audio on Bluetooth phone calls?
Click to expand...
Click to collapse
I don't have it listed anywhere. I dumped the firmware from stock and pulled the bluetooth and implemented it into this. I tested it and didn't notice any issues but I went back to stock. Lineage is not my thing. All I can say is to test it out and report any issues and I'll continue to work on any problems that may exist.
09/27 update posted
10/01 update posted
TheSayaMan said:
10/01 update posted
Click to expand...
Click to collapse
Changelog?
Beytullah61 said:
Changelog?
Click to expand...
Click to collapse
Changes in regards to bluetooth connectivity only.
LineageOS/Bluetooth at main · MikeSaya1/LineageOS
Contribute to MikeSaya1/LineageOS development by creating an account on GitHub.
github.com
10/09 update posted. More bluetooth improvements.
TheSayaMan said:
10/09 update posted. More bluetooth improvements.
Click to expand...
Click to collapse
10/15 posted. October security patch.
Thread changed from LineageOS 19 Android 12 to LineageOS 20 BETA Android 13
Can you build for oneplus 9?
imbasador said:
Can you build for oneplus 9?
Click to expand...
Click to collapse
Yes, I'm working on it
Because of the lack of interest on this. This thread will be closed.
Thread closed at the OP's request.