I cannot find GN on Lineage OS's download list any more.
LineageOS 13 has been removed from the build roster. As that was the only officially supported version on the GNex, that means the GNex no longer has any official builds, and the last one (20180211) has aged off the download server.
I don't know if anyone has it available somewhere else.
Try this: https://download.lineage.microg.org/maguro/
Just in case it's not obvious to everyone, that microg build is different to the official Lineage build. (I don't know, but I assume it simply takes the official build and adds microg stuff to it.)
The last official LineageOS 13.0 signed image for Galaxy Nexus Maguro
Does anyone have it? or have a link? That would be really great. Cant find it anywhere.
udusimus said:
Does anyone have it? or have a link? That would be really great. Cant find it anywhere.
Click to expand...
Click to collapse
I think this is mirror from official lineage downloads : https://androidfilehost.com/?fid=962187416754467700
And this is built by Android-Andi : https://androidfilehost.com/?fid=962187416754460076
Don't know differences, but both are little different in size by 100kb, there may be something different, you can give try to both..
I just checked the md5 displayed at that first link against the file I downloaded from LOS in February, and it matches. The hashes I got here are:
md5 - A049F70667D018F814B84D221B844C97
sha1 - B98E1760CE063E2C64C07BAAE33AB4DBECB5823B
sha256 - AF4F3E07DF677AA5BF4E2D6D9CB8AF3F410029344ACC099DCD8589F39778D115
Does anybody know if general security fixes are being applied to the Lineage OS 13 branch at all any more? No point in rolling your own if the patch level isn't being kept up to date.
dumas777 said:
Does anybody know if general security fixes are being applied to the Lineage OS 13 branch at all any more? No point in rolling your own if the patch level isn't being kept up to date.
Click to expand...
Click to collapse
LOS's Changelog 16 says "The branches will not be locked, so it’ll still be open for contributions such as security patches, like the 11.0 branch which has been getting security patches backported from the community."
I have no idea whether anybody is actually doing it, though.
Yes, development of LIneage13 is still continue : https://review.lineageos.org/#/q/branch:cm-13.0
Good deal. Thanks for the info from both of you. Looking forward to building it myself and here when it finishes in a week (only slight exaggeration) I will be gold lol.
There is an unofficial Lineage OS 14.1 build floating around on XDA somewhere. I have it installed on a Galaxy Nexus and it's not bad, a little slow at times but I also installed the pico open gapps package as well.
Found the link: https://forum.xda-developers.com/galaxy-nexus/development/dev-lineageos-14-1-t3649194
Hey there, I hope that maybe someone could take the time to explain this process to me a bit.
I'm building LineageOS 15.1 for the Axon7. As there hardly are any updates, besides monthly Security Updates, I'm always just waiting for those to get merged. As hardly anyone is still interested in the 15.1 source this sometimes takes quite a while (not complaining).
I've had a look at the merged commits in the Lineage source and all I can see is that literately one string gets updated. The Date.
Now my question is. If I were to change that string in my local source, with the (as mentioned in the "version_defaults.mk") corresponding and matching date of the Android Security Patch Level , would that automatically sync all necessary patches and the security patch level of my ROM (if it builds)would be up to date?
Also does it have to be the exact date, or simply any date, after the Security Patch was commited?
Would that really be all it takes?
Thanks in advance to anyone, who might help me clear that up.
You can use repopick to build with patches not merged yet. Like...repo sync source build/envsetup.sh repopick -t n-asb-2020-04 breakfast...
July patches for oreo are merged
https://review.lineageos.org/q/topic:%22O_asb_2020-07%22
August patches are not yet in gerrit
Also erstmal danke für deine Antwort.
I'm really relatively new to building roms and I appreciate any and all info that I can get, so again, thanks you for that.
Is there, like I asked, any chance tho to build it with the latest security updates before they are added as "open" to the gerrit?
Can it be added the way I mentioned above, or is there more to it?
So yesterday I installed LineageOS 17.1 on my Tab S3 (T820). Installation went without a lot of problems, but when I booted into the system for the first time, I got a notification about the security version. I clicked the notification to see what's up. Turns out I'm running a security patch from February 5, 2020
(See screenshots in link)
imgur (dot) com/a/yBfDlnH
I already tried updating via several buttons, but no luck.
Is there any way for me to update this manually to a new security patch? Or is it not needed?
MrDanMan said:
So yesterday I installed LineageOS 17.1 on my Tab S3 (T820). Installation went without a lot of problems, but when I booted into the system for the first time, I got a notification about the security version. I clicked the notification to see what's up. Turns out I'm running a security patch from February 5, 2020
(See screenshots in link)
imgur (dot) com/a/yBfDlnH
I already tried updating via several buttons, but no luck.
Is there any way for me to update this manually to a new security patch? Or is it not needed?
Click to expand...
Click to collapse
It's not about patch level. It says "signed with public keys" that's typical for unofficial builds.
The patch levels can only be updated by building a new installation zip. Vendors patch level only if manufacturer releases an update and developer includes updated components.
kurtn said:
It's not about patch level. It says "signed with public keys" that's typical for unofficial builds.
The patch levels can only be updated by building a new installation zip. Vendors patch level only if manufacturer releases an update and developer includes updated components.
Click to expand...
Click to collapse
So there is no way for me to update to a newer security version (for example September 2020)?
MrDanMan said:
So there is no way for me to update to a newer security version (for example September 2020)?
Click to expand...
Click to collapse
Way 1 - search
Way 2 - wait
Way 3 - build
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