yashsingh1/xdaforums huggingface dataset:
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Yokurt815:
Maybe not dead, but latest lilac builds I can see are from July 22: https://download.havoc-os.com/?dir=lilac
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] eve1374:
Hi,

I've installed the 20.0 1.1 version (with wiping data and all), and with MindTheGapps. Everything worked well out of the box. Congratulations to the developers.

I try different launchers - currently I like "Wide" because it lets you order the icons in the app drawer manually (and also you can put funny widgets on the home screen and link them to an app, like an icon).

I'm also testing a whole bunch of camera apps so I can find one that I like.

There was one thing that didn't work in the LOS 19 version I had : using the split screen with animations disabled. With LOS 20 1.1 + default launcher trebuchet, it worked. At the moment I write this, I can't have split screen anymore, maybe because I changed launcher. when trying to setup split screen, something crashes and I have a popup saying that trebuchet crashed. I don't know how trebuchet and Wide work together, I thought Wide would replace trebuchet when I set it as a default launcher.

Two things that I personnally don't really like are :

- when you display all apps currently open, the "close all" button is faaaar away on the left, if you have many apps running. Is there a workaround to have it more accessible than having to go through all the opened apps to close all ?

- I enabled the gesture navigation so that I gain some space on the screen. I like that going back is a swipe from left to right, but I'd like if swiping right to left was going forward instead of being the same shortcut. So if you go back by mistake, you can re-.go forward by swiping the other way. I had this on my web browser vivaldi when I had the latest sony android version and no navigation gesture enabled from android. If there was a workaround for this, I would be interested as well.

Cheers

Eve
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Arcline:
Hey there, the two features you don't like are ether a part of AOSP or mainstream LineageOS. Lineage doesn't take feature requests, but you can submit a patch and let them review it. Yes, that means you have to know how to code.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] eve1374:
Thanks for your reply. Since I don't have other phone to compare I wasn't sure were these feature come from. So there are no settings to change this.

I do code sometimes, but I think I'm not close to add something interesting (and working :)) to Lineage. If one day it becomes my favorite hobby, I'll think about it, for sure.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Maflo:
Thank you for your return. I take advantage that you are on LineageOS to know if:

1) the button dedicated to the camera which works correctly?

2) Do you have an option for network traffic in the status bar?

3) Can you display the seconds in the status bar or in lock screen?
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Arcline:
You have all of these options, yes.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Maflo:
Thank you for your answer, it motivates me to test LineageOS 20.0
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] eve1374:
@Maflo , yes.

for point 1, the dedicated camera button works when the phone is unlocked, with a long press. When I had the Sony Android version, double pressing the power button at any time (even with phone locked) used to start the camera, without entering the code. Now with LOS20 it asks for the code / fingerprint. I noticed that the phone doesn't go to sleep when camera is on - which is a problem if you accidentally turn on the camera when the phone is in your pocket (overheating, battery). I'm not sure if that was the case before installing LOS though.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Tim700_0:
Is LinneageOS 20 finally working with Telekom network providers?

Hello I'd like to update to LOS 20 again.

I tried that last November but encountered the issues with mobile network and interrupting in a constant cicli.

I posted that here and reverted back to LOS 19.1 (build 1.3) finally. I saw the topic popping up again here since then but did not know if the issues finally could have been solved?

I used 19.1 as a daily driver but since 2 weeks I can't get a stable GPS lock anymore even though up to 20 satellites are shown as "visible".

Do you have any tips to get it working again? I always use the GPS Test app to get a better connection fix and toggled the location services on and off also- something seems to have stopped working it seems.

Or I should really try LOS 20 now for a second time?

Thank you in advance.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Maflo:
Thank you for this detailed answer.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] rez78:
Yes
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] berti42:
I updated from 19.1 to 20.0 the dirty way (without wiping anything) and everything is working perfectly! Thank you! I'm using "OpenCamera" as camera app.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Maflo:
Finally on LineageOS 20.0 (v1.1)!

So far, I'm pretty happy with it. Lack may be more customization compared to HavocOS but it is a detail compensated by everything else (including being in A13). Two quick questions:

- No way to constantly hide the status bar in full screen mode (especially in games); the green GPS light is not a problem, but it sometimes makes me reappear the entire bar (with the time, the battery, etc.) to make it disappear again later.

- In an option (in confidentiality then Trust), I am told to manually update the "vendor.img" file; where can i find this file?

If not, who should we donate this rom to? :)

For those interested, I can provide you with a tutorial and the files to have the Sony Music player via the Play Store (without the message that our phone is incompatible)
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] petefoth:
I would be interested in that. Thanks
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Maflo:
No root need

1) Go to this address (if not valid, I could create a link): https://drive.google.com/file/d/1MevyoFMXNl7ggxaGH3cBuoQ8LOmwo17A/view

2) Get the "system" folder (or download the archive and extract the "system" folder). Noticed: The "priv-app" folder will not be useful, you can delete it

3) Put the "system" folder on your SD card or internal memory

4) Boot into TWRP, go to "mount", mount System (uncheck "Mount system partition read-only")

5) Go to "Advanced", then "File manager", move the folders and files present in the "system" folder that we downloaded ("etc" and "framework" folder, not "priv-app" folder) in "/system_root/system"

6) Reboot and enjoy, Sony music is valid in play store
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] flyingfishfinger:
Hmm, anyone have trouble with NFC? I can't even enable it, the slider just toggles back off immediately.

Thoughts and / or fixes?

R
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] android666:
it happened to me on Z1C, when I broke NFS connection during battery replacement :-)

but yes, it can be also software related
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Flamefire:
Found something funny/strange: When using the TWRP from this thread (twrp-3.6.2_12-0-20221002-lilac.img) with a LOS 18.1 installed then the ROM fails after that TWRP is started once.

I.e.:

Boot LOS 18.1 to verify everything works

Boot TWRP 3.6.2

Power off device (i.e. don't do anything in TWRP at all)

Boot LOS 18.1 again

E.g. bluetooth service crashes repeatably due to strange SELinux denials on `/data/user_de/0/com.android.bluetooth/databases` and below

Any idea how simply booting TWRP can affect the ROM such that SELinux issues arise which can only be resolved by formatting /data and not booting into TWRP again?

I reproduced this every time with LOS 18.1 and it does not happen with TWRP 3.7.0 (twrp-3.7.0_9-0-lilac.img)

Is that expected as that TWRP seems to be for A12 (LOS 19) and up? Or might this be a bug fixed in TWRP 3.7+?
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] 7alvoo:
Dear derf elot unfortunately this twrp-3.6.2_12-0-20221002-lilac.img is only capable of installing updates, the data partition backup restore is not working propely. Really miss a stable working new 3.7 twrp for 12/13. Of course it's a wonder that it the old worked when you created it after all it wasn't even supported in the 12/13.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Rrreutel:
I did a new lineageos-20 build with some kernel updates to test (cip v4.4-st38 merged in) in combination with lineageos-20 source tree from 2023-03-22, and microG included, but the resulting ROM doesn't get past the Lineageos animated bootlogo. It animates for 10 minutes, then reboots. Not sure what's to blame: LOS, kernel or microG (or you know, PEBKAC). I actually waited about an hour till it completed at least 5 reboots to see if android rescue party would kick in and boot to recovery with some diagnostic info, but it doesn't, it just keeps rebooting after every 10 minutes of LOS boot animation. adb won't connect at this stage.

I tried:

1) formatting data first

2) dirty flashing the new ROM after a good boot with an older ROM

3) using an older boot.img kernel and initramfs (known to work in combination with the ROM it was built with)

Now regarding 3):

It's been a while since I separately flashed just a boot.img instead of installing a complete ROM, but this is confusing me: I can't get the device to boot with a different boot.img than the one that was built with the ROM. If I try a different boot.img (from an earlier and working ROM version), the device just hangs at the white (kernel?) screen with Sony boot logo. If I reflash the original boot.img from the ROM with the method below, the boot does continue past the Sony logo screen.

It doesn't matter if I try to boot another boot.img one time with

fastboot boot boot.img

or if I flash it first:

fastboot flash:raw boot boot.img

or

fastboot flash boot boot.img

I'd expect it to be possible to boot with a different kernel this way, or is there a step I'm missing? (I've seen some general references to flashing vbmeta.img partition first to disable some verity related checks, but that's a step I don't see in the LOS install script of the ROM either, and that's working fine somehow: when installing a ROM, the boot.img within the zip gets flashed correctly and boots ok)

Any hints on how to properly boot with another kernel? Or do I need to build and install a complete ROM everytime I'd like to test some kernel patches?
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] q4q9x:
I'm seeing a problem with Enterprise WPA that I haven't seen before running other LineageOS versions (or derivatives such as /e/OS). Of course, the old PEAP/MSCHAPv2 situation's involved, but I'm already aware of the nature of that and how to work around it—normally, that is.

Basically, as on other LineageOS versions and /e/OS 1.9, I ignore the Domain field with its' exhortation that I "must specify a domain," and select "Trust on first use" for the CA Certificate field. Connection is made to the access point, I'm prompted to verify the trust of the connection's certificate, and I'm successfully connected.

However, unlike the other LineageOS versions or /e/, the next time the connection's made it fails until I set "CA Certificate" back to "Trust on first use" and connect again.

Is this a known issue with Lineage 20?
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Rrreutel:
Turns out to be a kernel issue in the end. Bisected all changes from cip v4.4-st38, and this is the culprit:

ALSA: pcm: Move rwsem lock inside snd_ctl_elem_read to prevent UAF (e8064dec) · Commits · cip-project / cip-kernel / linux-cip · GitLab

[ Note: this is a fix that works around the bug equivalently as the two upstream commits: 1fa4445f9adf ("ALSA: control - introduce snd_ctl_notify_one() helper") 56b88b50565c ("ALSA: pcm: Move rwsem lock...

gitlab.com

reverted it for now, and the rest of the merge is fine.

Strange that @Flamefire 's builds don't seem to suffer from this commit, maybe because of the subsequent commits in his branch:

ALSA: pcm: Move rwsem lock inside snd_ctl_elem_read to prevent UAF · Flamefire/android_kernel_sony_msm8998@e8064de

[ Note: this is a fix that works around the bug equivalently as the two upstream commits: 1fa4445f9adf ("ALSA: control - introduce snd_ctl_notify_one() helper") 56b88b50565c (&quo...

github.com

edit: I should have done better research beforehand: @Flamefire submitted a PR to the los20 branch of the whatawurst kernel repo last week already, including a proper fix for the problematic commit instead of just a revert-workaround. Great work!
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] petefoth:
If I were to make a build with Whatawurst's current `whatawurst/android_kernel_sony_msm8998` repo, would I need to revert this commit?
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Rrreutel:
No need to revert the commit in that case, whatawurst/android_kernel_sony_msm8998 doesn't yet have cip v4.4-st38 changes (which includes this change) merged into it atm.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Flamefire:
Not only that, I submitted the fix to CIP and they included it in st39 :) so it is/will be fixed going forward
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Dfis:
Hello. Any new updates for Lineage 20?
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Rrreutel:
There's a good number of updates to both LineageOS and also some to the kernel (cip tag v4.4-st39) including 2 asb patchsets that would make a new release useful. Hopefully @derf elot is willing to invest some time once more.

On a side note: one interesting feature being worked on in the LOS codebase is charging control (similar to smart charging stock feature, e.g. stop charging at 90% or use a charging schedule).

If this could be used in the yoshino/lilac builds (maybe similar to this) that would enable managing battery life a bit better. I've tried to adapt and build for lilac, it builds, but I've had no success yet actually getting charging to stop, only to be able to use the charging control Settings UI.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] flyingfishfinger:
On the subject of new builds - anyone tried out the NFC? If it's working, how can I debug mine?

Cheers,

R
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Rrreutel:
I can only say that NFC works on my own LOS20/microG build which is slightly more recent than the 'official unofficial' one in this thread, but I don't recall it failing on a previous build either. I tested with NFC tools, which properly scans a NFC tag. I can also toggle NFC on and off in Settings just fine. If you enable developer options menu (tap Settings->About Phone->buildnumber several times until developer options enabled) there's an option "NFC stack debug log" to increase NFC log level if a normal logcat does not give enough info.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] flyingfishfinger:
Ok, here's a logcat from me attempting to toggle the NFC enable from the pull-down menu, it just stays greyed out. I'm not sure what to do with this except ask for help - there ARE a couple of errors.

The second is a post-boot log, which also has some errors - many of the same, but also some different ones.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Arcline:
I believe the NFC problem is connected to the stock firmware you had installed before Los.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Rrreutel:
I compared your log to mine, this is different:

yours:

[04-19 14:15:23.871 3821:665 I/libnfc_nci]
[INFO:NativeNfcManager.cpp(775)] nfaDeviceManagementCallback: NFA_DM_ENABLE_EVT; status=0x3

[04-19 14:15:23.871 3821:4525 E/libnfc_nci]
[ERROR:NativeNfcManager.cpp(1242)] nfcManager_doInitialize: fail nfa enable; error=0x0

mine:

04-18 12:33:55.188 3159 4025 I libnfc_nci: [INFO:NativeNfcManager.cpp(775)] nfaDeviceManagementCallback: NFA_DM_ENABLE_EVT; status=0x0

Probably the nfc controller fails to initialize for some reason, maybe hardware failure. No good advice on what to do about it other than reflashing a known good ROM where it used to work, stock if necessary. If that doesn't work either, then at least you know it's likely a hardware failure.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Rrreutel:
Good point, be sure to have had stock 47.2.A.11.228 installed before installing LOS20 (and while you're at it, check if NFC works there ;-)
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Dfis:
Did anyone notice that during a call, the other person barely hear? low-volume microphone... He said that I sound like talking far away... I need to speak very close to the mic to hear myself well....

Came across with this forum: https://xdaforums.com/t/los14-15-16...c-gain-and-a-little-speaker-gain-too.3491483/

It might related to mixer_paths.xml
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] flyingfishfinger:
I found it as a TAR file from here - can I just flash that with TWRP? It's not a zip...
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Rrreutel:
No, that's not a complete ROM, you can't install it.

You can try the XperiFirm tool, use that to download a 47.2.A.11.228 version (not sure about the status of the topmost *.234 version, any 228 should be fine).

edit: to be more clear: you can't flash the stock firmware with TWRP either, you can check out this page for instuctions (or search xda ;-) Backup first!
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] flyingfishfinger:
Ah, why won't TWRP work? I had a hard time getting it on there in the first place - seems silly to undo all of that. But ok, will check. Thanks for the info!
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Maflo:
If I can help you a bit; here is the tutorial I am doing to put my phone back to stock: Steps to use Newflasher to flash Sony Xperia
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] flyingfishfinger:
Ehh, this is the SO-02K version. Newflasher complains about the mismatched signatures, and there is only 47.2.B.5.38 available for this version on XperiTool. I'm not sure if that's newer or older than 47.2.A.11.228...
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Rrreutel:
That would've been good info upfront, these SO-02K devices are slightly different beasts. See e.g. here where someone mentions that losing NFC is to be expected. You might get better help in those specific SO-02K/Docomo threads than in this thread about LOS20.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] flyingfishfinger:
Ya sorry - I actually didn't realize it myself for a while. The LOS ROM shows me G8441 in the device strings / Settings and I totally forgot that I had purchased this version.

Anyway, thanks for the help, I'll go check over there. FWIW, LOS20 works nicely on the device either way.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] petefoth:
Some recent builds for lilac based on this ROM​

I have recently made new builds for lilac of a few different ROMs, based on this LineageOS ROM and the `whatawurst` github repos

LineageOS for microG: `lineage-20.0-20230424-4microg-UNOFFICIAL-lilac.zip`. Support and questions (if needed) in this thread. Note that I am no longer building the 'CUSTOM' version: it was primarily for my onw benefit, but I have now moved my own phone on to ...

IodéOS :`iode-4.1-20230419-lilac.zip` Supported in this thread on the IodéOS community forums

/e/OS: `e-1.10-s-20230413-UNOFFICIAL-lilac.zip` Supported in this thread on the /e/OS community forums
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Arcline:
Thanks for the build! Refreshing.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Maflo:
Thanks. I admit that I am a little lost with all these solutions.

"LineageOS for microG" tells me something; I can update directly from my current version? (lineage-20.0-20230108-UNOFFICIAL-1.1-lilac.zip)

On the other hand the other two (IodéOS and /e/OS), know absolutely not: S
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] petefoth:
Correct. You should be able to 'dirty flash` the new version over your existing setup without losing any apps or data. ( I usually make a back up before flashing, but I've not had to use it yet!)

They are both custom ROMs, based on LineageOS for microG, which aim to be even more privacy-respecting. Here's a brief summary (based on my personal experience and opinion of both systems - other may see things differently), but if you are interested in exploring them, then it's worth exploring their own web sites and user forums

/e/OS

aims to provide a 'complete, fully “deGoogled”, mobile ecosystem`, offering all the features a new user needs 'out of the box', including and online account (based on NextCloud) and built-in toools to use it

provides 'Advanced privacy` tools allowing users a further configurable level of privacy. These tools are new, and at present still quite buggy

implements and curates its own app store, called App Lounge, which can install FOSS apps from F-Droid, non-FOSS, free apps from Google's Play store, and Progressive Web Apps. Again, this app is quite new and still buggy, particularly in comparison to established app stores like F-Droid and Aurora Store

chooses to make its own recognisable UI, by implementing their own homescreen / launcher app, called Bliss, and by forking various open source apps ( email, SMS messaging, calendar, notes, and tasks apps) in order to use the same colour scheme

IodéOS

focusses more on flexibility, allowing users to pick which of the included apps they want to install

does not include an online account

allows blocking of calls to the network by installed apps. This is configurable either at the system level or on a pre-app basis

offers included apps mostly without forking. This means that these apps are generally more up-to-date in terms of features and bug fixes than their /e/OS equivalents. But they all have different colour schemes

includes both F-Droid and Aurora Store app stores

the exception is the IodéOS browser app, which is a fork of Mozilla's Firefox, with some privacy features improved, telemetry removed, and a samll amount of UI 'branding'
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Maflo:
Thank you for taking your time for some explanations :)
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] knutlegrand:
Hello,

Since update from LOS 18, everything seems to be OK, except the display which is always ON when the phone is charging. Dev option "Leave screen ON when charging" is disabled.

I'd like the screen to be switched off when charging.

It worked on LOS 18 (and previous versions). Is this a bug of Android 13 ? or LOS 20 ?

So, what's the way to get the screen switched off after a specified delay when charging ?

Thx
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Arcline:
Hey, seems theres a new build. Check the changelog here https://xdaforums.com/t/rom-lineageos-20-0-unofficial-1-2-2023-05-06.4501493/
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] norabitox:
It looks like the 2 button navigation is gone with the update.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Maflo:
Thank you, I had not seen indeed that a version was available for the month of May
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] 3ncryptet:
@Flamefire Thanks for the most recent Update and keeping my beloved XZ1 Compact alive (y):cool:
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] GT500s:
I think it's for XZ1 not XZ1c
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Maflo:
Version 1.2 for xz1c is also available: here

Same for MindtheGapps which has been updated