EOL [ROM][Unofficial][9.0][signed][OTA] Lineage OS 16.0 for Xperia Z1 compact

[MSe1969]

I already tried that without luck It seems that the creation of the location provider services is very very early at boot (in "system process") and that the RRO engine is not working at this time. I did make sure that the apk is working by overriding a visible marker and can confirm that my overlay apk was working. If I didn't miss something I'm afraid there is no option for this.

Could you please share your AndroidManifest.xml and vour core/res/res/values.xml file, which you have used to create your RRO? And where did you put it and how did you create and sign it?

 

[115ek]

[MENTION=8036586]
I did but unfortunately without success. The framework-res ended up with

<string-array name="config_locationProviderPackageNames">
        <item>com.google.android.gms</item>
        <item>com.android.location.fused</item>
</string-array>

Is it possible for your to have a deeper look? It would be ok if it's impossible. In this case I have to wait until I get some free time again and will dig into building my own ROM.

Umm, okay. It seems the overlay overwrites instead of appending to existing stuff.
I applied this patch now and uploaded a new build.

But don't get so much hope this will ever be merged in lineage. I highly doubt it.

 

[greenflash1986]

Could you please share your AndroidManifest.xml and vour core/res/res/values.xml file, which you have used to create your RRO? And where did you put it and how did you create and sign it?

The source is at github.com/greenflash1986/UnifiedNlpOverlay/ together with the answers of the other questions in the readme. The commented code in config.xml L11 and L12 was my marker for "overlay is working" because this is visible. I already tried a version with "isStatic" in the manifest. Thank you for looking into this.

[...] and uploaded a new build.

Thank you very much! It's working! Atleast Unified was working until I but Gapps on the phone. Digging deeper in the code it seems that there is in fact only one service allowed. Not questioning if this service is enabled or not ... Anyway, the "best" service is based on the "serviceVersion" in the metadata of the manifest in the package... you can have a look at github.com/LineageOS/android_frameworks_base/blob/lineage-16.0/services/core/java/com/android/server/ServiceWatcher.java#L244
One is able to look for possible matching services with

pm query-services -a com.android.location.service.v3.NetworkLocationProvider

.
I will dig deeper in this stuff the next days. Thank you very much for providing me a working image! Would cost me some days to get into building a ROM on my own. Thank you very much!

(PS: had the same problem with the download as 2faraway2. But where successful after some attempts and mirror changes)

 

[greenflash1986]

Hi there,

@MSe1969 did you find something else in the repo I could try?

@115ek thank you veeery much for you build. I figured it out how this thing could work and already created a PR for LOS 16.0 at https://review.lineageos.org/c/LineageOS/android_vendor_lineage/+/295384/2
I will propagate this thing up to 18. if it's accepted.

I will keep you updated.

 

[MSe1969]

Hi all,

I have uploaded new builds for both build variants, they are already offered as OTA updates.

A. Standard LineageOS 16.0 build

https://sourceforge.net/projects/lin16/files/amami/LineageOS_16_signed/lineage-16.0-20201213-UNOFFICIAL-signed-amami.zip/download

• Version string 2020-12-01 (this month, no kernel updates found)
• System Webview on 86.0.4240.198

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

https://sourceforge.net/projects/lin16/files/amami/LineageOS_16_signed/lineage-16.0-20201212-UNOFFICIAL-microG-signed-amami.zip/download

• Version string 2020-12-01 (this month, no kernel updates found)
• Bromite System Webview on 87.0.4280.106
• F-Droid updated to 1.10-alpha1-114
• microG updated from upstream to 0.2.14.204215-15 (picked until 720b089)

As indicated before, I am planning to start providing a respective 17.1 microG build and then stop the 16.0 builds, so @115ek and I would offer only 17.1 builds - more to come soon.

@115ek - right now, with the new XDA forum software and DevDB gone, I am not able any more to edit the OP (have posted a question about that in the respective support thread). So could you please update the change log of the OP accordingly? Thanks!

Happy flashing, regards M.

 

[MSe1969]

@MSe1969 did you find something else in the repo I could try?

Sorry for the late reply, I was very busy work-wise. And no, I did not try myself or found anything.
However, I have seen that you considered already all the points, I could think of and which I would have tried, if they hadn't been mentioned already by you. So it indeed seems to be the case, that the RRO "engine" only comes into effect 'too late' for location providers...

 

[MSe1969]

Lineage 17.1 microG build

I have published now another LineageOS 17.1 "microG" build for the amami device:

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

I'll announce it also in the respective Lineage 17.1 thread by @115ek

 

[MSe1969]

Heading towards EOL . . .

Hi all,
as you have read already in previous posts, we are switching over to lineage-17.1 now.

@115ek had since about a year already the below thread for the regular lineage-17.1 builds for the amami device, and since longer time, those builds have been stable and in daily-driver quality:

EOL [ROM][Unofficial][10.0][signed][OTA] Lineage OS 17.1 for Xperia Z1 compact

This thread is discontinued - please visit the LineageOS 18.1 sucessor thread This thread aims at providing LineageOS 17.1 builds for the Sony Xperia Z1 compact with current security patches. You can consider this thread as a successor of our...

forum.xda-developers.com

In the last weeks, I have started to provide lineage-17.1 test builds of the "microG" 2nd build varaint and since last month, I have also added the lineage-17.1 "microG" build as 2nd build variant to the above thread.
I have now built both variants for 17.1 and published them in above thread.

As mentioned already before, you can simply "dirty"-flash the 17.1 build over the 16.0 build, if you stay in the build variant, i.e.:
lineage-16.0 build variant A => lineage-17.1 build variant A
lineage-16.0 build variant B => lineage-17.1 build variant B

In fact, going forward, this is what @115ek and I recommend to you. We will keep this thread still open for a while and will also answer questions concerning the 16.0 builds (especially migration to 17.1 related questions).

Besides that, thank you for your interest in our 16.0 builds and looking forward to seeing you in our above mentioned known 17.1 amami thread.

Cheers,
115ek and MSe1969

 

[z1compactuser]

Hi! Thank you so much for your hard work on all your roms for the z1 compact!

This is the first time I have found a problem, I tried to update from lineage-16.0 build variant A to lineage-17.1 build variant A by "dirty"-flashing but I must have done something wrong because after it tried to boot for a while (it was stuck on the lineage logo) I was then just rebooted back to the recovery. Thankfully I was able to recover a backup.

I have the latest standard lineage os 16 with GApps installed and the twrp that allows for ota-uppgrades.

If you have the time, could you please provide some more detailed instructions on how to dirty-flash from the standard lineage os 16 to the standard lineage os 17.1?

 

[115ek]

If you have the time, could you please provide some more detailed instructions on how to dirty-flash from the standard lineage os 16 to the standard lineage os 17.1?

Maybe these official instructions on how to do a version upgrade may help you.
Yes, they are for the Z3 compact, but these steps are device independent.
You don't have to do the installation via sideloading - copying the new zips to sdcard/internal storage and flashing them from TWRP works as well.

I'd guess you made the mistake to not install the new (17.1) gapps package after installing Lineage 17.1 and before the first boot.

 

[MSe1969]

EOL
Hi all, in the LineageOS 17.1 successor thread, new builds with the February ASB patches have been published.
As already announced, this thread is EOL and we recommend you to upgrade (scroll back for more information), if not yet done.

We'll stop watching this thread and recommend to ask questions regarding migration to LineageOS 17.1 in our 17.1 thread.
@115ek - I suggest to ask the XDA forum admins to close this thread.

 

[shadowstep]

THREAD LOCKED

Requested by OP.

Regards,
shadowstep
Forum Moderator