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

[gregeerg]

At least you have ADB. While bootlooping, try:

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:

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.

 

[gregeerg]

At least you have ADB. While bootlooping, try:

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:

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

 

[AndyYan]

@gregeerg 's bootloop had been narrowed down to the rogue QCOM LogKit app plus a dirty /data. However, as @keymanhattan 's device is Exynos-based, I suppose this reason doesn't apply to everyone. @Mohinesh @keymanhattan - as the last mentioned message said, waiting on your info.

 

[keymanhattan]

@gregeerg 's bootloop had been narrowed down to the rogue QCOM LogKit app plus a dirty /data. However, as @keymanhattan 's device is Exynos-based, I suppose this reason doesn't apply to everyone. @Mohinesh @keymanhattan - as the last mentioned message said, waiting on your info.

@AndyYan thank you for this GSI project. In my case bootloop is at LOS logo. Clean wipe. Do you think exynos-based devices are not compatible with GSI ? thx

 

[AndyYan]

@AndyYan thank you for this GSI project. In my case bootloop is at LOS logo. Clean wipe. Do you think exynos-based devices are not compatible with GSI ? thx

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

 

[gregeerg]

@AndyYan thank you for this GSI project. In my case bootloop is at LOS logo. Clean wipe. Do you think exynos-based devices are not compatible with GSI ? thx

Waiting on you, @keymanhattan. Should be refreshing this site every min to see notifications

Am getting bootloop in The lastest version...idk if its only me...can anyone confirm?

You too, @Mohinesh

 

[gregeerg]

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.

 

[jfudisj_17639]

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.

 

[Crrrr]

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]

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

[ 0.000000] [0: swapper: 0] charging_night_mode : 0x0(0)[ 0.0 - Pastebin.com

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

pastebin.com

 

[tosiaczus]

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]

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

[ 0.000000] [0: swapper: 0] charging_night_mode : 0x0(0)[ 0.0 - Pastebin.com

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

pastebin.com

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.

 

[Incomtus]

.

 

[Nowty_Nethshan]

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]

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.

 

[DarkEvinho]

how to instal Gaaps on LOS bvS.img , dont works for me (partition size small error in twrp)

 

[x53]

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.

 

[HProt]

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]

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

 

[AndyYan]

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.