Develop Bugs

[ROM][SGT7-UT][20130515] Ubuntu Touch [DEV][RETIRED]

Code:
*** Disclaimer by cdesai
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Introduction
I'm starting this thread to see if DEVs and collaborators get motivated and help. I'm not really a DEV but...
Ubuntu Touch is still a WiP itself, and this is a Work-in-Progress of getting it to our SGT7 Tabs - P1000, P1000N/L/R/T/CDMA/etc
Click to expand...
Click to collapse
Features
Works: touch, wireless, camera...
Doesn't: audio, brightness, sensors, 3G/Mobile...
Click to expand...
Click to collapse
Installation instructions
Regular flash through CwM Recovery:
Wipe/Factory Reset
Flash cm-10.1-YYYYMMDD-UNOFFICIAL-p1.zip or cm-10.1-YYYYMMDD-UNOFFICIAL-p1c.zip
Flash quantal*.zip
Flash hdpi_overlay.zip
Click to expand...
Click to collapse
Changelog
UT ROM based on CM10.1 with humberos' kernel, p1 and p1-common. OS image directly from Ubuntu downloads.
Click to expand...
Click to collapse
Code:
Current changelog: 2013-05-15
[note] My second UT boot
[new] p1c build!
[changed] screen resolution and proportions (new hdpi_overlay.zip)
[fixed] screen and touch rotation, manual brightness.
2013-05-10
[note] My first UT boot.
[new] Thread created.
[changed] built and booted
[fixed] Now it boots!
Downloads
Base ROM
cm-10.1-20130515-UNOFFICIAL-p1.zip - fourth update!
cm-10.1-20130515-UNOFFICIAL-p1c.zip - fourth update! - NOT working - bad kernel without recovery. Reported by @sxfx
Ubuntu Touch Quantal from the MWC Demo:
quantal-preinstalled-phablet-armhf.zip
Ubuntu Touch Saucy:
saucy-preinstalled-touch-armhf.zip
Screen configs - changes screen resolution and proportions
hdpi_overlay.zip 20130515
Sources
https://github.com/sgt7-ut - maybe someday. :cyclops:
Mods/Addons/Themes/User Art
Ubuntu Touch Auto-debloater & Ubuntu Logo Welcome Screen
Click to expand...
Click to collapse
FAQ
The FAQ section in a thread is bound to grow over time... check for updates.
Q: How do I flash?
A: Learn that before coming here.
Q: How do I restore my {fill in here} ROM?
A: Learn that before coming here.
Q: How do I use ODIN?
A: Learn that before coming here.
Q: How do I use Heimdall?
A: Learn that before coming here.​
Click to expand...
Click to collapse
​
Links and References
Ubuntu for Tablets
Touch install
UT Porting Guide
UT Building
Quantal MWC Demo CD Images
XDA Ubuntu Touch General Porting Discussion Thread
XDA Ubuntu Touch Forum - For non-device specific stuff
How to use apt-get through ADB + Apache Proxy without Networking
Click to expand...
Click to collapse
Thanks To/Credits
Code:
* humberos, the latin kernel king.
* cdesai
...

Building Ubuntu Touch
First of all have your CM10.1 build up to date.. if you can't build CM10.1 then you shouldn't even try this.
[UPDATE 20130515]
Successful build for p1 and p1c!
Basically follow the Porting guide. Initialize the repo as instructed, using phablet-dev-bootstrap.
My draft for building... soon we will have the sgt7-ut repo that will do most of it for us.
Not necessarily in order.. you might have to start compiling untill you get the error and come back and check the steps again.
Code:
## our manifest
copy the roomservice.xml to .repo/local_manifests/
## clean
rm -rf out kernel
make installclean
make clean
* edit as porting guide:
kernel/samsung/aries/fs/proc/array.c
* add extra lines from the porting guide to the end of:
kernel/samsung/aries/arch/arm/configs/cyanogenmod_p1_defconfig
kernel/samsung/aries/arch/arm/configs/cyanogenmod_p1ln_defconfig
kernel/samsung/aries/arch/arm/configs/cyanogenmod_p1c_defconfig
* also change the following config in each of the 3 kernel configs:
CONFIG_TOUCHSCREEN_QT602240_ROT90=n
## prepare stuff
source build/envsetup.sh
breakfast p1
breakfast p1c
./get prebuilts in vendor/cm/
comment P1Parts, tvouthack and Torch from device/samsung/p1-common/device_base.mk
copy from your cm10.1 build - out/target/product/p1/obj/SHARED_LIBRARIES/libandroid_runtime_intermediates
copy from your cm10.1 build - out/target/product/p1c/obj/SHARED_LIBRARIES/libandroid_runtime_intermediates
?? cp out/target/product/p1/obj/UTILITY_EXECUTABLES/utility_make_ext4fs_intermediates/LINKED/make_ext4fs out/target/product/p1/obj/EXECUTABLES/make_ext4fs_intermediates/
?? cp out/target/product/p1c/obj/UTILITY_EXECUTABLES/utility_make_ext4fs_intermediates/LINKED/make_ext4fs out/target/product/p1c/obj/EXECUTABLES/make_ext4fs_intermediates/
Add chmod line in device/samsung/p1-common/init.p1-common.rc, like this:
# System server can control backlight brightness
chown system system /sys/class/backlight/s5p_bl/brightness
chmod 0666 /sys/class/backlight/panel/brightness
## Now build!
source build/envsetup.sh
breakfast p1
time make -j3 bacon # use -j1 to check for errors in their right order
breakfast p1c
time make -j3 bacon
.repo/local_manifests/roomservice.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="humberos/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-10.1" />
<project name="humberos/android_kernel_samsung_aries" path="kernel/samsung/aries" remote="github" revision="cm-10.1-dev" />
<project name="humberos/android_device_samsung_p1" path="device/samsung/p1" remote="github" revision="cm-10.1" />
<project name="humberos/android_device_samsung_p1c" path="device/samsung/p1c" remote="github" revision="cm-10.1" />
<project name="humberos/android_device_samsung_p1-common" path="device/samsung/p1-common" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="cm-10.1" />
</manifest>
Change ro.sf.hwrotation to 0 in build.prop!

reserved 3
reserved 3

Wow, thnx! I'm downloading!:beer:
send from my Nexus

:beer::thumbup:
Sent from my GT-P1000 using xda app-developers app

That is one of the ubuntu, unless my eyes are cheated by some spell

Nice Ubuntu Logo in CWM
Hi,
first test. Don't get nervous, while unpacking ubuntu file lasts (4.5 minutes)
Also be patient during boot, first time i thought the Tab went off.
ubuntu boots, i can activate the start menu, but no further actions.
Thank you for your great work, alroger and humberos!
cinq

So, I sort of flashed this and nothing happened. It's just a fresh CM installation. Am I supposed to build something on device?
Edit: had a brain fart, got it generally working.
Sent from my SCH-I510 using xda premium

alroger, try setting ro.sf.hwrotation to 0 (it's set from device/samsung/p1-common)
It should change the default orientation to landscape, and so you'll need to do a few other changes as well (we did them during initial 4.2 bringup, then reverted them for a better solution), so you revert the revert for the rest. (sensors and camera)

cdesai said:
alroger, try setting ro.sf.hwrotation to 0 (it's set from device/samsung/p1-common)
It should change the default orientation to landscape, and so you'll need to do a few other changes as well (we did them during initial 4.2 bringup, then reverted them for a better solution), so you revert the revert for the rest. (sensors and camera)
Click to expand...
Click to collapse
Yeah, if I set to 0, it's left-handed landscape. 180 makes it correct, but touch won't follow those rotations.
Could you point me in the right direction?

alroger said:
Yeah, if I set to 0, it's left-handed landscape. 180 makes it correct, but touch won't follow those rotations.
Could you point me in the right direction?
Click to expand...
Click to collapse
Keep it 0.
Next, in the kernel config, set CONFIG_TOUCHSCREEN_QT602240_ROT90 to n, it's set to y currently.
That should fix touchscreen.

cdesai said:
Keep it 0.
Next, in the kernel config, set CONFIG_TOUCHSCREEN_QT602240_ROT90 to n, it's set to y currently.
That should fix touchscreen.
Click to expand...
Click to collapse
Cool, it works!
Hey, isn't there a ROT180 to use to invert the landscape? Or can you point me to the right file to edit this ROT90 config?
EDIT: Found it.. gonna try hacking a new ROT180 config.
EDIT2: Yay, I did it! My first customized kernel config: CONFIG_TOUCHSCREEN_QT602240_ROT180

Have you fixed the touchscreen bug? Can you please reupload the recompiled cm?
Thanks!

UPDATE 20130515 it works!
Current changelog: 2013-05-15
[note] My second UT boot
[new] p1c build! let us know if it boots!
[changed] screen resolution and proportions (new hdpi_overlay.zip)
[fixed] screen and touch rotation
Building tips in Post #2.

Ubuntu Saucy
It works with the latest Ubuntu Sacy Salamander, but no wifi. Download link added.
Must edit /usr/bin/ubuntu-session manually in the ZIP and change:
Code:
# defaults
GRID_UNIT_PX=8
QTWEBKIT_DPR=1.0
FORM_FACTOR="tablet"
Don't use hdpi*zip on this one.

Something in display it's broken. Seems flipped (also the camera is flipped).
I'm setting up a DEV enviroment too, so I'll post updates.

UPDATE 20130515 rotation fixed! brightenss fixed!
dexterash said:
Something in display it's broken. Seems flipped (also the camera is flipped).
I'm setting up a DEV enviroment too, so I'll post updates.
Click to expand...
Click to collapse
Rotation fixed! New uploads!
Camera is aligned with then screen now.
Brightness fixed - uncheck Automatic brightness and you can choose your brightness.
Enough for today...

Is WiFi and mobile data working?
Sent from my GT-P1000 using xda app-developers app

Very cool to see this progressing.
Is there any reason why this is based on an old quantal based ut build?
Sent from my ST25i using xda app-developers app

areshinakya said:
Very cool to see this progressing.
Is there any reason why this is based on an old quantal based ut build?
Sent from my ST25i using xda app-developers app
Click to expand...
Click to collapse
No, the base ROM is the base for any UT. But as I said it's working only with that build. Saucy worked also but without wireless.. there are new daily updates for raring and saucy every day... gotta keep on trying.

[Q] How to add Sony Xpeira S binaries to AOSP rom build?

Hello
I'm newbie in building a rom. I do as http://source.android.com/source/building.html page of android
I'm stuck at the "Obtaining proprietary binaries" step
- I download Android source to the directory that I name it to be "android_src"
- I download Sony Xperia S's proprietary binaries from http://developer.sonymobile.com/knowledge-base/open-source/android-open-source-project-for-xperia-devices/already and I got the " vendor" folder which is not in the "android_src" folder.
How do I include the proprietary binaries into the my own AOSP rom?

anybody? please help

thsecmaniac said:
anybody? please help
Click to expand...
Click to collapse
Do pm to a developer.like abhinav2,or deadwar,op of carban rom
Sent from my LT26i using xda premium

thsecmaniac said:
Hello
I'm newbie in building a rom. I do as http://source.android.com/source/building.html page of android
I'm stuck at the "Obtaining proprietary binaries" step
- I download Android source to the directory that I name it to be "android_src"
- I download Sony Xperia S's proprietary binaries from http://developer.sonymobile.com/kno...droid-open-source-project-for-xperia-devices/already and I got the " vendor" folder which is not in the "android_src" folder.
How do I include the proprietary binaries into the my own AOSP rom?
Click to expand...
Click to collapse
Hi,
I would not recommend you to use the binaries on the Sony website as they are outdated. Instead, please have a look at this github - https://github.com/billchen1977?tab=repositories
billchen1977 has provided all the required stuff for building aosp. So basically you need to create a local manifest in .repo/local_manifests.
You can do that by following these steps -
Code:
cd .repo
mkdir local_manifests
gedit nozomi.xml
Now copy this code into the XML file -
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="kernel/sony/msm8x60" name="billchen1977/kernel_sony_msm8x60" remote="github" />
</manifest>
I have added only one repo (the kernel). Similarly add the other two repos also and then simply run repo sync and you should be able to build the ROM then.
Sent from my Xperia S using Tapatalk

What is it different between billchen1977's rom and Sony's rom except Sony's is older than billchen1977's? I'm curious
abcdjdj said:
Hi,
I would not recommend you to use the binaries on the Sony website as they are outdated. Instead, please have a look at this github - https://github.com/billchen1977?tab=repositories
billchen1977 has provided all the required stuff for building aosp. So basically you need to create a local manifest in .repo/local_manifests.
You can do that by following these steps -
Code:
cd .repo
mkdir local_manifests
gedit nozomi.xml
Now copy this code into the XML file -
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="kernel/sony/msm8x60" name="billchen1977/kernel_sony_msm8x60" remote="github" />
</manifest>
I have added only one repo (the kernel). Similarly add the other two repos also and then simply run repo sync and you should be able to build the ROM then.
Sent from my Xperia S using Tapatalk
Click to expand...
Click to collapse

thsecmaniac said:
What is it different between billchen1977's rom and Sony's rom except Sony's is older than billchen1977's? I'm curious
Click to expand...
Click to collapse
These files are known as the vendor blobs. They are proprietary files whose source code is not available to the public. Some of these vendor files are used by various components of the phone like the camera etc. The ones on the Sony website are very old so if you use them, it is quite possible that the camera might not function properly. As Sony released official updates, if I remember, they even fixed laggy 1080p recording. So it would be much better to use the latest blobs.
Sent from my Xperia S using Tapatalk

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

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
brought to you by the
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
****
These builds are for all G4 models: official unlocked and UsU'd devices
****
UsU? http://bit.do/unlockg4​
About /e/
/e/ is an a mobile ecosystem (ROM + onlines services) that:
is open source
is pro-privacy
is compatible with most existing Android applications
cares about usability
is as far as possible freed from shackles by Google and OEMs
already exists!
It’s the alternative to the Apple/Google duopoly on the smartphone.
... so again and just to be clear: /e/ is not just a ROM, it is more a complete privacy ecosystem and consists of:
an installable mobile operating system for smartphones, which is forked from Android and strongly “ungoogled”
a set of sorted and improved default open source applications
various online services that are linked to the mobile operating system, such as: a meta search engine for the web, drive (with synchronization), mail, calendar, notes, tasks.
Features
Based on LineageOS so a very stable base
microG fully pre-installed with Signature Spoofing in restricted mode!
All features described on the /e/ page: What is e
All features and fixes of my LOS 16 builds.
Finally I had the time to setup an own OTA server.. so my builds come with full OTA update support
... you know that thing which informs you that a new update is there and where you just click to download + install
Difference from pure /e/ or: why are the builds CUSTOM?
The /e/ app store has been removed completely (read the FAQ why I did this drastic change)
AuroraStore has been added (pls always use "anonymous" unless you need paid apps to avoid bans)
F-Droid has been added (The OpenSource alternative store. First search for any apps here!)
Dozens of F-Droid repositories are pre-installed (activate them with just a finger tip! That's needed to ensure you only get what you want)
added PhoneSky a patched Google playstore working with microG
added Lawnchair (latest from their TG group)
The above changes are the reasons why my builds are of the type "CUSTOM" and not "UNOFFICIAL".
This is according to the rules /e/ defined.
Known issues:
Keep in mind that this is brand new stuff so it may (still) contain unknown issues!
So back up regularly and frequently!
Check the current issues at the github tracker (feel free to help, provide logs etc!)
If you find a bug not listed, follow the instructions here and provide me with the logs: FAQ #1
Requirements
Your device need to be unlocked either officially (h815 international or h811) or by UsU
Your bootloader stack should be on lastest MM version for your model. That is e.g. 20p for the H815 models or 20x for H811.
So.. NO SUPPORT ON LOWER bootloader stacks then the latest MM version for your model
... and NO SUPPORT for the BETA v29A as well!!
-> for your convenience I have created TWRP flashable files for that !!!! (click)
Of course ensure you just use files for your model, your ARB and UsU'd or not. If unsure ask.
in particular that means this thread is for:
F500, H810, H811, H812, H815 (official unlocked or UsU'd), H819 , LS991, US991, VS986
Latest TWRP - PREVIEW build: click or SHRP build: click
Do a full Nandroid backup before doing anything!
Installation
This single very first step is for UsU'd devices only (SKIP when you have an official unlocked model):
If you have ever flashed the UsU baseband package: Clean flash the modem partition from your backup in TWRP.
If you do not know if you ever flashed it simply re-flash your modem partition again and you can be sure. This can't do any harm.
If you have no backup:
- TWRP flashable MM modems (N will not work)
Ensure your bootloader is current! You will have issues if you are not on the latest bootloader stack. Read the above Requirements topic to find a link to TWRP flashable files.
Full clean install as described here (FAQ "#2") is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash /e/
Optional (if you want root): Flash Magisk
Flashing OpenGapps ????? NO No no! you don't want that on a google-free phone! /e/ contains everything you need to live without Google! So flashing OpenGapps on /e/ is like using a bit more secure LOS but that's not the point of /e/. Either try without or go with LOS (imho).
Boot it (will take a bit on first boot!!! be patient!)
Enjoy the most easy way to have a privacy focused and google-free phone!
Download
OFFICIAL builds (new install or re-install):
https://doc.e.foundation/search?q=LG G4
CUSTOM builds (new install or re-install)
https://leech.binbash.rocks:8008/e-os/pie/
If you have /e/ installed already and just want to update to a newer release:
Android settings -> Updater (yes my CUSTOM builds have OTA support like OFFICIAL has!)
Note:
CUSTOM builds: Builds are updated as soon as possible. There is no build cycle.
Information pertaining to your device is displayed accordingly.
The current build is the latest for your device.
Changelogs
CUSTOM: posted in my Telegram build channel
OFFICIAL: https://gitlab.e.foundation/e/os/releases/-/releases
Support
Of course in this thread but also by Telegram. I have created a generic group for all stuff around Android : here
and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here
Credits
LineageOS (the base of /e/)
The /e/ foundation and all related devs making this experience possible!
The Suicide-Squirrel team (ThePiGuy, kessaras, steadfasterX)
aoleary
and more..
Sources
local build manifest
repo init manifest
XDA:DevDB Information
g4_eos-pie_custom, ROM for the LG G4
Contributors
steadfasterX
Source Code: https://gitlab.e.foundation/e
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
ROM Firmware Required: latest MM firmware for your model !
Based On: Lineage OS
Version Information
Status: Stable
Created 2020-08-03

faq
Frequently Asked Questions (FAQ)
Q #0: Why is the /e/ App store not included??? It is GREAT!
Mainly due to security and privacy concerns. Wth? I thought /e/ is secure and privacy focused? Yes it is but.. read on:
First of all the App store itself has no security or privacy issues. It is opensource and I see no issues with the app itself!
... the most important point for a smartphone is the availability of apps. I mean having a secure device which respects your privacy is great but it will have no chance to win when you cannot get easily apps on it.
... and the most dangerous part for a smartphone is installing apps because here is where Malware can easily step in! So whatever you do never install APK files from a website directly unless you can be 100% safe it is trustworthy.
It is all about trust again and when you look in the sources of the /e/ Apps store you find it connects to: cleanapk.org.
/e/ makes that not a secret though as you can read here.
So who is behind that cleanapk.org? Why is /e/ trusting them? While reading through the /e/ forums I found that this page hosts (as far as we know) apps mirrored from apkpure + fdroid.
.. and it's completely unclear who hosts that site and where is behind it. On the other site /e/ (Gael, the founder as well) states clearly they are not in any relation to that site. "They just using their api".
here some facts:
you cannot get the owner by a whois request
They have a info page here which just roughly describes where the apps are coming from and how
There is no detailed privacy statement or even an info if they keep your data GDPR compliant or not
No way for devs to get their apps removed or updated
The /e/ foundation clearly states they have no relationship to that repository of apps but some things are interesting aren't they:
IP's of /e/ and cleanapk are at least nearby
During an ongoing discussion about exactly that topic something took my attention: the welcome notification on api.cleanapk.org was exactly at that time: https://archive.is/U1E0y (I mean.... )
/e/ itself was audited several times by a site named "infosec-handbook" and of course even they find that app store at least "mysterious"
During that mentioned discussion and after pointing Gael to that - the welcome message suddenly changed to what it is today..
The full topic where even Gael is talking (not that friendly) is: here
TL;DR:
/e/ is providing apps (the most used way to get infected by malware) by an API which is at least questionable.
I do not say /e/ is doing questionable things and as said before the /e/ ROM is 100% trustworthy (otherwise I would not do any builds for it) but that cleanapk.org site is truly another story.
An interesting quote of Gael can make one read between the lines (I marked the interesting ones bold and cursive):
Some users have reported that they are using Aurora, [...] (context: we will never integrate this) because it’s infriging the play store terms of services.
For this, we have to use indirect mechanisms, that don’t infrige the play store TOS, and therefore, we are using a service that is not officially part of the /e/ project, and which is called cleanapk.org
On the long run, we other plans with partners, to offer something more transparent, but it’s too soon to talk about this.
Click to expand...
Click to collapse
Of course /e/ needs to ensure that what they are doing is 100% legal and offering an app repository like cleanapk.org is not.
My personal assumption is that /e/ is offering that repo - indirectly so not officially by the e.foundation itself.
A relation between is for sure nothing they want to have public as this would cause legal questions.
So the last question is:
Q: Why do I consider AuroraStore "better" then using cleanapk.org and so removed the /e/ apps store and adding AuroraStore instead?
A: Because I definitively know where the apps are coming from when using Aurora instead of /e/. Not just the app itself is OSS (like the /e/ one) the apps are coming directly from the play store instead of an unknown source.
Q #01: I want to report an issue. What is the proper way to do so?
I'm glad that you are asking: before doing so check the KNOWN ISSUES topic in the OP and ofc the other FAQ's listed here!
If you encountered a kernel panic follow FAQ #6 in this post instead.
If you have issues with "just" the boot process follow FAQ #7 for a very easy way to grab the boot logs.
if you have an audio issue follow FAQ #10 instead.
If your issue is not listed there click here to proceed:
If your issue is not listed there follow the directions here briefly and I may can fix it:
logcat GUIDE
Ensure you have done a full CLEAN install before doing so (refer to FAQ #2 for what that means).
Warning: NO SUPPORT when:
- magisk is installed (known to cause issues sometimes - regardless of the ROM or version)
- Xposed is installed (known to cause issues sometimes - regardless of the ROM or version)
If you have installed any of these UNINSTALL or better do a FULL CLEAN install (see FAQ #2) before doing anything else. Often enough these above causes several issues like battery draining, problems on booting and much more. Even when they may work properly you should re-produce your issue without them first and follow the above to grab the log.
Magisk is a great piece of software and besides that it is Open Source which SuperSu never was.
I just saying I do not "support" issues with LOS when you have Magisk installed. Why? It is (like Xposed) extendable with modules (made by whoever) and those can cause billions of issues.
Other then that magisk was sometimes the reason for battery drain etc. Magisk modifies the boot "process" and sits very deep in the system (which is needed to make it work ofc) but that has the potential to make a system/ROM unstable or result in strange behaviors.
so in order to support a specific issue I have to be sure the ROM is in a "clean" state, no magisk, no xposed.
Pro-Tip: set magisk to core functions only to see if an extension causes your issue or not.
Q #02: I want to install clean, how? What is a clean install? What is the recommended way to flash a new ROM version?
A clean install ensures that there are no leftovers from any previous install. One can say that there are 2 phases of a clean flash:
1) regular
2) full - when you (still) encounter issues
Usually the regular one is fully ok when flashing a new ROM version but if you encounter strange issues nobody else is reporting or if a release post is recommending it you should do a full clean install instead.
A regular clean install can be done like this:
WIPE -> Advanced -> select: System + Cache
Flash the ROM
reflash root addon/magisk if you want root
A full clean install needs 2 steps more then the regular:
follow the steps for regular clean
go back in WIPE -> touch Factory Reset and let it do its job
go back in WIPE -> touch the "FORMAT data" button and type "yes" to format the internal storage (you will LOOSE ALL YOUR DATA - obviously)
REBOOT -> Recovery
Flash the ROM
reflash root addon/magisk if you want root
It is absolutely recommended to create a backup before and COPYING IT to your PC(!) before doing the above.
Q #03: Are there any plans or a chance of official /e/ builds?
yes this in progress (as of April 2021) and so should happen somewhen in 2021
Q #04: Will this ROM support / pass SafetyNet?
When you install Magisk you can hide and so yes you might be able to pass SafetyNet. Which can change every day though because even when that might work atm you should note the following:
Magisk has its own protections to ensure you pass safetynet but this is something which will change one day and there is no known method yet to workaround that.
Q #05: It looks like the CPU cores 5 and 6 are disabled - how can I fix that?
TLDR;
There is no fix required! it is fully ok when those are idle. they get hot plugged whenever needed.
Details:
we have 2 clusters of CPU cores resulting in a Hexa-core CPU set: (4x1.4 GHz Cortex-A53 & 2x1.8 GHz Cortex-A57)
the big one (2 CPU cores - higher performance = more battery drain, more heat which potentially causing the: bootloop issue) and the little (4 CPU cores - less battery drain but a bit slower) are handled dynamically based on the load of your device.
the big cluster will run ONLY when it is NEEDED - i.e. high load.
so when you look closer: those are not DISABLED they are IDLE which is a big difference.
Q #06: I get a kernel panic or green/purple/blue screen how to grab logs for this?
When you encounter a kernel panic and you are able to reboot without taking out the battery (taking out the battery will erase RAM and so erase the needed logs):
1) reboot (without taking out the battery!) to either TWRP/SHRP or (if you have root access) to your ROM
2) grab everything need from here: /sys/fs/pstore/ (e.g. adb pull /sys/fs/pstore/)
If you don't have a pc near you can do it directly from the device as well:
Enable the terminal app in developer options or download any
Open the terminal app.
su
cd /sdcard/Download
tar czf pstore.tgz /sys/fs/pstore
Attach pstore.tgz to your post.
It is crucial important that you do this only after the reboot happened . It's not important "when" though - as long as the device stays powered on.
Developers note:
convert PMSG log (requires a linux system):
Code:
tr -cd '\11\12\15\40-\176' < pmsg-ramoops-0 | sed 's/TENS\s/\n/g' > readable-pmsg.txt
Q #07a: I get a kernel panic on boot or having other boot issues but the pstore log are empty! What should I do?
Q #07b: How can I provide a clean boot log?
Since a while there is a very easy way to provide debug logs for the boot process. Before my convenient logging you had to follow FAQ #1 to grab them and it was a bit of PITA for some users.
So here you go for a much easier way:
boot Android
once booted : reboot to TWRP/SHRP
when you have a bootloop instead: take the battery out just before the bootloop occurs, or better press the key combo to get into TWRP all the time to eventually get there directly
once in TWRP ensure that "Cache" is mounted in the "Mount" menu (if not mount it by ticking the box)
open a terminal on your PC and type:
Code:
adb pull /cache/debug/boot_lc_crash.txt
adb pull /cache/debug/boot_lc_full.txt
adb pull /cache/debug/boot_lc_kernel.txt
paste one by one to a paste service like https://del.dog/ , https://paste.systemli.org/ or https://paste.omnirom.org/
Q #8: upgrade your bootloader stack only?! Read here how:
Check the OP of this thread which has TWRP flashable files linked.
Q #9: Is there an /e/ specific FAQ?
Sure:
FAQ: click
Forum: click
HOWTOs: click (a great resource for all your first questions)
Q #10: issues with audio (e.g. echo's, silence on one or the other site, ..)? Read here how to provide a specific log for that:
Do the following steps:
1) Ensure you have adb set up on your PC, and have adb debugging and adb root enabled in developer options on your phone
2) Then perform the following (all one command)
On Linux:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver" && sleep 10 && adb logcat -b all |egrep -vi "(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)"
Click to expand...
Click to collapse
On windows:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver && sleep 10 && logcat -b all |egrep -vi '(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)' "
Click to expand...
Click to collapse
3) Then re-produce your audo issue and cancel the logcat from step 2 before hanging up!
4) Share the logcat output from the console screen using paste.omnirom.org
Q #11: I'm scared about that microG , I don't want to expose my phone so is this /e/ version a security risk?
First of all you need a lot of trust installing ANY custom ROM. A developer can do nasty things right? Besides that yes microG allowing to let apps act like as they are another app, also known as signature spoofing. This CAN be a good and a bad thing. Read on why my builds are different:
In general the microG patch is an all or nothing. A ROM which supports microG (i.e. signature spoofing) have that feature enabled, always.
The difference in my /e/ builds is that I am using the "restricted" option of signature spoofing so as long as you trust me you are as safe as without microG.
Q #12: I have graphic glitches / issues, what can I do?
My builds using skiaGL instead of OpenGL since a while. skia is the new and faster renderer coming with pie by default but it can cause graphic glitches in some applications and/or situations.
Is there any fix for skiaGL coming? No, details here .
To check if your current ROM version is using skiaGL do this:
Code:
adb shell getprop debug.hwui.renderer
If you get an empty result it means skiaGL is active.
If for any reason you wanna go back and enforce OpenGL you can do so by
temporary (immediately activated):
Code:
adb root (must be enabled in dev options)
adb shell setprop debug.hwui.renderer opengl
or make that change persistent:
Code:
boot TWRP
backup system
mount system
adb shell
echo "debug.hwui.renderer=opengl" >> /system/build.prop
sync
reboot
.-

Reserved

Awesome! Nice initiative! Cannot wait to test it when I get my hands on my old G4!

Thank you so much for this port!
No more tinkering with Magisk to stub Google services.
And such good news for the OTA!

Amazing work. I just came back to my G4 to set it up as an in car GPS and this is an amazing ROM for it.
It is very smooth, the device does not overheat, and location works very well.
Thank you Steadfasterx.

Man, this is AWESOME !
The most sustainable phone (well, second to the Fairphones, of course) with the best Google-alternative ROM… Could I ever dream of something better ? OTA updates, maybe ?
EDIT (after reading fully) :
Wow… OTA updates are there. You rock. You really do !!

Thank you for the love that you give to keep this community alive. I still cannot believe that you brought /e/ to LG G4 OTA is also very exciting news.
I also appreciate that you pre-install F-Droid (it is almost the first thing I need when booting to a new ROM).
I have been running your LOS ROMs for a long time. I have heard about /e/ before, and now, I am excited to give it a shot on my h815 device! Just hoping that it receives updates along with your LOS builds.
Good luck

Does encryption work?
I imagine that it's the same limitations as with LineageOS version, TWRP cannot decrypt, isn't it?

zeduck said:
Does encryption work?
I imagine that it's the same limitations as with LineageOS version, TWRP cannot decrypt, isn't it?
Click to expand...
Click to collapse
yes it does. the limitations is not in the ROM its in TWRP so yes you cannot decrypt.
.-

steadfasterX said:
yes it does. the limitations is not in the ROM its in TWRP so yes you cannot decrypt.
.-
Click to expand...
Click to collapse
Thanks for the quick and very clear response!
Just to be sure: as we have OTA updates on this ROM, it's completly usable to encrypt the phone, even if we cannot decrypt partitions with TWRP, right?

zeduck said:
Thanks for the quick and very clear response!
Just to be sure: as we have OTA updates on this ROM, it's completly usable to encrypt the phone, even if we cannot decrypt partitions with TWRP, right?
Click to expand...
Click to collapse
correct. flashing a ROM (and so an OTA) will just modify the /system partition which is always unencrypted so no issue on that.
.-

I encrypted the phone, but now I cannot boot anymore.
The prompt for decryption pop up correctly, and I am sure of the password.
What did I do wrong?

zeduck said:
I encrypted the phone, but now I cannot boot anymore.
The prompt for decryption pop up correctly, and I am sure of the password.
What did I do wrong?
Click to expand...
Click to collapse
do you have the latest bootloader stack for your device?
.-

steadfasterX said:
do you have the latest bootloader stack for your device?
.-
Click to expand...
Click to collapse
I thought I had.
I reflashed it just in case (h815_20p_bootloader_20p_modem_TWRP-flashable.zip).
It doesn't change anything.

zeduck said:
I thought I had.
I reflashed it just in case (h815_20p_bootloader_20p_modem_TWRP-flashable.zip).
It doesn't change anything.
Click to expand...
Click to collapse
Hm strange . Did you format (!) data before ? If not try it now pls (ofc that means your data is gone).
I may can re-check tomorrow but the last time it went without any issues here....
EDIT:
hm.. thats weird. I tested it on my h815 UsU'd device with a build from 16th of July and it works fine (no PIN set). After it booted I set a PIN and choose to ask that on boot. still working fine.
on my other H815 I tested it with the latest eOS build (PIN set before) and it does not work.
same for a LOS (!) build from July. still investigating..
EDIT2:
re-flashed latest version and set no pin, encrypt, bootloops. so there must had happen something between 16th july and august.. will check
EDIT 3:
uh I was a bit too impatient. it looped just 2 or 3 times then it boots up and is encrypted now! so a workaround is to set no pin/pass before the initial encryption. Once it is encrypted setting a key works fine...
so there must be something failing on initial encryption when a pin/pass is set.. will check
.-
Sent from my OnePlus 7T Pro using XDA Labs

steadfasterX said:
:
EDIT 3:
uh I was a bit too impatient. it looped just 2 or 3 times then it boots up and is encrypted now! so a workaround is to set no pin/pass before the initial encryption. Once it is encrypted setting a key works fine...
so there must be something failing on initial encryption when a pin/pass is set.. will check
.-
Click to expand...
Click to collapse
I confirm, I had a password set!
Meanwhile, I reflashed the ROM after having wiped everything.

zeduck said:
I confirm, I had a password set!
Meanwhile, I reflashed the ROM after having wiped everything.
Click to expand...
Click to collapse
yea the strange thing is now I cannot re-produce it anymore.. whatever I do it just works all the time now..
.-

zeduck said:
I confirm, I had a password set!
Meanwhile, I reflashed the ROM after having wiped everything.
Click to expand...
Click to collapse
wait! iirc there is a bug in TWRP: after you encrypted did you tried to decrypt in TWRP?
EDIT:
nah that wasn't it as well.. damn cannot reproduce the issue..
EDIT 2:
ok finally ..
I was able to reproduce it by flashing LOS 17 and encrypting there (which is failing atm). After that encrypting in Pie (LOS and /e/) fails as well.
Have moved that into an github issue #52
EDIT 3: @zeduck
the workaround is mentioned here: https://github.com/Suicide-Squirrel/issues_pie/issues/52#issuecomment-675457810
or wait until the next TWRP preview which allows to wipe it in the UI
.-

BREAKING NEWS
I've decided to create a Telegram group for all stuff around Android : here
and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here
New builds are cooking...
I have added a test in my jenkins build process to ensure that the unified device tree is working as it should.
Unifying our device tree makes it much easier to maintain and to add other not-yet added models - while it comes with the risk something goes wrong when it comes to blobs.
Nevertheless:
I would highly recommend doing the following (I have done that in my manual builds but you get it from jenkins - so there is a tiny little chance of bad luck .. ):
Pre-Cautions | Flashing instructions
Recommended: Backup (system, userdata in TWRP, your internal storage which contains your photos etc elsewhere)
Required: Do a "REGULAR CLEAN FLASH" (see bottom of this post)
Flash LOS - DO NOT choose to reboot afterwards - stay in TWRP.
TWRP menu: "Mount" --> choose "System"
From a terminal execute:
Code:
adb shell md5sum /system/etc/firmware/venus.mbn
Compare the value (last 4 characters is fully enough) with these:
If you flash:
h815, f500, h818, h819 it should be: d1f6fe863643b1e8d1e597762474928c
h810, h811, h812, ls991, us991, vs986 it should be: 78e5cf520d0de4a413ef1cfa7bbbe713
WARNING: If that checksum is NOT as it should be: DO NOT PANIC! simply FLASH the PREVIOUS LOS version BEFORE booting!. This will ensure you will not blow a fuse.
While the above test should be considered safe: If you are unsure about this procedure: WAIT before flashing until someone (or I) had done the above quick test from the builds jenkins is providing at my leech server.
Whenever an error occurs while flashing in TWRP (e.g "E1001: Failed to update system image.Updater process ended with ERROR: 7")
or if the above checksum does not match:
provide the recovery.log (FAQ #4 A)!!
... then flash the previous LOS version to get back to life - without harming your device.
if instead (as we all expect) all went well and you had opengapps before - ensure you reflash gapps
Cooking order & LIVE cooking view
H815
H811
H815 UsU
VS986
H812
H810
Live - View:
Normal view: https://shebang.binbash.rocks:8800/job/LG-G4/job/eOS-pie/job/Build all LGE-G4 models/workflow-stage/
Blue Ocean: https://shebang.binbash.rocks:8800/blue/organizations/jenkins/LG-G4/eOS-pie/Build all LGE-G4 models/ (click at the top line )
Noteworthy Changes:
Flashing method: "REGULAR CLEAN FLASH" is REQUIRED!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
(See the FAQ #2 of the LOS thread how to do this)
If you encounter any overheat or lagging issues follow this:
Code:
adb shell
logcat -b all -d | egrep -i "thermal|kill" > /sdcard/Download/log.txt
ps -A >> /sdcard/Download/log.txt
free -m >> /sdcard/Download/log.txt
logcat -b crash -d >> /sdcard/Download/log.txt
exit
adb pull /sdcard/Download/log.txt
Share the log.txt as an attachment of your reply (bc txt is fine for that) or - as usual - by your favorite paste service
Platform Security Patch: 2020-08-05
Due to some user reports I reverted the GPS updates by kessaras. Please let me know if GPS works better with this build or not.
New signing keys. You may now the "Trust" feature by LOS telling you if the build is trustworthy or not?! It checks if selinux is enforcing (it is in my builds) and if non-default signing keys (I sign my builds with my own ones) are in use.
The signing keys are required to allow installing OTA updates (it downloads, checks if the signature is mine, rejects if not or accepts and installs if).
Unfortunately I had to re-generate the signing keys that means you have to install this new build as usual in TWRP.
All builds after that one will fully support OTA. sorry for that
...... and more. Read "Full details"
Full details:
kernel: commits
g4-common tree: commits
g4 unified tree: commits
/e/OS: gitlab
Keep in mind that almost all pie ROM's sharing the same common device tree (or main parts of it), same model device trees and for sure the same kernel - so you can enjoy most fixes for any pie ROM available.. :victory:
ok enough of words, just one more thing:
flash and enjoy this privacy focused and totally Google-Free experience
.-

LineageOS 16 Unofficial Build

Hi,
I've managed to build the latest LineageOS 16 sources for the Oppo Find 7 and to my great surprise
after flashing the zip it works, so I thought to share it here. It is a ROM signed with userdebug keys
so I suspect a full wipe is needed before flashing it. Please report if you succeed without wiping!
It was built following the instructions at:
https://wiki.lineageos.org/devices/find7/build
The only different step was about proprietary blobs, rather than extracting them from the device I've added
https://github.com/TheMuppets/proprietary_vendor_oppo/tree/lineage-16.0
to ~/android/lineage/.repo/local_manifests/roomservice.xml
which looks like:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_device_oppo_find7" path="device/oppo/find7" remote="github" />
<project name="LineageOS/android_device_oppo_msm8974-common" path="device/oppo/msm8974-common" remote="github" />
<project name="LineageOS/android_kernel_oppo_msm8974" path="kernel/oppo/msm8974" remote="github" />
<project name="LineageOS/android_device_oppo_common" path="device/oppo/common" remote="github" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" />
<project name="TheMuppets/proprietary_vendor_oppo" path="vendor/oppo" remote="github" revision="lineage-16.0" />
</manifest>
After that building is as simple as running the following commands:
Code:
cd ~/android/lineage
repo sync
source build/envsetup.sh
breakfast find7
croot
brunch find7
I will eventually from time to time post new builds synced to latest lineage code as long as they do build without to much trouble.
I you find some bugs report them upstream to LineageOS, I don't have the knowledge nor the time to fix them.
Google Apps could be added from:
https://bitgapps.ga/
Enjoy
Download:
lineage-16.0-20210627-UNOFFICIAL-find7.zip
MD5SUM efeeb520cb7d0c383c3b33a872f696fa
lineage-16.0-20210703-UNOFFICIAL-find7.zip
MD5SUM 9b5c16dc1e17682d840b38282c2e334a
Feedback is appreciated!

I suspect that by reverting this commit :
https://github.com/LineageOS/lineage_wiki/commit/3c7f61f7c5e2353202427d6ff44587770b644ce3
and with a few more hacks even newer versions of android could be built for the Oppo Find7, any gurus out there that could help with this task?

Just tried to compile LineageOS 17.1 sources. I'm taking a look at the oneplus one device tree because they use the same SoC and it has already received even LineageOS 18.1. To compile successfully I need to repopick 279639 279641 279647 and 266411.
There is no MindTheGapps 10 so I tried OpenGApps pico but could not flash due to limited space.
Finally I tried to boot anyway but with no luck like @farmatito with LineageOS 16. So yes we need a guru, maybe @mikeioannina jump on the train again?

As mentioned by @farmatito BiTGApps can be installed. And i got it boot but i could not take a screenshot because of insufficient memory. screenrecording was possible though

Hi,
this is great news, I hoped this would be possible! Keep up with the good work.
With a little help this could be a fully usable phone as the OPO is still supported IIRC.
P.S.: in the next week when high season is over I hope to post a new build of LineageOS 16.

I think you must compile ones a migration build to switch from official to your builds without wiping data. I have done it in the past with this script from lineageos.org.

Hi,
I've read about the script but had not the time to implement it, also I suspect that it would not be a good idea
to migrate users to user-debug keys but that you need to generate a private key. If I would use my private key
for this I suspect that it would have security implications for the user. So best would be to generate a private key
for every user at installation time to protect his privacy and security but then where do we store this key? onto the
device itself seems not a good idea...
This crypto stuff scares me as I don't fully understand it.
Best would be every body compiles it on his computer and uses his own key.

I don't know why LineageOS never officially integrated LVM support, but for me having only 3GiB of internal storage was always a problem. 16GiB looks much better, I think. And since twrp officially supports lvm as well...

Yes. I know. OmniRom had LVM working and I still somewhere have the zip files to flash but the build system needs also to be patched (there was a patch for this from omnirom to lineage but I lost it). It scares me to touch that pile of code and I hate git. There would also be chinese partitioning, should have the the exe somewhere, but even for that the build system needs to be patched with the new partition offsets (and the kernel?).

At least encryption doesn't work on my LVM build at the moment and there is no auto-detection whether LVM or not. So the user can decide if he wants to use LVM or not.

I pushed the changes so maybe someone can pick this up.
Source Code
Whats NOT working:
Encryption
Screenshots saving
GApps installation
What you tell...
As I noticed the system file system is only 1024MiB but the system partition is 1324M so we are wasting 300M where we could install GApps.
Can someone please confirm that your system partition is also 1324M.
Run in TWRP
Code:
fdisk -l /dev/block/mmcblk0 | grep system
or attach full output

gcs88 said:
I pushed the changes so maybe someone can pick this up.
Source Code
Whats NOT working:
Encryption
Screenshots saving
GApps installation
What you tell...
As I noticed the system file system is only 1024MiB but the system partition is 1324M so we are wasting 300M where we could install GApps.
Can someone please confirm that your system partition is also 1324M.
Run in TWRP
Code:
fdisk -l /dev/block/mmcblk0 | grep system
or attach full output
Click to expand...
Click to collapse
fdisk -l /dev/block/mmcblk0 | grep system
14 294912 3006463 1324M 0700 system
Hi,
I will try to build with your repo as soon as I have some spare time, at the moment I am busy with another
project that has some kind of deadline.
Ciao,
farmatito

OK if anybody is interest in LineageOS 17.1 test builds you can find it here.
Code:
- Use at your own risk.
- I am not responsible for bricked devices, dead SD cards etc.
OK guy's I pushed the changes to gerrit and big thanks to @npjohnson for helping me out.

gcs88 said:
OK if anybody is interest in LineageOS 17.1 test builds you can find it here.
Code:
- Use at your own risk.
- I am not responsible for bricked devices, dead SD cards etc.
OK guy's I pushed the changes to gerrit and big thanks to @npjohnson for helping me out.
Click to expand...
Click to collapse
Thanks for your try. Installed 6th October build and basics are working well. Didn't test much but Wifi/Bluetooth/Phone are just fine. Update from last official Lineageos required flashing twice (first went straight back to recovery, second time booted to system).
Gapps (tried OpenGApps nano no chance: got code 64 in recovery). I will try Bitgapps next free time slot
Keep up with the good work.

gcs88 said:
OK if anybody is interest in LineageOS 17.1 test builds you can find it here.
Click to expand...
Click to collapse
Hello and many thanks for that rom.
I do have a question but don't know if it exactly belongs here. Maybe someone can tell from experience.
I did change to "Chinese unification storage method" using "X9007_Android5.0_16G_20150520" for a Find7a (X9006) as explained in this post.
My device storage now is 16 gigs, 4 already used after a clean install of Lineage OS 17.1.
Weird for me is the "mobile storage" which now shows
a corrupted sd-card which can not be formatted (seems to be like a left over from the previous partition, like its there but not) and
my external sd-card, which works fine
Is this normal that after using "Chinese unification storage method" that a "corrupted" sd-card stays in the system?
Thanks for any advice / clarification.

los 17 flashed using bitgapps and it works pretty fine. no screenshot saving issue
install procedure
- do unified storage procedure (LVM to Chinese unified storage thread)
- flash setup lvm and remove lvm zips (might not be required)
- wipe system, data and cache
- flash los 17, bitgapps then cm 13 unified patch
- boot up.
if you get wallpaper glitch on the lockscreen just change wallpaper.
color os stock cam doesnt work anymore on android 10. use bacon camera from playstore
open gapps pico may not work. it flashes normally but you either get bootloop, stuck on setup (wifi wont connect) or google play services will be broken.

morTimar said:
Is this normal that after using "Chinese unification storage method" that a "corrupted" sd-card stays in the system?
Thanks for any advice / clarification.
Click to expand...
Click to collapse
Yes, that's ok for Chinese partitions. I have this problem on all versions of lineage

Sounds like for ringtone, notification or alarm can not be selected.
"android.process.media keeps stopping"
But good trial. At least I was able to flash Android 10 on my old Find 7 just for fun

farmatito said:
Hi,
I've managed to build the latest LineageOS 16 sources for the Oppo Find 7 and to my great surprise
after flashing the zip it works, so I thought to share it here. It is a ROM signed with userdebug keys
so I suspect a full wipe is needed before flashing it. Please report if you succeed without wiping!
It was built following the instructions at:
https://wiki.lineageos.org/devices/find7/build
The only different step was about proprietary blobs, rather than extracting them from the device I've added
https://github.com/TheMuppets/proprietary_vendor_oppo/tree/lineage-16.0
to ~/android/lineage/.repo/local_manifests/roomservice.xml
which looks like:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_device_oppo_find7" path="device/oppo/find7" remote="github" />
<project name="LineageOS/android_device_oppo_msm8974-common" path="device/oppo/msm8974-common" remote="github" />
<project name="LineageOS/android_kernel_oppo_msm8974" path="kernel/oppo/msm8974" remote="github" />
<project name="LineageOS/android_device_oppo_common" path="device/oppo/common" remote="github" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" />
<project name="TheMuppets/proprietary_vendor_oppo" path="vendor/oppo" remote="github" revision="lineage-16.0" />
</manifest>
After that building is as simple as running the following commands:
Code:
cd ~/android/lineage
repo sync
source build/envsetup.sh
breakfast find7
croot
brunch find7
I will eventually from time to time post new builds synced to latest lineage code as long as they do build without to much trouble.
I you find some bugs report them upstream to LineageOS, I don't have the knowledge nor the time to fix them.
Google Apps could be added from:
https://bitgapps.ga/
Enjoy
Download:
lineage-16.0-20210627-UNOFFICIAL-find7.zip
MD5SUM efeeb520cb7d0c383c3b33a872f696fa
lineage-16.0-20210703-UNOFFICIAL-find7.zip
MD5SUM 9b5c16dc1e17682d840b38282c2e334a
Feedback is appreciated!
Click to expand...
Click to collapse
地址怎么用

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

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
About LineageOS:
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
​**** These builds are for both: official unlocked and UsU'd devices **** ​UsU? http://bit.do/unlockg4​
Requirements
Your device need to be unlocked either officially (h815 international or h811) or by UsU
Your bootloader stack should be on MM 20p (20x for H811) or higher! (see FAQ #8 for how to upgrade your bootloader stack witbout lgup).
.... and for your convenience I have alternatively created TWRP flashable files for that !!!! (click)
in particular that means this thread is for:
F500 (UsU'd), H810 (UsU'd), H811, H812 (UsU'd), H815 (official unlocked or UsU'd), H819 (UsU'd), LS991 (UsU'd), US991 (UsU'd), VS986 (UsU'd)
Latest SHRP build: click
or latest TWRP - PREVIEW build: click
Do a full Nandroid backup before doing anything else!
Installation
This single very first step is for UsU'd devices only:
If you have ever flashed the UsU baseband package: Clean flash the modem partition from your backup in TWRP.
If you do not know if you ever flashed it simply flash your modem partition again and you can be sure. This can't do any harm.
If you have no backup: TWRP flashable MM modems (N might not work)
Full clean install as described here (FAQ "#2") is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash this ROM
Optional (f-droid is already included): Flash GApps (11.0 - ARM64) if you like to use google apps
Optional (if you want root): Flash Magisk
Boot (will take a bit on first boot!!! but no longer then a few minutes)
Enjoy
Features
Pure LineageOS ROM experience
F-Droid included (Open Source alternative to Google Play)
Like with all my builds: OTA support included
Known issues:
Keep in mind that this is brand new stuff so it may (still) contain unknown issues! So back up regularly and frequently!
Check the current issues at the github tracker (feel free to help, provide logs etc!)
If you find a bug not listed, follow the instructions here and provide me with the logs: FAQ #1
Download
Get your builds from my leech server: https://leech.binbash.rocks:8008/lineage/18.1
Note:
Builds are updated as soon as possible. There is no build cycle. I build when I build (usually when a new security patch has been released at least).
Information pertaining to your device is displayed accordingly.
Changelogs
see commits at github or ideally you join my matrix or telegram groups (see topic "Support")
Credits
LineageOS
aoleary (for the whole a11 bringup!)
DevUt (for nothing)
and more..
Sources
build manifest
Support
Post in this thread
Quick support by [Matrix] || build notification by [Matrix]
Quick support by Telegram: sfX_Android || build notification in sfX_ci

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

reserved - not sure for what

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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