• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[GSI][11] LineageOS 18.x GSI (all archs)

Should I build *B with EXT4 share duplicate blocks?

  • Yes - my /system is small, I need every bit of space saving to make it fit

    Votes: 14 51.9%
  • No - I'm not short on space, and/or I prefer mountable /system

    Votes: 13 48.1%

  • Total voters
    27
  • Poll closed .
Search This thread

marcusah123

Senior Member
Sep 27, 2009
121
20
That's an older device that probably didn't ship forceencrypt, this is one exception LOS left open for legacy devices.
I tried the flashable zip that "disables" forceencrypt but it didn't work it messed everything up. I suppose I should just be ok with losing all my data when my phone goes crazy, even with backups. Having good backups is key, but none of the backup programs get all the data so when I move from an old device to a new one sometimes I want to pull the data when they are not booted for various reasons due to issues. Anyhow I think that's a minor issue. I'd be happy with just fixing the gapps and the hardware overlay issues.
 
D

Deleted member 11799823

Guest
Hi, I have tested the August build (arm64 AB), the non-vndklite version has 30MB of free space in /system, perfect for using adaway but it is not rw, and the vndklite version only has 3MB of free space. Is there a way to have the same free space in the vndklite version to take advantage of it in programs like Adaway?

And... Sorrry for my bad english.
 

bomzhellino

Member
Nov 2, 2019
46
24
Hi, I have tested the August build (arm64 AB), the non-vndklite version has 30MB of free space in /system, perfect for using adaway but it is not rw, and the vndklite version only has 3MB of free space. Is there a way to have the same free space in the vndklite version to take advantage of it in programs like Adaway?

And... Sorrry for my bad english.
Try to repair and resize the System partition on twrp.
 

AndyYan

Recognized Contributor
Jan 30, 2012
4,308
3,592
Beijing
Updated all variants with September security patches and in sync with PHH v312. [Insert obligatory backup-and-test warning here]

One notable change of this month is removing llkd (livelock daemon), which is known to mistakenly cause certain apps like Genshin Impact to freeze/restart after 10 minutes of usage. I've been running alright without llkd for a month by now, but if you notice a regression after this build, do let know.

PHH is currently on a vacation; luckily, A11 is nearing its end, and A12 has been pushed back to Oct 4th (current leak), so there's no need to worry. I've also finished scouting A12 ahead for my personal changes and should be ready to publish them for other builders' reference, and build for generic target on release day.
 

flix27

New member
Feb 11, 2021
1
0
I tried to install this gsi on my ZTE blade a7 2020 with twrp (by first factory resetting and then flashing the .img file as sytem image) file but it doesn't Work:

The device has a 64Bit CPU but 32 Bit OS and is project Treble supported (it shows a dedicated vendor partition in twrp)

When I use ARM with b partitioning scheme it reboots and just goes back into recovery.

All other versions just bootloop.

Is there anything i'm doing wrong?
 

knoelli

Member
Jul 26, 2020
7
1
Hamburg
I like to add (nano open) GApps to the rom and also prefer Magisk over phh-su, so I was looking for a way to make the system image writeable again. Some posts above a guide from PHH was given to unshare duplicate blocks directly on the phone once the image has been flashed, but I wanted to perform these steps before flashing the image.

I came up with the following method to unshare duplicate blocks on a linux machine. Note that you need "simg2img" and "img2simg" to convert from and to sparse image file. Those tools should be available on most current linux distributions (i.e. on debian/ubuntu you can install them with a simple "sudo apt-get install simg2img img2simg").

Here's are the commands to unshare duplicate blocks. Replace ##FILENAME## in the first line with the actual name of the downloaded .xz-image file:
xz -d -k -c ##FILENAME## > ROM.img simg2img ROM.img ROM_RAW.img e2fsck -y -f ROM_RAW.img resize2fs ROM_RAW.img 3500M e2fsck -E unshare_blocks -y -f ROM_RAW.img e2fsck -f -y ROM_RAW.img resize2fs -M ROM_RAW.img img2simg ROM_RAW.img Lineage_RW.img

If you want, like me, to remove phh-su in the process, use the following commands just after the "e2fsck -E unshare_blocks..." command:
mkdir tmpdir mount -o loop,rw ROM_RAW.img tmpdir rm tmpdir/system/bin/phh-su rm tmpdir/system/etc/init/su.rc umount tmpdir

The final image is then stored as Lineage_RW.img which can be flashed to the phone instead of the originally downloaded image.
 
  • Like
Reactions: Kurt Krummbein

Chaplin0906

Member
Sep 10, 2021
16
0
Hey guys,I use this gsi on my htc u11 for daily use,but when I call someone ,
I can’t hear his voice with the earpiece but the speaker , how can I fix it ?
 

LichtEstarossx

Senior Member
Nov 23, 2017
64
19
Updated all variants with September security patches and in sync with PHH v312. [Insert obligatory backup-and-test warning here]

One notable change of this month is removing llkd (livelock daemon), which is known to mistakenly cause certain apps like Genshin Impact to freeze/restart after 10 minutes of usage. I've been running alright without llkd for a month by now, but if you notice a regression after this build, do let know.

PHH is currently on a vacation; luckily, A11 is nearing its end, and A12 has been pushed back to Oct 4th (current leak), so there's no need to worry. I've also finished scouting A12 ahead for my personal changes and should be ready to publish them for other builders' reference, and build for generic target on release day.

Updated all variants with September security patches and in sync with PHH v312. [Insert obligatory backup-and-test warning here]

One notable change of this month is removing llkd (livelock daemon), which is known to mistakenly cause certain apps like Genshin Impact to freeze/restart after 10 minutes of usage. I've been running alright without llkd for a month by now, but if you notice a regression after this build, do let know.

PHH is currently on a vacation; luckily, A11 is nearing its end, and A12 has been pushed back to Oct 4th (current leak), so there's no need to worry. I've also finished scouting A12 ahead for my personal changes and should be ready to publish them for other builders' reference, and build for generic target on release day.
I have tried both methods in phh aosp, update the webview, but my galaxy a51 does not support or something similar the "setprop ctl.stop lkd"
A "temporary" solution in my case is to put the kernel in permissive when I use the applications that have crashes, once I finish using them I make the kernel is enforcing again, I do it from termux with these commands
its
getenforce to confirm selinux status
setenforce to change the state of it (1 for enforcing) (0 for permissive)
At the moment it is just a speculation of mine, but maybe it could be useful for someone else
 

AndyYan

Recognized Contributor
Jan 30, 2012
4,308
3,592
Beijing
I have tried both methods in phh aosp, update the webview, but my galaxy a51 does not support or something similar the "setprop ctl.stop lkd"
A "temporary" solution in my case is to put the kernel in permissive when I use the applications that have crashes, once I finish using them I make the kernel is enforcing again, I do it from termux with these commands
its
getenforce to confirm selinux status
setenforce to change the state of it (1 for enforcing) (0 for permissive)
At the moment it is just a speculation of mine, but maybe it could be useful for someone else
Code:
su
setprop ctl.stop llkd-0
setprop ctl.stop llkd-1
 

Top Liked Posts

  • There are no posts matching your filters.
  • 8
    AOSP Android 12 source has dropped just now, and unlike previous years, this time I'm joining the day-1 fun in my way.
    I've already (re-)done most of my frameworks_base personal mods and, as a demo, applied them on top of an aosp_arm64 build, which you can download here. It's also RW-enabled so you can poke around it further. The modifications themselves are open-sourced here, some of which could be of use to custom ROM makers.
    Note that, booting- and feature-wise, this would be no different from Google's aosp_arm64 build, so if you're looking for a daily driver, this isn't it.

    EDIT: Emphasize that this build is merely an appetizer/demo - it won't get support or updates.
    4
    Updated all variants with October security patches. Note that there's no impactful change in v313. [Insert obligatory backup-and-test warning here]

    As with last year, I'll continue to build 18.x until some time later when disk space becomes an issue, likely a month or two before Android T.

    PHH is making steady progress on S, but no ETAs.
    2
    Hi,

    Is it working for Essential Ph-1 ? if someone did it, please share tour experience
    Thanks in advance
    i tried it, but it boots in to fastboot on my device. Tried google pixels beta 5 for gsi , does the same.
    2
    AOSP Android 12 source has dropped just now, and unlike previous years, this time I'm joining the day-1 fun in my way.
    I've already (re-)done most of my frameworks_base personal mods and, as a demo, applied them on top of an aosp_arm64 build, which you can download here. It's also RW-enabled so you can poke around it further. The modifications themselves are open-sourced here, some of which could be of use to custom ROM makers.
    Note that, booting- and feature-wise, this would be no different from Google's aosp_arm64 build, so if you're looking for a daily driver, this isn't it.

    Hi, unfortunately I wasn't able to boot after install. I tried a few times and even by using the TWRP option reboot to system.

    Samsung A20e.
    1
    I like to add (nano open) GApps to the rom and also prefer Magisk over phh-su, so I was looking for a way to make the system image writeable again. Some posts above a guide from PHH was given to unshare duplicate blocks directly on the phone once the image has been flashed, but I wanted to perform these steps before flashing the image.

    I came up with the following method to unshare duplicate blocks on a linux machine. Note that you need "simg2img" and "img2simg" to convert from and to sparse image file. Those tools should be available on most current linux distributions (i.e. on debian/ubuntu you can install them with a simple "sudo apt-get install simg2img img2simg").

    Here's are the commands to unshare duplicate blocks. Replace ##FILENAME## in the first line with the actual name of the downloaded .xz-image file:
    xz -d -k -c ##FILENAME## > ROM.img simg2img ROM.img ROM_RAW.img e2fsck -y -f ROM_RAW.img resize2fs ROM_RAW.img 3500M e2fsck -E unshare_blocks -y -f ROM_RAW.img e2fsck -f -y ROM_RAW.img resize2fs -M ROM_RAW.img img2simg ROM_RAW.img Lineage_RW.img

    If you want, like me, to remove phh-su in the process, use the following commands just after the "e2fsck -E unshare_blocks..." command:
    mkdir tmpdir mount -o loop,rw ROM_RAW.img tmpdir rm tmpdir/system/bin/phh-su rm tmpdir/system/etc/init/su.rc umount tmpdir

    The final image is then stored as Lineage_RW.img which can be flashed to the phone instead of the originally downloaded image.
  • 38
    640px-Lineage_OS_Logo.png


    Background:
    This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019.
    LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
    All the source code for LineageOS is available in the LineageOS GitHub repo. And if you would like to contribute to LineageOS, please visit Gerrit Code Review.

    Disclaimer:
    This is still mostly a LineageOS team / PHH @phhusson effort, credits to them and all associated for making all this possible.
    No flashing instructions will be offered. If you're here in this forum, you should know what you're doing.
    No guarantees that everything would work. This is a GSI, bugs are bound to happen.

    Download:
    https://sourceforge.net/projects/andyyan-gsi/files/
    Compressed as .xz archives - extract first.
    Vanilla except for these changes:
    • Modifications needed to make it build/boot/feature-complete
    • Revived navbar layout tuning via sysui_nav_bar tunable
    • Disabled "vendor mismatch" warning on boot
    • Signature spoofing support from MicroG
    • Default stretch-to-fullscreen (force apps to render in longer than 16:9)

    Stuff on GitHub (builders-only):
    Since builders' stuff aren't really interesting to end users, I decided not to separately document the modifications needed in this post; instead just check out the scripts/patches, where most things should be self-explanatory: lineage_build_unified, lineage_patches_unified (where patches_treble_phh contains PHH's treble_patches adjusted for LOS). Not the cleanest code, but should help if you need some clues.

    Donate?
    https://paypal.me/AndyCGYan
    16
    Reserved

    Couple of things to note:
    • I now have a rather taxing day job, and can't devote nearly as much time/effort into this as I did as a student.
    • As always, you are strongly advised to try PHH's AOSP first and identify/report issues there, before moving onto other GSIs that are based on his work. Please report bugs here only if it's specific to this GSI.
    • Thanks to patches from @eremitein , Magisk compatibility is partially restored. For devices that still don't play well with it (e.g. kernel restrictions implemented by OEM), use PHH-SU instead. Install the app and you'll get root for apps.
    • A-only and VNDKLite targets are now generated from AB images instead of built from source, see sas-creator. Kinda hacky and might be buggy. Move on to an AB device if you can.
    • To mount /system RW on AB devices, refer to this.
    • exfat SD cards still don't seem to work. Any help related to this would be appreciated.
    9
    March patch is ready, but due to lack of time, I'll have to postpone this month's update for a while. I worked on it yesterday but couldn't figure out a core problem in time.
    9
    Updated all variants with March security patches and in sync with PHH v302. [Insert obligatory backup-and-test warning here]

    Two years of GSIs. Life is trying to rob me of this "hobby" - I'll keep this going as long as I can handle it.
    8
    Initial builds are based on PHH v300.j and December security patches.
    Building-related bits have been published, but only for AB targets - I'm not sure if I want to integrate sas-creator yet.