This thread aims at providing LineageOS 18.1 builds for the Sony Xperia Z1 compact with current security patches.
You can consider this thread as a successor of our LineageOS 17.1 thread, where you may also find some useful information.
This is the joint effort of 115ek and MSe1969 (contributions welcome).
Just wanted to share my success story and thank all the developers for their awesome work on this ROM!
Some quick background info: my device is several years old and it was sold to me as "not working", "for parts only". After buying it, I once managed to boot it enough to see that it was running a version of CyanogenMod but that was it. For several years it's been a surprisingly expensive paperweight and nothing else. Just for the sake of it, I decided pulling it out yesterday and seeing what, if anything, happens if I press down the hard reset button located next to the SIM card slot. Lo and behold, the phone vibrated!
After a crash course in adb and its several quirks and other related, relevant things, I thought I knew what to do and how to proceed. Luckily for me, the phone had a TWRP version installed so I didn't need to figure that out. Phew!
...so imagine my shock and horror when the OS (the old CyanogenMod one, that is) had been wiped out and the Lineage OS ROM, despite really being the correct one, refused to flash! I'm not sure what was going on there, was it a TWRP bug or something, but despite my device being an amami, it was reporting itself (in TWRP at least?) as "" (i.e. empty string), and thus the
After searching a bit I ended up in an XDA thread for a different device&ROM with the same issue and I went with the solution suggested there: just removing the assert() call, because I knew that the target device was correct.
That worked and I was able to flash the ROM successfully! Not my first rodeo with adb and the like, but the first time I flashed a ROM. Admittedly it was a somewhat stressing procedure, and my stress was only alleviated by the knowledge that this is my paperweight, and not someone else's daily driver.
How are the telephony features on amami/honami on Lineage OS 18.1? I'm thinking of gifting a honami as a Christmas present to someone who is not that tech-savvy and uses the phone still for calls as well as for browsing the Internet, so having reliably working telephony features is a must. (Whereas for me, I'm just planning on using my amami as a testbed for mobile development related things so I'm not too concerned about telephony.)
Relatedly, some newbie questions that might be answered elsewhere but I was unable to locate the answers, so apologies in advance...
1. Where do the Bromite UI strings come from? A few (e.g. "Bookmark all tabs", "View source" and "Exit" in the main "three dots" menu) are untranslated into my language and I'd like to help out with the translation effort where possible.
2. Related to #1, the "Contacts" app name is correctly translated (as "Yhteystiedot") but in the app drawer view it shows up as "Yhteystie..." - is there a way to force the UI to render the whole word instead of three dots if and when the "truncated" word with three dots is equally long as the "full" word? (Yes, this is a super minor nitpick, I know!)
3. My device has a battery/charging-related problem that I assume is specific to my faulty device rather than the ROM, but I'll ask anyway...so, when charging, the screen turns on and if I manually turn it off, it'll just turn on again in a few seconds and it didn't charge past 33-34% in my testing yesterday. adb logcat output, which I dumped into a file, has some suspicious lines about a Daydream issue in the com.android.deskclock.Screensaver package. Some quick searching suggests that it's a known issue that oughta be very easy to fix. Can someone confirm/deny the existence of this Daydream-related issue? And does it impact charging and/or the battery in any way?
4. Potentially related to #3 and why the screen won't turn off on my device, but the adb logcat output has some suspicious lines related to "Telecom" and Bluetooth features etc. Are these messages just log noise or potentially indicative of some sort of a problem? I'd be more than happy to post snippets here or on a pastebin etc. for a developer to take a look at if this is something worth investigating.
Again, my thanks to all the awesome people working on keeping amami alive - hard to believe that little device is turning 8 years old next January! It's quite a lifespan for a mobile phone these days, and it would not have been possible without all of you!