{
"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
Wifi
Audio ( Record and Playback )
What's partially working:
Bluetooth
Video Playback
Camera
Camcorder
Flash
GPS
Nfc
What's not working :
SELinux enforcing
HWcomposer is buggy(rendering is made by gpu in order to avoid artifacts)
Instructions :
Download the latest build and gapps
Reboot to recovery
Do all wipes
Flash the latest build and gapps
Downloads :
Latest Build : LineageOS-16
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.
Sources
linckandrea - Repositories
Andrea Pucci. linckandrea has 46 repositories available. Follow their code on GitHub.
github.com
Credits :
LineageOS Team
if you want to offer me a coffee or anything else check this
reserved
nice, i never thought we would get another android pie attempt, Ill try soon
I just installed it and it works fine, but pls add sources. I already found them, but you should add them in your post.
and ofc thanks for all the effort you made @linckandrea
I am the first person to soft brick my N9 ig. To be fair, I installed Magisk, dirty flashed, ran undecrypted, everything not ideal circumstances, but here are ramoops as it now only boots to recovery saying "RescueParty".
cant share logs due to size limitations in xda, pastebin and hastebin. If you have a telegram acc it would make things easier.
Thanks for releasing 16.0. While I did have a bootable 16.0 back in March 2021, I couldn't fix the hwcomposer problems.
With your 16.0 build, Clash Royale completely froze and locked up after 15 minutes (roughly 5 games, each is 3 minutes long). adb logcat shows running low on memory? I can play same game on 15.1 with no problems.
After getting the logcat, I tried to start Clash Royale again, but the entire device locked up again and I get the same System UI isn't responding that I reported earlier.
Code:
5585 06-23 18:42:44.198 264 355 E ActivityManager: ANR in com.android.systemui
5586 06-23 18:42:44.198 264 355 E ActivityManager: PID: 661
5587 06-23 18:42:44.198 264 355 E ActivityManager: Reason: Input dispatching timed out (Waiting to send non-key event because the touched window has not finished processing certain input events that were delivered to it over 500.0ms ago. Wait queue length: 1. Wait queue head age: 6085.9ms.)
5588 06-23 18:42:44.198 264 355 E ActivityManager: Load: 4.6 / 2.01 / 1.62
5589 06-23 18:42:44.198 264 355 E ActivityManager: CPU usage from 0ms to 22509ms later (2021-06-23 18:42:21.538 to 2021-06-23 18:42:44.047):
Here's the output of top from adb shell. BTW, there's no rush to look at this. I know you are still fine tuning your changes locally and on github. Thanks.
Code:
Tasks: 198 total, 1 running, 197 sleeping, 0 stopped, 0 zombie
Mem: 1879792k total, 1306832k used, 572960k free, 816k buffers
Swap: 786428k total, 158840k used, 627588k free, 553684k cached
SirRGB said:
I just installed it and it works fine, but pls add sources. I already found them, but you should add them in your post.
and ofc thanks for all the effort you made @linckandrea
Click to expand...
Click to collapse
source link added(i missed when created the thread but they were already present(with git history) on my github account)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
retiredtab said:
Thanks for releasing 16.0. While I did have a bootable 16.0 back in March 2021, I couldn't fix the hwcomposer problems.
With your 16.0 build, Clash Royale completely froze and locked up after 15 minutes (roughly 5 games, each is 3 minutes long). adb logcat shows running low on memory? I can play same game on 15.1 with no problems.
Click to expand...
Click to collapse
due to broken hwc display composition is made by only the gpu
(this means that every heavily gpu apps will perform bad as the gpu does all the work)
retiredtab said:
Here's the output of top from adb shell. BTW, there's no rush to look at this. I know you are still fine tuning your changes locally and on github. Thanks.
Code:
Tasks: 198 total, 1 running, 197 sleeping, 0 stopped, 0 zombie
Mem: 1879792k total, 1306832k used, 572960k free, 816k buffers
Swap: 786428k total, 158840k used, 627588k free, 553684k cached
Click to expand...
Click to collapse
Would you say that @linckandrea 's v16 release is more up-to-date than your v15.1 release?
Obviously v16 > v15.1 but I wonder if the functionality is the same?
Having used both releases, would you say this one is more stable than your own?
Your last update for v15.1 was as of June 13, 2021.
Does this v16 update include both the security updates AND the hardware fixes in yours?
Such as improving the GPU rendering, etc?
I would assume that because it's v16, it would include all previous fixes from v15.1? Am I wrong in thinking this?
Or is the hardware decoding of video or say, YouTube; still an issue?
Also related/unrelated to these ROMs, have either of you (or other users reading) had the issues with the NEXUS9 related to crashing prior to installing any ROM; and then having those issues be resolved with the installation of this or any other ROMs? I'd like to know if this is a hardware-based or software-based issue.
If my NEXUS9 is still going to crash, I don't think it's worth my time installing any ROMs, etc.
Will there be any more development of Android 9? I am asking because your repos werent updated since June 24th and I dont know of anyone else, that is working on it...
SirRGB said:
Will there be any more development of Android 9? I am asking because your repos werent updated since June 24th and I dont know of anyone else, that is working on it...
Click to expand...
Click to collapse
i'm actually using a custom build of los15.1 of my nexus 9,
the hwcomposer bug is due by outdated display blobs(there's no tegra k1 device that has an oem pie build(this means that this issues will never be resolved))
so it is worth fixing the remain bugs when the performance will sucks no matter what?
probably not
and yes even on los17.1/18.1 display blobs would be the same
I currently run los16 just to try it and it runs quite nicely (only minor bugs e.g. livedisplay broken like A8, permissive selinux, ?fullscreen issue?). Ig dirty flashing was the reason it didnt work properly back then... Just wanted to note: a lot of people are using your build, so thanks for all your work.
LineageOS Statistics
stats.lineageos.org
When i power off, the device is in some sort of sleep not true power off. I power off and there was 50% battery and when i switch it on weeks later battery is depleted. I noticed this with another rom i installed before. Any way around this ? To get a true power off. Apart from this, the rom works great.
I made an enforcing build a few months ago, but now I cant get Lineage 16.0 to build... Can someone look into it?
hastebin
I use your dt, kt and vt
SirRGB said:
I made an enforcing build a few months ago, but now I cant get Lineage 16.0 to build... Can someone look into it?
Click to expand...
Click to collapse
I'm not an expert in compiler flags, but if I'm understanding this correctly ...
Code:
In file included from external/tinycompress/compress.c:57:
In file included from bionic/libc/include/fcntl.h:95:
bionic/libc/include/bits/fortify/fcntl.h:63:26: error: use of undeclared identifier 'O_TMPFILE'
__clang_error_if(__open_modes_useful(flags), "'open' " __open_too_few_args_error) {
it's complaining that 'O_TMPFILE' is not declared. You can bypass this by removing line 7 at
https://github.com/LineageOS/android_external_tinycompress/blob/lineage-16.0/Android.bp#L7
The "-Werror" according to
https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html
"Make all warnings into errors."
So by removing that flag, it should compile now.
Hm, I understand, but sadly it didnt work. In the end I nuked all flags and removed the out folder, but nothing changed...
Try renaming the external/tinycompress/Android.bp file to Android.bp.old as a test. That won't build that library at all then. You may also have to grep through the device/htc/flounder directory for instances of libtinycompress and comment it out.
I haven't tried to build 15.1 yet so I don't know if I will be affected by this or it's just in the 16.0 tree or it's specific to your build environment.
SirRGB said:
I made an enforcing build a few months ago, but now I cant get Lineage 16.0 to build... Can someone look into it?
hastebin
I use your dt, kt and vt
Click to expand...
Click to collapse
You used the wrong kernel branch... Pick lineageos-16...
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.
Warning !
Installing a custom ROM on your device can sometimes be difficult and also with unwanted consequences! Therefore, make sure that you understand exactly what risks this operation entails - you are the only one responsible for all actions taken on your device.
What's Working :
Touchscreen
Audio & Video
Hardware video decoder
Wi-Fi
Bluetooth
Lights
Camera
Internal/External Storage
USB/ADB/MTP/OTG
Off-mode Charging
DRM enabled ( the same Level L3 like on Stock EMUI Firmware )
Sensors
Notification light
Fingerprint scanner
RIL & LTE data connection
What's Not Working :
WiFi tethering
SELinux Disabled
Encryption
GPS
Instructions :
Install the new TWRP 3.3.1-1 ( needed for Android Pie/Q )
Reboot to TWRP 3.3.1-1
Perform a clean wipe for the first install
Flash the latest build available and gapps
Reboot
Downloads :
Final Build : 07/03/2021 : LineageOS-16.0-BTV
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.
DEV: Information
Contributors
surdu_petru
Kernel Source Code: android_kernel_huawei_btv
ROM OS Version: LineageOS 16.0 - Android Pie
Version Information
Status: CLOSED
Created 2020-11-22
Last Updated 2020-12-06
TWRP 3.3.1-1
TWRP 3.3.1-1
Downloads :
twrp-3.3.1-1.img md5: 5267939dc15954d4538855743e100ed7
*** reserved ***
Oooo
Very exciting news!
question: Why are you working on Android 9 instead of jumping to Android 10? (i think i saw in the other thread that you already managed to boot it up on your tablet)
Awesome! Btw encryption is listed as not working, does this mean android adoptable storage won't work?
Been using it for half a day now. I'm amazed that it's not laggy/buggy for a testing build.The build is fluid and smooth. I thought it'll random reboot every 5 minutes. No force closes or reboots until now. I might be spesking too soon though.
For rotation I used *rotation control* app from the play store and the controls are pinned in the notifications.
And Because it felt that stable I went and installed magisk and safetynet passed with the same steps explained in the Oreo thread.
Pie gestures are there for who cares about it. And you can enable A10 gestures with magisk and an app.. You can google (Android 10 gestures for android pie) and it's worth it tbh.
ofc If I encounter any bug first thing I'd do is removing magisk.
Appreciate your work man. Hope working on the Oreo builds helped a little in bringing Pie. We saw a glimpse of the huge efforts you made to bring Oreo and you keep pushing through.. Hope you're getting enough sleep n rest.
---------- Post added at 11:13 AM ---------- Previous post was at 11:08 AM ----------
ravedave2005 said:
Very exciting news!
question: Why are you working on Android 9 instead of jumping to Android 10? (i think i saw in the other thread that you already managed to boot it up on your tablet)
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=83888223&postcount=686
orangpelupa said:
Awesome! Btw encryption is listed as not working, does this mean android adoptable storage won't work?
Click to expand...
Click to collapse
Yes, unfortunately it doesn't work ... I guess it's working in the same way like in LOS 15.1.
I'll spend a few days in the near future to see why it doesn't work and maybe I'll find a solution.
Half Alive said:
Been using it for half a day now. I'm amazed that it's not laggy/buggy for a testing build.The build is fluid and smooth. I thought it'll random reboot every 5 minutes. No force closes or reboots until now. I might be spesking too soon though.
For rotation I used *rotation control* app from the play store and the controls are pinned in the notifications.
And Because it felt that stable I went and installed magisk and safetynet passed with the same steps explained in the Oreo thread.
Pie gestures are there for who cares about it. And you can enable A10 gestures with magisk and an app.. You can google (Android 10 gestures for android pie) and it's worth it tbh.
ofc If I encounter any bug first thing I'd do is removing magisk.
Appreciate your work man. Hope working on the Oreo builds helped a little in bringing Pie. We saw a glimpse of the huge efforts you made to bring Oreo and you keep pushing through.. Hope you're getting enough sleep n rest.
Click to expand...
Click to collapse
Thank you very much for your feedback
Update !
All sensors are working now on LOS 16.0
Hi !
Fingerprint sensor it's also fixed right now
Unfortunately the camera does not seem to be able to activate very easily ...
Starting now to build Android 11 , Lineage OS 18 ... if I manage to boot successfully, I guess I'll abandon this project ( and also I'll skip Android 10 ) and I'll start working on the last Android !
Why Android 9 without Camera working, instead Android 11 without Camera working, right ?
Anyway, I'll keep you updated ...
Hello,
First of all, I want to thank you for your amazing work. I really appreciate it.
Bugs in my btvdl09:
1) My bluetooth keyboard (logitech k380) connects but the tablet suddenly shuts down and boots into eRecovery. I'm having the same issue in LOS 15.1 and mentioned this issue in the thread. For LOS 15.1 I managed to resolve the issue by flashing your boot_lte_4.3.img kernel but I got the well-known wifi + bluetooth speed problem back!
The Google drive links of console-ramoops-0 and dmesg-ramoops-0 files (I don't know how to attach files to posts in threads.):
https://drive.google.com/file/d/1ObE1tOuG-5y50rDNMh5ZCJE6MrQP2cs8/view?usp=drivesdk
https://drive.google.com/file/d/1Oi5Od8U3If28GszdlRuZ6r8FNbJ58DPK/view?usp=drivesdk
2) When I insert a flash drive, everything works fine but as soon as i unplug the flash drive, it suddenly shuts down.
The links of console-ramoops-0 and dmesg-ramoops-0 files:
https://drive.google.com/file/d/1OskZOuvi0cc6nxI2fKNga9lamJEF5l6S/view?usp=drivesdk
https://drive.google.com/file/d/1OuHnnerAwUema7ufClNibt9XnByIIhLw/view?usp=drivesdk
3) I noticed that the display becomes snowy from time to time. It happens often under rather heavy tasks like surfing the web with 15 tabs open or installing something etc.
Below is the log file and a screenshot of the incident.
https://drive.google.com/file/d/1pp1CjEYiV-nvrfetfauQ1okFwsSBIEuk/view?usp=drivesdk
Userusing said:
Hello,
First of all, I want to thank you for your amazing work. I really appreciate it.
Bugs in my btvdl09:
1) My bluetooth keyboard (logitech k380) connects but the tablet suddenly shuts down and boots into eRecovery. I'm having the same issue in LOS 15.1 and mentioned this issue in the thread. For LOS 15.1 I managed to resolve the issue by flashing your boot_lte_4.3.img kernel but I got the well-known wifi + bluetooth speed problem back!
The Google drive links of console-ramoops-0 and dmesg-ramoops-0 files (I don't know how to attach files to posts in threads.):
https://drive.google.com/file/d/1ObE1tOuG-5y50rDNMh5ZCJE6MrQP2cs8/view?usp=drivesdk
https://drive.google.com/file/d/1Oi5Od8U3If28GszdlRuZ6r8FNbJ58DPK/view?usp=drivesdk
2) When I insert a flash drive, everything works fine but as soon as i unplug the flash drive, it suddenly shuts down.
The links of console-ramoops-0 and dmesg-ramoops-0 files:
https://drive.google.com/file/d/1OskZOuvi0cc6nxI2fKNga9lamJEF5l6S/view?usp=drivesdk
https://drive.google.com/file/d/1OuHnnerAwUema7ufClNibt9XnByIIhLw/view?usp=drivesdk
3) I noticed that the display becomes snowy from time to time. It happens often under rather heavy tasks like surfing the web with 15 tabs open or installing something etc.
Below is the log file and a screenshot of the incident.
https://drive.google.com/file/d/1pp1CjEYiV-nvrfetfauQ1okFwsSBIEuk/view?usp=drivesdk
Click to expand...
Click to collapse
Ok, I know your issues, unfortunately I can't do anything to fix your bluetooth keyboard.
New Update !
The links from OP are removed and will be updated asap !
You can download from here a second test of LOS 16.0 Android Pie .
Changelog:
All sensors fixed
Fingerprint sensor fixed
Downloads :
lineage-16.0.0-btv.zip
boot_w09.img
Thank you very much for your attention !
Did a total wipe, 9.0 nano gaaps, booted fine, restoring programs now, thanks!
friedsonjm said:
Did a total wipe, 9.0 nano gaaps, booted fine, restoring programs now, thanks!
Click to expand...
Click to collapse
OK, adoptable storage does not seem to work; formats card to 20% then reboots. Have to create partition on SD card using my PC, then format SD card to portable storage on M3 I am not able to download books using Amazon Kindle, I've uninstalled and reinstalled, won't download to main or SD Card. Other apps seem able to download OK Kindle error is 'Device Storage is Full' 19GB free on main, and 32GB free on SD Card
EDIT: And, I missed the part about the new TWRP version... time to start over.
OK, starting over, have confirmed that adopted storage still does not work.
SIM fixed right now on LOS 16.0 Android Pie !
Info not concerned to the WiFi devices.
The fix will be added to the next update !
Wooow.. U did it Los 16 for the M3...
Thank u so much for your hard work...
OK, new TWRP, fresh app installations, SD Card as portable storage, same problem with Kindle (on internal storage) being able to download.
EDIT: Apparently, when Kindle was restored, it did not automatically get storage permissions. Fixed that, and now working fine!
Will now try to download a Google Maps 'offline map' to internal.
This is strange... gboard installs, but voice typing does not work. Have checked permissions, that's not the issue. When I try to use it, says 'initializing' then that stops and does not allow voice input.
The problem may be that I don't have 'Voice Typing' showing under setting, even though gboard is installed... maybe because I used pico gaaps? Thinking about installing a larger package...
EDIT: Downloading the Micro GAAPS package added voice typing back into the system... I've turned on all permissions for board, set Google Voice typing to 'on,' and still not working.
I'm open to suggestions!
friedsonjm said:
This is strange... gboard installs, but voice typing does not work. Have checked permissions, that's not the issue. When I try to use it, says 'initializing' then that stops and does not allow voice input.
The problem may be that I don't have 'Voice Typing' showing under setting, even though gboard is installed... maybe because I used pico gaaps? Thinking about installing a larger package...
EDIT: Downloading the Micro GAAPS package added voice typing back into the system... I've turned on all permissions for board, set Google Voice typing to 'on,' and still not working.
I'm open to suggestions!
Click to expand...
Click to collapse
Well, on Android 9 our hal Audio ( we still using stock hal Audio from EMUI 5.x, Android 7 ) it's not fully working ... in fact wasn't working at all at beginning but I managed to find a hack to enable audio working but only partially as you can see !
Headset and also voice call on LTE devices it's not working due to this issue ... and ofcourse your related audio issues !
I'm sorry I wasn't clear from the beginning .
Hello !
{
"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"
}
Android 10 is coming on your Huawei MediaPad M3 8.4, Kirin 950 SoC with the LineageOS 17.1 !
Devices Supported: Huawei MediaPad M3 8.4 : BTV-DL09; BTV-L0J; BTV-W09
LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), 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.
Warning !
Installing a custom ROM on your device can sometimes be difficult and also with unwanted consequences! Therefore, make sure that you understand exactly what risks this operation entails - you are the only one responsible for all actions taken on your device.
What's Working :
Touchscreen
Sensors
Lights
Audio
Video
Bluetooth
WiFi
GPS
4G/data connectivity
Fingerprint sensor
Internal/External Storage
USB/ADB/MTP/OTG
Off-mode Charging
DRM enabled ( the same Level L3 like on Stock EMUI Firmware )
Hardware Video Decoder
What's Not Working :
Camera
USB tethering
Encryption
SELinux disabled !
there could be also others minor issues !
Instructions :
Install the new TWRP 3.3.1-1 ( needed for Android Pie/Q )
Reboot to TWRP 3.3.1-1
if you are installing LOS for the first time, you must format the data under TWRP and reboot device again to TWRP
Perform a clean wipe for the first install
starting with 14/05/2022 you can increase the system partition to 5GB from here
Flash the latest build available
optional flash ( always the last available packages ) GApps
Reboot
Downloads :
New Update February 2023 : LineageOS-17.1-BTV_2023-02-25
GApps : recommended : ARM64, Android 10 ( nano or pico for devices with 2GB of System Partition )
Credits :
dianlujitao - helped me to boot on Android 10 !
Luk1337 - helped me to fix TWRP for Pie/Q !
XePeleato - for his fix/hack of FPS !
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.
DEV: Information
Contributors :
surdu_petru
Paypal Donation : paypal.me/petrusurdu1
Kernel Source Code: android_kernel_huawei_btv
ROM OS Version: LineageOS 17.1 - Android 10
ROM Kernel: Linux 4.4.x
ROM Firmware Required: Stock Android 7 (Nougat) - EMUI 5.x
Based On: AOSP Android 10
Version Information :
Status: Stable
Created : 2020-12-06
Last Updated : 2023-02-25
*** reserved ***
Ok, the OP was updated right now with the links for download a very early test ... of course it's not be intended to be used, only for test and fun for the moment !
Thank you for your attention !
OK, installed with OpenGapps Micro; on boot, getting error 'Android System' 'There's an internal problem with your device. Contact your manufacturer for details.' This shows up over the 'Hi there' screen. I will try to continue the installation..
EDIT: It is not able to see wifi networks. I will skip and see what happens.
EDIT: Able to setup PIN; no option for fingerprint on setup.
EDIT: Booted Lineage, but still not able to see any wifi; at this point, I will stop testing.
friedsonjm said:
OK, installed with OpenGapps Micro; on boot, getting error 'Android System' 'There's an internal problem with your device. Contact your manufacturer for details.' This shows up over the 'Hi there' screen. I will try to continue the installation..
EDIT: It is not able to see wifi networks. I will skip and see what happens.
Click to expand...
Click to collapse
Yes, I have the same issue after boot ... I guess it'll be fixed in the next update, it's nothing serious ... Just a Warning !
Also you can consult What's Working list from OP !
Anyway, thank you very much for confirmation that it's booted successfuly on BTV-W09 !
I saw the title and I just laughed.. man I never ever expected to get a custom rom on this device let alone Android 10! .. will try it as soon as I can.
Half Alive said:
I saw the title and I just laughed.. man I never ever expected to get a custom rom on this device let alone Android 10! .. will try it as soon as I can.
Click to expand...
Click to collapse
Thanks !
Actually you can install it only for fan or to explore what Android 10 come with ... as for moment almost all functions are still not enabled !
This is a big surprise for me. Never expect to see a custom ROM for this device. Time to try to unlock the bootloader. Lineage 17.1 is a great ROM. Thanks!
Project Status : WIP. So I guess we will not be able to get the camera working?
surdu_petru said:
Thanks !
Actually you can install it only for fan or to explore what Android 10 come with ... as for moment almost all functions are still not enabled !
Click to expand...
Click to collapse
Yeah I know I read the short not working list haha.. And I can see that some didn't. Maybe make it bolder and bigger. XD
I used reverse tethering to get some kind of internet conenction. Installed some apps and I'm having fun. it's usable. Posting this comment from it now.
Chrome got some freezes. But the stock browser is working fine. For me if it's not soft rebooting every couple of seconds then it's usable. Job well done.
Amazing, because we can take modernity on our device thanks to you. I stay still EMUI, however I am glad that you give us great possibilities.
Thank you very much surdu_petru.
Hi !
Bluetooth & Audio fixed right now on Android 10 LOS 17.1 ... unfortunately, audio it works exactly like on Android 9 with the same issues .
For root, https://download.lineageos.org/extras only goes through 16.0 Wouldn't this ROM require 17 ?
surdu_petru said:
Hi !
Bluetooth & Audio fixed right now on Android 10 LOS 17.1 ... unfortunately, audio it works exactly like on Android 9 with the same issues .
Click to expand...
Click to collapse
Link says 17.1.1 lineage-17.1.1-btv.zip but download file name is lineage-17.1.0-btv.zip ?
friedsonjm said:
Link says 17.1.1 lineage-17.1.1-btv.zip but download file name is lineage-17.1.0-btv.zip ?
Click to expand...
Click to collapse
Ok, sorry ... fixed !
Booted... so far, same 'there is an internal problem with your device' error message immediately upon boot...
Still no connection to wifi, will restore back to 15.1 and wait for next version.
Thank you for continuing to develop this!
friedsonjm said:
Booted... so far, same 'there is an internal problem with your device' error message immediately upon boot...
Still no connection to wifi, will restore back to 15.1 and wait for next version.
Thank you for continuing to develop this!
Click to expand...
Click to collapse
Do you flashed the same build of LOS 17.1 and do you expect it to go better than the first time ?
surdu_petru said:
Do you flashed the same build of LOS 17.1 and do you expect it to go better than the first time ?
Click to expand...
Click to collapse
No, I booted the 2nd build, to see if there were any changes. Unless I'm confused and there was actually only one build?
friedsonjm said:
No, I booted the 2nd build, to see if there were any changes. Unless I'm confused and there was actually only one build?
Click to expand...
Click to collapse
I'm sorry once again that I wasn't explicit enough ... Usually I stated clearly New Update when a new release is out !
I'm working to fix WiFi before to release the second test and I hope to release the new update as soon as possible !
Hi,man,amazing rom update.It's too difficult to cook a custom android 10 rom because of the Huawei Kirin 950 chip.What are the difficulties in the future. Thank you surdu_petru.
{
"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"
}
DivestOS is a more private and more secure aftermarket system.
Galaxy Nexus Notes:
- GPS works on these builds!
- I wouldn't be surprised if there are radio issues on toro/toroplus.
edit: I managed to place a call in 2022(!) on my toroplus
Features:
- strong focus on FOSS
- various system hardening
- various privacy enhancements
- automated removal of unnecessary proprietary blobs
- automated kernel hardening and CVE patching
- ability to relock bootloader on supported devices
- verified boot on supported devices
- no root support
- SELinux always enforcing
- encrypted by default
- monthly updates
- OTA delta updates
- OTA updates over Tor (optional)
- F-Droid included
- hardened system WebView with rapid updates: https://divestos.org/misc/ch-dates.txt
Extra Features (not installed by default & also compatible with all systems):
- Mull, our hardened fork of Fenix with rapid updates: https://divestos.org/misc/ffa-dates.txt
- Hypatia, our real-time malware scanner
- Extirpater, our free space eraser
Links:
- Website: https://divestos.org
- Onion: http://divestoseb5nncsydt7zzf5hrfg44md4bxqjs5ifcv4t7gt7u6ohjyyd.onion
- Downloads: https://divestos.org/index.php?page=devices&base=LineageOS#device-maguro
- Changelogs: https://divestos.org/index.php?page=news
- Project History: https://divestos.org/index.php?page=history
- Known Issues: https://divestos.org/index.php?page=broken#maguro
- Screenshots: https://divestos.org/index.php?page=screenshots
- Security Patching Overview: https://divestos.org/index.php?page=patch_levels
- About + Credits + Notices: https://divestos.org/index.php?page=about
- Donate: https://divested.dev/donate
- Source Code: https://github.com/divested-mobile or https://gitlab.com/divested-mobile
- XMPP Chat Room: xmpp:[email protected]
Device Specific Links
- Device Tree: https://github.com/Galaxy-Nexus/android_device_samsung_tuna, https://github.com/Galaxy-Nexus/android_device_samsung_maguro, https://github.com/LineageOS/android_device_samsung_toro, https://github.com/LineageOS/android_device_samsung_toroplus
- Kernel: https://github.com/Galaxy-Nexus/android_kernel_samsung_tuna
- Kernel CVE Patches Applied: https://github.com/Divested-Mobile/...1/CVE_Patchers/android_kernel_samsung_tuna.sh
Other Bits:
- Good and bad feedback is welcomed. Else how can we improve?
- If you find a bug, please report it below or via GitHub/GitLab.
- Testing/Translations/Code contributions are gratefully appreciated.
Important Notes for New Users:
- Please make a backup of your device and copy it to another computer.
- You must wipe before installing this OS.
- This OS has userdata encrypted by default
- You are intended to relock your bootloader with this OS (if your device is marked supported for that).
DivestOS does *not* support the following:
- Google Apps (OpenGAPPS)
- DRM (Widevine)
- alternative recoveries (TWRP)
- root (Magisk)
- runtime modification frameworks (Xposed or theme engines)
All downloads are GPG signed with the following key:
Code:
#B874 4D67 F9F1 E14E 145D FD8E 7F62 7E92 0F31 6994
-----BEGIN PGP PUBLIC KEY BLOCK-----
mDMEXupIxBYJKwYBBAHaRw8BAQdAC1RiTvrqJaAQ4FIHsxX+gzEgdT4mspISS+p0
y847Nge0SERpdmVzdE9TIFJlbGVhc2UgU2lnbmluZyAoMjAyMCAjMSkgPHN1cHBv
cnQrcmVsZWFzZXNpZ25pbmdAZGl2ZXN0b3Mub3JnPoiQBBMWCAA4FiEEuHRNZ/nx
4U4UXf2Of2J+kg8xaZQFAl7qSMQCGwMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AA
CgkQf2J+kg8xaZR1BgEAwwLVVsG7kbp8M3GTV987XpVl5cZeTtDc/g+66briCHUB
APiuH/dk8eRnhFnq4Up2/j7uD/8FtSvxPbHiz6t1MdgB
=VzP2
-----END PGP PUBLIC KEY BLOCK-----
Thank you for updating this old device. I want to use Anydesk app in this rom to control it remotely. but in remote PC or phone it shows a message: "Connected! Waiting for image"
[email protected] said:
Thank you for updating this old device. I want to use Anydesk app in this rom to control it remotely. but in remote PC or phone it shows a message: "Connected! Waiting for image"
Click to expand...
Click to collapse
Likely will not work on DivestOS:
AnyDesk/TeamViewer accomplishes that by having “add-on” apps. Each app requests the INJECT_EVENTS permission.
However INJECT_EVENTS has a protectionLevel of signature meaning only apps signed with the releasekey of the system image can request it. If you take a look some of the add-on apps you’ll see that they are actually signed by each manufacturer.
jarsigner -verify -verbose -certs x.apk
Seems they managed to get a ton of manufacturers to sign their helper apps.
I have no intent on signing any proprietary software with my signing keys to grant such permissions.
Ok keep going on and keep DivestOS safe. thanks for quick replay
Thank you for supporting old devices like mine. Sadly this one (as well as all the other AOSP variants) I've tried fail to provide a working camera.
"Camera is not available".
I'm not sure you are familiar with zeelogs unofficial 7.1.2 build: https://zeelogkang.blogspot.com/2017/05/lineageos-141-unofficial-712-gnex-tuna.html + https://github.com/zeelog
This is the only rom so far that manages to give me a consistently working and responsive device. Everything (but GPS) just works. Sadly he's since moved on to other devices and is no longer updating it and thus we no longer get any security updates.
I've tried to build that rom myself with the plan to backport security fixes but so far I've failed even building a stable version.
Any advice/help/ideas?
entux said:
Thank you for supporting old devices like mine. Sadly this one (as well as all the other AOSP variants) I've tried fail to provide a working camera.
"Camera is not available".
Click to expand...
Click to collapse
Camera does work on this.
I think you might need to update your firmware maybe?
Try flashing the bootloader and radio partition again from here: https://developers.google.com/android/images#yakju
If that doesn't fix it, please upload a logcat:
adb logcat -b all -d | grep -i -e dlopen -e audit
at the minimum
So I am not entirely sure what "fixed" it. Either a combination of things or one specific thing of the following:
Update Firmware
Cleared cache and rebooted
Added location permissions
Not sure when the issue will arise again but it seems to work for now.
Hey there!! I super appreciate you building this; holy moly. That being said -- are you.... "backporting" things back to LineageOS 14.1 somethow?
The reason I ask is I want to run Android 7.x with the FDroid and Aurora app stores... but also have Magisk for things like force-enabling VoLTE on Sprint as well as messing around with the HSPAP settings on the i9250... and as far as I can tell yours is the ONLY OS that has these.
I know this is a dumb question because the whole point of your OS is for it to be secure. That being said, I'd like to run it on one device and have an insecure second. Or be able to use Magisk. Or something.
IDK I'm rambling. But you rock and are awesome.
DivestOS based on Oreo time? (JKJKJK)
EirikrHinnRauthi said:
Hey there!! I super appreciate you building this; holy moly. That being said -- are you.... "backporting" things back to LineageOS 14.1 somethow?
The reason I ask is I want to run Android 7.x with the FDroid and Aurora app stores... but also have Magisk for things like force-enabling VoLTE on Sprint as well as messing around with the HSPAP settings on the i9250... and as far as I can tell yours is the ONLY OS that has these.
I know this is a dumb question because the whole point of your OS is for it to be secure. That being said, I'd like to run it on one device and have an insecure second. Or be able to use Magisk. Or something.
IDK I'm rambling. But you rock and are awesome.
DivestOS based on Oreo time? (JKJKJK)
Click to expand...
Click to collapse
Nougat not Oreo
DrTrax said:
Nougat not Oreo
Click to expand...
Click to collapse
What is the questions?
SkewedZeppelin said:
What is the questions?
Click to expand...
Click to collapse
User asked way down below whether it's based on Oreo...
Thank you for keeping our beloved nexus alive.
Hi I have read that it does not support gapp, is there any other package that supports it?
Narcoticx said:
Hi I have read that it does not support gapp, is there any other package that supports it?
Click to expand...
Click to collapse
Google Apps are *not* supported.
After CyanogenMod Android v4.4.4 KitKat stopped working, my Galaxy Nexus was restored to the stock JellyBean 4.3 and put away. Then, owing to house painting, I lost track of where it was. Out of sight, followed by 2 years of a hermit existence with only 2 trips away from the house for vaccinations, I have spent most of my time fixing things including roof leaks, car, computer, air conditioners, microwave, I came across my dear old friend and searched for newer custom firmware to revive it. Most ROMs from the active period for Nexus Maguro 5 - 6 years ago were no longer available for download. I had hoped for Marshmallow and would have been happy with Lollipop. Looking at firmware that was available for download, I was surprised to find DivestOS Nougat. Not expecting success, I decided that nothing would be lost but the time to try. I had reoccurring issues with the USB adb drivers and also could not get the divested-14.1-20220214-dos-maguro-recovery.img recovery file to work as required and started again with TWRP. I tried loading Open Gapps nano and SU, but found later that it was not successful. Nevertheless I was surprised that on rebooting after one try, I had DivestOS 14.1 / 7.1.2 Nougat running. Moreover everything worked after first boot, including WiFi, Bluetooth and Camera. The system is clean and fast, but I found no browser and installed Bromite. It's like having a new phone, which is especially pleasing since this phone is the one I had always loved most because of it's lack of bloatware. Thank you so much DivestOS, you made this old man very happy.
I have an old maguro device from my Son. It runs under TWRP Recovery and Lineage 13.0.
I dont know how to setup to yours.
Had I to change the recovery with fastboot like I installed the TWRP ?
And then installing the Rom after Wiping with the new recovery?
Or what else, the informations in this forum and on the DivestOS Homepage are not clear for me.
I have an interest to try this Rom witout Google.
ottomueller said:
I dont know how to setup to yours.
Click to expand...
Click to collapse
The steps are here: https://divestos.org/index.php?page=bootloader#fastboot
I followed these steps except 8 and 11 (not necessary here I guess). In step 12, my maguro will only display the boot animation forever, while getting warm. I waited 30 minutes and repeated, still no luck. Any pointers?
beepmod said:
I followed these steps except 8 and 11 (not necessary here I guess). In step 12, my maguro will only display the boot animation forever, while getting warm. I waited 30 minutes and repeated, still no luck. Any pointers?
Click to expand...
Click to collapse
Assuming you came from another OS, did you format data? And maguro is slow, but 15 minutes is more than enough for its first boot.
Coming from an already wiped Lineage I did wipe data volume again. To be sure after your post, I flashed TWRP and did "Format Data" (which to my knowledge is only needed when removing encryption) and made sure the partition is ext4. After that I followed the instructions from step 6 on: flashing divested recovery, sideloading system and doing a factory reset. Still the same, hangs at boot logo.
Thank you for your answer, I appreciate the help. I don't really need the phone or anything, just wished to try out divestos.
{
"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/hotdog
Downloads :
https://download.lineageos.org/hotdog
GPL compliance :
https://github.com/LineageOS/android_kernel_oneplus_sm8150
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:
Is this rom based on oos 11 or oos 12?
Stiffah said:
Is this rom based on oos 11 or oos 12?
Click to expand...
Click to collapse
OOS12
The perfect gift for January 1st!
Thanks, dear developers.
Little question - Gapps built in?
Can anyone who has installed share ss? And initial impressions?
MRoose said:
The perfect gift for January 1st!
Thanks, dear developers.
Little question - Gapps built in?
Click to expand...
Click to collapse
No gapps
Stiffah said:
Can anyone who has installed share ss? And initial impressions?
Click to expand...
Click to collapse
Upgraded yesterday following the Lineage upgrade instructions. Went without a hitch, all data migrated successfully.
So far it feels smooth and have not encountered any incompatibilities or bugs. The new camera is pretty neat - massive improvement over Camera2. Animations are slightly improved throughout (app switching specifically stands out) and the fingerprint sensor is quick to respond. Theming is also more customizable, which is nice.
Overall I'm happy with the update. Do a backup and give it a whirl!
Max-E-Moose said:
Upgraded yesterday following the Lineage upgrade instructions. Went without a hitch, all data migrated successfully.
So far it feels smooth and have not encountered any incompatibilities or bugs. The new camera is pretty neat - massive improvement over Camera2. Animations are slightly improved throughout (app switching specifically stands out) and the fingerprint sensor is quick to respond. Theming is also more customizable, which is nice.
Overall I'm happy with the update. Do a backup and give it a whirl!
View attachment 5799679View attachment 5799683View attachment 5799693
Click to expand...
Click to collapse
What backup method you recommend? Havent had any luck last time with the old school ones.
The old school ones!
Code:
adb pull "/sdcard"
and
Code:
adb backup -apk -shared -all
Most data is synced/stored off of my phone so there's not a lot to lose if the worst happens and the thing needs to be nuked.
Max-E-Moose said:
The old school ones!
Code:
adb pull "/sdcard"
and
Code:
adb backup -apk -shared -all
Most data is synced/stored off of my phone so there's not a lot to lose if the worst happens and the thing needs to be nuked.
Click to expand...
Click to collapse
Thank you, meanwhile I was too curious and flashed it and I got one question. Can CTS Safetynet be passed? One of my banking apps refuses to work now and on my previous ROM everything worked perfectly.
You'll need to install Magisk to pass Safetynet.
Max-E-Moose said:
The old school ones!
Code:
adb pull "/sdcard"
and
Code:
adb backup -apk -shared -all
Most data is synced/stored off of my phone so there's not a lot to lose if the worst happens and the thing needs to be nuked.
Click to expand...
Click to collapse
What the heck ! I never know about that method ! Thanks really it will help me !
I installed the rom this morning, all working except the fingerprint scanner.
Do you know how to resolve the problem ? Do I need to reinstall ? Thanks !
I hear LOS20 has a new LoS camera.. can anyone tell me how is it?
Does it do justice to all the lenses?
MRoose said:
Which GApps recommend?
Click to expand...
Click to collapse
Ones in the instructions...
Has anyone been able to successfully run banking apps and wallet apps on this with Magisk? I'd like to know as I've had to stop running root due to banking apps. If you have, could you please tell me the sequence of steps you took? Everytime I root in the past, even using Zygisk and hiding the magisk manager, after a certain amount of time the apps would find root and stop working.
REQUEST:
Can someone please upload the Camera app apk with its default profile XML?
[email protected] said:
Has anyone been able to successfully run banking apps and wallet apps on this with Magisk? I'd like to know as I've had to stop running root due to banking apps. If you have, could you please tell me the sequence of steps you took? Everytime I root in the past, even using Zygisk and hiding the magisk manager, after a certain amount of time the apps would find root and stop working.
Click to expand...
Click to collapse
I have banking apps running inside shelter sandbox (work profile) and have Magisk installed with the normal hiding options in the main profile. No problems so far.
Thanks, upgraded. At a first glance it works well though I will test further.
Preserved Widevine L1.
Since I have been reading about problems with Widevine reverting to L3 during oem unlock on OOS 12 I migrated straight from LOS 18/ Android 11.
If anyone needs to repeat the steps for widevine:
I had unlocked on OOS11 EU ROM preserving Windevine L1 and installed one of the last builds of LineageOS 18.1 - now Installing is no longer relevant so we can directly move to updating firmware.
Then I downloaded and updated using the instructions in the device page https://wiki.lineageos.org/devices/hotdog/fw_update
At first the recovery fastboot option was not working for me so I updated platform-tools to the last version and installed the USB Driver (probably it was the culprit as previously it was showing as HD1917 and now it's HD1911 - this can be an issue if you only had your drivers installed for a different "model"), booted a recent recovery and did the rest of the actions from the advanced fastboot setting in the recovery.
Flashed latest nightly, recovery, rebooted, flashed gapps and the new patched magisk boot image and everthing is still working fine ... actually it seems to work better now.
A big thanks to LuK1337 and the LOS team!
On the banking apps topic - in the long run It's a lost cause I think. Only one of my banking apps doesn't work though and 3 others work fine with hiding. The weird thing is all sorts of apps complain about the modified OS - even apps for ordering pizza, etc. I really don't get why they would be interested if my phone is modified or not.
The only minor issue in upgrading is that device showed my phone as not secure so I had to remove my work profile and add it once more.
The other upgrade changes like having to reenable magisk modules and similar are expected.
The way I got all my banking apps and Google Pay to work is as follows:
-Magiskhide Props Config to Nexus 6P
-Hide Magisk Manager
-Zygisk every bank app+google play services
-Universal SafetyNet Fix mod by Displax
It was a chore but seems to work for now.
By the way battery life really tanked, especially while idle.
{
"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/lemonadep
Downloads :
https://download.lineageos.org/lemonadep
GPL compliance :
https://github.com/LineageOS/android_kernel_oneplus_sm8350
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 you for this!!
Is vendor firmware included in build or do i need to flash it separately? @LuK1337
EugenStanis said:
Is vendor firmware included in build or do i need to flash it separately? @LuK1337
Click to expand...
Click to collapse
Same as 19.1.
Nice New Years present, thanks! Just sideloaded it without any hiccups whatsoever and it seems to work perfectly. (Just be patient when it is 47% finished, it takes some time.)
So just to confirm, if I'm on 19.1, I should be able to just sideload lineage 20/gapps/magisk, and I'm good? Don't have to wipe my data, or worse, revert to stock and upgrade stock to whatever their latest version is (I assume an update from android 12 to 13)?
Still going to use Swift Backup to backup as much of my stuff as I can, just in case. Hopefully I won't need it.
Zhono said:
So just to confirm, if I'm on 19.1, I should be able to just sideload lineage 20/gapps/magisk, and I'm good? Don't have to wipe my data, or worse, revert to stock and upgrade stock to whatever their latest version is (I assume an update from android 12 to 13)
Click to expand...
Click to collapse
Correct. Very smooth upgrade experience without loosing any data on my device.
Can I flash this over latest OOS 13 ? Does it already have firmware. Please don't tell me it is same as LOS 19 because I don't know about LOS 19 instructions.
ElitePotato said:
Can I flash this over latest OOS 13 ? Does it already have firmware. Please don't tell me it is same as LOS 19 because I don't know about LOS 19 instructions.
Click to expand...
Click to collapse
no.
how can i activate the wifi icon ?
i see instead a dot icon
thx
AOD seems a little wonky on Lineage 20 with the full size double-line clock... Like it's offset too low on the screen, so it overlaps with the battery percentage overlay.
Also some apps like FX File Explorer aren't allowed to enable notifications (even though I had never disabled them in 19.1).
Haven't figured out any workarounds yet.
Edit: I've disabled double-line clock for now until the AOD offset gets fixed.
And turns out the disabled notifications issue is an Android 13 issue which some apps are afflicted with, but it can be fixed on the app side, per this MalwareBytes forum thread: https://forums.malwarebytes.com/topic/290668-android-13-blocking-notifications/
someone the same bug with the icons in the status bar ?
osm0sis said:
Edit: I've disabled double-line clock for now until the AOD offset gets fixed.
Click to expand...
Click to collapse
how can i disable double line clock ?
thx
xerves78 said:
someone the same bug with the icons in the status bar ?
View attachment 5799809
Click to expand...
Click to collapse
I've got same problem
xerves78 said:
how can i disable double line clock ?
thx
Click to expand...
Click to collapse
Settings > Display > Lock screen > Double-line clock.
LuK1337 said:
Same as 19.1.
Click to expand...
Click to collapse
Any plans to upgrade Los 20 to oos13 firmware? Or just when los21 will be released?
Is there a reason why devs stay with a12 firmware? Thanks for your work on all op devices.
pxrave said:
Any plans to upgrade Los 20 to oos13 firmware? Or just when los21 will be released?
Is there a reason why devs stay with a12 firmware? Thanks for your work on all op devices.
Click to expand...
Click to collapse
Eventually.
MJPollard said:
Settings > Display > Lock screen > Double-line clock.
Click to expand...
Click to collapse
thx
Cool! How is Magisk working on the latest Android?
Anyone know why you can't sideload Magisk in recovery or even use twrp to install it? It freezes and does nothing? I patched the boot which is a alternative but it's longer that way.