yashsingh1/xdaforums huggingface dataset:
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Rrreutel:
@derf elot Not sure where to post issues, I'll try here first:

I built a custom LOS20 build for Lilac today, based on current (as of nov 8) state of whatawurst and lineageos repo's, and while it builds, Bluetooth seems to crash (when turning BT on via quick tile, or when trying to pair a new device (no devices show up in the list of available devices, a crash of the bt app instead). Logcat fragment here.

I did another build without two BT related commits (1, 2) from yoshino-common repo (reverted them), but BT still crashes. Not sure where to look, it seems a selinux_android_setcontext call fails.

I found only one reference to a similar issue, without context, apparently from a logcat of raven device (Google Pixel 6 plus).

ROM is plain, no other patches, no gapps, no magisk etc. I built a signed build, with keys generated by the build script (including 'bluetooth' key).

On your LOS20 1.0 build BT works OK.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] derf elot:
Hello,

I am assuming, you are signing the build with your own keys? In that case, you shouldn't use your own for bluetooth, otherwise they won't match the ones used for the BT module. The way I am doing it is to use the bluetooth keys from build/target/product/security/ to sign, instead of my own.

Hope that helps.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Rrreutel:
Yes, that worked, bluetooth is working now!

I wonder if this would apply to other key(s) such as sdk_sandbox as well (using the LOS key instead of own key). At least I'll know where to look if I see something similar, thanks!
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] derpster:
Hey,

encountered the following issues with this, which may or may not a me problem.

The linked TWRP would not work but freeze at the splash screen, requiring ADB commands to get the phone to react to anything again. Used the newest instead.

Once flashed my unit's network capabilities go crazy and won't function. This applies to WLAN, mobile carrier network and location.

All of them constantly drop in second intervals and appear to reinitilize themselves endlessly, without ever getting anywhere.

These log entries loop endlessy and the phone may become sluggish and unresponsive eventually

xxx = Always the same value for the respective variable.

SPN is empty and occasionally shows "Willkommen", which translates to "Welcome"

The Fs may be more than I put here. Assuming this is a hex print just assume as many Fs as can be had without overflowing.

The hardware, by principal, is functional, as the stock ROM behaves as expected.

No idea whether that is my fault, my unit's, has something do with the ROM or my installation process. Tried everything that seemed reasonable to me but nothing would work and effectively render this ROM unusable for me, unfortunately.

Cheers.

EDIT: I'm not a mobile dev, so take this with a grain of salt. The log suggests that an event winds up on a bus, is being reacted on insufficiently due to reasons and then rethrown on the bus, repeating the process endlessly.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] android666:
hello. is possible to add ext4 support for external SD ? Twrp support it but v20 looks to me that no :-(. it works with v19 (in case, someone would like to use ext4 for external SD (like my 512GB): link )

thanks
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] TheArt.:
Is this a dirty flash? I have the 19.1 so don't know how to dirty flash properly
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Tim700_0:
Sorry to ask again, but does that mean that there's no fully working solution for installing Lineage 20.0 with microG up to this point?

I am very happy with 19 but would like to test.

Than. you in advance for a tip.

microG
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Rrreutel:
Several Pull Requests for enabling microG builds of LOS20 are waiting to be merged at the lineageos4microg repo's, after that it will be more straightforward to build this ROM in combination with microG. I've been testing a personal LOS20+microg build for over a week, haven't had issues with it yet so far.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] RKirpest:
Nice rom. But I will have to flash a different one.

Problems:

My phone keeps disconnecting of the phone network every few seconds. (KPN Netherlands network).

I tried switching to 3G, Disabling IMS, and manually selecting the profile with modem switcher. It all did not help.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] petefoth:
I have finally managed to create Unofficial and Custom builds based on this ROM. AndroidFileHost is still unwell, so the ROMs can be downloaded from Jaguar (links will expire in 180 days (2023-05-27) -

Unofficial https://share.jaguar-network.com/dba26051-29c9-41d5-a4e6-02a746b47c85

Custom https://share.jaguar-network.com/2403f484-3b2a-4191-abf6-4cdf6114ad27

Many thanks to the people here and in the `lineageos4microg/docker-lineage-cicd` repo who have provided invaluable help.

I have successfully dirty flashed the Custom build on my daily driver, and clean flashed both versions on a test device.. They both seem to work OK, and I haven't bumped into any major problems.

Have fun, good luck, and please feel free to provide feedback here, or raise issues in my Codeberg repo .

An outline of the necessary steps in this post in my Codeberg project issue Please feel free to PM me if you would like more information
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] petefoth:
See the previous post: an unofficial LOS for Microg 20 ROMs is now available for download and testing. It's been running on my 'daily driver` device for at least 5 hours now, and nothing has broken yet ;)

Have fun, and good luck!
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Arcline:
Hey thanks a lot for you great work, as always!

By dirty flash do you mean dirty flash over your Los 19.1 MicroG builds?
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] petefoth:
Yes. I flashed the new LOS 20 CUSTOM-PLUS-E ROM over the LOS 19.1 version, and everything seemed to carry on as normal when I rebooted :)

Which is handy because, when I was testing on my test device, I wasn't able to make a restorable TWRP backup of my 19.1 data. I did have an up-to-date ABRT backup, but I didn't need it
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Arcline:
I just installed it, everything works great, if not better! Battery life seems better too. Overall a nice refinement of android 12. Im curious how this will develop.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Arcline:
I encountered a problem, but I think it's connected to the Los 20 build itself, not the MicroG variant. When you open the files app and select the Sd card it shows only "No files", but 3rd party file managers work fine. Anyone encounter that issue?

Edit: I found the problem. A magisk module called "NoStorageRestrict". Just update it to the latest version.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] petefoth:
And they're now on AndroidFileHost too

Unofficial https://www.androidfilehost.com/?fid=14871746926876849129

Custom https://www.androidfilehost.com/?fid=14871746926876849128
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Tim700_0:
I dirty-flashed your LOS 20 builds peteforth but encountered the same problem with connectivity on my german telekom network that some others mentioned before:

-disconnecting phone calls and no mobile internet connection possible. All the tips of setting new APNs switching back to 3G connectivity etc did not help at all.

The ROM simply seems to kill any connection to the network every few seconds.

I have stayed on the older LOS 19.1 version before and never had any issues.

Have i missed a fix for that problem or is there a way to downgrade to it again without having to wipe all my data and the phone completely?

I tried both versions, the LOS 20.0 4microG UNOFFICIAL and the PLUS-E CUSTOM one.

Thanks in advance for any tips.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] petefoth:
I assume the others you mention were having problems on the non-MicroG built by @No1Alien (as I have only just published my MicroG builds). Have you tried with that build?

EDIT: Are your problems similar to those reported in this post?

I have not come across any of these problems in either my builds or @No1Alien's. They may be specific to your network operator, and I can only suggest trying whatever fixes have been mentioned in response to the earlier comments.

You could try 'dirty flashing` the old version. It's not something I've tried but it **might** work. Alternatively, if you have access to a Linux computer - real or VM - then backup your apps and data using Android Backup and Restore Tools project, then clean flash the 19.1 version. It won't backup everything but it's the best backup solution I know of (apart from TWRP, but I haven't been able to make TWRP backup / restore work on LOS 19.1 or 20)

Good luck, and I'm sorry I can't be more help
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Tim700_0:
@peteforth: Thanks for your very quick reply:)

It seems like I am stuck on your LOS20 build 4microG a bit.

Dirty flashing back to 19.1 does not work and ends in a boot loop, the same for @No1Alien's original LOS 20 UNOFFICIAL version.

Everything works fine except the mobile data and GPS locking and calls get interrupted as soon as I switch on mobile data.

I evaluated in the LOS 19.1 UNOFFICIAL thread again and saw that those problems seem to be ongoing for some european t-mobile users since version 1.4 of 19.1 (and seemingly ongoing in LOS 20 now too?)

- I missed that before because I never upgraded further from 19.-1.3.

RKirpest's issues (the post you quoted) are identical to mine.

But perhaps someone can help me out with TWRP backups?

There's are options to choose System or System Image and Vendor Image in the backup function (the others do not seem to contain much data?)

-Which one do I have to tick for backupping my personal data?

Thanks again

Tim.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] TheArt.:
I know the thank you button exists but.... THANK YOU anyway for keeping alive this little nice phone with microg!
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Rrreutel:
I don't remember seeing a logcat yet of when this network/data flapping is occurring, anyone?
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] jimmygumble:
Hey. Can whomever created the custom build please start a new thread. It'll only cause confusion for people needing help with the official release in this thread. :)
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] petefoth:
For general discussion of my Lineage for Microg builds for this and other devices, I use the GitHub Discussions feature in this repo

Any problems can be raised in my Codeberg issue tracker

I will continue to publicise new builds in this thread as and when I build them, which will usually be when @No1Alien makes new builds of his ROM.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Yokurt815:
Is my understanding correct?

Unofficial = rebuild of this threads rom

custom = microg variant
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] petefoth:
No. Both are Microg.

- Unofficial is standard LOS for Microg

- Custom is a custom build, aimed at users of the privacy-friendly /e/OS and their cloud ecosystem.

More details here
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Flamefire:
@derf elot Your TWRP (3.6.2) doesn't seem to support sha256 checksum files. Any chance to build one with SHA2 support or provide some instructions how to easily build that TWRP?
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] cRaZy-bisCuiT:
Hey guys! Thank you very much for this rom! Right now I do use [0]. I can't install GCam. Do any of you have successfully installed a GCam mod? One of my preferences would be the version of "onFire". While in some other threads with other ROMs people had success, I don't know if the issues are caused by Android 13, Lineageos 20 or the XZ1C itself. Do I need to patch the camera API first or something like that?

[0] Rom in use:

Unofficial https://share.jaguar-network.com/dba26051-29c9-41d5-a4e6-02a746b47c85
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] geodescent:
See attached (Edit: logcat edited to remove sensitive info).

Some choice lines below seem to lead to this Lineage bug report.

12-10 12:03:09.194 0 0 E : modem subsystem failure reason: dog_hb.c:266:DOG_HB detects starvation of task 0x9b65e990, triage with its own.
12-10 12:03:09.194 0 0 W subsys-restart: subsystem_restart_dev(): Restart sequence requested for modem, restart_level = RELATED.
12-10 12:03:40.501 0 0 I subsys-restart: subsystem_restart_wq_func(): [kworker/0:2:19200]: Restart sequence for modem completed.

12-10 12:17:48.963 1584 1646 W BroadcastQueue: Permission Denial: receiving Intent { act=android.intent.action.SERVICE_STATE flg=0x1000010 (has extras) } to com.android.cellbroadcastreceiver.module/com.android.cellbroadcastreceiver.CellBroadcastReceiver requires android.permission.READ_PHONE_STATE due to sender android (uid 1001)

12-10 12:17:49.188 2853 9800 D CS-Configurator: reApplyModem - current modem: /system/etc/customization/modem/amss_fsg_lilac_tmobile_us_ims_tar.mbn

Getting the notification:

sony modem

status: 0

amss_fsg_lilac_tmobile_us_ims_tar.mbn

com.codeaurora.ims already has unchangeable permissions so there's little I can do as I haven't rooted.

I saw someone else wasn't able to dirty flash a downgrade, but I'll give it a shot.

Worst case I have to clean flash lineage-19.1-20220408-UNOFFICIAL-1.2-lilac, which is may work since it's mentioned here that everything from 1.3 on has this problem.

g8441 US variant

T-Mobile

twrp-3.7.0_9-0-lilac

lineage-20.0-20221002-UNOFFICIAL-1.0-lilac (clean flash)

MindTheGapps-13.0.0-arm64-20220927_220846
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] geodescent:
Had to clean flash lineage-19.1-20220408-UNOFFICIAL-1.2-lilac with MindTheGapps-12.1.0-arm64-20220605_112439 but all is well.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Rrreutel:
Great, your log + version info is at least something that can be investigated. A watchdog process is observing starvation of a task (deprived of, or waiting for some resource) causing restart of the modem. I don't have enough low-level knowlegde to diagnose this, but out of interest will have a look.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Rrreutel:
This might be going off on a tangent, but the only reference I found to the error message:

E : modem subsystem failure reason: dog_hb.c:266:DOG_HB detects starvation of task 0xbab03e10, triage with its own.

is on a linux-arm-msm mailinglist message here where a very similar error occurred (although probably not on a lilac device).

As a solution this answer was given:

where diag-router might refer to this tool.

That doesn't seem to me like something you'd like to run permanently as part of an Android ROM.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] anarki@butterblume:
@petefoth Just flashed your custom build over Flamefires' 18.1, wiping system and cache while keeping data. It runs flawlessly. Thanks a lot!

I must say LOS20' GUI is definitely a drawback compared to 18.1. Strange screen space reservations, different clock positions and styles, some heading fonts huge while other text pretty small.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] anarki@butterblume:
Btw @petefoth I don't use K9 (since I do mail on my Arch machine only). Now I can disable K9 via

adb shell pm disable com.fsck.k9

but adb won't let me uninstall via

adb shell pm uninstall com.fsck.k9

I'd leave it like that but F-Droid keeps asking to update K9. Do you know how to remove it?
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] petefoth:
A couple of things to try:

Either of the below commands should work

adb shell pm uninstall --user 0 com.fsk.k9

adb uninstall --user 0 com.fsk.k9

In F-Droid

- Settings |Manage installed apps

- click on K-9 Mail

- from the 'three dots' menu, choose 'Ignore All Updates'
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Rrreutel:
It's not ideal, especially for our small screen. It's not a proper solution, but in Settings you can decrease 'display size' one or two notches, which helps a bit with decreasing the large margins and round corners. If text becomes too small to your taste, you can increase 'font size'.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] petefoth:
I use Lawnchair with font size set to 85% and icon size set to 75% and it looks fine to me :)
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] anarki@butterblume:
@Rrreutel @petefoth Increasing 'Smallest Width' in developer options from 349 to 399 improved font display for me. Some fonts seem to use that for size calculation in 20.0 (and some don't). Since it had a low initial value, some headings would render too large. It's naming is unambiguous, I think, since the entered value is of type dpi.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] anarki@butterblume:
Thank you! The --user switch did the trick. I also removed bromite the same way to be able to manage it by F-Droid (F-Droid complained different signing keys).
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] anarki@butterblume:
Which makes me think that I may have to repeat that every time after updating your build.

Android seems to handle my formerly installed bromite and the one shipped with you build as different apps, so the latter couldn't load my existing user profile.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] petefoth:
Where rid you get your installed Bromite? Mine is pulledd from the Bromite f-droid repo https://www.bromite.org/fdroid
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] anarki@butterblume:
Well, this I do not understand yet:

1) Had flamefires 18.1, installed Bromite via F-Droid, used that for months

2) Flashed your 20.0, kept /data. All apps and settings persisted, but:

3) Bromite shipped with you build wouldn't load my former profile

4) Tried to update shipped Bromite 102 to 108 via F-Droid. F-Droid complained different signing keys

5) Removed shipped Bromite 102 by pm uninstall --user 0

6) Install of Bromite 108 via F-Droid fails. pm logs more information:

adb shell pm install --user 0 /data/user/0/org.fdroid.fdroid/files/Bromite-108.0.5359.109.apk
Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE: Existing package org.bromite.bromite signatures do not match newer version; ignoring!]

More to this:

7) Removed all cached Bromite data and packages

8) Install of Bromite like in 6) still failing

9) Removed /vendor/etc/org.fdroid.fdroid/bromite_repos.xml and rebooted

10) Now I can install Bromite 108 via F-Droid and also by pm like in 6)
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] petefoth:
Standard F-Droid does not include Bromite https://search.f-droid.org/?q=bromite&lang=en I guess you either

- downloaded the Bromite APK in a web browser, then used F-Droid to instal the downloaded APK

- or you added FFUpdate from F-Droid and used that to install Bromite

- or you added a repo to F-Droid which does contain Bromite

However you installed it, your Bromite has a different signature from the version in my ROM. I thought that mine was the latest version from Bromite, but I've checked and I'm wrong. I will try and fix that, but until I do I\m afreaid you will need to disable or uninstall mine. Sorry
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] anarki@butterblume:
I always install Bromite via its F-Droid repository using the keys fingerprint E1EE5[...] as listed at bromite.org/fdroid - exactly the the same fingerprint you put into /vendor/etc/org.fdroid.fdroid/bromite_repos.xml

Now after I temporarily removed the latter xml and rebooted, my F-Droid client 1) still knows Bromites F-Droid repository and 2) installs Bromite without errors, which makes me suspicious. I will look further into this.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] anarki@butterblume:
@petefoth I now did a complete wipe and reinstalled your 20.0 build. F-Droid reports the two microG F-Droid repo and archive as set in you bromite_repos.xml. But it doesn't see Bromite repo, although it is listed in the latter xml.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] petefoth:
Yes. I'm sorry, but Bromite in my custom ROM is a bit broken :( I've not noticed it before as I don't use Bromite myself. It's only in my custom builds for people who don't like Mozilla- based browsers. I plan to remove it from my builds in future, unless I can find an easy way of fixing the problems.

Sorry again!
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] anarki@butterblume:
No worries. I use Bromite a lot I like that you're shipping it. I think the problem is the pubkey line in your xml config. It points to the key's fingerprint, not the key itself.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] anarki@butterblume:
@petefoth Bank app issue: "SecureGo Plus"

- was working on FlameFires 18.1

- was also working after flashing your build over 18.1 without wipe

- refusing to start after a complete wipe on a newly installation of your build

Do you have suggestions?

Addendum:

This app seems happy with the existence of microG. I installed a current build of MinMicroG (like I had on 18.1) and it starts without errors.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] petefoth:
In what way is it not working?

Does the app refuse to run?

Does some part of the app not function?
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] anarki@butterblume:
Sorry for ambiguous wording. The app refused to launch. At some point it opened a web page stating that "rooted phone or some other modification" has been detected.

I just built a recent release of MinMicroG and installed it via TWRP. Now the app doesn't complain anymore. The reason might be the existence of microG / com.google.android.gms or even FakeStore.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] petefoth:
I can't reproduce that I'm afraid. I did a clean install of `lineage-20.0-20221127-4microg-CUSTOM-PLUS-E-lilac.zip`, installed SecureGo Plus from Aurora Store and it ran just fine.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] anarki@butterblume:
Thank you for looking into it.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] gladykov:
I just encountered GSM connectivity problem accompanied by WiFi disconnecting after few months of using Lineage 20. Brasil, Claro network.

It is puzzling, is phone dying or carriers around the world introduce new hardware / software, which is not compatible with something?
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] gladykov:
Question: If it occur again, how I can gather useful debug logs from modem?
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] geodescent:
This, perhaps?
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Rrreutel:
Nice find. I took a look, and while it's somewhat related because the issue is also a restarting modem subsystem, it mainly prevents a kernel panic (phone crash) after modem subsystem restarts. It doesn't seem to be the same issue at the root. The patch(es) add a check for existence of a gsi_reg array before clearing, but this datastructure does not even to exist in file dwc3-msm.c of our 4.4 kernel.