{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), which is designed to increase performance and reliability over stock Android for your device.
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. Linked below is a package that has come from another Android project that restore the Google parts. 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 out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
This build includes microG, a free and open implementation of the Google Play Services Framework. It allows applications calling proprietary Google APIs to run on AOSP-based ROMs like Replicant and LineageOS. Acting as a replacement for the closed-source Google Apps (GAPPS), it is a powerful tool to reclaim your privacy while enjoying Android core features such as Google Cloud Messaging.
It also includes WireGuard, a next generation secure VPN tunnel for the Linux kernel, with modern yet conservative cryptography and simple design principles. It is meant as a replacement for OpenVPN and for IPsec, and generally has better performance and security characteristics than both. It also is much easier to use. The whitepaper was peer reviewed for NDSS17 and the protocol itself has been formally verified. Since it lives in the kernel, it not only is very fast, but it is able to integrate in clever ways that are quite nice for battery life and overall smoothness. There are already commercial VPN providers offering services using WireGuard, and it is very easy to run your own WireGuard servers as well.
I probably won't do other types of builds unless somebody has a really terrific suggestion. These builds exists for my own convenience and I thought I'd share it with the XDA community where I've been lurking and leeching for years.
Features
Embedded root (can be enabled in Developer Settings)
Restricted (system-only) signature spoofing
microG (FakeStore, GmsCore, GsfProxy, legacy mapsv1 implementation)
Mozilla Location Services + Nominatim for network-based location
FDroid (+Privileged Extension)
WireGuard-enabled LineageOS kernel
Monthly automagical OTA updates (signed builds, https)
Reporting Bugs
I just build using the latest official LineageOS (also see this thread), wireguard patch, TheMuppets proprietary files and microG prebuilts. Report any "regular" bugs to those threads and/or Git pages unless you're sure the problem is unique to these builds.
Initial installation
NOTE: TWRP gets replaced by the stock recovery every time you install a ROM zip. Either use fastboot to boot TWRP or flash the TWRP zip file every time after you flash a ROM zip.
OnePlus firmware must be installed on your device on both A/B slots. Hence the instructions below tell you to flash OxygenOS twice.
Wipe system, data and cache.
Flash latest OxygenOS using TWRP.
Reboot to TWRP
Flash OxygenOS again using TWRP.
Reboot to TWRP
Flash the newest build using TWRP.
Reboot to TWRP.
Flash the newest build using TWRP again.
Reboot and enjoy!
OTA Updates
For OTA updates, use the built-in Updater app. Everything should JustWork(TM) without any TWRP/recovery magic.
Downloads
https://lineage.darwinkel.net/builds/full
Delta/partial updates are not supported.
I recommend Aurora Store if you want to download and install apps from Google Play.
Hi,
Many thanks!
What's the process if we want to install opengapps, magisk and custom kernel?
Will they survive to OTA?
Cygnust said:
Hi,
Many thanks!
What's the process if we want to install opengapps, magisk and custom kernel?
Will they survive to OTA?
Click to expand...
Click to collapse
This build has a free software alternative to opengapps baked-in. This ROM is probably not what you're looking for if you want to install the regular Google Play Services. No clue about Magisk or a custom kernel surviving OTA.
Thanks for the ROM (and the nice presentation!). Do you know if Magisk work properly with your ROM since it has embedded root? Is there any "interference"?
Tomatot- said:
Thanks for the ROM (and the nice presentation!). Do you know if Magisk work properly with your ROM since it has embedded root? Is there any "interference"?
Click to expand...
Click to collapse
I don't use Magisk so I'm not certain, but I don't think it should cause any problems. Do give it a try!
perhaps it's a stupid question but i can install google play to log in my games or restore the apps after install?
AndroidBolder said:
I don't use Magisk so I'm not certain, but I don't think it should cause any problems. Do give it a try!
Click to expand...
Click to collapse
I would have omitted embedded root, to be taken care of by Magisk instead, because of certains apps that just do not work on rooted phones (that's what Magisk Hide is for).
Can somebody please try how it does with embedded root disabled in Developer Settings and Magisk installed?
Master One said:
I would have omitted embedded root, to be taken care of by Magisk instead, because of certains apps that just do not work on rooted phones (that's what Magisk Hide is for).
Can somebody please try how it does with embedded root disabled in Developer Settings and Magisk installed?
Click to expand...
Click to collapse
I'm not that fond of Magisk and neither are the LineageOS devs. I don't use any apps that use SafetyNet and this works for me personally (I mainly use root for Yalp Store and WireGuard). I have, however, tested it. I enabled DroidGuard and microG's SafetyNet attestation and tested it with an app. Unfortunately, it didn't seem to pass even with root disabled in developer settings. Magisk Hide might help, though.
Toni Moon said:
perhaps it's a stupid question but i can install google play to log in my games or restore the apps after install?
Click to expand...
Click to collapse
I'm pretty sure you can install a Google Play Store APK, but you would have to disable or remove FakeStore for it to work, I think. I personally use Yalp Store to download apps from Google Play (including paid ones).
EDIT: download speeds have been fixed.
1 Question, how to get snapchat and chromecast work?
TheMellowOne said:
1 Question, how to get snapchat and chromecast work?
Click to expand...
Click to collapse
I don't use either of those apps, no clue.
Can I use blue Spark twrp?
noky76 said:
Can I use blue Spark twrp?
Click to expand...
Click to collapse
You can.
@AndroidBolder, I have done some extended research concerning VoLTE & VoWiFi today. I have found a way to explicitly enable VoLTE & VoWiFi using build.prop and both are working on LineageOS, but the problem is that it does not show the VoLTE & VoWiFi symbols in the display (which is a problem if you are abroad and can not be sure if you are indeed using VoWiFi without going to airplane).
FYI It's fully working on OOS, partly working on HAVOC OS (only VoLTE, but not VoWiFi) and not working at all on OmniROM.
@AndroidBolder, what's the easiest way to remove su from your build? Can the file addonsu-remove-15.1-arm64-signed.zip from the offical Extras repo be used (although it's for 15.1)? Or would you be so kind to create a flashable su removal for your build?
This is exactly what I've been waiting for. One question though before I flash it, how is the battery life?
Master One said:
@AndroidBolder, I have done some extended research concerning VoLTE & VoWiFi today. I have found a way to explicitly enable VoLTE & VoWiFi using build.prop and both are working on LineageOS, but the problem is that it does not show the VoLTE & VoWiFi symbols in the display (which is a problem if you are abroad and can not be sure if you are indeed using VoWiFi without going to airplane).
FYI It's fully working on OOS, partly working on HAVOC OS (only VoLTE, but not VoWiFi) and not working at all on OmniROM.
Click to expand...
Click to collapse
Sounds really interesting, but the way you're putting it, it seems somewhat unstable/unreliable. VoLTE works fine with my carrier so I have no way to test it. If multiple people can confirm it works without causing instability then I'll consider changing build.prop.
Master One said:
@AndroidBolder, what's the easiest way to remove su from your build? Can the file addonsu-remove-15.1-arm64-signed.zip from the offical Extras repo be used (although it's for 15.1)? Or would you be so kind to create a flashable su removal for your build?
Click to expand...
Click to collapse
I presume addonsu remove would work, no clue if the 15.1 version works on Pie. Did a quick search but I can't find one for LOS16. Bingo! uploaded by Luk1337, one of the LOS devs.
admiralderp said:
This is exactly what I've been waiting for. One question though before I flash it, how is the battery life?
Click to expand...
Click to collapse
Like most custom roms slightly worse than OxygenOS, but completely fine otherwise!
Noob question, need forgiveness, does google maps work with it as I've tried microg on other roms but maps were not working. That's all I need from google(maps).
nksonfire said:
Noob question, need forgiveness, does google maps work with it as I've tried microg on other roms but maps were not working. That's all I need from google(maps).
Click to expand...
Click to collapse
It works on most custom ROMs as long as you use Maps 9.82.1
Thank you a TON for providing these builds. This finally gives me a path to move off of OxygenOS. Installed, tested, everything working beautifully *including VoLTE and VoWiFi* (on U.S. T-Mobile).
TheMellowOne said:
1 Question, how to get snapchat and chromecast work?
Click to expand...
Click to collapse
I have managed a way to get at the very least Snapchat working on this ROM.
Flash as normal.
After that, flash Magisk from TWRP.
Add the *Nanodroid*, not official, microG repo to F-Droid and install the DroidGuard Helper from there. You'll have to web-search "nanodroid fdroid repo" as I cannot provide external links on this new account.
(I've not tested any of this with the official repo's DroidGuard Helper, but there are issues on microG's Github repo suggesting that SafetyNet will only pass with Nanodroid's version of DroidGuard Helper.)
Install a file manager with root capability (such as Amaze on F-Droid) and navigate to /data/app where you will find the DroidGuard Helper under "org.microg.gms.droidguard-randomstringhere". Move this folder to /system/priv-app and reboot.
Make sure SafetyNet is on in microG Settings and ensure it is using the official server (by hitting the three dots in the corner, selecting Advanced and selecting "Use official server".)
Enable Magisk Hide in Magisk Manager and enable hiding for Snapchat and DroidGuard Helper.
Try SafetyNet attestation under Magisk Manager. Hopefully both checks should pass.
Enjoy.
I did a test OTA (the current 1/30/19 version is available there, so I just downloaded and installed it again) and the only changes to be made were to re-flash TWRP and Magisk then re-install DroidGuard Helper and move it to /system/priv-app. All microG and Magisk Manager settings were retained.
As your post says, I have a really terrificant suggestion.
Why don't you try to port Sailfish Os on op6?
If you think that my suggestion is not terrificant I will understand. I would like to port it but I can't do that. For many reasons. Bye and congrats for this build. it looks like great.
Ceers
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Moto Z2 Force
Code:
- Your warrenty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the official Lineage OS thread for the Motorola Moto Z2 Force, codename nash.
We support both the Sprint, International, and T-Mobile variants, as their bootloaders are unlockable, while we can 't support the Verizon and AT&T variants, as their bootloaders are permanently locked.
How to install:
Necessary Base Firmware: 8.0.0 (OCSX27.1.2, May 2018) (for TMO, or equivalent security patches for other variants)
Boot the newest TWRP .img from the Official TWRP Project Site.
In TWRP, click "Wipe", "Format Data", then type "yes" as prompted.
ADB sideload the newest weekly
(Optionally) You can flash the newest TWRP Installer also found at the Official TWRP Project Site if you wish to maintain TWRP, though the pre-installed Lineage Recovery instance will do everything you need it to in most cases. We don't recommend or support the use of the TWRP installer, as it is overwritten on every update (will need ot be re-installed every update), and has no addon.d-v2 persistence.
Click "Reboot, then choose "Recovery", this will boot you to either Lineage Recovery or TWRP depending on your choice to install TWRP or not. It is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic.
(Optionally) Flash GApps - MindTheGApps arm64 are recommended, OpenGApps are compatible with A/B as of 09102018, but I still only reccoemend and support MindTheGApps.
(Optionally) Flash SU - you'll need to turn it on from in developer settings after first boot Lineage OS SU Addon. - Magisk works fine, though is not supported.
Reboot
Known Problems:
Audio Mods don't work (this includes headphone jacks on mods) -- We can't fix this, don't use custom ROM's if you care about these.
Official Lineage OS builds will not ever allow Moto's Battery Mod "Efficiency Mode" to work -- though these can be made to work unofficially, join our discord if you're interested in this feature.
Wi-Fi Calling won't work until either the International or T-Mobile variant gets 8.1 blobs.
Ultrasonic Proximity Sensor doesn't work -- likely won't ever. It is used my Motorola's Active Display, but by nothing in Lineage.
Compass doesn't work -- no clue why.
Stock Display Color Profiles (the ones in Settings, "Display", "Colors") -- The ones in Settings, "Display", "LiveDisplay" work.
The default LiveDisplay "Natural" setting in Settings, "Display", "LiveDisplay", will occasionally dispaly color corruption, to deal with this, just swap to the "SRGB" profile, and swap back to "Natural", or leave it on "SRGB if you don't mind, then you won't experience those infrequent issues.
Notes:
Official Lineage OS builds will not pass CTS/SafetyNet -- due to the AVB flag's "red" status.
Official Lineage OS builds ship with full treble compatibility, with VNDK runtime enforcement! This means that unlike most "ported treble" you'll see, ours is just as it would be from the OEM, and can run any GSI (yes, even Pie!) without need for hacks or additional flashable zips. We relabeled /oem as /vendor (as /oem isn't used in custom ROM's anyway). To use a GSI, flash official Lineage, then flash your GSI, it's that simple! Flashing a factory image will likely write over /oem and remove the mock vendor image. Please don't report GSI bugs here, report them instead to the GSI's maker.
Download:
LineageOS Updater
XDA:DevDB Information
[OFFICIAL] [WEEKLIES] [TREBLE] Lineage OS 15.1, ROM for the Moto Z2 Force
Contributors
npjohnson, invisiblek, erfanoabdi
Source Code: https://github.com/LineageOS
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: 8.0.0 (OCSX*)
Based On: LineageOS
Version Information
Status: Stable
Created 2018-07-15
Last Updated 2019-03-18
first (always wanted to do that)
thanks for this, nice work everyone!!!
Nice, I was wondering when we were going to get an official thread. I'll be waiting for the 17th to install the weekly.
I have the international version (-05) and have installed plenty of these version (since unofficial release from both invisiblek site and ods.ninja site) as well as the official weeklies (all versions already released) and everything works (based on the description here and known issues), so I'd say it's safe to say intl version had been tested and known to be working as well.
Let me know if you need additional/specific tests that I can do here.
Thanks the official post!
Also, how about volte support? Is it supposed to work?
felipevsw said:
I have the international version (-05) and have installed plenty of these version (since unofficial release from both invisiblek site and ods.ninja site) as well as the official weeklies (all versions already released) and everything works (based on the description here and known issues), so I'd say it's safe to say intl version had been tested and known to be working as well.
Let me know if you need additional/specific tests that I can do here.
Thanks the official post!
Also, how about volte support? Is it supposed to work?
Click to expand...
Click to collapse
If it isn't in the bugs list, its expected to work, it works on TMO and SPR. And I'll flag the international as compatible, thanks.
Since it isn't in known issues, I assume VoIP compression was fixed?
Edit: known workaround is use Bluetooth for video/VoIP calls. I don't know if USB audio would work or not.
Uzephi said:
Since it isn't in known issues, I assume VoIP compression was fixed?
Edit: known workaround is use Bluetooth for video/VoIP calls. I don't know if USB audio would work or not.
Click to expand...
Click to collapse
Added to OP as an issue.
??? for listing known accurate issues ???
I was pissed after installing Invictrix rom only to find out sound mods don't work.
I'm having an issue with video calls on Whatsapp and Duo. The other person can't hear me and I can't hear the other person.
Some other issues:
- Ok google not working with screen off (but it's fine to me)
- Overview is messy sometimes when using multi-window (doesn't show previews of multi-windowed apps)
- Even when installing Moto Camera the app does not show secondary camera functions (Portrait, B/W, etc)
For my daily usage the audio on video calls is the most serious issue that drives me back to stock. I hope they fix it soon.
fixed, can remove this.
DTHayakawa said:
I'm having an issue with video calls on Whatsapp and Duo. The other person can't hear me and I can't hear the other person.
Some other issues:
- Ok google not working with screen off (but it's fine to me)
- Overview is messy sometimes when using multi-window (doesn't show previews of multi-windowed apps)
- Even when installing Moto Camera the app does not show secondary camera functions (Portrait, B/W, etc)
For my daily usage the audio on video calls is the most serious issue that drives me back to stock. I hope they fix it soon.
Click to expand...
Click to collapse
Anything that uses VoIP compression is broken. Most video calling or internet calling apps in general use it.
DTHayakawa said:
I'm having an issue with video calls on Whatsapp and Duo. The other person can't hear me and I can't hear the other person.
Some other issues:
- Ok google not working with screen off (but it's fine to me)
- Overview is messy sometimes when using multi-window (doesn't show previews of multi-windowed apps)
- Even when installing Moto Camera the app does not show secondary camera functions (Portrait, B/W, etc)
For my daily usage the audio on video calls is the most serious issue that drives me back to stock. I hope they fix it soon.
Click to expand...
Click to collapse
1. Added to known bugs.
2. I don't experience this (and if it is present, its platform wide, and not our problem specifically).
3. I can't really easily support a prebuilt app all that easily. The B&W cam us supported in the default Snap camera.
Also, OTA will be broken until we figure out why signing server's aren't signing our payload zips right.
To work around this, you can update weekly by sideloading the nightly, rebooting to recovery (important), re-sideloading any mods you use (GApps, AddonSU, etc.).
fixed, can remove post now.
Uzephi said:
Anything that uses VoIP compression is broken. Most video calling or internet calling apps in general use it.
Click to expand...
Click to collapse
So I assume this would apply to hangouts and hangouts dialer?
npjohnson said:
Also, OTA will be broken until we figure out why signing server's aren't signing our payload zips right.
To work around this, you can update weekly by sideloading the nightly, rebooting to recovery (important), re-sideloading any mods you use (GApps, AddonSU, etc.).
Click to expand...
Click to collapse
Resolved.
Unable to install Lineage su addon (using TWRP 3.2.2-2)
_BEGIN_
Installing su addon...
set_metadata: Error on lstat of "/system/etc/init/superuser.rc": too many symlinks encountered
Updater process ended with ERROR: 7
_END_
Thoughts?
MattKilla said:
Unable to install Lineage su addon (using TWRP 3.2.2-2)
_BEGIN_
Installing su addon...
set_metadata: Error on lstat of "/system/etc/init/superuser.rc": too many symlinks encountered
Updater process ended with ERROR: 7
_END_
Thoughts?
Click to expand...
Click to collapse
I was literally plugging in to try this ROM until I read this. Have you tried Magisk yet?
Magisk Works
3's&7's said:
I was literally plugging in to try this ROM until I read this. Have you tried Magisk yet?
Click to expand...
Click to collapse
I have ran into this same issue when flashing build > lineage-15.1-20180721-nightly-nash-signed.zip
I can confirm that it happens with both TWRP 3.2.2-2 & TWRP 3.2.1-1
I flashed Magisk 16.4 and it works flawlessly no issues.
I am very happy with this ROM it works great for me. Thank You Devs! :good:
MattKilla said:
Unable to install Lineage su addon (using TWRP 3.2.2-2)
_BEGIN_
Installing su addon...
set_metadata: Error on lstat of "/system/etc/init/superuser.rc": too many symlinks encountered
Updater process ended with ERROR: 7
_END_
Thoughts?
Click to expand...
Click to collapse
was TWRP installed or did you just boot to it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Google Pixel 3a XL
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 18.1 thread for the Google Pixel 3a XL.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
bonito
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
None.
Find any? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
Kernel Source: https://github.com/LineageOS/android_kernel_google_msm-4.9
Going to try it now.
Thank you!
npjohnson said:
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
Click to expand...
Click to collapse
syntax error Are we talking about the Kernel being bundled?
ssurell said:
syntax error Are we talking about the Kernel being bundled?
Click to expand...
Click to collapse
What? No, firmware, like modem, bootloader, etc.
Question:
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
So are you saying if we root there is no support? As most of us coming from stock would at least need root temporarily to restore all our apps.
Can anyone confirm if root even works on this build. I woudnt see any reason not but would like to know cause of the above reason.
UPDATE: Decided to just go for it and everything is working great so far. Took a little work to get google apps working instead of the included aosp ones (phone calendar and contacts) and a bt more work to get it to pass safteynet but its all working 100% now. Also tested this build with both ex kernel and mvk and they both seem to work just fine as well. Will report back if anything changes as have only been running it.a few hours but so far no issues or complaints at all.
Great job LOS team
What is the official way to obtain root access? or is there one any more?
cliffordd said:
What is the official way to obtain root access? or is there one any more?
Click to expand...
Click to collapse
Based on the above statement i quoted sounds like root is not "officially" supported at all. That said to get root i followed the process by which you patch a boot image file with magisk manager. Making it pass safteynet net took additional steps.
If you need more details on either process just post back and i can be more detailed
adm1jtg said:
If you need more details on either process just post back and i can be more detailed
Click to expand...
Click to collapse
Yes please - maybe message me off thread, as this topic might not be appropriate on here.
I have Magisk app installed, due to using Titanium Backup to keep a backup of my app. The upgrade went great and everything is working fine under LOS 18.1. But I miss the ability to take backups and use certain features properly on the device (ie clipboard sharing and other features in KDE Connect, scheduling backups etc) There used to be a package provided by LOS to add or remove su - https://download.lineageos.org/extras but that seems to have stopped now. I was just wondering if there was an "official" way of doing it!
I actually held off upgrading due to the previous download being released on 1st April and not finding some previous April fools pranks to be very funny!!
cliffordd said:
Yes please - maybe message me off thread, as this topic might not be appropriate on here.
I have Magisk app installed, due to using Titanium Backup to keep a backup of my app. The upgrade went great and everything is working fine under LOS 18.1. But I miss the ability to take backups and use certain features properly on the device (ie clipboard sharing and other features in KDE Connect, scheduling backups etc) There used to be a package provided by LOS to add or remove su - https://download.lineageos.org/extras but that seems to have stopped now. I was just wondering if there was an "official" way of doing it!
I actually held off upgrading due to the previous download being released on 1st April and not finding some previous April fools pranks to be very funny!!
Click to expand...
Click to collapse
sent you a private
cliffordd said:
What is the official way to obtain root access? or is there one any more?
Click to expand...
Click to collapse
i flashed the version of Magisk (v21.4) via the LineageOS recovery using the adb sideload and just updated to v22 via the app. I haven't had any issues with root since installing.
First off, I want to say thank you for all the hard work on these builds.
I have came across one issue that isn't working for me, but might not be something everyone else uses a lot. My "squeeze" for Assistant isn't working, but I can change it to take a screenshot of any other option, except the Assistant. Am I doing something wrong or is there another settings need to activate for it to work?
Thanks!
Really want to try this, but can't "fastboot boot twrp.img" or "fastboot flash boot twrp.img" in Android 11 to backup my partitions. What's the point of Android OS if I can't backup my system? I can boot into Lineage OS Recovery, enable adb, figure out the partition names, dd the partitions from shell or pull with adb? But good grief, kinda ridiculous if you ask me.
Haven't been able to use twrp since Android 9 far as i know
lineage-18.1-20210401-nightly-bonito-signed.zip
Searching Settings aborts after a matter of seconds and while typing.
Derelict non-clearable notifications requiring reboot or force close.
Desk Clock stuck at "Loading".
The final LOS 17 seems more polished, but lingering notifications are still present requiring force close.
Nevermind, user error.
ssurell said:
lineage-18.1-20210401-nightly-bonito-signed.zip
Searching Settings aborts after a matter of seconds and while typing.
Derelict non-clearable notifications requiring reboot or force close.
Desk Clock stuck at "Loading".
The final LOS 17 seems more polished, but lingering notifications are still present requiring force close.
Click to expand...
Click to collapse
you're using opengapps - don't do that ;p
Use MindTheGapps, which doesn't break that feature.
npjohnson said:
you're using opengapps - don't do that ;p
Use MindTheGapps, which doesn't break that feature.
Click to expand...
Click to collapse
Actually, it's the first time I've used MindTheGapps. I used OpenGapps after falling back to 17.1 though since it is recommended on the LOS site. I kind of liked the Slim Gapps feel of MTG though, and might try it on 17.1
ssurell said:
Actually, it's the first time I've used MindTheGapps. I used OpenGapps after falling back to 17.1 though since it is recommended on the LOS site. I kind of liked the Slim Gapps feel of MTG though, and might try it on 17.1
Click to expand...
Click to collapse
weird - we don't have MTG builds for 17.1 though, sadly.
How do I disable encrypted device? Tried ElemntalX kernel and Disable_Dm-Verity_ForceEncrypt_quota.zip but phone is still encrypted under security settings after first boot.
When I see "Say Hello To Trust", I just want to punch it in the face. Somebody just needs to build an updated LOS 16 so we have TWRP and possible access to /data (formerly user space) and call it a day.
ssurell said:
How do I disable encrypted device? Tried ElemntalX kernel and Disable_Dm-Verity_ForceEncrypt_quota.zip but phone is still encrypted under security settings after first boot.
When I see "Say Hello To Trust", I just want to punch it in the face. Somebody just needs to build an updated LOS 16 so we have TWRP and possible access to /data (formerly user space) and call it a day.
Click to expand...
Click to collapse
Why do you want encryption disabled?
It's hardware backed, and FBE, so very little gain from running unencrypted...
"Trust" has nothing to do with encryption, it can be on, off, trust just reports it to the user.
Why do you want TWRP? Lineage Recovery does the job just fine. What do you mean "/data (formerly userspace)"? That statement doesn't make much sense.
Regardless of all the above, the disabel force encrypt zip, followed by `fastboot -w` to format userdata ought to do it - but be warned, if you set a PIN, Android (AOSP, not a lineage thing specifically) will re-encrypt you... hence there being no point.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of android, 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. If you would like to contribute to LineageOS, please visit our Wiki for more details.
Downloads:
pixel 3: https://download.lineageos.org/blueline
pixel 3 xl: https://download.lineageos.org/crosshatch
gapps zip: (use arm64) https://wiki.lineageos.org/gapps#downloads
Initial Install Instructions:
pixel 3: https://wiki.lineageos.org/devices/blueline/install
pixel 3 xl: https://wiki.lineageos.org/devices/crosshatch/install
Update Instructions:
pixel 3: https://wiki.lineageos.org/devices/blueline/update
pixel 3 xl: https://wiki.lineageos.org/devices/crosshatch/update
Upgrade Instructions: (from 18.1 to 19.1)
pixel 3: https://wiki.lineageos.org/devices/blueline/upgrade
pixel 3 xl: https://wiki.lineageos.org/devices/crosshatch/upgrade
Notes:
1. lineage roms come with adb root that you can enable in developer options, but if you want root for apps, you can grab the magisk apk, then adb sideload it in lineage recovery.
2. The newest vendor, radio, & bootloader img's are included in the official lineage rom zip, so no need to worry about updating those manually.
3. When you format data in lineage recovery, you might see an error like "cant send spi message". you can ignore it. The same thing happens with google's stock rom and recovery.
Changelog:
blueline
crosshatch
Bug reporting:
https://wiki.lineageos.org/how-to/bugreport
Known issues:
1. low microphone gain in phone calls. fixed
Source Code:
crosshatch device tree: https://github.com/LineageOS/android_device_google_crosshatch/tree/lineage-19.1
blueline device tree: https://github.com/LineageOS/android_device_google_blueline/tree/lineage-19.1
kernel tree: https://github.com/LineageOS/android_kernel_google_msm-4.9/tree/lineage-19.1
vendor tree: https://github.com/TheMuppets/proprietary_vendor_google/tree/lineage-19.1
Credits:
Many thanks to my fellow LineageOS team members and all the contributors out there in the community.
Android version: 12.1 (12L)
Kernel version: 4.9.337
Status: nightly
Reserved for first comment!
Glad to see this device refused to end of its life
reserved
I just wanted to express my sincere appreciation for the hard work of everyone involved to maker this happen. Hopefully it'll be feature complete and official soon!
Thanks for the ROM, flashed on my blueline. Worked like charm, unfortunately had to come back to stock due to some office apps. It had nothing to do with ROM just some ease of restoring the backup.
Kudos and thanks again. Please keep on.
What is working and not working with this?
Thank you @razorloves.
If running LOS18.1 with opengapps pico, I'd need to do a clean install? Asking since 19.0 only works with MindtheGapps for now. And not sure you can update from a running system with opengapps to one with mindthegapps.
BootloopedMillennials said:
If running LOS18.1 with opengapps pico, I'd need to do a clean install?
Click to expand...
Click to collapse
I dont think so. Will probably work fine going from opengapps to mtg. If it doesn't work you can grab a logcat and send to me and I can tell you how to fix.
razorloves said:
I dont think so. Will probably work fine going from opengapps to mtg. If it doesn't work you can grab a logcat and send to me and I can tell you how to fix.
Click to expand...
Click to collapse
The upgrade went smoothly. Thanks.
Small issue I noticed.
1. Android System Intelligence keeps stopping. It mainly occurs in Settings. Once when Google Voice requested a new permission I guess related to it. But does so randomly as well.
Hard to replicate it. Try going into Accessibility>Live Captions>Allow Permission and just back out of it without doing anything.
I don't know if this is a LOS 19 issue or Android System Intelligence issue. When official Android 12 itself was in beta, there were reports of this app crashing.
'Android System Intelligence' keeps crashing for some on Android 12 Beta
Besides a handful of issues, Android 12 Beta 4 is quite stable for day-to-day usage. Now, an Android 12 System Intelligence crashing bug...
9to5google.com
Edit: FYI maybe related. When clicking allow permission in that example. It takes you to the settings screen to "allow to display over apps" permission screen and Live Captions isn't in there.
Also there is this small glitch in the Trebuchet app drawer. It's triggered by entering an app (any) and going back into the app drawer. It happens randomly. Related to Trebuchet features not being fully implemented yet?
Normal:
Glitch:
Working pretty nice, the only bug I've hit so far is the home settings. Icons are only movable when set to locked. I.e. the toggle is inverted.
Thanks for the hard work
jaythespacehound said:
Working pretty nice, the only bug I've hit so far is the home settings. Icons are only movable when set to locked. I.e. the toggle is inverted.
Thanks for the hard work
Click to expand...
Click to collapse
yep, thats the only bug i've seen too. thanks.
and there's already a fix, here.
i'll include it in my next build in a day or 2, that will have january security patches and source code released by google a few days ago.
Does dt2s in status bar work?
Shotg1 said:
Does dt2s in status bar work?
Click to expand...
Click to collapse
no, it's not there. that feature hadn't been ported yet when i released the first builds.
but the port is in progress now, https://review.lineageos.org/q/topic:twelve-dt2s
so i'll add it to the next build.
New builds in first post with January updates from google.
Android Security Bulletin—January 2022 | Android Open Source Project
source.android.com
Pixel Update Bulletin—January 2022 | Android Open Source Project
source.android.com
Also lots of changes and features added, including items I mentioned in previous posts.
Hello, been trying different rom to find right one stable battery life because jesus pixel 3 xl battery life sucks especially when use LTE. So far I'm amazed how stable this rom is I have been heavy using it and abusing it lol im using
Kirisakura_S 4.0.0 kernel and try pass safetynet current methods it won't pass i gave up lol. Good job on this rom, battery life im still testing it...
Thank you making LOS19!
contevo said:
Hello, been trying different rom to find right one stable battery life because jesus pixel 3 xl battery life sucks especially when use LTE. So far I'm amazed how stable this rom is I have been heavy using it and abusing it lol im using
Kirisakura_S 4.0.0 kernel and try pass safetynet current methods it won't pass i gave up lol. Good job on this rom, battery life im still testing it...
Thank you making LOS19!
Click to expand...
Click to collapse
Try this
Go to the OP: Initial Install instructions
Settings => Apps => See all => look for Magisk. If you find it, uninstall it.
When you get to step 7 Do not install the kernel. Just sideload Gapps and magisk canary 23016, and reboot.
Open Magisk and install SafetyNet Fix 2.2.1.
Homeboy76 said:
Try this/B]
If Magisk app is install, remove it
Settings => Apps => See all => look for Magisk. If you find it, uninstall it.
Download and install Magisk Canary
Note: Tap 3 dot menu across from canary => Download, app-debug.apk
Rename app-debug.apk magisk_canary-23016.zip
Put magisk_canary-23016.zip in the SDK Platform-tools folder on your computer: The folder with fastboot.exe in it.
Note: Make sure you have the latest version of SDK Platform-tools r 31.0.3 installed on your computer.
Open a Command prompt on your computer in the SDK Platform-tools folder: The folder with fastboot.exe in it.
On your phone, Boot bootloader (fastboot mode)
Press the Navigation button (Up or Down) until you see Recovery mode
Press the power buttom
When the lineage 19 recovery boots
Tap Apply update => Apply from ADB
On your computer Side load magisk_canary-23016.zip
adb sideload magisk_canary-23016.zip
When magisk finishes installing tap the back arrow on your phone, tap reboot system.
Check if Magisk was installed.
Click to expand...
Click to collapse
Hello, Thank You for your reply.
I followed this step on how to root androind 12 guide under guide section.
Download File(s)
Universal SafetyNet Fix · v2.1.3 (Riru) v2.2.1 (Zygisk)
Why Zygisk?
Install SafetyNet Fix 2.2.1
Open Magisk
Tap Modules icon
Tap Install from storage
Navigate to the SafetyNetFix file you downloaded
Tap the SafetyNetFix file
Tap the check mark (✓ at the bottom) to start the installation.
After it installs tap the Save icon to save the log
Tap Reboot.
Settings for Magisk Canary
Open Magisk App
Tap the Setup icon.
Scroll down to App and set the Update Channel to Canary.
Scroll down to Check Updates and enable it.
Scroll down to Magisk and enable Zygisk and Enforce DenyList.
Tap Configure DenyList => Tap 3 Dot Menu => Check ✓ Show system apps => Check ✓ Google Play Store, Google Pay, etc.
Scroll down to Superuser and enable Enable Biometric Authentication.
Get Device Certified Clear Google Play Services, Google Play Store, Google Pay, etc. data
Turn Airplane mode on
Open Settings
Tap Apps & notifications
Tap see all...
Tap three dot menu
Tap Show system
Scroll down to Google Play Store
Tap Storage and Cache
Tap Clear storage
Note: Repeat the 3 steps above for Google Play Services, Google Pay, etc.
reboot
Turn Airplane mode off
Check Device Certification
Open Google Play Store app
Tap Menu - Circle top right
Tap Settings
Tap About
Check Play protect certification.
this didn't work either.
contevo said:
Hello, Thank You for your reply.
I followed this step on how to root androind 12 guide under guide section...
Click to expand...
Click to collapse
To install magisk after installing a lineageOS Custom ROM, you adb sideload magisk. Then open the Magisk app and Direct install Magisk.
After magisk is, fully, installed then you can used the steps above to pass SafetyNet:
- Install Universal SafetyNet Fix · v2.2.1 (Zygisk)
- Get Device Certified Clear Google Play Services, Google Play Store, Google Pay, etc. data...
- Check Play protect certification...
Hi All,
This is a revival of the original MagiskHide Props Config module.
I've been working on this all day and its finally ready to start taking fingerprint submissions so i thought id open a new thread here to reach more people.
Disclaimers -
I have copied and pasted from the original thread with a few changes where relevant.
I fully intend on handing this back over to @Didgeridoohan if they ever decide to take the reign again. Im simply just stepping in to fill a much needed void in the custom rom space.
As with any Magisk Module. This comes with risk. You can very easily break your device. I myself have a Samsung Note 10 Plus so i will be testing on my own device prior to making any releases.
I have no intention of collecting donations at all. This project depends upon the community more then myself.
What's this?
If you are wondering anything about what this module can do and how it works or if you're experiencing issues of some kind, take a look at the documentation on GitHub and see if whatever you wonder about is covered there (most things are). If they're not, look again and then post in the thread.
If you're wondering about the latest and greatest after an update, take a look at the changelog and accompanying release notes.
Prerequisites
Magisk v20.4+.
Installation
Install through the Magisk Manager Downloads section. Or, download the zip (attached below) and install through the Magisk Manager -> Modules, or from recovery. Combine a recovery installation with the use of the module configuration file and you can set up a certified fingerprint and any custom props you want without first booting on a clean flash. Instant settings.
Usage
After installing and rebooting, run the command props in terminal (you can find a terminal emulator on F-Droid or in the Play Store), and then follow the instructions to set your desired options (also see the documentation on GitHub). You might have to call su before running the command.
You can also run the command with options. Use -h for details.
Submitting Fingerprints
Now this is where you lovely people come in. There is no way ill be able to spend all my time gathering fingerprints and i have absolutely no intention of doing so. However i've made it very easy to submit your fingerprints in a way that i can process them with very little effort.
How to find your fingerprint
Submit your Fingerprint
Source
GitLab - All scripts are completely opensource and your free to download it yourself directly from source
Download Repository
MHPC Releases & Archive
Support
Discord Invite Link - For the time being i will only be able to support users either on here and Discord.
Credits and mentions
There are lots of people to thank for this project. I've included the main two below
@topjohnwu, for Magisk
@Didgeridoohan, for creating MHPC and maintaining it for so long
Original Module Thread
Link to Original Thread
@vithuselservices You forgot to attach the module in your post.
devnoname120 said:
@vithuselservices You forgot to attach the module in your post.
Click to expand...
Click to collapse
Hi. There haven't been any official releases just yet. ETA for the first beta releases are the end of this week but that's only if everything goes well and I see no issues on my tests. So far there are only Experimental releases that i have stopped uploading to the release fileshare.
Once the new build is ready I can begin working on integrating new Fingerprints from the submissions that have been given to me.
@vithuselservices I tried the latest master, and I rebooted. If I type `props` in Termux it says `No command props found`. I have the same issue with the original module though.
Any ideas how to fix this issue?
Edit: typing `su` before solves the issue..
devnoname120 said:
@vithuselservices I tried the latest master, and I rebooted. If I type `props` in Termux it says `No command props found`. I have the same issue with the original module though.
Any ideas how to fix this issue?
Click to expand...
Click to collapse
type su first
I have a really weird question:
I have a poco f3 (europe) phone. I extracted the props from the phones original system (MIUI 13.0.8.0 EEA). I editet the original printlist in the original magisk module, added the
POCO/alioth_eea/alioth:12/SKQ1.211006.001/V13.0.8.0.SKHEUXM:user/release-keys__2022-08-01
line to it, Then flashed the modified zip, and applied the new prop settings. The YASNAC apps says it passes safetynet, and i can use all my banking app except google wallet, and there is no netflix in the ploay store. If I change the props to a value that was part of the original printlist
POCO/alioth_eea/alioth:11/RKQ1.200826.002/V12.5.3.0.RKHEUXM:user/release-keys__2021-06-01
the google wallet works and the netflix app shows itself in the play store.
Is it something that I missed from the prop values? I cannot understand this behavior.
Any advice?
Is this project still alive? I haven't seen any updates for a few weeks. Did OP just ghost us?
neelchauhan said:
Post has been removed by a Moderator
Click to expand...
Click to collapse
Hi.
This is not the case. Can you please remove this post as its highly inaccurate?
Im still here. Apologies for the lack of updates.
Ive had a lot of work come in so its delayed things somewhat but the final version is indeed ready.
Theres a final bit of testing to be conducted prior to making a official release as the last thing i want is bricked phones or settings being dropped.
The first beta release will be out by sunday.
In future can you please give more then 2 hours prior to making such a claim? Its considered rude to make such a claim without reaching out to a dev with sufficient time to reply. Your welcome to fork it yourself. Thats your right. But be more thoughtful when you spread messages like this
dickta said:
I have a really weird question:
I have a poco f3 (europe) phone. I extracted the props from the phones original system (MIUI 13.0.8.0 EEA). I editet the original printlist in the original magisk module, added the
POCO/alioth_eea/alioth:12/SKQ1.211006.001/V13.0.8.0.SKHEUXM:user/release-keys__2022-08-01
line to it, Then flashed the modified zip, and applied the new prop settings. The YASNAC apps says it passes safetynet, and i can use all my banking app except google wallet, and there is no netflix in the ploay store. If I change the props to a value that was part of the original printlist
POCO/alioth_eea/alioth:11/RKQ1.200826.002/V12.5.3.0.RKHEUXM:user/release-keys__2021-06-01
the google wallet works and the netflix app shows itself in the play store.
Is it something that I missed from the prop values? I cannot understand this behavior.
Any advice?
Click to expand...
Click to collapse
Hi.
I believe google is now blocking basic Attestation on newer firmware. This is something im looking into as part of my android 13 upgrade. Certain devices will work better then others. Im sorry i cannot give you a solid answer at the moment. But once im done with my current release and the fingerprints have been updated i can work on this issue. Its likely going to require device specific configurations as newer phones come out. Some people have had luck. but it seems android 12 is the turning point.
vithuselservices said:
Hi.
I believe google is now blocking basic Attestation on newer firmware. This is something im looking into as part of my android 13 upgrade. Certain devices will work better then others. Im sorry i cannot give you a solid answer at the moment. But once im done with my current release and the fingerprints have been updated i can work on this issue. Its likely going to require device specific configurations as newer phones come out. Some people have had luck. but it seems android 12 is the turning point.
Click to expand...
Click to collapse
I understand your point but I don't think its about luck. I did the same thing with my OnePlus 6. In the original prop module the the latest fingerprint is:
OnePlus/OnePlus6/OnePlus6:11/RKQ1.201217.002/2109171635:user/release-keys__2021-09-01
and with that all apps and wallet was working fine as intended, an netflix and revolut was present in the play store.
I also edited the original print.sh file and added the latest available fingerpint extracted from a latest full OTA rom which is this:
OnePlus/OnePlus6/OnePlus6:11/RKQ1.201217.002/2111252325:user/release-keys__2021-11-01
It also did the exact same behavior as on the Poco F3: YASNAC reports that the Basic Integrity and the CTS Profile match is "PASS", normal banking apps works (local banks like OTP, Erste etc. with NFC payment), but Google Wallet reports that the phone is modified and not certified. Play store also lacks netflix, put reports the device is certified.
The results are the same when I create a printlist file in the root directory in the phone to use my fingerptints as a "Custom" one.
It seems it only happens when I manually add the fingerprint myself, but never with the inbuilt fingerprints. That's why I think something is missing when I use "my" fingerprints. It also the same under android 11. Tested with a Redmi Note 5 Pro LineageOS.
I'm not a dev but if I can help, I'm sure I will.
dickta said:
I understand your point but I don't think its about luck. I did the same thing with my OnePlus 6. In the original prop module the the latest fingerprint is:
OnePlus/OnePlus6/OnePlus6:11/RKQ1.201217.002/2109171635:user/release-keys__2021-09-01
and with that all apps and wallet was working fine as intended, an netflix and revolut was present in the play store.
I also edited the original print.sh file and added the latest available fingerpint extracted from a latest full OTA rom which is this:
OnePlus/OnePlus6/OnePlus6:11/RKQ1.201217.002/2111252325:user/release-keys__2021-11-01
It also did the exact same behavior as on the Poco F3: YASNAC reports that the Basic Integrity and the CTS Profile match is "PASS", normal banking apps works (local banks like OTP, Erste etc. with NFC payment), but Google Wallet reports that the phone is modified and not certified. Play store also lacks netflix, put reports the device is certified.
The results are the same when I create a printlist file in the root directory in the phone to use my fingerptints as a "Custom" one.
It seems it only happens when I manually add the fingerprint myself, but never with the inbuilt fingerprints. That's why I think something is missing when I use "my" fingerprints. It also the same under android 11. Tested with a Redmi Note 5 Pro LineageOS.
I'm not a dev but if I can help, I'm sure I will.
Click to expand...
Click to collapse
How odd.
Ill raise that as a issue on my Git and have a look at it. It likely wont be this week but ill aim to do some testing on it next week. Are you certain the build date is correct?
vithuselservices said:
How odd.
Ill raise that as a issue on my Git and have a look at it. It likely wont be this week but ill aim to do some testing on it next week. Are you certain the build date is correct?
Click to expand...
Click to collapse
Absolutely! I own all the 3 phones , I also did a full stock rom recovery on all to run the getprop command to make sure the fingerprint and the patch date is correct.
Ohh and almost forgot: thank you!
Beta release is now available!
You can download it via the download repo in the first post. Please let me know if you come across issues. For this first release I do not recommend upgrading daily driver devices just yet as there could still be issues.
Not much has been changed in this release. I'm working on improving the verification process during the install process. I know a lot of people are keen to get fingerprints updated so ill be focusing on that over the next few weeks.
vithuselservices said:
Beta release is now available!
You can download it via the download repo in the first post. Please let me know if you come across issues. For this first release I do not recommend upgrading daily driver devices just yet as there could still be issues.
Not much has been changed in this release. I'm working on improving the verification process during the install process. I know a lot of people are keen to get fingerprints updated so ill be focusing on that over the next few weeks.
Click to expand...
Click to collapse
I tried it right now: the installation has a little problem: it says the installation is failed but it installs it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After that it seems the module can't access for some files and it not really working after that.
I attached a log to help.
dickta said:
I tried it right now: the installation has a little problem: it says the installation is failed but it installs it.
View attachment 5759567
After that it seems the module can't access for some files and it not really working after that.
View attachment 5759575
View attachment 5759571
I attached a log to help.
Click to expand...
Click to collapse
How odd. It works for me. Ill have a run through the logs and get it sorted. Thank you for reporting back!
vithuselservices said:
How odd. It works for me. Ill have a run through the logs and get it sorted. Thank you for reporting back!
Click to expand...
Click to collapse
Same for me. After assigning a fingerprint, reboot will clear it and it reverts back to original
This is still being looked into.
Its coming to the end of the year so im having to process a lot of projects to completion in my day job. Sorry for the delay!
New Beta Build is up. This should fix the install issues users have been having.
Ill be uploading a load of fingerprints very soon. Just finishing off testing the ones i have to hand.
For the moment. Android 13 support is very hit or miss. I'm working to find a solution to this.
A future update will need the deletion of the existing module so it can properly overwrite the new install files. This will also be completed with the next update.
The module now installs without problem, but in the app itself the behavior is the same: it not applies the selected fingerprint, always shows that "not accessible file" error in all activity. It's a good start, keep up the good work
dickta said:
The module now installs without problem, but in the app itself the behavior is the same: it not applies the selected fingerprint, always shows that "not accessible file" error in all activity. It's a good start, keep up the good work
Click to expand...
Click to collapse
Can you try uninstalling the original module and do a clean install of this one?
Im afraid i am not able to recreate the issue at all on my device which is quite infuriating
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 13, which is designed to increase performance and reliability over stock Android for your device.
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. Linked below is a package that has come from another Android project that restore the Google parts. 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 out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions :
https://wiki.lineageos.org/devices/instantnoodlep
Downloads :
https://download.lineageos.org/instantnoodlep
GPL compliance :
https://github.com/LineageOS/android_kernel_oneplus_sm8250
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Thank for the new release!
Just flashed it. No issues so far.
I have just noticed that the "unlocked bootloader" message returned after flashing latest oos13 firmware. So, every time i restart my device i get the following "your device has been unlocked and can't be trusted". Just wanted to make sure that this is normal (since it was gone in oos12 firmware) and to alert other people about it.
For people who will root and need to pass safetynet the good old methods work however i was unable to find an android13 fingerprint using propsconfig. Instead i used a fingerprint for android 12 and i was able to pass all safetynet checks.
desosav said:
I have just noticed that the "unlocked bootloader" message returned after flashing latest oos13 firmware. So, every time i restart my device i get the following "your device has been unlocked and can't be trusted". Just wanted to make sure that this is normal (since it was gone in oos12 firmware) and to alert other people about it.
Click to expand...
Click to collapse
It's normal:
[Unlocked Bootloader][OOS13/OOS 13 based ROMs] How to remove bootloader unlocked message for OnePlus 8 Pro
This is a guide to remove the ugly "Your device has been unlocked and can't be trusted" or "The bootloader is unlocked and software integrity cannot be guaranteed" for OP8 Pro. This message was removed on OOS 12 which was one great thing by OP...
forum.xda-developers.com
desosav said:
For people who will root and need to pass safetynet the good old methods work however i was unable to find an android13 fingerprint using propsconfig. Instead i used a fingerprint for android 12 and i was able to pass all safetynet checks.
Click to expand...
Click to collapse
I want to ask about this
I've been using magisk, and have been unable to pass safety check on the stock ROM and thought Magisk stopped trying to beat safety net, so I stopped trying also.
It seems you have resolved this.
Can I ask you for direction on how to do this myself after I move to lineageos?
I don't necessarily need full instructions and would appreciate any guidance you can offer me.
Thanks
JustinChase said:
I want to ask about this
I've been using magisk, and have been unable to pass safety check on the stock ROM and thought Magisk stopped trying to beat safety net, so I stopped trying also.
It seems you have resolved this.
Can I ask you for direction on how to do this myself after I move to lineageos?
I don't necessarily need full instructions and would appreciate any guidance you can offer me.
Thanks
Click to expand...
Click to collapse
I haven't tried on 20 yet, but:
root with magisk then add the following modules:
propsconfig and change the fingerprint to a pixel 6 pro
kdragons safetynet patch
Make sure play store and other services are on the magisk deny list.
There are more detailed instructions in various threads specific to each step, but this is the gist of it.
No issues with following the lineage os version upgrade procedure to keep from needing to format data? The upgrade procedure didn't have about needing oos13 firmware beforehand, so I wasn't sure if it'd make a difference.
-update-
No issues yet after following the upgrade procedure without flashing oos13 stock fw first.
I still have some weird issue where it makes me have to sign in to the T-Mobile network. I think it's because I had a Verizon sim in sim slot 2 at one point.. it'll probably require a network settings reset to fix..
Is the 48MP sensor on the camera still locked? Just wondering considering the changes with the camera app and API with LOS 20.
d3viou5 said:
I haven't tried on 20 yet, but:
root with magisk then add the following modules:
propsconfig and change the fingerprint to a pixel 6 pro
kdragons safetynet patch
Make sure play store and other services are on the magisk deny list.
There are more detailed instructions in various threads specific to each step, but this is the gist of it.
Click to expand...
Click to collapse
hi, @d3viou5 how did you root?
I've updated from LOS19 to LOS20, following the official procedure.
Now. I've
- Installed Magisk (tried both canary and stable)
- extracted the boot.img with Payloader-Dumper-Go
- patched boot.img with Magisk
- flashed patched boot.img, system is NOT rooted
- tried to boot (not flash) the patched boot.img, again system NOT rooted
I'm missing something?
thx!
Installed manually coming from LOS 19.1. Did not update firmware, but did the DTBO and VBMETA flashing to be on the safe side. No issues and running very smooth so far. New camera app gets good pics with good lighting. Low light is 2014 quality.
miramax001 said:
hi, @d3viou5 how did you root?
I've updated from LOS19 to LOS20, following the official procedure.
Now. I've
- Installed Magisk (tried both canary and stable)
- extracted the boot.img with Payloader-Dumper-Go
- patched boot.img with Magisk
- flashed patched boot.img, system is NOT rooted
- tried to boot (not flash) the patched boot.img, again system NOT rooted
I'm missing something?
thx!
Click to expand...
Click to collapse
If you go into recovery, sideload magisk apk. That's what I did with 25.2 and it's rooted.
mattgyver said:
If you go into recovery, sideload magisk apk. That's what I did with 25.2 and it's rooted.
Click to expand...
Click to collapse
Thanks @mattgyver
The problem WAS the WORK profile (with SHELTER).
I had to remove my WORK PROFILE (from SETTINGS->ACCOUNT)
And then, sideload magisk.apk (renamed as magisk.zip) and now I'm rooted again.
ThX!
roaringcrown said:
Installed manually coming from LOS 19.1. Did not update firmware, but did the DTBO and VBMETA flashing to be on the safe side. No issues and running very smooth so far. New camera app gets good pics with good lighting. Low light is 2014 quality.
Click to expand...
Click to collapse
Hi, I'm guessing you "dirty flashed" LOS 20 over 19.1 through the LOS recovery?
I was hoping to avoid factory resetting/formatting...
Thanks!
Kuronosu said:
Hi, I'm guessing you "dirty flashed" LOS 20 over 19.1 through the LOS recovery?
I was hoping to avoid factory resetting/formatting...
Thanks!
Click to expand...
Click to collapse
yes, just follow the official guide
Upgrade LineageOS on instantnoodlep | LineageOS Wiki
wiki.lineageos.org
How to install the rom with twrp? i.m using oneplus 8 pro global varient ty
@LuK1337
Thanks for the great work!
I'm currently trying to build LOS 20 myself and as far as I can tell everything compiled properly.
However in the last steps of the build I receive the following error:
Bash:
The following HALs in device manifest are not declared in FCM <= level 4:
[email protected]::IEffectsFactory/default
[email protected]::IDevicesFactory/default
[email protected]::IBootControl/default
[email protected]::IMediaCasService/default
[email protected]::ICryptoFactory/wfdhdcp
[email protected]::ICryptoFactory/widevine
[email protected]::IDrmFactory/wfdhdcp
[email protected]::IDrmFactory/widevine
[email protected]::ICryptoFactory/clearkey
[email protected]::IDrmFactory/clearkey
[email protected]::IHealth/default
[email protected]::IDevice/qti-default
[email protected]::IDevice/qti-dsp
andro[email protected]::IDevice/qti-gpu
[email protected]::IDevice/qti-hta
android.hardware.power.IPower/default (@1)
[email protected]::IRadio/slot1
[email protected]::IRadio/slot2
[email protected]::ISecureElement/SIM1
[email protected]::ISecureElement/SIM2
[email protected]::ISecureElement/eSE1
[email protected]::ISoundTriggerHw/default
[email protected]::IUsb/default
android.hardware.vibrator.IVibrator/default (@1)
android.hardware.wifi.hostapd.IHostapd/default (@1)
android.hardware.wifi.supplicant.ISupplicant/default (@1)
[email protected]::IWifi/default
INCOMPATIBLE
stderr:ERROR: files are incompatible: Runtime info and framework compatibility matrix are incompatible: No compatible kernel requirement found (kernel FCM version = 5).
For kernel requirements at matrix level 5, For config CONFIG_DEBUG_FS, value = y but required n
For kernel requirements at matrix level 6, For config CONFIG_ANDROID_PARANOID_NETWORK, value = y but required n
: Success
Any idea why this is happening?
sToRm1nG said:
@LuK1337
Thanks for the great work!
I'm currently trying to build LOS 20 myself and as far as I can tell everything compiled properly.
However in the last steps of the build I receive the following error:
{code}
The following HALs in device manifest are not declared in FCM <= level 4:
[email protected]::IEffectsFactory/default
[email protected]::IDevicesFactory/default
[email protected]::IBootControl/default
[email protected]::IMediaCasService/default
[email protected]::ICryptoFactory/wfdhdcp
[email protected]::ICryptoFactory/widevine
[email protected]::IDrmFactory/wfdhdcp
[email protected]::IDrmFactory/widevine
[email protected]::ICryptoFactory/clearkey
[email protected]::IDrmFactory/clearkey
[email protected]::IHealth/default
[email protected]::IDevice/qti-default
[email protected]::IDevice/qti-dsp
[email protected]::IDevice/qti-gpu
[email protected]::IDevice/qti-hta
android.hardware.power.IPower/default (@1)
[email protected]::IRadio/slot1
[email protected]::IRadio/slot2
[email protected]::ISecureElement/SIM1
[email protected]::ISecureElement/SIM2
[email protected]::ISecureElement/eSE1
[email protected]::ISoundTriggerHw/default
[email protected]::IUsb/default
android.hardware.vibrator.IVibrator/default (@1)
android.hardware.wifi.hostapd.IHostapd/default (@1)
android.hardware.wifi.supplicant.ISupplicant/default (@1)
[email protected]::IWifi/default
INCOMPATIBLE
stderr:ERROR: files are incompatible: Runtime info and framework compatibility matrix are incompatible: No compatible kernel requirement found (kernel FCM version = 5).
For kernel requirements at matrix level 5, For config CONFIG_DEBUG_FS, value = y but required n
For kernel requirements at matrix level 6, For config CONFIG_ANDROID_PARANOID_NETWORK, value = y but required n
: Success
{code}
Any idea why this is happening?
Click to expand...
Click to collapse
You seem to be doing something wrong, e.g. building -user instead of -userdebug or something else.
LuK1337 said:
You seem to be doing something wrong, e.g. building -user instead of -userdebug or something else.
Click to expand...
Click to collapse
Yeah, you're right... I was building user isntead of userdebug.
Thank you so so much for this! ♥ It works like a charm and it's so so much better than OxygenOS 13 (I can minimize notifications omg!!!1!).
The only thing I personally am missing, is the classic LOS 18 style quick shortcuts in the pull-down notification menu. I always used 1 row with 6 circles, but since LOS 19 it changed to 2 rows with only 4 large shortcuts. But oh well, I guess you can't have everything!
Thank you for maintaining this device @LuK1337 !
@LuK1337
Thank you for your great work.
Not only for your work for this great Oneplus 8 Pro device, but also for other devices before!
You are really one of the most important and best device maintainers.
haxorinjector said:
How to install the rom with twrp? i.m using oneplus 8 pro global varient ty
Click to expand...
Click to collapse
TWRP is only available for A11 and lower. It does not work on A12 or A13.