Hi,
I have a bug since the last update.
In plane mode, my screen keeps turning on for no reason, which result in battery drain.
And when combine with an alarm set on it uses more than 50% of battery in about 4 hours.
It used to do that (screen turning on when in plane mode but really less) this summer and then it stopped. But it’s back and my phone don’t last the night if I set an alarm.
And when I just put it in plane mode during the night it uses at least 20% of battery.
I don’t use a lot of plane mode except when I’m not home and need an alarm… I usually turn off my phone at night.
I don’t if anyone has this behavior or if you know how to fix it
Sorry I’ve not seen this behaviour, but I don’t use this ROM any more. You could check in Settings, Battery, Battery usage if you can see which app is to blame. Then try force stopping and clearing data for that app. (It may be a system app and you would need to choose ‘Show system’ from Settings, Apps)
Ok thanks.
I don’t see anything that causes this.
I did some screen shots when it happened, I’ll put theme here.
Nothing obvious there, but it is definitely discharging quicker than it should
It might be worth installing the Battery Bot Pro app, leave it for a while, then check the logs
Ok thanks I’ll do that
Here’s a new CUSTOM build made from the v1.9-s tag. (See here for information about build types)
The reason it is CUSTOM rather than UNOFFICIAL, is that in this build it is possible to use Trebuchet as the default Home / Launcher app. If you clean flash the build, you will be offered a choice between Trebuchet and Bliss at the end of first time setup. This was achieved by changing two lines of code, (shown in the patch in my earlier post).
I don’t plan to make an UNOFFICIAL build without the Trebuchet change: if you don’t want to use Trebuchet, then choose Bliss, which should work as well as it always does 
Release notes here
I have clean flashed the build and it seems to work: the test phone boots up fine, internet access via WiFi work, fingerprint scanner works. I’ve not tried calls SMS and mobile internet because I don;t currently have a spare SIM lying around. But there’s not reason why it shouldn’t work
It should dirty flash OK over previous unofficial and custom S builds, but - as always - use at your own risk.
Release notes not yet available for 1.9 builds but they sgould be here soon
Have fun 
Thanks for all the links!
Hi, thank you very much for keeping XZ1c alive.
Did I get it correctly :
- stock camera is only available on Android 10 = “Q”, right ? Either /e/OS or Lineage for microG would be fine.
- /e/ once released “q” ROM but not available anymore ?
Currently (stock ROM) I use F-droid and Aurora stores.
I’m about to switch my xz1c to another ROM for the first time, never done that before and I’m a little bit confused, especially for finding the trustworthy repositories for the “Q” ROMs (/e/ and Lineage/microg).
Thanks for your help.
Welcome @Kracien to the world of privacy-respecting custom ROMs
That’s correct. Nobody has made the Sony stock camera app work on Android versions beyond Android 10 /Q/. Interestingly, there is a new FOSS camera app called Aperture, which is available in LIneageOS 20 / Android 13 builds (see below), and is apparently much better than OpenCamera (used in /e/OS) and Snap and Camera2 used in earlier versions of LineageOS. I don’t know whether its as good as the stock Sony app, as I’m not a camera expert.
Yes, it was an official /e/ device for a while, but /e/ did not want the /e/OS ROM for lilac to include the stock Sony Camera. They asked the ROM maintainer (me ) to remove the Sony app, but I didn’t want to, so the device stopped being official. /e/ cotinued to make builds, but they were only available as OTA updates for people who had downloaded and installed it when it was official and publicly available. However, you can get your hands on it if you want it - see below
/e/OS
- The latest official /e/OS version is Q, and though it isn’t publicly availabe for download, I did download the OTA updates andthem make them available in my AndroidFileHost account. The latest I have is
e1.4-q-20220923220853devand I believe it still has the stock camera. If you install that, there may be later versions available as OTA updates. - If you can live without the stock Sony camera app, then I have made unofficial builds of later versions /e/OS - the latest is
e-1.9-s-20230312-UNOFFICIAL. These unofficial builds don’t get OTA updates, but I try to make builds available soon after /e/ release a new version.
LOS
- The upstream developer FlameFire makes LOS 17.1 / Android Q versions with the stock camera app (as well as 18.1 / R and 19.1 / S versions). He makes normal LOS builds and Lineage4Microg builds. They are available in his AndroidFileHost account and supported in this XDA forum thread. The latest Lineage4Microg build is from 25th February. Again, these don’t get OTA updates, but the developer does make regular releases for you to install manually. The updates can usually be ‘dirty flashed’ with no loss of user-installed apps and data
- If you want the very latest, then Lineage OS 20 / Android 13 builds are available:
- Normal LIneage OS are available from the upstream developer’s SourceForge account
- Lineage4MicroG builds, built by me using the same sources, are available in AndroidFileHost.
- Support is in this XDA forum thread
TWRP Recovery
Get the latest TWRP recovery for this device - which will work with whatever Android versions or OSs you choose - from SourceForge. If you stumble across a version of /e/'s Recovery for this device, do not try to use it: it was built but never tested, and it doesn’t work
All the ROMs I build for this device - /e/OS, LIneageForMicroG, and IodéOS - are available in my AndroidFileHost account. If you have any more questions about /e/OS or TWRP for lilac, please feel free to post them here. If you want more information about LineageOS or IodéOS, please either send me a private message or ask in the XDA forums linked above or the IodéOS forums - these forums are for supporting /e/OS.
Good luck, and have fun
1 Like
Hi @petefoth , so much good information in your neat answer, thanks a lot.
I’ll begin with 17.1 ROM. My priorities are perfect phone call and SMS, battery efficiency, compatibility with bank apps. Up to date apps thanks to f-droid and aurora, I don’t care about other stores.
(Tempted too by your bleeding age ROMs, if I can test enough to be confident in phone call reception sturdiness.)
Thanks again for kind help.
A short report of my tests.
Lineage 20 based ROM : not extensively tested because of the camera app still being limited to 8MP.
I’ll stay on 17.1 with stock camera. I hope EOL is not too close yet. At least until lineage camera is improved. Only one flaw found : bluetooth crashing after re-entering TWRP (not required one ROM is flashed, it was just to better understand the tool, so easy fix : don’t do that). I read you had same bug once.
Thanks again.
I have uploaded the latest official Android 10 / Q build - which has the stock Sony camera, as well as /e/'s OpenCamera fork - to AndroidFileHost
https://androidfilehost.com/?fid=4279422670115732504
You can always find the latest builds for lilac in this AndroidFileHost folder
Here’s a new CUSTOM build made from the v1.10s tag. (See here for information about build types)
https://androidfilehost.com/?fid=4279422670115735398
Like previous builds, the reason it is CUSTOM rather than UNOFFICIAL, is that in this build it is possible to use Trebuchet as the default Home / Launcher app. If you clean flash the build, you will be offered a choice between Trebuchet and Bliss at the end of first time setup. This was achieved by changing two lines of code, (shown in the patch in my earlier post).
I have clean flashed the build and it seems to work: the test phone boots up fine, internet access via WiFi work, fingerprint scanner works. I’ve not tried calls SMS and mobile internet because I don;t currently have a spare SIM lying around. But there’s not reason why it shouldn’t work
It should dirty flash OK over previous unofficial and custom S builds, but - as always - use at your own risk.
Release notes not yet available for 1.10 builds but they should be here soon
And here is the latest official dev build e-1.10-q-20230416280390-dev-lilac.zip
1 Like
Latest official v1.11-r-dev and custom v1.11-s builds now available at AndroidFileHost
Official version:
https://androidfilehost.com/?fid=10620683726822056115
When I did the OTA update over v1.10-r-dev, the Settings app kept stopping and I had to do a factory reset. That was probably my error - I am constantly swapping bewteen different ROMs and Andrid versions on my test phone - but probably worth backing up your apps and data before flashing or applying the update
Custom version
https://androidfilehost.com/?fid=10620683726822056114
I dirty flashed this over v1.11-r-dev and everything worked fine, but…
This has the latest changes from the upstream unofficial LOS build so it may include “smart charging”, and the other goodies in the latest release of that ROM, but I’ve not tested them.
/e/OS release notes for 1.11 are here
Have fun
Hi,
I’m totally new to Android (from iOS). Bought an XZ1 Compact a few weeks ago and it finally arrived not too long ago. Been mulling over what to do with it. At first I thought I’d try it use it out of the box as is by manually disabling google’s analytics stuff but after messing with it for a bit I got tired of it. It’s a Docomo branded phone from Japan so it came with a ton of their unremovable bloatware on it.
I’m interesting in using /e/OS but I’m not sure where to start. As I’ve said I only have experience with non-jailbroken iPhones so this is a new world for me. I could use some help getting pointed in the right direction as far as installing one of these builds goes. Out of the box my phone is running Android 9 and it doesn’t look like I can update it higher.
What do I need to do to start the process of installing /e/OS on this thing? Sorry if this isn’t the right place to ask.
1 Like
Right now I appear to be stuck in the bootloader phase. My device’s status is
BOOTLOADER UNLOCK ALLOWED: NO
https://www.youtube.com/watch?v=eQrAVqZPDJU
Seems like I can change that using a tool called qUnlock Tool, but I’d have to pay money for it. Has anyone else used or have experience with this tool and is reputability? The site for the tool also wants me to put my IMEI in, but I dunno if it’s safe to do that or not.
edit: After reading around a bit more it seems like the Sony Xperia XZ1 Compact SO-02K Model is rather notorious for not having any easy ways change the bootloader unlock allowed from NO to YES without putting your faith in a sketchy looking closed source program you have to pay for. What are my options? I can return the phone. For now I’m just going to wait for a second opinion because this is clearly way too advanced for someone of my Android experience to be looking into without guidance and I don’t want to do something stupid that will brick the phone.
This phone is basically worthless to me if I can’t get /e/OS or some other custom ROM put on it. I really hate the out of the box Docomo Android experience, and probably the out of the box Android experience in general. Wouldn’t imagine tamping down the spyware on something like a Pixel would be much less of a headache.
As far as I know, the Docomo XZ1 Compact (model number SO-02K) is a different model - made for the Japanese market - from the normal XZ1 Compact (model number G8441).
I don’t know whether /e/OS builds (either this build or the official Android Q build), or the unofficial LineageOS builds on which /e/OS is based, will even work on your model. So I’m sorry I can’t help.
Best to ask in one if the XDA forum threads for this device: https://forum.xda-developers.com/f/sony-xperia-xz1-compact-roms-kernels-recoveries.6930/
Hey thanks for the quick reply. As far as I’m aware there are 3 different models of the XZ1C.
- SO-02K was the one sold in Japan through Docomo, some even with Docomo branding on the back. Apparently it lacks NFC according to one website?
- G8441 I think was the North American model whose fingerprint scanner didn’t work for reasons. (Does it work when putting a custom OS on it like Lineage or /e/?
- G8442 was a planned model that was going to have dual SIM support but apparently it got cancelled at the last minute. Shame.
- D5503 is a model that is incorrectly listed on GSMarena. That’s a model of the Xperia Z1 Compact. So actually there’s only 2 real models.
Given all of this headache I think I might just return this one and buy one with a permissable bootloader. It’d save me 25 bucks. What do you think? I might try asking around on XDA tomorrow as well. Wish I had known about all of these model difference shenanigans before putting down the money though.
https://www.phonemore.com/compare/phones/sony-xperia-xz1-compact-g8441-vs-sony-xperia-xz1-compact-so-02k/7006911
Maybe this will shed some light. They’re both Lilac, I can see that at least.
Following @petefoth’s earlier advice I found https://forum.xda-developers.com/t/can-xz1-compact-so-02k-run-custom-roms.4261539/ – might be worth a read before you decide to RTS.
As far as various models I consulted https://storage.googleapis.com/play_public/supported_devices.html and found
Retail Marketing Name, Device, Model
Branding,
Sony, Xperia XZ1, 701SO, 701SO
Sony, Xperia XZ1, G8341, G8341
Sony, Xperia XZ1, G8342, G8342
Sony, Xperia XZ1, G8343, G8343
Sony, Xperia XZ1, SO-01K, SO-01K
Sony, Xperia XZ1, SOV36, SOV36
Sony, Xperia XZ1 Compact, G8441, G8441
Sony, Xperia XZ1 Compact, SO-02K, SO-02K
1 Like