[ROM][UNOFFICIAL][O][UsU] LineageOS 15.1 [H815] DEPRECATED

[ROM][UNOFFICIAL][O][UsU] LineageOS 15.1 [H815] DEPRECATED - G4 Android Development

Reserved

Hey! I'm using it and it works flawlessly except 1 thing for me. I use bt calls much but now it has background noise as mentioned in known issues section. I can live without it but I hope you to solve this problem. Is there anything I can do for help? Thanks again @steadfasterX

emrtnl said:
Hey! I'm using it and it works flawlessly except 1 thing for me. I use bt calls much but now it has background noise as mentioned in known issues section. I can live without it but I hope you to solve this problem. Is there anything I can do for help? Thanks again @steadfasterX
Click to expand...
Click to collapse
Thanks for offering your help but unfortunately you can't do anything at the moment. I'm working on it at highest priority because I need it by myself but this issue is absolutely a nightmare and not easy to fix
Sent from my LG-H815 using XDA Labs

Thank You!
First of all, THANK YOU @steadfasterX for your work. I'm so happy there are still active developers for the G4, i'm finally free from the LG's claws.
I'm currently running the latest version of LOS available and here's a list of bugs/errors I found:
- I can't find/connect to 5GHz Wireless networks;
- The torch tile isn't working;
- Feels like even 2.4Ghz wi-fi connections are slowed down;
- SeLinux is permissive;
- Not an error, but I coudn't get Floatify to work on my lockscreen, guess it is not compatible with Oreo yet.
I didn't have issues with bluetooth media as some people had, though. There's no background noise
I hope this feedback help you somehow

igorgpsouza said:
First of all, THANK YOU @steadfasterX for your work. I'm so happy there are still active developers for the G4, i'm finally free from the LG's claws.
I'm currently running the latest version of LOS available and here's a list of bugs/errors I found:
- I can't find/connect to 5GHz Wireless networks;
- The torch tile isn't working;
- Feels like even 2.4Ghz wi-fi connections are slowed down;
- SeLinux is permissive;
- Not an error, but I coudn't get Floatify to work on my lockscreen, guess it is not compatible with Oreo yet.
I didn't have issues with bluetooth media as some people had, though. There's no background noise
I hope this feedback help you somehow
Click to expand...
Click to collapse
BT music is ok but calls has that bad noise.

Thanks for building this. Think I prefer Lineage to AOSCP.
Just a couple of issues that I have noticed so far.
I have the same problem on this ROM that I had using AOSCP. I tried to change the lockscreen to pattern during the initial setup wizard but it crashed and next time round I just skipped that step. Now when I try and set my lockscreen it just crashes the settings app.
Also torch tile doesn't work in the quick settings panel.

Rich Rich said:
Thanks for building this. Think I prefer Lineage to AOSCP.
Just a couple of issues that I have noticed so far.
I have the same problem on this ROM that I had using AOSCP. I tried to change the lockscreen to pattern during the initial setup wizard but it crashed and next time round I just skipped that step. Now when I try and set my lockscreen it just crashes the settings app.
Also torch tile doesn't work in the quick settings panel.
Click to expand...
Click to collapse
torch tile --> check the Known Issues in the OP for a workaround
regarding the settings crash: without logs no one can help you
adb shell
su
logcat -b all -c
logcat -b all
(now immediately reproduce the crash)
ctrl+c to cancel
Click to expand...
Click to collapse
copy the whole console output and paste it at http://bpaste.net (ensure you set the dropdown there to never)

steadfasterX said:
torch tile --> check the Known Issues in the OP for a workaround
regarding the settings crash: without logs no one can help you
copy the whole console output and paste it at http://bpaste.net (ensure you set the dropdown there to never)
Click to expand...
Click to collapse
https://bpaste.net/show/b78884ff63dc
---------- Post added at 09:42 AM ---------- Previous post was at 09:01 AM ----------
Just realised I wasn't rooted so went and flashed SuperSU.
Do you need me to produce another log with root?

Rich Rich said:
https://bpaste.net/show/b78884ff63dc
---------- Post added at 09:42 AM ---------- Previous post was at 09:01 AM ----------
Just realised I wasn't rooted so went and flashed SuperSU.
Do you need me to produce another log with root?
Click to expand...
Click to collapse
no. all good.

Rich Rich said:
https://bpaste.net/show/b78884ff63dc
---------- Post added at 09:42 AM ---------- Previous post was at 09:01 AM ----------
Just realised I wasn't rooted so went and flashed SuperSU.
Do you need me to produce another log with root?
Click to expand...
Click to collapse
please do a backup in TWRP
then flash this TEST kernel in TWRP: http://leech.binbash.it:8008/kernel...ental/h815_usu_los_boot_TEST-build-1-oreo.zip
try again to access the settings screen

steadfasterX said:
please do a backup in TWRP
then flash this TEST kernel in TWRP: http://leech.binbash.it:8008/kernel...ental/h815_usu_los_boot_TEST-build-1-oreo.zip
try again to access the settings screen
Click to expand...
Click to collapse
Same error again. Here's log;
https://bpaste.net/show/2290419a8aee

Rich Rich said:
Same error again. Here's log;
https://bpaste.net/show/2290419a8aee
Click to expand...
Click to collapse
ok I have my h815 UsU'd as well and I cannot reproduce your issue.
Do you have tried to do a clean flash (means format system! --> FORMAT data! --> flash ROM) ?
Hint: obviously this will delete ALL your internal storage so take care of that and I recommend to use the app FlashFire for the backup of your internal storage before doing the above
.

steadfasterX said:
ok I have my h815 UsU'd as well and I cannot reproduce your issue.
Do you have tried to do a clean flash (means format system! --> FORMAT data! --> flash ROM) ?
Hint: obviously this will delete ALL your internal storage so take care of that and I recommend to use the app FlashFire for the backup of your internal storage before doing the above
.
Click to expand...
Click to collapse
Just tried that. Still the same.
Tried it twice, once as you said then again by picking all the wipe options. If I try set a password or code it will crash then ask me to re-enter the password which always fails.
Think I'll just use it without a lockscreen.

New build up
Happy leeching
@Rich Rich try that one too. Its really strange that it does work here and for you not. what firmware version is your bootloader stack?
Sent from my LG-H815 using XDA Labs

steadfasterX said:
New build up
Happy leeching
@Rich Rich try that one too. Its really strange that it does work here and for you not. what firmware version is your bootloader stack?
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Just flashed that and it's the same. My device is an import from Taiwan, so originally on the TWN firmware is that makes a difference.
How do I check the bootloader stack? I used the UsU guide and flashed the files given there.

Rich Rich said:
Just flashed that and it's the same. My device is an import from Taiwan, so originally on the TWN firmware is that makes a difference.
How do I check the bootloader stack? I used the UsU guide and flashed the files given there.
Click to expand...
Click to collapse
and what was the exact firmware version you were on before flashing UsU?
you can use SALT and check "Firmware (system)" in the main screen. its not 100% but we will see.
if you have followed the unlock guide you would have a backup of that. Then its enough to do this (requires Linux/FWUL):
Open a terminal in the directory where you have your SALT backup before UsU'd.
Then:
Code:
strings misc.bin | grep LG
and paste the whole output

steadfasterX said:
and what was the exact firmware version you were on before flashing UsU?
you can use SALT and check "Firmware (system)" in the main screen. its not 100% but we will see.
if you have followed the unlock guide you would have a backup of that. Then its enough to do this (requires Linux/FWUL):
Open a terminal in the directory where you have your SALT backup before UsU'd.
Then:
Code:
strings misc.bin | grep LG
and paste the whole output
Click to expand...
Click to collapse
I've attached a screenshot of my SALT window. Hope this shows the info needed.

Rich Rich said:
I've attached a screenshot of my SALT window. Hope this shows the info needed.
Click to expand...
Click to collapse
you know that you are using an outdated version of SALT? current is 3.16 atm.
now check the backup files as mentioned.
.

steadfasterX said:
you know that you are using an outdated version of SALT? current is 3.16 atm.
now check the backup files as mentioned.
.
Click to expand...
Click to collapse
Don't know where the backup files are stored. I just have SALT installed in a standalone VMWare Linux machine, I'm not Linux literate so not sure where to start looking for the files. What's the default backup location?

Related

[ROM][H815][6.0|MM][UNOFFICIAL] Lineage OS 13.0 for LG G4

FAQ
1. Q: Encryption is not possible?
A: if the GUI for encrypting the device is not working:
Its highly recommended to backup all your data including the internal storage (I recommend FlashFire or / and Titanium)
Flash my screenlock fix (search here at XDA) in TWRP.
Reboot to android.
ensure that you met all usual requirements (battery, screen lock set) and then open a terminal or adb shell. Type:
vdc cryptfs enablecrypto inplace pin 1234
Replace 1234 with your desired pin ofc.
sfX

Reserved

Hi steadfasterX !
Thanks for keeping this alive ! I'm still on an old 13.0 version, it runs fine ATM.
steadfasterX said:
the kernel has security bugs which need to be addressed
Click to expand...
Click to collapse
Could you please be more precise on this ?
Where those bugs also in genesixx build, or are they specific to your build ?
Are these bugs LOS specific, or are they AOSP related ?
Thanks !

thewild said:
Hi steadfasterX !
Thanks for keeping this alive ! I'm still on an old 13.0 version, it runs fine ATM.
Could you please be more precise on this ?
Where those bugs also in genesixx build, or are they specific to your build ?
Are these bugs LOS specific, or are they AOSP related ?
Thanks !
Click to expand...
Click to collapse
its the same source then the official build (and so genessix) used so it should work the same way but as my device is broken atm and I await repair I cannot test it..
Last time I checked the security patches in my build got increased to July 2017 where the latest official ones had June..
so afaik there should be no critical issues in Android but the kernel is last time updated in May 2016 (should be the same for genessix builds).
My plan is maybe to integrate the Llama kernel and backport fixes from the 14.x tree.
don't expect that this happen in the near future (we can hope though) because atm I'm quite busy with my unofficial unlock stuff.
.

OK I'll keep an eye on this thread then.
Good luck !

Any tester reports?

Netsab said:
Any tester reports?
Click to expand...
Click to collapse
Yes.. I use that ROM with my unofficial unlock testers. Atm I cannot test cell service but it boots up fine, WiFi, cam etc works fine.
sfX
Sent from my LG-H815 using XDA Labs

Hi,
I can't make encryption work.
Can you write a procedure to use it with this ROM, please?
What I did:
- Install TWRP latest version
- Install latest nightly
- Remove gate keeper (using this)
- Launch encryption
What happened:
- Device reboot, display a green android on a black screen for a second, then reboot again try to boot on LineageOS but it froze after maybe a minute.
- I put off the battery and reboot the phone, that boot normally (data not encrypted but not corrupted either).
Thanks by advance

zeduck said:
Hi,
I can't make encryption work.
Can you write a procedure to use it with this ROM, please?
What I did:
- Install TWRP latest version
- Install latest nightly
- Remove gate keeper (using this)
- Launch encryption
What happened:
- Device reboot, display a green android on a black screen for a second, then reboot again try to boot on LineageOS but it froze after maybe a minute.
- I put off the battery and reboot the phone, that boot normally (data not encrypted but not corrupted either).
Thanks by advance
Click to expand...
Click to collapse
thx for testing..
yea I rem that there was a "trick" .. Could you try this build pls: http://droid.binbash.it:58885/h815/lineage-13.0-20170912-UNOFFICIAL-h815.zip
It includes an insecure kernel which will allow to debug.
Factory Reset in TWRP
Flash in TWRP
Boot Android
Enable encryption
when it reboots open a terminal and type (linux or FWUL): while true; do adb logcat ;done
on windows ensure that once the logcat aborts that you restart it immediately again!! and use just adb logcat
if using windows or linux: ensure the terminal buffer is big enough bc thats a a lot to handle.. (go into the settings of the cmd or terminal and set it to a very high value. e.g. 5000000)
let it bootloop and boot into Android again (logcat should run all the time)
CTRL+C when its completed with the above
copy & paste the whole stuff in a text file and attach it here
sfX

Are there any special modifications that would make it work?
Because I use this ROM as a daily driver and I would appreciate not to backup and reflash several times
If not, I will take the time to test this weekend.

zeduck said:
Are there any special modifications that would make it work?
Because I use this ROM as a daily driver and I would appreciate not to backup and reflash several times
If not, I will take the time to test this weekend.
Click to expand...
Click to collapse
without logs I cannot say anything for sure...
It may can be solved by just typing the encrypt command over adb or it requires to modify the ROM..
If you like you can try the following but keep in mind that having a complete Backup is a good idea always and when I say complete I mean including internal storage which is not be backuped by TWRP!! Use e.g FlashFire app to accomplish this. I would take a TWRP backup for all (use my latest beta!!!) and then FlashFire to backup internal storage.
Encryption often fails to a wrong formatted data partition so this can be a reason as well.
Try this:
Backup as described above
In TWRP select wipe - advanced - press "Format data" button to format the data partition
Boot android
set a pin or password for the lock screen!
Encrypt
If succeeded restore backup with FlashFire
As always there is a risk and it requires some time so I would not recommend to do this on a busy day.. as you say at the weekend fe.
Then we can try to use the adb commands and if that doesn't work as well the logcat..
sfX
Sent from my LG-H815 using XDA Labs

Hi !
I gave a try with lineage-13.0-20170918-UNOFFICIAL-h815.zip that I dirty-flashed over my previous lineage-13.0-20170204-UNOFFICIAL-h815 version.
Everything went fine (I had to replace the su zip/app though), except that satellite location would not work (network location was fine) : I kept getting
Code:
QCOM PowerHAL : Failed to acquire lock.
in logcat.
I'll give another try with the latest lineage-13.0-20170927-UNOFFICIAL-h815.zip.
If that fails too, I guess I'll have to clean-flash it then.
EDIT :
Bad news : after a clean flash, I keep getting
Code:
QCOM PowerHAL : Failed to acquire lock.
in logcat.

No GPS?! Kind of annoying bug... I'm still in 20170608 build and that news don't make me want to updated. I use GPS everyday, so this is very annoying

Netsab said:
No GPS?! Kind of annoying bug... I'm still in 20170608 build and that news don't make me want to updated. I use GPS everyday, so this is very annoying
Click to expand...
Click to collapse
After flashing several successive versions of that ROM, I discovered that version lineage-13.0-20170813-UNOFFICIAL-h815.zip seems to be the last one with satellite location working fine.
Starting from lineage-13.0-20170814-UNOFFICIAL-h815.zip, satellite location stops working. I guess something is broken in that build.
@steadfasterX :
Can you look and see what's happened with 20170814 ? Thanks !
@Netsab :
You can safely upgrade to 20170813.

breversa said:
After flashing several successive versions of that ROM, I discovered that version lineage-13.0-20170813-UNOFFICIAL-h815.zip seems to be the last one with satellite location working fine.
Starting from lineage-13.0-20170814-UNOFFICIAL-h815.zip, satellite location stops working. I guess something is broken in that build.
@steadfasterX :
Can you look and see what's happened with 20170814 ? Thanks !
@Netsab :
You can safely upgrade to 20170813.
Click to expand...
Click to collapse
Thanks you, I'll try.

breversa said:
After flashing several successive versions of that ROM, I discovered that version lineage-13.0-20170813-UNOFFICIAL-h815.zip seems to be the last one with satellite location working fine.
Starting from lineage-13.0-20170814-UNOFFICIAL-h815.zip, satellite location stops working. I guess something is broken in that build.
@steadfasterX :
Can you look and see what's happened with 20170814 ? Thanks !
@Netsab :
You can safely upgrade to 20170813.
Click to expand...
Click to collapse
thanks for your report. btw a dmesg is very helpful in these cases but the above should be fixed on next build.
next build will also have all proprietary stuff upgraded to v20p.
sfX
EDIT
new build is up
.

Hey sfX,
When trying to dirty-flash 20170930 over 20170813, the phone gets stuck on the boot animation (for over 30 minutes).
I did not try to clean-flash it though ; I thought I'd let you know first.

Sir SteadfasterX!
I use Unofficial 13.0-20170625-UNOFFICIAL-h815 as a daily driver and it never crashed once. I will try yours in near future, beginning with a dirty flash (but with a backup in case).
My question is, do the Bluetooth APT-X include in this rom?
One of my other phones Sony Z5 (modded stock) includes from factory an APT-X notifier, whenever it connects to a Bluetooth with APT-X I get a toast message that the device using "BLUETOOTH apt-x".
I see in Nougat 7 that it is possible to check in "developer mode" which Bluetooth protocol that currently is in use.
[Request] It would be nice if you could pick Bluetooth APT-X drivers/codec from above version of LinageOS14
Thank you very much!
I have attached the spoken AptxNotifier.APK from Sony z5 Marshmallow

datorprofessor said:
Sir SteadfasterX!
I use Unofficial 13.0-20170625-UNOFFICAIL-h815 as a daily driver and it never crashed once. I will try yours in near future, beginning with a dirty flash (but with a backup in case).
My question is, do the Bluetooth APT-X include in this rom?
One of my other phones Sony Z5 (modded stock) includes from factory an APT-X notifier, whenever it connects to a Bluetooth with APT-X I get a toast message that the device using "BLUETOOTH apt-x".
I see in Nougat 7 that it is possible to check in "developer mode" which Bluetooth protocol that currently is in use.
[Request] It would be nice if you could pick Bluetooth APT-X drivers/codec from above version of LinageOS14
Thank you very much!
I have attached the spoken AptxNotifier.APK from Sony z5 Marshmallow
Click to expand...
Click to collapse
Better wait until I fixed the current nightlies..
nice app btw. when all is fixed i may take a look into it
Sent from my LG-H815 using XDA Labs

[UNOFFICIAL][PRE-ALPHA][7.1.2][H930] LineageOS 14.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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Code:
#include "std_disclaimer.h"
/*
* Your warranty is 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.
*/
Working
Boot
Mobile data
Cam (pics only)
flashlight
fingerprint
sdcard is recognized/mounted
Unknown/Untested
GPS
NFC
calls/sms (should work i guess, because data works)
audio (cant test that in class )
Issues
USB
Wifi
Bluetooth
Recording
Brightness change
Everything i forgot probably
As you can see on the "Working" list, this is a highly experimental build, flash at your own risk, and don't come crying to me if it should brick anything (it didn't for me, but seeing from the TWRP Thread the V30 can be picky).
Dont forget to make a backup!!!
If you want to report any bugs, NEVER do it without providing logs. I can't try to fix things without logs.
Helpful log commands:
logcat (usage: e.g. logcat > /sdcard/logcat.txt )
dumpsys (usage: e.g. dumpsys SurfaceFlinger > /sdcard/dump_sf.txt)
dmesg (usage: e.g. dmesg > /sdcard/dmesg.txt , might need root)
for more examples on how to use the commands, either google (do that first) or ask (only do this if you already googled how to use those commands).
FAQ
USB isn't working. How do I get logs?
In the ramdisk theres a nice little script which will print the logcat to /data/ramoops/cm14.1_<number>_logcat_<date/time>.txt
The logcat is many many hundreds of MB in size, why?
Its currently spammed with something like this:
Code:
E/QMI_FW ( 674): xport_reg Failed for service_id=0x35 version=0x1001 on 15
Replace
Code:
[0-9][0-9]-[0-9][0-9] [0-9][0-9]:[0-9][0-9]:[0-9][0-9].[0-9][0-9][0-9] E/QMI_FW ( [0-9][0-9][0-9]): xport_reg Failed for service_id=0x35 version=0x1001 on [0-9]*[0-9]
in the log with your favorite editor which can use regex with nothing (or delete all those lines if you have that option)
Is there another way to get some logs?
In Developer Options, turn on "Local Terminal", and get a logcat or other logs with that.
The screen glitches, is there a way to fix this?
I hope so, working on this too.
After restoring my backup with TWRP, my phone won't recognize my PIN (not SIM PIN). What todo now?
Just follow the guide on here. Afterwards you have to setup your PIN again (also Fingerprints, and enable Trusted Agents in Settings -> Fingerprints & Security)
Download
Version 0.0.2: https://www.androidfilehost.com/?fid=962187416754470110
Version 0.0.1: https://www.androidfilehost.com/?fid=818070582850487924
XDA:DevDB Information
Unofficial LineageOS 14.1, ROM for the LG V30
Contributors
SGCMarkus
Source Code: https://github.com/SGCMarkus
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
Version Information
Status: Testing
Created 2018-01-25
Last Updated 2018-01-25

Changelog
v 0.0.1 Initial build
it boots
v 0.0.2
Mobile data works
Cam works (pictures only)
fixed graphics glitches
Fingerprint works
flashlight works
SDCard is recognized

If you are interested to contribute/help out/test, hit me up in PM, or join my Discord Server: https://discord.gg/DJRnTRC
I set it up to be a general server for all kinds of LG V30 things, but also for Developers to meet and talk to each other, and help each other out.

Downloading...
I'll try to flash it. I'm new on LG devices (come from Samsung...)

It BOOTS

Mike.YT said:
It BOOTS
Click to expand...
Click to collapse
I agree... FC everywhere
But I hope it's a first step...

Exam time here though, so i couldnt really work on this more :/
But i have hope now for actual Treble support (we have a partition called OP, idk how important the stuff in there is though, 344MB if im not wrong, gathered all the Oreo blobs from the V300S kdz (i hope i have all needed ones), and those take up 324MB xD)
But atleast already a working recovery (TWRP 3.2.1) which would recognize the /OP as /vendor
Will work on each project a bit more when exams are over

i don't know if can help someone to build lineage or aosp based rom, btw here are the link to source and kernel for v30:
h930: http://opensource.lge.com/osSch/list?types=ALL&search=h930
us998: http://opensource.lge.com/osSch/list?types=ALL&search=us998
v300: http://opensource.lge.com/osSch/list?types=ALL&search=v300
Here the content of readme:
1. Android build
- Download original android source code ( android-7.1.2_r4 ) from http://source.android.com
( $repo init -u https://android.googlesource.com/platform/manifest -b android-7.1.2_r4
$repo sync -cdq -j12 --no-tags
$repo start android-7.1.2_r4 --all
)
- Untar opensource packages of LGH930_Nougat_Android.tar.gz into downloaded android source directory
a) tar -xvzf LGH930_Nougat_Android.tar.gz
- And, merge the source into the android source code
- Run following scripts to build android
a) source build/envsetup.sh
b) lunch 1
c) make -j4
- When you compile the android source code, you have to add google original prebuilt source(toolchain) into the android directory.
- After build, you can find output at out/target/product/generic
2. Kernel Build
- Uncompress using following command at the android directory
a) tar -xvzf LGH930_Nougat_Kernel.tar.gz
- When you compile the kernel source code, you have to add google original "prebuilt" source(toolchain) into the android directory.
- Run following scripts to build kernel
a) cd kernel/msm-4.4
b) mkdir -p out
c) make ARCH=arm64 O=./out joan_global_com_defconfig
d) make ARCH=arm64 O=./out CROSS_COMPILE=$(pwd)/../../prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android- KERNEL_COMPRESSION_SUFFIX=gz -j4
* "-j4" : The number, 4, is the number of multiple jobs to be invoked simultaneously.
- After build, you can find the build image(Image.gz) at out/arch/arm64/boot
Click to expand...
Click to collapse

I always loved to know how to build Kernel or ROM.
I'm not a dev so i cannot solve any FC or any other problem, so I need to know where to get the sources.

Little update here, decided to fix LOS14.1 first as 15.1 didnt wanna work at all ?

SGCMarkus said:
Little update here, decided to fix LOS14.1 first as 15.1 didnt wanna work at all
Click to expand...
Click to collapse
heheh don't give up my little dev... We believe in your skill :good:

Also could someone with a US998 test this?
And check what works (and doesnt)? And then send me the logcat (from /data/ramoops) after copying to the sdcard in twrp or whereever before restoring a backup xD

SGCMarkus said:
Also could someone with a US998 test this?
And check what works (and doesnt)? And then send me the logcat (from /data/ramoops) after copying to the sdcard in twrp or whereever before restoring a backup xD
Click to expand...
Click to collapse
I was just getting ready to ask if this will work on US998. If I get a chance I will try it out but I'm not sure how to do the logcat thing sorry.

foamerman said:
I was just getting ready to ask if this will work on US998. If I get a chance I will try it out but I'm not sure how to do the logcat thing sorry.
Click to expand...
Click to collapse
The logcat is taken automatically, as for idk why it wont be recognized via USB... (same kernel as the TWRP, ramdisk and so should also work), just boot into recovery after you used it a bit (if it even boots, otherwise do the button dance), and there, before you wipe/restore a backup, go to advanced -> file manager, browse to /data/ramoops and copy the log in there to the sdcard or whatever else is safe

SGCMarkus said:
The logcat is taken automatically, as for idk why it wont be recognized via USB... (same kernel as the TWRP, ramdisk and so should also work), just boot into recovery after you used it a bit (if it even boots, otherwise do the button dance), and there, before you wipe/restore a backup, go to advanced -> file manager, browse to /data/ramoops and copy the log in there to the sdcard or whatever else is safe
Click to expand...
Click to collapse
OK but now I have another problem TWRP backup failed on me. So if I do install 14.1 and it doesn't boot I have WETA 1.5 I can do the button dance and go twrp and reinstall weta as soon as I get some time I'll will try it.
---------- Post added at 02:45 PM ---------- Previous post was at 02:26 PM ----------
Sorry one more question I'm guessing we need to download our own gapps too yes? so arm64 7.1 pico would be fine that's the least one

foamerman said:
OK but now I have another problem TWRP backup failed on me. So if I do install 14.1 and it doesn't boot I have WETA 1.5 I can do the button dance and go twrp and reinstall weta as soon as I get some time I'll will try it.
---------- Post added at 02:45 PM ---------- Previous post was at 02:26 PM ----------
Sorry one more question I'm guessing we need to download our own gapps too yes? so arm64 7.1 pico would be fine that's the least one
Click to expand...
Click to collapse
Try it without gapps, its not worth to setup all that, it isnt daily driver ready... and gapps would just add more (unneccessary) stuff to the log ^^

--snip--

Well I tryred it but I got error 7 thats all I got

foamerman said:
Well I tryred it but I got error 7 thats all I got
Click to expand...
Click to collapse
Probably because of wrong device, remove the assert line in the updater-script in side the .zip file
(.zip/META-INF/com/google/android/updater-script)

SGCMarkus said:
Probably because of wrong device, remove the assert line in the updater-script in side the .zip file
(.zip/META-INF/com/google/android/updater-script)
Click to expand...
Click to collapse
OK I unzipped the file and deleted the (.zip/META-INF/com/google/android/updater-script) OK now I need a little help I'm a little slow I'm not sure how to zip it back up

[ROM][UNOFFICIAL][O][UsU] LineageOS 15.1 [VS986] DEPRECATED

Reserved

So for this rom I am supposed to use the MM modem, not the N modem as stated in the Unlock thread?

Yoyodude1124 said:
So for this rom I am supposed to use the MM modem, not the N modem as stated in the Unlock thread?
Click to expand...
Click to collapse
Its clearly stated in this OP.

I Installed it yesterday, so far almost everything works out of the box, I've tested:
-4G LTE
-Roaming
-Phone Calls
-Wi-fi
-Bluetooth
-GPS
-Both cameras
The only thing that doesn't work is the flashlight button in the quick settings, although it works in the camera app.
I was unable to test NFC and wireless charging since I no longer have the original back cover.
As a side note, it fails Google's Safety Net even after completely removing root support from LOS, so banking apps are gonna be an issue.

lkeeler said:
I Installed it yesterday, so far almost everything works out of the box, I've tested:
-4G LTE
-Roaming
-Phone Calls
-Wi-fi
-Bluetooth
-GPS
-Both cameras
The only thing that doesn't work is the flashlight button in the quick settings, although it works in the camera app.
I was unable to test NFC and wireless charging since I no longer have the original back cover.
As a side note, it fails Google's Safety Net even after completely removing root support from LOS, so banking apps are gonna be an issue.
Click to expand...
Click to collapse
As long as this ROM is in permissive mode you will never pass safety net for sure. This is listed in the known issues in the OP. Torch is a known issue as well and have been added to the same link of the OP. As far as I know NFC will not work in any custom ROM at least it doesn't even in aoscp
Sent from my LG-H815 using XDA Labs

Hello everyone. Tell me how to switch to CDMA

lkeeler said:
I Installed it yesterday, so far almost everything works out of the box, I've tested:
-4G LTE
-Roaming
-Phone Calls
-Wi-fi
-Bluetooth
-GPS
-Both cameras...
Click to expand...
Click to collapse
I see you got phone calls to work. Do you still have Verizon?

ANDROID2468 said:
I see you got phone calls to work. Do you still have Verizon?
Click to expand...
Click to collapse
No, I'm on Virgin Mobile.

New build up
Happy leeching
Sent from my LG-H815 using XDA Labs

steadfasterX said:
New build up
Happy leeching
Click to expand...
Click to collapse
Is the blobs fixed yet?

ANDROID2468 said:
Is the blobs fixed yet?
Click to expand...
Click to collapse
Still working on this.. It's not a quick task
if you want to help :
Flash this Rom and tell me if it boots for you because for me it doesn't but I do not have your model here to test :
http://leech.binbash.it:8008/lineage/oreo/vs986-UsU/experimental/
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Still working on this.. It's not a quick task
if you want to help :
Flash this Rom and tell me if it boots for you because for me it doesn't but I do not have your model here to test :
http://leech.binbash.it:8008/lineage/oreo/vs986-UsU/experimental/
Click to expand...
Click to collapse
Ok i will try it tonight! I understand that it's not easy to build something from the ground up! I appreciate that someone is willing to develop firmware for a 3 year old phone that's lock down!

steadfasterX said:
Still working on this.. It's not a quick task
if you want to help :
Flash this Rom and tell me if it boots for you because for me it doesn't but I do not have your model here to test :
http://leech.binbash.it:8008/lineage/oreo/vs986-UsU/experimental/
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Installed on my VS986 running MM 27c with 2BA bootstack (as in FAQ #20; verified FAQ #26)
No Gapps yet, but did flash SuperSU.
Booted quickly, no bootloops.
Tested camera, browser on Wi-Fi… looks good so far!
But, as usual there is no cell service- the phone isn’t seeing the SIM card.
This is the first LOS Oreo that would boot for me, so thank you!

cowsngrass said:
Installed on my VS986 running MM 27c with 2BA bootstack (as in FAQ #20; verified FAQ #26)
No Gapps yet, but did flash SuperSU.
Booted quickly, no bootloops.
Tested camera, browser on Wi-Fi… looks good so far!
But, as usual there is no cell service- the phone isn’t seeing the SIM card.
This is the first LOS Oreo that would boot for me, so thank you!
Click to expand...
Click to collapse
wow great! didnt expect that it even boots.. yea cool the blobs I use are taken from 2BA!
for the SIM:
dialer: type *#06# (do you see your imei?)
settings: phone info -> do you see your imei? do you see your mobile phone number?

the experimental rom did not boot for me. it was close the welcome screen pop up for a couple seconds

ANDROID2468 said:
the experimental rom did not boot for me. it was close the welcome screen pop up for a couple seconds
Click to expand...
Click to collapse
then its very likely the firmware. whats yours?
.

steadfasterX said:
wow great! didnt expect that it even boots.. yea cool the blobs I use are taken from 2BA!
for the SIM:
dialer: type *#06# (do you see your imei?)
settings: phone info -> do you see your imei? do you see your mobile phone number?
Click to expand...
Click to collapse
*#06# I get MEID, which is a different number from the IMEI
Settings> System> About phone> Status> SIM status: both IMEI and phone number show correctly

cowsngrass said:
*#06# I get MEID, which is a different number from the IMEI
Settings> System> About phone> Status> SIM status: both IMEI and phone number show correctly
Click to expand...
Click to collapse
thats... weird.. is the IMEI correct when going to the imei boot screen? --> poweroff phone, disconnect USB, press vol+up and vol+down the same time
.

steadfasterX said:
thats... weird.. is the IMEI correct when going to the imei boot screen? --> poweroff phone, disconnect USB, press vol+up and vol+down the same time
.
Click to expand...
Click to collapse
IMEI boot screen shows correct IMEI with barcode.
Serial number is blank with a short barcode.

[ROM][Pie][OFFICIAL] Resurrection Remix v7.0.2 [beckham]

{
"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"
}
Resurrection Remix P
Code:
[SIZE="4"]/*
* 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.
*/[/SIZE]
Resurrection Remix the ROM has been based on LineageOS, SlimRoms, Omni and original Remix ROM builds, this creates an awesome
combination of performance, customization, power and the most new features, brought directly to your Device.
Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!
Special thanks to the LineageOS team, Omni team, SlimRoms and of course to all the supporters.

Make sure you have the latest TWRP.img
Download the latest RR-P zip and GApps zip (opengapps nano or smaller)
fastboot boot twrp.img (TWRP cannot be flashed permanently at this time)
If coming from stock for the first time, flash copy-partitions-AB.zip from second post (It takes a backup of active slot to inactive slot)
In TWRP, choose -> Wipe -> Format data and type "yes" at the prompt (Note: this will wipe internal storage)
Flash latest RR-P.zip
Reboot and let the ROM boot once (it is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic)
Reboot back to bootloader and fastboot boot twrp.img again
In TWRP, choose -> Wipe -> Format data and type "yes" at the prompt (You may be able to get away with just doing a factory reset at this point, but that's on you to try)
Flash Google Apps package (optional)
Flash Magisk (also optional) (Note: If Magisk doesn't stick after setting up your device, fastboot boot twrp.img one last time and flash it again, no need to wipe anything)
First boot may take up to 10 minutes.
ROM Download
GApps
Resurrection Remix Source
Device Source
Kernel Source
Vendor Source
XDA Developers
LineageOs Team
Omni Team
And Of Course To All The Supporters, Donators And Users
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, Team Resurrection Remix and me quite some time.
Download the MatLog app from the Play Store.
After downloading the MatLog 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 MatLog 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 thread with a brief description of the error.

XDA:DevDB Information
Resurrection Remix Pie v7.0.2, ROM for the Moto Z3 Play
Contributors
Jleeblanch, erfanoabdi, vache, RR Team
Source Code: https://github.com/ResurrectionRemix
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: LineageOS
Version Information
Status: Beta
Beta Release Date: 2019-02-25
Created 2019-02-26
Last Updated 2019-04-21

Copy partitions zip
[size=+2]Important info, please read...[/size]
Starting from build 20190414, encryption is disabled (temporarily) and you must clean flash
[size=+1]Coming from stock?[/size]
Make sure to flash the copy-partitions-AB.zip in twrp before you do anything else. You can download it from the attachment below...

Reserved

The real mvp. Although I have the prime version so I can't use it.
Sent from my Moto Z3 Play using XDA Labs

triggerlord said:
The real mvp. Although I have the prime version so I can't use it.
Sent from my Moto Z3 Play using XDA Labs
Click to expand...
Click to collapse
No way to unlock the bootloader on that variant?

Can someone confirm Verizon support on this rom? I know for others - there has been issues receiving SMS/MMS...

Does It have Moto Mods support?

pbjr92 said:
Does It have Moto Mods support?
Click to expand...
Click to collapse
It has some Moto Mods support, yes. I only have the battery mod that came with the device, and it is working (both default and efficiency modes). There should be support for more mods as well, but not all mods.

Jleeblanch said:
It has some Moto Mods support, yes. I only have the battery mod that came with the device, and it is working (both default and efficiency modes). There should be support for more mods as well, but not all mods. View attachment 4712886View attachment 4712887View attachment 4712888View attachment 4712889
Click to expand...
Click to collapse
That's the one I needed. I'll flash this rom later then.
Thanks for the reply.

Anyone can point me how to root unlocked variant of this device and or bootunlock and how to rom..Don't have to have root but want this rom...
---------- Post added at 09:47 AM ---------- Previous post was at 09:42 AM ----------
Got the USA version...if it's possible to even rom

kenbrownstone said:
Anyone can point me how to root unlocked variant of this device and or bootunlock and how to rom..Don't have to have root but want this rom...
---------- Post added at 09:47 AM ---------- Previous post was at 09:42 AM ----------
Got the USA version...if it's possible to even rom
Click to expand...
Click to collapse
It's possible. You just need to type in a fastboot command, paste a code into their website, then paste the unlock code into fastboot. It only takes a couple minutes.
Sent from my Moto Z3 Play using XDA Labs
Jleeblanch said:
No way to unlock the bootloader on that variant?
Click to expand...
Click to collapse
Sunshine says it can but it needs root and there's no way to root this device.
Sent from my Moto Z3 Play using XDA Labs

kenbrownstone said:
Anyone can point me how to root unlocked variant of this device and or bootunlock and how to rom..Don't have to have root but want this rom...
---------- Post added at 09:47 AM ---------- Previous post was at 09:42 AM ----------
Got the USA version...if it's possible to even rom
Click to expand...
Click to collapse
First step is to go to Motorola bootloader unlocking site and follow the steps there. Once you've followed their steps, you should be unlocked and ready to go.
Keep in mind, the install instructions in the OP aren't entirely correct for this device. In fact, it's a little more complicated than that.
I'll update the OP with better install instructions later this evening. There is also a zip that needs to be flashed if coming from stock for the first time. If you look in the G6+ forums in the OP of Lineage-16.0 thread, you'll see what I'm talking about. The process is mostly the same.

Wow! Glad to see a custom ROM for this phone. I will be trying it out in the next day or so.

So I installed this morning, looks good. Send and receive text works fine, unable to receive or make phone calls with Google Fi. Also the phone will not hang up, gets stuck in hanging up, wont end in force stop, only way to end it is with a reboot. I know others had phone issues with Verizon in Lineage.
If you need any more info or logs let me know.

Droid_Nut said:
So I installed this morning, looks good. Send and receive text works fine, unable to receive or make phone calls with Google Fi. Also the phone will not hang up, gets stuck in hanging up, wont end in force stop, only way to end it is with a reboot. I know others had phone issues with Verizon in Lineage.
If you need any more info or logs let me know.
Click to expand...
Click to collapse
First I've heard of this, but I will obviously look into it. If you can, please get a log while reproducing the issue. I use my device daily and make and receive calls without any issues, so I'd imagine it's a simple fix for you Verizon guys [emoji6]

Do have an install of twrp yet? Or still temporarily boot into twrp recovery to install rom?
Thanks for the new rom Dev!

so i installed and test with mods battery mods work
speakers dont
projector does
camera mod doesnt
also issue with the hanging up issue was on mine as well with tmobile
and then using pixel launcher caused a strange "phone is starting" never ending screen on reboot but was gone in safe mode?? ill test a bit more on that

ignore

Jleeblanch said:
First I've heard of this, but I will obviously look into it. If you can, please get a log while reproducing the issue. I use my device daily and make and receive calls without any issues, so I'd imagine it's a simple fix for you Verizon guys [emoji6]
Click to expand...
Click to collapse
I have access to Google Fi and Verizon sims, so I can pull logs for both.
Actually with Lineage it was opposite. I could do incoming and outgoing calls, but I could not do text either way, and the phone app would crash when I did. I was noting that others had a problem with Verizon phone calls.

I could not even get service with Verizon, so that was a bust.
Here is what I got with Google Fi
Text out. OK
Text in. OK
Call in. Went to voicemail after ring timeout
Call out. Failed, never rang on either end
Hang up. Failed
logcat.txt https://hastebin.com/gifurosawi.coffeescript
dmesg.txt https://hastebin.com/kuhimacibo.md
device_info.txt https://hastebin.com/tizumugiki.http

Development [ROM][UNOFFICIAL][Q/A10][SM-J530F] /e/ OS for Samsung J5 2017 (j5y17lte) - 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.
*/
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 the stable Lineage OS
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 LineageOS
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/
UNOFFICIAL builds (having the tag UNOFFICIALin ROM filename):
There are no differences. its pure /e/. just an unofficial build (this ROM is currently still in progress to get approved by /e/ for official builds)
Note (2022-09-09):
This project was in the transition to become official which got stuck due to build issues on /e/ site. Because of that I stopped building UNOFFICIAL as they made no sense when my code becomes official and just providing CUSTOM builds atm. As the process to become official takes longer then expected I will likely build UNOFFICIAL again in the (hopefully) near future.
Note (2022-11-22):
All open issues have been fixed, first official test builds finally work as they should. the current progress becoming official can be tracked here
I won't build a new UNOFFICIAL release atm in the hope this process will be finished soon
the camera will have a stretched preview as it is pure /e/ and so my modification (see CUSTOM) won't apply there.
You can always install the fixed cam version from here (opencamera_sfX_j5_fixPreview.apk) though and install in parallel to the stock one (the reason why I changed the package id for that modded one to "foundation.e.camera.j5").
CUSTOM builds (having the tag CUSTOM in ROM filename):
The following apps are included: click
A note about Google Play Store / Phonesky: Phonesky is THE original Google Play store - "just" modified that it works without the Google service dependencies. It is still the original google play store though.
Besides the fact this Play store works on the microG backend it allows to use paid apps - which is something some users requested.
Google Play Store / Phonesky can be easily disabled in the App settings screen (must be re-done after every upgrade though).
The stretched camera preview (photo & video recording) is "fixed" (since v1.5):
Unfortunately this works for the /e/ STOCK camera app ONLY so if you install any other camera app you will have that stretched preview there again
For those being curious: the code changes can be found here always.
the app package id has changed to "foundation.e.camera.j5" to allow a parallel install with the stock cam version (on OFFICIAL and/or UNOFFICIAL builds)
Known issues:
Keep in mind that this is brand new stuff so it may (still) contain unknown issues!
So back up regularly and frequently!
When your current STOCK firmware or the latest you had flashed is not PIE (Android 9) then flash the following STOCK version: J530FXXS7CTF1 (pie)
selinux: permissive (will be set to enforcing once I got some user feedback if my build working as stable for others as for me)
Camera preview is "stretched". This affects the preview only, pictures taken are fine. sorry there is no known way to solve that afaik.
If you find a bug not listed let me know and SHARE LOGS! -> READ FAQ#1 for how to provide proper logs.
Requirements
Latest TWRP or SHRP build.
This ROM has been tested with stock firmware J530FXXS7CTF1 . If you use an older one switch to this first. If you have a newer one things might not work for you (like cam etc)
Do a full (i.e. Nandroid) backup before doing anything!
Installation
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
Get your builds from my leech server (new installs or re-installs)
https://leech.binbash.rocks:8008/e-os/a10/j5y17lte/
If you have a previous version of my(!) /e/ Q installed already and just want to update to a newer release:
Android settings -> Updater (yes my builds have built-in OTA support!)
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
search results from this thread: click
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
nailyk
Astrako, wth.. you did an AWESOME job for this SoC!
LineageOS (the base of /e/)
The /e/ foundation and all related devs making this experience possible!
The Exynos7870 Team
and more..
Sources
build manifest
XDA:DevDB Information
j5y17lte_eos-q_unofficial, ROM for the Samsung Galaxy J5
Contributors
steadfasterX, nailyk, Astrako for ALL Q porting stuff!!! and: ananjaser1211,DarkLord1731,Exynos7870 Team (github)
Source Code: https://gitlab.e.foundation/e
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: only tested on PIE bootloader - so upgrade if you are on Oreo or older
Based On: Lineage OS
Version Information
Status: Stable
Created 2020-10-01

.
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 have an audio issue follow FAQ #6 instead.
Often selinux can cause issues so try that at very first:
Code:
if you have magisk installed:
adb shell
su
setenforce permissive
When " usb debugging root" is enabled in developer settings:
adb root
adb shell
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 your issue is not solved with selinux permissive 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 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: a very first test is to set magisk on 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 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. With your help! What you can do? Test and report EVEN SUCCESS in this thread.
Q #4: Is there an /e/ specific FAQ?
Sure:
FAQ: click
Forum: click
HOWTOs: click (a great resource for all your first questions)
Q #5: 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 audio 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 #6: 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 #7: What is the difference between CUSTOM and UNOFFICIAL builds?
UNOFFICIAL is like pure /e/ - untouched. This is the base for OFFICIAL builds (coming soon)
CUSTOM:
removed: /e/ Apps (read here why)
added: AuroraStore, F-Droid, F-Droid xtra repos (manual enable required), DNS66 (adblock w/o root), Omega Launcher (as alternative Launcher)
Q #8: Banking not working? Your app <fill-in-appname> does not work because root is detected?
So you wanna install and use a banking app or any other which is trying to detect root? The following might help you out:
[ROM][UNOFFICIAL|CUSTOM|LOCKEDBL][Q/A10][hotdog] /e/ OS for OnePlus 7T Pro - BYE Google, HELLO privacy and security (LOCK your BOOTLOADER)!
brought to you by the /* * 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...
forum.xda-developers.com
--> See FAQ 8 there!Yes that FAQ was written for a oneplus device but is generic for every device and model.
.-

Reserved

Excellent work Stead, and glad to see you here!

Gooooood Work!
Will love to see it on other 7870s as well....

Astrako said:
Excellent work Stead, and glad to see you here!
Click to expand...
Click to collapse
Without your work it would had take several (more) weeks to finish , so that thanks goes back to you dude
Sent from my OnePlus 7T Pro using XDA Labs

amazing work sir
it works perfectly so far
sad cuz i cant flash other kernels but hey its smooth af even with stock kernel
keep up the good work

Thanks a lot, it works fine for me - except for the GPS...

tiboleplubo said:
Thanks a lot, it works fine for me - except for the GPS...
Click to expand...
Click to collapse
What was the last stock version you flashed ? Also: share a screenshot of your baseband version in android settings.
Sent from my OnePlus 7T Pro using XDA Labs

steadfasterX said:
What was the last stock version you flashed ? Also: share a screenshot of your baseband version in android settings.
Sent from my OnePlus 7T Pro using XDA Labs
Click to expand...
Click to collapse
The last version that was available on SamMobile... It was "J530FXXU6CSK9_J530FXEF6CSL1_XEF"... if that's what you asked...
Here is the screenshot : https://ibb.co/7Q8jq2N

tiboleplubo said:
The last version that was available on SamMobile... It was "J530FXXU6CSK9_J530FXEF6CSL1_XEF"... if that's what you asked...
Here is the screenshot : https://ibb.co/7Q8jq2N
Click to expand...
Click to collapse
Well i would expect that it should work but as it does not flash the J530FXXS7CTF1 stock firmware . You could also try just flashing the modem partition of that firmware but if you dont know how then the fulk stock firmware is the easiest.
Sent from my OnePlus 7T Pro using XDA Labs

steadfasterX said:
Well i would expect that it should work but as it does not flash the J530FXXS7CTF1 stock firmware . You could also try just flashing the modem partition of that firmware but if you dont know how then the fulk stock firmware is the easiest.
Click to expand...
Click to collapse
It works now ! (I don't understand, I didn't do anything... Just think I had not been patient enough ^^')
Sorry for disturbing ^^' Anyway, thanks again, I hope we'll get an official build !

Gapps
Hi, thanks for your work. Please, i need to have gapp on this Rom, how i can (if is possible) install it?

pupunar said:
Hi, thanks for your work. Please, i need to have gapp on this Rom, how i can (if is possible) install it?
Click to expand...
Click to collapse
uhm.. you want to use /e/ which main goal is to live without google.... and you want to install google bloat and spyware on it? maybe read the Installation topic again?
View attachment 5119347
if you really need gapps (really?) and so google crap then simply go with LOS instead.
.-

Hey !
Quick question, I currently have an unofficial CrDroid on my phone that works great, except for the camera, which is stretched in almost all the apps...
So, just to be sure, does the camera work flawlessly in this rom ?
Thanks for your hard work ! :victory:

lPolarisl said:
Hey !
Quick question, I currently have an unofficial CrDroid on my phone that works great, except for the camera, which is stretched in almost all the apps...
So, just to be sure, does the camera work flawlessly in this rom ?
Thanks for your hard work ! :victory:
Click to expand...
Click to collapse
Yea within my vacation i had an user report about that. Will check that soon.
Sent from my OnePlus 7T Pro using XDA Labs

Hi, I have a question, I have only one app on my phone that use the Google Service Framework sadly..
I'm pretty sure I already know the answer, but will it work with /e/ ?

Morceaux said:
Hi, I have a question, I have only one app on my phone that use the Google Service Framework sadly..
I'm pretty sure I already know the answer, but will it work with /e/ ?
Click to expand...
Click to collapse
maybe if you tell what "it" is?
.-

steadfasterX said:
maybe if you tell what "it" is?
.-
Click to expand...
Click to collapse
Yeah, my bad >.>
It's Pulse SMS
(I tried to use it without the Gapps on my actual ROM, but It didn't work)

Morceaux said:
Yeah, my bad >.>
It's Pulse SMS
(I tried to use it without the Gapps on my actual ROM, but It didn't work)
Click to expand...
Click to collapse
should work according to https://community.e.foundation/t/sms-mms-app-question/1615
but the only way to find out for sure is try and see
(/e/ has microG included so that is way different then just choosing a ROM without installing gapps)
.-

Develop Bugs

welcome