yashsingh1/xdaforums huggingface dataset:
[Xperia Z1 Compact Android Development] multiwirth:
Oh thanks for the quick reply,

It's actually set to balanced, changing it to efficient will limit the max. cpu clock just like it does on my oneplus 3t.

However 2 cores min still online.

On my HTC One M8 this won't take any effects at all

Will have a look at the sources and compare if i find any differences but probably tomorrow, since you have a build manifest it should be too easy to make my own build then and test :D

Maybe also taking a look at stock, haven't taken a look on it just prepared to unlock.
[Xperia Z1 Compact Android Development] traegr:
Hi, this might be outdated and not to hijack secc's post but I would love that step by step guide. :p

I want to revive my old Z1 Compact and will be installing this ROM (but no rooting) for the first time. (coming from stock ROM Android 5.1.1 Build 14.6.A.1.236). So far I have downloaded the adb and flashboot and also the TWRP recovery. Haven't unlocked the bootloader yet but that will be next step. I don't plan to do a backup because it's just stuffed with so much bloatware and the data (pictures, videos, etc) isn't all that important so I'm willing to wipe that all.

What do you mean by sd or no sd? I do have a micro sd where I stored my pictures (I'm not sure if they are apps but I don't think so?) but I also have a brand new, unused micro sd card? Could you maybe help me out? Thanks!!
[Xperia Z1 Compact Android Development] 115ek:
Check this older thread. There you'll find Installation Instructions in the OP.

I'd suggest you to use this TWRP.

If you want gapps (optional):

But the most important part is unlocking the bootloader. Everything else is pretty straight forward. There are enough guides and instructions. When in doubt - ask. ;)
[Xperia Z1 Compact Android Development] traegr:
Thanks for the quick response!

The TWRP I should get is the 3.4.0-1 right?

I did come across that thread before, but I guess I still couldn't take the plunge to unlock the bootloader haha (will def do it this weekend when I have all the time for it).

I guess with all the different tutorials from different timelines, I couldn't make up my mind whether I wanted/needed to do a TA Backup (which requires rooting - but I do want to use the phone daily and would require banking apps and can't risk them not working). On the other hand, do I really need the DRM keys? I don't use Spotify and my warranty is long over lol. Or are there other functions to the DRM? (Sorry, super newbie here, and possibly for the off-tangent question)
[Xperia Z1 Compact Android Development] 115ek:
Right.

Just follow the official sony instructions for unlocking the bootloader.

Forget about the DRM keys. It's mostly historical. Earlier, they were necessary to be able to use some special camera functionalities for example. But that isn't necessary anymore. Everything works without them.

You can use netflix and spotify just fine. Banking apps may require installation of gapps as some of them use some checks depending on playservices. But I haven't experiences with that. I'm not using banking apps. Just give it a try.
[Xperia Z1 Compact Android Development] traegr:
Right so I unlocked the bootloader and tried following all the instructions here and after flashing the twrp, it had an OKAY response with the finished time, I did the "fastboot boot TWRP.img" part the phone booted and got stuck on the SONY logo and then USB connection malfunctioned and windows doesn't recognize it and is now listed as Unknown USB Device. I tried updating the drivers but failed.

What have I done wrong, and how do I fix this? Thank you in advance!

Edit: Was it because I failed to insert a SD card?
[Xperia Z1 Compact Android Development] 115ek:
fastboot boot is not working with every recovery image. But why do actually need it?

If you flashed the recovery.img to the recovery partition you can just power off the phone and enter the recovery mode directly. Maybe check these instructions from my old TWRP thread.

It has nothing to do with sd cards ;)
[Xperia Z1 Compact Android Development] traegr:
I guess I was just trying to follow the instructions to a T ....

Well but the phone is now still stuck on the Sony logo and pressing the power button (or any other key combination) doesn't seem to shut it down
[Xperia Z1 Compact Android Development] 115ek:
Remove the battery :p

Joke aside: How long did you press the power button? Try holding Vol+ and Power for several seconds (until device turns off). At least that's what I remember darkly.

My dev device indeed has a open backside so I just pull the plug if something goes wrong. But you should achieve the same with a key combination.

Edit: several seconds could also mean 10 secs or so...
[Xperia Z1 Compact Android Development] traegr:
Found the hidden force shutdown button next to the sim insert - forgot all about it until I looked at the manual again. Your method(s) work too of course ;)

But good news! LineageOS17.1 is now successfully installed. Thank you for all your patience and in answering my questions.

:D
[Xperia Z1 Compact Android Development] 115ek:
New build is up. It is also being shipped as ota update.

All october framework security patches were actually already applied before. So this is just a string update shown in the settings. More info here.

07.10.2020

synced LineageOS sources (security patch level October 05, 2020)
[Xperia Z1 Compact Android Development] traegr:
It took me a couple of days to find out but I realize when my phone has been on deep sleep (wifi and mobile data disabled) my alarm clock rings two minutes later than the set time and hitting the snooze is in reference to that time instead of the original time. For example, alarm at 5.30, it rings at 5:32 and snooze would make it ring at 5:42 instead of 5:40 (as I'm used to with other alarms but who knows that might just be the new snooze function). It seems to only happen when the phone has been on sleep a long time bc when I tried reproducing it in the day and it rings on time. Is it a bug ?

Edit: Redundant question about the update build :P
[Xperia Z1 Compact Android Development] 115ek:
I'm not aware of such a behaviour and I use the alarm function every morning (also with different performance settings).

I remember an issue in Lineage 16 when alarms fired at random times after they actually should. This was fixed by disabling the battery optimization for the alarm app. But it's disabled now by default as consequence.

I'll keep my eyes open the next days.

Is it the same delay every time?
[Xperia Z1 Compact Android Development] traegr:
At first I thought I just slept through the first minute while it rang but the later snoozes seem to indicate that it 'moved'. I have to observe for a few more days and will report back.
[Xperia Z1 Compact Android Development] traegr:
So my bad... the alarm has been ringing on time whether on deep sleep or otherwise so I don't think there's a bug. Though if the snooze is hit a few minutes later , the point of reference is no longer the original time but from the time the snooze is activated.
[Xperia Z1 Compact Android Development] 115ek:
Good to hear it was your bad. :)

Concerning the snooze function: This totally makes sense. Think about what would happen in case your "snooze time" is shorter than you wait to hit the snooze button. You'll end up in an undefined state where the new alarm will be in the past. And that doesn't make sense to be honest.

Just a short example: Your default snooze time is 5 min, your alarm fires at 6:00. If the point of reference for the snooze would be the original alarm time now and you enable snoozing at 6:06 (because you weren't able to find your phone for 6 minutes or whatever...) the snooze alarm would be set to 6:05 which lies in the past. That's why the time of disabling the alarm / enabling the snooze is taken as reference.
[Xperia Z1 Compact Android Development] traegr:
Yes I agree with you that it makes way more sense. My old phone with stock ROM did it the other way, which meant less sleep if you hit the snooze a couple minutes before the 'snooze point' :eek:

Off-tangent, I saw that booting into recovery doesn't take me into the TWRP Recovery (I thought of making a backup now that I downloaded all the other apps I want) but the one from Lineage. It has 'factory reset' but no backup and/or restore.
[Xperia Z1 Compact Android Development] 115ek:
Did you enable the update recovery switch in developer options?

That's the first thing coming to my mind...

When enabled, a system update will also replace the recovery.

EDIT: I'm going to include an inbuilt back-up solution for testing purposes soon...
[Xperia Z1 Compact Android Development] traegr:
Yeah, it was enabled. Didn't notice it the first time around.

:D
[Xperia Z1 Compact Android Development] 115ek:
Calling out for fearless testers

A new feature called seedvault is making its way into LineageOS. It's still under development but I thought it could be nice to check it out already.

Integrating it into LineageOS needs some more testing - so let's do our part ;)

Seedvault is a backup application directly built into the system. It allows encrypted backups which can be stored in various locations ranging from SD card over USB drives to cloud storages like nextcloud. Please have a look here for further information: https://calyxinstitute.org/projects/seedvault-encrypted-backup-for-android.

Please be aware this build is for testing purposes! It won't reach via "normal" OTA updates yet. You need to act if you want to test it.

If you encounter issues during testing please report here or directly open a ticket here and attach logs.

Don't get confused by the "Please file a bug if you see this!" text ;)

As I already said: work-in-progress.

If you now really want to test you've got 2 options:

Download and install it manually. The build is also signed and can be dirty flashed.

Option two: Switch to the testing channel and get it via OTA update. Therefore you have to edit the /system/build.prop:

Enable adb and root over adb.

Connect device.

adb root

adb remount

adb shell nano /system/build.prop

change

lineage.updater.uri=https://raw.githubusercontent.com/115ek/OTA/lineage-17.1/amami.json

to

lineage.updater.uri=https://raw.githubusercontent.com/115ek/OTA/test/amami.json
[Xperia Z1 Compact Android Development] 115ek:
New build is up. It is also being shipped as ota update.

08.11.2020

synced LineageOS sources (security patch level November 05, 2020)

Seedvault is included officially now (inbuilt backup solution)
[Xperia Z1 Compact Android Development] 115ek:
If someone wants to have a look on Lineage 18: here you go

Please consider this as an early preview. Known problems so far: broken camera.
[Xperia Z1 Compact Android Development] jho55:
The bad font rendering from 17.1 is gone in this build.

https://xdaforums.com/showpost.php?p=82417295&postcount=91
[Xperia Z1 Compact Android Development] -FancyUsername-:
You are a god
[Xperia Z1 Compact Android Development] Guffiuk:
Hi

Recently rooted my Z1compact via twrp and magisk. Phone is now running well on the latest build 20201108. Only thing I found is that I couldn't send a .Apk file to it, other files works well from a standart Z1c and samsung tablet.

Is this a Android 10 "feature" or Lineage OS?

Thanks
[Xperia Z1 Compact Android Development] 115ek:
What do you mean by sending? Sending via bluetooth? Copying over usb?
[Xperia Z1 Compact Android Development] 115ek:
New build is up. It is also being shipped as ota update.

18.12.2020

synced LineageOS sources (security patch level December 05, 2020)

Important note:

Encryption AND usage of gapps may cause problems. This is a problem affecting many legacy devices that use full disk encryption (FDE). More details here.
[Xperia Z1 Compact Android Development] IJK_CZ:
Hello,

Any solution to change SD card camera destination .../Android/data/org.lineageos.snap/files , which cannnot be viewed in Gallery app?
[Xperia Z1 Compact Android Development] 115ek:
You can no longer store images on the sdcard with snap (the default camera app). This feature is broken and got removed. Check this for more details.

You may use OpenCamera or save to internal memory and copy it to the sdcard manually. Or the best option: Fix the "save to sd card" feature in snap and push it to gerrit. I guess you would make many people happy. :)
[Xperia Z1 Compact Android Development] MSe1969:
2nd build variant "hardened microG build" now available

Hi all,

similar to the LineageOS 16.0 thread, which is operated by @115ek together with me, we are now also offering the 2nd build variant of the "hardened microG build" for LineageOS 17.1 - download link here:

https://sourceforge.net/projects/lin17/files/amami/LineageOS_17_signed/lineage-17.1-20201219-UNOFFICIAL-microG-signed-amami.zip/download

For those of you using this "microG" build variant already for LineageOS 16.0, you can simply "dirty-flash" it over the LineageOS 16.0 "microG" build.

Features of this 2nd build variant:

Pre-installed microG and F-Droid same as the LineageOS for microG project

Pre-installed AuroraStore

eSpeak TTS engine (FOSS TTS solution)

Bromite as default browser

Additional security hardening features listed below

Cloudflare as default fallback DNS (instead of Google)

Privacy-preferred default settings

Optional blocking of Facebook- and Google-Tracking (Settings - Network & Internet)

Optional disable captive portal detection or choose from various providers (default is GrapheneOS and not Google; Settings - Network & Internet)

Increased max. password length of 64

No submission of IMSI/phone number to Google/Sony when GPS is in use

Default hosts file with many blocked ad/tracking sites

Privacy-enhanced Bromite SystemWebView

Extra control of sensor access for additionally installed user apps (Special access under app permissions)

Firewall (control internet access per app - under Trust)

Constified JNI method tables

EDIT: Sec. string 2020-12-05

@115ek :

Please adapt the OP of this thread accordingly - thanks!

(Unfortunately, the "contributor feature" is gone with the new forum software, I would have loved to get more useful features taken over . . . - nobody e.g. needs this useless "Topics" waste of space on the left-hand side...)

Cheers, M.
[Xperia Z1 Compact Android Development] J_C_D:
Just installed it and it feels gorgeous! Thank you!!!

One question: Is it possible to get the camera button working again like it worked in the Stock ROM? i.e. directly open the Camera app meanwhile the device is locked.

I do also have another problem: it seems that photos taken by the Camera app cannot be deleted again by the Gallery app. I'll investigate that further.
[Xperia Z1 Compact Android Development] J_C_D:
Btw., am I right that microG core in this build cannot be updated by F-Droid?

If so, will you do another build with an updated microG core 0.2.16?
[Xperia Z1 Compact Android Development] MSe1969:
The answer is "yes" for both questions. With each monthly release, I also update, if applicable, the microG stuff.
[Xperia Z1 Compact Android Development] 2faraway2:
I flashed it dirty over the last MicroG Android 9 build, congratulations for a very, very smooth update possibilty (y):)(y)

Just two small things:

- I would recommend to flash Magisk together with the V10 build, else Magisk is gone (the Magisk survival script doesn't work in this constellation)

- Max front camera resolution for video recording seems to be 1600x1200 ? At least this is what camera2 probe reports.

But our devices support 4K video recording with the front camera, which is imho 3840x2160 pixel

This may cause video recording apps not to support the max size ..

Anyway, a huge thanks for this A10 build which is almost nearly perfect :-)
[Xperia Z1 Compact Android Development] J_C_D:
Ok, it's a bug in the Gallery App itself. So let's hope that it's already fixed upstream and the fix will be contained in your next build :cool:
[Xperia Z1 Compact Android Development] zeec:
After installing 18.12.2020 ota update:

When i try to check for updates "the update check failed. Please check your internet connection and try again later.

Mobile data&wifi works.

Flashlight is greyed out, nothing happens when i try to press it.

When i have sensors off camera app crashes/wont start at all, works when i have sensors on. camera worked on previous update while sensors were off.
[Xperia Z1 Compact Android Development] 115ek:
Which version are you using? Standard or microG?

Concerning the update check: I guess the new repo containing the OTA update information isn't setup yet. It'll be if the next update rolls out. This will also be announced here. Please report back if it doesn't work for you after this.
[Xperia Z1 Compact Android Development] zeec:
Standard, can i switch over to microg in recovery without ADB/SD card?
[Xperia Z1 Compact Android Development] 115ek:
Yes. This is possible. The easiest approach would be a clean flash.

Download the microg version and save it in the internal storage (should be stored in downloads of internal storage by default)

Reboot to recovery

Wipe /cache, /data, /system

Install the .zip from /sdcard/Download (if you downloaded it to the Download folder...)

reboot

This, however, would lead to loosing your data (installed apps, wifi keys, ...). Your internal storage (pictures, media, etc...) will stay untouched.

You could also switch between buildflavours without wiping /data. Please check this thread, especially the point Switching between build flavors.

This requires some more work, though.

@MSe1969 The instructions should be still usable, right? Except that YalpStore is Aurora now...
[Xperia Z1 Compact Android Development] MSe1969:
Correct!
[Xperia Z1 Compact Android Development] J_C_D:
It may be a stupid question, but why is it not possible? Shouldn't microG core be updateable like any other system app?

Is there a way to allow updating by F-Droid?
[Xperia Z1 Compact Android Development] 115ek:
Android apks need to be signed with a developer's key. For the first installation of an app this signature doesn't matter. However, if you want to install an app with the same package name (typical update scenario) the android package installer checks if the apk was signed by the same key as the previously installed. If the signatures don't match, the installation aborts.

That way you can prevent installing non-trustworthy updates (you have to trust the first package signature anyway...).

All apps found in fdroid are signed with fdroid's keys. The microg apks published on the microg website are signed with some microg keys (and also the ones provided in the microg fdroid repo). And as we also build microg from source - you can already imagine - the packages are signed with our keys.

Building microg from source has a historical background. When we started, microg was lacking some commits. Making all things working correctly required applying own patches. Nowadays, the microg maintainer (@MaR-V-iN) is back in the game and these things are merged upstream. However, switching back isn't simply possible as the signatures differ. The only way (I currently know of) would be a manual deinstallation of the affected packages. In connection with OTA updates this is really tricky.

So if you want to update microG from fdroid, you have to remove the existing microg installation. But then any further OTA update will break ;)

Anyway: We provide builds every month including google's monthly ASB's. I think that's an acceptable timeframe. As this also happens as OTA update, there isn't a huge effort for you.

Once we stop the builds (as happened with 15.1 already), you could simply use the "original" microg to be able to update it further.

EDIT: Please have a look at the post below by @MSe1969 for more details. He's the one behind all the microg related stuff in our builds.
[Xperia Z1 Compact Android Development] MSe1969:
The answer is more complicated. Originally, I was using the original apk (which means: updatable via F-Droid), which - about more than 7-8 months ago hadn't received any updates since long and due to developments by Google in the FCM area, more and more issues with apps depending on Google functionalities have occurred, when these apps were updated.

So I decided to switch to the /e/ fork, which has temporarily solved a lot of issues, as it was addressing these issues.

When the original microG started to be very actively maintained again some months ago, I decided to switch back - however, I have learned the hard way, that the switch isn't that trivial in fact:

Different apk signature means to factually deinstall and reinstall the app during a ROM update. The /e/ fork has FCM enabled by default, so all app registrations have "survived" the switch, despite microG app data being purged during switch. But the original microG apk has FCM disabled by default! This means that during a switch (ROM with different apk signature flashed), all FCM registrations of apps with respective dependencies would get lost! In that case, it is unfortunately not always possible to simply re-enable it - for specific apps, that would mean having to even reinstall them!

Therefore I build microG myself with a patch to have FCM enabled by default.

Further, often, I could ship a microG having already further commits than the official release and releases have appeared ~every 2 months. Only very recently, the release frequency seems to have become monthly. So in the past, you could even benefit from developments for EN api as part of my monthly ROM release, before they were officially available...
[Xperia Z1 Compact Android Development] J_C_D:
@MSe1969, @115ek, @MaR-V-iN (and many the others)

THANK YOU for your work!
[Xperia Z1 Compact Android Development] MSe1969:
New builds available with January 2021 ASB patches

Hi all, new builds are available for download and also offered as OTA update:

A. Standard LineageOS 17.1 build

https://sourceforge.net/projects/lin17/files/amami/LineageOS_17_signed/lineage-17.1-20210114-UNOFFICIAL-signed-amami.zip/download

ASB Security string 2021-01-01

Kernel slightly upstreamed

System Webview: Fix of persistent histogram bug (eating space in some cases)

B. Pre-installed microG build variant with additional security patches

https://sourceforge.net/projects/lin17/files/amami/LineageOS_17_signed/lineage-17.1-20210114-UNOFFICIAL-microG-signed-amami.zip/download

ASB Security string 2021-01-01

Bromite Webview on 87.0.4280.131

Updated microG from upstream to 0.2.16.204713-10 (picked until 2f29b93)

Updated F-Droid to 1.10-alpha1-212

Happy flashing!

@115ek :

Please update the changelog. Further, if your previous build still points to "your" OTA repo, you would need to copy the amami.json file from our org. to your repo as a one-time activity.
[Xperia Z1 Compact Android Development] 115ek:
Done.

I should have adapted it in the last build already.

If someone can't find this update in the OTA updater: please report here. We'll give a quick instruction how to fix that. We could also fix that for you ;)
[Xperia Z1 Compact Android Development] tramp20:
On two phones OTA does not find the update 14.01.2021. But no problem, I can flash it.
[Xperia Z1 Compact Android Development] 115ek:
Thanks for reporting. I tracked down the problem. The build property ro.lineage.releasetype changed from UNOFFICIAL to UNOFFICIAL-signed.

As the updater checks for this property, you won't see the new OTA update if you're on my 20201218 standard version.

EDIT: This should be solved now automatically. No need for further user interaction.

There are 2 ways now to handle this:

1. Downloading the newest build manaully and dirty flash it. All further OTA updates are going to work then.​

​

or

2. Change the build property manually and download the update via inbuilt OTA updater. All further OTA updates are going to work with this method as well.​

enable adb and root over adb in developer options

connect device to PC with adb installed

adb root

adb remount

adb shell

nano /system/build.prop change ro.lineage.releasetype from UNOFFICIAL to UNOFFICIAL-signed

reboot

after restart check for updates again

Sorry for the inconvenience.

@MSe1969 Are you aware of a simpler way?