yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] Alvin50:
Thank you for your kind reply

In the meantime, just for sake of clarity, I reinstalled TWRP and then all LOS18.1 again.

So I can report that the same reboots occur again, maybe with lower frequency.

Now I'll try to resize as you suggest. Let's hope it succeeds in fixing.

Kind regards

Edit: Sadly, no way... resizing didn't fix the random reboot. Thank you, anyway.

Edit1: reboots look to be temporized to near 24 minutes: I registered a reboot at 11:22, 11:46:,12:10, 12:35, 12:59.

Shall I send any log to help debugging? Please tell me.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
As usual...
[Treble-Enabled Device Development A/AB ROMS] :
It could be a matter of system partition size. Older models have this problem sometimes, even with newer custom ROM (not only with gsi). Try to ask in J5 thread if there's a tool to extend system partition.
[Treble-Enabled Device Development A/AB ROMS] Alvin50:
Thank you for your kind reply.

I'm going to download the last AOSP 11.0 v300.I from phhusson's github, but am in doubt: is it right the system-roar-arm64-aonly-vanilla.img.xz ?

I tried it anyway, but it shall be a wrong one, gives reboot just out of recovery.

Any hint, please?
[Treble-Enabled Device Development A/AB ROMS] Alvin50:
Thank you for the suggestion, but this time I think it's best I follow AndY Yan and go to test phhusson's last AOSP.

Kind regards
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Which build of mine did you download? PHH named his build clearer than mine actually...
[Treble-Enabled Device Development A/AB ROMS] Alvin50:
lineage-18.1-20210212-UNOFFICIAL-treble_arm64_avS.img. In Phh Github AOSP page I only saw those system-roar files, and thought that that one was the more likely right... BTW, your LOS works well, with the said minor problems, while Phh file is on infinite reboot, for sure it's my fault, I downloaded the wrong item, but cannot figure which is the right one.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Sounds like the correct one, now that's a more baffling situation than your original bug... v300.m is available, mind trying that?
[Treble-Enabled Device Development A/AB ROMS] Alvin50:
Can you please address me to it? In PHH page I'm seeing AOSP 11.0 v300.I (release 84) is defined as the latest.

Edit: Never mind: found! I didn't see it before because it's a pre-release.

Now I go and try.

Edit: I have tried it, same result. It's a weird thing.

To be safe, I installed it as follows:

Factory reset

Format Data

wiping Dalvik, System, Data, Cache

Reboot to recovery

flash Exynos7870_RevertVendor_2.0.zip

Reboot to recovery

flash Exynos7870_CreateVendor_2.0.zip

Reboot to recovery

flash Exynos7870_ProjectSpagetX.zip

Reboot to recovery

install system-roar-arm64-aonly-vanilla.img

That's my usual procedure when performing a clean install.

And I stress that all usual ROMs behaved as expected.

Any hint?

Ah, I'm on TWRP 3.3.0-0
[Treble-Enabled Device Development A/AB ROMS] JuanTamqd21:
Hey uhm, I used to use the december build and the aod and/or ambient display works perfect. But when I used the Jan build, aod and ambient seems broken. I try to open the screen using power button but its only black screen(mind that I can input my pattern, which also vibrates because it is wrong. Is there a fix for this? I don't want to reboot everytime it happens.
[Treble-Enabled Device Development A/AB ROMS] Alvin50:
There's another bug I've found: on TWRP 3.3.3-0, I tried a 12 partitions backup to external SD (128 GB) that, to be exchanged with other units has been formatted in NTFS. When, after backing up, I returned to LOS 18.1, the system claimed my external SD wasn't usable neither for internal nor for exchange use, asking for permission to format it, that I denied. rebooted to TWRP , ext SD was correctly visible. I then made various attempts to let it come back also in LOS, wiping and re-formatting the main partitions, until wiping it all and reinstalling system from scratch. Nope, same LOS behaviour until I erased the backup. A subsequent LOS reinstallation correctly saw the SD again. I presently didn't other experiments, suspecting that someone could warn me about my TWRP version were outdated, and addressing the correct replacement.

I shall also add that, attempting a restore just after backup crashed after the system image restore, throwing off the recovery to infinite reboot.

Kind regards
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with March security patches. [Insert obligatory backup-and-test warning here]
[Treble-Enabled Device Development A/AB ROMS] Reznor7:
Many, many thanks for your continued support!
[Treble-Enabled Device Development A/AB ROMS] hunnia41:
Could we have some without su. I can run PHH, but I cannot use it, since my banking application coughs up on security with Supersu. It works with a cistum rom without it. (I did try to disable Stpersu but it did not help.
[Treble-Enabled Device Development A/AB ROMS] knoelli:
Although I would also very much prefer a build without SU integrated (I need to hide SU for my banking app as well, which works fine in Magisk+MagiskHide but not in PHH-SU), I was able to "unroot" this ROM by deleting the following files (through TWRP) after having flashed the ROM:

/system/bin/phh-su

/system/etc/init/su.rc

After deleting the two files, my banking app does not detect root anymore.
[Treble-Enabled Device Development A/AB ROMS] hunnia41:
Unfortunately I have cubot x20 pro, for which there is no TWRP. If I remember, I tried to to delete through adb but I could not make /system rw, since not system but / was mounted as a device and so I could not delete it with adb.
[Treble-Enabled Device Development A/AB ROMS] eremitein:
are you tried Phh settings > Misc > Securize?
[Treble-Enabled Device Development A/AB ROMS] Kurt Krummbein:
So, you tried to "mount -o rw,remount /system" ??? Why not trying "mount -o rw,remount /" ... or did i get something wrong?

Cheers

Kurt
[Treble-Enabled Device Development A/AB ROMS] hunnia41:
Yes I did. It did not work. I do not remember the exact details why, it was months ago. Right now I am on stock due to the banking application. Just to note, even phh android 11 worked, but for the banking. I tried to decompress, delete the supesu app and recompress the firmware, but it did not boot.
[Treble-Enabled Device Development A/AB ROMS] Kurt Krummbein:
Hm, to get root without having a TWRP (or OrangeFox) i used to install phh-superuser with:

adb install me.phh.superuser_1033.apk

then you should be able to:

su

mount -o rw,remount /system

Maybe the block-device, which holds the system-filesystem might be read-only, then you can check which that device is (check with mount command) and run:

blockdev --setrw /dev/block/dm-X (or whatever ... this is the way it looks with dynamic partitions).
[Treble-Enabled Device Development A/AB ROMS] hunnia41:
I rooted it with magisk. Got the stock boot.img. Patched it with magisk app. and flashed the patched boot.img with fastboot. I will try your suggestion, but I semember that it was read only.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with April security patches. [Insert obligatory backup-and-test warning here]

I no longer have a device on 17.1, but so far disk space still allows for coexistence, so guess I'll just build on until Android S arrives, by which time I'll have to clean 17.1 off my drive.
[Treble-Enabled Device Development A/AB ROMS] roperp:
At the risk of being "that guy" I'm going to ask for some help here. I have successfully flashed this ROM to my Umidigi Bison, and have enjoyed being Google (gapps, etc.) free for a few weeks now. Unfortunately, I've got one bug that persists. I've searched this thread, this forum, and the world wide web, but I need some help clarifying the terms of my search because searching for "phone echo" is useless, understandably.

Specifically, when I try to call anyone via Bluetooth audio output (e.g. connected car, Bluetooth headphones), there is a bad echo. It's almost like the Bluetooth device doesn't filter out my side of the call. Or like the phone mic is also picking up sound at the same time as the Bluetooth device mic is. For clarification, this issue only occurred once I flashed the new rom.

I appreciate all the help, and sorry for any redundancy I present in asking.
[Treble-Enabled Device Development A/AB ROMS] eremitein:
is it same issue https://github.com/phhusson/treble_experimentations/issues/1783 ?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
I haven't checked the other logs yet, but the DownloadProvider log seems to show that you have flashed this GSI on top of something else (i.e. dirty flash), and DownloadProvider can't read its newer version of database?
[Treble-Enabled Device Development A/AB ROMS] dhacke:
Well the logs are from my newest try.

My steps were:

1. Flashed the factory image

2. Booted it once

3. Reboot into fastboot

4. Erase system.img from the stock rom

5. Flashed your GSI.

So in my opinion i made clean flash.

Just one thought: The script which flashes the factory image wiping the userdata; not formatting the userdata.

What do you think? Could that be the cause of my problems?

Seems so.
[Treble-Enabled Device Development A/AB ROMS] eremitein:
if you not wiped userdata after step 5 then it's a dirty flash

you should boot to gsi with a clean data
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Not cleaning out userdata is definitely not clean flash...

The latest factory image for Pixel 4 line is built on top of android-10.0.0_r14 (QD1A.190821.014.C2), while LOS uses a different tag r11 (QP1A.191105.004). From what I can see in AOSP code, r14 has database version 114 and r11 has 113. Booting the factory image once initialized data for every app including a v114 database for DownloadProvider, and LOS can only understand v113 right now. Basically, wipe userdata before booting this.
[Treble-Enabled Device Development A/AB ROMS] dhacke:
Ah ok then i was wrong. I thought wiping is enough.

So i guess i must execute this command after the flash of the factory image:

"fastboot format userdata"

And after that flashing the gsi and boot it.

Correct?

Will the lower database version reduce my security level somehow?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Wiping should be enough, but thing is you didn't even wipe (you booted the factory image once, which generated leftover data).

Usually an increase in app database version means they've implemented something new and requires an accompanying change in database structure (e.g. an additional field). AFAIK this is not related to the monthly security patch.
[Treble-Enabled Device Development A/AB ROMS] dhacke:
Ok thx for all you explanations. So next time before i install your GSI i will make a wipe/format of user data and don't boot the factory image once.

Then the crash should be gone when i'm understanding your explanations right.

I guess i will try it next month.
[Treble-Enabled Device Development A/AB ROMS] I1V1A1N:
On my box ,the X96 Amlogic s905x started up.Only now there are no root rights yet.True here are the messages that the Bluetooth stops.Thanks.
[Treble-Enabled Device Development A/AB ROMS] HueyT:
I always "format data" in TWRP before installing GSI (keeping all my files and image on external SD card so safe from formatting data).

That said, not all GSI work for every GSI compatible devices. This LOS17 works fine for my Moto G7 (river) however.
[Treble-Enabled Device Development A/AB ROMS] reynard1:
Any update?to fix bug like mediaserver?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
You said you have the same problem as dhacke, and I've answered him already (basically, keep your /data clean). If that's not actually your problem, then as usual check whether it's specific to this GSI.
[Treble-Enabled Device Development A/AB ROMS] reynard1:
ok but i do that and everytime clean userdata but still the same

and mediaserver is not the only bug

mypost:

messeges app crash when send sms = in phh work fine

music app not play anything same as gallery = in phh work fine

battery usage not showing anything = same as phh

and i have a qouestion

whats the base of this version on phh?

and phh release v 205 and 206 to fix camera and other stuff

do you have any plan to rebase lineage on it?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Then logs please?

Battery usage requires a device overlay. If nobody has created one for your device, it's up to you.

I update when LOS merges the month's sec patches - I don't necessarily follow PHH's pace.
[Treble-Enabled Device Development A/AB ROMS] killerscope2:
hey guys does it work with a device having arm64 aonly?
[Treble-Enabled Device Development A/AB ROMS] nhicko95:
someone tested this on redmi 6 ?
[Treble-Enabled Device Development A/AB ROMS] icodix:
camera keeps on crashing, cant open. how to fix this?
[Treble-Enabled Device Development A/AB ROMS] eremitein:
try this https://xdaforums.com/showpost.php?p=80944013&postcount=27
[Treble-Enabled Device Development A/AB ROMS] icodix:
thanks mate! will try to fix this later. Thank you so much!
[Treble-Enabled Device Development A/AB ROMS] sn809:
Hi, does lineage 17.0 have dual apps function?
[Treble-Enabled Device Development A/AB ROMS] iamthatakhil:
I'm on a non-GSI LineageOS 16.0 build now on my Samsung Note 8 (Exynos).

Can anyone tell me the steps to flash this GSI onto my phone?

Thankyou!:)
[Treble-Enabled Device Development A/AB ROMS] Reznor7:
Edit: Never mind. Finally got it sorted.
[Treble-Enabled Device Development A/AB ROMS] Vulnerability:
I've been getting some odd random reboots with this latest build, when gaming or doing any heavy tasks it seems to just crash the whole system UI or reboot the device.

I don't recall it happening in earlier builds. I have since flashed the latest A10 HavocOS build from December & I have not had any random reboots during heavy usage. Not sure what's going on!

My setup is pretty basic, latest A only Lineage, no encryption, stock kernel/vendor, no Magisk, no GAPPS or microG.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with May security patches. [Insert obligatory backup-and-test warning here]
[Treble-Enabled Device Development A/AB ROMS] snoopy29:
Going mad here. :)

Need to either remove or replace the built in su (and possibly the busybox_phh) with magisk. On Android 10 the /system can be mounted but changes aren't kept, and while magisk can patch boot.img it then complains about the existing su.
[Treble-Enabled Device Development A/AB ROMS] demoneg:
Anybody else getting malware warning from AVG / Avast? for 6 applications:

I downloaded and flashed a64-bvS and everything works fine, then I installed Gapps and AVG and Avast " both are not running at the same time " and both antivirus gave me malware warning on 6 applications, that included Bluetooth , AudioFX, calendar and other built in and systems application.... anyone else having the same behaviour / issues? or anyone else could test to confirm?
[Treble-Enabled Device Development A/AB ROMS] snoopy29:
I don't see how it won't conflict, the /system partition changes are lost on boot with Android 10. Perhaps it's time to go back to Android 9.

Also the phh-securitise script, it has the same problem - mount /system, makes changes but lost on boot and su reappears in /system/xbin
[Treble-Enabled Device Development A/AB ROMS] snoopy29:
Yes it seems Android 10+ is a disaster for customisation. My device comes with Android 10 preinstalled and I'm wondering how possible it will be to go back to Android 9 (are the partitions going to be different or is flashing system.img enough...
[Treble-Enabled Device Development A/AB ROMS] z1022:
How to decide vndklite or non-vndklite ?

Thanks
[Treble-Enabled Device Development A/AB ROMS] santosst:
VNDK version is device-specific. Use the Treble Info app and see if it shows VNDK Lite in the "Treble and VNDK" Section.

Treble Info - Apps on Google Play

Helps you check Project Treble, A/B and Architecture for GSI installation

play.google.com

However, the VNDK Lite version should work in non-lite vendors, so you can test both and see which works. And if you want to mount the system as R/W, use the VNDK Lite version.

Edit: This last information about mounting as R/W is valid only for Android 11 builds, after v300.j, what is not the scope of this thread. I'm sorry.
[Treble-Enabled Device Development A/AB ROMS] snoopy29:
Where did you get this from?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Note that this info is only useful for Android 11 starting v300.j.
[Treble-Enabled Device Development A/AB ROMS] snoopy29:
So far it has been impossible to mount /system as r/w. I've tried numerous solutions including

https://xdaforums.com/t/tool-win-li...ake-partitions-rw-in-super-partition.4120963/

But 64 bit binaries won't run on the a64-b version of this ROM which I'm thinking is a bug. I'm a bit confused what makes a64-b required, my (MT6761) A53 CPU's are 64 bit, I guess it's a constraint by the device/vendor using 32 bit binaries and needing to retain compatibility?
[Treble-Enabled Device Development A/AB ROMS] santosst:
Thanks for alerting me to the error. I edited the original message to avoid misunderstandings.

Does your device have dynamic partitions? What's the error you are facing when trying to mount /system as R/W?
[Treble-Enabled Device Development A/AB ROMS] snoopy29:
All Android 10 & 11 have dynamic partitions.

Try it and see, any changes disappear after reboot. I don't see how VNDK Lite makes any difference.
[Treble-Enabled Device Development A/AB ROMS] santosst:
Hmmm, you can do changes but they disappear, so it's not a mounting problem. Are you using Magisk?
[Treble-Enabled Device Development A/AB ROMS] snoopy29:
No to magisk. phh-su. The only reason to mount is to try and get rid of su :)

PHH said...

"Issue is either some Mediatek protection of super partition (in which case, only work around, so far, is to flash from recovery), or magisk"

I don't believe Mediatek could even accomplish such a protection and there's nothing anywhere to suggest it. For it to do what it is the partition must be loaded into memory and either allocated blocks are restricted from rewrite or all changes go into RAM.
[Treble-Enabled Device Development A/AB ROMS] snoopy29:
I'm beginning to build these without su. Here's the a64 version. I'll build others if requested.

For me on my particular phone this is the only way to run a banking app. Magisk can be installed and being there's no built in su it won't conflict. I know very little about Android dev and this is always going to be based on AndyYan's work.

lineage-17.1-20210608-UNOFFICIAL-treble_a64_bvN.img.xz
[Treble-Enabled Device Development A/AB ROMS] santosst:
Oh, I see. I didn't know about this issue with Mediatek, that's boring!

Anyway, thanks for building a new version without su and sharing here! Since your biggest problem is with inbuilt root, you can also try to mount current build as RW in your computer, remove su and add secure file (I'm supposing you are running Linux since you built a GSI lol)
[Treble-Enabled Device Development A/AB ROMS] snoopy29:
That was the first thing I tried mate. su returns as does every other file. :)

Happily I have a solution. Also can report battery life is excellent on a Cubot King Kong Mini 2. Over a 5hr cycle ride battery life using a little GPS now and then, I lost 3%.
[Treble-Enabled Device Development A/AB ROMS] santosst:
Oh, what spectacular battery performance! LOS 17.1 is really great in the battery life.

I only don't understand why the modifications you did outside your phone are reverted when you flash the modified system image. In general, I do some mods using bash scripts to add an overlay, remove extra libs, etc, and you also should be able to do it (since the mods in the system aren't done in the device).
[Treble-Enabled Device Development A/AB ROMS] snoopy29:
Android 10+ uses a super partition and modifications to /system aren't kept upon reboot. This is the problem. Neither Phh or AndyYan can understand why it's happening as they say their images (<phh v600) are built with the ext4 flag which is responsible for this, so it seems something else in a phone like the bootloader or super can also override the partition settings /system was compiled with.

I can flash modified system image (i.e with magisk) but it conflicts with the built in su, hence the need to rebuild this ROM without it.
[Treble-Enabled Device Development A/AB ROMS] santosst:
Yes, I know about this limitation when editing the system partition in the device, but I didn't imagine that editions in the system image outside the device don't appear when you flash an edited image.

I really thought that a simple bash script like the attached one could remove root. It mounts the system image in Linux and remove all the files related to the inbuilt su. However, if it's not possible and since you have a proper solution (although it's a bit tiring lol), let it be :)
[Treble-Enabled Device Development A/AB ROMS] bomzhellino:
@AndyYan thank you for June update! )
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with June security patches. [Insert obligatory backup-and-test warning here]
[Treble-Enabled Device Development A/AB ROMS] flying_tree:
I installed this ROM (version 17.1-20210512) using Fastboot commands on a Xiaomi Redmi Go. Everything is fine, it is a really good job, except for an important issue : if I receive an SMS, when I will try to send another SMS I do not more access to any network provided by my SIM card until reboot. And multiple attempts are often needed to complete boot.

Sorry for the English, I am French. Also, should I post somewhere else ?

Edit : I saw the phh setting "Automatically restart RIL", tried it, rebooted, but no signal at all so I disabled this setting.
[Treble-Enabled Device Development A/AB ROMS] ZorEl212:
I have 3 big problems

1. No in call voice. I can't hear anything while in call and nothing on the other end as well.

2. No Audio in Bluetooth devices. Whenever I connect a Bluetooth device music players start to malfunction and I can't hear anything on Bluetooth devices. I tried many players but no luck.

3. Rooting problem. I did a clean flash and Los booted successfully. I mean the above 2 bugs are still exist, other than that, FINE. But when I flash magisk (phh version) and reboot, I get bootloop in the kernel. I.e restarts continuously on Samsung logo.

I used arm_a only vS. Is it conflicting with built-in su? if so, anyone can Tell me how to activate the built-in su? since it is missing in developer options.

Please help????🙏🙏🙏
[Treble-Enabled Device Development A/AB ROMS] flying_tree:
About the built-in su, I just installed the Superuser app (a su manager) and it provides su properly.
[Treble-Enabled Device Development A/AB ROMS] ZorEl212:
Which one? I tried SuperSU it says binary occupied.
[Treble-Enabled Device Development A/AB ROMS] eremitein:
you need SuperUser apk
[Treble-Enabled Device Development A/AB ROMS] ZorEl212:
I have installed it already and when I open the app I get "Binary occupied!" Error
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
SuperSU ≠ Superuser.

Superuser | F-Droid - Free and Open Source Android App Repository

Manage root access

f-droid.org

This is only documented in the 18.x thread, so you're not to be blamed here.
[Treble-Enabled Device Development A/AB ROMS] ZorEl212:
Oh, I got it. Good to go now.

If there is a way to fix magisk please let me know.
[Treble-Enabled Device Development A/AB ROMS] MrHomebrew:
You know the easiest way to deal with safetynet with this GSI is to go in to phh settings. Go to misc and click on securize. Phone, tablet or whatever device you have will reboot and you should pass safetynet without the need for magiskhide.

Remember phh settings, misc and then select securize.

If safetynet does not pass after this then install magiskhide, but again I do securize and boom su crap is removed and magisk runs fine passing safetynet.

OP should include this valuable information.