{
"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 11, 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/enchilada
Downloads :
https://download.lineageos.org/enchilada
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:
It's cool
wondering anyone tried this?
[email protected] said:
wondering anyone tried this?
Click to expand...
Click to collapse
Just booted with NikGapps and canary Magisk - GPS seems to work neither here nor on POSP, which I migrated from. Otherwise seems okay!
Edit: the fingerprint auth doesn't work too and the camera crashes upon detecting a face - prolly should've done a factory reset when migrating lmao. Will report in a while how that went
Edit 2: after a factory reset I managed to get GPS working, however fingerprint auth and face detection still fail
dikivan2000 said:
Just booted with NikGapps and canary Magisk - GPS seems to work neither here nor on POSP, which I migrated from. Otherwise seems okay!
Edit: the fingerprint auth doesn't work too and the camera crashes upon detecting a face - prolly should've done a factory reset when migrating lmao. Will report in a while how that went
Edit 2: after a factory reset I managed to get GPS working, however fingerprint auth and face detection still fail
Click to expand...
Click to collapse
Just curious, did you flash with TWRP or use the Lineage recovery? If TWRP works it will make installing Magisk much simpler.
dikivan2000 said:
Just booted with NikGapps and canary Magisk - GPS seems to work neither here nor on POSP, which I migrated from. Otherwise seems okay!
Edit: the fingerprint auth doesn't work too and the camera crashes upon detecting a face - prolly should've done a factory reset when migrating lmao. Will report in a while how that went
Edit 2: after a factory reset I managed to get GPS working, however fingerprint auth and face detection still fail
Click to expand...
Click to collapse
Also, How's the experience with POSP. I'm currently on Pixen Android 11 which is good with issues majorly in Camera during Face Detection.. Battery Life ais great and ROM is very snappy. Liking it.
Clean flash, latest OOS, TWRP, LOS 18 in both slots, and Nikgapps and Magisk Modded. It boots, but NFC it´s no working. All the rest in my initial setup works ok. I didn´t try camera at moment.
With Magisk Canary it doesn´t boot, goes to fastboot mode.
At first it doesn´t pass Safetynet test. With Magisk Props module it´s ok. (Correction: Magisk props works with Manager Canary app over Magisk Modded, but root it´s lost)
Thanks dev for your work!
Dirty flashed, latest OOS, current TWRP, flashed Lineage 18 both slots. No magisk or other mods. Mobile data not working and when I try to open the network from settings it crashes back to the home screen. Wiping cache doesn't help.
Oh well, guess it's time to wipe and start with a fresh install I was hoping ...
Nut_House said:
Just curious, did you flash with TWRP or use the Lineage recovery? If TWRP works it will make installing Magisk much simpler.
Click to expand...
Click to collapse
Afaik LOS recovery does not allow flashing; I used TWRP
dikivan2000 said:
Afaik LOS recovery does not allow flashing; I used TWRP
Click to expand...
Click to collapse
Thanks. Makes sense, I never used LOS recovery, always just booted to TWRP when I needed to update or flash something.
Got impatient, went ahead and made the leap earlier and tried a dirty flash. It didn't go well. Just finished doing a wipe and clean install and so far so good. Will start reinstalling apps and see how things play out.
@LuK1337 Thanks for bringing LineageOS 18 for OP6.
I have found a few bugs,please have a look at them
1) Front camera FC when face is brought closer to the camera.
2) unable to make call when Volte is enabled.
3) NFC does not work(quick toggle is greyed out).
Update: 2nd build fixed camera and volte
Hi @LuK1337,
thanks a lot for taking care of our devices,
to install, which base must be on ? Latest OOS, or beta preview for P ?
And about gapps, do we have to use gapps for 11 or can we use opengapps 10 ? (did not see beta 11 for opengapps)
Cygnust said:
Hi @LuK1337,
thanks a lot for taking care of our devices,
to install, which base must be on ? Latest OOS, or beta preview for P ?
And about gapps, do we have to use gapps for 11 or can we use opengapps 10 ? (did not see beta 11 for opengapps)
Click to expand...
Click to collapse
>to install, which base must be on ? Latest OOS, or beta preview for P ?
No idea what firmware I'm even on but i'm definitely not on Android 9 one...
>And about gapps, do we have to use gapps for 11 or can we use opengapps 10 ? (did not see beta 11 for opengapps)
It depends whether you actually want your phone to work or not.
Thanks to Luk for delivering high quality ROMs - the second build indeed fixes the camera. However, does not boot with Magisk (21000) anymore
qualo said:
Clean flash, latest OOS, TWRP, LOS 18 in both slots, and Nikgapps and Magisk Modded. It boots, but NFC it´s no working. All the rest in my initial setup works ok. I didn´t try camera at moment.
With Magisk Canary it doesn´t boot, goes to fastboot mode.
At first it doesn´t pass Safetynet test. With Magisk Props module it´s ok. (Correction: Magisk props works with Manager Canary app over Magisk Modded, but root it´s lost)
Thanks dev for your work!
Click to expand...
Click to collapse
Hi,
which magisk version are you using ? mine goes on fastboot too
Cygnust said:
Hi,
which magisk version are you using ? mine goes on fastboot too
Click to expand...
Click to collapse
The one shared in post #42 in POSP 11 beta ROM.
(Sorry, I didn't find how to share the direct link to post)
With this Magisk_debug2.zip it boots and you can pass safetynet with MagiskProps without updating manager
I'm running the 10/09 build of LOS with magisk v21.0 (21000) and it boots with no issues. In fact, after a few days of usage I'm impressed with just how well everything works for such an early release. Twice it appeared to unlock with my pattern and then dumped me back to the login screen and the connection to my Garmin watch has dropped a couple of times, which never happened with LOS 17.1. Otherwise, it's been smooth sailing.
LuK1337, well done :good:
installed fine with magisk canary and manually patched boot.img from payload to flash in twrp.
just high cpu usage with zygote 64 and system_server other than that nice job LuK1337
Stoowyguy said:
installed fine with magisk canary and manually patched boot.img from payload to flash in twrp.
just high cpu usage with zygote 64 and system_server other than that nice job LuK1337
Click to expand...
Click to collapse
I noticed the CPU usage bug too. Hopefully Luk1337 can sort it out.
Sent from my ONEPLUS A6003 using Tapatalk
Just want to say thank you for LuK1377, the ROM is REALLY GREAT ! The smoothness and new features of Android 11 makes me wanna stick to it, even though it's still in early development.
I'm running the latest build from today and just want to give my feedback about one point: even though the screen is set to time out in 30 seconds (in my case), it turns off and a second later, it turns on again without anyone touching the phone.
If I block my phone using the power button, it works correctly. If I wait the 30 seconds, it stays awake (phone not charging, stay awake option on dev options is off).
The battery life was also not great (when I was using the build from october 11th, still testing this one) but it's expected and I'm not concerned about it.
Thank you again LuK1337!
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"
}
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.
What's not working :
cool issues list
Instructions :
Download the latest build and gapps
Reboot to recovery
Flash the latest build and gapps
Reboot
Downloads :
Builds : https://download.lineageos.org/charlotte
Root addon : https://download.lineageos.org/extras
Google Apps : https://wiki.lineageos.org/gapps.html
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:
XDA:DevDB Information
[ROM][OFFICIAL][charlotte][9] LineageOS 16.0, ROM for the Huawei P20 Pro
Contributors
LuK1337
Source Code: https://github.com/LineageOS
ROM OS Version: Windows 8 Mobile
Version Information
Status: Testing
Created 2018-12-12
Last Updated 2019-03-01
NOTE: These builds require EMUI 9 firmware, they will not boot on EMUI 8 devices.
I wrote in the previous thread about NFC not working, Luk has fixed it now, woo!
The Huawei camera app still can't save pictures though (It just creates a 0 byte file) - saving videos work fine however.
Thank You Luk. I am very glad you still work on p20 pro!
whitekidney said:
I wrote in the previous thread about NFC not working, Luk has fixed it now, woo!
The Huawei camera app still can't save pictures though (It just creates a 0 byte file) - saving videos work fine however.
Click to expand...
Click to collapse
If i may, which recovery have you used? Have you updated to emui 9 right before flashing it?
forever_lol said:
Thank You Luk. I am very glad you still work on p20 pro!
If i may, which recovery have you used? Have you updated to emui 9 right before flashing it?
Click to expand...
Click to collapse
Yep, use the newest EMUI 9 base, then flash TWRP. Sideload the LOS 16 ZIP and opengapps, then flash stock recovery and wipe data from there.
Wiping data in TWRP doesn't work with TWRP on L29 devices for some reason.
whitekidney said:
Yep, use the newest EMUI 9 base, then flash TWRP. Sideload the LOS 16 ZIP and opengapps, then flash stock recovery and wipe data from there.
Wiping data in TWRP doesn't work with TWRP on L29 devices for some reason.
Click to expand...
Click to collapse
Thank you sir! You mean unofficial twrp by pretorian?
forever_lol said:
Thank you sir! You mean unofficial twrp by pretorian?
Click to expand...
Click to collapse
No, the official one. The unofficial one is even more broken.
@LuK1337
fully camera API2 in this rom?
starbase64 said:
@LuK1337
fully camera API2 in this rom?
Click to expand...
Click to collapse
If stock didn't support full camera api 2 then this won't do it either.
whitekidney said:
I wrote in the previous thread about NFC not working, Luk has fixed it now, woo!
The Huawei camera app still can't save pictures though (It just creates a 0 byte file) - saving videos work fine however.
Click to expand...
Click to collapse
Wait, NFC is fixed in this build ???
LJAM96 said:
Wait, NFC is fixed in this build ???
Click to expand...
Click to collapse
Yeah.
I wiped my phone 3 times and re-flashed like 20 times to help luk troubleshoot
Doings gods work. :good: Working camera port and its daily driver worthy. Keep up the good work Luk.
LuK1337 said:
NOTE: These builds require EMUI 9 firmware, they will not boot on EMUI 8 devices.
Click to expand...
Click to collapse
Is there any path / steps to get to LOS 16 from an EMUI 8 device ( CLT-L04 ). I can get to PixelExperience 9 that breaks TWRP.
Thx Luk.
ePearl said:
Is there any path / steps to get to LOS 16 from an EMUI 8 device ( CLT-L04 ). I can get to PixelExperience 9 that breaks TWRP.
Thx Luk.
Click to expand...
Click to collapse
1. Somehow flash EMUI 9
2. Flash twrp
3. Flash lineage, gapps, ...
4. Wipe data (it's best if you do that in stock recovery)
5. Profit?
LJAM96 said:
Doings gods work. :good: Working camera port and its daily driver worthy. Keep up the good work Luk.
Click to expand...
Click to collapse
The huawei camera is included in /system/product/ (along with a bunch of other huawei apps: HwAOD HwCamera2 HwDolby HwFidoAsm HwFidoClient HwPCExplorer HwPCSystemUI HwSmartShot )
However they are not currently present in this build as Luk dismounts that partition.
The app itself works without any issues except it can't save image files (it just creates a 0 byte file for some reason)
Here's the logcat from when I take a picture and save it, hopefully someone will be able to make more sense out of than I have https://hastebin.com/yeheqegori.coffeescript
I can't see why it fails to save the image. Probably an easy fix.
ePearl said:
Is there any path / steps to get to LOS 16 from an EMUI 8 device ( CLT-L04 ). I can get to PixelExperience 9 that breaks TWRP.
Thx Luk.
Click to expand...
Click to collapse
You can try using Huawei Firmware Finder (it's an app) to try and force the OTA through on your device if you haven't received it yet.
Alternatively, you try using HuRupdater (is that how I spell it?) or the instructions found here https://forum.xda-developers.com/hu...uide-how-to-install-emui-9-android-9-t3839316 but for the newer EMUI 9 (163?) build.
Once you are on EMUI 9, you can follow LuKs instructions above, but remember to wipe data via the stock recovery (flash the stock recovery_ramdisk, not erecovery) after you have flashed LOS 16 and opengapps.
legend
Great to see this ROM here. I will install it later on. But first, I have a question: last time I installed EMUI 9 (beta) on my device (CLT-L29), I ended up being stuck with FRP locked, OEM unlock greyed out, no root possible, no TWRP possible. The only solution was to downgrade using FunkyHuawei. I am afraid that I will find myself in the same situation again.. Anyone here who can confirm upgrading to EMUI 9 and flashing TWRP is working on CLT-L29? Thanks.
ChangeToTower said:
Great to see this ROM here. I will install it later on. But first, I have a question: last time I installed EMUI 9 (beta) on my device (CLT-L29), I ended up being stuck with FRP locked, OEM unlock greyed out, no root possible, no TWRP possible. The only solution was to downgrade using FunkyHuawei. I am afraid that I will find myself in the same situation again.. Anyone here who can confirm upgrading to EMUI 9 and flashing TWRP is working on CLT-L29? Thanks.
Click to expand...
Click to collapse
Yes, it's working.
<- L29 on LOS16 with TWRP.
Thanks for the ROM!
which TWRP could I take?
I had done a wipe over TWRP since then the normal recovery doesn't work anymore... what can I try?
TWRP remains only with logo but ADB Works with TWRP
Heinzx3 said:
Thanks for the ROM!
which TWRP could I take?
I had done a wipe over TWRP since then the normal recovery doesn't work anymore... what can I try?
TWRP remains only with logo but ADB Works with TWRP
Click to expand...
Click to collapse
Official one.
{
"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.0 (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.
Important:
Official build are now available
What's working :
Boots
RIL (Calls, SMS, Data)
Wifi
Wifi Hotspot
Bluetooth
Video Playback
Audio ( Record and Playback )
Camera
Camcorder
Flash
GPS
Nfc
SELinux enforcing
Everything else
What's not working :
you tell me
Instructions :
Download the latest build and gapps
Reboot to recovery
Do all wipes
Flash the latest build and gapps
Downloads :
Latest Build : LineageOS for Moto X 2014
Google Apps
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.
Credits :
invisiblek & tortel: for working the victara - lineage maintainer
Motorola: For providing the Kernel Source Code
LineageOS Team
All member of Telegram Testers group
if you want to offer me a coffee or anything else check this
XDA:DevDB Information
Lineage 16 for victara, ROM for the Moto X 2014
Contributors
linckandrea
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.4.x
Version Information
Status: Beta
Device tree Source: Beta
Created 2019-04-20
Last Updated 2019-08-23
reserved
That's amazing! Thank you so much! I'm trying it out right now!
Edit. So here's what I did:
1. Entered Twrp 3.2.3.0, and wiped everything but USB OTG.
2. Downloaded latest build and GApps ARM 9.0 Stock, and pushed them to `/sdcard`.
3. Installed both ZIPs.
4. Reboot.
Everything seems to be working but Pixel Launcher didn't launch--got "Pixel Launcher keeps stopping". Managed to launch Trebuchet via App Info > Search > Defaults (since I had no launcher). Everything else works 100%, but still can't launch Pixel Launcher.
Thanks again!
Whaaaaaay the ringer and notification volumes are merged))
Thanks
same for me
hagg3n said:
That's amazing! Thank you so much! I'm trying it out right now!
Edit. So here's what I did:
1. Entered Twrp 3.2.3.0, and wiped everything but USB OTG.
2. Downloaded latest build and GApps ARM 9.0 Stock, and pushed them to `/sdcard`.
3. Installed both ZIPs.
4. Reboot.
Everything seemed to work but Pixel Launcher never opened--got the "Pixel Launcher keeps stopping". Managed to launch Trebuchet via App Info > Search > Defaults (since I had no launcher). Everything else is work 100%, but still can't launch Pixel Launcher.
Thanks again!
Click to expand...
Click to collapse
Chus81 said:
same for me
Click to expand...
Click to collapse
Actually I spoke too soon.
After my first reboot my Sim card was *not* detected and Photos behave the same as Pixel Launcher--"Program keeps stopping".
fix to bug inthe ROM
prediction for the correction of ROM in the error of the chip that when it is time to turn on the cell the same is not recognized and it is necessary to restart the same? :laugh:
hagg3n said:
Actually I spoke too soon.
After my first reboot my Sim card was *not* detected and Photos behave the same as Pixel Launcher--"Program keeps stopping".
Click to expand...
Click to collapse
I installed the [ROM] [9.0.0] [UNOFFICIAL] LineageOS 16.0 and the sim didn't detect me, so I restarted in recovery, and from the nandroid backup I made of the official lineageOS 14.1, I only reinstalled the modem, now it detects phone sim, try and see if it works for you too
vab sas said:
I installed the [ROM] [9.0.0] [UNOFFICIAL] LineageOS 16.0 and the sim didn't detect me, so I restarted in recovery, and from the nandroid backup I made of the official lineageOS 14.1, I only reinstalled the modem, now it detects phone sim, try and see if it works for you too
Click to expand...
Click to collapse
Hey thanks for the tip! But I'll actually need more than that. I'm not familiar with Android development so how exactly would I pick only the "modem" (is that an app? a package?) out of an official Lineage build? You can simply point me towards a tutorial/article/website, that ought to be enough.
Same issues here.
EDIT: On some boots the SIM works and on some boots it doesn't. Google Photos works if you configure OpenGApps to not install it and install it from Google Play later. I also configured it to keep the stock gallery.
hagg3n said:
Actually I spoke too soon.
After my first reboot my Sim card was *not* detected and Photos behave the same as Pixel Launcher--"Program keeps stopping".
Click to expand...
Click to collapse
Thanks for the ROM ! Took a few reboots to get the SIM working. Also, can we not give root access to apps from developer options ? It only shows allow for ADB.
Can anyone post a modem that can be flashed to get the SIM functionality working properly with this ROM?
agentsmith988 said:
Can anyone post a modem that can be flashed to get the SIM functionality working properly with this ROM?
Click to expand...
Click to collapse
I flashed the modem from official lineage os 14.1. However, that did not solve the sim issue for me.
Hi, thank for the rom.
Is posible install Magisk in this rom?.
Regards.
juanantofb said:
Hi, thank for the rom.
Is posible install Magisk in this rom?.
Regards.
Click to expand...
Click to collapse
Magisk works for me.
Hi, thanks you, i will try now.
Regards.
Hi, Magisk 19.2 work correctly.
Thanks to all.
Regards.
Hi, thanks so much for doing this! I flashed the latest build you have posted and openGapps but for some reason I'm having extremely slow wifi performance. On a network that's capable of 250Mbps I was getting 7Mbps, and now on a mobile hotspot I'm seeing 90kbps. Is there some tuning setting for the wifi I'm missing by default?
hey guys
howi can do this ? "Selinux in enforcing mode " ? ty guys
---------- Post added at 01:07 AM ---------- Previous post was at 12:29 AM ----------
nick79325 said:
Hi, thanks so much for doing this! I flashed the latest build you have posted and openGapps but for some reason I'm having extremely slow wifi performance. On a network that's capable of 250Mbps I was getting 7Mbps, and now on a mobile hotspot I'm seeing 90kbps. Is there some tuning setting for the wifi I'm missing by default?
Click to expand...
Click to collapse
have same problem, you solved ? i'll return to my other room, but i lost modem and say no sim card now
nick79325 said:
Hi, thanks so much for doing this! I flashed the latest build you have posted and openGapps but for some reason I'm having extremely slow wifi performance. On a network that's capable of 250Mbps I was getting 7Mbps, and now on a mobile hotspot I'm seeing 90kbps. Is there some tuning setting for the wifi I'm missing by default?
Click to expand...
Click to collapse
does it fixed?
{
"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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/10.0/README.mkdn
VoLTE
WireGuard
MicroG support
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
gapps (Download from here)
Magisk 20.0 or newer for root (after first boot) - (Download from here)
First time installation:
Fastboot Flash Essential's Jan update (You can get it here)
Flash twrp, then boot into it.
Flash the rom.
Flash the twrp zip.
Optional: flash OpenGapps package of your choice.
Optional: boot into system, then flash magisk.
Sources:
ROM: https://github.com/crdroidandroid
Kernel: kernel url
Download:
ROM https://www.androidfilehost.com/?w=files&flid=314554
Changelog: https://raw.githubusercontent.com/crdroidandroid/android_vendor_crDroidOTA/10.0/changelog_<device codename>.txt
Known issues:
Speaker phone call volume stays at a fixed level.
Visit official website @ crDroid.net
crDroid <device> Telegram
crDroid Community Telegram
Donate to help our team pay server costs
XDA:DevDB Information
crDroid, ROM for the Essential Phone
Contributors
monark88
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Flash January Stock image.
Based On: LineageOS
Version Information
Status: Testing
Created 2020-07-06
Last Updated 2020-11-09
Reserved
I was quite tired of all the mata ROMs with built-in gapps, and so many without all the great customizations that crDroid brings. We needed a ROM with Signature Spoofing for microg support. I've tested out the 360 degree camera, it's working. I tested phone calls, wifi, messaging, and microg installation. All works, can even get location with UnifiedNLP on Android 10! I tested with minmicrog and NanoDroid with magisk overlay.
If this is well received, I'll work on improving issues and getting official status.
Reserved2
Thank you. I'm going to test it.
Funny I would see this. I had the exact same idea yesterday. I finally got around to building crDroid v6.7 with the LineageOS 17.1 kernel as you have. I also used the LineageOS 17.1 device files, and TheMuppets vendor files, (https://github.com/TheMuppets/proprietary_vendor_essential). I then installed Magisk and MinMicroG NoGoolag edition. I find that this ROM so far has been working fine. The only real issue I have found is that Aurora Droid which is installed from the MinMicroG package seems to crash during the first launch sync. However, relaunching it and syncing resolves the issue. This didn't seem to happen when building LineageOS 17.1 with full signature spoofing when I was testing that. Not entirely sure though if others will see that, or if it was my build.
I really hope to see your build get more testing, and get official status!
Best of luck!
TDP95 said:
Funny I would see this. I had the exact same idea yesterday. I finally got around to building crDroid v6.7 with the LineageOS 17.1 kernel as you have. I also used the LineageOS 17.1 device files, and TheMuppets vendor files, (https://github.com/TheMuppets/proprietary_vendor_essential). I then installed Magisk and MinMicroG NoGoolag edition. I find that this ROM so far has been working fine. The only real issue I have found is that Aurora Droid which is installed from the MinMicroG package seems to crash during the first launch sync. However, relaunching it and syncing resolves the issue. This didn't seem to happen when building LineageOS 17.1 with full signature spoofing when I was testing that. Not entirely sure though if others will see that, or if it was my build.
I really hope to see your build get more testing, and get official status!
Best of luck!
Click to expand...
Click to collapse
I did have one force close of NLP backend with minmicrog, but it cleared up after the initial crash. NanoDroid beta had no issues. It's comforting to know others are interested in gapps-less (or less gapps ) ROMs, to the extent of building their own!
monark88 said:
I did have one force close of NLP backend with minmicrog, but it cleared up after the initial crash. NanoDroid beta had no issues. It's comforting to know others are interested in gapps-less (or less gapps ) ROMs, to the extent of building their own!
Click to expand...
Click to collapse
Speaking of NLP, and location services in general, I do notice in the microG self-check mine appears to not have the proper permission to access location in the background, and it seems the permissions is unknown. I see the permissions as "android.permissions.group.UNDEFINED", and I am unable to grant it permission. Did you notice this as well? Or, were you able to provide all permissions without issue?
TDP95 said:
Speaking of NLP, and location services in general, I do notice in the microG self-check mine appears to not have the proper permission to access location in the background, and it seems the permissions is unknown. I see the permissions as "android.permissions.group.UNDEFINED", and I am unable to grant it permission. Did you notice this as well? Or, were you able to provide all permissions without issue?
Click to expand...
Click to collapse
The only thing I had to do finish microg setup was run this from ADB or termux.
Code:
pm grant com.android.vending android.permission.FAKE_PACKAGE_SIGNATURE
I've attached screenshots of my microg self-check results and locations permissions. The only unticked box is last known location, which I think is because I haven't used it since last flash..
EDIT: attachments weren't loading.. uploaded here
Thanks! I have already granted signature spoofing, and that appears correct. I'll check into this more later.
Thanks for the rom, I saw two issues related to Lineage tree, VoLTE not work for me, I fix with a Magisk module and codec aptx don't work too.
mpena said:
Thanks for the rom, I saw two issues related to Lineage tree, VoLTE not work for me, I fix with a Magisk module and codec aptx don't work too.
Click to expand...
Click to collapse
Thank you for reporting the issues. If I may ask, what magisk module did you flash to fix VoLTE?
EDIT: i think i found it here
monark88 said:
Thank you for reporting the issues. If I may ask, what magisk module did you flash to fix VoLTE?
EDIT: i think i found it here
Click to expand...
Click to collapse
Yes that is
Something I have noticed with my build is that the status bar clock freezes, and the network monitor when enabled in the crDroid settings disappears from the status bar quite frequently. The time on the lock screen and clock app appear correct always. Rebooting the system or system UI, as well as locking and unlocking a few times corrects it. But it happens again after the next lock or so. Is this something you have noticed with your build as well? Or, are you not seeing these issues?
So far so good. I love performance on this rom. The only issue for me is crdroid launcher. I'm replace it with pixel launcher + quickswitch and everything working so smooth. I'm waiting for the next build in future for more optimize.
Any chance to have the wireguard module baked in the kernel?
Thanks for this gappless signature spoofing enabled Rom!
Finally one that works out of the box
foueddyf said:
Any chance to have the wireguard module baked in the kernel?
Thanks for this gappless signature spoofing enabled Rom!
Finally one that works out of the box
Click to expand...
Click to collapse
I will add WireGuard support in the next release. Thank you for your suggestions, and feedback!
mpena said:
Thanks for the rom, I saw two issues related to Lineage tree, VoLTE not work for me, I fix with a Magisk module and codec aptx don't work too.
Click to expand...
Click to collapse
foueddyf said:
Any chance to have the wireguard module baked in the kernel?
Thanks for this gappless signature spoofing enabled Rom!
Finally one that works out of the box
Click to expand...
Click to collapse
New release is up. It has WireGuard and VoLTE enabled by default. Tested both, both working. Be aware that there could be a DNS leak for wireguard using kernel right now.
Screenshots for proof
Download is in first post, or you can shortcut here.
Dirty flash worked fine for me, but ymmv.
monark88 said:
New release is up. It has WireGuard and VoLTE enabled by default. Tested both, both working. Be aware that there could be a DNS leak for wireguard using kernel right now.
Screenshots for proof
Download is in first post, or you can shortcut here.
Dirty flash worked fine for me, but ymmv.
Click to expand...
Click to collapse
Bluetooth fixed ? Need gappless but also need aptx.
Also ymmv?
Your Mileage May Vary (YMMV) - basically saying that your results may not match exactly to the ones shown.
dememted1 said:
Bluetooth fixed ? Need gappless but also need aptx.
Also ymmv?
Click to expand...
Click to collapse
I made no changes in regards to aptx. Is there an essential ROM that does have aptx working? I can look at how they've implemented and try to recreate.
Failing that, I don't foresee myself implementing aptx into this ROM.
{
"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.
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. LineageOS does still include various proprietary hardware-specific code.
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.
Informations :
This ROM uses source built kernel, kernel modules, boot kernel modules (vendor_boot) and vendor image.
This ROM bundles the latest firmware so you don't have to worry about updating firmware.
To use the eSIM you need to have GApps
Instructions :
Follow https://wiki.lineageos.org/devices/barbet/install for how to install
Follow https://wiki.lineageos.org/devices/barbet/upgrade for how to upgrade from LineageOS 19
Downloads :
Official builds
Optional GApps: MindTheGapps
Reporting Bugs
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/*
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.
Known Issues
Google Play Store provides a very out of date version of Google Camera. You can use GoogleCamera.apk extracted from stock here
Contributors
mikeioannina
aleasto
The LineageOS team
Source Code: https://github.com/LineageOS
ROM OS Version: Android 13
Source code temporarily on my github before it can be moved to the LineageOS organization
Thanks for putting this together so quickly! I've been running for a couple of days now with MindTheGapps and haven't noticed any significant issues. I'm now pretty darn satisfied with my new 5a (Even though it's a friggin chonk). I'm on Visible and I was able to just pop my SIM card in and everything worked. Wifi calling, texting, 5G connection, etc - all good.
Only weird thing I've noticed is that after setting up fingerprints for device locksreen security I'm not able to then use fingerprint security within my other apps. For example - Chase app tells me "You haven't set up fingerprint sign in on this device", PayPal app says "We're having trouble confirming your fingerprint right now" and Bitwarden app doesn't present an option to enable "Unlock with Biometrics". So I'm using currrently using PINs for these apps which is a fine compromise for me - would be curious to know whether others have experienced this.
There have been some changes to SafetyNet in the past couple of days that tripped ctsProfile on my Pixel 4a running official LineageOS but I was able to pass SafetyNet check in this ROM by installing kdrag0n's Universal SafetyNet Fix v2.0.0 and using MagiskHide Props Config to set device fingerprint to Pixel 5.
CapriciousCrawdad said:
Thanks for putting this together so quickly! I've been running for a couple of days now with MindTheGapps and haven't noticed any significant issues. I'm now pretty darn satisfied with my new 5a (Even though it's a friggin chonk). I'm on Visible and I was able to just pop my SIM card in and everything worked. Wifi calling, texting, 5G connection, etc - all good.
Only weird thing I've noticed is that after setting up fingerprints for device locksreen security I'm not able to then use fingerprint security within my other apps. For example - Chase app tells me "You haven't set up fingerprint sign in on this device", PayPal app says "We're having trouble confirming your fingerprint right now" and Bitwarden app doesn't present an option to enable "Unlock with Biometrics". So I'm using currrently using PINs for these apps which is a fine compromise for me - would be curious to know whether others have experienced this.
There have been some changes to SafetyNet in the past couple of days that tripped ctsProfile on my Pixel 4a running official LineageOS but I was able to pass SafetyNet check in this ROM by installing kdrag0n's Universal SafetyNet Fix v2.0.0 and using MagiskHide Props Config to set device fingerprint to Pixel 5.
Click to expand...
Click to collapse
I doubt you need to set device fingerprint to Pixel 5 for safetynet.
Will fix fingerprint in apps in the next build now fixed
Thanks for the build! it seems mostly good from my testing but one issue im having... for some reason the phone refuses to connect to the carrier after a sim card is inserted. I can see that it is detecting it, and that it sees that it should be using t-mobile, but It wont connect. Not sure if this helps, but i got a logcat of adding the simcard and airplane mode toggling on/off. maybe there is a useful log in there. Log is here. Thank you for your hard work!
grassyloki said:
Thanks for the build! it seems mostly good from my testing but one issue im having... for some reason the phone refuses to connect to the carrier after a sim card is inserted. I can see that it is detecting it, and that it sees that it should be using t-mobile, but It wont connect. Not sure if this helps, but i got a logcat of adding the simcard and airplane mode toggling on/off. maybe there is a useful log in there. Log is here. Thank you for your hard work!
Click to expand...
Click to collapse
I'm afraid i don't know what's wrong.
Can you try with adb logcat -d -b radio
aleasto said:
I'm afraid i don't know what's wrong.
Can you try with adb logcat -d -b radio
Click to expand...
Click to collapse
Here you go
aleasto said:
I doubt you need to set device fingerprint to Pixel 5 for safetynet.
Will fix fingerprint in apps in the next build now fixed
Click to expand...
Click to collapse
You're right. I'm passing now with Pixel 5a fingerprint.
Also thanks for the quick update. After flashing 09/07 build all the biometric security stuff is working as expected. All apps I'd listed in my previous post are fixed.
No new issues to report. Loving the setup
New build out with september security patch
@grassyloki Does your radio work on the latest build by any chance?
aleasto said:
@grassyloki Does your radio work on the latest build by any chance?
Click to expand...
Click to collapse
I can verify radio is fine on my phone. Maybe it's carrier related. I'm on Google Fi with E-sim.
aleasto said:
@grassyloki Does your radio work on the latest build by any chance?
Click to expand...
Click to collapse
The build did not initially... but some fiddling with hidden menus eventually triggered cellular to activate!
See this video as to the issue. Basically the phone was seeing the SIM but not activating, same as the other builds. Airplane mode did nothing, even leaving it for an extended period of time off. I did get it eventually working by heading into the secret menu *#*#4636#*#* in the dialer, then the phone info screen. In here I cycled mobile radio power and changed the prefered network type to something different. Then Cellular activated. Once that happened, i went and selected the correct APN and enabled mobile data, and it worked! Not sure if any code change effected this outcome, but im just glad its working now! Thanks for the build and looking at my issue. Maybe this will help someone out who is having the same issue.
does the lineage updater work on this build or whats the process to update to the newest build?
thanks
aleasto said:
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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. LineageOS does still include various proprietary hardware-specific code.
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.
Informations :
This ROM uses source built kernel, kernel modules, boot kernel modules (vendor_boot) and vendor image.
This ROM bundles the latest firmware so you don't have to worry about updating firmware beforehand.
To use the eSIM you need to have GApps
Instructions :
Download the latest recovery image and rom zip
Boot to bootloader
fastboot flash boot lineage-recovery.img
Boot to recovery
Format data
Sideload LineageOS zip
Optionally flash any addons:
Advanced > Reboot to recovery
Sideload the addons
Reboot
See https://wiki.lineageos.org/devices/redfin/install for more detailed instructions (that's for Pixel 5 but the procedure is the same)Downloads :
Unofficial builds: sourceforge
Optional GApps: MindTheGapps or opengapps nano
Reporting Bugs
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/*
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.
Known Issues
Stock Google Camera app crashes in Night Mode or Astrophotography. As a workaround, install this magisk module.
Contributors
aleasto
The LineageOS team
Source Code: https://github.com/LineageOS
ROM OS Version: Android 11
Click to expand...
Click to collapse
The recovery I flashed keeps telling me that "E:Failed to open /dev/block/bootdevice/by-name/misc: No such file or directory"
Flash Factory Reset also fails for that reason.
I am unable to Enable ADB to Flash Lineage OS for this reason. What am I doing wrong? I used https://mirrorbits.lineageos.org/recovery/redfin/20210908/lineage-18.1-20210908-recovery-redfin.img
Zedicus said:
does the lineage updater work on this build or whats the process to update to the newest build?
thanks
Click to expand...
Click to collapse
Updater does not provide unofficial builds.
Boot recovery and sideload the new zip. If you had addons (gapps, magisk), reboot recovery and flash them again, like the first time.
weeems said:
The recovery I flashed keeps telling me that "E:Failed to open /dev/block/bootdevice/by-name/misc: No such file or directory"
Flash Factory Reset also fails for that reason.
I am unable to Enable ADB to Flash Lineage OS for this reason. What am I doing wrong? I used https://mirrorbits.lineageos.org/recovery/redfin/20210908/lineage-18.1-20210908-recovery-redfin.img
Click to expand...
Click to collapse
Pixel 5a is barbet. That recovery says it's for redfin (Pixel 5).
You need to download the recovery from the sourceforge link in the OP.
Uploaded a new build.
No differences except some experiments on kernel side (branch redbull-merge for the sources). Please let me know if audio still works:
https://sourceforge.net/projects/aleasto-lineageos/files/LineageOS%2018.1/barbet/lineage-18.1-20210911-UNOFFICIAL-barbet.zip/download
Is there a prebuilt magisk for this?
I am on 0909 and audio has been working. It does not get real loaud but otherwise works fine.
Thanks for the build.
Zedicus said:
Is there a prebuilt magisk for this?
Click to expand...
Click to collapse
Just adb sideload Magisk-v23.0.apk in recovery
aleasto said:
Uploaded a new build.
No differences except some experiments on kernel side (branch redbull-merge for the sources). Please let me know if audio still works:
https://sourceforge.net/projects/aleasto-lineageos/files/LineageOS%2018.1/barbet/lineage-18.1-20210911-UNOFFICIAL-barbet.zip/download
Click to expand...
Click to collapse
Just got my 5a delivery today. Applied today's image, worked without any issues whatsoever. Fantastic work, very much appreciated.
{
"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 12, 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/enchilada
Downloads :
https://download.lineageos.org/enchilada
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:
Great..........
a surprise gift for oneplus 6 thanks for the great things you do !
Thanks , looking forward for this project
Thanks for bringing LineageOS 19 to our device. Everything is working as expected, Just a small bug in Volte/Vowifi calls IMS ringtone is missing.
Ggreat！！！
vikash1994b said:
Thanks for bringing LineageOS 19 to our device. Everything is working as expected, Just a small bug in Volte/Vowifi calls IMS ringtone is missing.
Replacing ims.apk from evolutionX vendors fixed it. Link: https://github.com/Evolution-X-Devi...mmit/b38ca998c8c916cdd2685b07f8aafd89a863e142
Click to expand...
Click to collapse
Did you upgrade from 18 or clean flash?
diemadedrei said:
Did you upgrade from 18 or clean flash?
Click to expand...
Click to collapse
Clean flash
-- posting just to have this thread in my 'new posts' view --
Has anyone tried ih8sn with this version?
And if it works what is recommended in the conf file?
With 18.1 I used this but in 19 I'm unsure since the android version no longer matches, perhaps it is better to use another phones build info.
Code:
BUILD_FINGERPRINT=OnePlus/OnePlus6/OnePlus6:11/RKQ1.201217.002/2111252325:user/release-keys
BUILD_DESCRIPTION=OnePlus6-user 11 RKQ1.201217.002 2111252325 release-keys
BUILD_SECURITY_PATCH_DATE=2021-11-01
BUILD_TAGS=release-keys
BUILD_TYPE=user
BUILD_VERSION_RELEASE=11
DEBUGGABLE=0
MANUFACTURER_NAME=OnePlus
PRODUCT_NAME=OnePlus6
ponanovn said:
Has anyone tried ih8sn with this version?
And if it works what is recommended in the conf file?
With 18.1 I used this but in 19 I'm unsure since the android version no longer matches, perhaps it is better to use another phones build info.
Code:
BUILD_FINGERPRINT=OnePlus/OnePlus6/OnePlus6:11/RKQ1.201217.002/2111252325:user/release-keys
BUILD_DESCRIPTION=OnePlus6-user 11 RKQ1.201217.002 2111252325 release-keys
BUILD_SECURITY_PATCH_DATE=2021-11-01
BUILD_TAGS=release-keys
BUILD_TYPE=user
BUILD_VERSION_RELEASE=11
DEBUGGABLE=0
MANUFACTURER_NAME=OnePlus
PRODUCT_NAME=OnePlus6
Click to expand...
Click to collapse
Worked fine the last time i tried on self compiled lineage 19.1, so should work here too.
Just did a dirty flash from LOS 18.1 and everything works fine.
I had to reinstall some Google apps (YouTube, Gmail, Keep, GCam, Photos), as they stopped working after the upgrade (maybe because I accidentally clicked No on the Signature verification failed screen while flashing Gapps and didn't notice, then the OS didn't boot. whoops. So I went back into the recovery and flashed Gapps again. Sure enough, the install went through. So be careful and make sure to click the correct button, lol)
Everything else seems to work perfectly!
Thanks again LuK for your work!
In case anyone with Gapps and Magisk wants to try a dirty flash from 18.1, here are the steps I did:
(you're on your own if things break! better to do a clean flash! magisk isn't officially supported!)
1. Restored images in Magisk
2. Removed PIN and fingerprints
(Not sure if these first two steps are needed, but did them just in case)
3. adb reboot sideload
4. adb sideload lineage-19.1-20220426-nightly-enchilada-signed.zip
5. Advanced->Reboot to Recovery
6. Apply Update->Apply from ADB
7. adb sideload MindTheGapps-12.1.0-arm64-20220416_174313.zip
8. adb sideload Magisk-v24.3.apk
9. Back->Reboot system now
Wow! I installed from latest oxygenos. I unlocked the bootloader and followed the tutorial. It all works perfectly. Thanks a lot!
Awesome, just updated from 18.1 to 19.1. Everything seems OK.
Reboot to Recovery, then when your device reboots, click Apply Update, then Apply from ADB.
adb sideload lineage-19.1-20220426-nightly-enchilada-signed.zip
Reboot to Recovery
adb sideload MindTheGapps-12.1.0-arm64-20220416_174313.zip
adb sideload Magisk-v24.3.apk
Reboot system now
Couldn't be any easier. Thanks @LuK1337
Thank you all, in particular LuK1337, I've been waiting for this for some time. I have 3 questions:
- Is call recorder implemented?
- I use AFWall+, but iptables is deprecated. How works eBPF? Is a separated app or built-in on generic SO settings (Apps menu)? Some opinion AFWall+ vs EBPF?
- Also, I use Adaway, Magisk works fine?
OP6 is my daily driver and older devices are not supported, for this reason I ask.
Thanks!
Thanks LuK1337. Just installed it in my OP6. Initial impression is good.
pdmr said:
Thank you all, in particular LuK1337, I've been waiting for this for some time. I have 3 questions:
- Is call recorder implemented?
- I use AFWall+, but iptables is deprecated. How works eBPF? Is a separated app or built-in on generic SO settings (Apps menu)? Some opinion AFWall+ vs EBPF?
- Also, I use Adaway, Magisk works fine?
OP6 is my daily driver and older devices are not supported, for this reason I ask.
Thanks!
Click to expand...
Click to collapse
Magisk and Adaway works just fine, not sure about the others
19.1 runs fine so far. but when I relock the bootloader, I always end in fastboot mode (bootloader). with 18.1 it was working.
Hi, the upgrade was smooth. I've noticed that notification sound seems quite loud, even when set to the first notch (lower means muted).
Also sometimes the status bar is a bit off, here the 4G inscription
CrysisLTU said:
Magisk and Adaway works just fine, not sure about the others
Click to expand...
Click to collapse
Thanks! v24.3 and patching boot.img?