Related
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1.x (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Information:
This is the nightly builds of LineageOS 14.1 for Zenfone 5 (T00F,T00J) and Zenfone 6 (T00G).
Known issues:
FM Radio is unsupported.
Like on the most devices with LineageOS 14.1, some video formats do not play so good.
In nature, there are no official Android Nougat builds for 32-bit Intel devices, so we cannot update some non device-specific blobs (like Houdini and wvm) to latest versions and there may be problems with some apps (e.g. 2GIS and UC Browser).
GPS doesn't work
Bug reporting:
Before the report make sure that your device was properly updated to the latest stock base (modem firmware is mostly important) and you've installed the latest build of the ROM.
Explain the bug in details and, if possible, methods to reproduce it.
For most issues, you should attach the logcat. It you have problems with the network/RIL, attach the radio logcat too (logcat -b radio).
Random reboots? Please upload all ramoops files from /sys/fs/pstore immediately after the kernel crash.
Links:
Download LineageOS 14.1
Download GAPPS
Download Root Addon
Credits:
LineageOS community (CyanogenMod (R.I.P))
jrior001
crpalmer
X AnwarMov
And other Zenfone contributors.
Donation:
I don't force you, but if you like my work and want to:
Donate to me
XDA:DevDB Information
Unofficial LineageOS 14.1 Nightly Builds, ROM for the Asus Zenfone 5
Contributors
flex1911
Source Code: https://github.com/zenfone-legacy
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Testing
Created 2016-12-31
Last Updated 2017-11-06
Reserved
Changelog:
Code:
[B]20171021:[/B]
Updated LineageOS to the latest git base
Krack vulnerability fixes
Various of kernel security updates
[B]20171003:[/B]
Updated LineageOS to the latest git base
October security bulletin
[B]20170922:[/B]
Updated LineageOS to the latest git base
September security bulletin
[B]20170812:[/B]
Updated LineageOS to the latest git base
August security bulletin
Kernel security updates
[B]20170707:[/B]
Updated LineageOS to the latest git base (android-7.1.2_r24)
July security bulletin
Updated kernel to the upstream 3.10.107 version
[B]20170628:[/B]
Updated LineageOS to the latest git base
Updated kernel to the upstream 3.10.106 version
Switched to the AOSP libril
Various security and bugfix kernel patches
[B]20170611:[/B]
Updated LineageOS to the latest git base (android-7.1.2_r17)
June security bulletin
[B]20170524:[/B]
Updated LineageOS to the latest git base
T00F: doze display state is unsupported by our hwc
Various security and CVE kernel patches
[B]20170509:[/B]
Updated LineageOS to the latest git base (android-7.1.2_r8)
May security bulletin and security kernel updates
Revert to the modified libril
[B]20170425:[/B]
Updated LineageOS to the latest git base
Enabled call recording
Disabled SIM batch operations (contacts import should be good now, but export will not work anyway)
Switched off from the laggy screen off animation to the fade off (animate screen lights)
Merged some security related kernel patches
[B]20170414:[/B]
Updated LineageOS to the latest git base
Android 7.1.2
April security bulletin
[B]20170329:[/B]
Updated LineageOS to the latest git base
Various fixes and kernel updates
[B]20170317:[/B]
Updated LineageOS to the latest git base
Disabled sdcardfs to fix apps issues
Updated f2fs to the latest mainline backports
Security patches for network stack
Minor kernel fixes and updates
[B]20170310:[/B]
Updated LineageOS to the latest git base (android-7.1.1_r25)
Updated fs-related kernel stuff and enabled sdcardfs
[B]20170228:[/B]
Updated LineageOS to the latest git base
February security patch
Fixed minor stuff and (maybe) power issues
[B]20170214:[/B]
Updated LineageOS to the latest git base
Fixed booting issues
Moved to ondemand again and fixed some issues related to it
Enabled Snap camera (most of the issues are fixed now)
Security-related kernel updates
Killed built-in root (use su addon instead)
Minor fixes
[B]20170205:[/B]
Updated LineageOS to the latest git base
Added correct power profile (should fix some issues with battery capacity)
Moved back to interactive governor and enabled touchboost
Updated houdini to the latest MM revision
Various updates and fixes
[B]20170123:[/B]
Updated LineageOS to the latest git base
Updated security-related stuff in the kernel
Moved back from Snap to AOSP Camera2 (it's better choice for us now)
Updated offline charging images (imported it from Z00D's tree, hope it will work)
Minor updates and fixes
[B]20170116:[/B]
Updated LineageOS to the latest git base (android 7.1.1-r9)
Smart Cover support via FlipFlap application
Reverted all recent upstream kernel updates (3.10.20 again)
Moved to ondemand governor and kanged latest cpufreq changes from Z00D
[B]20170109:[/B]
Updated LineageOS to the latest git base (android 7.1.1-r9)
January security patch
Bringed back hall sensor support to the kernel
Minor updates and fixes
[B]20170104:[/B]
Updated LineageOS to the latest git base
Fixed various things related to T00G (Zenfone 6)
Updated kernel to the latest upstream base (3.10.104) and picked most changes from Z00D
Fixed network configuration (should fix bugs with mobile internet after WiFi)
Slightly tweaked interactive governor
Minor fixes
[B]20170101:[/B]
Updated LineageOS to the latest git base
Fixed camera
Updated some config-related options
Minor updates and fixes
[B]20161231:[/B]
First Nougat build for ZF5/6
As Nikolai752 said, almost everything work excluding the camera.
I don't have ZF5, so I need more logs and other stuff.
If you want to report bug - upload your logcat and dmesg.
finally!! nougat is landing on zf5, amazing :silly:
Camera was fixed.
Flash new boot.img - https://drive.google.com/file/d/0B7jApZFEHXFuNXRQclBJbjVJVGs/view?usp=sharing
Happy New Year to all!
flex1911 said:
Camera was fixed.
Flash new boot.img - https://drive.google.com/file/d/0B7jApZFEHXFuNXRQclBJbjVJVGs/view?usp=sharing
Happy New Year to all!
Click to expand...
Click to collapse
Amazing! Happy new year!
Is the home and recents button fixed ?
Sent from my ASUS_T00F using Tapatalk
---------- Post added at 04:38 PM ---------- Previous post was at 04:36 PM ----------
Btw , thanks your very much sir!! And happy new year!
Sent from my ASUS_T00F using Tapatalk
fakhri_adi551 said:
Is the home and recents button fixed ?
Sent from my ASUS_T00F using Tapatalk
---------- Post added at 04:38 PM ---------- Previous post was at 04:36 PM ----------
Btw , thanks your very much sir!! And happy new year!
Sent from my ASUS_T00F using Tapatalk
Click to expand...
Click to collapse
Yes, just flash the latest build and then update boot.img. Everything should work as expected.
flex1911 said:
Yes, just flash the latest build and then update boot.img. Everything should work as expected.
Click to expand...
Click to collapse
Okay sir thank you for your reply
Sent from my ASUS_T00F using Tapatalk
This ROM is a best New Year's gift. Thanks for your work
Amazing! Eager to test your ROM. Is Vulkan API working?
Kyo. said:
Amazing! Eager to test your ROM. Is Vulkan API working?
Click to expand...
Click to collapse
I don't think that Vulkan ever would work. We need either source code of our graphic stack or vulkan binaries for sgx.
Guys, I need to know T00F's CPU frequencies to make power and performance-related things slightly better.
Give me the output of
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
Hello, can you add some scr? ) thx.
Edit : deleted
flex1911 said:
guys, i need to know t00f's cpu frequencies to make power and performance-related things slightly better.
Give me the output of
Click to expand...
Click to collapse
1200000 933000 800000
flex1911 said:
Guys, I need to know T00F's CPU frequencies to make power and performance-related things slightly better.
Give me the output of
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
Click to expand...
Click to collapse
2.0 and 1.6 and 1.2
1600000 1333000 933000 800000
DT2W ?
Davega said:
DT2W ?
Click to expand...
Click to collapse
No its not working
The Unlegacy Android ProjectIntroduction
Unlegacy-Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy Android was born. In our opinion, these ROMs are how the official updates would look.
On top of AOSP, we only include changes which are necessary to support the hardware, be secure, and get acceptable performance. Current features for hammerhead include:
BFQ IO scheduler (official kernel 3.4 release), set up so GUI processes have the highest priority
Volume button wakeup (setprop persist.wm.volume_wake_screen 1)
Last upstream (kernel/msm) hammerhead kernel tag merged
Charging LED control (setprop persist.sys.led_on_charger 0)
Enhanced backlight map for lower min brightness
Night display blue light filter (GLES-based)
KCAL & PCC color temperature interfaces
Other security patches & minor bug fixes
F2FS support from K4.4 backports
SELinux in Enforcing mode
Installation
It's important that /system needs to be unmounted before installing the ROM - some recoveries tend to leave it mounted after performing operations on it.
If you're planning to install GApps, be sure to read the second post.
Aside from these, installation and upgrading is no different than on other ROMs.
Problems
No known issues on Nougat builds
See post #3 for Oreo/Pie notes
If you notice anything, be sure to report it in this thread. Stability is our main concern. While it may takes some time, I usually read the thread and acknowledge the bug reports, even if I don't reply directly to them.
Downloads
See: http://builds.unlegacy-android.org. Our automated builds ensure that we always have the latest Android security patches merged in, without having to manually start and upload builds
Also, we'll have a built-in OTA updater (just like stock) soon (it's a work in progress).
Features?
There isn't much to say here - this is AOSP, if you install GApps, you pretty much get the same thing that's running on the Nexus devices (see second post). The aim of this project is to create a fast and stable ROM, as close to AOSP as possible without diminishing usability. Occasionally, small non-AOSP features may be implemented, provided there is a clear need and they make sense on hammerhead.
XDA:DevDB Information
Unlegacy Android Project, ROM for the Google Nexus 5
Contributors
amaces, Ziyan
Source Code: https://github.com/Unlegacy-Android
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 7.1.2
Stable Release Date: 2017-04-18
Current Beta Version: 9.0.0
Beta Release Date: 2017-10-02
Created 2017-04-21
Last Updated 2018-10-30
GApps
If you want to install GApps, we recommend micro packages on N builds (e.g., Open GApps), and pico otherwise.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. If you experience any issues with the Google applications, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
Stock-like setup
Disable the following built-in (AOSP) apps:
- Android keyboard (once you installed Gboard)
- Browser
- Calculator
- Camera
- Clock
- Email
- Gallery
Install the following apps from the Play store:
- Google Photos (https://play.google.com/store/apps/details?id=com.google.android.apps.photos)
- Calculator (https://play.google.com/store/apps/details?id=com.google.android.calculator)
- Chrome (https://play.google.com/store/apps/details?id=com.android.chrome)
- Clock (https://play.google.com/store/apps/details?id=com.google.android.deskclock)
- Gboard (https://play.google.com/store/apps/details?id=com.google.android.inputmethod.latin)
- Gmail (https://play.google.com/store/apps/details?id=com.google.android.gm)
- Google Calendar (https://play.google.com/store/apps/details?id=com.google.android.calendar)
- Google Camera (https://play.google.com/store/apps/details?id=com.google.android.GoogleCamera)
- Google Now Launcher (https://play.google.com/store/apps/details?id=com.google.android.launcher)
Rooting
You can flash the latest SuperUser (phh's open source fork), Chainfire's SuperSU, or Magisk to get rooted.
Oreo/Pie Status & CAF Notes
Oreo 8.1 builds are almost bug-free at this point, but still tagged as experimental. While last issues are sorted out, I will trigger manual builds, also published at https://builds.unlegacy-android.org/aosp-8.1/hammerhead.
To my knowledge, these are the remaining issues:
Bluetooth HFP speaker (mono/SCO) output is garbled. This seems related to a more general issue with audio effect/ACDB blobs.
Once all visible issues are fixed, and stability is comparable to Nougat builds, I'll switch on official builds on our Jenkins server.
Pie 9.0 builds are also becoming fully usable. Current builds have the same one remaining HFP bug described above.
Beyond "official" experimental builds, I post personal builds (including CAF experiments) in the hammerhead folder here.
Regarding sources for the WIP CAF kernel-based builds, see https://github.com/airend/android_kernel_lge_hammerhead/commits/tmp/caf+113+common. Corresponding device tree is still in rough shape and not uploaded yet, but assuming everything goes well, it'll replace current device tree when it's ready.
I've used the 05/04 build for 2 days a few weeks ago and it was a great rom.
The only issue I came across back then was that it has the green flickering when recording videos.
It's nice that the project has a XDA thread now and I gonna test this rom asap.
Thanks for keeping our good old Nexus 5 up to date.
Nexive said:
The only issue I came across back then was that it has the green flickering when recording videos.
Click to expand...
Click to collapse
Should be fixed on current builds (both green bar, and Google Camera flickering).
have a volume wake option?
Does it have issues with network location (Battery saver location)?
Some AOSP-based ROMs have this issue, so many apps (Chronus, Google Fit, f.lux, Instagram) can't get location.
alessio89g said:
Does it have issues with network location (Battery saver location)?
Some AOSP-based ROMs have this issue, so many apps (Chronus, Google Fit, f.lux, Instagram) can't get location.
Click to expand...
Click to collapse
No, all UA ROMs have this issue fixed
Ziyan said:
No, all UA ROMs have this issue fixed
Click to expand...
Click to collapse
Great, I think I'll try this ROM tomorrow!
--- --- ---
EDIT:
Is there any kind of changelog?
--- --- ---
RE-EDIT:
Okay, I found this:
https://gerrit.unlegacy-android.org
Hi....
Any screen shot?
keretapanau said:
Any screen shot?
Click to expand...
Click to collapse
Umm… it's barebones AOSP?
Buttery smooth,everything seems to be working fine here..Awesome jobs dev..keep it up.Finally this is the rom i been waiting for.:good:
CreateYourDream said:
have a volume wake option?
Click to expand...
Click to collapse
It is not an AOSP feature. It is something custom roms introduced.
Android-Andi said:
It is not an AOSP feature. It is something custom roms introduced.
Click to expand...
Click to collapse
thanks for answer, but i have broken power button :crying:
Cant Install Gapps
I've flashed it for about half a day, and it's very promising, it seems a great ROM!
I've noticed only three defects:
- The blue light filter (Night mode) is missing;
- With stock kernel, SuperSU will be in system mode;
- The Clock app crashes if you try to add another Time zone in the main screen.
Everything else works fine.
CreateYourDream said:
thanks for answer, but i have broken power button :crying:
Click to expand...
Click to collapse
Did you try this
Check out "Custom Navigation Bar"
https://play.google.com/store/apps/details?id=xyz.paphonb.systemuituner
Thanks for the ROM guys!
When I flash Open Gapps this message appears:
"This Gapps pkg is for Android 7.1.x ONLY
Please download the correct version for you ROM: 5.1.1 (SDK 22)"
I've flashed build ua_hammerhead-7.1.2-20170423031839 before gapps
Is there any alternative app for kcal..?KCAL app seems to be force closing once installed.
substratum support please
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 9.x (Pie),which is designed to increase performance and reliability over stock Android for your device.All the source code for LineageOS is available in the LineageOS GitHub repo.And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.Official LineageOS website : http://lineageos.org
Downloads Links
LineageOS 16.0 (Unlocked Bootloader) :Test builds :
lineage-16.0-20191019-UNOFFICIAL-odin.zip | by CyberWalkMaN for Xperia ZL
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Google Applications (optional) :OpenGapps : http://opengapps.org/ (Use packages for ARM, Android 9.0, Nano or Pico)Information : Flash the GApps before the first boot. If not, a clean flash is recommended.Flashing and updatingLineageOS clean install :- (Optional) Flash the boot.img kernel from the ROM zip with Fastboot or Flashtool- (Optional) Wipe the data & cache (Backup to make sure not to loose data)- Flash the LineageOS ROM zip from the Recovery- (Optional) Flash the GApps to have the Google Applications- (Optional) Every additional zip you want to flash- RebootLineageOS update / upgrade :- (Information) Don't wipe anything unless you want to- (CM / UNOFFICIAL) Nothing to wipe when switching- (FUTURE RELEASES) Might need clean, informations will be updated- Flash the latest LineageOS ROM zip from the Recovery- (Optional) Flash the GApps on first install / upgrade. Not required later, but do update sometimes- (Optional) Every additional zip you want to flash- RebootLineageOS addonsu for root access :- (Information) Read the Root section of the Q&A thread- (Download) Download the addonsu for arm : LineageOS Downloads / Extras- (Optional) Flash the zip on a working Lineage installation (once)- (Information) Upon ROM updates, the addonsu is preserved- Reboot
Issues and reports- Report issues only if you are using the ROM kernel- If an additional mod is installed, make sure it's unrelated, and mention it- Make sure the issue wasn't discussed earlier in the threads- Share a log of the error with CatLog for example
About LineageOS Legal : http://lineageos.org/legal/The LineageOS team would like to thank everyone involvedin helping with testing, coding, debugging & documenting! Enjoy!
Also thanks to :- The LineageOS Team- The CyanogenMod Team- Everyone involved in working and testing
XDA:DevDB Information
[ROM][FINAL][9.0] LineageOS 16.0 for Xperia ZL, ROM for the Sony Xperia ZL
Contributors
CyberWalkMaN, AdrianDC
Source Code: https://github.com/fusion3-common
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Created 2019-04-22
Last Updated 2019-10-20
FEATURES AND ISSUES
Code:
- Boot : Ok
- GApps : OpenGApps Nano Ok
- FOTA Recovery : Ok (see below)
- WiFi : Ok (real SONY MAC address)
- Bluetooth : Ok (real SONY MAC address)
- WiFi Hotspot : Ok (2.4GHz only)
- RIL - Phone - Data : Ok
- GPS : Ok
- Camera : Ok
- Camcorder : Ok
- MicroSD : Ok
- Accelerometer : Ok
- Compass : Ok
- Gyroscope : Ok
- AOSP sensors : Ok
- FM Radio : Ok
- Vibrator : Ok
- Microphone : Ok
- Audio & external audio : Ok
- Bluetooth audio : Ok
- NFC : Ok
- Kernel : Ok
- Graphics : Ok
- 3D Rendering : Ok
- Clock : Ok
- Offline Charging : Ok
- SEPolicies : Work In Progress
At the moment, FM radio, manual network selection and auto brightness does not work (maybe something else). New builds will be uploaded as source updates / bug fixes are updated.
camera ok?
using as a daily cell phone, this is fast, congratulations.
Switch from nkomarn Lineage 16.O build. Camera works okay, so it was great. Only problem is flashing twrp, cannot successful flash using the app. Always go back to lineage recovery even light indicator goes purple to orange. Any workaround?
Also power off function not work, it rebooted. Anyways, it was great and thank you for continue work on this. Cheers! ?
Sent from my Sony Xperia ZL using XDA Labs
Just started testing this Rom, my feedback for now is:
Autorotate is not working.
Can't change any sound (calls, SMS, etc)- (APP crashes).
I've experienced some random reboots in the first few hours after flashing, it seems stable now.
Advanced reboot is not working properly.
Magisk is working fine.
Nova Launcher is working fine.
I'll continue to test...
Hope my feedback can help make this better.
hi, many thanks to develper! smooth running even such older device! the only issue is battery indicator always start from 12% but I am not sure if it is common issue.
Flash the latest build 0803, Sensors are now working. Auto Rotate is working, since sensor driver is there. FM Working properly also.
Still have issue on Turn Off, it keep restarting.
Cannot able to flash Twrp Recovery, still booting to lineage recovery.
But still, thank you for your time on updating this Rom
Sent from my Sony Xperia ZL using XDA Labs
Fiz uma instalação limpa do zero. Há 2 dias estou usando e sem bugs, ou reinicialização inesperada. Ótimo trabalho e muito obrigado por isso =D
New build uploaded (lineage-16.0-20190824-UNOFFICIAL-odin.zip), major changes since May:
All sensors works now (Thanks to @Chippa_a)
Manual network selection fixed
Telegram calls fixed (Need to confirm)
FM Radio fixed
Small gps improvement
Performance improvement
Updated kernel (fixed bug with rebooting instead of shutting down and some other bugs), also we now use binder and lmk from AOSP 3.18 kernel
SELinux denials resolved at 90%
Magisk issue fixed
Android 9.0.0_r46 (August security patches)
Addonsu is already included, you can enable root access in the developer settings
CyberWalkMaN said:
New build uploaded (lineage-16.0-20190824-UNOFFICIAL-odin.zip), major changes since May:
All sensors works now (Thanks to @Chippa_a)
Manual network selection fixed
Telegram calls fixed (Need to confirm)
FM Radio fixed
Small gps improvement
Performance improvement
Updated kernel (fixed bug with rebooting instead of shutting down and some other bugs), also we now use binder and lmk from AOSP 3.18 kernel
SELinux denials resolved at 90%
Magisk issue fixed
Android 9.0.0_r46 (August security patches)
Addonsu is already included, you can enable root access in the developer settings
Click to expand...
Click to collapse
Thank you for the update! I dirty-flashed it over the 0803 build. You see, I run the stable Magisk v19.3, which, along with some modules, then allowed me to pass both Safetynet tests. Not anymore. As you stated that Selinux was almost ready, I had uninstalled ibuprophen's The SELinux Switch app prior to flashing the new build. I was using it in order to set Selinux to enforcing. As Selinux is still off in the new build, I tried to install the app back, but the new build doesn't allow me to do it. Even the zip, although correctly installed in recovery, after booted up, no SELinux Swich app is in the drawer, because directory /data/app/com.ibuprophen.selinux-1 has been deleted during the boot up process! What's happening?
EDIT: I decided to do a clean install. Everything is back to normal! Thanks, anyway!
Pixel Launcher
Thanks again for your hard work in bringing Android 9 to this very old, but still powerful, device of ours.
Well, I prefer Pixel Launcher over the embedded home app, but it keeps crashing all the time upon being selected as the default home app. For those who also plan to use Pixel Launcher, edit /data/system/packages.xml, and add up the following entries, under <package name="com.google.android.apps.nexuslauncher"> and <perms>:
Code:
<item name="android.permission.STATUS_BAR" granted="true" flags="0" />
<item name="android.permission.MANAGE_ACTIVITY_STACKS" granted="true" flags="0" />
Could you make such changes in your next build?
After flashing the 0824 build, i experienced much better scrolling experience, performance improved a lot.
Also Twrp works now and turn off function work properly, no need to reboot and press volume down go to stock recovery just to turn this off. So thank you for continue working on this
Sent from my Sony Xperia ZL using XDA Labs
I thank you for continuing to develop! I'll install that, i report issues!
Perfect, bug-free, fast and stable ROM, using with magisk, everything runs perfectly.
New build uploaded (lineage-16.0-20191019-UNOFFICIAL-odin.zip), major changes since August:
Fast battery drain fixed (for 15.1 nightlies too)
SELinux denials resolved at 99% (You can make builds in enforced SELinux, but I would recommend continuing to build them in permissive). Current build in permissive SELinux.
Oktober security patches
Minor performance and stability improvements (for 15.1 nightlies too)
Added missing props for gps and Miracast.
Build status - Stable.
Addonsu is already included, you can enable root access in the developer settings
This is where my support for android 8-9 for Z/ZL/ZR/Tablet Z ends, this build will be the last. All the changes made in the sources are already available on github.com/LineageOS, if someone wants to continue supporting and get the official LineageOS 16.0 - write to PM, I will explain in detail what remains to be done in the sources. Also, if someone wants to try to build other roms for our devices based on android 8-9 from the available sources - try to choose CAF-based roms (for example, AOKP, LineageOS, Ressurection Remix, AICP, etc.), then with 95% chance you will build and run the rom. Our sources are based on CAF, and for the build of roms based on AOSP, additional fixes are required, plus there will be problems with sound anyway.
I also want to note that I made a most part of the changes made in 16.0 to the official 15.1 nightlies, which should significantly improve their stability and performance
CyberWalkMaN said:
New build uploaded (lineage-16.0-20191019-UNOFFICIAL-odin.zip), major changes since August:
Fast battery drain fixed (for 15.1 nightlies too)
SELinux denials resolved at 99% (You can make builds in enforced SELinux, but I would recommend continuing to build them in permissive). Current build in permissive SELinux.
Oktober security patches
Minor performance and stability improvements (for 15.1 nightlies too)
Added missing props for gps and Miracast.
Build status - Stable.
Addonsu is already included, you can enable root access in the developer settings
This is where my support for android 8-9 for Z/ZL/ZR/Tablet Z ends, this build will be the last. All the changes made in the sources are already available on github.com/LineageOS, if someone wants to continue supporting and get the official LineageOS 16.0 - write to PM, I will explain in detail what remains to be done in the sources. Also, if someone wants to try to build other roms for our devices based on android 8-9 from the available sources - try to choose CAF-based roms (for example, AOKP, LineageOS, Ressurection Remix, AICP, etc.), then with 95% chance you will build and run the rom. Our sources are based on CAF, and for the build of roms based on AOSP, additional fixes are required, plus there will be problems with sound anyway.
I also want to note that I made a most part of the changes made in 16.0 to the official 15.1 nightlies, which should significantly improve their stability and performance
Click to expand...
Click to collapse
Thanks for your hardwork and making a stable build, but i encounter issue Installing it.
Clean Flash it including system, but result in Rebooting to twrp, tried to flash previous Build then Update, stuck to Boot Animation and Reboot to Twrp. I'm quite sure the file is not corrupted, downloaded it two times. Sadly it was the Final build but hoping you will address and fix it. Thanks
[Updated]
Hello!!
Kran007 said:
Thanks for your hardwork and making a stable build, but i encounter issue Installing it.
Clean Flash it including system, but result in Rebooting to twrp, tried to flash previous Build then Update, stuck to Boot Animation and Reboot to Twrp. I'm quite sure the file is not corrupted, downloaded it two times. Sadly it was the Final build but hoping you will address and fix it. Thanks
[Updated]
Click to expand...
Click to collapse
Could you try the rom? or you can't intall it anyway? I gonna try it in the xperia zl that i will give to my father, but i can't get some error, He gona kill me! Actually , his ZL is running august version.
Can someone make a Build with December Security Patch?
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
Magisk Patched Unofficial GrapheneOS for the Pixel 6 / 6 Pro (oriole/raven)
This ROM will allow you to lock the boot loader. Do not ever disable the OEM unlocking checkbox when using a locked bootloader with root.
This is critically important. With root access, it is possible to corrupt the running system, for example by zeroing out the boot partition.
In this scenario, if the checkbox is turned off, both the OS and recovery mode will be made unbootable and fastboot flashing unlock will not be allowed.
This effectively renders the device hard bricked.
I am not responsible for any harm you may do to your device, follow at your own risk etc etc, Rooting your device can potentially introduce security flaws, I am not claiming this to be secure. If you would like to have more security and peace of mind then I highly recommend you follow This Guide to build this rom using your own encryption keys.
GrapheneOS is a privacy and security focused mobile OS with Android app compatibility developed as a non-profit open source project. It's focused on the research and development of privacy and security technology including substantial improvements to sandboxing, exploit mitigations and the permission model. It was founded in 2014 and was formerly known as CopperheadOS.
The features page provides an overview of the substantial privacy and security improvements added by GrapheneOS to the Android Open Source Project (AOSP). Many of the past features were contributed to AOSP, Linux and other projects to improve privacy and security for billions of users so they're no longer listed on the features page.
More info:
Official releases are available on the releases page (Not Magisk Patched) and installation instructions are on the install page.
GrapheneOS also develops various apps and services with a focus on privacy and security. Vanadium is a hardened variant of the Chromium browser and WebView specifically built for GrapheneOS. GrapheneOS also includes our minimal security-focused PDF Viewer, our hardware-based Auditor app / attestation service providing local and remote verification of devices, our modern privacy / security focused camera app, and the externally developed Seedvault encrypted backup which was initially developed for inclusion in GrapheneOS.
No Google apps or servicesGrapheneOS will never include either Google Play services or another implementation of Google services like microG. It's possible to install Play services as a set of fully sandboxed apps without special privileges via our sandboxed Google Play compatibility layer. See the FAQ section for more details on our plans for filling in the gaps from not shipping Play services and Google apps.
Installation Instructions: Fashing-factory-image
Locking the bootloader is Optional but does increase the device security Locking-the-bootloader
Update Instructions: simply follow these instructions Updates-sideloading to sideload the latest patched OTA update package (You can update from any previous version if using full ota update)
Android OS Version: 13
Current Version: See Post #2
Download: See Post #2
Sources: GrapheneOS - AVBRoot - Magisk - Patch Guide
PayPal Donation Link
Builds for Pixel 6 Pro (Raven)
Magisk-Patched GrapheneOS Factory Install Build
Full system install builds for clean and new installs
Build based on release#2023061402 (2023-06-14)
SourceForge_Download
Build based on release#2023050100 (2023-05-01)
SourceForge_Download
Build based on release#2023041100 (2023-04-11)
SourceForge_Download
Build based on release#2023032000 (2023-03-20)
SourceForge_Download
Build based on release#2023022300 (2023-02-23)
SourceForge_Download
Build based on release#2023020600 (2023-02-06)
SourceForge_Download
Build based on release#2023020200 (2023-02-02)
SourceForge_Download
Build based on release#2023012500 (2023-01-25)
SourceForge_Download
Build based on release#2023011000 (2023-01-10)
SourceForge_Download
Build based on release#2023010300 (2023-01-03)
Anonfiles Download | 1fichier Download | SourceForge_Download
Build based on release#2022122000 (2022-12-20)
Anonfiles Download | 1fichier Download
Build based on release#2022121400 (2022-12-14)
Anonfiles Download | 1fichier Download
Build based on release#2022121100 (2022-12-11)
Anonfiles Download | 1fichier Download
Build based on release#2022120300 (2022-12-03)
Anonfiles Download | 1fichier Download
Build based on release#2022113000 (2022-11-30)
Anonfiles Download
Build based on release#2022112500 (2022-11-25)
Anonfiles Download
Build based on release#2022111800 (2022-11-18)
Anonfiles Download
Build based on release#2022111000 (2022-11-10)
Anonfiles Download
Build based on release#2022101800 (2022-10-18)
Anonfiles Download
Click to expand...
Click to collapse
Magisk Patched OTA Update packages
Full OTA Builds will let you update from any older version
Patched OTA based on release#2023061402 (2023-06-14)
SourceForge_Download
Patched OTA based on release#2023050100 (2023-05-01)
SourceForge_Download
Patched OTA based on release#2023041100 (2023-04-11)
SourceForge_Download
Patched OTA based on release#2023032000 (2023-03-20)
SourceForge_Download
Patched OTA based on release#2023022300 (2023-02-23)
SourceForge_Download
Patched OTA based on release#2023020600 (2023-02-06)
SourceForge_Download
Patched OTA based on release#2023020200 (2023-02-02)
SourceForge_Download
Patched OTA based on release#2023012500 (2023-01-25)
SourceForge_Download
Patched OTA based on release#2023011000 (2023-01-10)
SourceForge_Download
Patched OTA based on release#2023010300 (2023-01-03)
Anonfiles Download | 1fichier_Download | SourceForge_Download
Patched OTA based on release#2022122000 (2022-12-20)
Anonfiles Download | 1fichier_Download
Patched OTA based on release#2022121400 (2022-12-14)
Anonfiles Download | 1fichier Download
Patched OTA based on release#2022121100 (2022-12-11)
Anonfiles Download | 1fichier Download
Patched OTA based on release#2022120300 (2022-12-03)
Anonfiles Download | 1fichier Download
Patched OTA based on release#2022113000 (2022-11-30)
Anonfiles Download
Patched OTA based on release#2022112500 (2022-11-25)
Anonfiles Download
Patched OTA based on release#2022111800 (2022-11-18)
Anonfiles Download
Patched OTA based on release#2022111000 (2022-11-10)
Anonfiles Download
Patched OTA based on release#2022110800 (2022-11-08)
Anonfiles Download
Click to expand...
Click to collapse
Builds for Pixel 6 (oriole)
Always do a backup of your data before flashing any updates, just in case.
I make no promises that this works or that I will provide regular updates. I will attempt to provide updates when they are available and I have time, you may have issues with this rom, you could lose your data or brick your device (although it's very unlikely if you follow the instructions and use common sense)
#Reserved
Isn't there already an official build for graphene for Raven?
iBe.Jacob said:
Isn't there already an official build for graphene for Raven?
Click to expand...
Click to collapse
Yes. But not for a rooted version of it.
New Release 2022111800
Changes since the 2022111000 release:
don't skip ahead-of-time (AOT) compilation of apps that weren't recently used since we depend on full AOT compilation being done for performance rather than JIT compilation with background JIT profile guided AOT compilation like Android
battery usage UI: use fallback name for unknown components
change minimal value of battery saver schedule to 5% again as it was before Android 13
enable the post-upgrade "Optimizing apps" progress indication UI
app crash UI: show process uptime and optional extra text
Sandboxed Google Play compatibility layer: show version of GmsCompatConfig in the crash UI
Sandboxed Google Play compatibility layer: stop splitting multi-package PackageInstaller sessions
Sandboxed Google Play compatibility layer: improve handling of activity starts
Sandboxed Google Play compatibility layer: bugfix: Parcel position wasn't reset by dynamic stubs
Sandboxed Google Play compatibility layer: bugfix: missing handling of ListSlices in dynamic stub
GmsCompatConfig: make sure Play Store PhenotypeFlags are overridable by Gservices flags (further deterring Play Store trying to update Play services / Play Store beyond supported versions)
Pixel 7, Pixel 7 Pro (adevtool): drop unused face unlock components since we have no plans to enable support for an insecure face unlock implementation incapable providing reasonable security due to lack of dedicated face unlock hardware (Pixel 4 and Pixel 4 XL had dual infrared cameras, IR dot projector and IR flood illuminator providing a more secure biometric unlock system than fingerprint unlock as opposed to simply using the front camera in a way that could be done on any device)
Pixel 4, Pixel 4 XL, Pixel 4a, Pixel 4a (5G), Pixel 5, Pixel 5a, Pixel 6, Pixel 6 Pro, Pixel 7, Pixel 7 Pro: include gril library to avoid qns crash on Pixel 7 and Pixel 7 Pro
Pixel 7, Pixel 7 Pro: include vendor_kernel_boot partition requirement in factory images metadata to force an error with an incompatible fastboot such as the currently buggy Arch Linux package
kernel (Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro): update GKI to Linux 5.10.150
Auditor: update to version 66
Click to expand...
Click to collapse
Download in Post #2
I don't see a real value in locking the bootloader. In theory, the only thing it protects is undetectable modification being made when the device is out of your direct control. However, strong security practices require you to assume that *anything* could have been done to the device when it is outside of your direct control, so the "security" you get from the locked bootloader is artificial.
ANY time a device leaves your physical control, you have to assume it to be compromised. No exceptions.
I would also like to point out that, no offense to OP, but using a "high security" operating system that *HAS* been modified by an unknown 3rd party.... is insane. I'd recommend that anyone interested in this actually take the time to understand the process and reproduce it on their own.
96carboard said:
I don't see a real value in locking the bootloader. In theory, the only thing it protects is undetectable modification being made when the device is out of your direct control. However, strong security practices require you to assume that *anything* could have been done to the device when it is outside of your direct control, so the "security" you get from the locked bootloader is artificial.
ANY time a device leaves your physical control, you have to assume it to be compromised. No exceptions.
I would also like to point out that, no offense to OP, but using a "high security" operating system that *HAS* been modified by an unknown 3rd party.... is insane. I'd recommend that anyone interested in this actually take the time to understand the process and reproduce it on their own.
Click to expand...
Click to collapse
Sorry but I am not interested in arguing about this stuff
I didn't create this thread to argue about potential security issues or how secure phones really are
it seems you have more of an issue with the security of Android in general
I would recommend everyone who just wants to share opinions like this which are essentially unrelated to the ROM, please just don't
I am not claiming rooting your phone to be perfectly secure and I am not interested in arguing about it
Although as explained here https://forum.xda-developers.com/t/...pdated-november-9-2022.4343431/#post-85733797
there are advantages to using a locked bootloader, even with root.
optimumpro said:
The rom could be used on locked bootloader with ROOT (donate feature) with or without Gapps.
The benefits of LOCKED BOOTLOADER combined with WORKING AVB-2 protection are:
Get back your DRM L1 certificate. Most banking apps will work regardless of Magisk.
Security: Nobody and nothing can modify Kernel, Recovery and Virtual Partitions without triggering a red screen of death with the message 'your device is corrupted and cannot boot'.
At that point, the only option is to unlock bootloader. But, if a user had previously disabled OEM unlock in Developer settings, then unlocking becomes unavailable, and so does flashing via fastboot. In other words, if your phone gets into the hands of an adversary, their only option is to use MSM tool to make the phone work again, but no access to your data or any other partition.
Why prebuilt Magisk? Because you can't modify kernel or recovery on locked bootloader post installation, and that's exactly what Magisk does.
Click to expand...
Click to collapse
I am offering this as a free feature, not a donate feature and I have also created a guide so that anyone is able to build the rom and sign it using their own keys for even greater security than trusting me.
Magisk isn't just some unknown third party, Graphene, Magisk, AVBRoot, they are all open source projects
FireRattus said:
Sorry but I am not interested in arguing about this stuff
I didn't create this thread to argue about potential security issues or how secure phones really are
it seems you have more of an issue with the security of Android in general
I would recommend everyone who just wants to share opinions like this which are essentially unrelated to the ROM, please just don't
I am not claiming rooting your phone to be perfectly secure and I am not interested in arguing about it
Click to expand...
Click to collapse
I'm not talking about the utility or security of root (hint: Its perfectly safe and secure when used RESPONSIBLY). I'm talking about the value of using a security hardened OS with modifications made by someone who you don't know and can't trust. Doing so throws away ALL security because there is no way to tell what else someone has changed.
96carboard said:
I'm not talking about the utility or security of root (hint: Its perfectly safe and secure when used RESPONSIBLY). I'm talking about the value of using a security hardened OS with modifications made by someone who you don't know and can't trust. Doing so throws away ALL security because there is no way to tell what else someone has changed.
Click to expand...
Click to collapse
So just follow the guide I provided so you can build the rom yourself, you can inspect all the source code and work out exactly what it's all doing if you are so inclined
https://forum.xda-developers.com/t/...-using-rooted-grapheneos-magisk-root.4510295/
FireRattus said:
So just follow the guide I provided so you can build the rom yourself, you can inspect all the source code and work out exactly what it's all doing if you are so inclined
https://forum.xda-developers.com/t/...-using-rooted-grapheneos-magisk-root.4510295/
Click to expand...
Click to collapse
Yes exactly!
@FireRattus is there any chance we can see pre-build images for Oriole in the future? I'm having trouble building it myself.
KainoaK said:
@FireRattus is there any chance we can see pre-build images for Oriole in the future? I'm having trouble building it myself.
Click to expand...
Click to collapse
What are the troubles you are having with building it yourself? I can try my best to help
I would be able to build images for Oriole probably but I wouldn't be able to test them myself and building for more variants would take more time making updates slower so I don't want to invest in that currently.
I do think it's best to build it yourself if you are able so I am glad you have tried already
> What are the troubles you are having with building it yourself? I can try my best to help
My computer just doesn't have enough RAM + Disk space to build it, plus I seem to keep getting stuck at getting all the tools to work together
I'd be happy to donate monthly or whatnot to help keep up oriole builds though
KainoaK said:
> What are the troubles you are having with building it yourself? I can try my best to help
My computer just doesn't have enough RAM + Disk space to build it, plus I seem to keep getting stuck at getting all the tools to work together
I'd be happy to donate monthly or whatnot to help keep up oriole builds though
Click to expand...
Click to collapse
I will try to build it for you, since the pixel 6 and 6 pro share the same Build ID, I should be able to build it without needing to download everything again
New Release #2022112500
Changes since the 2022111800 release:
Sandboxed Google Play compatibility layer: fix missing handling of APEX ListSlices in dynamic stubs (improves compatibility when granting Nearby devices permission to Play services with a WearOS device connected)
Sandboxed Google Play compatibility layer: mark PackageInstallerStatusForwarder as not exported
Settings: avoid OBB toggle unnecessarily force stopping app
extend original-package renaming to static launcher shortcuts to fix Vanadium new tab shortcut for users with an install predating the package rename
Camera: update to version 57
Vanadium: update Chromium base to 107.0.5304.141
Contacts: add support for dark mode
kernel (Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro): restore fix for CVE-2022-3176 which was reverted upstream (GKI LTS branch) due to not being marked as a security fix and changing the GKI ABI
Pixel 4, Pixel 4 XL: set frozen patch level string to 2022-11-01 (has been provided since the 2022110800 release but we initially left the patch level string at the previous value)
port GrapheneOS changes to Linux 5.15 GKI LTS branch in order to prepare for 6th/7th generation Pixels potentially moving to the Linux 5.15 LTS and late 2023 devices which will be based on it
Click to expand...
Click to collapse
Download in Post #2
KainoaK said:
My computer just doesn't have enough RAM + Disk space to build it, plus I seem to keep getting stuck at getting all the tools to work together
I'd be happy to donate monthly or whatnot to help keep up oriole builds though
Click to expand...
Click to collapse
I am not able to test them myself but I have provided a patched, signed build which should work
just check post #3 for the download links, I would appreciate a donation if you feel it's worth it but no pressure
Edit: Moved it to post #2 with the other downloads
96carboard said:
I don't see a real value in locking the bootloader. In theory, the only thing it protects is undetectable modification being made when the device is out of your direct control. However, strong security practices require you to assume that *anything* could have been done to the device when it is outside of your direct control, so the "security" you get from the locked bootloader is artificial.
ANY time a device leaves your physical control, you have to assume it to be compromised. No exceptions.
I would also like to point out that, no offense to OP, but using a "high security" operating system that *HAS* been modified by an unknown 3rd party.... is insane. I'd recommend that anyone interested in this actually take the time to understand the process and reproduce it on their own.
Click to expand...
Click to collapse
To be fair you'll always be using something done by a third party, including android itself, unless it's you writing and compiling your own OS.
MidnightDevil said:
To be fair you'll always be using something done by a third party, including android itself, unless it's you writing and compiling your own OS.
Click to expand...
Click to collapse
Android is open source. Open source code is auditable. Compiled binaries are NOT.