yashsingh1/xdaforums huggingface dataset:
[Xperia Z1 Compact Android Development] dmbdd72:
Thanks for your hard work.

Coming from 15.1 I have no real problems with dirty-flashed test build one week ago. Only Magisk was lost and had to be re-flashed.

I use this device as my daily driver and I am amazed about battery life. It's great! I hope to see regulary updates soon.
[Xperia Z1 Compact Android Development] MSe1969:
Hi all,

another LineageOS 16.0 Test build for the "microG" build flavor with February 2020 sec. patches is available:

https://sourceforge.net/projects/li...9-UNOFFICIAL-microG-signed-amami.zip/download

It will also be offered via OTA update, if you have already flashed the previous one.

From next month onwards, there will be both build flavors in our Lineage 16.0 Thread

Regards, M.
[Xperia Z1 Compact Android Development] 2faraway2:
[MENTION=7929484]MSe1969[/MENTION]:

first of all thanks a lot for your great work so far :)

I would like to be one of the first guys to test the new 16.0 MicroG build.

Would you give a short advice how to flash 'dirty', means your newest 16.0 MiccorG build over the lastest 15.1 MicroG build.

I assume that wiping cache,dalvik and system would be be required while preserving data should work, right ?

And I also assume that TWRP and Magisk will survive the flash, right ?

Thanks in advance for a short hint ;)
[Xperia Z1 Compact Android Development] MSe1969:
Hi,

all steps are described in this post (#264), just scroll back ;)

Regarding Magisk, I am not sure - Magisk normally uses a "survival script", but as said - not sure in this specific case.

Cheers, M.
[Xperia Z1 Compact Android Development] 2faraway2:
Thanks for your hint ;)

The update worked like a charme. I came from 15.1 (also encryted in 15.1), made a dirty flash, all data and configurations 'survived'. I just lost Magisk, but that wasn't a big challenge to reflash it.
[Xperia Z1 Compact Android Development] MSe1969:
EOL

Hi all,

as already announced and discussed before,

this thread is now EOL.

Please visit our LineageOS 16.0 thread, where new LineageOS 16.0 builds for both flavors with March 2020 ASB patches have been published.

If not yet done, we recommend to upgrade your OS, as decribed in post #264 :

Update TWRP to the version from this thread

Make a nandroid backup with TWRP and make a backup of the Internal memory (both steps are important, don't skip them!)

Your device is not encrypted or you have encrypted it using

LineageOS 15.1

? => Easy: Dirty-flash (or clean-flash) the LineageOS 16.0 test build and all good.

Your device has been encrypted with a cm-14.1 build? Or you are already in the situation that the LineageOS 16.0 build tells you it can't decrypt? => Follow the steps below exactly as described.

Boot into TWRP and

format

the /data partition

Reboot into TWRP

Install the latest LineageOS 15.1 build (with your build flavor) and boot into an empty system (don't restore anything,yet!)

Encrypt the device now - it'll take only a couple of seconds until the device reboots - wait for the reboot to finish

Restore now the Internal Memory and reboot to TWRP

if you want to "dirty-flash", restore the nandroid backup now and afterwards, still in TWRP,

flash the LineageOS 16.0 build => done, finally

Please post any questions, you may have in regards to migrate/upgrade to LineageOS 16.0 in our LineageOS 16.0 thread!

We would like to thank you for your interest in the LineageOS 15.1 builds for the Xperia Z1 compact and hope to see you all in our LineageOS 16.0 thread.

Kind regards,

[MENTION=8036586]115ek[/MENTION] and [MENTION=7929484]MSe1969[/MENTION]
[Xperia Z1 Compact Android Development] MSe1969:
Both links work for me, and mirrors are found. Can you try again?

In the past, I have also experienced sometimes temporary issues with AFH; wait and try again helped eventually . . .
[Xperia Z1 Compact Android Development] Royal.Bengal:
Just tried now, working. Thanks
[Xperia Z1 Compact Android Development] MSe1969:
Some additional comments about Xposed from my side, @ [MENTION=7475468]CyanoFriend[/MENTION]:

- On some other Non-Oreo devices (e.g. when I use the cm-12.1 ROM for the amami device), I myself use Xposed for the Xprivacy (or the successor Xprivacy-Lua for Nougat) module.

- With the exception of this module, I tend to agree to be very careful, what you do with Xposed

- As already explained by [MENTION=8036586]115ek[/MENTION], we can't help if the issue is related to Xposed

- Xposed is still in beta state regarding Oreo, that is why I don't use it in Oreo any longer

- In my case (as I was using Xprivacy before), I have included and improved privacy enhancements, which I found in different places into the "microG" build flavor
[Xperia Z1 Compact Android Development] lm089:
Just a quick but big THANK YOU for your work. Performance and esp. endurance is really impressive: I'm back at over 3 days between charging sessions, didn't have that since I left munjeni's 14.1 ROM. And sometime a get an extremly quick GPS fix :good:
[Xperia Z1 Compact Android Development] lm089:
Sorry if the following is somewhat awkward or plain stupid but I have to admit that didn't quite get the implications of a "signed" build; so I think I better ask:

I'm currently running the "plain" LOS version of this ROM; before that it was the current AICP Oreo version. Yesterday I by chance saw that the kernel installed on my phone is marked as

[B]3.4.0-aicp-[/B]<some_key_etc>
android@localhost #1
Sat Dec 29 12:58:05 CET 2018

Q1: Not that I think that it makes any difference, but is this the kernel that's coming with your firmware? Or is it just a remainder of my previously installed firmware?

Q2: Anyways, this made me think about what would happen if I tried to install a totally different (compatible) kernel. Would there be some sort of conflict with "your key" / signature? Or is there no connection whatsoever between kernel and the signed firmware?

Please don't hesitate to point me to whatever wiki etc.; never too old to learn ;)
[Xperia Z1 Compact Android Development] lm089:
Thanks a ton for this very comprehensive post! Helps a lot to understand.

Are you talking about phone encryption (from settings >> security >> encryption >> encrypt phone)? Or is this something different?

In fact I did not encrypt /data (not feeling too well about it), mainly because in the past I had quite a few problems with an encrypted adoptable storage partition on my SD card, especially from within recovery. I know (or assume) that this is something different here. I'll have closer look into that.
[Xperia Z1 Compact Android Development] MSe1969:
Yes, I am exactly talking about that in conjunction with a "strong enough" PIN/password (unfortunately, under LineageOS 15.1, such nice apps like Snooper stopper allowing you to have a very strong startup password combined with a short lockscreen PIN don't work any longer). That is the best protection against loss and/or misuse of your phone (forget about the "remote wipe your device" BS offered by G* or various "snake oil" companies)

Fair enough, adoptable storage has got its issues (I first liked this idea, but after having read about all the side effects, I tend to recommend refraining from it).
[Xperia Z1 Compact Android Development] 115ek:
Does someone know if stock rom supports stereo FM?

I've read in an other forum that FM only works in mono mode on our firmware. I just verified this on my own by using audacity.

We have two channels, but both with the same signal.

I just want to be sure stereo is supported by the hardware before getting deeper into it and search for reasons.
[Xperia Z1 Compact Android Development] marsa47:
I am currently using Spirit FM app on a 5.1.1 ROM and it does work in stereo. The hardware is stereo for sure. There is one thing though. Spirit FM has many options, and can be set to "digital" or "analog" mode. When set to digital, the sound quality is way worse and the stereo sound may not be achieved. In analog mode the sound is way better and the stereo is very clear.

The FM on the Z1c is one of the most important features for me, that's why I use an older android. This LineageOS 12.1 from MSe1969 is the latest android with all working FM including Spirit FM support. Later Roms all give me an "incompatible kernel" error in the Spirit FM app.

Audacity screenshot
[Xperia Z1 Compact Android Development] lm089:
:D

Yes, I remember that Sony's latest stock used to have stereo FM. Back then I was frequently tuning to "Heute im Stadion" (live soccer broadcasts) on public radio, therefor I remember quite well. Unfortunately there was no FM radio support at all in munjeni's LineageOS Nougat port. Until your post I wasn't even aware that FM support is back! :D
[Xperia Z1 Compact Android Development] 115ek:
Well, it looks like real stereo in the beginning. But you can check it definitely by substracting both tracks...

You have to:

duplicate the signal

invert the first signal

split the first signal

split the second signal

remove left track from first signal and right part from second signal

combine signals to stereo again

downmix to mono

listen

If you can't here anything --> mono. Else: stereo.

Is stereo also possible without Spirit? With the inbuilt Cyanogen radio player?
[Xperia Z1 Compact Android Development] marsa47:
Just tested as you advised. SpiritFM = true stereo. Stock app plays mono, no matter what (good reception, etc).
[Xperia Z1 Compact Android Development] lm089:
Out of curiosity I just tested fm radio on my Xperia tablet Z (SGP311) running LineageOS 15.1 OFFICIAL. As the device is of similar age as our Z1c there's probably a chance that both are equipped with the same or similar hardware. We'll, maybe not, just a wild guess.

Anyways, FM reception on my tablet is excellent, and in stereo. I also realized that the radio apps are different (somehow I had expected to find the same app on both devices):

LOS 15.1 OFFICIAL came with com.android.fmradio V 2.0

This ROM here installed com.caf.fmradio V 8.1.0 instead.
[Xperia Z1 Compact Android Development] fidi_h:
Fragile GPS

First of all, many thanks for keeping the Z1c alive. I'm using this rom instead of the Lollipop from MSe1969 for daily use.

The only problem I recognised, is a complete loss of GPS functionality after a few days (about 5 - 6). That happened two times up to now.

The only way for me, to get GPS back to work is to:

backup my device via TWRP to SD card

restore the stock rom

get GPS back to work by using it somehow

flash TWRP

restore the backup

There seems to be "something" regarding GPS that is not completely handled by your rom. Is there any other known way to "reset" GPS completely than reinstalling the stock rom?
[Xperia Z1 Compact Android Development] lm089:
Cannot not confirm this on my device; I'm using GPS quite frequently in device only mode, mainly for tracking purposes. GPS reception is not brilliant, not halfway as good as it used to be, but that's been true since I moved away from STOCK. To be exact, with this ROM here I'm having the best reception from all custom ROMs I've been using so far.

I'm aware that this doesn't help you really. What I mean is that your experience maybe is not coming from this ROM, at least not only

Thinking about it, what I did was fiddling with my gps.conf file. 115ek here once wrote that this may be snake oil, and he's probably right.

On the other hand you might give it a try; make sure you have a backup of your original conf file.

For this ROM it's the file /system/vendor/etc/gps_debug.conf

I changed the #NTP server section to this:

#NTP server
NTP_SERVER=pool.ntp.org
NTP_SERVER_1=0.pool.ntp.org
NTP_SERVER_2=1.pool.ntp.org
NTP_SERVER_3=2.pool.ntp.org
NTP_SERVER_4=3.pool.ntp.org

Good luck.
[Xperia Z1 Compact Android Development] fidi_h:
Thanks for your answer. My device seems to be special regarding GPS. It's one of the latest produced devices from 23/15, sold by Sprint UK.

If GPS works, its preformance is always great whith each ROM I've tested (incl. stock rom). GPS and GLONASS are supported, a fix never takes longer than about 5 sec. (using A-GPS), tracks are quite accurate.

I had GPS issues with the Lollipop of MSe1969 (and reported there). But only immediate, after flashing updates and than constant. If not, GPS worked rock solid with months of uptime.

I'm always using nearly the same set of apps. So I would wonder, if the installed apps are the reason for the problems. It would be a pity to go back to Lollipop, Oreo performs really great here.

I'll try you gps.conf modifications. I remember doing similar modifications before on lollypop, unfortunately without success. But - who knows ...
[Xperia Z1 Compact Android Development] fred's:
Thank you for this rom. Finally Google is off all my devices and out of my life!

Still on original battery but this rom is like having a new battery fitted compared to stock rom. Easily lasts all day with heavy use.

Only problem I had was touchscreen becoming unresponsive one or two times a day. Since I first replaced the screen I have always had the same issue with custom roms. Fixed by using RZ kernel. I gave that a go because it specified

I don't know if that was the reason but I do not have the problem with this rom and RZ kernel.

Thanks again for your excellent work.

k
[Xperia Z1 Compact Android Development] MSe1969:
New builds with January ASB available

Hi all,

new builds are available with January 2019 security patches:

1. Standard LineageOS 15.1 build

https://androidfilehost.com/?fid=11410963190603899467

(Note: Android System Webview now also updated to M71)

2. Security hardened microG build

https://www.androidfilehost.com/?fid=11410963190603899584

Features of both builds:

Security string 2019-01-05

Various kernel security patches
[Xperia Z1 Compact Android Development] MSe1969:
Glad to read - regarding screen, no idea, but if the custom kernel helps you, cool.

(Maybe we'll find some time to see what was done, but I can't promise anything)
[Xperia Z1 Compact Android Development] foresto:
I don't see any build instructions there. Did I miss something?
[Xperia Z1 Compact Android Development] MSe1969:
Updated: https://github.com/lin15-microG/local_manifests

(That's however the short version only, which is good enough to build on your own.

You may want to look into the LineageOS Wiki or the AOSP build guide to better understand the backgrounds.

The scripts we use to make our builds are stored in the root-scripts and z_patches repo)
[Xperia Z1 Compact Android Development] foresto:
Thanks.

Problem 1, with workaround:

The build fails with the following error:

loadlocale.c:130: _nl_intern_locale_data: Assertion `cnt < (sizeof (_nl_value_type_LC_TIME) / sizeof (_nl_value_type_LC_TIME[0]))' failed

This can be fixed by exporting the environment variable LC_ALL=C. A regional locale setting might work, too, though I haven't tested it. Given that others on the web have also seen this problem, perhaps due to differing national language settings or due to the fact that build containers are not guaranteed to have locale variables set, I suggest adding this step to the build instructions.

Lex: applypatch <= bootable/recovery/edify/lexer.ll

FAILED: /mnt/buildboxext/project/android/makebox-oreo/out/target/product/amami/obj/STATIC_LIBRARIES/libedify_intermediates/lexer.cpp

/bin/bash -c "prebuilts/misc/linux-x86/flex/flex-2.5.39 -o/mnt/buildboxext/project/android/makebox-oreo/out/target/product/amami/obj/STATIC_LIBRARIES/libedify_intermediates/lexer.cpp bootable/recovery/edify/lexer.ll"

flex-2.5.39: loadlocale.c:130: _nl_intern_locale_data: Assertion `cnt < (sizeof (_nl_value_type_LC_TIME) / sizeof (_nl_value_type_LC_TIME[0]))' failed.

Problem 2:

The build fails with the following error:

ACCELEROMETER_ROTATION_ANGLES cannot be resolved or is not a field

From a quick glance, it looks to me like that constant is missing from frameworks/base/core/java/android/provider/Settings.java, though I don't know the code, so I don't know if that's truly the proper place. I found a related changeset here.

ERROR: /mnt/buildboxext/project/android/makebox-oreo/frameworks/base/services/core/java/com/android/server/policy/PhoneWindowManager.java:1089.44: ACCELEROMETER_ROTATION_ANGLES cannot be resolved or is not a field

ERROR: /mnt/buildboxext/project/android/makebox-oreo/frameworks/base/services/core/java/com/android/server/policy/PhoneWindowManager.java:2761.44: ACCELEROMETER_ROTATION_ANGLES cannot be resolved or is not a field

[ 90% 69177/76658] Building with Jack:...l_intermediates/with-local/classes.dex

ninja: build stopped: subcommand failed.

18:36:23 ninja failed with: exit status 1
[Xperia Z1 Compact Android Development] MSe1969:
Thanks for the hint - I was able to reproduce the issue and I have fixed it:

Yesterday, changes in lineage-sdk and frameworks/base, which depend on each other, have been merged by LineageOS. As we have a frameworks/base fork, it was now 2 commits behind, whilst we directly track lineage-sdk from LineageOS. I have now pulled the two commits from LineageOS' frameworks/base repo, so it is in synch again and now it compiles fine. When you pull frameworks/base, you sould be able to compile as well.
[Xperia Z1 Compact Android Development] ohno66:
Hotspot doesn't seem to work over 5GHz band.

I can't see the network on a 5GHz capable PC. Hotspot over 2,4GHz is working.

Has anyone else had success on this?
[Xperia Z1 Compact Android Development] foresto:
Thanks. I was able to complete a build (with the additional export LC_ALL=C step) once you did that. Would it make sense to put known-good revision tags in your manifests, to avoid this kind of problem in the future, and to make sure that people building from source are using the same code that you are?

Also, I'd like to build the microG version. I tried running switch_microG.sh microG, but it produced a bunch of errors. Am I supposed to run some other script instead?

error: pathspec 'lin-15.1-microG' did not match any file(s) known to git.

-

/home/ubuntu/android/oreo/frameworks/base

error: pathspec 'lin-15.1-microG' did not match any file(s) known to git.

-

/home/ubuntu/android/oreo/frameworks/native

error: pathspec 'lin-15.1-microG' did not match any file(s) known to git.

-

/home/ubuntu/android/oreo/kernel/oneplus/msm8996

error: pathspec 'lin-15.1-microG' did not match any file(s) known to git.

-

/home/ubuntu/android/oreo/packages/apps/Camera2

error: pathspec 'lin-15.1-microG' did not match any file(s) known to git.

-

/home/ubuntu/android/oreo/packages/apps/Dialer

error: pathspec 'lin-15.1-microG' did not match any file(s) known to git.

-

/home/ubuntu/android/oreo/packages/apps/Eleven

error: pathspec 'lin-15.1-microG' did not match any file(s) known to git.

-

/home/ubuntu/android/oreo/packages/apps/LockClock

error: pathspec 'lin-15.1-microG' did not match any file(s) known to git.

-

/home/ubuntu/android/oreo/packages/apps/Jelly

error: pathspec 'lin-15.1-microG' did not match any file(s) known to git.

-

/home/ubuntu/android/oreo/packages/apps/Settings

error: pathspec 'lin-15.1-microG' did not match any file(s) known to git.

-

/home/ubuntu/android/oreo/packages/apps/SetupWizard

error: pathspec 'lin-15.1-microG' did not match any file(s) known to git.

-

/home/ubuntu/android/oreo/packages/apps/Trebuchet

error: pathspec 'lin-15.1-microG' did not match any file(s) known to git.

-

/home/ubuntu/android/oreo/system/bt

error: pathspec 'lin-15.1-microG' did not match any file(s) known to git.

-

/home/ubuntu/android/oreo/system/core

error: pathspec 'lin-15.1-microG' did not match any file(s) known to git.

-

/home/ubuntu/android/oreo/system/sepolicy

error: pathspec 'lin-15.1-microG' did not match any file(s) known to git.

-

/home/ubuntu/android/oreo/vendor/lineage

error: pathspec 'lin-15.1-microG' did not match any file(s) known to git.
[Xperia Z1 Compact Android Development] 115ek:
No. You just need to add a

git fetch

before trying to checkout the new microg branch.

Insert after this line: https://github.com/lin15-microG/root-scripts/blob/611203d965cb291cf30e80cc9cc37585e8cc08f5/switch_microG.sh#L7.

[EDIT]: Make sure you insert inside switch_microG.sh located in the root dir. Not the one from /root-scripts ;)

It seems the repo tool doesn't get all branches by default. That's why you can build standard lineage but no microg version.

Concerning the tags: I don't know how many people are building from source. At least one I suppose. ;)

But my intention to build on my own would be getting a very fresh build. So using old tags maybe isn't the right way.

I think there aren't so many problems if you build a standard lineage. Microg can cause more problems because we use forks here.

And it seems you're a clever guy. Fixing one or two things wouldn't be a problem for you :)

But lets wait for [MENTION=7929484]MSe1969[/MENTION]. Maybe he used tags with cm12.1 before.
[Xperia Z1 Compact Android Development] MSe1969:
Hi [MENTION=2359841]foresto[/MENTION] and [MENTION=8036586]115ek[/MENTION],

concerning tags: 100% agree to what 115ek stated already. Besides, tags would technically not solve that issue, as we can't set tags on LineageOS's owned repos.

The repo's in the lin15-microG Organization on Github, which are forked from LineageOS, have two branches - lineage-15.1 and lin-15.1-microG

The lineage-15.1 branch is always supposed to be in synch with LineageOS. All content from LineageOS is pulled, so this branch either shows the status "even with LineageOS" or "<x> commit(s) behind LineageOS". Before new builds are made, the repos are brought in synch.

If you would like to build, and you see that a forked lineage-15.1 branch (and consequently also the lin-15.1-microG branch, at least in most cases) needs an update, you have two options:

a. Either, ping me and wait until the branch is updated

b. Do it yourself :) (see below)

I'll explain it with the example of frameworks/base, but you should do that with all forked repositories.

Step 1 (one time step): Maintain additional remotes

List your remotes:

git remote -v

You should see a result like this:

github	git://github.com/lin15-microG/android_frameworks_base (fetch)
github	git://github.com/lin15-microG/android_frameworks_base (push)

Now add two further remotes:

git remote add origin https://github.com/lin15-microG/android_frameworks_base
git remote add upstream https://github.com/LineageOS/android_frameworks_base
git remote -v

The result now looks like this:

github	git://github.com/lin15-microG/android_frameworks_base (fetch)
github	git://github.com/lin15-microG/android_frameworks_base (push)
origin	https://github.com/lin15-microG/android_frameworks_base (fetch)
origin	https://github.com/lin15-microG/android_frameworks_base (push)
upstream	https://github.com/LineageOS/android_frameworks_base (fetch)
upstream	https://github.com/LineageOS/android_frameworks_base (push)

Checkout the lineage-15.1 branch and enter git pull once. Repeat that step for each forked repo.

Afterwards, also the switch_microG.sh script will work (must be copied to the "root" of your build tree).

Now, to update your repo, in case our forks aren't yet updated, checkout the lineage-15.1 branch and enter

git pull upstream lineage-15.1

To bring those commits to the lin-15.1-microG branch, checkout the lin-15.1-microG and cherry-pick the new commits in the right order.

Regards, M.