[Alpha][miatoll] Droidian (Debian Bookworm) for Xiaomi Redmi Note 9 Pro - 9 Pro Max - 9S - Poco M2 Pro - Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke

[Alpha][miatoll] Droidian (Debian Bookworm) for Xiaomi Redmi Note 9 Pro - 9 Pro Max - 9S - Poco M2 Pro - Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke

{
"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?

Related

[TOOL] Lx Multi Tool v1.3.2 [WIN/LIN/MAC][Unlock/Recovery/Stock/Kernel/More]

{
"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"
}
It has LINUX/UNIX and MAC support!

Because there is another tool for Android called Android Multi Tools, I renamed this one to Lx Multi Tool, future releases will go under this name.
 Features: 
Fastboot- Unlock/Lock Bootloader- Flash Recovery Menu (you can choose and add recoveries) - TWRP 2.8.7.2 Included- Flash any partition (Flashing submenu)- Flash full Stock images (you can choose and add images)- Erase partitions (you can choose which of the partitions)- Reboot (you can choose again...)Adb- Sideload .zip files (you can choose and add .zip files) - SuperSU v2.56 (Systemless!) included- Backup (you can choose the name and place for your backup)- Restore (you can choose your backup)- Version (it just shows the version of your adb binaries) - platform-tools 23.0.1 included- Logs (DMESG and Logcat)- Screenshots (you can directly take screenshots to your PC with no Root)- Reboot (lots of choices)Others- Refresh and delete files/folders from menus (Right-click or key F5 and Del)- Open tool folders from the menus (to add your own kernel/stock image/recovery/sideload zip files)- Tab key support for easier keyboard navigation- Tool-tips for all buttons- Check for updates- Link to xda-thread (here) Download links: 
Windows x86|x64 - Linux x64 - MAC x64All released versions can be found here.

(The latest versions are always on the bottom.)[ROOT] Use SuperSU 2.62 or higher from here systemless for 6.0.1 and above.
 Known bugs/limitations: 
- For partition Flashing, it is recommended(mandatory?) to do a reboot-bootloader if you want to flash multiple partitions one after the other. (according to the Google flashing scripts) (Implemented in 1.2.1)- For the return to stock, the tool will be stuck after your phone successfully boots, you need to reboot to fastboot again in order to flash the Radio and finish the full return to stock. (Fixed in 1.2.0)
 Changelog: 
Check the changelog for each release here. Tutorials/FAQ: 
Q: How do I get in bootloader/fastboot mode?Turn off the phone and turn it on by using Volume down + Power key.Q: How do I check for updates on your tool?Follow the instructions on the screen below.
Q: Where can I find the device driver to install it for windows?Click here, download the driver, and run the setup.Q: How do I root my stock phone?- Unlock bootloader.- Flash recovery.- Use SuperSU 2.62 systemless or higher from here.(Usually the latest version upon tool release is included in the Sideload folder of the tool, you can either sideload it or copy it to recovery and flash it manually)Q: I get an error "Cannot open file" on MAC, what should I do?Open the terminal, go to your application path and paste this command:
Code:
chmod +x LxMultiTool.app/contents/macos/*
Q: What do I need to do in order to be in Fastboot or in ADB mode.Fastboot mode will be detected only while being in bootloader.ADB mode will be detected from Recovery (custom) and actual ROM with USB debugging active.Refresh button needs to be used in order to check for what mode you are in.Q: Are there any other software that I need to install in order to run this tool?On Windows and MAC everything is bundled, so nothing needs to be installed, just run.On Linux you need to install from your package manager libQt5Core, libQt5Widgets, libQt5Gui, libQt5Network.If it's not enough, use ldd LxMultiTool in the terminal to find out what you're missing from your environment.Q: I have a yellow/orange/red text screen during boot, what's that?When you unlock you usually get the Orange screen and it's normal, but if you really want to know what's this about, give a reading to this.Q: Hey, my device is not detected, why?On windows, you need to manually install the USB drivers, they are not included and probably they won't be included in this tool.Also, make sure you click the connection Refresh button after connecting the device to your PC.Q: What do I need to do in order to install a custom ROM?1. Unlock Bootloader.2. Flash a custom recovery of your choice.3. Flash an insecure kernel (boot).4. Flash custom ROM with no problems via recovery.All those things are found and can be done via this tool.Q: Hi, I just downloaded this tool, how do i use it?First, extract the folder somewhere.After that, run LxMultiTool.exe on windows by double-clicking it, LxMultiTool on Linux, and the same on mac.Q: Do I need android-sdk installed or something else?No! This tool uses its own supplied binaries for adb and fastboot, if you have android-sdk installed it will be ignored anyway.This tool is fully portable and stand-alone.Q: I get an error while trying to unlock the bootloader -> FAILED(remote: oem unlock is not allowed), what now?Starting with Android 5.0, you need to enable Bootloader Unlocking from the developer settings, in order to do that, follow these steps:- Enable Developer options- Enable USB Debugging- Look for the ‘OEM Unlock’ Option and toggle it.Q: How do I use the return to stock feature?First, download the latest package from here, then extract the contents (there is an archive in the archive) until you get to a folder like angler-mda89dthat contains the images, that folder needs to be copied in the /Data/StockPackages folder in order to be visible.Easier steps -> Get your device in bootloader -> Start the tool -> Hit refresh -> go to Stock -> hit open folder -> copy the extracted folder with the name angler-xxxxxx in there, hit F5 or Right-click + Refresh -> you should see the folder in there like in the following screenshot. Thanks @ursa08 for the screenie.
Q: How do I enable Developer options?- Launch the Settings- Scroll Down and Tap on About Phone(or About Device)- Locate the Build Number Section- Tap on the Build Number Option 7 Times- Go Back to the Main Settings Page- Scroll Down and Tap on Developer OptionsQ: Hi, I just bought a phone what should I do now?Well, you firstly need to unlock your bootloader...Q: What is logcat?Well, you can pretty much use google for that answer, but to put it short, is that thingy that tells you what is happening behind the scenes of your phone.It is usually used for debugging and entertainment(?).When you report an error/bug to somebody, it will be a blessing to provide a logcat (log file)!Q: What is a Custom Recovery and why do I need one?A custom recovery is that thingy that lets you flash .zip files, use your logic, and you will get it why you need one.Q: There are other guides/tutorials out there. Should I check them instead of this?If you manage to get things done using this one, no, otherwise yes, note that some could be outdated...Q: What is sideload and how do I use it?Sideload is a function from adb that let's you flash a zip file while in recovery directly from your PC.Please note that you need to be in sideload mode on your recovery before doing this.To enter sideload mode, in TWRP go to Advanced -> ADB Sideload -> Swipe to sideload
 Sources: 
The official and original repository can be found here.
 Bug reports/feature requests: 
If you have any bug, or you consider a feature to be a must-have, please use the issue functionality on GitHub for more traceability here.
 Licensing: 
Please note that this tool is open source and released under the GPL v3 license, which can be read here.Make sure you understand at least the short version of the license that's provided in the tool before using it or before contributing/forking and other related stuff.
 Tech and stuff: 
Some additional marketing for stuff used in this toolQt - An awesome cross-platform IDEVmware - For letting me test this tool on all platforms (Linux and MAC).Icons8 - A nice platform for good-looking FREE icons. (Big thanks!)UnixUtils - For the sed utility for Windows.AndroidFileHost - For the awesome file-management platform for developers.
 Donations: 
Even though this tool is provided free of charge, fully open-source, donations are very welcome to support the future development of this tool and to buy me a beer while coding future improvements on it.This section will also include the hall of fame for donors and on the github repository.Special thanks for donations:- @john7760
 Disclaimer: 
I will not be responsible for smashed screens, bricked phones, or any other things that you can accuse me of, I've done this tool to help people, use it at your own risk and consider giving a THANKS if you use it and like it.Please consider leaving some feedback, what to improve, what could be done better, what annoys you, it really helps me improve the tool.
Also, to avoid useless threads on general, Q&A, or useless posts, please read the FAQ section upside, it's like a Mini-Guide!
XDA:DevDB Information
Lx Multi Tool, Tool/Utility for the Huawei Nexus 6P
Contributors
Lexmazter
Source Code: https://github.com/lexmazter/LxMultiTool
Version Information
Status: Stable
Created 2016-01-01
Last Updated 2016-01-16

Already tool kit?
*Damn, nexus dev support is amazing
I feel so bad for buying galaxy s6, 0 aosp roms, Mod edit: Profanity removed dev support and all because of stupid exynos ;C

You da man! Can't wait for my phone to show up.

That was quick!! Waiting for this phone to be launched in India.

It works great thanks.I mean Tool

Wow. Can't wait to get my 6P and use this
Sent from my A0001 using Tapatalk

Add to Nexus 6P index thread:
[INDEX] Huawei Nexus 6P

Haven't even received my device yet, just wanted to say Thanks in advance!

Showing so much promise
I can't say more for this kind of support.

Great to see this already in the forum. Waiting on my 6P 128 Gig MONSTER.

wilbarger said:
Great to see this already in the forum. Waiting on my 6P 128 Gig MONSTER.
Click to expand...
Click to collapse
Got the 128gb monster on the way myself.

Thanks for this. Making it easy for everyone is a great thing I'm so excited to get back on a nexus

Thanks for this tool, I need to start from scratch because I don't have a Nexus since Nexus One

Thanks for this. Will be a first time user for the nexus generation. Just ordered the 6P so will definitely be doing this .

Great seeing this already. Coming from an S4 to the 64GB 6P. Will it be possible to relock the bootloader after installing a custom recovery or is the stock recovery required for the lock?
Sent from my SPH-L720 using Tapatalk

C4PO said:
Great seeing this already. Coming from an S4 to the 64GB 6P. Will it be possible to relock the bootloader after installing a custom recovery or is the stock recovery required for the lock?
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
AFAIK, locking bootloader has nothing to do with the recovery, but then again, I never locked a bootloader...

Pretty sure you'd need to flash stock recovery. It won't hurt anything to try it without stock recovery, but if it doesn't work then you'll know for sure why.

I'm not planning to mess around with it too much until a stock system file is available. I need a Plan B. Lol

Doesn't run for me. (Mac User)
Heres the terminal error
sh [Path to location]/6PMultiTool.v0.2/6PMultiToolv0.2-M.sh
[Path to location]/6PMultiTool.v0.2/6PMultiToolv0.2-M.sh: line 3: [Path to location]/6PMultiTool.v0.2/simple_curses.sh: No such file or directory
There doesn't seem to be a "simple_curses.sh" file in the tool directory that I can find. Hope you can get it figured out! Thanks for the awesome tool as well!

ryman222 said:
Doesn't run for me. (Mac User)
Heres the terminal error
sh [Path to location]/6PMultiTool.v0.2/6PMultiToolv0.2-M.sh
[Path to location]/6PMultiTool.v0.2/6PMultiToolv0.2-M.sh: line 3: [Path to location]/6PMultiTool.v0.2/simple_curses.sh: No such file or directory
There doesn't seem to be a "simple_curses.sh" file in the tool directory that I can find. Hope you can get it figured out! Thanks for the awesome tool as well!
Click to expand...
Click to collapse
Unfortunately I never got the chance to test the MAC version, finally I have a tester
From what I can see at a first look is that this simple_curses.sh is some leftover from when I experimented with some UI tricks for bash to try to simulate the looks of the batch version..
Can you please check this temporary version from here -> 6PMultiTool.v0.2.1.zip

[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 issuesI 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
DownloadGet 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 infoXDA: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][11][UNOFFICIAL] Blissrom 14.2

If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you and our team quite some time.
-Download the Catlog app from the Play Store.
-There is also a donate version which you can purchase to show appreciation.
-After downloading the Catlog app, go to the app settings, and change the log level to Debug.
-Clear all previous logs and take the exact steps to produce the error you are receiving.
-As soon as you receive the error (probably a force close), go straight into Catlog and stop the log recording.
-Copy and paste the entire log either to Hastebin or Pastebin
-Save the log, and copy and paste the link into the forum with a brief description of the error.
BlissRoms GithubBlissRoms GerritBlissRoms Device SourcesBlissRoms Kernel SourceDevice TreeDevice Tree (wahoo)
BlissRoms Website Bliss Blog BlissRoms FacebookBlissRoms TwitterBlissRoms InstagramBlissRoms Telegram GroupBlissRoms Announcements Telegram ChannelBliss Wiki
Donate:

Donate to Maintainer:

@jackeagle
@electrikjesus
@Rohanpurohit
@rwaterspf1
@ideaman924
@Makaveli_da_dev
@ElfinJNoty
@BitOBSessiOn
@customworx
@nilac
@sixohtew
@aclegg2011
@Roger.T
@T.M.Wrath
@kanttii
@REV3NT3CH
@techfreak243
@SuperDroidBond
@USA_RedDragon
@bcrichster
@DeadmanxXD
@krittin98
@blackscorpion
@TechExhibeo
@DroidBot
@Siphonay
@pacer456
@nitin1438
@theGeekyLad
@kunalshah912
@LordArcadius
@AryanAA
A huge thanks to Chainfire, CM/LineageOS, Android-x86, Jide, topjohnwu (Magisk) @farmerbb & all the other developers who work hard to keep all the great features coming!
We really appreciate all your knowledge & hard work!
Thank you for using Bliss! And as always: #StayBlissful

*Reserved*

Cant flash NikGapps on it, using the vanilla build (i prefer up to date GApps), NikGapps reports 0 free space on /system - seen this on a few ROMS...no idea why it wont let me install
Doing adb shell df -h /system after flash and reboot reports 1Gb free...but yet still NikGapps wont install on there
Same NikGapps (full, with config to cherrypick what i use) as i use on Proton, PixelExeprience
Back to Proton/PixelExperience for now
Edit/Update:
Looks like it may be a NikGapps build issue, im downloading a new one and will retest
Nope, that didnt do it either.

Just flashed the gappd build and things are working smooth and apps are getting restored as i write. Will monitor the performance and battery drain over the next couple of days.
Couldnt find active edge in here, hopefully it's added in future builds.

73sydney said:
Cant flash NikGapps on it, using the vanilla build (i prefer up to date GApps), NikGapps reports 0 free space on /system - seen this on a few ROMS...no idea why it wont let me install
Doing adb shell df -h /system after flash and reboot reports 1Gb free...but yet still NikGapps wont install on there
Same NikGapps (full, with config to cherrypick what i use) as i use on Proton, PixelExeprience
Back to Proton/PixelExperience for now
Edit/Update:
Looks like it may be a NikGapps build issue, im downloading a new one and will retest
Nope, that didnt do it either.
Click to expand...
Click to collapse
I think you need to check if the system_root partition is mounted or not. I faced that error too. Had to format the system partition into ext4 and then I could install opengapps and nikgapps as well. Currently I am on the vanilla build with opengapps (pico) installed on it.

RealOkabe said:
I think you need to check if the system_root partition is mounted or not. I faced that error too. Had to format the system partition into ext4 and then I could install opengapps and nikgapps as well. Currently I am on the vanilla build with opengapps (pico) installed on it.
Click to expand...
Click to collapse
I had to do the EXT2 to EXT4 trick on /data already because of the old storage = 0 issue, i wish someone would fix TWRP
I didnt check for system_root or notice it though, so ill look into it, cheers...

So no edge sense in this build?

RealOkabe said:
I think you need to check if the system_root partition is mounted or not. I faced that error too. Had to format the system partition into ext4 and then I could install opengapps and nikgapps as well. Currently I am on the vanilla build with opengapps (pico) installed on it.
Click to expand...
Click to collapse
Is there any benefit over gapps?

73sydney said:
Cant flash NikGapps on it, using the vanilla build (i prefer up to date GApps), NikGapps reports 0 free space on /system - seen this on a few ROMS...no idea why it wont let me install
Doing adb shell df -h /system after flash and reboot reports 1Gb free...but yet still NikGapps wont install on there
Same NikGapps (full, with config to cherrypick what i use) as i use on Proton, PixelExeprience
Back to Proton/PixelExperience for now
Edit/Update:
Looks like it may be a NikGapps build issue, im downloading a new one and will retest
Nope, that didnt do it either.
Click to expand...
Click to collapse
Always using for all roms without gapps this configuration and works everything fine.
Here me nikgapps.conf
# NikGapps configuration file
# visit https://nikgapps.com/misc/2020/11/22/NikGapps-Config.html to read everything about nikgapps
# If you are not sure about the config, just skip making changes to it or comment it by adding # before it
#InstallPartition=system
mode=install
# set WipeDalvikCache=0 if you don't want the installer to wipe dalvik/cache after installing the gapps
WipeDalvikCache=1
# set WipeRuntimePermissions=1 if you want to wipe runtime permissions
WipeRuntimePermissions=0
# Addon.d configs set them to 0 to skip the functionality
execute.d=1
mount.d=1
unmount.d=1
# Addon version (set it to 3 if you use lineageOs recovery, set it to 2 if you're using twrp recovery)
addon_version.d=2
# Following are the packages with default configuration
# Set Core=0 if you want to skip installing all packages belonging to Core Package
Core=1
>>ExtraFiles=1
>>GooglePlayStore=1
>>GoogleServicesFramework=1
>>GoogleContactsSyncAdapter=1
>>GoogleCalendarSyncAdapter=1
>>GmsCore=1
DigitalWellbeing=1
VancedManager=0
GoogleMessages=0
GoogleDialer=0
GoogleContacts=1
CarrierServices=1
GoogleClock=1
# Set SetupWizard=0 if you want to skip installing all packages belonging to SetupWizard Package
SetupWizard=1
>>SetupWizard=1
>>GoogleRestore=1
>>GoogleOneTimeInitializer=1
# Set Pixelize=0 if you want to skip installing all packages belonging to Pixelize Package
Pixelize=1
>>PixelSetupWizard=1
>>AndroidMigratePrebuilt=1
>>PixelTips=0
>>PixelConfigOverlays=1
GoogleCalculator=0
Drive=0
GoogleMaps=0
GoogleLocationHistory=1
Gmail=0
GooglePhotos=0
DeviceHealthServices=1
GoogleDuo=0
Velvet=1
GBoard=1
# Set PixelLauncher=0 if you want to skip installing all packages belonging to PixelLauncher Package
PixelLauncher=1
>>PixelLauncher=1
>>DevicePersonalizationServices=1
>>QuickAccessWallet=1
# Set GoogleFiles=0 if you want to skip installing all packages belonging to GoogleFiles Package
GoogleFiles=0
>>GoogleFiles=1
>>StorageManager=1
PlayGames=0
GoogleCalendar=0
MarkupGoogle=1
GoogleWallpaper=1
GoogleFeedback=0
GooglePartnerSetup=1
GoogleSounds=1
AndroidDevicePolicy=1
GoogleKeep=0
Books=0
Assistant=1
YouTubeMusic=0
GoogleRecorder=1
GoogleTTS=1
GoogleTalkback=1
DeviceSetup=1
AndroidAuto=0
# Set GoogleChrome=0 if you want to skip installing all packages belonging to GoogleChrome Package
GoogleChrome=1
>>GoogleChrome=0
>>WebViewGoogle=1
>>TrichromeLibrary=1
GoogleDocs=0
GoogleSheets=0
GoogleSlides=0
# Set CoreGo=0 if you want to skip installing all packages belonging to CoreGo Package
CoreGo=0
GoogleGo=1
AssistantGo=1
MapsGo=1
NavigationGo=1
GalleryGo=1
GmailGo=1

irmas5 said:
Always using for all roms without gapps this configuration and works everything fine.
Here me nikgapps.conf
# NikGapps configuration file
# visit https://nikgapps.com/misc/2020/11/22/NikGapps-Config.html to read everything about nikgapps
# If you are not sure about the config, just skip making changes to it or comment it by adding # before it
#InstallPartition=system
mode=install
# set WipeDalvikCache=0 if you don't want the installer to wipe dalvik/cache after installing the gapps
WipeDalvikCache=1
# set WipeRuntimePermissions=1 if you want to wipe runtime permissions
WipeRuntimePermissions=0
# Addon.d configs set them to 0 to skip the functionality
execute.d=1
mount.d=1
unmount.d=1
# Addon version (set it to 3 if you use lineageOs recovery, set it to 2 if you're using twrp recovery)
addon_version.d=2
# Following are the packages with default configuration
# Set Core=0 if you want to skip installing all packages belonging to Core Package
Core=1
>>ExtraFiles=1
>>GooglePlayStore=1
>>GoogleServicesFramework=1
>>GoogleContactsSyncAdapter=1
>>GoogleCalendarSyncAdapter=1
>>GmsCore=1
DigitalWellbeing=1
VancedManager=0
GoogleMessages=0
GoogleDialer=0
GoogleContacts=1
CarrierServices=1
GoogleClock=1
# Set SetupWizard=0 if you want to skip installing all packages belonging to SetupWizard Package
SetupWizard=1
>>SetupWizard=1
>>GoogleRestore=1
>>GoogleOneTimeInitializer=1
# Set Pixelize=0 if you want to skip installing all packages belonging to Pixelize Package
Pixelize=1
>>PixelSetupWizard=1
>>AndroidMigratePrebuilt=1
>>PixelTips=0
>>PixelConfigOverlays=1
GoogleCalculator=0
Drive=0
GoogleMaps=0
GoogleLocationHistory=1
Gmail=0
GooglePhotos=0
DeviceHealthServices=1
GoogleDuo=0
Velvet=1
GBoard=1
# Set PixelLauncher=0 if you want to skip installing all packages belonging to PixelLauncher Package
PixelLauncher=1
>>PixelLauncher=1
>>DevicePersonalizationServices=1
>>QuickAccessWallet=1
# Set GoogleFiles=0 if you want to skip installing all packages belonging to GoogleFiles Package
GoogleFiles=0
>>GoogleFiles=1
>>StorageManager=1
PlayGames=0
GoogleCalendar=0
MarkupGoogle=1
GoogleWallpaper=1
GoogleFeedback=0
GooglePartnerSetup=1
GoogleSounds=1
AndroidDevicePolicy=1
GoogleKeep=0
Books=0
Assistant=1
YouTubeMusic=0
GoogleRecorder=1
GoogleTTS=1
GoogleTalkback=1
DeviceSetup=1
AndroidAuto=0
# Set GoogleChrome=0 if you want to skip installing all packages belonging to GoogleChrome Package
GoogleChrome=1
>>GoogleChrome=0
>>WebViewGoogle=1
>>TrichromeLibrary=1
GoogleDocs=0
GoogleSheets=0
GoogleSlides=0
# Set CoreGo=0 if you want to skip installing all packages belonging to CoreGo Package
CoreGo=0
GoogleGo=1
AssistantGo=1
MapsGo=1
NavigationGo=1
GalleryGo=1
GmailGo=1
Click to expand...
Click to collapse
Dude, i know how to make a config file

Sui77 said:
So no edge sense in this build?
Click to expand...
Click to collapse
No Edge sense. And I have fallen back to Havoc for now, as the settings in this ROM is very agressive in killing apps even if they are idling in background like cpu or battery monitor apps.
Haven't faced that in audio or IM calls.

palimatix said:
No Edge sense. And I have fallen back to Havoc for now, as the settings in this ROM is very agressive in killing apps even if they are idling in background like cpu or battery monitor apps.
Haven't faced that in audio or IM calls.
Click to expand...
Click to collapse
Unfortunately ive noticed this too, across most current ROMs, a lot of background apps/processes getting killed, even if not optimized in battery optimization.
Case in point, and most notable, because it vibrates everytime it loses connection, is all the Galaxy Wear related apps/processes for my Active 2 watch. The ridiculous thing is that the processes die and the watch goes into standalone mode pretty much ONLY when youre actively using the phone. Even browsing a website will cause the watch dropout
Devs are being too aggressive in optimization or performance, yes you can alter these settings yourself with some fiddling, but shouldnt have to out of the box...
In better news, after a couple of days being stuck in the custom build system and NikGapps, the lovely dev fasttracked my stuck custom build and i have it downloading now, my custom build comes in at 740Mb, wont need a config file at all as it only has my cherrypicked apps that i use and should hopefully cause less storage issues than the full one at 1Gb

Just plain rude to make a thread one day after I built the bliss.
I will not make one with this.

Blackjubel said:
Just plain rude to make a thread one day after I built the bliss.
I will not make one with this.
Click to expand...
Click to collapse
I thought you had just made a test build...that you posted in the other thread...
Not sure this dev was aware?

So....still no go here
Still unable to get this to work, more work than ive ever put into trying to flash any ROM ever
Even with my new custom smaller NikGapps...
Process (from other ROM):
adb reboot bootloader
fastboot erase userdata && fastboot erase system_a && fastboot erase system_b
fastboot boot twrp-3.5.2_9-0-taimen.img (note i tried 3 other versions)
change filesystem on data and system (from) EXT4 to EXT2 and back to EXT 4 again
(all partitions mounted correctly - usually i just do all this blindly from my PC via command line and never look at the phone)
adb sideload Bliss-v14.2-taimen-UNOFFICIAL-vanilla-20210502.zip
adb reboot bootloader
fastboot boot twrp-3.5.2_9-0-taimen.img
adb sideload NikGapps-73sydney-arm64-11-20210504-signed.zip
errors out again about not enough room on system.....ffs....spent 2 days on this...not the same error as yesterday, now its clear the ROM doesnt leave enough room on /system
Getting tired of ROMS you cant actually put your own GApps on, this is now one of 3 current ROMS that error our when trying to do what people like me have done for eons...since the beginning of time, and Android
Back to something that works, for the second night in a row...
ROMS with a /system size issue that i will no longer test (unless someone wants to fix them):
BlissROM (this vanilla version)
Havoc
ArrowOS
Of course devs could make people like me wanting to use their own GApps redundant by updating their included G-Apps, because thats why i dont use GApps included builds, the GApps are always months out of date, and so apart from a massive zip download, then i have to download another 400-600Mb of updates from the App Store
At this point im going to stick between Proton (when thats fixed) and PixelExperience and stop testing other ROMs, wastes too much time

Blackjubel said:
Just plain rude to make a thread one day after I built the bliss.
I will not make one with this.
Click to expand...
Click to collapse
If you want to maintain it then I can just stop.

73sydney said:
So....still no go here
Still unable to get this to work, more work than ive ever put into trying to flash any ROM ever
Even with my new custom smaller NikGapps...
Process (from other ROM):
adb reboot bootloader
fastboot erase userdata && fastboot erase system_a && fastboot erase system_b
fastboot boot twrp-3.5.2_9-0-taimen.img (note i tried 3 other versions)
change filesystem on data and system (from) EXT4 to EXT2 and back to EXT 4 again
(all partitions mounted correctly - usally i jst do all this form my PC via command line and never look at the phone)
adb sideload Bliss-v14.2-taimen-UNOFFICIAL-vanilla-20210502.zip
adb reboot bootloader
fastboot boot twrp-3.5.2_9-0-taimen.img
adb sideload NikGapps-73sydney-arm64-11-20210504-signed.zip
errors out again about not enough room on system.....ffs....spent 2 days on this...not the same error as yesterday, now its clear the ROM doesnt leave enough room on /system
Getting tired of ROMS you cant actually put your own GApps on, this is now one of 3 current ROMS that error our when trying to do what people like me have for eons...
Back to something that works, for the second night in a row...
At this point im going to stick between Proton (when thats fixed) and PixelExperience and stop testing other ROMs, wastes too much time
Click to expand...
Click to collapse
Dude, just change filesystem on your data partition and install normally through twrp. It works. I am using the same. If not, then go for the gapps build or download the factory image that I have posted on sourceforge.

RealOkabe said:
Dude, just change filesystem on your data partition and install normally through twrp. It works. I am using the same. If not, then go for the gapps build or download the factory image that I have posted on sourceforge.
Click to expand...
Click to collapse
Please read my post again, where i clearly state i change the filesystem to EXT2 and then back to EXT4 on both data and system to properly mount them and have them correct size...thats not it, its the ROM
As i said, if devs want to build GApps included ROM's with up to date GApps, then im up for that....but i wont be downloading any GApps included ROMS that have GApps in them that are months old and then having to waste 400-600Mb on top of that out of my data allowance to update GApps from the Play Store (i cant be the only person annoyed by this). Unless devs want to pay my data bills, of course.
The entire reason i prefer GApps free builds...especially testing multiple ROMs is because it saves me data/money. I can download NikGapps once a month and flash them across multiple ROMs, where as if i downloaded GApps included ROM's (with out of data GApps), im wasting so much data/money it isnt funny...
3 x GApps(less) ROM's a month = @2.1 Gb
1 x NikGapps a month = @700Mb
Total = 2.8Gb
3 x GApps(included) ROM's a month = @3.5 Gb
3 x 400Mb updates for out of date GApps from Play Store = @1.2Gb
Total = 4.7Gb
Big difference, hope that makes it clear

Okay so since there is someone else who wants to maintain this rom, I will be stepping down from this. I will be back with some other rom. Thanks for trying it out. Do look forward to my next work.

@73sydney, I already talked about this before, but my advice was ignored
After flashing rom in both slots, flash nikgapps and if it gives an error about insufficient memory, then switch to another slot, reboot into twrp again and flash nikgapps again

[ROM][UNOFFICIAL][A11][F500,LS991,H81x,US991,VS986] LineageOS 18.1

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

[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 issuesKeep 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
SupportOf 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

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)

Develop Bugs

welcome