[ROM][Huawei][11][UNOFFICIAL] CAOS - Android 11 for Huawei device

[ROM][Huawei][11][UNOFFICIAL] CAOS - Android 11 for Huawei device - P8 Lite (2017) Development

C A O S [UNOFFICIAL]
Your warranty is now void!
We're 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 us for messing up your device, we will laugh at you
CAOS (Custom AOSP OS) is a project which based on phhuson's Treble GSI AOSP 11. CAOS is a modified AOSP by eretemin which I modified to be compatible with Huawei hi6250 phones. I also provided several patches
Changelog :
CAOS 316 March 2022 version
March 2022 SPL
CAOS 315+ Febrary 2022 version
Febrary 2022 SPL
CAOS 315 January 2022 version
January 2022 SPL
Fix all storage/permission in social apps like instagram, messenger.
implemented Huawei IMS patches
added Seedvault app and option in Treble app for activating it
full fixes access for media files from some apps like WhatsApp or Telegram
backported changes from v400h device_phh_treble: All devices support unprocessed audio source
patch for gsicharger removed, should fix offline charger animation for some devices (need test)
volume dialog UI now follows rounded corners
added CAOS logo image
CAOS 314 December 2021 version
Initial build
Decembre 2021 SPL
Integrate NFC, Miracast/cast , Live Display patches
Add media patch (Fix "Error loading media" in social apps like instagram, messenger..)
Pre-requisite :
You must have TWRP installed, use this one (make sure to have the unofficial Android 11 one ! ).
Installation :
Download this file caos-v316-220321-arm64-iceows-huawei.7z:
go to TWRP
flash this file Huawei-Decrypt-Emui_8.zip to change mount data partition (disable FBE : FileBaseEncryption)
format data
reboot to TWRP again
do a full wipe (system, data, cache, dalvik/art cache) !
reboot to bootloader
extract the img from caos-v316-220321-arm64-iceows-huawei.7z
run: fastboot flash system <drag system.img here>
reboot to TWRP
resize system
(optional) flash patches :
1 - Google Apps lite : [RECOVERY]LiteGapps_arm64_11.0_v2.6_official.zip
2 - Enable AGPS : 7-AGPS-FIX-AltairVendor-v3.6-signed.zip
3 - If you are on EMUI 8.0.0.408 or sup : 8-Huawei-PRA-FixPreav-A-v1.1-signed.zip
reboot to System and set up the phone with Lineage first start assistant. You can also add most
reboot to System
(optional) install GCamGo (GoogleCamera_2.12.413042791.apk)
Enjoy !!!
Not Working :
Nothing
ROM OS Version: Android 11
ROM Kernel: Linux 4.4.x (stock 4.4.26 or Siberia_4.4.302-1.1.zip)
ROM Firmware Required: EMUI 8.0.0.360 ---> 8.0.0.402
Based On: Caos (eremitein)
Credits:
eremitein
And all the others who tested my patches and helped me improve this ROM
CAOS11 Project
GSI Treble patches. Included Phh, Andy Yan and my personal Treble works. You can using patches/solutions from here and from linked manifests (all or few my own) in none-commercial usage only and yo...
github.com
Support Group

reserved

Is there any specificity to this ROM ? I mean, compared to Lir and LeaOS you posted recently, or DotOS which is more about performance ?

Hykosit said:
Is there any specificity to this ROM ? I mean, compared to Lir and LeaOS you posted recently, or DotOS which is more about performance ?
Click to expand...
Click to collapse
CAOS , LiR, DotOS, crDRom etc. are AOSP GSI ROMs based on 'phhusson' sources, so the difference in performance, battery life, etc. is minimal. And all have some common bugs- VoLTE, native call recording, offline charging etc. If you like to take pictures, you will be disappointed with the camera...(btw, Footej camera 2-premium is a good enough replacement for gcam).
The main differences between these ROMs are in the customization options.
In my experience CAOS is faster, crDRom is customization monster, LiR is a perfect balance between battery efficiency, performance and the customization. As for DotOS, the previous version 5.1.3 was better.

hi Alf.
Indeed it is a good comparison of the different ROMs. For charging go to PHH trebble option and enable fastcharging to 4000ma. For the Volte it is in progress..., and for the camera I provide GCAM in addition

AltairFR said:
For charging go to PHH trebble option and enable fastcharging to 4000ma.
Click to expand...
Click to collapse
-Alf- said:
offline charging
Click to expand...
Click to collapse
AltairFR said:
I provide GCAM
Click to expand...
Click to collapse
try Footej 2-premium and you'll see what I'm talking about...

Thanks you two ! That's good stuff to know
AltairFR said:
For charging go to PHH trebble option and enable fastcharging to 4000ma
Click to expand...
Click to collapse
But won't this one harm the battery ?

-Alf- said:
try Footej 2-premium and you'll see what I'm talking about...
Click to expand...
Click to collapse
So I looked for this one, unfortunately the app was sell to an other company (ZipoApp), and seeing the recent opinions on google play the app was just monetized and the premium is now 10€ by damn week, and people fear for user privacy ... Smell like a bad story to me
Do you have any old apk, from before the acquisition ?

moriel5 said:
Disclaimer: I am a simple user, and am not affiliated with Semaphore or ZipoApps.
Recently, Footej Camera (or officially, Footej Camera 2) was bought by ZipoApps.
After seeing things like the buyouts of software like QuickPic or certain (legacy) parts of Nano Defender and the resulting consequences, naturally I was concerned with this, especially when ZipoApps's line of business is buying existing apps and monetizing them.
After some sleuthing, I managed to get the personal cellular number of ZipoApps's CEO, Alik Hochner (I am not going to divulge any more information about how and what was needed for this, to preserve his and other involved people's privacy), and I just spoke with him a few minutes ago.
While I am not completely reassured, due to not having experience with ZipoApps's history, he did strike me as someone who does want to be able to monetize apps while protecting user's privacy to the best of his abilities, though understandably limited by the tools the current market offers without being independent of the mass market.
Make of that what you will, I will continue to keep an eye on the matter, to see whether this turns out to be a turning point for such buyouts for the better or not.
Click to expand...
Click to collapse
from :
[Android 5.0+] Footej Camera 2 2021.5.6
Get it on Google Play A brand new, fascinating, user-friendly and robust camera app is here, ready to capture, orchestrate and give a new life to your best moments… *** If you have any problem or if you can't find manual controls, before give...
forum.xda-developers.com

Hykosit said:
Do you have any old apk, from before the acquisition ?
Click to expand...
Click to collapse
Yes, look here

-Alf- said:
try Footej 2-premium and you'll see what I'm talking about...
Click to expand...
Click to collapse
For my part I have no problem with offline charging. Can you describe the problem?

AltairFR said:
For my part I have no problem with offline charging. Can you describe the problem?
Click to expand...
Click to collapse
I suppose it was a question for me.
I was wondering if changing initial charging values could be harmful to the longevity of the battery as those are (i think) calibrated for specific values

AltairFR said:
For my part I have no problem with offline charging. Can you describe the problem?
Click to expand...
Click to collapse
On A/B GSI doesn't work at all (Kirin-devices).

-Alf- said:
On A/B GSI doesn't work at all (Kirin-devices).
Click to expand...
Click to collapse
Ok

Hykosit said:
So I looked for this one, unfortunately the app was sell to an other company (ZipoApp), and seeing the recent opinions on google play the app was just monetized and the premium is now 10€ by damn week, and people fear for user privacy ... Smell like a bad story to me
Do you have any old apk, from before the acquisition ?
Click to expand...
Click to collapse
Here is install this apk, it is modified:
- cleaned resources,
- disable wakelock,
- disable loging and analitics,
- enable premium version

AltairFRGOOD work !!!

AltairFRHi Master. Please make ROM with all patches for a variety...
Nusantara_v3.2-11-arm64_avN-29082021-OFFICIAL-0849.img.xz
NusantaraROM - GSI
NusantaraProject ROM GSI (Generic system image ROM) For all devices with supported project treble.
www.pling.com

I have flashed this to Honor 8 frd-l19 (emui 8 device). Some problems have been tackled down now with help of dev, thanks to that. Apparently only things to do for now would be able to create misc folder at /data/misc and also credstore at /data/misc/credstore to be able to boot now.*1
Any ideas how to get those folders done? atm. I can access to phone via adb while phone stays at CAOS logo screen, maybe between 10-15mins.
I've tried to:
sudo adb root
adb remount rw, /data
which succees
then
sudo adb shell
cd data
mkdir misc
but get error
mkdir: '/data/misc': Read-only file system
I've also tried to install busybox at twrp*2, but using it via twrp terminal doesn't give su or sudo. When trying without su and just busybox mkdir /data/misc/ it seems to create one and I can even cd to it and create subfolder. After changing right permissions and using chown to those folders everytjing seems to be good. Sure twr doesn't show misc_ce and misc_de etc under data which were tegere when using adb.
Well no surprise that reboot habgs to CAOS logo and when xhecking via adb shell thete's no misc folder under data.
Can anyone give some tips how to be able to create those folders since I can't use adb via twrp or stock recovery. Also strange that when remounting /system as rw I can push & echo changes to there, but not able to create directories to /data after doing the same.
If someone can help, I will shere needed steps to get this running at Honor 8 frd, unless that will just revel next layer of problems.
*1 Device will boot to OS at first boot, won't boot after restart. So after logs there could b found reasons and now tried to fix those with help of dev and might be at the stage that to create folders just once again will be fix.
*2 I have found only 2 different twrp images, both at version 3.2.1-0 which are suitable for this device, others haven't work at all.

I don't have a solution but LiR build doesn't seem to have that problem. I could reboot many times on a hi3650 P9

huuhaa_tm said:
I have flashed this to Honor 8 frd-l19 (emui 8 device). Some problems have been tackled down now with help of dev, thanks to that. Apparently only things to do for now would be able to create misc folder at /data/misc and also credstore at /data/misc/credstore to be able to boot now.*1
Any ideas how to get those folders done? atm. I can access to phone via adb while phone stays at CAOS logo screen, maybe between 10-15mins.
I've tried to:
sudo adb root
adb remount rw, /data
which succees
then
sudo adb shell
cd data
mkdir misc
but get error
mkdir: '/data/misc': Read-only file system
I've also tried to install busybox at twrp*2, but using it via twrp terminal doesn't give su or sudo. When trying without su and just busybox mkdir /data/misc/ it seems to create one and I can even cd to it and create subfolder. After changing right permissions and using chown to those folders everytjing seems to be good. Sure twr doesn't show misc_ce and misc_de etc under data which were tegere when using adb.
Well no surprise that reboot habgs to CAOS logo and when xhecking via adb shell thete's no misc folder under data.
Can anyone give some tips how to be able to create those folders since I can't use adb via twrp or stock recovery. Also strange that when remounting /system as rw I can push & echo changes to there, but not able to create directories to /data after doing the same.
If someone can help, I will shere needed steps to get this running at Honor 8 frd, unless that will just revel next layer of problems.
*1 Device will boot to OS at first boot, won't boot after restart. So after logs there could b found reasons and now tried to fix those with help of dev and might be at the stage that to create folders just once again will be fix.
*2 I have found only 2 different twrp images, both at version 3.2.1-0 which are suitable for this device, others haven't work at all.
Click to expand...
Click to collapse
I have tried several roms on my honor 8 but It gets stuck with the logo ( Waiting for solutions

Related

Lineageos 14 in V20 H990

Code:
[B][COLOR="Red"]Your warranty is now void.[/COLOR][/B]
I am not responsible for bricked devices, dead SD cards. Please
do some research if you have any concerns about features included in this method
before apply it!
I also do not provide any warranty! The result of a failure could include voiding of warranty and hardware damage.
Be careful! Many of these commands have a high probability of resulting in a brick if mistyped.
What you’ll need
Backup your personal data. It is good idea backup your system with twrp too
Divice Lg V20 H990
Unlocked bootloader and rooted Device ([url]https://forum.xda-developers.com/v20/development/dirtysanta-h990-t3624296[/URL])
ADB (in Linux , windows)
twrp 3.2.1 recovery
New method(07-05-2018)
Here you have an only one zip rom. Flash via twrp, reboot and wait. Please be patient, you have to wait +-18mins.
Works
NFC
gps
call
sms
wifi
Bluetooth
Hotspot
Camera focus and good resolution
STEPs
Download: https://drive.google.com/drive/folders/1zZHGjigoPZq2VNjWAn-Lg4azlTst4UzW
flash
reboot
wait
Old Method
ISSUES
Bluetooth
Hotspot
Camera poor resolution
Other that you find
STEPs
Download Official Lianogeos 14 ROM and save in SDCARD (lineage-14.1-20180405-nighttly-h910-signed.zip)
Download neocore.zip kernel and save in SDCARD ([url]https://forum.xda-developers.com/v20/development/kernel-t3726416[/URL])
Save firmware wifi files (fw_bcm*) from your device (/system/etc/firmware) in your computer
Save configuration file (bcmdhd.cal) from your device (/system/etc/wifi) in your computer
Modify zip of rom to H990:
Open(not uncompress) with some zip program
go to META-INF/com/google
open and edit update-script: replace 910 by 990
save and close
Reboot into Twrp recovery, wipe system, data, cache
flash lineageos
Reboot into Twr
if twrp ask abot password, click cancel, go wipe and format data
flash neocore.zip
Reboot into Twrp
Push wireless firmware into your device (connect your device to pc):
virify your device is ready
Code:
adb devices
into via adb
Code:
adb shell
mount sytem partition
Code:
mount /dev/block/sda14 /mnt
push
Code:
exit
adb push fw_bcmdhd.bin /mnt/system/etc/firmware
adb push fw_bcmdhd_mfg.bin /mnt/system/etc/firmware
adb push fw_bcmdhd_apsta.bin /mnt/system/etc/firmware
adb push bcmdhd.cal /mnt/system/etc/wifi
Reboot into SYSTEM
Enjoy!

Does this work on a H990DS

faeterov said:
Does this work on a H990DS
Click to expand...
Click to collapse
I dont have h990ds but i tried installing SuperV20 custom rom (h990ds Stock-rom based) and that works in h990, MAYBE my solution works in h990ds

You should package the zip folder and is there a result for us to use old nightly ?

I have tried with 20180419 version and this worked fine

Hi,
Possible to package the whole zip ?
@x86cpu

The main point here is that could be posible compile lineageos for h990 only we have to be careful to configure kernel like neocore respect to mode to handle modem and using the correct firmware for gps

XolYnrac said:
The main point here is that could be posible compile lineageos for h990 only we have to be careful to configure kernel like neocore respect to mode to handle modem and using the correct firmware for gps
Click to expand...
Click to collapse
I'm trying build it

joaovictorsouza said:
I'm trying build it
Click to expand...
Click to collapse
Let me know to test

H990ds ???
Is there any H990ds developpement guys ???

So i heard you guys using my kernel for this but have issues with 2nd screen overflow, ill give a try to build one with the lineage patches to prevent overflowing of screen contents in the second screen.

Kernel compiled its in my neocore page, you guys could give it a test. Remeber have a back up, its the only build i have not personally tested cause im not on Lineage
https://forum.xda-developers.com/v20/development/kernel-t3726416

thirdzcee said:
Kernel compiled its in my neocore page, you guys could give it a test. Remeber have a back up, its the only build i have not personally tested cause im not on Lineage
https://forum.xda-developers.com/v20/development/kernel-t3726416
Click to expand...
Click to collapse
The lineage patches should work fine. the kernel I use for TWRP is stock based (which needs either Lineage's patches or manually adjusting twrp's config to stop the overflow), until recently it was 99% stock.

I still find it suss we haven't had any definitive response from someone who has flashed this to say whether or not it's working. No screenshots, anything.

thirdzcee said:
So i heard you guys using my kernel for this but have issues with 2nd screen overflow, ill give a try to build one with the lineage patches to prevent overflowing of screen contents in the second screen.
Click to expand...
Click to collapse
Hi, to me it isnot a disvantage, i consider that like a advantage because meaning we can manipulate the second screen. The task is that in the GUI layer add some area in the upper place, that would give us podinility to put anything in that area more than simple shortcut.
I am speculating because i dont know android architecture.
The other task is identify how neocore handle the modem and introduce that in lineageos kernel.
Yesterday i compiled lineageos based on a installation like this thread. When i installed that i only had problem with modem, wifi worked fine

iDefalt said:
I still find it suss we haven't had any definitive response from someone who has flashed this to say whether or not it's working. No screenshots, anything.
Click to expand...
Click to collapse
I coul give you a screenshot runnig lineageos on my h990.

@XolYnrac
Have you tried using the ported Google Camera to see if the camera resolution / quality issues are resolved?
https://www.celsoazevedo.com/files/android/google-camera/
You could probably try a LOS compatible one, or something by cstark or BSG

jl10101 said:
@XolYnrac
Have you tried using the ported Google Camera to see if the camera resolution / quality issues are resolved?
https://www.celsoazevedo.com/files/android/google-camera/
You could probably try a LOS compatible one, or something by cstark or BSG
Click to expand...
Click to collapse
I will try that but I have tried with that https://forum.xda-developers.com/lg-v30/themes/cstark27-google-camera-mod-wide-angle-t3747263 the resolution is good but the focus isnt work

I'll test in H990DS. I'm building again LineageOS with the H910 binaries.

Here my own compilation of lineageos for h990 with neocore kernel.
In the screenshot we can see the complity screen but I cant see the upper left corner in the cellphone because in this part are the camera and sensors

[ROM] Unofficial LineageOS 15.1 [OPM7.181205.001] for ZTE Blade S6 (P839F30)

Code:
[I]DISCLAIMER[/I]
[COLOR="red"]Do not mirror my builds![/COLOR] Please post a link to this thread instead.
All information and files — both in source and compiled form — are provided on an as is basis.
No guarantees or warranties are given or implied. The user assumes all risks of any damages
that may occur, including but not limited to loss of data, damages to hardware, or loss of
business profits. Please use at your own risk. Note that unless explicitly allowed by the
warranty covering your device, it should be assumed that any warranty accompanying your
device will be voided if you tamper with either the system software or the hardware.
Introduction
This is my unofficial build of LineageOS 15.1 for the ZTE Blade S6 aka P839f30.
This is the first beta release, so be aware that issues could arise.
I have tested this version with my AS variant device. Other variants have to be tested.
Click to expand...
Click to collapse
Features
working:
phone: calls, sms, data.
wifi
bluetooth
sensors
gps: mostly I have used the energy saving mode
sound
camera: rear with flash and front.
torch
headphone detection
swap back and menu button
light: button backlight, brightness control and adaptive brightness, breath light (notification and/or battery)
not working:
SELinux is permissive.
We have to test to find out.
Click to expand...
Click to collapse
Installation instructions
It is best to have installed the latest stock rom beforehand, so modem and all other vendor stuff is up to date.
If you like you can use this mod to have a unified data partition, please proceed with caution.
You will need TWRP or any other custom recovery.
Reboot into recovery and do a nand backup.
Do a factory format.
Download Rom and put it on your phone or use adb sideload.
Install the rom and then clear cache and dalvik cache.
optional: install su and/or gapps (preferable nano).
Please check this prop!
Click to expand...
Click to collapse
Changelog:
16.10.2019 - 2nd stable release:
los security patch level 05.10.
merge upstream kernel from oppo devices
kernel version 3.10.108
30.08.2019 - 1st stable release:
los security patch level 05.08.
use sdcard fs now
updated fs drivers
updated wifi driver
fix line-out, you can use it now
use deep-buffer for audio playback
23.12.2018 - 2nd beta release:
los security patch level 05.12.
cpu min freq. 200MHz, min cpu 0
correct modem and wcnss symlinks.
11.12.2018 - first beta release:
los security patch level 05.11.
standard features working.
Click to expand...
Click to collapse
Downloads
second stable release - 16.10.2019:
Google Drive or here.
first stable release - 30.08.2019:
Google Drive or here.
second beta release - 23.12.2018:
Google Drive or here.
first beta release - 11.12.2018:
Google Drive or here.
If you want root use the lineage addon package found here - download arm version.
Install it after flashing the rom or download your favourite root package and install it.
Sources
device
msm8916-common
vendor
kernel
Click to expand...
Click to collapse
FAQ
Here you will find some answers to common question which could arise.
Q: How to give root access to an app or adb?
A: First install the su extra package from Lineage OS or any other su tool you like. Then go into settings and about device, click there multiple times on the build number until you unlocked the developer options. Go to developer options and look for root access.
Q: There is no weather provider available to download for los-15.1 - what to do now?
A: Search for it here on xda or see this post or use this download link.
Q: I thing I found an issue, what to do now?
A: Do a logcat or grab a dmesg while having the issue, otherwise we can't say what is happening. Report as much info as possible. Quote your stock rom your device shipped with or which device variant you possess.
Click to expand...
Click to collapse
Thanks To/Credits
Code:
*aquaris-dev team
*aymende7
XDA:DevDB Information
Unofficial LineageOS 15.1 [OPM7.181205.001] P839F30, ROM for the ZTE Blade S6
Contributors
lightwars
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Based On: LineageOS 15.1
Version Information
Status: Stable
Current Stable Version: OPM7.181205.001
Stable Release Date: 2019-08-30
Current Beta Version: OPM7.181205.001
Beta Release Date: 2018-12-23
Created 2018-12-11
Last Updated 2019-10-16

The end of the year is coming and some will have a christmas feast before. So this is a small christmas gift for you - LineageOS 15.1 aka Oreo for our phone. Have fun with it.
In my opinion it is better than nougat.

Thanks!!!
Tested and no issues found
Great Rom:good:

Files error
There is an issue with files or smth. Some apps can't get the files (all permissions are given)

d.alvick said:
There is an issue with files or smth. Some apps can't get the files (all permissions are given)
Click to expand...
Click to collapse
Check if your build.prop has "ro.sys.sdcardfs=false" or check with terminal or adb shell:
Code:
getprop ro.sys.sdcardfs
it has to be false.
I have read about some problems with that and found it not to be working at the moment, so I disabled it.

d.alvick said:
There is an issue with files or smth. Some apps can't get the files (all permissions are given)
Click to expand...
Click to collapse
It´s true, with other file manager different from the stock (Root explorer / ES Explorer) I cann't see the files in storage.

lightwars said:
Check if your build.prop has "ro.sys.sdcardfs=false"
Click to expand...
Click to collapse
I've added this key, everything is fine with that now, sdcard is visible for all apps. Also there is a well-known (?) bug with audio/video streaming from web. Playback can't be resumed if I pause it (HD YouTube videos or SoundCloud, for example)

d.alvick said:
I've added this key, everything is fine with that now, sdcard is visible for all apps. Also there is a well-known (?) bug with audio/video streaming from web. Playback can't be resumed if I pause it (HD YouTube videos or SoundCloud, for example)
Click to expand...
Click to collapse
Great that it could be resolved so fast. I will check, why the prop got not in or overwritten. For the second thing: I didn't know that, this is an android oreo thing?

lightwars said:
this is an android oreo thing?
Click to expand...
Click to collapse
Very similar error was in old LineageOS or miui builds for our device or in both of them, I don't quite remember. Tried it again just now, playback is fine... Maybe it depends on device's mood or smth with charging, but I can't repeat it

There are a few more bugs in build.prop. Our SoC is Snapdragon 615 (MSM8939), but you wrote MSM8916 (actually, this is Sd 410). This may not be very good due to the different architecture of these SoCs. Apps, such as the Xposed Framework, identify the phone as armeabi-v7 (32-bit), and in fact it is armeabi-v8 (64-bit). This can affect performance, so I will try to change these keys if there are no reasons why I should leave everything as it is

d.alvick said:
There are a few more bugs in build.prop. Our SoC is Snapdragon 615 (MSM8939), but you wrote MSM8916 (actually, this is Sd 410). This may not be very good due to the different architecture of these SoCs. Apps, such as the Xposed Framework, identify the phone as armeabi-v7 (32-bit), and in fact it is armeabi-v8 (64-bit). This can affect performance, so I will try to change these keys if there are no reasons why I should leave everything as it is
Click to expand...
Click to collapse
These are no bugs! There wont be an impact in performance. Go and look for a device tree which defines msm8939... The platforms msm8ôô916 and msm8939 aren't that different. Even qualcomm defines the values like this, have a look at the CAF. Some vendors habe a common device tree for both platforms, for example asus.
And the last thing the Hardware is 64bit, but the Software is 32bit,changing to armeabi-v8 will not make the Software be 64bit.

Works great so far. Thank you
PS: could unbrick my phone

Update in the OP. new beta release.

2nd beta is fine.
I've been using your LOS ROM's for a while, and there is a question I want to ask. Why do Gapps consume waaay too much battery? 15.1 with Gapps has really the least working time I've ever seen (about 3-4 hours screen-on), 14.1 is better a little (4-6 hours), so I have to charge phone twice a day. On MIUI9 and stock everything wasn't that bad. Now I'm trying 15.1 with no Gapps, and it seems a lot better, 2 hours screen-on and I still have about 60%. Internet is always on. I think Gapps do the thing, but why does working time vary from MIUI9 to 14.1 to 15.1? Or is my battery becoming dead?

d.alvick said:
2nd beta is fine.
I've been using your LOS ROM's for a while, and there is a question I want to ask. Why do Gapps consume waaay too much battery? 15.1 with Gapps has really the least working time I've ever seen (about 3-4 hours screen-on), 14.1 is better a little (4-6 hours), so I have to charge phone twice a day. On MIUI9 and stock everything wasn't that bad. Now I'm trying 15.1 with no Gapps, and it seems a lot better, 2 hours screen-on and I still have about 60%. Internet is always on. I think Gapps do the thing, but why does working time vary from MIUI9 to 14.1 to 15.1? Or is my battery becoming dead?
Click to expand...
Click to collapse
I try to answer your question, but I haven't any insight views or infos, should I could be barely wrong... Over time GApps have gotten more permissions ands task and also more GApps have been published. I think at first there was the syncing of contacts, calendar and sorts of thinks, than the geolocation services. Now we have backups or storage expansion through GApps and also tracking of your fitness, reading out sensor data of your phone. And maybe other sorts of thing, which should make your experience with a smartphone better, but also consums energy.
To emphasizes your feelings about GApps I attach a screenshot of my phone, you can see how often the google service triggers and alarm or wakeup in a span of some hours, roughly speaken every minute.
I stumbled across LKT, which should give you more screen on time. I have used it, but found mixed results. I also think that the battery optimization of 15.1 needs some time, but I could be also wrong.
At the moment I use the naptime app to get more usage, I'm afraid to say this will only help your device last longer, when not used in my opinion.

Hello, I need Help for my Blade S6 (AS version).
LineageOS 15.1 from this thread I do not work, i had a Boot-Loop by the Logo of Lineage ...
The Device will not start again, its only Start in TWRP!
I have tried to go back to CM12 who works before. No chance to get out of this problem ....
I have try to flash the stock-rom with is modifide for TWRP but the result is the same
Coud some one help me to save my phone to get out of the TWRP mode, please?

MouZ124 said:
Hello, I need Help for my Blade S6 (AS version).
LineageOS 15.1 from this thread I do not work, i had a Boot-Loop by the Logo of Lineage ...
The Device will not start again, its only Start in TWRP!
I have tried to go back to CM12 who works before. No chance to get out of this problem ....
I have try to flash the stock-rom with is modifide for TWRP but the result is the same
Coud some one help me to save my phone to get out of the TWRP mode, please?
Click to expand...
Click to collapse
Hi,
have you run the factory reset command from within the android settings menu?
So the device only boots the recovery, even if you select to start the system within TWRP, right?
In the TWRP terminal or from the adb shell with su permission you can try to reset all flags in the misc partition like so:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
You can also back the partition beforehand to be sure, nothing breaks.

Hello lightwars,
thank you for your answer
lightwars said:
have you run the factory reset command from within the android settings menu?
Click to expand...
Click to collapse
No, the Device starts automatically into TWRP after Lineage OS 15.1 has the Boot-Loop
lightwars said:
So the device only boots the recovery, even if you select to start the system within TWRP, right?
Click to expand...
Click to collapse
Yes, i can select Reboot - System, then i see the ZTE-Logo with vibration and then start the TWRP short after this Logo...
If i tipped this Command in the TWRP terminal it shows an Error:
Code:
dd: can't open '/sys/block/bootdevice/by-name/misc' : No such file or directory
I try to go back to the old Partition-Layout and try to flash CM12.1, stock-rom B15 (modifide for TWRP), LineageOS 15... nothing works
I try TWRP 3.0.2 and TWRP 3.2.3
I try to flash CM12.1 with other Kernels with is Modified for CM12.1 from the other thread but it fails too...
What else could I do?
Screen if i install a zip

Wenn ich sys/block im File Manager öffne und mir ansehe sind nur loop0 - loop7, ram0 - ram15, zram0, mmcblk0, mmcblk0pmb, mmcblk1 dateien vorhanden

MouZ124 said:
Wenn ich sys/block im File Manager öffne und mir ansehe sind nur loop0 - loop7, ram0 - ram15, zram0, mmcblk0, mmcblk0pmb, mmcblk1 dateien vorhanden
Click to expand...
Click to collapse
Sorry, my bad. It is not in sys, it is dev so this is the correct command:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc

[UNOFFICIAL] Enhanced TWRP

Enhanced twrp for op3 and op3t
Download from official server:
Download for oxygenos and other non-treble ROMs: https://glassrom.pw/op3_recovery.img
Download for treble ROMs: https://glassrom.pw/op3_recovery-treble.img
Download from CDN:
Download for oxygenos and other non-treble ROMs: https://cdn.glassrom.pw/op3_recovery.img
Download for treble ROMs: https://cdn.glassrom.pw/op3_recovery-treble.img
Unofficial mirrors:
Hosted by @Sytis https://storage.ceres-sys.de/glassrom
Don't ask these questions. Seriously:
Features: none. It's a recovery. It should be as simple as possible because you rely on this stuff to recover your device in case something goes wrong
Seriously. Were you expecting features from a custom recovery?
Screenshots: it looks like TWRP
Important. There is a blank option and a system_root option in the mounts section. These are only for compatibility with scripts. Do not try to tick them yourself
Some scripts may throw a "failed to umount /system_root" message. This is fine
Important: why do some ROMs refuse to flash?
Some ROMs like oxygenos and glassrom use a feature called "downgrade attack prevention". If TWRP's build date is higher than the build date of the ROM the installation script assumes a downgrade attack is happening and the flashing fails
System nandroid restore fails:
You are not supposed to be restoring file-based backups of the system partition on a device with dm-verity in the first place. Backup and restore system image backups.
Glassrom users: if this is your first time flashing glassrom remember that the current enhanced twrp will always have a build date higher than the current glassrom build. In other words you can only flash a newer glassrom build as long as your enhanced twrp build is older or in other words:
Switching to glassrom: use official twrp, flash glassrom and then flash enhanced TWRP to enforce downgrade attack prevention
Updating glassrom: no need to switch to official. Always update glassrom before you update enhanced twrp
This was intentionally done to prevent downgrade attacks on glassrom. Using enhanced twrp with glassrom is recommended
This TWRP addresses a number of issues that have been plaguing the op3:
Uses a backported F2FS driver (5.1-rc1-3.18) that fixes an issue where TWRP would get stuck on the TWRP splash screen for a long time if the user was using F2FS
Uses an upstream kernel that was taken from lineage's common kernel https://github.com/LineageOS/android_kernel_qcom_msm8996
Added all crypto footer code back to resolve all encryption issues
Improved detection of device variant. Recovery now validly detects op3 and op3t
A full selinux policy so that files do not get labelled incorrectly. This resolves a bunch of issues like "device doesn't boot after restoring nandroid"
Built against full lineage source. No minimal manifest or any other nonsense
Upstreamed sdfat driver for better suppport for USB-OTG drives
No prebuilt kernels. Uses a fully source built kernel
Kernel built with a compatible GCC 8. No weird compiler optimisation
Ext4 is the default filesystem instead of f2fs
Current issues: even if the source code is out building TWRP against lineage is not something a beginner can do. If somebody is willing to contribute build documentation they are more than welcome
XDA:DevDB Information
Anupritaisno1's enhanced twrp builds, Tool/Utility for the OnePlus 3
Contributors
anupritaisno1, anupritaisno1, dianlujitao
Source Code: https://github.com/GlassROM-devices
https://bitbucket.org/anupritaisno1/aarch64-linux-gnu
Version Information
Status: Stable
Current Stable Version: 3.3.0
Stable Release Date: 2019-05-01
Created 2019-05-03
Last Updated 2019-05-02

A request to moderators:
People often ask "screenshots" and "features" while this really doesn't make much sense in the context of a recovery. It's a recovery
Please delete such posts to keep the thread clean

Reserved

Feedback:
update-scripts that use run_program("/sbin/busybox) doesn't work as of the latest TWRP builds.

aboodyaiman said:
Feedback:
update-scripts that use run_program("/sbin/busybox) doesn't work as of the latest TWRP builds.
Click to expand...
Click to collapse
Busybox was removed. I've updated my flashable zips to use run_program("/sbin/mount", "/system"); instead.
Replacing 'busybox' with 'toybox' should work too.

Dirk said:
Busybox was removed. I've updated my flashable zips to use run_program("/sbin/mount", "/system"); instead.
Replacing 'busybox' with 'toybox' should work too.
Click to expand...
Click to collapse
Have you tried this*? I'm waiting feedback :silly:
I'm not in a good time for messing around..
*i mean the recovery as general

aboodyaiman said:
Feedback:
update-scripts that use run_program("/sbin/busybox) doesn't work as of the latest TWRP builds.
Click to expand...
Click to collapse
Busybox is pretty terrible and most of it's executables aren't even compliant to standards
Please update your scripts to use toybox or ship the actual statically linked binaries

Dirk said:
Busybox was removed. I've updated my flashable zips to use run_program("/sbin/mount", "/system"); instead.
Replacing 'busybox' with 'toybox' should work too.
Click to expand...
Click to collapse
You should specify the "-o rw,remount" flag otherwise if mount system partition read-only is ticked there's a high chance system is mounted read-only and the script won't actually touch the system partition. This can be achieved by using a shell script instead of run_program()
Your command can also fail with "cannot find /system in the fstab". Instead of calling mount that way you should use this edify command and then call mount with run_program() to make sure it doesn't fail
Code:
mount(fs_type, partition_type, name, mount_point)
Please see https://source.android.com/devices/tech/ota/nonab/inside_packages
Toybox uses a slightly different mount command so merely replacing all instances of busybox with toybox will not work

anupritaisno1 said:
Busybox is pretty terrible and most of it's executables aren't even compliant to standards
Click to expand...
Click to collapse
IMHO bb is much more sophisticated then tb. If compiled with long options enabled bb is more posix compliant then any other multicall binary I know of.
The original decission to replace bb by tb by google was made because of license politics (bb: gnu copy left; tb: apache) - technically bb is superior to tb, for the amount of implememted commands as well as the posix compliance of the implemented commands (if configured correctly). I.e. parts of dns and resolver libs in tb are broken from the beginning of tb used in android (though this doesn't matter in recovery only use). fgrep/egrep are another broken/non-posix-compliant topic, which is solved by adding standalone binaries.
The claim you've made is at least questionable, and since you are publishing your sources (aka complying to gpl), the main reason for not using bb is not true for your twrp builds.
You may consider to put in bb additionally. For los integration, I've made a bb setup not overriding any tb links and installing bb as well as it's links to /system/xbin. With nearly no effort the installation target could be changed to i.e. /xbin or /bb/bin. If the installation dir is added in the path after the path to tb, you'll ship a recovery not only compatible with latest pie sources, but also with backward compatibility for flashable zips relying on bb.
https://github.com/nvertigo/android_external_busybox/tree/nlos-16.0

nvertigo67 said:
IMHO bb is much more sophisticated then tb. If compiled with long options enabled bb is more posix compliant then any other multicall binary I know of.
The original decission to replace bb by tb by google was made because of license politics (bb: gnu copy left; tb: apache) - technically bb is superior to tb, for the amount of implememted commands as well as the posix compliance of the implemented commands (if configured correctly). I.e. parts of dns and resolver libs in tb are broken from the beginning of tb used in android (though this doesn't matter in recovery only use). fgrep/egrep are another broken/non-posix-compliant topic, which is solved by adding standalone binaries.
The claim you've made is at least questionable, and since you are publishing your sources (aka complying to gpl), the main reason for not using bb is not true for your twrp builds.
You may consider to put in bb additionally. For los integration, I've made a bb setup not overriding any tb links and installing bb as well as it's links to /system/xbin. With nearly no effort the installation target could be changed to i.e. /xbin or /bb/bin. If the installation dir is added in the path after the path to tb, you'll ship a recovery not only compatible with latest pie sources, but also with backward compatibility for flashable zips relying on bb.
https://github.com/nvertigo/android_external_busybox/tree/nlos-16.0
Click to expand...
Click to collapse
Thanks. I guess I was wrong about busybox
I'm still not considering shipping busybox. Whenever I've tried it something broke so I'll just be sticking with toybox on that part
What I might be able to do is make a zip that copies busybox to /sbin/busybox and since it's just copying in ram there shouldn't be much of a problem. Users can flash this zip as a way to have backward compatibility with older zips. That sounds like a much better option honestly as then the fix is not just tied to my recovery but can be used on every recovery that doesn't have busybox on the op3
Edit: I also do not think shipping your busybox is a very good idea. You're compiling busybox with this
-Wno-error=implicit-function-declaration -Wno-implicit-function-declaration
Click to expand...
Click to collapse
I don't even know why this is a compiler warning. This should be an error but if you're shipping busybox with that warning disabled instead of fixing it that's just asking for trouble

anupritaisno1 said:
What I might be able to do is make a zip that copies busybox to /sbin/busybox and since it's just copying in ram there shouldn't be much of a problem.
Click to expand...
Click to collapse
...and on every second page of this thread, you'll be asked, if flashing bb is necessary on each update. Then you'll need to answer every time: "no, you need to flash it prior to each flashing of a bb needing zip."
If you just say bb is droped upstream and you want to keep your twrp clean.
Anyway: I've fixed the static build target.
anupritaisno1 said:
Edit: I also do not think shipping your busybox is a very good idea. You're compiling busybox with this
Click to expand...
Click to collapse
Thanx for the heads up - you are absolutly right here! (This was on my todo list more then 2 years ago, then I fogot to do it... I don't like people pointing me to my old and forgotten todos... )
https://github.com/nvertigo/android_external_busybox/commit/f512d6cbb4181970b47383a6efe0c01f27a0d978

nvertigo67 said:
...and on every second page of this thread, you'll be asked, if flashing bb is necessary on each update. Then you'll need to answer every time: "no, you need to flash it prior to each flashing of a bb needing zip."
If you just say bb is droped upstream and you want to keep your twrp clean.
Anyway: I've fixed the static build target.
Thanx for the heads up - you are absolutly right here! (This was on my todo list more then 2 years ago, then I fogot to do it... I don't like people pointing me to my old and forgotten todos... )
https://github.com/nvertigo/android_external_busybox/commit/f512d6cbb4181970b47383a6efe0c01f27a0d978
Click to expand...
Click to collapse
I haven't really checked the code but I'm not that sure about this part
Shouldn't it be like
Code:
#ifndef _GNU_SOURCE
#define _GNU_SOURCE
Idk just sounds more correct that we don't want a redefinition here

Is there any need for a manual mount of 'fakecache' like in Enhanced TWRP of OP2 ?
I hope not...
Thanks for the development !

gps3dx said:
Is there any need for a manual mount of 'fakecache' like in Enhanced TWRP of OP2 ?
I hope not...
Thanks for the development !
Click to expand...
Click to collapse
The entire fakecache experiment was me trying to port treble to the op2
That obviously failed and I'm in the process of removing that hack even from the op2
It's not there on this TWRP. That's for sure

F2FS 5.2-rc1-3.18 is out
The update will first arrive on glassrom and then on enhanced TWRP

anupritaisno1 said:
F2FS 5.2-rc1-3.18 is out
The update will first arrive on glassrom and then on enhanced TWRP
Click to expand...
Click to collapse
Glassrom is out but I've sadly not received any feedback from the twrp testers yet
The new release might be delayed and I'm also busy working on op2
It will definitely come in 1-2 days

Glad you made this twrp @anupritaisno1.
Working great here and happy to see all issues I had with other versions (some warnings on terminal, time issues etc...) are gone!
Keep up the good work

@anupritaisno1
Any chance your TWRP is not compatible with PIE ? ( i.e either that PIE is not supported or PIE is NOT the highest SDK supported )
I ask since many users across OP3 & 3T forum complained about "BSoDwWL" (Black Screen of Death with White Led ) issue that appear randomly ( not during recovery, but in android ) and freeze the device for ~15sec which ends in systemUI reboot.
I'm not sure, but around the week I updated myy recovery to your TWRP, I started to suffer for that issue - which is partially in accordance with this report - i.e that SOME TWRP is responsible
please don't get me wrong... as it might be TWRP original code fault - not something directly related to your own wonderful work here.
I wonder if you encountered this issue as well ?
Does TWRP 3.3.x is already Q compatible ? what's the LAST twrp version that its higher SDK support is PIE (3.2.x / 3.1.x ) ?

gps3dx said:
@anupritaisno1
Any chance your TWRP is not compatible with PIE ? ( i.e either that PIE is not supported or PIE is NOT the highest SDK supported )
I ask since many users across OP3 & 3T forum complained about "BSoDwWL" (Black Screen of Death with White Led ) issue that appear randomly ( not during recovery, but in android ) and freeze the device for ~15sec which ends in systemUI reboot.
I'm not sure, but around the week I updated myy recovery to your TWRP, I started to suffer for that issue - which is partially in accordance with this report - i.e that SOME TWRP is responsible
please don't get me wrong... as it might be TWRP original code fault - not something directly related to your own wonderful work here.
I wonder if you encountered this issue as well ?
Does TWRP 3.3.x is already Q compatible ? what's the LAST twrp version that its higher SDK support is PIE (3.2.x / 3.1.x ) ?
Click to expand...
Click to collapse
Please get me a copy of /sys/fs/pstore/console-ramoops-0 on the next boot after the crash

gps3dx said:
@anupritaisno1
Any chance your TWRP is not compatible with PIE ? ( i.e either that PIE is not supported or PIE is NOT the highest SDK supported )
I ask since many users across OP3 & 3T forum complained about "BSoDwWL" (Black Screen of Death with White Led ) issue that appear randomly ( not during recovery, but in android ) and freeze the device for ~15sec which ends in systemUI reboot.
I'm not sure, but around the week I updated myy recovery to your TWRP, I started to suffer for that issue - which is partially in accordance with this report - i.e that SOME TWRP is responsible
please don't get me wrong... as it might be TWRP original code fault - not something directly related to your own wonderful work here.
I wonder if you encountered this issue as well ?
Does TWRP 3.3.x is already Q compatible ? what's the LAST twrp version that its higher SDK support is PIE (3.2.x / 3.1.x ) ?
Click to expand...
Click to collapse
Hi I checked this myself
There seems to be absolutely no difference between drivers from 5.0.8 and 9.0.2
It feels as if oneplus simply took the drivers from 5.0.8 and smashed them onto 9.0.2 so I have no idea what crashes you're observing. Please submit logs

How To Guide [OUTDATED - PLEASE USE UNOFFICIAL LINEAGEOS INSTEAD] Installing a GSI on Samsung M12/A12.

I am deleting this guide since M12 will soon recieve an unofficial build of LineageOS 19.1. Don't ask when, as I'm not the lead developer but I helped with it

Update 1: I figured out how to make script run on boot. Instructions revised. If you followed earlier check them again
Update 2: Magisk 24.1 is now stable. Instructions revised.
Update 3: I contacted phh and he implemented the script inside his trebleapp. Instructions revised and modified trebleapp is attached. NOTE: GSIs newer than 7/Feb/2022 will include this workaround by default.
Update 4: This guide is now unnecessary now that unofficial LineageOS is very close to release

Achievement unlocked: flashed GSI with FBE enabled!
{
"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"
}
In short, I've successfully done flashing of @phhusson's latest version of Android 12 GSI (which is v402 as of today). To do this, I needed to modify the multidisabler script so it won't disable FBE, format the userdata using the stock recovery, flash TWRP, resize tmpfs to proper size, push GSI image into tmpfs and flash it using TWRP. I used the securized image with vndklite variant, since there was no securized images for regular vndk releases (but it seemed that vndk was working better for me, at least I have no USB connection anymore where with VNDK I was able to have USB debugging). Maybe I'll try re-flashing it once I'll patch the regular images and securize them (since I'm on *nix, I can just mount them and modify their contents) and take an approach of finding how Samsung ROMs are working OK. For now, I need to take a break from all bootloops I had in the process of FBE flashing .
Anyway, the goal of this experiment was to use GSI ROMs as a daily driver and having FBE disabled could otherwise cause a serious problem on device loss.
So, onto the list what's been tested (that wasn't noted before):
Screen locking – it seems that the workaround for the screen is not applied before unlocking the phone, probably because the app is not running yet. This might work with the script used as postfs module.
EDIT: I've found some notes in the Magisk documentation that both post-fs data and late_start services are run after data is decrypted, which basically means applying this workaround using Magisk seems to be pointless for now (maybe not after PPH app will stop providing the workaround)... Probably the best option would be patching the ROM itself, either with flashable ZIPs or directly before flashing it (most GSIs can be mounted under Linux and tweaked).
Adaptive brightness – not working, since all virtual sensors are not working for now. Might be easy to fix through as I've found some stuff in the official ROM that I had an idea to experiment with putting them into GSIs (as a Magisk module, to avoid a breakage).
USB – as I said, a data transfer via USB is not working for me for some reason. It worked for me once I had VNDK Android 12 GSI installed (same version).
Booting with stock kernel – I had some successful attempts doing that, but it further was a cause of a bootloop, at least once I had installed Magisk. Therefore, I'll recommend patching the Magisk the way as in tutorial (after patching the kernel) to have everything working for now.
For people who wants to play with stock images but don't know how: you can use simg2img, lpunpack and Linux to extract and mount the official ROM image in approach of finding there some tips like in initrc services why some stuff is working fine on Samsung while it doesn't on GSIs. Maybe I would tinker with it a bit, trying to export a few services and libraries in an approach to create a Magisk module with all stuff needed to have a fully functional GSI, but I'm tired of modding for now, especially when this is my first Samsung phone I had to deal with.
Edit: Typo fixes, added additional text formatting.

Amazing work. If you need testers feel free to PM me. As a sidenote, poking in sysfs led me to believe that android is sending the info needed to read the proximity but the kernel is sending garbage which gets interpreted as the sensor not being triggered. Also phh should have added the workaround into his trebleapp starting from phh AOSP 12 v401, so aside from installing magisk no post install workarounds should be needed.
Attached is a photo of what cmd_result reads when a whatsapp voice message is played which reads proximity to play the message in the earpiece and turn screen off when proximity is triggered

ap4ss3rby said:
Also phh should have added the workaround into his trebleapp starting from phh AOSP 12 v401, so aside from installing magisk no post install workarounds should be needed.
Click to expand...
Click to collapse
Unfortunately, the commit was reverted as of master branch, so we should prepare for it to stop to work unless phh will work on it before releasing an another version. Also I wrote that the workaround didn't seem to apply itself before unlocking the phone (FBE encrypted) the first time and therefore decrypting sensitive data after boot. For now this makes it an requirement when using PHH app to unlock the phone before it sleeps so the touch is going to be responsive.
Anyway, it seems that even Magisk (v24.1) is not capable of running the services before data is decrypted, so now I have no idea how to bypass that in other way than patching the ROM itself and creating the `initrc` service... Anyway, this is also a hint that what samsung is doing starts before basically everything, so no APK file nor script is going to really fix it since they are meant to start after data is decrypted...

SB3P said:
Unfortunately, the commit was reverted as of master repo, so we should prepare for it to stop to work unless phh will work on it before releasing an another version. Also I wrote that the workaround didn't seem to apply itself before unlocking the phone (FBE encrypted) the first time and therefore decrypting sensitive data after boot. For now this makes it an requirement when using PHH app to unlock the phone before it sleeps so the touch is going to be responsive.
Anyway, it seems that even Magisk (v24.1) is not capable of running the services before data is decrypted, so now I have no idea how to bypass that in other way than patching the ROM itself and creating the `initrc` service... Anyway, this is also a hint that what samsung is doing starts before basically everything, so no APK file nor script is going to really fix it since they are meant to start after data is decrypted...
Click to expand...
Click to collapse
I guess for now we have two options:
A: Build custom kernel/vendor specifically for GSIs that correctly reports sensors as GSIs expect them to
B: Fix GSI issues through Magisk services implementing various workarounds in scripts. (an example is the touchscreen sleep/wake issue)

ap4ss3rby said:
Attached is a photo of what cmd_result reads when a whatsapp voice message is played which reads proximity to play the message in the earpiece and turn screen off when proximity is triggered
Click to expand...
Click to collapse
Also that's interesting those virtual sensors are still present, I personally thought that Samsung made it the way there's an virtual device create as on Linux and there's their proprietary software running somewhere in the system that uses the camera as an input and calculates it to provide the data... On the other hand, when I think about that logic, even some (if not all) virtual devices on Linux (e.g. v4l2loopback) needs to have their module loaded with the kernel to work. I'm glad at least there's no need to reinvent the wheel and no one really needs to recreate the entire algorithm for it if it's going to be in the kernel sources...
ap4ss3rby said:
I guess for now we have two options (...)
Click to expand...
Click to collapse
I feel like the B option is worse than patching the GSI ROMs, either via flashable ZIPs or on your own... This is because I couldn't find anything in docs that would let me run services before /data is going to be decrypted... Personally, I've made myself a such service using the statically-compiled Linux ARM binary (non-NDK, using GNU libs – yes, it is still runnable on Android as well) – it applies the workaround for now both when screen is turned on and off (I had no idea on which event it should really run, so I made it to run on both just to be safe) by watching the file changes based on (AFAIK) filesystem events – so it has a major advantage over your script, as it won't run in endless loop, yet watch the file responsible for brightness to change and then do its job. But even with that, TSP doesn't seem to make touch available immediately and it is still expected to be revived after 1-2 seconds.
Also, as of the methods of applying these workarounds, the other way could be modifying the ramdisk (maybe with the help of Magisk, which I believe has documented how it's actually doing it itself and how others could modify the root and init as Magisk does to load files before the OS will properly initalize itself. Yet I don't like an idea of messing myself with the boot partition, at least for now...

Debug info: I tried flashing stock to grab logs from the touchscreen driver. The logs attached here do not appear at all on an unpatched GSI (I.E flashing the GSI as is without any touch workaround).

ap4ss3rby said:
Hi, I installed LineageOS 18.1 GSI on my M127F. I want to share my guide to installing this GSI.
Code:
DISCLAIMER:
By following this guide you accept that you
may do irreversible damage to your phone.
If something breaks the responsibility is
yours only. If you want stable software that
is guaranteed to work 100% don't follow
this guide.
I assume you are running a fully stock system and and locked bootloader and firmware U3/U4.
Installing TWRP and custom kernel
Enable Developer Options by tapping on software information > build number 7 times
Enter developer options then toggle OEM Unlocking on.
Power off your phone.
Hold Vol Up + Vol Down then plug in your phone to enter download mode
THIS WILL ERASE ALL YOUR DATA AND VOID YOUR WARRANTY. Follow on screen instructions to unlock your bootloader. THIS WILL ERASE ALL YOUR DATA AND VOID YOUR WARRANTY
After this you want to download and install attached Orangefox recovery using odin. After odin is done flashing enter recovery
Format data (not wipe) in recovery
Enter terminal and type multidisabler twice
Reboot to system and verify that under security encryption is disabled
Download TWRP and custom kernel for your phone
Reboot into recovery and locate the downloaded twrp image
Select recovery.
Reboot into recovery
Install kernel, then wipe cache and reboot. You should now see that it is complaining about some internal issue. This is normal.
Installing the GSI
Download your favorite ROM from the list provided below. You want to install an arm64 a/b image.
Extract the image file
Reboot to recovery.
Select install then install image
Locate the GSI image
Select install system
After that is done return to recovery and select factory reset.
Reboot then do setup (if applicable) then download attached magisk and phh trebleapp. If your phone is stuck on bootanimation check under to fix it.
IMPORTANT: DO NOT LET THE SCREEN TURN OFF OR YOU WILL HAVE TO REBOOT TO MAKE TOUCH WORK AGAIN.
Install attached magisk
Open magisk and click on install then direct install
Download and install the attached phh-treble app apk.
Touch should now work. Enjoy your GSI.
Extras
Magisk 24.1
Open Magisk
Go to settings
Update Magisk Manager app to version 24.1
Relaunch Magisk then install magisk
Choose direct instal
Migrating to patched trebleapp
Download and install attached trebleapp
Open your root file manager
go to /data/adb/service.d
Delete the script you added earlier
Tips in case things don't work
In case after rebooting to the GSI the phone bootloops:
Download stock image from wherever you download your firmware (I use a python program called samloader)
Extract the AP of the downloaded firmware
Find userdata.img.lz4 and create a .tar archive only containing this file
Reboot to download mode
In odin select AP then locate the newly created .tar archive Then click on flash
Reboot
Continue from step 7 under the "Installing the GSI" portion of the guide
To revive the touchscreen using ADB:
In case you didn't grant adb root access but installed magisk, run adb shell then su. A root access for the app shell will appear. Grant root permission
Plug in phone to a computer with ADB
adb shell
su
cat /sys/class/sec/tsp/cmd_result
echo check_connection > /sys/class/sec/tsp/cmd
What works:
Boots
RIL
Fingerprint
Main rear camera
Front camera
Sleep/Wake (workaround in steps above, may need to sleep wake several times before it works)
WiFi
Flashlight
Rotation
Magisk 24
90Hz (M12 only. A12 doesn't have 90Hz refresh rate)
LineageOS 18.1
LineageOS 19
CAOS (GApps variant available)
phh AOSP 11 v313
phh AOSP 12 v400h
Untested
GPS
Flashing GApps. (I use fdroid and aurora store on LineageOS and CAOS has built in GApps)
USB-OTG
A127F
M127G
If I didn't list it under broken or working I didn't try it or forgot to test it.
Broken
Double tap to wake. Touchscreen turns off and I have no idea how to keep it alive while lcd is off
MTP
Virtual Proximity. Screen will stay on in phone calls and WhatsApp will always play voice messages through speaker
Flashlight brightness. Flashlight will always stay on weakest brightness with no way to adjust.
Adaptive refresh. The framerate you set in phh addons is what you get. Be prepared for slightly reduced battery.
You tell me (even though I probably don't have the solution)
Bugs
You may need to wait a little bit before touchscreen responds or sleep/wake several times before screen responds after turning the screen off
Credits
@physwizz for kernel, TWRP and orangefox
@phhusson for implementing workaround in trebleapp as well as GSI list
me for touch workaround
Links
Kernels and recoveries: https://t.me/a127f_res/113
GSIs: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Click to expand...
Click to collapse
Great guide.
Well done

Thanks for the great guide. Unfortunately, I don't know how to resize tmpfs. Can anybody tell me how to do that? I only have 4 GB or less on my Samsung Galaxy A12 with 64 GB of Storage (it should have, it only shows something like 3 or 4 gigabytes like I mentioned)

matahbeyz said:
Thanks for the great guide. Unfortunately, I don't know how to resize tmpfs. Can anybody tell me how to do that? I only have 4 GB or less on my Samsung Galaxy A12 with 64 GB of Storage (it should have, it only shows something like 3 or 4 gigabytes like I mentioned)
Click to expand...
Click to collapse
You don't have to resize TMPFS if you don't want to have FBE encryption or have the external SD card (you can use microSD for flashing, which might be a better choice if you need to flash a larger devices). Also you can't resize TMPFS to 64 GB, it uses your RAM to store regular data instead of storage (this is basically the concept of TMPFS). What I was mentioning is that /data won't work under FBE and custom recoveries for now, so you need to use your RAM instead if you don't have any external storage device to save images somewhere via ADB.
As of resizing the TMPFS, you should be able to find some Linux tutorial how to do that, on Android this is works basically the same (even on both Linux and Android you have /tmp directory with TMPFS by default).
Anyway, I've decided to share some stuff that you may need for that. Here's the multidisabler script I was using for flashing GSIs with FBE encryption preserved. I was also working on the native binary that would work as the workaround for the touchscreen so it can be used instead of the script. The advantages are that it actually listens to filesystem events and therefore does not need to read file in loop in order to get the information if brightness has changed. Maybe I'll share it with you once I find it to be ready, right now I'll just share my multidisabler script with patches.
BTW, I've tested LineageOS GSIs (both 11 and 12) and noticed they behave completely different, no matter of variant (the USB actually uses some driver, which is not fully compatible with M12 but close enough to provide basic communication through ADB). I guess pphusson just changed something and now these drivers aren't applied by default, yet I think I've noticed the issues with Bluetooth's HSP/HFP profiles which as I remember was not the case with latest stable pphusson's vanilla Android 12 GSIs. Now I just hope these problems are going to be resolved in the next builds of Android's GSIs with phhusson's patches and with the knowledge that MTP just worked fine on TWRP I used, there's a little hope that we will gain the proper combination of drivers/firmware to have both USB and Bluetooth functional at the same time someday.
I've also approached patching the kernel under newer kernel base 4.19.112, yet I gave up on properly resolving its conflicts. I may work on that as well in order to patch some vulnerabilities, with a hope that I'll succeed updating kernel as closest to the latest patch as possible. The 4.19.112 is going to be just a test if Samsung is capable of actually booting from it and if I may be able to use git with common human logic and my limited programming skills to actually patch it the way it would do so (without much understanding about the code itself, yet basic knowledge about C syntax). For now I've only succeed reproducing the upstream Linux kernel commit structure from 4.19.111, with a single additional commit for Samsung changes and another one for physwizz ones.

can anyone guide me how to unlock bootloader on Samsung Galaxy M12G ?

@SB3P Thanks so much. Sorry for my late reply, but thank you!

SB3P said:
Achievement unlocked: flashed GSI with FBE enabled! View attachment 5533799In short, I've successfully done flashing of @phhusson's latest version of Android 12 GSI (which is v402 as of today). To do this, I needed to modify the multidisabler script so it won't disable FBE, format the userdata using the stock recovery, flash TWRP, resize tmpfs to proper size, push GSI image into tmpfs and flash it using TWRP. I used the securized image with vndklite variant, since there was no securized images for regular vndk releases (but it seemed that vndk was working better for me, at least I have no USB connection anymore where with VNDK I was able to have USB debugging). Maybe I'll try re-flashing it once I'll patch the regular images and securize them (since I'm on *nix, I can just mount them and modify their contents) and take an approach of finding how Samsung ROMs are working OK. For now, I need to take a break from all bootloops I had in the process of FBE flashing .
Anyway, the goal of this experiment was to use GSI ROMs as a daily driver and having FBE disabled could otherwise cause a serious problem on device loss.
So, onto the list what's been tested (that wasn't noted before):
Screen locking – it seems that the workaround for the screen is not applied before unlocking the phone, probably because the app is not running yet. This might work with the script used as postfs module.
EDIT: I've found some notes in the Magisk documentation that both post-fs data and late_start services are run after data is decrypted, which basically means applying this workaround using Magisk seems to be pointless for now (maybe not after PPH app will stop providing the workaround)... Probably the best option would be patching the ROM itself, either with flashable ZIPs or directly before flashing it (most GSIs can be mounted under Linux and tweaked).
Adaptive brightness – not working, since all virtual sensors are not working for now. Might be easy to fix through as I've found some stuff in the official ROM that I had an idea to experiment with putting them into GSIs (as a Magisk module, to avoid a breakage).
USB – as I said, a data transfer via USB is not working for me for some reason. It worked for me once I had VNDK Android 12 GSI installed (same version).
Booting with stock kernel – I had some successful attempts doing that, but it further was a cause of a bootloop, at least once I had installed Magisk. Therefore, I'll recommend patching the Magisk the way as in tutorial (after patching the kernel) to have everything working for now.
For people who wants to play with stock images but don't know how: you can use simg2img, lpunpack and Linux to extract and mount the official ROM image in approach of finding there some tips like in initrc services why some stuff is working fine on Samsung while it doesn't on GSIs. Maybe I would tinker with it a bit, trying to export a few services and libraries in an approach to create a Magisk module with all stuff needed to have a fully functional GSI, but I'm tired of modding for now, especially when this is my first Samsung phone I had to deal with.
Edit: Typo fixes, added additional text formatting.
Click to expand...
Click to collapse
Could you explain how you done this.... i mean please explain step by step... i am using Galaxy M12G Varient....thanks in advance

milindbhaliwade said:
Could you explain how you done this.... i mean please explain step by step... i am using Galaxy M12G Varient....thanks in advance
Click to expand...
Click to collapse
If you would see the *untested* section at the initial post of this thread, it is unknown whetever this works or not for M127G phones (if it bootloops it might not work at all). Anyway, here's how I did it on M127F (at least how I remember this):
1. I did steps from 1-6, I believe I skipped 7 since I was aware it will mess something up with the data partition.
2. I modified the multidisabler script and pushed it to my phone via the ADB (to TMPFS). You can find this script pushed as xz compressed file. Before executing multidisabler script I have done a backup of the recovery and system partitions (using dd tool) which I am going to reflash later.
3. I rebooted to download mode and flashed TWRP image.
4. After TWRP ended flashing, I booted into the recovery. I flashed the physwizz kernel and then my own GSI image as it was described in the instructions at the initial post. Just remember that /data partition is not functional with FBE and TWRP so you need to push your images somewhere else like microSD card or TMPFS partition. OTG might work here as well, this is something I haven't tested yet through...
5. Once you are done with flashing you need to restore the original recovery partition via the download mode. TWRP won't boot the GSIs with FBE encryption enabled actually it does boot now for me, yet I still recommend switching to stock recovery if your phone bootloops or you need to format/wipe userdata partition. You can then safely format your /data partition with the stock recovery.

For anyone who has starred this thread, I and other devs have released a proper build of LineageOS with /vendor. Aside from VoLTE (which I don't think worked in GSIs anyways) everything should work. Moderators, please close this thread

ap4ss3rby said:
For anyone who has starred this thread, I and other devs have released a proper build of LineageOS with /vendor. Aside from VoLTE (which I don't think worked in GSIs anyways) everything should work. Moderators, please close this thread
Click to expand...
Click to collapse
LineageOS is not only GSI available, I think someone might still find it useful if they want to flash another ROMs. Also Phhuson's GSI also contains some features that unofficial GSI release don't have (i.e. flashlight control in Phhusson's app), so they still might be useful for someone.
This is why I think it is better to not close this thread and maybe revive original guide.

SB3P said:
LineageOS is not only GSI available, I think someone might still find it useful if they want to flash another ROMs. Also Phhuson's GSI also contains some features that unofficial GSI release don't have (i.e. flashlight control in Phhusson's app), so they still might be useful for someone.
This is why I think it is better to not close this thread and maybe revive original guide.
Click to expand...
Click to collapse
Our rom is built completely from source, not a GSI, and it is more or less a complete replacement of stock firmware. If you want you can use a GSI over that instead, and it should function much better than just replacing stock firmware

ap4ss3rby said:
Our rom is built completely from source, not a GSI, and it is more or less a complete replacement of stock firmware. If you want you can use a GSI over that instead, and it should function much better than just replacing stock firmware
Click to expand...
Click to collapse
I haven't said GSI are better, I personally use this unofficial LineageOS build. But what I've said, GSI brings much more variety of picking the OS you can install. Even Linux can be installed on phones nowadays using GSI with only Halium-patched kernel as an requirement. This is why I think leaving this tutorial archived (no updates, interest on fixing bugs etc.) is better than removing it.

Development [ROM][Unofficial][pdx214][13] crDroidAndroid 13.0 - 2023-04-27

crDroid Android is a free firmware distribution of Android 13, which is designed to increase performance and reliability over stock Android for your device.
crDroid is based on the LineageOS & Android Open Source Project with extra contributions from many people within the Android community.
All the source code for crDroid is available in the crDroid GitHub repo
Basic requirements:
Unlock your bootloader, make sure you are on Android 13 firmware (tested over 61.2.A.0.410)
Make sure you can send and receive SMS and receive calls (also via WiFi and LTE, if possible). It would be better for you to get VoLTE/VoWiFi utilized once on stock to provision IMS
Currently tested on XQ-BQ52 (Global version)
Current build has no Gapps built-in so it's up to you either to stay Gapps-less or flash Gapps version you want (I would recommend NikGapps personally)
Make sure you have gone through the installation guide once before proceed!
Installation:
Flash additional partitions and recovery.
Download the following files from the download link:
dtbo.img
vendor_boot.img
boot.img
Connect your device to your PC via USB if isn't already
If your device is not already in fastboot mode, on the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type:
Bash:
adb reboot bootloader
Flash the downloaded image files to your device by typing:
Bash:
fastboot --set-active=a
fastboot flash dtbo_a <dtbo>.img
fastboot flash vendor_boot_a <vendor_boot>.img
fastboot flash boot_a <boot>.img
Now reboot into recovery to verify the installation:
Bash:
fastboot reboot recovery
Installing ROM from recovery
Download the crDroid installation package that you would like to install from the download link
If you are not in recovery, reboot into recovery
Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
Return to the main menu
Sideload the crDroid package
On the device, select "Apply Update", then "Apply from ADB" to begin sideload
On the PC, sideload the package using:
Bash:
adb sideload filename.zip
Return to the main menu
(Optionally) If you want to install any add-ons (Gapps, Magisk..), click "Advanced", then "Reboot to Recovery", then when your device reboots, click "Apply Update", then "Apply from ADB", then "adb sideload filename.zip" those packages in sequence.
Once you have installed everything successfully, click the back arrow in the top left of the screen, then "Reboot system now"
Downloads:
https://sourceforge.net/projects/xperia5iii/files/crdroid13/
Device Trees & Kernel Source:
https://github.com/faust93/android_device_sony_sm8350-common
https://github.com/faust93/android_device_sony_pdx214
https://github.com/xperiaossdev/kernel_sony_sagami
Build Information
Device: Xperia 5 III (pdx214)
Build Type: Unofficial
ROM OS Version: 13
Kernel Version: 5.4.219-Krispy-v1.2
Kudos:
@Sakuu
@clfbbn

Changelog
2023-04-27:
- crDroid v9.4
- kernel side tuning and optimisations
2023-04-15:
- crDroid sources repo sync
- performance optimizations
- HW assistant button gestures fix: single, long, double click works and can be re-assigned

Geez, our first custom ROM! Thank you very much for your efforts :^)
Any list of what's working and not working?

Gray47Maxx said:
Geez, our first custom ROM! Thank you very much for your efforts :^)
Any list of what's working and not working?
Click to expand...
Click to collapse
My daily driver for about a week now. Haven't found any problems so far. Seems everything to be working. But for sure we need more testing..

faust93 said:
My daily driver for about a week now. Haven't found any problems so far. Seems everything to be working. But for sure we need more testing..
Click to expand...
Click to collapse
Neat! Based on stock, I guess?

Gray47Maxx said:
Neat! Based on stock, I guess?
Click to expand...
Click to collapse
Well, it's not GSI if that's what you meant. Closed source proprietary blobs are taken from stock ROM, otherwise just fully-fledged build from crDroid sources.

faust93 said:
Well, it's not GSI if that's what you meant.
Click to expand...
Click to collapse
Not exactly. There's an initiative called SODP which provides all the necessities and binaries to build anything you want. Alas, usually it's not stable enough, especially on newer devices with hard configurations (like with our periscope camera).
Anyway, gonna test crDroid today and report anything I'd find interesting or worth noting

Gray47Maxx said:
Not exactly. There's an initiative called SODP which provides all the necessities and binaries to build anything you want. Alas, usually it's not stable enough, especially on newer devices with hard configurations (like with our periscope camera).
Anyway, gonna test crDroid today and report anything I'd find interesting or worth noting
Click to expand...
Click to collapse
Aah, I see. It's my first SONY device so I'm not aware about all the nuances yet No, it's not SODP based build.

thanks very nice rom

Good work, btw might want to do a rebuild with the newest Krispy version, major speedups on the 1 III that's running Krispy-v1.2.1 plus some battery life improvement, maybe I'll do 5 III builds too, if I get any testers that is.

Just installed this. Feels like I've been waiting ages for a custom ROM, and now here it is!
So far it seems too good to be true, not a single issue yet.

Sakuu said:
Good work, btw might want to do a rebuild with the newest Krispy version, major speedups on the 1 III that's running Krispy-v1.2.1 plus some battery life improvement, maybe I'll do 5 III builds too, if I get any testers that is.
Click to expand...
Click to collapse
Will test later today. Curious to see if refresh rate can be locked @ 120hz. The GSI builds I tried on A11 and A12 were stuck at 60

bhow11 said:
Will test later today. Curious to see if refresh rate can be locked @ 120hz. The GSI builds I tried on A11 and A12 were stuck at 60
Click to expand...
Click to collapse
Of course you can lock that dunno if he added the stuff for the refresh rate qs tile though

Sakuu said:
Of course you can lock that dunno if he added the stuff for the refresh rate qs tile though
Click to expand...
Click to collapse
Just a prop edit?

bhow11 said:
Just a prop edit?
Click to expand...
Click to collapse
Not even that, i think you can turn it on from the settings, but qs tile is more convenient

All good thus far

Will google wallet work with this ROM?

dima_vy said:
Will google wallet work with this ROM?
Click to expand...
Click to collapse
For me it works. Magisk Delta does the trick.

After using it for a few days, it is very stable and smooth, the battery performance is also great, thank you for your efforts

Cannot get Photo Pro and other sony app running after install sony framework in Magisk delta. Any one else has the same issue?

Database Info

welcome