[DISCONTINUED][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

gregeerg

Senior Member
May 12, 2022
106
14
At least you have ADB. While bootlooping, try:
Code:
adb shell
su
pm disable com.qualcomm.qti.logkit.lite
reboot
And see if it goes further. If not, more logs, it might get stuck on some other apps.

I've added some more needed info on the above post, please go through and let me know what you missed too.

Also, I've tried reproducing on my side using a copy of the app I found in FairPhone 3. Unfortunately I can only semi-reproduce it - it does spew out a similar error on directly installing the APK:
Code:
INSTALL_FAILED_SHARED_USER_INCOMPATIBLE: Reconciliation failed...: Reconcile failed: Package com.qualcomm.qti.logkit.lite has no signatures that match those in shared user android.uid.system; ignoring!
...but when embedded into vendor, it doesn't cause a bootloop and seems to just get ignored silently with no mentions of it.
EDIT: been narrowed down to the rogue QCOM LogKit app plus a dirty /data. Thanks, Andy.

Ok, will try. Will that effect regular texting/calling at all because I do need those. Mine just sits at the LOS boot logo where the circle goes across the line thing and just does that repeatedly. Happens with 18.1 May patch and March patch and happened on LOS17 too. Haven't had any releases work for me yet since this is my first time trying to install LOS.
 
Last edited:

gregeerg

Senior Member
May 12, 2022
106
14
At least you have ADB. While bootlooping, try:
Code:
adb shell
su
pm disable com.qualcomm.qti.logkit.lite
reboot
And see if it goes further. If not, more logs, it might get stuck on some other apps.

I've added some more needed info on the above post, please go through and let me know what you missed too.

Also, I've tried reproducing on my side using a copy of the app I found in FairPhone 3. Unfortunately I can only semi-reproduce it - it does spew out a similar error on directly installing the APK:
Code:
INSTALL_FAILED_SHARED_USER_INCOMPATIBLE: Reconciliation failed...: Reconcile failed: Package com.qualcomm.qti.logkit.lite has no signatures that match those in shared user android.uid.system; ignoring!
...but when embedded into vendor, it doesn't cause a bootloop and seems to just get ignored silently with no mentions of it.
EDIT2: been narrowed down to the rogue QCOM LogKit app plus a dirty /data. Thanks, Andy.

phhgsi_a64_ab:/ # pm disable com.qualcomm.qti.logkit.lite
cmd: Can't find service: package

EDIT: just realized I double replied, whoops
 
Last edited:

keymanhattan

Senior Member
Dec 23, 2012
168
32

gregeerg

Senior Member
May 12, 2022
106
14

gregeerg

Senior Member
May 12, 2022
106
14
Possible LOS bug? So, with SeedVault, the issue I've been having is each thing listed says, "waiting to back up..." and gets stuck on that for forever. *BUT* I just noticed....when I tap the Back Up button, it IS actually making the backup folder on my SD card as well as filling the folders with the backup information, but on the device, it'll always just keep saying, "waiting to back up..." Basically, it does actually back up but the "waiting to back up" never changes and appears to not be backed up when it is.
 
Last edited:

jfudisj_17639

Member
Jun 2, 2022
9
0
Hi, so I installed this GSI on my SM-A125F and I have a problem: when I boot the phone it works perfectly, but when i lock the screen or it goes black, the touch doesn't work anymore until I reboot the system and the same again.
Can anyone help me please? Thank you.
 
Last edited:

Crrrr

Senior Member
It's not that clear cut. Go back to that post and post all info as required there.

In general (not only for this update) I get a bootloop at the LOS logo after recharging my Samsung A20e from zero battery. However, I discovered that if I simply log to TWRP and from there I select reboot to system I get a normal boot. Maybe this could do the trick in this case as well ...?
 

tosiaczus

Member
Nov 5, 2010
22
6
Samsung A51 sm-a515f
Version below works fine
lineage-18.1-20211108-UNOFFICIAL-treble_arm64_bvS-vndklite

Version:
lineage-18.1-20220511-UNOFFICIAL-arm64_bvS-vndklite
cause bootloop

After Samsung's boot logo there is black screen for few seconds and reboot.
There is logfile in the attachment. console-ramoops-0

 
Last edited:

tosiaczus

Member
Nov 5, 2010
22
6
In general (not only for this update) I get a bootloop at the LOS logo after recharging my Samsung A20e from zero battery. However, I discovered that if I simply log to TWRP and from there I select reboot to system I get a normal boot. Maybe this could do the trick in this case as well ...?
In that case I am disoonnecting the usb and then restart phone pressing vol- + power and then connect usb again.
 

AndyYan

Recognized Contributor
Jan 30, 2012
4,481
3,835
Beijing
Samsung A51 sm-a515f
Version below works fine
lineage-18.1-20211108-UNOFFICIAL-treble_arm64_bvS-vndklite

Version:
lineage-18.1-20220511-UNOFFICIAL-arm64_bvS-vndklite
cause bootloop

After Samsung's boot logo there is black screen for few seconds and reboot.
There is logfile in the attachment. console-ramoops-0

Checked the log, unfortunately it seems too early a failure and beyond my skills.
At this moment I can only suggest 1) trying a newer (but still R) stock base, and 2) trying LOS 19.x instead.
 
Apr 20, 2020
5
0
i managed to get bluetooth media working by enabling "Force-disable A2DP offload" and bluetooth workarounds to "MediaTek" as my phone is a galaxy A10s, but the audio seems to randonly cut off and comeback and also the bluetooth range is VERY VERY poor. cant walk like 2 feet away from bluetooth device , audio stops playing. Thanks in advance for any help! Also im using the vndklite version.
 

AndyYan

Recognized Contributor
Jan 30, 2012
4,481
3,835
Beijing
Updated all variants with June security patches. [Insert obligatory backup-and-test warning here]

Next month's will supposedly be the final 18.1 build, after which I'll need to make room for The nexT big Thing.
 

x53

Senior Member
May 8, 2013
123
90
Little side note: I've dirty flashed lineage-18.1-20220511-UNOFFICIAL-a64_bvS.img.xz over lineage-18.1-20220315-UNOFFICIAL-a64_bvS.img.xz and have had problems with two apps. Those apps (OsmAnd and Transistor) didn't work anymore. They had forgotten all settings like factory settings. Even worse they won't accept new data. Bottom line all resettings didn't help. I had to reinstall both apps. However, I don't see a difference between reinstalling apps or removing app data and cache. But in my case there was a difference. Osmand has had a second big problem. With ROM 20220315 I had located all my maps and data on external sd (folder: /storage/xxxx-xxxx/Android/data/net.osmand.plus/files). This place doesn't work anymore using the new rom. Since rom upgrade Osmand has no rights to read/write this folder, created by it's own?!? Since that new rom I have to place all osmand data in /storage/xxxx-xxxxx/download/net.osmand.plus/files. I know about the access problems using Android 10/11. But in my case I was using Android 11 the whole time and I did only a small upgrade. Bottom line, I never would have guessed so much problems and work with this small upgrade. Has anyone noticed similar problems e.g. with other apps? I've some other older apps installed. They showed no such problems.
 
  • Like
Reactions: ROO3VER

HProt

Member
Nov 30, 2013
16
4
Hi, tell me what's wrong. If i used GSI from Google and charging with the device turned off it work fine. When i use GSI Lineage OS and charging with the device turned off, tablet show logo and does not load, generally freezes and does not turn off even if the wire is pulled out.

I see that in the GSI Lineage OS in /system/init/hw/hw/init.rc the gsicharger service is spelled out and in /system/etc/init/hw/init.rc at the bot charger. Maybe this is the matter? But there are no lines in boot.img

on charger
class_start charger

on property:sys.boot_from_charger_mode=1
class_stop charger
trigger late-init

I tried to add with my hands

on charger
class_start gsicharger

on property:sys.boot_from_charger_mode=1
class_stop gsicharger
trigger late-init

Does not work.
 

Sheepmister

Member
May 22, 2020
41
4
Samsung Galaxy A12
Hi, so I installed this GSI on my SM-A125F and I have a problem: when I boot the phone it works perfectly, but when i lock the screen or it goes black, the touch doesn't work anymore until I reboot the system and the same again.
Can anyone help me please? Thank you.
Flash Rainbow kernel it fixed the touch issue,search in samsung galaxy a12 thread
 
Last edited:

AndyYan

Recognized Contributor
Jan 30, 2012
4,481
3,835
Beijing
Updated all variants with July security patches. [Insert obligatory backup-and-test warning here]

The nexT big Thing is around the corner, so in preparation I'll clear 18.x off my drive in a week. This will be the final batch of 18.x builds from me.

As a farewell gift of sorts, I present to you GAPPS variants - regular for A64/64, and Go for 32/A64, matching the combo from PHH's AOSP. Compound that with A-only and VNDKLite, and we get a whopping 16 variants and close to 200GB of disk space eaten up by build artifacts (see why I didn't make them earlier?).
I myself have minimally tested regular GAPPS by logging in and downloading an app from Play, while another user had daily driven it for a few days with no issues reported; Go GAPPS is entirely untested. Regardless, GAPPS will be treated with the same principle as 19.x - builds are offered as-is without guarantees, and you'll have to help each other out on GAPPS-related/-induced issues.
To deal with the Play Protect certification error, visit here.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Updated all variants with July security patches. [Insert obligatory backup-and-test warning here]

    The nexT big Thing is around the corner, so in preparation I'll clear 18.x off my drive in a week. This will be the final batch of 18.x builds from me.

    As a farewell gift of sorts, I present to you GAPPS variants - regular for A64/64, and Go for 32/A64, matching the combo from PHH's AOSP. Compound that with A-only and VNDKLite, and we get a whopping 16 variants and close to 200GB of disk space eaten up by build artifacts (see why I didn't make them earlier?).
    I myself have minimally tested regular GAPPS by logging in and downloading an app from Play, while another user had daily driven it for a few days with no issues reported; Go GAPPS is entirely untested. Regardless, GAPPS will be treated with the same principle as 19.x - builds are offered as-is without guarantees, and you'll have to help each other out on GAPPS-related/-induced issues.
    To deal with the Play Protect certification error, visit here.
  • 50
    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
    20
    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
    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.
    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.