[ROM][UNOFFICIAL][A11][F500,LS991,H81x,US991,VS986] LineageOS 18.1 - G4 Android Development

{
"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:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
About LineageOS:
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. 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.
​**** These builds are for both: official unlocked and UsU'd devices **** ​UsU? http://bit.do/unlockg4​
Requirements
Your device need to be unlocked either officially (h815 international or h811) or by UsU
Your bootloader stack should be on MM 20p (20x for H811) or higher! (see FAQ #8 for how to upgrade your bootloader stack witbout lgup).
.... and for your convenience I have alternatively created TWRP flashable files for that !!!! (click)
in particular that means this thread is for:
F500 (UsU'd), H810 (UsU'd), H811, H812 (UsU'd), H815 (official unlocked or UsU'd), H819 (UsU'd), LS991 (UsU'd), US991 (UsU'd), VS986 (UsU'd)
Latest SHRP build: click
or latest TWRP - PREVIEW build: click
Do a full Nandroid backup before doing anything else!
Installation
This single very first step is for UsU'd devices only:
If you have ever flashed the UsU baseband package: Clean flash the modem partition from your backup in TWRP.
If you do not know if you ever flashed it simply flash your modem partition again and you can be sure. This can't do any harm.
If you have no backup: TWRP flashable MM modems (N might not work)
Full clean install as described here (FAQ "#2") is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash this ROM
Optional (f-droid is already included): Flash GApps (11.0 - ARM64) if you like to use google apps
Optional (if you want root): Flash Magisk
Boot (will take a bit on first boot!!! but no longer then a few minutes)
Enjoy
Features
Pure LineageOS ROM experience
F-Droid included (Open Source alternative to Google Play)
Like with all my builds: OTA support included
Known issues:
Keep in mind that this is brand new stuff so it may (still) contain unknown issues! So back up regularly and frequently!
Check the current issues at the github tracker (feel free to help, provide logs etc!)
If you find a bug not listed, follow the instructions here and provide me with the logs: FAQ #1
Download
Get your builds from my leech server: https://leech.binbash.rocks:8008/lineage/18.1
Note:
Builds are updated as soon as possible. There is no build cycle. I build when I build (usually when a new security patch has been released at least).
Information pertaining to your device is displayed accordingly.
Changelogs
see commits at github or ideally you join my matrix or telegram groups (see topic "Support")
Credits
LineageOS
aoleary (for the whole a11 bringup!)
DevUt (for nothing)
and more..
Sources
build manifest
Support
Post in this thread
Quick support by [Matrix] || build notification by [Matrix]
Quick support by Telegram: sfX_Android || build notification in sfX_ci

Frequently Asked Questions (FAQ)
Q #01: I want to report an issue. What is the proper way to do so?
I'm glad that you are asking: before doing so check the KNOWN ISSUES topic in the OP and ofc the other FAQ's listed here!
If you encountered a kernel panic follow FAQ #6 in this post instead.
If you have issues with "just" the boot process follow FAQ #7 for a very easy way to grab the boot logs.
if you have an audio issue follow FAQ #10 instead.
If your issue is not listed there click here to proceed:
If your issue is not listed there follow the directions here briefly and I may can fix it.
Often selinux can cause issues so try that at very first:
Code:
adb shell
su
(or "adb root" when enabled in developer settings)
setenforce permissive
Try again and if the issue is gone when in permissive mode: provide me a logcat as described here -> on step 3 I need the SELINUX log (option D)
If that does not solve your issue follow the logcat GUIDE to provide a valid log depending on what your issue is.
Ensure you have done a full CLEAN install before doing so (refer to FAQ #2 for what that means).
Warning: LIMITED to NO SUPPORT when:
- magisk is installed (known to cause issues sometimes - regardless of the ROM or version)
- Xposed is installed (known to cause issues sometimes - regardless of the ROM or version)
If you have installed any of these UNINSTALL or better do a FULL CLEAN install (see FAQ #2) before doing anything else. Often enough these above causes several issues like battery draining, problems on booting and much more. Even when they may work properly you should re-produce your issue without them first and follow the above to grab the log.
Magisk is a great piece of software and besides that it is Open Source which SuperSu never was.
I just saying I do not "support" issues with LOS when you have Magisk installed. Why? It is (like Xposed) extendable with modules (made by whoever) and those can cause billions of issues.
Other then that magisk was sometimes the reason for battery drain etc. Magisk modifies the boot "process" and sits very deep in the system (which is needed to make it work ofc) but that has the potential to make a system/ROM unstable or result in strange behaviors.
so in order to support a specific issue I have to be sure the ROM is in a "clean" state, no magisk, no xposed.
Q #02: I want to install clean, how? What is a clean install? What is the recommended way to flash a new ROM version?
A clean install ensures that there are no leftovers from any previous install. One can say that there are 2 phases of a clean flash:
1) regular
2) full - when you (still) encounter issues
Usually the regular one is fully ok when flashing a new ROM version but if you encounter strange issues nobody else is reporting or if a release post is recommending it you should do a full clean install instead.
A regular clean install can be done like this:
WIPE -> Advanced -> select: System + Cache
Flash the ROM
reflash root addon/magisk if you want root
reflash opengapps if you want to use Google crap
A full clean install needs 2 steps more then the regular:
follow the steps for regular clean
go back in WIPE -> touch the "FORMAT data" button and type "yes" to format the internal storage (you will LOOSE ALL YOUR DATA - obviously)
REBOOT -> Recovery
Flash the ROM
reflash root addon/magisk if you want root
reflash opengapps if you want to use Google crap
It is absolutely recommended to create a backup before and COPYING IT to your PC(!) before doing the above.
Q #03: Are there any plans or a chance of official LOS builds?
TL;DR answer is: no. Background: see FAQ 3 of the LOS 17.1 thread
Q #04: Google Play shows that my device is not "certified" - how can I fix that?
There is a lot of discussion around that. Search by google but the TL;DR is it will be likely not possible anymore these days.
Q #05: It looks like the CPU cores 5 and 6 are disabled - how can I fix that?
TLDR;
There is no fix required! it is fully ok when those are idle. they get hot plugged whenever needed.
Details:
we have 2 clusters of CPU cores resulting in a Hexa-core CPU set: (4x1.4 GHz Cortex-A53 & 2x1.8 GHz Cortex-A57)
the big one (2 CPU cores - higher performance = more battery drain, more heat which potentially causing the: bootloop issue) and the little (4 CPU cores - less battery drain but a bit slower) are handled dynamically based on the load of your device.
the big cluster will run ONLY when it is NEEDED - i.e. high load.
so when you look closer: those are not DISABLED they are IDLE which is a big difference.
Q #06: I get a kernel panic or green/purple/blue screen how to grab logs for this?
If you encounter a kernel panic and you are able to reboot without taking out the battery (taking out the battery will erase RAM):
1. reboot (without taking out the battery!) to either TWRP or (if you have root access) to your ROM
2. grab everything need from here: /sys/fs/pstore/: adb pull /sys/fs/pstore/
If you don't have a pc nearby you can do it directly from the device as well (requires root!):
Enable the terminal app in developer options or download any other.
Open the terminal app.
Bash:
su
cd /sdcard/Download
tar czf pstore.tgz /sys/fs/pstore
Now share the pstore.tgz directly from the device or next time when you have access to a PC you can grab it like this
adb pull /sdcard/Download/pstore.tgz
Attach pstore.tgz to your post.
It is crucial important that you do this only after the reboot happened . It's not important "when" though - as long as the device never was powered off.
Developers note:
convert PMSG log (requires a linux system):
Code:
tr -cd '\11\12\15\40-\176' < pmsg-ramoops-0 | sed 's/TENS\s/\n/g' > readable-pmsg.txt
Q #07a: How can I provide a boot log?
Q #07b: I get a kernel panic on boot or having other boot issues but the pstore log are empty! What should I do?
Since a while there is a very easy way to provide debug logs for the boot process. Before my convenient logging you had to follow FAQ #1 to grab them and it was a bit of PITA for some users.
So here you go for a much easier way:
boot Android
once booted : reboot to TWRP
when you have a bootloop instead: take the battery out just before the bootloop occurs, or better press the key combo to get into TWRP all the time to eventually get there directly
once in TWRP ensure that "Cache" is mounted in the "Mount" menu (if not mount it by ticking the box)
open a terminal on your PC and type:
Code:
adb pull /cache/debug/boot_lc_crash.txt
adb pull /cache/debug/boot_lc_full.txt
adb pull /cache/debug/boot_lc_kernel.txt
paste one by one to a paste service like https://del.dog/ , https://paste.systemli.org/ or https://paste.omnirom.org/
Q #8: upgrade your bootloader stack only?!
see FAQ 8 of the LOS 17.1 thread
Q #9: The ROM is lagging and/or the device gets very hot/warm, what can I do to help fixing that?
Ensure you read and understand about the ILAPO first.
If you encounter any overheat or lagging issues follow this:
Code:
adb shell
logcat -b all -d | egrep -i "thermal|kill" > /sdcard/Download/log.txt
ps -A >> /sdcard/Download/log.txt
free -m >> /sdcard/Download/log.txt
logcat -b crash -d >> /sdcard/Download/log.txt
exit
adb pull /sdcard/Download/log.txt
Share the log.txt as an attachment of your reply (bc txt is fine for that) or - as usual - by your favorite paste service
Q #10: issues with audio (e.g. echo's, silence on one or the other site, ..)? Read here how to provide a specific log for that:
Do the following steps:
1) Ensure you have adb set up on your PC, and have adb debugging and adb root enabled in developer options on your phone
2) Then perform the following (all one command)
On Linux:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver" && sleep 10 && adb logcat -b all |egrep -vi "(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)"
Click to expand...
Click to collapse
On windows:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver && sleep 10 && logcat -b all |egrep -vi '(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)' "
Click to expand...
Click to collapse
3) Then re-produce your audo issue and cancel the logcat from step 2 before hanging up!
4) Share the logcat output from the console screen using any paste service like paste.omnirom.org (ensure you always set a life time of several months at least!)

reserved - not sure for what

hello! I just flash it (18.1-22020511) , nice rom (my device h815)
but I found that Apps can't get location ( like Google map ) I trun on all location right for app ,but it just can't work
Please check it
thank you!!

for note! Don't flash the newest open-gapps
I flash the open-gapps-20220503 , it will make system just crash ,can not boot
But use the last release version 20020215 it works well !

atlus666 said:
hello! I just flash it (18.1-22020511) , nice rom (my device h815)
but I found that Apps can't get location ( like Google map ) I trun on all location right for app ,but it just can't work
Please check it
thank you!!
Click to expand...
Click to collapse
hi, well I can confirm GPS works fine here on my H815 and also 2 other ppl reporting that GPS just works fine. Consider a FULL clean flash (see FAQ #2 above) and try again.

hi ! I wipe system,DAV cache ,data ,cache & reflash , it works!!
Thank you!!

Cant believe people ported android 11 to a 7 year old device 0_0

This is interesting. Couple things, I see in another thread that it is a known issue that there are no bars/data for cellphone signal quality. Not really a problem since it does have signal.
I'm curious about led notifications though. I can't seem to get it to be a blinking dot. Solid dot only. I set the colour to a different custom colour so I know I am changing it and thus in the right settings area, but changing solid to flashing at different speeds and such does not seem to make it flash.

I have a problem:
Auto-rotate not working on Lineage 18.1​/device h815
I have installed it on h815 (usu) I try to flash Lineageos 17.1 and the auto-rotate work fine there but on 18.1 can't manage to make it work.
I have tried this line of code but not work:
Root your device
Run these commands:
adb shell
su
restorecon -RF /persist
restorecon -RF /mnt/vendor/persist one of the restorecon commands may fail but it is ok.
Reboot your device.
please Help

ismystore said:
I have a problem:
Auto-rotate not working on Lineage 18.1​/device h815
I have installed it on h815 (usu) I try to flash Lineageos 17.1 and the auto-rotate work fine there but on 18.1 can't manage to make it work.
Click to expand...
Click to collapse
For what it is worth, can confirm that auto-rotate works on my h815 official unlock. Out of curiosity if you open an app and then try to rotate the screen with auto-rotate _disabled_ in drop down, do you get the symbol appear in the bottom right corner telling you auto-rotate is disabled?

llarr said:
For what it is worth, can confirm that auto-rotate works on my h815 official unlock. Out of curiosity if you open an app and then try to rotate the screen with auto-rotate _disabled_ in drop down, do you get the symbol appear in the bottom right corner telling you auto-rotate is disabled?
Click to expand...
Click to collapse
no, as the sensor not working, if I rotate the device, he doesn't know I am rotating him. so no symbol appears.
and yes auto-rotate works on my h815 - not official unlock (USU)

ismystore said:
and yes auto-rotate works on my h815 - not official unlock (USU)
Click to expand...
Click to collapse
I was just confirming that auto-rotate works for me on this here L18.1 on my h815.

I can confirm that auto-rotate is not working for me too..
in 2 phones h811... full clean flash
is look like the dirver for gyroscope or accelerometer are not working..... if you reboot the phone in fly mode... disable nfc bluetooth and rotate .. reboot the phone sometime 1 reboot work.. others 2 reboot... and when the phone start enable rotate... and will work..

llarr said:
I can confirm that auto-rotate is not working for me too..
drasterlx said:
in 2 phones h811... full clean flash
is look like the dirver for gyroscope or accelerometer are not working..... if you reboot the phone in fly mode... disable nfc bluetooth and rotate .. reboot the phone sometime 1 reboot work.. others 2 reboot... and when the phone start enable rotate... and will work..
Click to expand...
Click to collapse
-rotate works for me on this here L18.1 on my h815.
Click to expand...
Click to collapse
I have flash Xtended-XR (android 11) and rotating is now working.

llarr said:
This is interesting. Couple things, I see in another thread that it is a known issue that there are no bars/data for cellphone signal quality. Not really a problem since it does have signal.
I'm curious about led notifications though. I can't seem to get it to be a blinking dot. Solid dot only. I set the colour to a different custom colour so I know I am changing it and thus in the right settings area, but changing solid to flashing at different speeds and such does not seem to make it flash.
Click to expand...
Click to collapse
Signal bars should have been fixed . At least it was confirmed by 3 ppl and myself. Did you a FULL clean flash?? See faq how.
ismystore said:
I have a problem:
Auto-rotate not working on Lineage 18.1​/device h815
I have installed it on h815 (usu) I try to flash Lineageos 17.1 and the auto-rotate work fine there but on 18.1 can't manage to make it work.
I have tried this line of code but not work:
Root your device
Run these commands:
adb shell
su
restorecon -RF /persist
restorecon -RF /mnt/vendor/persist one of the restorecon commands may fail but it is ok.
Reboot your device.
please Help
Click to expand...
Click to collapse
Yes auto rotate does not work for some while it works for others. Still trying to find the reason for that. Seems to be a LOS specific issue though.

myphoneisweirdlol said:
Cant believe people ported android 11 to a 7 year old device 0_0
Click to expand...
Click to collapse
Yea and all that for 2 thanks clickz lol..

steadfasterX said:
Signal bars should have been fixed . At least it was confirmed by 3 ppl and myself. Did you a FULL clean flash?? See faq how.
Click to expand...
Click to collapse
Hmmm, yes I did a full clean flash. I also flashed h815_20p_bootloader_20p_modem_TWRP-flashable.zip from your leech server using twrp 3.5.2_9_prev275 for both, with reboot to twrp between. I thought that I was already on that bootloader but I figured it couldn't hurt to make sure.
It seems I can get bars/connection data if I change mobile network > preferred network type > from 4G (recommended) to 3G but it doesn't stick when reverting back.

llarr said:
Hmmm, yes I did a full clean flash. I also flashed h815_20p_bootloader_20p_modem_TWRP-flashable.zip from your leech server using twrp 3.5.2_9_prev275 for both, with reboot to twrp between. I thought that I was already on that bootloader but I figured it couldn't hurt to make sure.
It seems I can get bars/connection data if I change mobile network > preferred network type > from 4G (recommended) to 3G but it doesn't stick when reverting back.
Click to expand...
Click to collapse
Yea that's exactly the same behavior then from before the fix. Will look into that again but might be hard as i cannot reproduce that here anymore.

steadfasterX said:
Signal bars should have been fixed . At least it was confirmed by 3 ppl and myself. Did you a FULL clean flash?? See faq how.
Yes auto rotate does not work for some while it works for others. Still trying to find the reason for that. Seems to be a LOS specific issue though.
Click to expand...
Click to collapse
I hope this will e fixed soon

Related

[EXPERIMENTAL][AOSP][NRD90U] Unofficial Android 7.0 Nougat build

Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Hello guys, this is an unofficial build of AOSP Nougat (with tag android-7.0.0_r6). Kernel is based on CM13's, with some recent commits in kernel/common in AOSP. Sources and patches are available at the end of the post.
Note: this ROM is just for having the first taste of Nougat, and thus missing a lot of key features. I may not be able to update it regularly.
Basic hardware functionality:
Almost everything works, except video hardware encoding, which causes camcorder to fail. HW decoding works though.
Everything should be working since 20160903.
I didn't find more hardware failures, but there can be more.
And remember, the proprietary firmwares and blobs are still in the age of Marshmallow, and a system won't be complete without corresponding firmwares and blobs.
Known bugs:
1. HW disk encryption is likely broken. I reverted some commits to make cryptfs_hw build, but I'm not sure if that works. Do not try it.
2. SELinux is permissive, and init allows service without a SELinux domain to start.
3. GPS may take longer to obtain a position fix. (yes it's working... sorry for the misunderstanding)
4. Only Launcher2 is included. You may install a new one as you like.
5. No LiveDisplay and gestures except DT2W (DT2W can not be turned off via Settings app for now) Color calibration is possible, see FAQ below.
6. Default input method could be broken. Be ready to "pm install your_ime.apk" in adb shell. Fixed in 20160828
7. com.qti.dpmserviceapp may produce continous FC. You can disable it via adb shell ("su -c pm disable com.qti.dpmserviceapp"). Removed in 20160828
8. Rotating screen while playing video can cause the display to "split" Fixed in 20160903
9. Camera service and media codecs all run in the same process, eliminating one of the security enhancements of Android N. May not be fixed until new HAL and blobs are available.
So the security improvements in Nougat are not making much difference in this only-a-taste ROM. If you rely on this, it would be better to wait for official releases.
FAQs:
1. Root / Gapps?
I'm using SuperSU 2.76 stable and OpenGapps 7.0 pico. They work without any issue.
If your contacts / calendars is not syncing, try the following steps:
1. Goto Settings > Apps, tap "Show system" in menu
2. Find "Google Contacts Sync", tap on it, tap "Permissions", turn on everything
3. Go back to Detail screen, clear its data
4. Go back to app list, clear "Contacts Storage"' data
5. Do the same for calendars (2-4)
6. Reboot
Click to expand...
Click to collapse
2. F2FS?
I did not test this myself... But kernel has support already (of cource, it's from CM) so you may have a try. Remember to backup!
EDIT: Some users reported that F2FS partitions are corrupted. If you are using F2FS, maybe you should wait.
Click to expand...
Click to collapse
3. Menu key / App switcher?
Menu key now acts as recents, since I don't think the former is as useful as the latter. And there is no more lag while tapping home button since we don't check for double tap anymore.
Click to expand...
Click to collapse
4. TWRP shows error?
If that's two lines of "log", you can safely ignore it.
If there is something else, please stop and post it here.
If you are using MultiROM, you may modify update-script. Read the first ~8 pages and you will find it.
Reference: I'm using official TWRP 3.0.2 w/o MultiROM This recovery didn't get replaced by stock one...
Click to expand...
Click to collapse
5. File manager (to install APKs)?
http://forum.xda-developers.com/showpost.php?p=68402423&postcount=73
Click to expand...
Click to collapse
6. Disable HW keys, enable soft keys, screen color calibration?
Disable HW keys: echo 0 > /proc/touchpanel/keypad_enable (needs repeat on reboot)
Enable soft keys: echo "qemu.hw.mainkeys=0 >> /system/build.prop (once)
Screen color calibration: echo "32768 31784 27852" > /sys/class/graphics/fb0/rgb (needs repeat on reboot, change the values as you need. This example is 100% R, 97% G, 85% B)
Optionally you can enable color enhancing: echo 1 > /sys/class/graphics/fb0/color_enhance
Click to expand...
Click to collapse
Screenshot spoiler
{
"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"
}
Flashing Guide by @The Dork Knight Rises
In the 3rd post. Direct link: http://forum.xda-developers.com/showpost.php?p=68397804&postcount=3
Video hands-on by @savadam
https://www.youtube.com/watch?v=r54vWk-Azh8
Thanks for all your support!
Download:
20160919: Mirror 1: https://drive.google.com/open?id=0BwkmhbR5VHpAYWRKd1owSUNudEU Mirror 2: https://mega.nz/#!fEk1CTyJ!F8rdnqT_oiipP-tHCuzFGFvsQGmUV6LRaD2t81N2WIA
You can still use HALs from 20160906 if you want.
(And if you are posting this somewhere else, please include the HALs in your post)
Older versions:
20160918: Mirror 1: https://drive.google.com/open?id=0BwkmhbR5VHpAMWZ4OEx6Unp5bU0 Mirror 2: https://mega.nz/#!rdlkgboI!LQuFDtcppbizC_7Tfww1uWAmhw-lYuxjAlrhg9Z0tuQ
20160910: Mirror 1: https://drive.google.com/open?id=0BwkmhbR5VHpAdGVTV3V0ekZaWHM Mirror 2: https://mega.nz/#!XEsTESpR!QDa7he2jdPCeIsbMY1vJAlCZ0RokAKV0IdtyuB0R-yc
20160906: Mirror 1: https://drive.google.com/open?id=0BwkmhbR5VHpAWHNFb0xyYlBZM3c Mirror 2: https://mega.nz/#!zBVX1DTZ!S-LnpIEgJqn1r7So6QmEoD_APUqDnp93XbP-Ug__XBk
CAF and original AOSP HALs: https://drive.google.com/open?id=0BwkmhbR5VHpAaGdCQmxDUWgxQlU
Note on the HALs:
AOSP HALs (msm8996 display + msm8974 media) can not record screen, but they "seem" to make the system smoother. (msm8974 display HAL cannot be used because it corrupts the display when rotating screen with video playing)
CAF HALs (both based on vanilla CAF LA.BF.1.1.3_rb1.13) can record screen but "seem" not to be so efficient as AOSP ones.
The HAL included in the ROM are the AOSP variant.
20160903: Mirror 1: https://drive.google.com/open?id=0BwkmhbR5VHpATlN5T29WTS01Qkk Mirror 2: https://mega.nz/#!OcFlTDDK!EYiNpfE-9Pxx2wu4Oto7kO_oevfe0bMkXOTdhP1HDZc
20160831: Mirror 1: https://drive.google.com/open?id=0BwkmhbR5VHpAVE1WR2xYd180MzA Mirror 2: https://mega.nz/#!jE92iSAD!pl0NMU6PPY3UNXE5DTDBKLUd4sFLG6fNTaUUMI0xdzg
20160828: Mirror 1: https://mega.nz/#!XdlXFDBQ!p7E0N64IEkGHn4GBzOZQDTCgR4KdD00O0dRwJlEnvcw Mirror 2: https://drive.google.com/open?id=0BwkmhbR5VHpAczA2T2g0RUZRS3c
20160827: https://drive.google.com/open?id=0BwkmhbR5VHpAUVdWUHNlc0lHZWs
Note: please read "known bugs" section before flashing! Also you can read the guide below.
When updating the ROM, just dirty-flash new build and Gapps (if you use them).
In order to prevent your recovery from being replaced by the stock one, flash SuperSU along with the ROM.
Sources:
Kernel: https://github.com/updateing/android_kernel_oneplus_msm8974/tree/nougat
Device: https://github.com/updateing/android_device_oneplus_bacon/tree/nougat
Build system: https://github.com/updateing/platform_build/tree/custom-kernel
And there are a lot more repos I didn't fork. The changes there as well as local_manifest are here:
20160918+ Check GitHub
20160910 https://drive.google.com/open?id=0BwkmhbR5VHpAcmo1RjhPd0N1c3c
20160906 No new patches except the HALs. For AOSP HALs, check previous patch archive and Sony's guide. For CAF HALs, just cherry-pick "Fix clang build" from CM.
20160903 https://drive.google.com/open?id=0BwkmhbR5VHpAQXFqZEJCT21UNDA
20160831 https://drive.google.com/open?id=0BwkmhbR5VHpASW54QnR4eGFlR1E
20160828 https://drive.google.com/open?id=0BwkmhbR5VHpAOEx2OWNYcE1xU2s
20160827 https://drive.google.com/open?id=0BwkmhbR5VHpALXdkNkptRnBLMkU
Changelog:
20160919
Fixed Fackbook crash by avoiding preloading libboringssl-compat.so (CM camera HAL is the only camera HAL that does not require this)
Updated BT configuration (please test if it has any side effect. Sometimes you need to search twice to find your Bluetooth gadgets.)
Tried to fix network location (added Google's network location provider)
20160918
Reverted to previous "stub" power HAL. May fix lagging and unusual power consumption noticed by some users.
Tried to fix NFC FW download mechanism. May fix non-working NFC for some users.
20160910
Updated to NRD90U (android-7.0.0_r6)
Switched to CM/QCOM power HAL. The original power HAL is more like a placeholder.
Now on Tap can be launched by long-pressing home button
Switchable WebView implementation, thanks to @fards here
Note:
1. If you are experiencing display issues (such as screen flicker with FLV SW decoding), try switching on "Disable HW Overlay" in Development Settings.
2. If you need multi-user feature, remove /system/priv-app/com.qualcomm.location. Otherwise the system will crash. It was accidentally added in this build.
20160906
Switched back to AOSP HALs to increase performance, but screen recording is broken again. You can choose CAF HALs listed above to fix that. Camcorder and HW encoding work with both variants, no need to worry.
Updated media profiles. Front camera knows that it is not capable of 1080p recording.
20160903
Fixed HW encoder and camcorder (they are different issues, though related) (and switched to CM13 media HAL)
Fixed display corruption while rotating screen with video playing (by switching to CM13 display HAL, don't know which lines of code fixed that)
DT2W can be turned off via Settings
Added Reboot option in power menu
20160831
Fixed crash in World Clock page when selecting countries/regions
Fixed hang in Developer Settings when the ROM is installed as secondary
Fixed crash when taking photos with HDR on
Added support for kexec
Added Stk
20160828
Fixed default input method FC
Remove com.qti.dpmservices to prevent FC
Dev: updated build system to finally automate everything
20160827
Initial build
Click to expand...
Click to collapse
Notes on the sources:
1. Build system produces correct boot.img in $OUT, but the boot image in OTA zip still has no DT included. Fixed in 20160828
2. Some fixes are really "dirty" (as I'm not able to find a proper way)...
3. Some JNIs fail to build (lots of C++ symbols no found). You may try linking C++ libs dynamically (c++_static -> c++_shared) to avoid this. See 20160828 patches, packages/inputmethods/LatinIME for example.
4. Some apps require android-8 ndk, but the earliest version in the tree is android-9. A symlink will do (or you can change the Android.mk in app) but I'm not really sure this will not introduce any bug.
5. Android N split mediaserver into multiple processes to improve security, such as cameraserver, mediacodec, etc. But camera blobs and old HALs were not designed like this. They assume they run in the same process, thus a buffer created by blobs are being used everywhere, which will cause illegal memory access under Android N. I reverted lots of patches about this, forcing camera and codec services to run in the mediaserver process as before - security compromised with functionality, again.
Hope you enjoy this.
I am going to try this out, thanks @updateing for your work:good:
If I could find fixes then I would send an pull request.
The All-In-One Post
Oh look at the time...it's flashy time already? XD
Screenshots:
(Layers themes work. Use Substratum app)
Guide to flashing this properly (TWRP v3.0.2-0):
(THIS GUIDE IS MAINLY FOR THE FIRST BUILD 20160827. AS I AM RUNNING IT SMOOTHLY, I DO NOT PLAN TO UPDATE TO 20160828, AS IT HAS SOME MINOR FIXES, ALREADY COVERED IN MY GUIDE.
IF HOWEVER, YOU'RE FLASHING 20160828 OR LATER BUILD, HERE'S WHAT YOU SHOULD DO DIFFERENTLY:
-Flashing Google keyboard is not mandatory, as default input mode has been fixed
-adb steps do not need to be performed as the com.qti.dpmserviceapp has been removed
-You probably shouldn't flash the SystemUI Tuner mod zip, as the SystemUI APK from previous build may not be compatible with new build. If you flash it on 28 build and have SystemUI FCs or missing SystemUI, just reflash ROM, and don't flash the mod.
REST OF THE GUIDE REMAINS THE SAME)
(This guide is for flashing as primary ROM without MultiROM. MultiROM guide by @7u5h4r: http://forum.xda-developers.com/showpost.php?p=68413163&postcount=242)
TL;DR version (that means short version)
http://forum.xda-developers.com/showpost.php?p=68552389&postcount=1172
Download ROM zip from OP and Google Keyboard flashable zip, as well as any of the zips I linked below.
Wipe your device (data, cache, dalvik/ART cache; preferably even system, just to be as "clean" as possible)
(NOTE ABOUT DIRTY FLASHING:
-If you dirty flash this ROM (eg. flashing newer build), you will need to flash GApps again along with the ROM zip as GApps are not preserved
-This ROM actually booted for me even on a dirty flash from an MM custom ROM, and as a result I didn't face a lot of the problems you'd face on clean flash (GApps crashes, continuous qti app FCs, etc)
But a lot of my apps were crashing until I reinstalled them, and in any case, it is not advised to dirty flash when coming from MM)
Flash ROM zip and keyboard zip, optionally any of the following addons (DO NOT FLASH GAPPS YET):
-SuperSU (v2.68+) for root
-Any of the mods I linked below
-Any other mods like Viper4Android etc (AT YOUR OWN RISK)
Boot into the ROM. you'll probably see a lot of crashes, ignore them, and just find a PC for the next step
(Optionally, you could try to enable Developer Options by tapping past the FC dialogs, once you have DevOps enabled, you'll see an option to mute FC notifications till next boot)
Using ADB on your PC, disable the com.qti.dpmserviceapp package by running following commands:
Code:
adb devices
You should see a device in the list of devices connected
Code:
adb shell
pm disable com.qti.dpmserviceapp
If you get error with permissions, you may need root. If your device is rooted:
Code:
su
pm disable com.qti.dpmserviceapp
(SKIP 6, 7 & 8 if you do not need Google services)
Now reboot into recovery and flash a compatible GApps package (USE 7.0 GAPPS ONLY)
Boot into ROM
Go to Settings>Apps
Find Google Play Services, and go to its Permissions. Enable essential permissions. Now Play Services won't keep crashing on you. Also find Google Contact Sync and give it permission to access Contacts.
Go to Settings>Accounts and add your Google account
Profit
Praise DuARTe
Hit Thanks if this helped
Here's some helpful zips for you guys!
My flashable zip to ENABLE Navbar/softkeys (same as the one on the MM thread) https://drive.google.com/open?id=0B2Y1syM7UNuDYVRhM3BTYVA3SXc
Flashable zip to DISABLE HW keys
https://drive.google.com/open?id=0B2Y1syM7UNuDSFZwUHNLQ0RfdXM
Flashable zip to ENABLE HW keys (revert changes made by zip above)
https://drive.google.com/open?id=0B2Y1syM7UNuDalVLVzd0SFdLekk
Flashable stock bootanimation (same as the one in MM thread; since this ROM doesn't really have a bootanimation and uses the basic fallback bootanimation)
https://drive.google.com/open?id=0B2Y1syM7UNuDelFPZVh6dmxSR2c
Flashable zip to ENABLE Hidden SystemUI Tuner Features (thanks to @AL_IRAQI, see his original guide here)
This one was tricky, my first time decompiling an APK. I was getting some crashes at first, but I think this ZIP should work fine (I tested it on a dirty flash, and it works)
https://drive.google.com/open?id=0B2Y1syM7UNuDd0JBV2ViMXl1bnc
Flashable Google Keyboard 5.1
https://drive.google.com/open?id=0B2Y1syM7UNuDbnBmdEtWZlRlNlk
Flashable Nexus Launcher (credits to uploader)
https://www.androidfilehost.com/?fid=24588232905722237
Replace the stock Power Menu with an extended custom power menu (thanks to @nofx161):
See his post
Link to app
Layers themes are supported, use Substratum app (Play Store link) to apply
(ROOT NEEDED)
NOTE: Themes made only for Substratum will not work (properly) as this ROM doesn't support Substratum (that will need patches to ROM source). Only which support RRO/Layers will work without any issues.
Wow! Great work
Subscribed!
thanks for your work dude
Cool, thanks, gonna try asap
Enviado desde mi A0001 mediante Tapatalk
Great! Thank u dev!
updateing said:
2. SELinux is permissive, and init allows service without a SELinux domain to start.
Click to expand...
Click to collapse
Which sepolicy did you use? I am porting to a different device and Im currently trying to fix neverallows which is painful but I think I merged a commit to qcom/sepolicy which allows domain to start (im not very good in sepolicy). Its based off Cyanogenmod qcom/sepolicy repo. If you want to take a look its here android_device_qcom_sepolicy-1 and I had to add one thing to platform_system_sepolicy. I hope we'll be able to fix sepolicy soon.
Awesome.... Downloading already.
Awesome! Has anyone tried If gapps work?
Flashed it. But i get a FC all the time
com.qti.dpmserviceapp has stopped.
I cant do anything..?
Deltastylez said:
Flashed it. But i get a FC all the time
com.qti.dpmserviceapp has stopped.
I cant do anything..?
Click to expand...
Click to collapse
Really sorry that I forgot this. You could do "pm disable com.qti.dpmserviceapp" in adb shell (su first if it asks so)
A fellow hamster I see! Nice one.
updateing said:
Really sorry that I forgot this. You could do "pm disable com.qti.dpmserviceapp" in adb shell (su first if it asks so)
Click to expand...
Click to collapse
I am kind of a newbie to ADB
Could you perhabs tell me how to? step a step?
Thanks!
Deltastylez said:
I am kind of a newbie to ADB
Could you perhabs tell me how to? step a step?
Thanks!
Click to expand...
Click to collapse
You may find a lot of adb tutorials around...
But if there is a mute option in the FC dialog, you can mute it and disable in Settings.
updateing said:
Really sorry that I forgot this. You could do "pm disable com.qti.dpmserviceapp" in adb shell (su first if it asks so)
Click to expand...
Click to collapse
updateing said:
You may find a lot of adb tutorials around...
But if there is a mute option in the FC dialog, you can mute it and disable in Settings.
Click to expand...
Click to collapse
well, getting this error
" Error: java.lang.SecurityException: Shell cannot change component state for com.qti.dpmserviceapp/null to 2 "
Never mind, fixed
updateing said:
You may find a lot of adb tutorials around...
But if there is a mute option in the FC dialog, you can mute it and disable in Settings.
Click to expand...
Click to collapse
i've tried through adb shell but it doesn't work shell cannot change component state for com.qti.dpmserviceapp/null to 2 moreover it is not possible to disable it in settings thank u for your job
anyone!! please any reviews??
Knew it wouldn't be long before the famous Bacon machine got that great taste of nougat :good:
holy crap holy crap
EVERYONE BOARD THE HYPE TRAIN! CHOO CHOO!

[ROM][UNOFFICIAL][P][F500,LS991,H81x,US991,VS986] LineageOS 16.0

{
"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:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
About LineageOS​
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.
**** These builds are for both: official unlocked and UsU'd devices ****
UsU? http://bit.do/unlockg4​
Requirements​
Your device need to be unlocked either officially (h815 international or h811) or by UsU
Your bootloader stack should be on MM 20p (20x for H811) or higher! (see FAQ #8 for how to upgrade your bootloader stack without lgup BUT for your convenience I have alternatively created TWRP flashable files for that !!!! (click))
in particular that means this thread is for:
F500 (UsU'd)
H810 (UsU'd)
H811
H812 (UsU'd)
H815 (official unlocked or UsU'd)
H819 (UsU'd)
LS991 (UsU'd)
US991 (UsU'd)
VS986 (UsU'd)
Latest TWRP - PREVIEW build: click
Do a full Nandroid backup before doing anything!
Installation​
This single very first step is for UsU'd devices only:
If you have ever flashed the UsU baseband package: Clean flash the modem partition from your backup in TWRP.
If you do not know if you ever flashed it simply flash your modem partition again and you can be sure. This can't do any harm.
If you have no backup:
- TWRP flashable MM modems (N will not work)
Full clean install as described here (FAQ "#2") is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash LOS
Optional (f-droid is already included): Flash GApps (9.0 - ARM64) if you like to use google apps
Optional (if you want root): Flash the official LOS root-addon (addonsu-16.0-arm64-signed.zip) or Magisk (ensure you read FAQ #1 when using Magisk though)
Boot (will take a bit on first boot!!!)
Enjoy
Features​
Pure LineageOS ROM experience
F-Droid included (Open Source alternative to Google Play)
Torch workaround included (no root)
BT voice FIXED
Known issues​I can't test everything on my own, so a lot of things only show up after a release. That means:
- back up regularly and frequently!
- report issues the issue tracker (see next)
Check the current issues at the github tracker (feel free to help, provide logs etc!
If you find a bug not listed, follow the instructions here and provide me with the logs: FAQ #1
Download​Get your builds from my leech server
https://leech.binbash.rocks:8008/lineage/16.0/
Note:
Builds are updated as soon as possible. There is no build cycle.
Information pertaining to your device is displayed accordingly.
The current build is the latest for your device.
Changelogs​
only at my Telegram group
Credits​
LineageOS
The Suicide-Squirrel team (ThePiGuy, kessaras, steadfasterX)
aoleary
WiZaRd981
berkantkz
sdembiske
and more..
Sources​
build manifest
LEGACY XDA DB info​XDA:DevDB Information
lineage-16.0, ROM for the LG G4
Contributors
steadfasterX, ThePiGuy, kessaras, aoleary, WiZaRd981, HardStyl3r
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
ROM Firmware Required: latest MM / N (exact version is model dependent)
Based On: pure LineageOS
Version Information
Status: Stable
Created 2019-05-10
Frequently Asked Questions (FAQ)
Q #01: I want to report an issue. What is the proper way to do so?
I'm glad that you are asking: before doing so check the KNOWN ISSUES topic in the OP and ofc the other FAQ's listed here!
If you encountered a kernel panic follow FAQ #6 in this post instead.
If you have issues with "just" the boot process follow FAQ #7 for a very easy way to grab the boot logs.
if you have an audio issue follow FAQ #10 instead.
If your issue is not listed there click here to proceed:
If your issue is not listed there follow the directions here briefly and I may can fix it.
Often selinux can cause issues so try that at very first:
Code:
adb shell
su
(or "adb root" when enabled in developer settings)
setenforce permissive
Try again and if the issue is gone when in permissive mode: provide me a logcat as described here -> on step 3 I need the SELINUX log (option D)
If that does not solve your issue follow the logcat GUIDE to provide a valid log depending on what your issue is.
Ensure you have done a full CLEAN install before doing so (refer to FAQ #2 for what that means).
Warning: NO SUPPORT when:
- magisk is installed (known to cause issues sometimes - regardless of the ROM or version)
- Xposed is installed (known to cause issues sometimes - regardless of the ROM or version)
If you have installed any of these UNINSTALL or better do a FULL CLEAN install (see FAQ #2) before doing anything else. Often enough these above causes several issues like battery draining, problems on booting and much more. Even when they may work properly you should re-produce your issue without them first and follow the above to grab the log.
Magisk is a great piece of software and besides that it is Open Source which SuperSu never was.
I just saying I do not "support" issues with LOS when you have Magisk installed. Why? It is (like Xposed) extendable with modules (made by whoever) and those can cause billions of issues.
Other then that magisk was sometimes the reason for battery drain etc. Magisk modifies the boot "process" and sits very deep in the system (which is needed to make it work ofc) but that has the potential to make a system/ROM unstable or result in strange behaviors.
so in order to support a specific issue I have to be sure the ROM is in a "clean" state, no magisk, no xposed. The LOS root-addon is tested with LOS and made for it so that is not an issue but for the rest there are so many things which can going wrong..
Q #02: I want to install clean, how? What is a clean install? What is the recommended way to flash a new ROM version?
A clean install ensures that there are no leftovers from any previous install. One can say that there are 2 phases of a clean flash:
1) regular
2) full - when you (still) encounter issues
Usually the regular one is fully ok when flashing a new ROM version but if you encounter strange issues nobody else is reporting or if a release post is recommending it you should do a full clean install instead.
A regular clean install can be done like this:
WIPE -> Advanced -> select: System + Cache
Flash the ROM
reflash root addon/magisk if you want root
reflash opengapps if you want to use Google crap
A full clean install needs 2 steps more then the regular:
follow the steps for regular clean
go back in WIPE -> touch the "FORMAT data" button and type "yes" to format the internal storage (you will LOOSE ALL YOUR DATA - obviously)
REBOOT -> Recovery
Flash the ROM
reflash root addon/magisk if you want root
reflash opengapps if you want to use Google crap
It is absolutely recommended to create a backup before and COPYING IT to your PC(!) before doing the above.
Q #03: Are there any plans or a chance of official LOS builds?
TL;DR answer is: no.
Background:
LineageOS has "some" requirements before they accept it to do official builds: device-support-requirements.
For sure we do not met all and the most problematic one will be the kernel reqs as do provide a good battery life and a fast kernel kessaras had made unacceptable (for LOS) changes regarding several parts of that requirement topic. So a new kernel (branch) is needed to remove all the improvements we made which are not accepted. This process alone can take weeks (if you do not want to loose every good thing here). A much easier approach here would be to build a "just working" LOS stock kernel without any improvements and fixes and tell everyone: "Flash LOS, then a TITAN kernel afterwards". So while that might be the easier approach it will nevertheless take time to do that kernel and include the reqs + sec patches to the day.
Besides that a bit work is needed to fulfill some of the others like that.
Other then that and that is one of the most important things here:
Even when the device was accepted going official in the past (14.1... long time ago..) an incredible amount of changes happened to get oreo and now pie running. All these will be put to the test. Which actually means every commit we made will be discussed (worst case, yea, but ..) and changed. That can be from a simple "the commit message is wrong" to "pls re-write the code here". You maybe get an idea that this process is nerve-wracking (for me) and costs a lot of my free time.
Before RIL has been fixed (which had happened in the end of June 2019 first) it would have been impossible, I guess.
Now the base is fine, we could put a big amount of time into going to official to get finally ........ yea, what?
Well.. I would free resources on my build and leech server (I don't care - atm)
I would save bandwidth (I don't care - atm)
I would not need to tamper around anymore with (i.e jenkins) build issues (I don't care - atm)
you?
you would get a (LOS signed) build with a slow kernel, bad battery life and all the goodies missing... unless I build LOS kernels to bring those things back.
ok but to be honest. I can fully understand that request and I would feel better by myself when I were you. You do not know me so are my builds trustworthy ? Who knows. I could be a bad guy. :fingers-crossed:
Besides that I wrote above "I don't care - atm" so that might change in the future right? Correct.. there is no guarantee how long I can provide new builds or offer them on my leech server. There is nothing at the horizon that this might change soon but who knows? I can say that I am incredible happy with my OnePlus 6T and - believe it or not - I run STOCK OxygenOS here.. Why? It is just enough for me. So no need to do any dev there - which means all my dev time is still going here - to the G4. It is also a personal project to learn stuff around the Android eco system and woa.. who knows maybe Q came one day to the G4 as well..
... and yea official builds would give you some kind of guarantee that builds will happen - while that might change with my unofficial builds some day.
So.. as said in the TLDR above: No I personally do not have any plans in going official for the described reasons.
If someone else wants to go that way and needs help, I am here. But I cannot spend my whole free time on that.
Q #04: Google Play shows that my device is not "certified" - how can I fix that?
First of all you must be on the latest build. I fixed that from the latest July (2019) builds on.
If your issue persists click here to proceed:
The second thing is you must not be rooted by the LOS root addon (afaik). Magisk has its own protections to ensure you stay certified but I hadn't the time to test the LOS root-addon.
You also need to know that google play remembers your devices last state so if you are on the latest build and still having that issue do this and it will be certified again:
android settings -> apps -> find play store -> clear data (yes data, not cache) -> reboot -> open play store -> wait 2..5 minutes -> check certified state again
Q #05: It looks like the CPU cores 5 and 6 are disabled - how can I fix that?
TLDR;
There is no fix required! it is fully ok when those are idle. they get hot plugged whenever needed.
Details:
we have 2 clusters of CPU cores resulting in a Hexa-core CPU set: (4x1.4 GHz Cortex-A53 & 2x1.8 GHz Cortex-A57)
the big one (2 CPU cores - higher performance = more battery drain, more heat which potentially causing the: bootloop issue) and the little (4 CPU cores - less battery drain but a bit slower) are handled dynamically based on the load of your device.
the big cluster will run ONLY when it is NEEDED - i.e. high load.
so when you look closer: those are not DISABLED they are IDLE which is a big difference.
Q #06: I get a kernel panic or green/purple/blue screen how to grab logs for this?
You need a ROM with pstore fully enabled and working (pstore = debug kernel panics/oops happened in a ROM)!
All builds starting from 2019-08-15 on support pstore due to: commit#1, commit#2, commit#3
This is a 2-site change if you want to make use of it in TWRP you must install the latest TWRP "PREVIEW" release as well (TWRP is only able to show pstore logs when the ROM is able to write them so I needed to fix pstore in the ROM first (see above commits #1 + #2 )).
Besides those 2 patches these kernel configs were set: PSTORE
You can check if a ROM does support writing pstore logs by:
as soon as possible on a fresh boot:
Code:
adb shell
dmesg | grep "ramoops|pstore"
Code:
[ 0.000000] cma: Found [email protected], memory base 0x000000001fe00000, size 2 MiB, limit 0xffffffffffffffff
[ 0.000000] cma: CMA: reserved 2 MiB at 0x000000001fe00000 for ramoops_mem
[ 0.200846] cma: Assigned CMA region at 0 to ramoops.78 device
[B][ 3.957553] console [pstore-1] enabled
[ 3.957939] ramoops: attached [email protected], ecc: 16/0[/B]
[ 3.958079] drv probe : 200 ramoops 3744
[ 6.262463] SELinux: initialized (dev pstore, type pstore), uses genfs_contexts
or (if you are not fast enough) this ensures mostly the same check:
Code:
adb shell
ls -la /dev/pmsg0
Code:
crw-rw-rw- 1 camera camera 254, 0 2015-01-05 04:54 /dev/pmsg0
If you get no output your ROM does not support pstore logs.
From now on when you encounter a kernel panic and you are able to reboot without taking out the battery (taking out the battery will erase RAM):
1) reboot (without taking out the battery!) to either TWRP or (if you have root access) to your ROM
2) grab everything need from here: /sys/fs/pstore/ (e.g. adb pull /sys/fs/pstore/)
If you don't have a pc near you can do it directly from the device as well:
Enable the terminal app in developer options or download any
Open the terminal app.
su
cd /sdcard/Download
tar czf pstore.tgz /sys/fs/pstore
Attach pstore.tgz to your post.
It is crucial important that you do this only after the reboot happened . It's not important "when" though - as long as the device stays powered on.
Developers note:
convert PMSG log (requires a linux system):
Code:
tr -cd '\11\12\15\40-\176' < pmsg-ramoops-0 | sed 's/TENS\s/\n/g' > readable-pmsg.txt
Q #07a: I get a kernel panic on boot or having other boot issues but the pstore log are empty! What should I do?
Q #07b: How can I provide a clean boot log?
Since a while there is a very easy way to provide debug logs for the boot process. Before my convenient logging you had to follow FAQ #1 to grab them and it was a bit of PITA for some users.
So here you go for a much easier way:
boot Android
once booted : reboot to TWRP
when you have a bootloop instead: take the battery out just before the bootloop occurs, or better press the key combo to get into TWRP all the time to eventually get there directly
once in TWRP ensure that "Cache" is mounted in the "Mount" menu (if not mount it by ticking the box)
open a terminal on your PC and type:
Code:
adb pull /cache/debug/boot_lc_crash.txt
adb pull /cache/debug/boot_lc_full.txt
adb pull /cache/debug/boot_lc_kernel.txt
paste one by one to a paste service like https://del.dog/ , https://paste.systemli.org/ or https://paste.omnirom.org/
Q #8: upgrade your bootloader stack only?! Read here how:
If you don't mind you can use lgup as long as you do not have an UsU'd device!
For UsU devices follow the UsU FAQ #20 instead of this one!!!!!
If you just wanna upgrade the bootloader stack without loosing data: Check the OP topic "Requirements" of this thread because:
it has a link to TWRP flashable files for updating your bootloader with just 1 click ..
Anyways if you still want to go on doing it manually instead of the easy way then:
Download a KDZ of your device model.
Keep in mind that there a frankenstein devices out there (means refurbished devices with mixed hardware inside so you think u have model XXX as it was shown in Android but the mainboard is NOT the same!).
How to identify a Frankenstein device? Read FAQ #21 in the UsU thread.
IMPORTANT: Check the ARB of that KDZ (SALT v3.11 will show the ARB of a KDZ on extract!) - If you are unsure - DO NOT PROCEED. you can easily hard brick your device if!
Extract that KDZ with SALT - DO NOT USE ANY OTHER TOOL FOR EXTRACTING! The known windows tools like LG Firmware extract does not extract what we need here and not in the way we need it! So do not use that! You have been warned..
Open a terminal in the directory where you SALT backup before flashing UsU (or your extracted KDZ) is.
Then put your device in fastboot mode and type these commands (you have another file extension? read FAQ #24 of the UsU thread):
Again this guide is NOT for UsU'd devices!!!
Code:
fastboot flash aboot aboot.bin
fastboot flash factory factory.bin
fastboot flash hyp hyp.bin
fastboot flash modem modem.bin
fastboot flash pmic pmic.bin
fastboot flash rpm rpm.bin
fastboot flash sbl1 sbl1.bin
fastboot flash sdi sdi.bin
fastboot flash sec sec.bin
fastboot flash tz tz.bin
Alternative with TWRP (if the above fastboot cmds work for you no need to do this!):
Again this guide is NOT for UsU'd devices!!!
Code:
Boot TWRP
adb push factory.bin /tmp/
adb push hyp.bin /tmp/
adb push modem.bin /tmp/
adb push pmic.bin /tmp/
adb push rpm.bin /tmp/
adb push sbl1.bin /tmp/
adb push sdi.bin /tmp/
adb push sec.bin /tmp/
adb push tz.bin /tmp/
adb push aboot.bin /tmp/
adb shell sync
adb shell "dd if=/tmp/factory.bin of=/dev/block/bootdevice/by-name/factory"
adb shell "dd if=/tmp/modem.bin of=/dev/block/bootdevice/by-name/modem"
adb shell "dd if=/tmp/hyp.bin of=/dev/block/bootdevice/by-name/hyp"
adb shell "dd if=/tmp/pmic.bin of=/dev/block/bootdevice/by-name/pmic"
adb shell "dd if=/tmp/rpm.bin of=/dev/block/bootdevice/by-name/rpm"
adb shell "dd if=/tmp/sbl1.bin of=/dev/block/bootdevice/by-name/sbl1"
adb shell "dd if=/tmp/sdi.bin of=/dev/block/bootdevice/by-name/sdi"
adb shell "dd if=/tmp/sec.bin of=/dev/block/bootdevice/by-name/sec"
adb shell "dd if=/tmp/tz.bin of=/dev/block/bootdevice/by-name/tz"
adb shell "dd if=/tmp/aboot.bin of=/dev/block/bootdevice/by-name/aboot"
Download this verify tool to ensure the flashing was successful: [ATTACH]4687157[/ATTACH] ([URL="http://leech.binbash.it:8008/misc/verifyflash.zip"]mirror --> verifyflash.zip[/URL])
Usage:
extract verifyflash.zip
adb push verifyflash.sh /tmp/
adb shell chmod 755 /tmp/verifyflash.sh
adb shell /tmp/verifyflash.sh
Read the output of the flashing on the screen and in your terminal. Do NOT flash anything else! Just the above - but ALL of the above! (if you miss a single file you will HARD BRICK)
If something is failing do NOT continue and try to re-do the above commands. if it still fails write in this thread or better come into IRC (when between Monday and Friday)!
If something failing here it WILL brick your phone.
Q #9: A life without Google?! Read here how:
A life without Google ? Is that possible ? ...and why you should consider it ?
So why? That's easy to answer and if those are worth it depends totally on your personal needs:
1) BATTERY. Google services are draining a LOT of your battery, so to get the most out of your battery you should abandon Google gapps
2) PRIVACY. Almost all Google apps phoning home to Google! You don't care about that? You really should. You have nothing to hide? Oh dear believe me you have no idea how much of your private data you do NOT want to share. Keep also in mind that you give your private data not to a company only , there are always humans behind and what they do.. You do not believe me? Read on
BREAKING NEWS:
You can go on with the following steps or simply head-over to /e/ OS which is LOS but completely Google-Free + microG fully working pre-installed:
check it out here!
WARNING:
The last build supporting this spoofing method was 20210307. Everything later has that patch removed. Sorry for any inconvenience but maintaining that patch took more time then thought and for those who really care about privacy there is now /e/ OS available containing full microG support. I will leave the instructions here for those who cannot or do not want to switch to /e/ OS.
So if you feel one or both reasons might fit your personal needs here are some first steps to go (if you do NOT want to switch to /e/ OS):
1) all my builds come with FDroid which is a special app store containing just free open-source apps. As this might be a very limited I recommend to install Aurora from here which is a frontend for Google play. So search in FDroid for "Aurora Store" and let it install. Start Aurora and choose anonymous!!! and you can install everything from play as before.
2) install the microG repo in FDroid. Just open that link from your G4 and it will install the repo:
https://microg.org/fdroid/repo?fing...EB6DAB39B73157451582CBD138E86C468ACC395D14165
3) due to the fact that many apps depends on Google services as backend you need to do 2 things now:
a) developer options -> scroll down to signature spoofing and enable it *(read FAQ #11 why)
b) Download the current stable "Services Core" apk from here: https://microg.org/download.html and install it like that:
Code:
adb install com.google.android.gms-[REPLACETHIS].apk
c) if you have root:
Code:
adb shell
su
mount -o remount,rw /system
exit
adb push /tmp/com.google.android.gms-[REPLACETHIS].apk /system/priv-app/GsmCore.apk
if you do not have root, boot to TWRP now and mount system, then:
Code:
adb push /tmp/com.google.android.gms-[REPLACETHIS].apk /system/priv-app/GsmCore.apk
4) Install a location backend provider to make location services work without Google (yea Google is spying you..).
There are several available, just search for them in F-Droid:
Apple UnifiedNlp Backend uses Apple’s Wifi database.
LocalGsmNlpBackend uses downloaded GSM Cell data (local)
LocalWifiNlpBackend uses (on-device generated) WiFi data (local)
Déjà Vu Location Service uses (on-device generated) WiFi + GSM Cell data (local) * recommended
MozillaNlpBackend uses Mozilla Location Services * recommended
Radiocells.org UnifiedNlp Backend uses Radiocells.org
Also install a reverse location backend:
- e.g. NominatimNlpBackend (currently the only I know)
5) Now it's time to configure microG. Go in the app drawer and open microG settings:
you will be prompted or a notification is showing for setting permissions, go through all of them and choose allow.
UnifiedNlp settings:
- Configure the location backend service (choose the one you installed in step 4)
- Configure the address lookup backend (choose the one you installed in step 4)
Go back to the main screen of microG:
Choose Self-Check:
- Tap "System grants signature spoofing permission" and you wou get a request for allowing that (which you should do..)
- Tap Battery optimizations ignored to ensure microG is function properly
- Ensure "UnifiedNlp is registered in system" is checked (if not repeat the above steps for pushing the APK to system/priv-app)
- Ensure "Location Backends" is checked (if not repeat UnifiedNlp settings above)
Read the installation wiki for microG and install whatever else you might need:
- https://github.com/microg/android_packages_apps_GmsCore/wiki/Installation
6) reboot & re-do the self-check in microG settings
7) ensure the location service is *NOT* set to GPS-only (for LOS that means enable battery saving)
8) some general things now:
you might need to switch to alternatives sometimes. I use Waze instead of Google maps even though Google would work (but I don't like the Google spys). I use FairEmail as I love my privacy and supporting open-source. Usually you can find always an alternative, often paid apps offer activations and buying without Google play and that is often even cheaper (e.g. AquaMail costs 39€ on play and 30€ on their website etc).
There is one thing which really hurts me when it comes to gapps-less life: no smart lock. I really enjoyed it but for me the both reasons above have more weight then this.
So as you can see a life without Google has its advantages but also some changes are needed. If it's worth it depends on you. I can just recommend it
Q #10: issues with audio (e.g. echo's, silence on one or the other site, ..)? Read here how to provide a specific log for that:
Do the following steps:
1) Ensure you have adb set up on your PC, and have adb debugging and adb root enabled in developer options on your phone
2) Then perform the following (all one command)
On Linux:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver" && sleep 10 && adb logcat -b all |egrep -vi "(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)"
Click to expand...
Click to collapse
On windows:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver && sleep 10 && logcat -b all |egrep -vi '(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)' "
Click to expand...
Click to collapse
3) Then re-produce your audo issue and cancel the logcat from step 2 before hanging up!
4) Share the logcat output from the console screen using paste.omnirom.org
Q #11: I'm scared about that microG , I don't want to expose my phone so is this LOS version a security risk?
First of all you need a lot of trust installing ANY custom ROM. A developer can do nasty things right? Besides that yes microG allowing to let apps act like as they are another app, also known as signature spoofing. This CAN be a good and a bad thing. Read on why my LOS is different:
In general the microG patch is an all or nothing. A ROM which supports microG (i.e. signature spoofing) have that feature enabled, always. That's what I don't like.
I want the user to decide if he wants to take the risk or not and not exposing a feature for everyone even when they don't need it.
That's why the user must enable it explicitly in developer options before it gets activated (as described in FAQ #9).
All details of the implementation and why can be found here:
https://github.com/steadfasterX/android_signature_spoofing
https://github.com/Suicide-Squirrel/issues_pie/issues/30
Q #12: The ROM is lagging and/or the device gets very hot/warm, what can I do to help fixing that?
Ensure you read and understand about the ILAPO first.
If you encounter any overheat or lagging issues follow this:
Code:
adb shell
logcat -b all -d | egrep -i "thermal|kill" > /sdcard/Download/log.txt
ps -A >> /sdcard/Download/log.txt
free -m >> /sdcard/Download/log.txt
logcat -b crash -d >> /sdcard/Download/log.txt
exit
adb pull /sdcard/Download/log.txt
Share the log.txt as an attachment of your reply (bc txt is fine for that) or - as usual - by your favorite paste service
Q #13: I have graphic glitches / issues, what can I do?
My builds using skiaGL instead of OpenGL since a while. skia is the new and faster renderer coming with pie by default but it can cause graphic glitches in some applications and/or situations.
Is there any fix for skiaGL coming? No, details here .
To check if your current ROM version is using skiaGL do this:
Code:
adb shell getprop debug.hwui.renderer
If you get an empty result it means skiaGL is active.
If for any reason you wanna go back and enforce OpenGL you can do so by
temporary (immediately activated):
Code:
adb root (must be enabled in dev options)
adb shell setprop debug.hwui.renderer opengl
or make that change persistent:
Code:
boot TWRP
backup system
mount system
adb shell
echo "debug.hwui.renderer=opengl" >> /system/build.prop
sync
reboot
.-
User recommendations to enhance the LOS experience
The following contains a list of 3rd party apps or mods to enhance the default LOS experience.
They are not tested by myself but recommended by the community for whatever reason..
If you miss something here post in the thread at least the app name, the google play store link to that app and a short description why it is that good.
Camera:
Google Cam as it has more options/settings.
Download Google Cam #1
or the trCamera_V5 port of Google Cam as recommended by Gigio755 here as finally videos are shown in gallery and you have also a lots of settings and advanced settings
Note: disable 2x and wide camera (in advanced settings) to avoid accidental touch and crashing camera app (just this)
Download Google Cam #2
Hedgecam 2 because it has tons of customization features & best in class (free app) manual video control options
Download Hedgecam 2
Launcher:
Nova Launcher because it feels more snappy
Download Nova Launcher
Keyboards:
Simple Keyboard because it is just that (a keyboard), also good for your privacy and available via F-Droid
Google Gboard because it has so many (but keep in mind: spying) features
Fleksy because I like it
Root:
Magisk because the LOS root-addon will be deprecated in LOS 17 and ofc because Magisk has so many nice features like hiding etc.
Download Magisk - only there - nowhere else!
Web Browser:
Via Browser, a very fast browser, clean UI, decently customizable. noteworthy features: 1) Back without reloading & 2) Use volume buttons to scroll.
Download Via Browser
Misc / Tools:
AnyMote for remote controlling IR devices because it seems to be the most stable and working one
Download AnyMote
Simple gallery pro (free when downloaded in F-Droid) as a replacement for the gallery app as it has a lot of customization options and feels much better
Download Simple Gallery Pro (F-Droid store, which is included in all LOS builds, free) alternative Download (Play Store, paid)
Frost for Facebook, a web based FB client, light, fast, & customizable. Allows for some extra control over notifications compared to the app (afaik) and it's also less cluttered
Download Frost for Facebook
TUNING:
Kernel Adiutor settings by User gkg2k for a faster and smoother experience: check out his great guide here
Note: I recommend to skip the RAM settings mentioned there when using build 20200324 or later. If you feel you still need those settings try it first without nevertheless .. I made a lot of improvements since that mentioned build so give it a go first.
.-
Nice. I never used UsU before, is that really necessary? I'm unlocked.
Glad we got Pie too. Hope it gets much more stable asap. Great work :good:
:highfive: can't wait, android pie plus LOS 16 is coming! Many thanks
Sent from my Samsung Galaxy S8+ using XDA Labs
Deleted
pedrogcsb said:
Nice. I never used UsU before, is that really necessary? I'm unlocked.
Click to expand...
Click to collapse
where do you read that UsU is necessary..?
.-
No builds atm ...
terema91 said:
No builds atm ...
Click to expand...
Click to collapse
dunno how i can say it more clear that this is in progress... https://i.imgur.com/bffYoNp.png
.-
No progress atm ...
terema91 said:
No progress atm ...
Click to expand...
Click to collapse
really? you must be god.
thread is closed for now as I do not have the time to feed trolls
.-
Builds are up for:
H811
H815
H815 - UsU
VS986
H812
H810
Before reporting issues ensure you have read the KNOWN ISSUES topic in the OP before
Keep in mind that this is brand new stuff so it may contain issues unknown yet!
That's why the whole project is declared as BETA - not STABLE.
It wasn't until Pie felt stable enough for everyday use that I released it publicly, but I still can't test everything on my own, so a lot of things only show up after a release.
So back up regularly and frequently.
If you find a bug, follow the instructions here and provide me with the logs: http://bit.do/logcat
.-
Does this have to be done for an LG G4 LS991 SV1? Or can I just straight up root no problem? Sorry. New to all this!
Stavinair Bluewing said:
Does this have to be done for an LG G4 LS991 SV1? Or can I just straight up root no problem? Sorry. New to all this!
Click to expand...
Click to collapse
afaik there is no SV1 for the LS991 but you really should go to the UsU thread and take the time to read first.
.,
This rom pass safetynet! Great, from time to time I have some lags but in general is fine, the performance of the battery is really good, many thanks and great work @steadfasterX
Sent from my Samsung Galaxy S8+ using XDA Labs
Just to say "thank you guys" for all this work !
Grazie mille, Merci beaucoup !
Looks great so far! I don't know why SELinux is disabled for me though... Is it because I flashed the ROM, Gapps, Magisk, then the high resolution video fix at the same time?
Edit: UI is a bit choppy (not too bad though), and app icons sometimes don't show when you're moving icons from the app drawer to your home screen for me. Also brightness slider might be a bit broken...
Sir Daniel III said:
Looks great so far! I don't know why SELinux is disabled for me though... Is it because I flashed the ROM, Gapps, Magisk, then the high resolution video fix at the same time?
Edit: UI is a bit choppy (not too bad though), and app icons sometimes don't show when you're moving icons from the app drawer to your home screen for me. Also brightness slider might be a bit broken...
Click to expand...
Click to collapse
regarding SELinux read the known issues. it is not enforcing atm.
yes the GL renderer is not optimal but you can try Pie's new default one if you like (known to have glitches)
just execute this (as root I guess)
Code:
setprop debug.hwui.renderer skiagl
That one works well for me but has sometimes in some situation graphic bugs. It will take effective immediately and will not survive a reboot (so must be set then again).
.-
Also, I have trouble backing up data via TWRP.... It says something about it unable to locate a storage device.

[ROM][UNOFFICIAL][P][F500,LS991,H81x,US991,VS986] /e/ OS | BYE Google, HELLO Privacy!

{
"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"
}
brought to you by the
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
****
These builds are for all G4 models: official unlocked and UsU'd devices
****
UsU? http://bit.do/unlockg4​
About /e/
/e/ is an a mobile ecosystem (ROM + onlines services) that:
is open source
is pro-privacy
is compatible with most existing Android applications
cares about usability
is as far as possible freed from shackles by Google and OEMs
already exists!
It’s the alternative to the Apple/Google duopoly on the smartphone.
... so again and just to be clear: /e/ is not just a ROM, it is more a complete privacy ecosystem and consists of:
an installable mobile operating system for smartphones, which is forked from Android and strongly “ungoogled”
a set of sorted and improved default open source applications
various online services that are linked to the mobile operating system, such as: a meta search engine for the web, drive (with synchronization), mail, calendar, notes, tasks.
Features
Based on LineageOS so a very stable base
microG fully pre-installed with Signature Spoofing in restricted mode!
All features described on the /e/ page: What is e
All features and fixes of my LOS 16 builds.
Finally I had the time to setup an own OTA server.. so my builds come with full OTA update support
... you know that thing which informs you that a new update is there and where you just click to download + install
Difference from pure /e/ or: why are the builds CUSTOM?
The /e/ app store has been removed completely (read the FAQ why I did this drastic change)
AuroraStore has been added (pls always use "anonymous" unless you need paid apps to avoid bans)
F-Droid has been added (The OpenSource alternative store. First search for any apps here!)
Dozens of F-Droid repositories are pre-installed (activate them with just a finger tip! That's needed to ensure you only get what you want)
added PhoneSky a patched Google playstore working with microG
added Lawnchair (latest from their TG group)
The above changes are the reasons why my builds are of the type "CUSTOM" and not "UNOFFICIAL".
This is according to the rules /e/ defined.
Known issues:
Keep in mind that this is brand new stuff so it may (still) contain unknown issues!
So back up regularly and frequently!
Check the current issues at the github tracker (feel free to help, provide logs etc!)
If you find a bug not listed, follow the instructions here and provide me with the logs: FAQ #1
Requirements
Your device need to be unlocked either officially (h815 international or h811) or by UsU
Your bootloader stack should be on lastest MM version for your model. That is e.g. 20p for the H815 models or 20x for H811.
So.. NO SUPPORT ON LOWER bootloader stacks then the latest MM version for your model
... and NO SUPPORT for the BETA v29A as well!!
-> for your convenience I have created TWRP flashable files for that !!!! (click)
Of course ensure you just use files for your model, your ARB and UsU'd or not. If unsure ask.
in particular that means this thread is for:
F500, H810, H811, H812, H815 (official unlocked or UsU'd), H819 , LS991, US991, VS986
Latest TWRP - PREVIEW build: click or SHRP build: click
Do a full Nandroid backup before doing anything!
Installation
This single very first step is for UsU'd devices only (SKIP when you have an official unlocked model):
If you have ever flashed the UsU baseband package: Clean flash the modem partition from your backup in TWRP.
If you do not know if you ever flashed it simply re-flash your modem partition again and you can be sure. This can't do any harm.
If you have no backup:
- TWRP flashable MM modems (N will not work)
Ensure your bootloader is current! You will have issues if you are not on the latest bootloader stack. Read the above Requirements topic to find a link to TWRP flashable files.
Full clean install as described here (FAQ "#2") is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash /e/
Optional (if you want root): Flash Magisk
Flashing OpenGapps ????? NO No no! you don't want that on a google-free phone! /e/ contains everything you need to live without Google! So flashing OpenGapps on /e/ is like using a bit more secure LOS but that's not the point of /e/. Either try without or go with LOS (imho).
Boot it (will take a bit on first boot!!! be patient!)
Enjoy the most easy way to have a privacy focused and google-free phone!
Download
OFFICIAL builds (new install or re-install):
https://doc.e.foundation/search?q=LG G4
CUSTOM builds (new install or re-install)
https://leech.binbash.rocks:8008/e-os/pie/
If you have /e/ installed already and just want to update to a newer release:
Android settings -> Updater (yes my CUSTOM builds have OTA support like OFFICIAL has!)
Note:
CUSTOM builds: Builds are updated as soon as possible. There is no build cycle.
Information pertaining to your device is displayed accordingly.
The current build is the latest for your device.
Changelogs
CUSTOM: posted in my Telegram build channel
OFFICIAL: https://gitlab.e.foundation/e/os/releases/-/releases
Support
Of course in this thread but also by Telegram. I have created a generic group for all stuff around Android : here
and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here
Credits
LineageOS (the base of /e/)
The /e/ foundation and all related devs making this experience possible!
The Suicide-Squirrel team (ThePiGuy, kessaras, steadfasterX)
aoleary
and more..
Sources
local build manifest
repo init manifest
XDA:DevDB Information
g4_eos-pie_custom, ROM for the LG G4
Contributors
steadfasterX
Source Code: https://gitlab.e.foundation/e
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
ROM Firmware Required: latest MM firmware for your model !
Based On: Lineage OS
Version Information
Status: Stable
Created 2020-08-03
faq
Frequently Asked Questions (FAQ)
Q #0: Why is the /e/ App store not included??? It is GREAT!
Mainly due to security and privacy concerns. Wth? I thought /e/ is secure and privacy focused? Yes it is but.. read on:
First of all the App store itself has no security or privacy issues. It is opensource and I see no issues with the app itself!
... the most important point for a smartphone is the availability of apps. I mean having a secure device which respects your privacy is great but it will have no chance to win when you cannot get easily apps on it.
... and the most dangerous part for a smartphone is installing apps because here is where Malware can easily step in! So whatever you do never install APK files from a website directly unless you can be 100% safe it is trustworthy.
It is all about trust again and when you look in the sources of the /e/ Apps store you find it connects to: cleanapk.org.
/e/ makes that not a secret though as you can read here.
So who is behind that cleanapk.org? Why is /e/ trusting them? While reading through the /e/ forums I found that this page hosts (as far as we know) apps mirrored from apkpure + fdroid.
.. and it's completely unclear who hosts that site and where is behind it. On the other site /e/ (Gael, the founder as well) states clearly they are not in any relation to that site. "They just using their api".
here some facts:
you cannot get the owner by a whois request
They have a info page here which just roughly describes where the apps are coming from and how
There is no detailed privacy statement or even an info if they keep your data GDPR compliant or not
No way for devs to get their apps removed or updated
The /e/ foundation clearly states they have no relationship to that repository of apps but some things are interesting aren't they:
IP's of /e/ and cleanapk are at least nearby
During an ongoing discussion about exactly that topic something took my attention: the welcome notification on api.cleanapk.org was exactly at that time: https://archive.is/U1E0y (I mean.... )
/e/ itself was audited several times by a site named "infosec-handbook" and of course even they find that app store at least "mysterious"
During that mentioned discussion and after pointing Gael to that - the welcome message suddenly changed to what it is today..
The full topic where even Gael is talking (not that friendly) is: here
TL;DR:
/e/ is providing apps (the most used way to get infected by malware) by an API which is at least questionable.
I do not say /e/ is doing questionable things and as said before the /e/ ROM is 100% trustworthy (otherwise I would not do any builds for it) but that cleanapk.org site is truly another story.
An interesting quote of Gael can make one read between the lines (I marked the interesting ones bold and cursive):
Some users have reported that they are using Aurora, [...] (context: we will never integrate this) because it’s infriging the play store terms of services.
For this, we have to use indirect mechanisms, that don’t infrige the play store TOS, and therefore, we are using a service that is not officially part of the /e/ project, and which is called cleanapk.org
On the long run, we other plans with partners, to offer something more transparent, but it’s too soon to talk about this.
Click to expand...
Click to collapse
Of course /e/ needs to ensure that what they are doing is 100% legal and offering an app repository like cleanapk.org is not.
My personal assumption is that /e/ is offering that repo - indirectly so not officially by the e.foundation itself.
A relation between is for sure nothing they want to have public as this would cause legal questions.
So the last question is:
Q: Why do I consider AuroraStore "better" then using cleanapk.org and so removed the /e/ apps store and adding AuroraStore instead?
A: Because I definitively know where the apps are coming from when using Aurora instead of /e/. Not just the app itself is OSS (like the /e/ one) the apps are coming directly from the play store instead of an unknown source.
Q #01: I want to report an issue. What is the proper way to do so?
I'm glad that you are asking: before doing so check the KNOWN ISSUES topic in the OP and ofc the other FAQ's listed here!
If you encountered a kernel panic follow FAQ #6 in this post instead.
If you have issues with "just" the boot process follow FAQ #7 for a very easy way to grab the boot logs.
if you have an audio issue follow FAQ #10 instead.
If your issue is not listed there click here to proceed:
If your issue is not listed there follow the directions here briefly and I may can fix it:
logcat GUIDE
Ensure you have done a full CLEAN install before doing so (refer to FAQ #2 for what that means).
Warning: NO SUPPORT when:
- magisk is installed (known to cause issues sometimes - regardless of the ROM or version)
- Xposed is installed (known to cause issues sometimes - regardless of the ROM or version)
If you have installed any of these UNINSTALL or better do a FULL CLEAN install (see FAQ #2) before doing anything else. Often enough these above causes several issues like battery draining, problems on booting and much more. Even when they may work properly you should re-produce your issue without them first and follow the above to grab the log.
Magisk is a great piece of software and besides that it is Open Source which SuperSu never was.
I just saying I do not "support" issues with LOS when you have Magisk installed. Why? It is (like Xposed) extendable with modules (made by whoever) and those can cause billions of issues.
Other then that magisk was sometimes the reason for battery drain etc. Magisk modifies the boot "process" and sits very deep in the system (which is needed to make it work ofc) but that has the potential to make a system/ROM unstable or result in strange behaviors.
so in order to support a specific issue I have to be sure the ROM is in a "clean" state, no magisk, no xposed.
Pro-Tip: set magisk to core functions only to see if an extension causes your issue or not.
Q #02: I want to install clean, how? What is a clean install? What is the recommended way to flash a new ROM version?
A clean install ensures that there are no leftovers from any previous install. One can say that there are 2 phases of a clean flash:
1) regular
2) full - when you (still) encounter issues
Usually the regular one is fully ok when flashing a new ROM version but if you encounter strange issues nobody else is reporting or if a release post is recommending it you should do a full clean install instead.
A regular clean install can be done like this:
WIPE -> Advanced -> select: System + Cache
Flash the ROM
reflash root addon/magisk if you want root
A full clean install needs 2 steps more then the regular:
follow the steps for regular clean
go back in WIPE -> touch Factory Reset and let it do its job
go back in WIPE -> touch the "FORMAT data" button and type "yes" to format the internal storage (you will LOOSE ALL YOUR DATA - obviously)
REBOOT -> Recovery
Flash the ROM
reflash root addon/magisk if you want root
It is absolutely recommended to create a backup before and COPYING IT to your PC(!) before doing the above.
Q #03: Are there any plans or a chance of official /e/ builds?
yes this in progress (as of April 2021) and so should happen somewhen in 2021
Q #04: Will this ROM support / pass SafetyNet?
When you install Magisk you can hide and so yes you might be able to pass SafetyNet. Which can change every day though because even when that might work atm you should note the following:
Magisk has its own protections to ensure you pass safetynet but this is something which will change one day and there is no known method yet to workaround that.
Q #05: It looks like the CPU cores 5 and 6 are disabled - how can I fix that?
TLDR;
There is no fix required! it is fully ok when those are idle. they get hot plugged whenever needed.
Details:
we have 2 clusters of CPU cores resulting in a Hexa-core CPU set: (4x1.4 GHz Cortex-A53 & 2x1.8 GHz Cortex-A57)
the big one (2 CPU cores - higher performance = more battery drain, more heat which potentially causing the: bootloop issue) and the little (4 CPU cores - less battery drain but a bit slower) are handled dynamically based on the load of your device.
the big cluster will run ONLY when it is NEEDED - i.e. high load.
so when you look closer: those are not DISABLED they are IDLE which is a big difference.
Q #06: I get a kernel panic or green/purple/blue screen how to grab logs for this?
When you encounter a kernel panic and you are able to reboot without taking out the battery (taking out the battery will erase RAM and so erase the needed logs):
1) reboot (without taking out the battery!) to either TWRP/SHRP or (if you have root access) to your ROM
2) grab everything need from here: /sys/fs/pstore/ (e.g. adb pull /sys/fs/pstore/)
If you don't have a pc near you can do it directly from the device as well:
Enable the terminal app in developer options or download any
Open the terminal app.
su
cd /sdcard/Download
tar czf pstore.tgz /sys/fs/pstore
Attach pstore.tgz to your post.
It is crucial important that you do this only after the reboot happened . It's not important "when" though - as long as the device stays powered on.
Developers note:
convert PMSG log (requires a linux system):
Code:
tr -cd '\11\12\15\40-\176' < pmsg-ramoops-0 | sed 's/TENS\s/\n/g' > readable-pmsg.txt
Q #07a: I get a kernel panic on boot or having other boot issues but the pstore log are empty! What should I do?
Q #07b: How can I provide a clean boot log?
Since a while there is a very easy way to provide debug logs for the boot process. Before my convenient logging you had to follow FAQ #1 to grab them and it was a bit of PITA for some users.
So here you go for a much easier way:
boot Android
once booted : reboot to TWRP/SHRP
when you have a bootloop instead: take the battery out just before the bootloop occurs, or better press the key combo to get into TWRP all the time to eventually get there directly
once in TWRP ensure that "Cache" is mounted in the "Mount" menu (if not mount it by ticking the box)
open a terminal on your PC and type:
Code:
adb pull /cache/debug/boot_lc_crash.txt
adb pull /cache/debug/boot_lc_full.txt
adb pull /cache/debug/boot_lc_kernel.txt
paste one by one to a paste service like https://del.dog/ , https://paste.systemli.org/ or https://paste.omnirom.org/
Q #8: upgrade your bootloader stack only?! Read here how:
Check the OP of this thread which has TWRP flashable files linked.
Q #9: Is there an /e/ specific FAQ?
Sure:
FAQ: click
Forum: click
HOWTOs: click (a great resource for all your first questions)
Q #10: issues with audio (e.g. echo's, silence on one or the other site, ..)? Read here how to provide a specific log for that:
Do the following steps:
1) Ensure you have adb set up on your PC, and have adb debugging and adb root enabled in developer options on your phone
2) Then perform the following (all one command)
On Linux:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver" && sleep 10 && adb logcat -b all |egrep -vi "(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)"
Click to expand...
Click to collapse
On windows:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver && sleep 10 && logcat -b all |egrep -vi '(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)' "
Click to expand...
Click to collapse
3) Then re-produce your audo issue and cancel the logcat from step 2 before hanging up!
4) Share the logcat output from the console screen using paste.omnirom.org
Q #11: I'm scared about that microG , I don't want to expose my phone so is this /e/ version a security risk?
First of all you need a lot of trust installing ANY custom ROM. A developer can do nasty things right? Besides that yes microG allowing to let apps act like as they are another app, also known as signature spoofing. This CAN be a good and a bad thing. Read on why my builds are different:
In general the microG patch is an all or nothing. A ROM which supports microG (i.e. signature spoofing) have that feature enabled, always.
The difference in my /e/ builds is that I am using the "restricted" option of signature spoofing so as long as you trust me you are as safe as without microG.
Q #12: I have graphic glitches / issues, what can I do?
My builds using skiaGL instead of OpenGL since a while. skia is the new and faster renderer coming with pie by default but it can cause graphic glitches in some applications and/or situations.
Is there any fix for skiaGL coming? No, details here .
To check if your current ROM version is using skiaGL do this:
Code:
adb shell getprop debug.hwui.renderer
If you get an empty result it means skiaGL is active.
If for any reason you wanna go back and enforce OpenGL you can do so by
temporary (immediately activated):
Code:
adb root (must be enabled in dev options)
adb shell setprop debug.hwui.renderer opengl
or make that change persistent:
Code:
boot TWRP
backup system
mount system
adb shell
echo "debug.hwui.renderer=opengl" >> /system/build.prop
sync
reboot
.-
Reserved
Awesome! Nice initiative! Cannot wait to test it when I get my hands on my old G4!
Thank you so much for this port!
No more tinkering with Magisk to stub Google services.
And such good news for the OTA!
Amazing work. I just came back to my G4 to set it up as an in car GPS and this is an amazing ROM for it.
It is very smooth, the device does not overheat, and location works very well.
Thank you Steadfasterx.
Man, this is AWESOME !
The most sustainable phone (well, second to the Fairphones, of course) with the best Google-alternative ROM… Could I ever dream of something better ? OTA updates, maybe ?
EDIT (after reading fully) :
Wow… OTA updates are there. You rock. You really do !!
Thank you for the love that you give to keep this community alive. I still cannot believe that you brought /e/ to LG G4 OTA is also very exciting news.
I also appreciate that you pre-install F-Droid (it is almost the first thing I need when booting to a new ROM).
I have been running your LOS ROMs for a long time. I have heard about /e/ before, and now, I am excited to give it a shot on my h815 device! Just hoping that it receives updates along with your LOS builds.
Good luck
Does encryption work?
I imagine that it's the same limitations as with LineageOS version, TWRP cannot decrypt, isn't it?
zeduck said:
Does encryption work?
I imagine that it's the same limitations as with LineageOS version, TWRP cannot decrypt, isn't it?
Click to expand...
Click to collapse
yes it does. the limitations is not in the ROM its in TWRP so yes you cannot decrypt.
.-
steadfasterX said:
yes it does. the limitations is not in the ROM its in TWRP so yes you cannot decrypt.
.-
Click to expand...
Click to collapse
Thanks for the quick and very clear response!
Just to be sure: as we have OTA updates on this ROM, it's completly usable to encrypt the phone, even if we cannot decrypt partitions with TWRP, right?
zeduck said:
Thanks for the quick and very clear response!
Just to be sure: as we have OTA updates on this ROM, it's completly usable to encrypt the phone, even if we cannot decrypt partitions with TWRP, right?
Click to expand...
Click to collapse
correct. flashing a ROM (and so an OTA) will just modify the /system partition which is always unencrypted so no issue on that.
.-
I encrypted the phone, but now I cannot boot anymore.
The prompt for decryption pop up correctly, and I am sure of the password.
What did I do wrong?
zeduck said:
I encrypted the phone, but now I cannot boot anymore.
The prompt for decryption pop up correctly, and I am sure of the password.
What did I do wrong?
Click to expand...
Click to collapse
do you have the latest bootloader stack for your device?
.-
steadfasterX said:
do you have the latest bootloader stack for your device?
.-
Click to expand...
Click to collapse
I thought I had.
I reflashed it just in case (h815_20p_bootloader_20p_modem_TWRP-flashable.zip).
It doesn't change anything.
zeduck said:
I thought I had.
I reflashed it just in case (h815_20p_bootloader_20p_modem_TWRP-flashable.zip).
It doesn't change anything.
Click to expand...
Click to collapse
Hm strange . Did you format (!) data before ? If not try it now pls (ofc that means your data is gone).
I may can re-check tomorrow but the last time it went without any issues here....
EDIT:
hm.. thats weird. I tested it on my h815 UsU'd device with a build from 16th of July and it works fine (no PIN set). After it booted I set a PIN and choose to ask that on boot. still working fine.
on my other H815 I tested it with the latest eOS build (PIN set before) and it does not work.
same for a LOS (!) build from July. still investigating..
EDIT2:
re-flashed latest version and set no pin, encrypt, bootloops. so there must had happen something between 16th july and august.. will check
EDIT 3:
uh I was a bit too impatient. it looped just 2 or 3 times then it boots up and is encrypted now! so a workaround is to set no pin/pass before the initial encryption. Once it is encrypted setting a key works fine...
so there must be something failing on initial encryption when a pin/pass is set.. will check
.-
Sent from my OnePlus 7T Pro using XDA Labs
steadfasterX said:
:
EDIT 3:
uh I was a bit too impatient. it looped just 2 or 3 times then it boots up and is encrypted now! so a workaround is to set no pin/pass before the initial encryption. Once it is encrypted setting a key works fine...
so there must be something failing on initial encryption when a pin/pass is set.. will check
.-
Click to expand...
Click to collapse
I confirm, I had a password set!
Meanwhile, I reflashed the ROM after having wiped everything.
zeduck said:
I confirm, I had a password set!
Meanwhile, I reflashed the ROM after having wiped everything.
Click to expand...
Click to collapse
yea the strange thing is now I cannot re-produce it anymore.. whatever I do it just works all the time now..
.-
zeduck said:
I confirm, I had a password set!
Meanwhile, I reflashed the ROM after having wiped everything.
Click to expand...
Click to collapse
wait! iirc there is a bug in TWRP: after you encrypted did you tried to decrypt in TWRP?
EDIT:
nah that wasn't it as well.. damn cannot reproduce the issue..
EDIT 2:
ok finally ..
I was able to reproduce it by flashing LOS 17 and encrypting there (which is failing atm). After that encrypting in Pie (LOS and /e/) fails as well.
Have moved that into an github issue #52
EDIT 3: @zeduck
the workaround is mentioned here: https://github.com/Suicide-Squirrel/issues_pie/issues/52#issuecomment-675457810
or wait until the next TWRP preview which allows to wipe it in the UI
.-
BREAKING NEWS
I've decided to create a Telegram group for all stuff around Android : here
and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here
New builds are cooking...
I have added a test in my jenkins build process to ensure that the unified device tree is working as it should.
Unifying our device tree makes it much easier to maintain and to add other not-yet added models - while it comes with the risk something goes wrong when it comes to blobs.
Nevertheless:
I would highly recommend doing the following (I have done that in my manual builds but you get it from jenkins - so there is a tiny little chance of bad luck .. ):
Pre-Cautions | Flashing instructions
Recommended: Backup (system, userdata in TWRP, your internal storage which contains your photos etc elsewhere)
Required: Do a "REGULAR CLEAN FLASH" (see bottom of this post)
Flash LOS - DO NOT choose to reboot afterwards - stay in TWRP.
TWRP menu: "Mount" --> choose "System"
From a terminal execute:
Code:
adb shell md5sum /system/etc/firmware/venus.mbn
Compare the value (last 4 characters is fully enough) with these:
If you flash:
h815, f500, h818, h819 it should be: d1f6fe863643b1e8d1e597762474928c
h810, h811, h812, ls991, us991, vs986 it should be: 78e5cf520d0de4a413ef1cfa7bbbe713
WARNING: If that checksum is NOT as it should be: DO NOT PANIC! simply FLASH the PREVIOUS LOS version BEFORE booting!. This will ensure you will not blow a fuse.
While the above test should be considered safe: If you are unsure about this procedure: WAIT before flashing until someone (or I) had done the above quick test from the builds jenkins is providing at my leech server.
Whenever an error occurs while flashing in TWRP (e.g "E1001: Failed to update system image.Updater process ended with ERROR: 7")
or if the above checksum does not match:
provide the recovery.log (FAQ #4 A)!!
... then flash the previous LOS version to get back to life - without harming your device.
if instead (as we all expect) all went well and you had opengapps before - ensure you reflash gapps
Cooking order & LIVE cooking view
H815
H811
H815 UsU
VS986
H812
H810
Live - View:
Normal view: https://shebang.binbash.rocks:8800/job/LG-G4/job/eOS-pie/job/Build all LGE-G4 models/workflow-stage/
Blue Ocean: https://shebang.binbash.rocks:8800/blue/organizations/jenkins/LG-G4/eOS-pie/Build all LGE-G4 models/ (click at the top line )
Noteworthy Changes:
Flashing method: "REGULAR CLEAN FLASH" is REQUIRED!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
(See the FAQ #2 of the LOS thread how to do this)
If you encounter any overheat or lagging issues follow this:
Code:
adb shell
logcat -b all -d | egrep -i "thermal|kill" > /sdcard/Download/log.txt
ps -A >> /sdcard/Download/log.txt
free -m >> /sdcard/Download/log.txt
logcat -b crash -d >> /sdcard/Download/log.txt
exit
adb pull /sdcard/Download/log.txt
Share the log.txt as an attachment of your reply (bc txt is fine for that) or - as usual - by your favorite paste service
Platform Security Patch: 2020-08-05
Due to some user reports I reverted the GPS updates by kessaras. Please let me know if GPS works better with this build or not.
New signing keys. You may now the "Trust" feature by LOS telling you if the build is trustworthy or not?! It checks if selinux is enforcing (it is in my builds) and if non-default signing keys (I sign my builds with my own ones) are in use.
The signing keys are required to allow installing OTA updates (it downloads, checks if the signature is mine, rejects if not or accepts and installs if).
Unfortunately I had to re-generate the signing keys that means you have to install this new build as usual in TWRP.
All builds after that one will fully support OTA. sorry for that
...... and more. Read "Full details"
Full details:
kernel: commits
g4-common tree: commits
g4 unified tree: commits
/e/OS: gitlab
Keep in mind that almost all pie ROM's sharing the same common device tree (or main parts of it), same model device trees and for sure the same kernel - so you can enjoy most fixes for any pie ROM available.. :victory:
ok enough of words, just one more thing:
flash and enjoy this privacy focused and totally Google-Free experience
.-

[Alpha][miatoll] Droidian (Debian Bookworm) for Xiaomi Redmi Note 9 Pro - 9 Pro Max - 9S - Poco M2 Pro

{
"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"
}
Droidian is a GNU/Linux distribution based on top of Mobian, a Debian-based distribution for mobile devices. The goal of Droidian is to be able to run Mobian on Android phones.
This is accomplished by using well-known technologies such as libhybris and Halium.​Carefully read the whole post before jumping to installation.​They are important to give you the best idea of the current state of the OS.​
What is working:​- Alarm Clock (bullseye/stable only. Doesn't work on bookworm/nightly)
- Manual brightness
- Vibration
- Carrier info, signal strength
- Data connection (read bugs section)
- Incoming, outgoing calls
- SMS in, out
- Change audio routing
- Voice in calls
- Volume control in calls
- Bluetooth
- WiFi
- Proximity
- Rotation
- Touchscreen
- Earphones
- Headphones
- Loudspeaker
- Microphone
- Volume control
- Pin unlock
- Waydroid
- Wireguard
What doesn't work:​- Most of the things not mentioned above.
Bugs:​- RIL gets broken after switching airplane mode or modem off/on. Fixed after a reboot.
- Mobile data stops working after making or receiving calls. Toggle mobile data on and off from the settings app.
- Mobile data doesn't work in the first 2-3 minutes after reboots. Toggle mobile data on and off from the settings app after waiting a while to get it working.
- Droidian has no power management yet so you're left with only the 5020mAh battery which can last up to 6 hours without heavy usage.
Installation:​
Make a backup now, as your device will be wiped.
Click to expand...
Click to collapse
Download the needed files and tools
Droidian rootfs (specific build required)
Android 10 (Q) stock firmware
Latest TWRP recovery
Adaptation (unofficial)
Device preparation
A USB 2.0 port/hub with an actual USB 2.0 controller is recommended (Using fastboot on a USB 3.0 port may cause errors with some Xiaomi devices)
Save your APN (Android)
The Access Point Name or APN can be found in the Settings menu of Android
Take a piece of paper or a text editor, and write down everything that you see on that screen
These are likely to include a URL (e. g., internet.carrier.net), a username, and possibly a password
Unlock the bootloader (Computer)
Refer to the instructions provided by the device manufacturer
Other useful sources include the LineageOS wiki and xda-developers
Boot into recovery (Computer)
Boot TWRP by running fastboot boot twrp-VERSION-miatoll.img
Wipe the device (TWRP)
Go to the Wipe menu
Select Advanced wipe
Tick the boxes called Dalvik / ART cache, Cache, System, Vendor, Data
Swipe to Wipe
Go back to the previous menu
Choose Format data and type yes
Go back to the main menu and select Reboot
Choose Bootloader
Boot TWRP again by running fastboot boot twrp-VERSION-miatoll.img
Copy the files to the device (Computer)
When TWRP is booted, open the device’s Internal storage from your computer
Copy all of the files you downloaded to this folder
Droidian installation (TWRP)
Install recovery
Install the file called twrp-VERSION-miatoll.img as an Image to the Recovery partition
Install Droidian rootfs
Install the file called droidian-rootfs-arm64_YYYYMMDD.zip as a Zip file
Alternatively, you can enter ADB sideload mode and run adb sideload droidian-rootfs-arm64_YYYYMMDD.zip
Installation is optional for stable releases, but it is recommended, because it helps with debugging
Finalizing the installation
Install adaptation package as a flashable zip (TWRP)
Install the file called adaptation-droidian-miatoll.zip as a Zip file
Alternatively, you can enter ADB sideload mode and run adb sideload adaptation-droidian-miatoll.zip
Boot your device
Go to the Reboot menu and choose System
TWRP might complain that there is no OS installed, but that’s fine
The first boot may take longer, and at least one spontaneous reboot is expected during the process
You should be greeted with the lock screen, the default password is 1234
Congratulations, if everything went well, now you should be running Droidian.
Notes:
Recovery
Use the recovery linked at the start of this page. The installation might fail with other recoveries that the one mentioned above.
Default password
The default password is 1234.
Apn
Mobile data needs an APN to be set up from Settings -> Mobile Network -> Access Point Names.
Broken mobile data after calls
Data connection might break after receiving and making calls. Switch it off and on from Settings -> Mobile Network to fix it. Be careful to not turn off the mobile modem or a device restart might be required.
Broken calls
Switching airplane mode on and off or switching the mobile modem off and on from the Quick Settings or the Settings App will break calls. If that’s the case reboot the phone to fix it.
Out of storage
By default when flashing Droidian it allocates 8GB of memory to the system. This might not be enough and luckily you can allocate more storage with ADB by running (while in recovery): adb shell e2fsck -fy /data/rootfs.img and adb shell resize2fs -f /data/rootfs.img xG where x is the amount of GB to allocate (eg: 50G for 50 GB).
Status
Droidian GSIs are experimental! Bugs and missing features are expected.
SSH access
Connect your phone to your computer and type ssh [email protected], the password is 1234 (on Windows, you may need PuTTY)
Applications
You can find a list of mobile-friendly Linux applications at LinuxPhoneApps
Credit:​Marcel Alexandru Nitan
Droidian Mobian UBports
You can ask for assistance specific to this device at Droidian for miatoll devices.
Sources:​- kernel
- adaptation package
Donate:​- PayPal
- Revolut
Announcement/Update ~ Droidian
Support for Droidian Bullseye has been discontinued. Droidian Bookworm has become more stable while the old Bullseye version hasn't received any updates from the devs since December 2021.
Users that are still on Bullseye are recommended to backup their data and install the Bookworm version for Droidian by following the new instructions located at https://devices.droidian.org/devices/miatoll/
For already Bookworm users:
Until now we've used the same ramdisk Ubuntu Touch uses because Droidian had no dynamic partition support. That has been changed on the previous days and a new adaptation package has been created to update the old ramdisk we used.
I've disabled the old miatoll ppa repository so the kernel won't get updated since it will "wipe" all the data and modifications.
To continue to receive kernel updates add the new miatoll ppa repository:
Your data and system changes will be cleared but will remain in /userdata/rootfs-overlay which will no longer be used after updating to the latest kernel as all the changes are now written into the Droidian rootfs.
Bash:
sudo curl -# --proto '=https' --tlsv1.2 -Sf https://miatoll-linux.github.io/repo/miatoll.gpg --output /usr/share/keyrings/miatoll.gpg && \
echo "deb [signed-by=/usr/share/keyrings/miatoll.gpg] https://miatoll-linux.github.io/repo/ bookworm main" > ~/miatoll.list && \
sudo mv ~/miatoll.list /etc/apt/sources.list.d/miatoll.list && \
sudo apt update
sudo apt upgrade
Thanks for the new Rom!
Can you reduce installation step. Currently it's too lengthy to follow.
Amazing work man! But I would be surprised if anyone would be even able to flash it. Recently I uploaded a ROM with a fully automated installer and even that was too complicated for many people so I already feel sorry for this thread and You the Dev.
Other than that. Thank You soooo much for this <3. I can't wait to flash it!
ProtoDeVNan0 said:
Amazing work man! But I would be surprised if anyone would be even able to flash it. Recently I uploaded a ROM with a fully automated installer and even that was too complicated for many people so I already feel sorry for this thread and You the Dev.
Other than that. Thank You soooo much for this <3. I can't wait to flash it!
Click to expand...
Click to collapse
Not to go off topic but that's one of the reasons I stopped making Roms on XDA and instead keep them for myself lol.
Anyways OP, Amazing to see people working on Debian based Roms for our device. Will definitely be checking this out sometime this week!
[email protected] said:
Thanks for the new Rom!
Can you reduce installation step. Currently it's too lengthy to follow.
Click to expand...
Click to collapse
Unfortunately I can't. The recoveries we have available for our phones are not able to mount the raw img file (rootfs.img) so sideloading the devtools and the adaptation package is not possible so we have to manually fix the mount via losetup and make the extraction of the packages above ourselves.
Probably everything will be fixed when we're going to get a fully working and stable recovery.
hi! what is it the current situation of battery drain, i really want to give a try
[email protected] said:
Thanks for the new Rom!
Can you reduce installation step. Currently it's too lengthy to follow.
Click to expand...
Click to collapse
Installation steps reduced
[email protected] said:
hi! what is it the current situation of battery drain, i really want to give a try
Click to expand...
Click to collapse
Well it improved since the last time. Don't expect days of battery life but it's enough to get you through the day
*Waydroid can decrease the battery like a lot btw.
Hi, I really love your work @nitanmarcel
Thanks
How is this for daily use?
Mobile data problems fixed?

[ROM][UNOFFICIAL][R/A11][F500,LS991,H81x,US991,VS986] /e/ OS | BYE Google, HELLO Privacy!

{
"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"
}
brought to you by the
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
****
These builds are for all G4 models: official unlocked and UsU'd devices
****
UsU? http://bit.do/unlockg4​
About /e/​/e/ is a mobile ecosystem (ROM + onlines services) that:
is open source
is pro-privacy
is compatible with most existing Android applications
cares about usability
is as far as possible freed from shackles by Google and OEMs
already exists!
It’s the alternative to the Apple/Google duopoly on the smartphone.
... so again and just to be clear: /e/ is not just a ROM, it is more a complete privacy ecosystem and consists of:
an installable mobile operating system for smartphones, which is forked from Android and strongly “ungoogled”
a set of sorted and improved default open source applications
various online services that are linked to the mobile operating system, such as: a meta search engine for the web, drive (with synchronization), mail, calendar, notes, tasks.
Features​
Based on LineageOS so a very stable base
microG fully pre-installed with Signature Spoofing in restricted mode!
All features described on the /e/ page: What is e
full OTA update support
... you know that thing which informs you that a new update is there and where you just click to download + install
Difference from pure /e/ or: why are the builds CUSTOM?​
F-Droid has been added (The OpenSource alternative store. First search for any apps here!)
Dozens of F-Droid repositories are pre-installed but NOT activated by default (activate them with just a finger tip! That's needed to ensure you only get what you want)
added PhoneSky a patched Google playstore allowing in-app-purchase on microG
added Lawnchair (latest from their TG group)
The above changes are the reasons why my builds are of the type "CUSTOM" and not "UNOFFICIAL".
This is according to the rules /e/ defined.
Known issues​Keep in mind that this is brand new stuff so it may (still) contain unknown issues!
So back up regularly and frequently!
Check the current issues at the github tracker (feel free to help, provide logs etc!)
If you find a bug not listed, follow the instructions here and provide me with the logs: FAQ #1
Requirements​
Your device need to be unlocked either officially (h815 international or h811) or by UsU
Your bootloader stack should be on lastest MM version for your model. That is e.g. 20p for the H815 models or 20x for H811.
So.. NO SUPPORT ON LOWER bootloader stacks then the latest MM version for your model
... and NO SUPPORT for the BETA v29A as well!!
-> for your convenience I have created TWRP flashable files for that !!!! (click)
Of course ensure you just use files for your model, your ARB and UsU'd or not. If unsure ask.
in particular that means this thread is for:
F500, H810, H811, H812, H815 (official unlocked or UsU'd), H819 , LS991, US991, VS986
Latest TWRP - PREVIEW build: click or SHRP build: click
Do a full Nandroid backup before doing anything!
Installation​
This single very first step is for UsU'd devices only (SKIP when you have an official unlocked model):
If you have ever flashed the UsU baseband package: Clean flash the modem partition from your backup in TWRP.
If you do not know if you ever flashed it simply re-flash your modem partition again and you can be sure. This can't do any harm.
If you have no backup:
- TWRP flashable MM modems (N will not work)
Ensure your bootloader is current! You will have issues if you are not on the latest bootloader stack. Read the above Requirements topic to find a link to TWRP flashable files.
Full clean install as described here (FAQ "#2") is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash /e/
Optional (if you want root): Flash Magisk
Flashing OpenGapps ????? NO No no! you don't want that on a google-free phone! /e/ contains everything you need to live without Google! So flashing OpenGapps on /e/ is like using a bit more secure LOS but that's not the point of /e/. Either try without or go with LOS (imho).
Boot it (will take a bit on first boot!!! be patient!)
Enjoy the most easy way to have a privacy focused and google-free phone!
Download​
Not available (yet) -> OFFICIAL builds (new install or re-install):
https://doc.e.foundation/search?q=LG G4
CUSTOM builds (new install or re-install):
http://leech.binbash.rocks:8008/e-os/a11
If you have /e/ installed already and just want to update to a newer release:
Android settings -> Updater (yes my CUSTOM builds have OTA support like OFFICIAL has!)
Note:
CUSTOM builds: Builds are updated as soon as possible. There is no fix build cycle.
Information pertaining to your device is displayed accordingly.
The current build is the latest for your device.
Changelogs​
CUSTOM: posted in my Telegram build channel
OFFICIAL: https://gitlab.e.foundation/e/os/releases/-/releases
Support​Of course in this thread but also by Telegram. I have created a generic group for all stuff around Android : here
and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here
Credits​
LineageOS (the base of /e/)
The /e/ foundation and all related devs making this experience possible!
The LG G Four team (aoleary, steadfasterX, Paul Tully)
and more..
Sources
build manifest
e OS source
Frequently Asked Questions (FAQ)
Q #01: I want to report an issue. What is the proper way to do so?
I'm glad that you are asking: before doing so check the KNOWN ISSUES topic in the OP and ofc the other FAQ's listed here!
If you encountered a kernel panic follow FAQ #6 in this post instead.
If you have issues with "just" the boot process follow FAQ #7 for a very easy way to grab the boot logs.
if you have an audio issue follow FAQ #10 instead.
If your issue is not listed there click here to proceed:
If your issue is not listed there follow the directions here briefly and I may can fix it:
logcat GUIDE
Ensure you have done a full CLEAN install before doing so (refer to FAQ #2 for what that means).
Warning: LIMITED SUPPORT when:
- magisk is installed (known to cause issues sometimes - regardless of the ROM or version)
If you have magisk installed currently UNINSTALL or better do a FULL CLEAN install (see FAQ #2) before doing anything else. Try to re-produce the issue. If it is gone, its magisk related. otherwise follow the above to grab the log.
Magisk is a great piece of software and besides that it is Open Source which SuperSu never was.
I just saying I do not "support" issues with LOS when you have Magisk installed. Why? It is (like Xposed) extendable with modules (made by whoever) and those can cause billions of issues.
Other then that magisk was sometimes the reason for battery drain etc. Magisk modifies the boot "process" and is placed very deep in the system (which is needed to make it work ofc) but that has the potential to make a system/ROM unstable or result in strange behaviors.
so in order to support a specific issue I have to be sure the ROM is in a "clean" state, no magisk, no xposed.
Pro-Tip: set magisk to core functions only to see if an extension causes your issue or not.
Q #02: I want to install clean, how? What is a clean install? What is the recommended way to flash a new ROM version?
A clean install ensures that there are no leftovers from any previous install. One can say that there are 2 phases of a clean flash:
1) regular
2) full - when you (still) encounter issues
Usually the regular one is fully ok when flashing a new ROM version but if you encounter strange issues nobody else is reporting or if a release post is recommending it you should do a full clean install instead.
A regular clean install can be done like this:
WIPE -> Advanced -> select: System + Cache
Flash the ROM
reflash root addon/magisk if you want root
A full clean install needs 2 steps more then the regular:
follow the steps for regular clean
go back in WIPE -> touch Factory Reset and let it do its job
go back in WIPE -> touch the "FORMAT data" button and type "yes" to format the internal storage (you will LOOSE ALL YOUR DATA - obviously)
REBOOT -> Recovery
Flash the ROM
reflash root addon/magisk if you want root
It is absolutely recommended to create a backup before and COPYING IT to your PC(!) before doing the above.
Q #03: Are there any plans or a chance of official /e/ builds?
yes this might happen when the following has been solved / implemented (which is NOT the case currently (see known issues):
- selinux = enforcing
- device encryption working
Q #04: Will this ROM support / pass SafetyNet?
When you install Magisk you can hide and so yes you might be able to pass SafetyNet. Which can change every day though because even when that might work atm you should note the following:
Magisk has its own protections to ensure you pass safetynet but this is something which will change one day and there is no known method yet to workaround that.
Q #05: It looks like the CPU cores 5 and 6 are disabled - how can I fix that?
TLDR;
There is no fix required! it is fully ok when those are idle. they get hot plugged whenever needed.
Details:
we have 2 clusters of CPU cores resulting in a Hexa-core CPU set: (4x1.4 GHz Cortex-A53 & 2x1.8 GHz Cortex-A57)
the big one (2 CPU cores - higher performance = more battery drain, more heat which potentially causing the: bootloop issue) and the little (4 CPU cores - less battery drain but a bit slower) are handled dynamically based on the load of your device.
the big cluster will run ONLY when it is NEEDED - i.e. high load.
so when you look closer: those are not DISABLED they are IDLE which is a big difference.
Q #06: I get a kernel panic or green/purple/blue screen how to grab logs for this?
When you encounter a kernel panic and you are able to reboot without taking out the battery (taking out the battery will erase RAM and so erase the needed logs):
1) reboot (without taking out the battery!) to either TWRP/SHRP or (if you have root access) to your ROM
2) grab everything need from here: /sys/fs/pstore/ (e.g. adb pull /sys/fs/pstore/)
If you don't have a pc near you can do it directly from the device as well:
Enable the terminal app in developer options or download any
Open the terminal app.
su
cd /sdcard/Download
tar czf pstore.tgz /sys/fs/pstore
Attach pstore.tgz to your post.
It is crucial important that you do this only after the reboot happened . It's not important "when" though - as long as the device stays powered on.
Developers note:
convert PMSG log (requires a linux system):
Code:
tr -cd '\11\12\15\40-\176' < pmsg-ramoops-0 | sed 's/TENS\s/\n/g' > readable-pmsg.txt
Q #07a: I get a kernel panic on boot or having other boot issues but the pstore log are empty! What should I do?
Q #07b: How can I provide a clean boot log?
Since a while there is a very easy way to provide debug logs for the boot process. Before my convenient logging you had to follow FAQ #1 to grab them and it was a bit of PITA for some users.
So here you go for a much easier way:
boot Android
once booted : reboot to TWRP/SHRP
when you have a bootloop instead: take the battery out just before the bootloop occurs, or better press the key combo to get into TWRP all the time to eventually get there directly
once in TWRP ensure that "Cache" is mounted in the "Mount" menu (if not mount it by ticking the box)
open a terminal on your PC and type:
Code:
adb pull /cache/debug/boot_lc_crash.txt
adb pull /cache/debug/boot_lc_full.txt
adb pull /cache/debug/boot_lc_kernel.txt
paste one by one to a paste service like https://del.dog/ , https://paste.systemli.org/ or https://paste.omnirom.org/
Q #8: upgrade your bootloader stack only?! Read here how:
Check the OP of this thread which has TWRP flashable files linked.
Q #9: Is there an /e/ specific FAQ?
Sure:
FAQ: click
Forum: click
HOWTOs: click (a great resource for all your first questions)
Q #10: issues with audio (e.g. echo's, silence on one or the other site, ..)? Read here how to provide a specific log for that:
Do the following steps:
1) Ensure you have adb set up on your PC, and have adb debugging and adb root enabled in developer options on your phone
2) Then perform the following (all one command)
On Linux:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver" && sleep 10 && adb logcat -b all |egrep -vi "(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)"
Click to expand...
Click to collapse
On windows:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver && sleep 10 && logcat -b all |egrep -vi '(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)' "
Click to expand...
Click to collapse
3) Then re-produce your audo issue and cancel the logcat from step 2 before hanging up!
4) Share the logcat output from the console screen using paste.omnirom.org
Q #11: I'm scared about that microG , I don't want to expose my phone so is this /e/ version a security risk?
First of all you need a lot of trust installing ANY custom ROM. A developer can do nasty things right? Besides that yes microG allowing to let apps act like as they are another app, also known as signature spoofing. This CAN be a good and a bad thing. Read on why my builds are different:
In general the microG patch is an all or nothing. A ROM which supports microG (i.e. signature spoofing) have that feature enabled, always.
The difference in my /e/ builds is that I am using the "restricted" option of signature spoofing so as long as you trust me you are as safe as without microG.
Q #12: I have graphic glitches / issues, what can I do?
My builds using OpenGL instead of skiaGL since a while. skia is the new and faster renderer coming with pie by default but it can cause graphic glitches in some applications and/or situations.
Is there any fix for skiaGL coming? No, details here .
To check if your current ROM version is using skiaGL do this:
Code:
adb shell getprop debug.hwui.renderer
If you get an empty result or "skiagl" it means skiaGL is active.
If for any reason you wanna enforce skiaGL you can do so by
temporary (immediately activated):
Code:
adb root (must be enabled in dev options)
adb shell setprop debug.hwui.renderer skiagl
or make that change persistent:
Code:
boot TWRP
backup system
mount system
adb shell
echo "debug.hwui.renderer=skiagl" >> /system/build.prop
sync
reboot
.-
I uploaded it, good speed, I will continue to try. Thank you
Thanks for this new ROM
I recommend a full cleanup with format
The only issue I have so far is that I can't connect to my Murena.io account, it keeps on loading. Logs attached
Thanks for this Rom, installed 72 hours ago, feels a bit slower than the same Pie Rom,thats expected, but it is fine, very usable. You do an excellent job with this Rom, feels more fluid and energy efficient than linage pie plus gapps and gms working as it should out of the box, this is the first and only Rom of all, i have tried, in every phone i had since my first android, from 2011 doing that. Wont gonna write nothing about battery usage, or SoT, batteries are the oem LG put in these phones.
Until now the only incovenience is that with dark theme enabled, sometimes, 3 out of 10 times, when i wake the screen its lights wont use the brightness it supposed to use, it wake very dim, i´m still debuging this glitch, pushing the power button to turn it off and then pushing it again bring back to full brightness the screen.
cvmg333 said:
Thanks for this Rom, installed 72 hours ago, feels a bit slower than the same Pie Rom,thats expected, but it is fine, very usable. You do an excellent job with this Rom, feels more fluid and energy efficient than linage pie plus gapps and gms working as it should out of the box, this is the first and only Rom of all, i have tried, in every phone i had since my first android, from 2011 doing that. Wont gonna write nothing about battery usage, or SoT, batteries are the oem LG put in these phones.
Until now the only incovenience is that with dark theme enabled, sometimes, 3 out of 10 times, when i wake the screen its lights wont use the brightness it supposed to use, it wake very dim, i´m still debuging this glitch, pushing the power button to turn it off and then pushing it again bring back to full brightness the screen.
Click to expand...
Click to collapse
The blackout when phone display is off is a well known issue since years with any custom ROM for the g4. We tried to fix that for a long time without any real success.
Interesting note, i did not know about it, thanks for the tip, i will use light theme now onwards then, got another little problem with the microphone, the other person hear me to low, only when i use speakerphone in a whatsapp call, with out the speakerphone activated every thing is working well, have not tried in a normal telephone call yet, i have tried changing microphone volume setting in kernel with ex kernel manager, but no success in that, changing screen colors and saturation works in that app, thank you.
@steadfasterX this could be tried https://github.com/sthomsonpl/devic...mmit/07db7d8be41997765f9a0c60d7e7476b5440545e
I installed this ROM yesterday, and its running fine so far.
Thanks a lot for bringing this gem to ye ole G4.
You really did an excellent job!
Auto rotate not working. H815 UsU'd. Yes - flashed UsU zip.
Edit: Also, when turning on bluetooth, connecting bluetooth headphones then playing a video, bluetooth turns off.
I haven't tested bluetooth on the pie /e/OS or the various LineageOS builds, so it could very well be affecting those too.
Hello,
I have unlocked my G4 H815 EU version with USU and installed /e/-OS with Android 11 on it, but afterwards I noticed that I can't make phone calls. I also can't receive phone calls, but the phone sends a message that I have received a phone call. How could this error be fixed?
pizza_alarm said:
Hello,
I have unlocked my G4 H815 EU version with USU and installed /e/-OS with Android 11 on it, but afterwards I noticed that I can't make phone calls. I also can't receive phone calls, but the phone sends a message that I have received a phone call. How could this error be fixed?
Click to expand...
Click to collapse
flash 20p bootloader stack and modem
Thanks. Where can I find the correct bootloader and modem files?
pizza_alarm said:
Thanks. Where can I find the correct bootloader and modem files?
Click to expand...
Click to collapse
pls check the OP -> Requirements (bootloader stack), Installation (Modem)

Categories

Resources