• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

EOL [ROM][Unofficial][8.1.0][signed][OTA] LineageOS 15.1 for Xperia Z1 compact

Status
Not open for further replies.
Search This thread

JIJOK

Senior Member
Jun 24, 2015
144
21
nice update, but some "problem" here, download works good, also restart to recovery, install too but when the phone keep on the boot lineage screen forever. I force turn off and then restart normally. I am using twrp 3.2.3-1 , could the recovry version be the problem or something else ?
 
nice update, but some "problem" here, download works good, also restart to recovery, install too but when the phone keep on the boot lineage screen forever. I force turn off and then restart normally. I am using twrp 3.2.3-1 , could the recovry version be the problem or something else ?
I also have TWRP 3.2.3-1, and to really make sure, I have downgraded to my October build and did the OTA update, all went perfectly fine!
So can't tell you more - just a hint: BE PATIENT after an update, the first boot indeed takes long; of course I don't know how long you have waited, before you have decided to force turn off. Maybe there indeed was an issue, so glad it finally worked out for you - just in general, don't "panic" if the boot animation is there for even several minutes.
 
  • Like
Reactions: JIJOK

maciej03

Member
Feb 21, 2015
13
0
I changed to this rom build with MicroG from LineageOS 14.1 by munjeni.
- Wifi works fine only with disabled Captive portal mode
- GPS is broken. 0 satellites found. I tried back to stock, and flash again. And change #NTP server gps_debug.conf. It still doesn't work
 

115ek

Senior Member
Jan 30, 2017
563
631
I changed to this rom build with MicroG from LineageOS 14.1 by munjeni.
- Wifi works fine only with disabled Captive portal mode
- GPS is broken. 0 satellites found. I tried back to stock, and flash again. And change #NTP server gps_debug.conf. It still doesn't work

Step 1: RTFM (in this case the OP)
which leads to step number 2: Create a bug report we can deal with or your post will be ignored.

Concerning captive portal mode @MSe1969 is the right one to ask.
Concerning GPS: install SatStat, run it, wait for gps and share a screenshot (like this one).

But in any case: Create a proper bugreport or we can't help. What was the scenario? What apps did you use? What settings? Exact error? And of course: Logs!
 

maciej03

Member
Feb 21, 2015
13
0
Ok. Every app maps is inaccurate as the location only works from the cellular network.
I attach a screenshot and hope a good log.

Step 1: RTFM (in this case the OP)
which leads to step number 2: Create a bug report we can deal with or your post will be ignored.

Concerning captive portal mode @MSe1969 is the right one to ask.
Concerning GPS: install SatStat, run it, wait for gps and share a screenshot (like this one).

But in any case: Create a proper bugreport or we can't help. What was the scenario? What apps did you use? What settings? Exact error? And of course: Logs!
 

Attachments

  • Screenshot_2019-11-19_18-04-52.png
    Screenshot_2019-11-19_18-04-52.png
    110.7 KB · Views: 94
  • logcat.txt
    17.2 KB · Views: 5

115ek

Senior Member
Jan 30, 2017
563
631
Ok. Every app maps is inaccurate as the location only works from the cellular network.
I attach a screenshot and hope a good log.

From your screenshot I'd guess you are inside a building. (correct me if I'm wrong).
GPS inside buildings isn't a good idea - especially with older devices. Can you test it outside again (or at least near a window...).
Line of sight between satellites and smartphone is always a good idea.
I think this should already fix the problem.

Concerning your log: Please share the complete log (if the first thing still doesn't help) you get with
Code:
adb logcat -b all > log.txt
If you've got security concerns you can also send it via PM @MSe1969 or to me.
 

JIJOK

Senior Member
Jun 24, 2015
144
21
This are my gps device only if you are curious

1st image : satstat --- 2 : gpstest ----- 3 : osmand

about 2 mins to get working gps and also using global optimized gps file replacer from magisk

Question : Can I manually update rom from twrp ? download zip, boot on twrp, flash ..... done ? or need to wipe ?
 

Attachments

  • satstat.jpeg
    satstat.jpeg
    43.5 KB · Views: 124
  • gpstest.jpeg
    gpstest.jpeg
    48.3 KB · Views: 122
  • osmand.jpeg
    osmand.jpeg
    90.4 KB · Views: 120
Last edited:
New builds with December 2019 ASB patches

New builds available with December 2019 ASB patches (sec. string 2019-12-05):

A. Standard variant
https://www.androidfilehost.com/?fid=4349826312261654448
- Updated System Webview 78.0.3904.96

B. Hardened microG build variant
https://www.androidfilehost.com/?fid=4349826312261654447
- Updated Bromite SystemWebview to 78.0.3904.119
- Updated AuroraStore to 3.1.5

OTA updates will be offered soon from within the ROM (Updater app), if you are at least on the August build of this ROM.
Regards - M.
 
  • Like
Reactions: 115ek

zoltaaaan

Member
Mar 10, 2019
12
3
I remember something from my cm-12.1- thread, maybe it is related - but not sure:
Could you please do the following? Connect your phone via 'adb' and enter a root shell, where you enter the following command:
Code:
cat /sys/devices/mdss_dsi_panel/panel_id
Please post the result.


Hey, your post is from a while back. But the problems occured every now and then and now I started to look into it again.
Code:
cat /sys/devices/mdss_dsi_panel/panel_id
result: auo novatek 720p cmd

The system info:
Recovery: TWRP 3.2.3-1
LineageOS-Version: 15.1-20191110-UNOFFICIAL-signed-amami
Kernel:3.4.0-g27406e978f59-45979-g7f017131843f (gcc version 4.9.x 20150123 (prerelease) (GCC))
Build: lineage_amami-userdebug 8.1.0 OPM7.181205.001

Right now, there is another more urgent matter. I set the phone up completly new a few days ago. I flashed the TWRP version 3.2.3-1 and installed the Lineage version with OTA updates. The phone worked fine and I configured Android and installed an OTA update. I used the SD card as internal storage.
As of today, the phone did not recognise the SD card. Apps do not work anymore and it is a big problem.

The SD card is somehow corrupted. There are two partitions on the card. A small one (16 MB, exFAT) and a big one (59,46 GB, unknown format). The phone cannot recognize the card and windows is not able to format the card as well.

Attached are some logfiles.


Edit: I tried to install catlog, to log what happens, when the screen freezes next time. The app crashes instantly. I attached the logcat from during catlog crashing as well: View attachment catlog_crash.log
 

Attachments

  • dmesg_01.txt
    287.6 KB · Views: 3
  • logcat_01.txt
    314.5 KB · Views: 5
  • last_kmsg.txt
    38.9 KB · Views: 7
Last edited:
Hey, your post is from a while back. But the problems occured every now and then and now I started to look into it again.
Code:
cat /sys/devices/mdss_dsi_panel/panel_id
result: auo novatek 720p cmd

The system info:
Recovery: TWRP 3.2.3-1
LineageOS-Version: 15.1-20191110-UNOFFICIAL-signed-amami
Kernel:3.4.0-g27406e978f59-45979-g7f017131843f (gcc version 4.9.x 20150123 (prerelease) (GCC))
Build: lineage_amami-userdebug 8.1.0 OPM7.181205.001

Right now, there is another more urgent matter. I set the phone up completly new a few days ago. I flashed the TWRP version 3.2.3-1 and installed the Lineage version with OTA updates. The phone worked fine and I configured Android and installed an OTA update. I used the SD card as internal storage.
As of today, the phone did not recognise the SD card. Apps do not work anymore and it is a big problem.

The SD card is somehow corrupted. There are two partitions on the card. A small one (16 MB, exFAT) and a big one (59,46 GB, unknown format). The phone cannot recognize the card and windows is not able to format the card as well.

Attached are some logfiles.


Edit: I tried to install catlog, to log what happens, when the screen freezes next time. The app crashes instantly. I attached the logcat from during catlog crashing as well: View attachment 4897217

Hi

in regards to your SD-card issue:
You have used the "adoptable storage" feature of Android and formatted your SD in a way to become part of your internal memory. Whilst this is a cool feature on the one-hand side, it has some really serious drawbacks - this article here gives a good overview (it starts with the drawbacks, so no need to read through everything). You are exactly in that situation, and as you said, your SD card is somehow corrupted - and that means, unfortunately, you need to do a factory reset . . .

In regards to the panel_id - let me search a little bit... I'll get back to you on that.
 

zoltaaaan

Member
Mar 10, 2019
12
3
Hi

in regards to your SD-card issue:
You have used the "adoptable storage" feature of Android and formatted your SD in a way to become part of your internal memory. Whilst this is a cool feature on the one-hand side, it has some really serious drawbacks - this article here gives a good overview (it starts with the drawbacks, so no need to read through everything). You are exactly in that situation, and as you said, your SD card is somehow corrupted - and that means, unfortunately, you need to do a factory reset . . .

In regards to the panel_id - let me search a little bit... I'll get back to you on that.

Well, I took the card out of the phone and put another one in. The new card (slower and less capacity) is formatted as external for now. I wil read the article later, thank you.
I can give you another logcat from during the screen freeze and restart. But also later today or maybe tomorrow.
 
Well, I took the card out of the phone and put another one in. The new card (slower and less capacity) is formatted as external for now. I wil read the article later, thank you.
I can give you another logcat from during the screen freeze and restart. But also later today or maybe tomorrow.
Not necessary with the logs - as you said yourself, the card has issues, and it used to work before - so there is no mistake in the ROM, and thus nothing I could do - the system simply cannot access certain files necessary to operate or where it expects them and now goes crazy about it. Nothing significantly else is what the logs indicate (did not go through them in much detail, tbh, but roughly that's it).
As far as I understood the article, an adopted SD card does really logically become part of the /data partition and not "only" part of the area below the symlink /data/sdcard - therefore your system will most probably continue to be lunatic, even after you have put another SD card in - that depends, which pieces of the entire /data partition are physically on the corrupted SD - therefore I am afraid, you will have to factory reset...
 

zoltaaaan

Member
Mar 10, 2019
12
3
Not necessary with the logs - as you said yourself, the card has issues, and it used to work before - so there is no mistake in the ROM, and thus nothing I could do - the system simply cannot access certain files necessary to operate or where it expects them and now goes crazy about it. Nothing significantly else is what the logs indicate (did not go through them in much detail, tbh, but roughly that's it).
As far as I understood the article, an adopted SD card does really logically become part of the /data partition and not "only" part of the area below the symlink /data/sdcard - therefore your system will most probably continue to be lunatic, even after you have put another SD card in - that depends, which pieces of the entire /data partition are physically on the corrupted SD - therefore I am afraid, you will have to factory reset...

Sorry for the confusion. The issue with the SD card is new and just happened after I set the phone up with new recovery and new version of the rom. To be honest it does work normally right now. The installation was only a few days old, when the SD card stopped working. The system is not behaving wrong right now.
Do you think a factory reset with the broken SD card inside will also fix the SD card? I was completly puzzled that it isn't even possible to format the SD card in windows right know or completly kill it with some other software. I do not need to save any contents, but I want to use the fresh SD card again.

There was a separate issue. The older issue with the touchscreen and the frozen device. Today I reproduced the freeze. The phone freezes, when it has no mobile internet AND there is user input on the touchscreen. It reproduces so exactly, that when you are in a train and loose your connection every now and then, you have to avoid touching the screen to avoid freezing. When you touch it when it has no mobile internet, it freezes.
And today I made a logcat and froze the phone.
That was the issue, where you wanted to know my touch panel ID for.
I did not manage to get a kernel log, but maybe the rest helps.
 

Attachments

  • logcat_12-09-2019_11-04-43.txt
    500.1 KB · Views: 3
  • dmesg.txt
    163.5 KB · Views: 1
Last edited:
  • Like
Reactions: MSe1969

marsa47

Member
Aug 1, 2010
43
19
IFAIK the screen freeze is related to non-original screens (drivers issue). I have one Z1c with non-original screen (cheap repair) and one in original condition. The one with the changed screen freezes if the screen is ON and the network connection goes to 2G mode (e.g. bad reception). If the connection mode cycles with the screen OFF, there is no problem. But if you use the phone in that exact moment, it will freeze and you can only hard reset it.
 
  • Like
Reactions: MSe1969
Hey, your post is from a while back. But the problems occured every now and then and now I started to look into it again.
Code:
cat /sys/devices/mdss_dsi_panel/panel_id
result: auo novatek 720p cmd
Just to let you know: I have the same result, so my idea will not lead to anywhere, in my cm-12.1 thread, we had a kernel issue a while back which was based on different hardware components, but that is not the case for your device. I though to look into that direction, but wrong path obviously, hence "Sorry, no idea"
 

zoltaaaan

Member
Mar 10, 2019
12
3
I don't know where I read it, but somewhere I read something about a driver for after market displays. That idea sounds odd to me, since aftermarket displays includes different panels. Is there some kind of generic touchscreen driver, which might work better than the stock driver?
 

zoltaaaan

Member
Mar 10, 2019
12
3
Just to let you know: I have the same result, so my idea will not lead to anywhere, in my cm-12.1 thread, we had a kernel issue a while back which was based on different hardware components, but that is not the case for your device. I though to look into that direction, but wrong path obviously, hence "Sorry, no idea"

You have the same result to this query, but you have a stock touchscreen?

Maybe that is the problem. Shouldn't the phone know, there is another panel built in? Maybe then it would handle it differently? I am just making assumption here, I have no idea about Android Development.

But this should be a problem for a lot of people, right? People who put in a new touchscreen in an old phone should be also those people who install custom roms to it. (making assumptions again) Does anyone know, if that general problem is present for various devices?
 
You have the same result to this query, but you have a stock touchscreen?

Maybe that is the problem. Shouldn't the phone know, there is another panel built in? Maybe then it would handle it differently? I am just making assumption here, I have no idea about Android Development.

But this should be a problem for a lot of people, right? People who put in a new touchscreen in an old phone should be also those people who install custom roms to it. (making assumptions again) Does anyone know, if that general problem is present for various devices?
The issue, which we've had in the cm-12.1 thread back in 2017, was based on the fact that the Z1c indeed was produced with different hardware components and we had solved it. So I simply thought if there was another component, there was the possibility to look at the fix again and adapt. But as said, that won't go...
Usually, replacing HW components should not cause issues, but obviously it does in your case...
 

115ek

Senior Member
Jan 30, 2017
563
631
I don't know where I read it, but somewhere I read something about a driver for after market displays. That idea sounds odd to me, since aftermarket displays includes different panels. Is there some kind of generic touchscreen driver, which might work better than the stock driver?

There are indeed different firmwares for different panels.
I just checked /system from latest stock (actually for a different thing...) and stumbled over system/etc/touch_fw_update.sh (appended it)
And there are different firmware binaries called touch_module_id_0x4d.img, touch_module_id_0x4e.img, touch_module_id_0x5d.img, touch_module_id_0x45.img, touch_module_id_0x48.img, touch_module_id_0x53.img and touch_module_id_0x54.img under system/etc/firmware

It seems we already ship them - however there's no update script. Maybe there's an other way to determine what to load (directly in kernel driver?).
I hadn't got time to investigate it further. Just wanted to share my findings. Feel free to dig into it :good:
 

Attachments

  • touch_fw_update.sh.txt
    1.3 KB · Views: 7
  • Like
Reactions: MSe1969
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 18
    Thread Closed Per OP Request

    This thread is dedicated to provide Lineage-OS 15.1 builds for the Sony Xperia Z1 compact with current security patches.
    This thread is discontinued - please visit the LineageOS 16.0 successor thread

    This is the joint effort of 115ek and MSe1969 (contributions welcome).
    There are two build flavors available, both are signed (see further below):

    A. Standard LineageOS 15.1
    This build flavor aims at providing LineageOS 15.1 "as is" with most recent security patches.
    Consider this flavor as continuation of the thread here by 115ek.
    Download here

    B. Security hardened microG build
    For the security/privacy focused
    Download here
    • Pre-installed microG and F-Droid same as the LineageOS for microG project
    • Pre-installed AuroraStore
      [*]Pre-Installed pre-release of microG DroidGuard helper to have a working SafetyNet attestation (see comments below!)
    • Additional security hardening features listed below
    • Access to /proc/net blocked for user apps
    • Bundled netmonitor app to allow network monitoring
    • Enhanced Privacy Guard: Switches for motion sensors, other sensors and certain background activities
    • Cloudflare as default DNS (instead of Google)
    • Privacy-preferred default settings
    • Optional blocking of Facebook- and Google-Tracking
    • Optional disable captive portal detection
    • Option to set own DNS
    • Option to deny new USB connections
    • 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
    • Additional restriction options for secondary users

    Current release levels
    Security string: 2020-02-05
    AOSP tag: 8.1.0_r52
    System Webview: M79 (Standard build)
    Bromite Webview: M79 (microG build)


    Source-code and build instructions
    Kernel: https://github.com/lin15-microG/kernel_sony_msm8974/tree/lineage-15.1
    Build manifest: https://github.com/lin15-microG/local_manifests

    TWRP Recovery
    Please use the TWRP recovery referred to in this thread

    Limitations
    Following limitations are known:
    • NFC-HCE does not work (needed for example for google pay)
    • FM does not work in stereo mode (mono works fine, though)
    • Problems with some 5 GHz Wifi channels (can be avoided by not using autochanneling) fixed with 20190408 build
    • MHL does not work
    • 5 GHz hotspot does not work (2.4 GHz hotspot works fine)

    Installation Instructions

    YOU ARE RESPONSIBLE SOLELY YOURSELF FOR ANY ACTIONS YOU DO WITH YOUR DEVICE !!!

    Please note - we won't explain any single aspect (e.g. how to install 'fastboot' on your PC or troubleshoot USB connectivity issues under Windows). Search the net and consult the search engine of your choice or look here in XDA, there is plenty information available.

    Pre-Requisites
    • Get familiar with the hardware keys of the Xperia Z1 compact device, especially how to enter fastboot mode and recovery mode
    • Have fastboot and adb installed on your PC and make sure, you can connect via USB to your device in fastboot mode and via adb
    • Download the most current .ZIP file of our ROM and place it to your phone's internal memory or SD card
    • Only valid for the "standard build flavor": If you wish to install Google apps (GApps), please refer to the GApps section further below
    • An unlocked bootloader (read the warnings carefully and backup your data!)
    • Only in case your device is still with the pre-delivered Sony Stock ROM: It is recommended that you have updated the Stock ROM to the latest version offered by Sony to make sure that the bootloader has the needed capabilities (see also 'trouble-shooting' below)

    Install TWRP recovery
    If you come from stock ROM and have just unlocked your boot loader, this is the next thing to do. If you have already a working custom recovery on your device, there is no necessity to replace it. However - we recommend to use the TWRP recovery linked in this thread. The following instructions are based on TWRP.
    To install TWRP, download the TWRP.img file (Note: replace "TWRP.img" in the following instructions with the real file name) from this section to your PC, connect the phone via USB to your PC, get it into 'fastboot mode' and enter the following command on your PC:
    Code:
    fastboot flash FOTAKernel TWRP.img
    Afterwards, directly boot into 'recovery mode' (enter fastboot reboot on your PC and use the right hardware keys to get into recovery mode) - we recommend not to boot the phone's Android system after having flashed TWRP. Once TWRP has been launched, you may decide to reboot your phone and install the ROM at any time later. But the first boot after flashing TWRP should be TWRP in recovery mode.
    Trouble-shooting:
    Depending on the Stock ROM you are on, you may face some difficulties to get the phone into recovery after flashing TWRP. If you are facing such difficulties (i.e. phone always boots into Stock ROM), get into fastboot mode, and manually boot into TWRP by entering the below command:
    Code:
    fastboot boot TWRP.img
    If that also does not help you, it could be that the firmware, you have previously used, included an outdated bootloader. In that case, use the Sony flash tool (Windows only) or Androxyde's Open source flshtool to flash a more current Sony firmware image.
    Both approaches can also help to "unbrick" your device.

    Advanced Wipe
    ONLY perform the steps described here, if you come from Stock ROM or a different Custom ROM!
    Boot into recovery mode. In TWRP, choose "Wipe", "Advanced" and spefify "Dalvik", "System", "Cache" and "Data" to be wiped. Make sure NOT to wipe "Internal memory" or "SD Card". Swipe to confirm the deletion and get back into the main menu.

    GApps
    DO NOT attempt to flash GApps on the "microG" build variant!
    For the "Standard" variant, the following applies:
    You do not need to install GApps, but you may wish to do so. In that case, download GApps from here and put the .ZIP also to the SD card or Internal memory of your device. Choose ARM as platform, Android 8.1 and the flavor of your choice. We recommend "pico", as this leaves you the most freedom to only install, what you really need; you can later still install all the Google products you want and do not need to live with pre-installed Google applications you have no use for.

    Install our ROM
    In the TWRP main menu, choose "Install". A file manager appears to let you navigate to your internal memory (path /sdcard) or your SD card (path /external_sd). Choose the .ZIP file of our ROM and swipe to flash.
    If you update from a previous version of our ROM, you don't need to perform a wipe. If you had GApps already installed before the update, there is no need to flash them again. They will be automatically restored during the flash process. (Note: If you wish to get rid of GApps, navigate to TWRP's file manager in the Advanced section of the main menu, go to path /system/addon.d and delete the file 70-gapps.sh, before flashing the ROM update)
    If you come from a different ROM (or stock firmware), make sure that you have performed the Wipe steps above. If you wish to install GApps, select the respective .ZIP file directly afterwards, do not boot into Android before having flashed GApps.
    When finished flashing, return to the main menu, choose "Reboot" and then "System", which will cause your phone to boot into our Lineage OS 15.1 - be patient, the first boot after flashing a new ROM takes quite long!

    microG
    Only valid for the "microG" build variant: After the first installation of this ROM, you need to setup microG.
    Please read the instructions given on the LineageOS for microG site, section "Post Install - UnifiedNlp"


    Encryption
    Encryption works, however - please consider the below important information:

    • If you have previously encrypted your device with a "Lollipop" (Android 5.x) based ROM (e.g. this one), our ROM unfortunately cannot decrypt and you will have to format the data partition and encrypt again. Be aware, that your 'Internal Memory' will be lost in that case, so don't forget to make a backup!
    • If the device has been encrypted with a "Nougat" (Android 7.x) based ROM, there won't be any issues, even if you switch between different Android releases including Android 8.x and 5.x for testing purposes
    • If you encrypt the device with our LineageOS 15.1 ROM, you will not be able to decrypt the /data partition with TWRP and have to 'sideload' any updates instead
    We consider this as a still open issue. We will be grateful for any advice on how to solve these compatibility issues.
    For the time being, it seems that flashing a naked Nougat-ROM (e.g. this one) to perform the encryption and then wipe and install LineageOS 15.1 will leave you with the most flexibility.


    Dealing with signed builds
    Please note, that our builds are signed with our own key. When you come from a different build, you cannot directly "dirty-flash" our build. You either have to perform a "clean flash" (recommended), or - if you e.g. would like to update from one of 115ek's previous builds, you need to follow below instructions.

    Coming from 115ek's Lineage 15.1 build:
    • Download and extract the file migration.sh from this archive
    • boot into TWRP
    • push the migration.sh file to the directory /data/local on your device and mount the /system partition in TWRP (you can do so using the dedicated TWRP's menu entry)
    • launch the built-in terminal in TWRP, cd into /data/local, make migration.sh executable (chmod +x) and execute the command ./migration.sh official
    • (In case you receive an error, try sh ./migration.sh official instead)
    • flash the ROM .zip
    • wipe Cache and Dalvik/ART Cache
    • reboot system
    More background information "theory behind" can be found in the LineageOS wiki and AOSP reference.


    Switching between build flavors
    You can easily do so via clean-install. However, if you want to switch between the standard build and the microG build and vice-versa without wiping your data, please follow the below instructions:

    Standard build => microG build
    • De-install any of the following apps, in case you have manual installations of them: Yalpstore, Privacy-friendly netmonitor, microG Services Core, microG Services Framework Proxy, Fake Store, F-Droid, Mozilla Unified NLP Backend, Nominatim Geocoder Backend
    • Deactivate System Webview
    • If you have flashed GApps before, deactivate all of them to remove any installed updates
    • Boot into TWRP recovery
    • If you have flashed GApps before, delete the file /system/addon.d/70-gapps.sh
    • Flash the microG ROM ZIP (make sure not to use an older version than the current standard build)
    • Wipe Cache & Dalvik and reboot
    • Follow the 'Post-install' steps outlined here

    microG build => standard build
    • Deactivate the following apps: Yalpstore, Privacy-friendly netmonitor, microG Services Core, microG Services Framework Proxy, Fake Store, F-Droid, Mozilla Unified NLP Backend, Nominatim Geocoder Backend, Bromite System Webview
    • Boot into TWRP recovery
    • Flash the standard ROM ZIP (make sure not to use an older version than the current microG build)
    • If you want to flash GApps, do it before re-boot
    • Wipe Cache & Dalvik and reboot

    Please note, that you may face issues with some apps, which depend on play services. In that case, try solving them in the following order: 1. delete app cache, 2. delete app data, 3. de-install and re-install app


    Weather Widget

    LineageOS does currently not offer Weather provider apps for LineageOS 15.1 for download (only for LineageOS 14.1)
    We've have built an APK for OpenWeatherMap for download from the LineageOS sources here, which works well with LineageOS 15.1


    SafetyNet

    Google SafetyNet is a device certification system, ensuring that the device is properly secured and compatible with Android CTS. Some applications use SafetyNet for security reasons, to enforce DRM or as a prerequisite for tamper-protection. General information about SafetyNet can be found here or e.g. see LineageOS' statement about SN.

    The below information is only relevant for the microG build. In the standard build, you have SafetyNet, if you flash Gapps. Whether the SN attestation passes or not is completely out of our influence!

    If you don't need SafetyNet (i.e. you don't use apps requiring it), I recommend to switch off SafetyNet in microG settings and in addition, go to Settings - apps, make system processes visible and disable the app 'microG DroidGuard Helper'
    In that case, you can safely skip the below information. (If you access the play store with Yalp coming with this build, apps, which the original playstore app would hide because of failed SafetyNet, such as e.g. Netflix, are still listed, so you don't need SafetyNet for that specific purpose)

    If you need SafetyNet, because you use an app requiring SafetyNet attestation to pass, switch SafetyNet on in microG settings and make sure the a.m. DroidGuard Helper app is active. Further, please consider below important information.

    The typical use-case, for which SafetyNet has been developped and is e.g. used by Google, is e.g. "Google Pay".
    Although it seems not to be the intention of Google to make SafetyNet part of "ordinary, average" apps - unfortunately - a certain tendency can be observed that more and more apps make use of it. Especially nosy and privacy intrusive apps seem to start using SafetyNet against Custom ROMs, because Custom ROMs usually allow to at least restrict uncontrolled data collection.

    microG GmsCore contains a free implementation of SafetyNet, but the official server requires SafetyNet requests to be signed using the proprietary DroidGuard system. A sandboxed version of DroidGuard has been added to this microG build as a prebuilt “DroidGuard Helper” app to run the Google code in an isolated environment. The chosen approach in my build is proposed and discussed within the microG project, but not yet officially implemented by microG.

    As of March 11th 2019, the microG build passes the SafetyNet attestation, when installed w/o root or Xposed.
    So, if you need SafetyNet and you also need root, Magisk would be the way to go.
    To avoid confusion: Magisk can hide itself from being detected by SafetyNet and thus help to pass SN, if the device would pass SN without having Magisk installed. Nothing more.

    Note: Currently, the DroidGuard helper app is not part of the build, as it currently does not work any more.

    There are apps available on the Play store to show, whether SafetyNet attestation is passed, for example 'SafetyNet Test' (org.freeandroidtools.safetynettest)


    IMPORTANT
    I cannot and I will not give any assurance that SafetyNet attestation is passed by this build!
    The SafetyNet code, which is dynamically downloaded from Google servers and executed on the device as part of the defined functionality, is regularly maintained and further developped by Google. Although it currently works, it could stop working in the future, until the microG team finds again a solution.
    (Interesting enough: Remote code execution is normally considered a severe vulnerability, but hey, it's Google and we all "trust" them 100%, don't we? ;) - At least I, besides others, exactly for that reason, do not use Gapps!)
    Further, I for my part refuse to use apps requiring SafetyNet, but that is of course everybody's own decision.


    Usage of ANT+

    You need the 2 apps:
    afterwards setting proper permissions is essential!
    1. Go to Apps & Notifications -> See All Apps
    2. Select 'ANT Radio Service'
    3. Select Permissions
    4. Select Additional permissions
    5. Slide switch to allow using of ANT hardware
    This refers to those instructions.


    Bug reports:
    If you have a problem please create a post with these information:
    Original Kernel shipped with this rom:
    Build Date:
    And try to get log as described here


    Credits
    In continuation of the previous thread, we would like to acknowledge:
    Android Open Source project (AOSP)
    LineageOS project
    AICP project
    SpiritCroc: big thanks to him for maintaining the device trees and a lot of very useful hints
    rcstar6696
    SuperLamic
    drakonizer
    AdrianDC
    munjeni: thanks for tips and tricks
    nailyk: thanks for tips and tricks
    All the other contributors on sony msm8974 platform
    microG project
    CopperheadOS project
    csagan5 (Bromite)
    Yeriomin (Yalp)


    XDA:DevDB Information
    [ROM][Unofficial][8.1.0][signed] LineageOS 15.1 for Xperia Z1 compact, ROM for the Sony Xperia Z1 Compact

    Contributors
    MSe1969, 115ek
    Source Code: https://github.com/lin15-microG/local_manifests

    ROM OS Version: 8.x Oreo
    ROM Kernel: Linux 3.4.x
    Based On: LineageOS

    Version Information
    Status: Stable
    Stable Release Date: 2020-02-09

    Created 2018-12-29
    Last Updated 2020-03-09
    6
    Using old firmware blobs from bacon mentioned here did the trick for me.
    Anyway I'm going to look into the difference between bacon and amami blobs - I just thought I understood how it works... :rolleyes:
    I'm able to see and use upper 5GHz channels now which means wifi auto channeling now works with my router.
    Going to build a clean testbuild for you now. I'll report back in a few hours :)

    ---------- Post added at 03:56 PM ---------- Previous post was at 02:59 PM ----------

    I'll only provide a testbuild for pure lineage - microg users have to wait at least for next ASB update (early april). I'm a bit lazy :laugh:
    You'll find the build here
    Just wipe /system, /"cachestuff" and install new .zip.
    Please report and share your experiences. I'm also interested if some other things are broken now (hotspot...).

    BTW: If there's a strong demand for a fixed microg version --> let us know. It's no problem to get one built before april.

    If you report the problem solved this fix will also be included in Lineage 16 and AICP 14 by @SpiritCroc
    5
    New build with February '19 ASB

    Hi all,
    new builds are available for the February ASB patches:

    A. Standard build flavor
    https://www.androidfilehost.com/?fid=1395089523397889456
    • ASB Security string 2019-02-05
    • Kernel: Various Security Patches and some additional 'spectre' mitigations
    • Fix of Eleven and LockClock app taken over from microG flavor

    B. microG build flavor
    https://www.androidfilehost.com/?fid=1395089523397889455
    • ASB Security string 2019-02-05
    • Kernel: Various Security Patches and some additional 'spectre' mitigations
    • Bromite SystemWebView updated to M72

    Happy flashing!
    Regards, M.
    4
    New builds with November 2019 ASB patches

    New builds available with November 2019 ASB patches (sec. string 2019-11-05):

    A. Standard variant
    https://androidfilehost.com/?fid=4349826312261626355

    B. Hardened microG build variant
    https://androidfilehost.com/?fid=4349826312261626354
    - Updated Bromite SystemWebview to 78.0.3904.72

    OTA updates will be offered from within the ROM (Updater app), if you are at least on the August build of this ROM.
    Regards - M.
    3
    Change log

    March 9th, 2020
    Announcement to discontinue this thread - please visit the LineageOS 16.0 successor thread

    February 9th, 2020
    • ASB Security string 2020-02-05
    • Replaced DRM lib (fixes issues with Netflix)
    • Standard flavor: System Webview on 79.0.3945.136
    • microG flavor: Bromite Webview on 79.0.3945.139
    • microG flavor: Updated AuroraStore to 3.1.8

    January 14th, 2020
    • ASB Security string 2020-01-05
    • Standard flavor: System Webview on 79.0.3945.116
    • microG flavor: Bromite Webview on 79.0.3945.107
    • microG flavor: Updated AuroraStore to 3.1.7
    • microG flavor: Updated AuroraServices to 1.0.5

    December 7th, 2019
    • ASB Security string 2019-12-05
    • Standard flavor: System Webview on 78.0.3904.96
    • microG flavor: Bromite Webview on 78.0.3904.119
    • microG flavor: Updated AuroraStore to 3.1.5

    November 10th, 2019
    • ASB Security string 2019-11-05
    • Standard flavor: System Webview on 77.0.3865.116
    • microG flavor: Bromite Webview on 78.0.3904.72
    • microG flavor: Updated microG GMS core 0.2.9.x

    October 14th, 2019
    • ASB Security string 2019-10-05
    • Standard flavor: System Webview on 77.0.3865.92
    • microG flavor: Bromite Webview on 77.0.3865.104
    • microG flavor: AuroraStore updated to 3.1.3

    September 10th, 2019
    • ASB Security string 2019-09-05
    • Standard flavor: System Webview on 76.0.3809.111
    • microG flavor: AuroraServices updated to 1.0.4

    August 11th, 2019
    • ASB Security string 2019-08-05
    • OTA Support
    • Standard flavor: System Webview on 76.0.3809.89
    • microG flavor: Bromite Webview on 76.0.3809.100
    • microG flavor: Aurorastore 3.0.9 with AuroraServices install method
    • microG flavor: Updated microG GMS core 0.2.8.x

    July 5th, 2019
    • ASB Security string 2019-07-05
    • microG flavor only: Bromite Webview on 75.0.3770.109

    June 12th, 2019
    • ASB Security string 2019-06-05
    • Recovery boot fix for Magisk 19.x
    • System Webview updated to 74.0.3729.157 (non-microG flavor)
    • microG flavor only: Bromite Webview on 75.0.3770.86
    • microG flavor only: Replaced Yalpstore with Aurorastore
    • microG flavor only: Removed RemoteDroidGuard
    • microG flavor only: Updated F-Droid & priv. extension
    • microG flavor only: Updated microG GMS core 0.2.7.x

    May 9th, 2019
    • ASB Security string 2019-05-05
    • System Webview / Bromite Webview both on M74
    • microG flavor only: Option to set own DNS
    • microG flavor only: Backport of 'Deny new USB' feature
    • microG flavor only: Additional options for secondary users
    • microG flavor only: Increased max. password length 64

    April 8th, 2019
    • ASB Security string 2019-04-05
    • Solved WLAN 5GHz channel issue (see thread discussion)
    • microG flavor only: Control switch in dev. settings for hosts file update

    March 11th, 2019
    • ASB Security string 2019-03-05
    • SystemWebView updated (includes CVE-2019-5786): M72 (standard flavor) / M73-Bromite (microG flavor)
    • microG flavor only: Prebuilt microG DroidGuard helper app to pass SafetyNet attestation

    February 10th, 2019
    • ASB Security string 2019-02-05
    • Kernel: Various Security Patches and some additional 'spectre' mitigations
    • microG flavor: Bromite SystemWebView updated to M72
    • Standard Flavor: Fix of Eleven and LockClock app taken over from microG flavor

    January 14th, 2019
    • ASB Security string 2019-01-05
    • SystemWebView updated to M71 in Standard flavor
    • Various Kernel security fixes

    December 29th, 2018
    Initial load
    • ASB Security string 2018-12-05
    • AOSP tag android-8.1.0_r52
    • SystemWebView: M69 (Standard flavor) / M71-Bromite (microG flavor)

    Initial feature list of microG flavor:
    • Pre-installed microG and F-Droid same as the LineageOS for microG project
    • Pre-installed YalpStore (Version 0.45)
    • Access to /proc/net blocked for user apps
    • Bundled netmonitor app to allow network monitoring
    • Enhanced Privacy Guard: Switches for motion sensors, other sensors and certain background activities
    • Cloudflare as default DNS (instead of Google)
    • Privacy-preferred default settings
    • Optional blocking of Facebook- and Google-Tracking
    • Optional disable captive portal detection
    • No submission of IMSI/IMEI to Google/Sony when GPS is in use
    • Default hosts file with many blocked ad/tracking sites
    • Privacy-enhanced Bromite SystemWebView