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

[MSe1969]

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:

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:

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:

• ANT Radio Service (Github) / (Google play)
• ANT+ Plugin Service (Github) / (Google play)

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

 

[MSe1969]

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

 

[MSe1969]

Information about Privacy/Security Hardening in microG build flavor

As announced in the OP, the microG build flavor contains a couple of specific features, which are explained in more detail in this section:

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

2. Pre-installed AuroraStore
works w/o having to enable "unknown sources"

3. Restrict access to /proc/net for user apps
An adapted SELinux policy prevents user apps from accessing the /proc/net pseudo file system, which can be misused to monitor and track the phone's internet traffic. For technical backgrounds, see here. For the legitimate use case of the smart phone owner him/herself monitoring the network traffic to see, what the installed apps do, the app Privacy-Friendly Network Monitor has been bundled.

4. Enhanced Privacy Guard - Sensor permission switches and background control
An own sensor template to control access to motion sensors ('ask' mode) and all other sensors (allowed by default, but can be restricted) has been implemented into the Privacy Guard. Further, the following background activities can be restricted in Privacy guard:

• Background Clipboad access (forbidden by default, can be allowed per app)
• Background Location access (allowed by default, if location access as such is allowed, can be forbidden per app)
• Background Audio recording (allowed by default, if microphone access as such is allowed, can be forbidden per app)

5. Cloudflare (instead of Google) default DNS
Cloudflare DNS has a better privacy policy than Google Public DNS and has DNS-over-TLS and DNS-over-HTTPS. In the deafult DNS settings (as fallback) and network diagnostics, the Cloudflare DNS adresses 1.1.1.1 and 1.0.0.1 are specified as defaults (instead of Google's 8.8.8.8 and 8.8.4.4)

6. Privacy-preferred default settings
When newly installed, the below settings are defaulted, different from standard LineageOS 15.1 (all settings can be changed at any time later):

• Privacy Guard is enabled on install (proposal during Setup)
• Anonymous LineageOS statistics disabled (proposal during Setup)
• The standard browsing app does not get the location runtime permission automatically assigned
• Sensitive information is hidden on the lock screen
• Camera app: Location tagging disabled by default
• Apps having the PACKAGE_USAGE_STATS permission appear by default as "not allowed" under Settings => Security & privacy => Apps with usage access (instead of opting out here, the user needs to explicitly opt-in in order to have the app collecting this data)

Further, when a lock screen protection is set (PIN, pattern, password), the Nfc, Hotspot and airplane mode tiles require authentication and cannot be set without

7. Optional blocking of Facebook- and Google-Tracking
Settings => Network & Internet => Data usage => Menu => "Apply iptables block script"
When activated, all outgoing connection attempts to Facebook servers will be suppressed.
Same applies to Google, but apps on an internal exception list will still be able to connect (Yalpstore, microG, or e.g. NewPipe, if installed)

8. Optional disable captive portal detection
Settings => Network & Internet => Data usage => Menu => "Disable Captive Portal"
When activated, the system will not ping a specific Google server any longer when establishing a WiFi connection to determine, whether a captive portal is being used.

9. No submission of IMSI or phone number to Google/Sony when GPS is in use
GPS also works fine, if no SIM card is present, so there obviously is no benefit for the phone holder (different from other involved parties ) to provide this data . . .

10. Default hosts file with many blocked ad/tracking sites
The system's hosts file redirects a comprehensive list of URLs known to be adware, tracking, etc. to 127.0.0.1 (ipv4) and ::1 (ipv6)

11. Privacy-enhanced Bromite SystemWebView
Instead of the default Chromium System Webview component, the Bromite SystemWebView is used offering more privacy, more ad blocking and less Google tracking.

12. Deny new USB option
Settings => Security & Privacy
Control, what happens, if a USB device is connected to the device: Allow, allow when unlocked or block.

13. Option to define an own DNS
Settings => Network & Internet (scroll down)
You can optionally define an own DNS, which is used instead of the default DNS of the ISP (uses iptables)
Note: If your ISP intercepts DNS queries to enforce their own ISP - e.g. to enforce surveillance/censorship - this option won't work . . .

14. Maximum password length increased to 64

15. Additional restriction options for secondary users
- Disallow app installation option
- Disallow audio recording option

 

[lm089]

Cool, thanks for keeping these ROM versions alive.

Is there a difference between the version here (los standard build 20181229) and the one from 115ek's old thread (build 20181213)?

 

[MSe1969]

Cool, thanks for keeping these ROM versions alive.

Is there a difference between the version here (los standard build 20181229) and the one from 115ek's old thread (build 20181213)?

Not really: The Updater is not anymore part of this build (as it was anyhow useless given that you can't download this build from LineageOS) and as explained in the OP, our build is signed with our own key. (We'll provide a flashable ZIP for the migration soon)

 

[Viktor245]

Good firmware! All with the coming!

 

[lm089]

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.

Hmm - can't see those instructions mentioned in op

 

[115ek]

Hmm - can't see those instructions mentioned in op

I just added them

 

[_Pano_]

there are no mirrors to download the standard version

UPDATE: now, yes

 

[CyanoFriend]

I just added them

Thanks,
gave it a try just after migration info.
Migrated from November-build to Standard-Version.
Everything seems to work. Great! (because i know about problems with different keys )

Btw one question: From the beginning of 115eks rom i have several (not every time the same) FCs at startup and on the run occasionnal FCs.
(No such FCs with the great lollipop version, neither with the nougat rom. Clean install.)
No great problem, since all this programs work perfect on next start, but a little bit annoying. May i be of any help to find the reason?

PS: Rhein-Main rules

 

[MSe1969]

Thanks,
gave it a try just after migration info.
Migrated from November-build to Standard-Version.
Everything seems to work. Great! (because i know about problems with different keys )

Btw one question: From the beginning of 115eks rom i have several (not every time the same) FCs at startup and on the run occasionnal FCs.
(No such FCs with the great lollipop version, neither with the nougat rom. Clean install.)
No great problem, since all this programs work perfect on next start, but a little bit annoying. May i be of any help to find the reason?

PS: Rhein-Main rules

Regarding the FCs, I did not experience such things recently (using the microG variant myself from the beginning), do you have specific examples or a log?

P.S.: You also in the Rhein-Main area?

 

[115ek]

Thanks,
gave it a try just after migration info.
Migrated from November-build to Standard-Version.
Everything seems to work. Great! (because i know about problems with different keys )

Btw one question: From the beginning of 115eks rom i have several (not every time the same) FCs at startup and on the run occasionnal FCs.
(No such FCs with the great lollipop version, neither with the nougat rom. Clean install.)
No great problem, since all this programs work perfect on next start, but a little bit annoying. May i be of any help to find the reason?

PS: Rhein-Main rules

Sure you can do something: get logs (logcat and dmesg) after you experience these FCs. We'll have a look then.
Do you use third party software like Magisk or exposed framework? Do you use Gapps (if yes, what size)?

 

[kamikaze1204]

NFC google pay

Sorry for my english.
This rom i great, but I have a problem with recognise NFC by payement apps (google pay). NFC i working fine, but google pay and my bank's apk says "Your phone don't have NFC" and I can't pay via phone.

 

[CyanoFriend]

Regarding the FCs, I did not experience such things recently (using the microG variant myself from the beginning), do you have specific examples or a log?

P.S.: You also in the Rhein-Main area?

Hello,

i will try to answer you, 115ek and also kamikaze1204 in one text:

- xposed: yes
- magisk: no
- su-addon: yes
- opengapps pico
- rhine-main (rhein-main): yes
- dmesg via adb: yes
- logcat via adb: failure
- logcat other way: yes
- nfc since cm-lollipop working: no

trying to send dmesg and logcat via pm to you and 115ek

and coming to the end:

Happy new year and 42

 

[kamikaze1204]

Hello,

i will try to answer you, 115ek and also kamikaze1204 in one text:

- xposed: yes
- magisk: no
- su-addon: yes
- opengapps pico
- rhine-main (rhein-main): yes
- dmesg via adb: yes
- logcat via adb: failure
- logcat other way: yes
- nfc since cm-lollipop working: no

trying to send dmesg and logcat via pm to you and 115ek

and coming to the end:

Happy new year and 42

But nfc and magisk are working

 

[lm089]

I just added them

Just tried to to execute migration.sh but it's not working. Here's what I did, but let me explain first that I'm a real noob when it comes to Linux. So please excuse me if the following should contain irrelevant info...

1. copied your tar.gz file to /data/local
2. Booted into twrp
3. Opened zero's terminal
4. Executed 'mount' to see the current mount status
5. Executed 'mount /system' then again 'mount' > apparently /system is now mounted
6. Changed into /data/local
7. Executed 'tar - xzvf adb-key-migration.tar.gz' > thus extracted migration.sh to same dir
8. Executed 'ls - l' to see full file settings
9. Executed 'chmod +x migration.sh'
10. Executed 'ls - l' again to see that file status has changed to '-rwxr-xr-x 1 system system'
11. Executed './migration.sh official'

Result are 3 lines of error telling me something like

CANNOT LINK EXECUTABLE "/system/bin/sh" : cannot locate symbol "__register_atfork" referenced by "/system/bin/sh"...
Libc: CANNOT LINK EXECUTABLE "/system/bin/sh" : cannot locate symbol "__register_atfork" referenced by "/system/bin/sh"...
Libc: fatal signal 6 (SIGABRT), code - 6 in tid 243 (migration.sh), pid 243 (migration.sh)

Then after a while twrp gets into a bootloop which I can only end by a hard reset.

What am I doing wrong?

Edit: twrp version is 3.2.2.0, installed ROM is 115ek's version build 20181213

Edit#2: got it! Step 11 in my case should have been 'sh migration.sh official' instead; this way it worked, and flashing signed ROM build 20181229 then worked as expected. :good:

 

[115ek]

Sorry for my english.
This rom i great, but I have a problem with recognise NFC by payement apps (google pay). NFC i working fine, but google pay and my bank's apk says "Your phone don't have NFC" and I can't pay via phone.

Easiest way of being able to use google pay is using Stock android lollipop. Payment with custom ROMs is generally tricky, especially if you're rooted.
The problem now is: Neither MSe nor myself are using google services, so there's not that big interest in getting this working. TWRP decryption has higher priority.
And if you don't supply any logs then there's nothing we can do. Sorry.

Hello,

i will try to answer you, 115ek and also kamikaze1204 in one text:

- xposed: yes
- magisk: no
- su-addon: yes
- opengapps pico
- rhine-main (rhein-main): yes
- dmesg via adb: yes
- logcat via adb: failure
- logcat other way: yes
- nfc since cm-lollipop working: no

trying to send dmesg and logcat via pm to you and 115ek

and coming to the end:

Happy new year and 42

Xposed is generally bad for people like us. It is able to modify the system in way no one can predict. If you load some "strange modules" you shouldn't wonder if something crashes.
My recommendation: clean installation with following observation if errors/FCs still occur. If yes -> it's probably a fault on our side. If not -> exposed does unwanted things.
From my experience: clean installation is really stable and reliable.
Anything you add or modify can cause additional problems - easy rule of thumb.
And for exposed and co. I can't give any help.

 

[Royal.Bengal]

Androidfilehost download issue

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

Great to see this development of ROM for Amami. Not sure what the reason might be, having trouble to download from Androidfilehost. No issue with the microG version but the vanilla one. Tried couple of days, different times but same issue: no download mirror found! Can you please take a look? Thanks in advance.

 

[lm089]

Great to see this development of ROM for Amami. Not sure what the reason might be, having trouble to download from Androidfilehost. No issue with the microG version but the vanilla one. Tried couple of days, different times but same issue: no download mirror found! Can you please take a look? Thanks in advance.

Can confirm, getting the same error right now from both my tablet and a PC browser. Been able to d'load yesterday, though.

 

[MSe1969]

Edit#2: got it! Step 11 in my case should have been 'sh migration.sh official' instead; this way it worked, and flashing signed ROM build 20181229 then worked as expected. :good:

Hmm, okay, will update the OP accordingly. Thanks