Related
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:
ANT Radio Service (Github) / (Google play)
ANT+ Plugin Service (Github) / (Google play)
afterwards setting proper permissions is essential!
Go to Apps & Notifications -> See All Apps
Select 'ANT Radio Service'
Select Permissions
Select Additional permissions
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
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
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
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)?
lm089 said:
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)?
Click to expand...
Click to collapse
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)
Good firmware! All with the coming!
MSe1969 said:
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.
Click to expand...
Click to collapse
Hmm - can't see those instructions mentioned in op
lm089 said:
Hmm - can't see those instructions mentioned in op
Click to expand...
Click to collapse
I just added them
there are no mirrors to download the standard version
UPDATE: now, yes
115ek said:
I just added them
Click to expand...
Click to collapse
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
CyanoFriend said:
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
Click to expand...
Click to collapse
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?
CyanoFriend said:
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
Click to expand...
Click to collapse
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)?
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.
MSe1969 said:
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?
Click to expand...
Click to collapse
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
CyanoFriend said:
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
Click to expand...
Click to collapse
But nfc and magisk are working
115ek said:
I just added them
Click to expand...
Click to collapse
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:
kamikaze1204 said:
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.
Click to expand...
Click to collapse
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.
CyanoFriend said:
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
Click to expand...
Click to collapse
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.
Androidfilehost download issue
MSe1969 said:
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
Click to expand...
Click to collapse
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.
Royal.Bengal said:
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.
Click to expand...
Click to collapse
Can confirm, getting the same error right now from both my tablet and a PC browser. Been able to d'load yesterday, though.
lm089 said:
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:
Click to expand...
Click to collapse
Hmm, okay, will update the OP accordingly. Thanks
This thread is discontinued - please visit the LineageOS 17.1 sucessor thread
This thread aims at providing LineageOS 16.0 builds for the Sony Xperia Z1 compact with current security patches.
You can consider this thread as a successor of our LineageOS 15.1 thread, where you may also find some useful information.
This is the joint effort of 115ek and MSe1969 (contributions welcome).
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
We offer two build variants:
A. Standard LineageOS 16.0 build
This build flavor aims at providing LineageOS 16.0 "as is" with most recent security patches.
If you want to install Google Apps (GApps) you have to use this build variant.
GApps are optional, of course. The smaller the GApps package, the better (pico). If you want "Okay google" support you need at least nano.
Just check the package comparison to see what fits your needs.
B. Pre-installed microG build variant with additional security patches
For the security/privacy focused (more details about below feature list, see here)
Pre-installed microG and F-Droid same as the LineageOS for microG project
Pre-installed AuroraStore
eSpeak TTS engine (FOSS TTS solution)
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 and other sensors
Cloudflare as default DNS (instead of Google)
Privacy-preferred default settings
Optional blocking of Facebook- and Google-Tracking
Optional disable captive portal detection
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
Constified JNI method tables
Status
List template by AdrianDC
Code:
- Boot : Ok
- Partitions (Data, Cache) : Ext4 and F2FS supported
- Bluetooth : Ok
- WiFi : Ok
- WiFi Hotspot : only 2.4 GHz
- RIL - Phone - Data : Ok
- GPS : Ok
- Camera : Ok
- Camcorder : Ok
- Lights : Ok
- MicroSD : Ok
- Accelerometer : Ok
- Compass : Ok
- Gyroscope : Ok
- Touchscreen : Ok
- FM Radio : Ok (mono)
- ANT+ : Ok
- Vibrator : Ok
- Microphone : Ok
- Audio & music : Ok
- Bluetooth audio : Ok
- MHL: broken
- NFC : Ok
- Kernel : Ok
- Graphics : Ok
- 3D Rendering : Ok
- Clock : Ok
- Offline Charging : Ok
- USB : Ok
- USB OTG : Ok
- Encryption : Ok
- SEPolicies : Enforcing
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)
ANT+ does not work fixed (see FAQ)
installing Magisk 19.1 prohibits entering recovery fixed with 20190521 build
GPS gets wrong time due to GPS week rollover since 3rd November 2019 (of importance when you record GPS tracks for example).
This also happens on stock and several other legacy devices. fixed with 20190611 build
Click to expand...
Click to collapse
Download
SourceForge
Click to expand...
Click to collapse
FAQ
What recovery system to use?
Please use this TWRP if you want to use OTA updates and/or encryption.
Click to expand...
Click to collapse
What about root access?
Root isn't included per default (except root over adb, but it's off by default).
If you want to gain root access to your apps use one of these (depending on your taste/needs):
Official Lineage Add-on https://download.lineageos.org/extras use su (arm) 16.0 here and flash via TWRP
Magisk https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Please note there is an issue starting with Magisk 19.1 which leads you to being unable to boot to recovery in any way. More info
Click to expand...
Click to collapse
ANT+ isn't working?
You need the 2 apps:
ANT Radio Service (Github) / (Google play)
ANT+ Plugin Service (Github) / (Google play)
afterwards setting proper permissions is essential!
Go to Apps & Notifications -> See All Apps
Select 'ANT Radio Service'
Select Permissions
Select Additional permissions
Slide switch to allow using of ANT hardware
This refers to those instructions which worked for me
Click to expand...
Click to collapse
I've got problems AND have magisk/exposed installed
I won't support anything related to magisk/exposed/other heavily system modifying things.
If you're encountering problems please make sure you're using a clean installation (at most gapps) to verify/reproduce the issue.
Click to expand...
Click to collapse
Bugreports
You'll find information about logging here.
Please also note how you got the error or how it can be reproduced.
Click to expand...
Click to collapse
Sources
Kernel: https://github.com/lin16-microg/android_kernel_sony_msm8974
Manifest: https://github.com/lin16-microg/local_manifests
Click to expand...
Click to collapse
Credits
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
LineageOS team
Click to expand...
Click to collapse
Installation instructions
Please see the OP of our (deprecated) LineageOS 15.1 thread or also here
Click to expand...
Click to collapse
Changelog
13.12.2020
ASB Security string 2020-12-01 (this month, no kernel updates found)
Webview updates for both builds (microG build on M87)
microG build only: F-Droid updated to 1.10-alpha1-114
microG build only: microG updated from upstream to 0.2.14.204215-15 (picked until 720b089)
Expand for older changelogs:
10.11.2020
ASB Security string 2020-11-05
Fix for CVE-2020-15999
AOSP E-Mail widget fixed
Webviews upodated to/within M86
microG build only: microG - fixes in EN API and GCM
microG build only: Replaced weak F-Droid signatures with ROM's V2 signatures
13.10.2020
ASB Security string 2020-10-05
microG build only: Bromite Webview on M86
microG build only: microG 0.2.12.203315 - including "Exposure notification API" for use of Covid tracing apps
microG build only: Additional hardening: constified JNI method tables
13.09.2020
ASB Security string 2020-09-05
Webviews on M85
microG build only: Added eSpeak TTS engine (microG build variant)
09.08.2020
ASB Security string 2020-08-05
Webviews on M84
microG build only: Location of firewall UI now in Network => data usage (Settings menu)
12.07.2020
ASB Security string 2020-07-05
microG build only: updated prebuilt microG GmsCore fom /e/ project (fixed FCM registration issues)
microG build only: F-Droid updated to 1.8 / F-Droid privileged extension updated to 0.2.11
microG build only: Aurorastore updated to 3.2.9 / AuroraServices updated to 1.0.6
11.06.2020
Security string 2020-06-05
GPS improvements / modernisation
Enable MIDI support
microG build only: Bromite Webview on M83
microG build only: Netmonitor exception in SEPolicy f. "Tracker Control" app
09.05.2020
Security string 2020-05-05
Standard build only:System Webview on M81
microG build only: AuroraStore updated to 3.2.8
11.04.2020
Security string 2020-04-05
Fix for CVE-2020-8597 (external/ppp)
Kernel: CVE-2019-10638 siphash 128bit for IP generation
microG build only: AuroraStore updated to 3.2.4
microG build only: Bromite Webview on M81
07.03.2020
Security string 2020-03-05
System Webviews on M80
2nd build variant 'hardened microG build' (known from 15.1 thread) available
microG build only: AuroraStore updated to 3.2.0
19.02.2020
fixed DRM (we now have widevine Level 3, Netflix for example runs fine)
fixed TWRP time bug
added option to prevent USB gadgets working when screen locked (trust HAL)
enabled changelog (can be accessed under /settings/system/updater/changelog)
synced LineageOS sources (security patch level February 05, 2020)
16.01.2020
synced LineageOS sources (security patch level January 05, 2020)
13.12.2019
synced LineageOS sources (security patch level December 05, 2019)
13.11.2019
fixed unreliable SMS/MMS receiving (https://review.lineageos.org/c/LineageOS/android_vendor_lineage/+/262653)
synced LineageOS sources (security patch level November 05, 2019)
19.10.2019
synced LineageOS sources (security patch level October 05, 2019)
13.09.2019
bring back wifi display
three finger screenshot gesture
synced LineageOS sources (security patch level September 05, 2019)
12.08.2019
fixed manual mobile network selection (once again)
synced LineageOS sources (security patch level August 01, 2019)
07.07.2019
synced LineageOS sources (security patch level July 05, 2019)
fixed AudioFX effects completely (thanks @NeoArian)
03.07.2019
start signing builds (please check this if you want to update)
enable OTA updates (thanks @NeoArian)
10.06.2019
synced LineageOS sources (security patch level June 05, 2019)
21.05.2019
fixed recovery issue introduced by Magisk versions starting with 19.1 (thanks @Myself5)
11.05.2019
synced LineageOS sources (security patch level May 05, 2019)
08.04.2019
fixed manual mobile network selection (thanks @SpiritCroc)
fixed problems with 5 GHz Wifi channels
added aptX/aptXHD
synced LineageOS sources (security patch level April 05, 2019)
11.03.2019
fixed alarm delay (came with new lineage sources)
fixed some more offline / USB charging problems (thanks @SpiritCroc)
synced LineageOS sources (security patch level March 05, 2019)
17.02.2019
fixed occasional camera problems (thanks @SpiritCroc)
various kernel patches (thanks @SpiritCroc)
synced LineageOS sources (security patch level February 05, 2019)
15.01.2019
fixed video playback for some applications (thanks @SpiritCroc)
fixed offline charging (thanks @SpiritCroc)
fixed FM radio (thanks @SpiritCroc)
updated webview to version 71 (thanks @MSe1969)
synced LineageOS sources
04.01.2019
initial release
Click to expand...
Click to collapse
XDA:DevDB Information
Lineage OS 16.0 for Xperia Z1 compact - amami, ROM for the Sony Xperia Z1 Compact
Contributors
115ek, MSe1969, SpiritCroc, drakonizer, rcstar6696, SuperLamic, AdrianDC, nailyk, LineageOS team
Source Code: https://github.com/lin16-microg/local_manifests
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Stable Release Date: 2020-11-10
Created 2019-01-04
Last Updated 2020-12-13
Changelog
The changelog was moved to the OP due to xda not allowing secondary thread owners to edit this post
Tips & Tricks
microG initial configuration after 1st install (microG build variant only)
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"
OTA Updates on an encrypted device
In case your device in encrypted and you have flashed apps creating "survival scripts" in /system/addon.d (e.g. Magisk), there *may* be a dependency to files in the data partition.
An OTA update until current TWRP 3.3.1 does not decrypt the data partition, as this is usually not needed - under specific circumstances however, this may lead to unwanted effects (up to a non-booting device!) during an OTA update, if such scripts aim at modifying files located in the data partition. If unsure, rather perform the update manually as dirty-flash in TWRP or - which in general is a good practice - regularly perform backups in TWRP. If you haven't flashed anything on top of my build (except for the LineageOS root addon, which is no problem), there shouldn't be any issue.
(This commit in TWRP indicates, that this potential issue will be solved in future TWRP releases).
Ok ok .
new build
New build:
15.01.2019
fixed video playback for some applications (thanks @SpiritCroc)
fixed offline charging (thanks @SpiritCroc)
fixed FM radio (thanks @SpiritCroc)
updated webview to version 71 (thanks @MSe1969)
synced LineageOS sources
https://androidfilehost.com/?fid=11410963190603900297
Important announcement:
There were problems with FM radio in lineage-16.0-20190114 which was linked one post above.
Please use lineage-16.0-20190115 from here: https://www.androidfilehost.com/?fid=11410963190603901105
Took a while, but last night I flashed this. And it's fabulous! Some observations, regarding your list in the OP (couldn't test everything, though):
GPS: not just OK but I had the fasted 3D fix since I moved away from stock! Much faster than with signed LOS 15.1 or munjeni's LOS 7.1.2 (well below 10 seconds from my living room window, down from sometimes 90 - 120 seconds!)
WiFi Hotspot: working good and reliably
Compass: somewhat working but GPS Test says "unreliable", and indeed compared to my tablet directions are off by several degrees (pointing to NNW where the tablet says N); attempts to calibrate didn't have any effect
FM radio: working but mono (you wrote that already)
USB OTG: working good and at least reading is about as fast as with other ROMs (USB stick is formatted NTFS, btw)
===
I flashed together with Magisk 18 and openGapps 9 pico
During first boot phone froze completely during boot animatoin; had to hard reset, then it booted fine into system
Google initial setup was a bit weird, had a FC first, then a short loop through the initial three screens, but after a few attempts it finally ran through.
Didn't do much more now, as I need my phone for, well, what you usually need a phone for , so I'm going back to 15.1 now. But the first few steps were extremely promising. Probably will be testing a bit more over the weekend.
Can't wait to use this as a daily driver! :good::good::good:
Using 15/01/2019.
Dirty flashed over last 15.1 (wiped cache/dalvik/system but kept data).
Working really well so far.
One thing I've noticed is that the UI seems a bit slower/somewhat choppier than 15.1, very slightly though. Barely noticeable, but the UI does seem to be a bit slower.
Other than that it's really impressive and is going to be my daily driver until/if something goes bad.
Another thing is twrp 3.2.3 backup restore of this rom seems to result in bootloop, but that might as well be because of me keeping data from 15.1.
lingowistico said:
Using 15/01/2019.
Dirty flashed over last 15.1 (wiped cache/dalvik/system but kept data).
Working really well so far.
One thing I've noticed is that the UI seems a bit slower/somewhat choppier than 15.1, very slightly though. Barely noticeable, but the UI does seem to be a bit slower.
Other than that it's really impressive and is going to be my daily driver until/if something goes bad.
Another thing is twrp 3.2.3 backup restore of this rom seems to result in bootloop, but that might as well be because of me keeping data from 15.1.
Click to expand...
Click to collapse
It's just my impression, but I've seen that sometimes the sense of slow UI may be just due to the speed of animations. Try changing the 3 scale animations on developer settings from 1x to 0.5x as is a common value
Sorry if this is the wrong place to ask this but: when using Dir file manager (super clean and light weight) I can't add home screen shortcuts to files for some reason. This worked on stock lollipop but not on Lineage 15.1 or 16.
How do I make this work again?
lingowistico said:
Sorry if this is the wrong place to ask this but: when using Dir file manager (super clean and light weight) I can't add home screen shortcuts to files for some reason. This worked on stock lollipop but not on Lineage 15.1 or 16.
How do I make this work again?
Click to expand...
Click to collapse
It's definitely a problem with the app itself.
I just tested my preferred file manager - Total Commander - and it worked fine.
Also ES did the job.
Only your mentioned Dir file manager wasn't able to do it.
It seems there is a new api to access shortcuts? Maybe they don't support it? Did you tried on an other device with Android >=8 ?
I just made a screenshot how it should look like (the confirmation dialog).
EDIT:
Yes. Had the right suspicion: https://github.com/veniosg/Dir/issues/126
It's a known app problem.
115ek said:
It's definitely a problem with the app itself.
I just tested my preferred file manager - Total Commander - and it worked fine.
Also ES did the job.
Only your mentioned Dir file manager wasn't able to do it.
It seems there is a new api to access shortcuts? Maybe they don't support it? Did you tried on an other device with Android >=8 ?
I just made a screenshot how it should look like (the confirmation dialog).
EDIT:
Yes. Had the right suspicion: https://github.com/veniosg/Dir/issues/126
It's a known app problem.
Click to expand...
Click to collapse
Thanks a lot for replying. For some reason, I assumed that Total Commander for Android was shareware/adware.
Hopefully Dir will be updated soon enough, meanwhile I'll be using Total Commander.
Thanks again for looking this up for me and for suggesting alternatives. :highfive:
After 1 month using this version 15.1.2019 every day, i have found this critical problems:
- camera (force closing)
- audiofx (not good working)
- sms app (when i receive sms phone is still vibrating)
- sometimes graphic artefacts on navigation buttons
- sometimes freezing when i use more apps
This rom is pretty, clean, without unuseful functions and this is why i like LineageOS. :good:
Jerri7 said:
After 1 month using this version 15.1.2019 every day, i have found this critical problems:
- camera (force closing)
- audiofx (not good working)
- sms app (when i receive sms phone is still vibrating)
- sometimes graphic artefacts on navigation buttons
- sometimes freezing when i use more apps
This rom is pretty, clean, without unuseful functions and this is why i like LineageOS. :good:
Click to expand...
Click to collapse
Concerning camera: I have this problems too (unregular) although I can't reproduce them. A reboot should help. @SpiritCroc has merged a commit that may be connected to this http://gerrit.aicp-rom.com/c/AICP/device_sony_msm8974-common/+/84248 though I'm not sure if it solves the problem. We'll see.
Concerning AudioFX: It's buggy in my opinion - independent of devices and android version. I also had issues with it on Oreo and on totally different devices. If someone has got a hint: feel free to share
Concerning SMS app: I also have issues here but I think it's related to the lineage code and nothing device specific. Keep in mind that Lineage 16 isn't officially released until now. If the next build is also buggy please provide a log.
Concerning the rest: Same as above --> LOS 16 isn't released and there are still issues left to fix.
I'll upload a new build soon. Let's see what it brings.
115ek said:
@SpiritCroc has merged a commit that may be connected to this http://gerrit.aicp-rom.com/c/AICP/device_sony_msm8974-common/+/84248 though I'm not sure if it solves the problem. We'll see.
Click to expand...
Click to collapse
If you didn't have that before, it should help; AICP didn't need it at first in comparison to lineage, but we included it now for a cleaner approach, see discussion here http://gerrit.aicp-rom.com/c/AICP/frameworks_base/+/84029
SpiritCroc said:
If you didn't have that before, it should help; AICP didn't need it at first in comparison to lineage, but we included it now for a cleaner approach, see discussion here http://gerrit.aicp-rom.com/c/AICP/frameworks_base/+/84029
Click to expand...
Click to collapse
Great! Thanks again for finding that
The new build is now available:
17.02.2019
fixed occasional camera problems (thanks @SpiritCroc)
various kernel patches (thanks @SpiritCroc)
synced LineageOS sources (security patch level February 05, 2019)
Micro Gapps
First: Thanks for the Update.
My question:
Mostly the Rom-Providers not using MicroG recommend Pico-Gapps for their builds.
I am using them too for all LOS-related Roms without problems.
Is there a special reason/need for your Rom to recommend Micro-Gapps instead?
CyanoFriend said:
First: Thanks for the Update.
My question:
Mostly the Rom-Providers not using MicroG recommend Pico-Gapps for their builds.
I am using them too for all LOS-related Roms without problems.
Is there a special reason/need for your Rom to recommend Micro-Gapps instead?
Click to expand...
Click to collapse
Yes, you're right. Generally spoken the smallest gapps package (pico) is the best in terms of performance (apart from no gapps package ).
Additionally you can easily install missing google apps from playstore afterwards (e.g. maps, youtube...). But there are apps/functionalities you can't get from the playstore, for example "Okay Google".
I just checked the gapps comparison again https://github.com/opengapps/opengapps/wiki/Package-Comparison
It seems nano is sufficient to get these functionalities (so with pico you won't get them). Maybe that was micro earlier... I don't know
But thanks for your hint, I'll update the thread accordingly.
115ek said:
It seems nano is sufficient to get these functionalities (so with pico you won't get them). Maybe that was micro earlier... I don't know
But thanks for your hint, I'll update the thread accordingly.
Click to expand...
Click to collapse
Since I opened my Z1c some 18 months ago I'm running the nano packages and am very happy with that. Same applies to my recently opened tablet z.
Hello.
sorry to interrupt you for a reason not directly related to this topic...
Does anybody of you know AdrianDC (who was part of the team of this Z1 ROM version also) and the way how to reach him?
Maybe you, 115ek?
I have a Sony Ericsson mobile (SEMC 2011 devices) and he was the one having released the only Lineage 14.1 ROM Nougat version for those models (cm13 has been released by 'LegacyXperia' group on basketbuild.com before). It runs perfectly except two remaining issues of the camera's audio function which should be the very last bug fix at it.
Unfortunately my direct messages on XDA to him don't seem to reach him (no read status).
Does anybody can help me to reach him?
I don't even know if the LegacyXperia team is still existing or where those developers have been moved to.
Thank you so much for any hint you can give to me!
Moderator Announcement: THREAD CLOSED on request of OP. If you're interested in the hardened LOS for the OnePlus 3 or 3T please follow this thread in the cross-device section in future: https://forum.xda-developers.com/oneplus-3/oneplus-3--3t-cross-device-development/rom-hardened-lineageos-16-0-oneplus-3t-t4034869
This thread is dedicated to provide hardened Lineage-OS 15.1 builds with microG included for the OnePlus 3/3T with current security patches.
This thread is discontinued, please visit the LineageOS 16.0 successor thread
Features of this ROM
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!)
Adapted LockClock app without wake-locks (fix of frozen weather widget after boot)
OTA Support
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 disabling of captive portal detection
Option to define own DNS
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
Option to deny new USB connections
Additional restrictions for secondary users
Increased password length
Kernel kept up to date with ASB patches and Google kernel/common 'android-3.18' branch
Current release levels
Security string: 2020-01-05
AOSP tag: 8.1.0_r52
Bromite System Webview: M79
Source-code and build instructions
Kernel: https://github.com/lin15-microG/android_kernel_oneplus_msm8996/tree/lin-15.1-microG
Build manifest: https://github.com/lin15-microG/local_manifests/tree/lin-15.1-microG
Installation Instructions
YOU ARE RESPONSIBLE SOLELY YOURSELF FOR ANY ACTIONS YOU DO WITH YOUR DEVICE !!!
Please note - I 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 of information available.
Pre-Requisites
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 the ROM and place it to your phone's internal memory
An unlocked bootloader (see e.g. LineageOS install instructions)
You need at least OxygenOS 5.0 firmware, otherwise you'll get error 7 when installing the zip. (Recommended 5.0.8 - DO NOT use 9.x firmware)
Install TWRP recovery
If you come from stock ROM and have just unlocked your boot loader, this is the next thing to do. I recommend to use the TWRP recovery for the OnePlus 3/3T. The following instructions are based on TWRP.
IMPORTANT NOTE - The official TWRP 3.2.3-1 is broken - DO NOT USE!
Please use the TWRP link in the official LineageOS install instructions instead.
To install TWRP, download the twrp-x.x.x-x-oneplus3.img file (Note: replace "x.x.x-x" in the following instructions with the respective values from the real file name) 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 recovery twrp-x.x.x-x-oneplus3.img
Afterwards, directly boot into 'recovery mode' (enter fastboot reboot on your PC and hold Power and vol.down) - DO NOT boot into 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 must be TWRP in recovery mode.
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". Swipe to confirm the deletion and get back into the main menu.
DO NOT flash Gapps!
This ROM comes with pre-installed microG. So don't attempt to flash Gapps.
Install ROM
In the TWRP main menu, choose "Install". A file manager appears to let you navigate to your internal memory (path /sdcard). 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 come from a different ROM (or stock firmware), make sure that you have performed the Wipe steps above.
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!
Dealing with signed builds
Please note, that this builds is signed with an own key. When you come from a different build, you cannot directly "dirty-flash" this build. You have to perform a "clean flash" (recommended), or - you do this on your own risk - you may try the below steps.
This happens at your own risk - make a backup with TWRP before!
Download and extract the file migration.sh from this archive
This file helps you to migrate from a build signed with the publicly available test keys (i.e. all builds around, which do not state that they are signed). If you come from another signed build (e.g. official LineageOS), you have to adapt the file accordingly (see below links).
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 and the "theory behind" can be found in the LineageOS wiki and AOSP reference.
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.
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.
Currently not working, hence not bundled
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.
Bug reports:
If you have a problem, please create a post with these informations:
Original Kernel shipped with this rom:
Build Date:
And try to get log as described here
Please note that I can't and won't support issues with builds using a different kernel or Xposed.
In regards to microG, I will try my best to help when it is related to this ROM (I use it myself), but any questions of the type "the YXZ-app can't do <some sort of fancy xyz Google functionality> properly" are better asked in the respective microG forums.
Credits
AOSP project
LineageOS project
microG project
CopperheadOS project
csagan5 (Bromite)
Yeriomin (Yalp)
XDA:DevDB Information
[ROM][Unofficial][8.1.0][microG][signed]hardened LineageOS 15.1 for Oneplus 3T, ROM for the OnePlus 3T
Contributors
MSe1969
Source Code: https://github.com/lin15-microG/local_manifests/tree/lin-15.1-microG
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
Based On: LineageOS
Version Information
Status: Stable
Stable Release Date: 2020-01-13
Created 2019-01-21
Last Updated 2020-04-30
Change Log
February 7th, 2020
Announcement to discontinue the LineageOS 15.1 builds - Please visit my LineageOS 16.0 thread, which continues with LineageOS 16.0 builds
January 14th, 2020
ASB Security string 2020-01-05
Bromite Webview on 79.0.3945.107
AuroraStore updated to 3.1.7
AuroraServices updated to 1.0.5
December 7th, 2019
ASB Security string 2019-12-05
Bromite Webview on 78.0.3904.119
AuroraStore updated to 3.1.5
November 10th, 2019
ASB Security string 2019-11-05
Bromite Webview on 78.0.3904.72
Updated microG GMS core 0.2.9.x
October 13th, 2019
ASB Security string 2019-10-06
AuroraStore updated to 3.1.3
Bromite Webview on 77.0.3865.104
September 10th, 2019
ASB Security string 2019-09-05
AuroraServices updated to 1.0.4
August 11th, 2019
ASB Security string 2019-08-05
Bromite Webview on 76.0.3809.100
Aurorastore 3.0.9 with AuroraServices install method
Updated microG GMS core 0.2.8.x
OTA Support
July 4th, 2019
ASB Security string 2019-07-05
Bromite Webview on 75.0.3770.109
June 12th, 2019
ASB Security string 2019-06-05
Kernel upstreamed to 3.18.140
Bromite Webview on 75.0.3770.86
Replaced Yalpstore with Aurorastore
Removed RemoteDroidGuard
Updated F-Droid & priv. extension
Updated microG GMS core 0.2.7.x
May 9th, 2019
ASB Security string 2019-05-05
SystemWebView: Bromite updated to 74.0.3729.106
Kernel: Upstreamed to 3.18.139
Backport of 'Deny new USB' feature
Option to set own DNS
Additional options for secondary users
Increased password length
April 8th, 2019
ASB Security string 2019-04-05
SystemWebView: Bromite updated to 73.0.3683.97
Kernel: Upstreamed to 3.18.138
Control switch in dev. settings for hosts file update
March 11th, 2019
ASB Security string 2019-03-05
SystemWebView: M73-Bromite (includes CVE-2019-5786)
Kernel: Upstreamed to 3.18.136
February 19th, 2019 - 2nd interim release
New upstreamed kernel (3.18.134) from here (yet w/o CAF tag LA.UM.6.5.r1-10600-8x96.0)
February 13th, 2019 - interim release
Reverted Kernel fixes, which seem to have caused crashes after wiping cache&dalvik
Prebuilt microG DroidGuard helper app to pass SafetyNet attestation
February 9th, 2019
ASB Security string 2019-02-05
SystemWebView: M72-Bromite
Kernel: CAF tag LA.UM.6.5.r1-10600-8x96.0
January 21st, 2019
Initial load
ASB Security string 2019-01-05
AOSP tag android-8.1.0_r52
SystemWebView: M71-Bromite
Initial feature list:
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
Security Hardening Features - Details
1. Pre-installed microG and F-Droid
same as the LineageOS for microG project
2. Pre-installed AuroraStore
works w/o having to enable the "unknown sources feature"
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
Until April 2019 build: Settings => Network & Internet => Data usage => Menu => "Apply iptables block script"
Starting with May 2019 build: Settings => Network & Internet (scroll down)
When activated, all outgoing connection attempts to Facebook servers will be suppressed.
Same applies to Google, but certain 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
Until April 2019 build: Settings => Network & Internet => Data usage => Menu => "Disable Captive Portal"
Starting with May 2019 build: Settings => Network & Internet (scroll down)
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
Further tips & tricks
Root
The ROM does not come with root baked in. A couple of features in this ROM even reduces the usual need for root.
Nevertheless, if you need/want to grant root permissions to some of your apps, the most popular options are:
Official LineageOS su addon (use 'addonsu-15.1-arm64-signed.zip')
Magisk (please search XDA on your own)
SuperSU
Note that I cannot and will not support any issues related to Magisk and/or SuperSU
Weather Widget
LineageOS does currently not offer Weather provider apps for LineageOS 15.1 for download (only for LineageOS 14.1)
I have built an APK for OpenWeatherMap for download from the LineageOS sources here, which works well with LineageOS 15.1
microG initial configuration after 1st install
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"
Firmware
You need at least OxygenOS 5.0 firmware, latest firmware recommended. Firmware updates (or downgrades, if needed) as flashable ZIP can be obtained e.g. here or here.
Do not confuse OnePlus 3 and OnePLus 3T firmware or you will brick your device!
Oooh thanks. I'll be having that!
Do you expect to release the 9.0 version when LOS 16 for 3T is ready?
sysak said:
Oooh thanks. I'll be having that!
Do you expect to release the 9.0 version when LOS 16 for 3T is ready?
Click to expand...
Click to collapse
Eventually yes - but not immediately, as I need some time to investigate to port the features.
MSe1969 said:
Eventually yes - but not immediately, as I need some time to investigate to port the features.
Click to expand...
Click to collapse
Maybe you can work together with nvertigo67, he has a rock solid los16 build. In the past, he has also promoted Android without Google Apps.
His thread: https://forum.xda-developers.com/on...oss-device-development/rom-nlos-16-0-t3879405
phoberus said:
Maybe you can work together with nvertigo67, he has a rock solid los16 build. In the past, he has also promoted Android without Google Apps.
His thread: https://forum.xda-developers.com/on...oss-device-development/rom-nlos-16-0-t3879405
Click to expand...
Click to collapse
Thanks for the information. I am aware of his thread and also his very knowledgeable feedbacks in the 'official' OP3T thread and I think I'll definitely try to get in touch with him.
For the time being however, I would like to concentrate on the "stable" LineageOS 15.1 (building also for the 'amami' device from same sources) to be used as a daily driver rather than bringing up a device for a new android version (I am actually not that good in this area). So I am somehow a little bit more "conservative"
this is something new ?
I'm new to this so my question is google playstore included??
and how is the gaming performance
Playstore not included
vip57 said:
this is something new
I'm new to this so my question is google playstore included??
and how is the gaming performance
Click to expand...
Click to collapse
Google play store is not included, but it had Pre installed yalp store. About gaming performance I can't comment because I don't play games.
Incase you are Intrested more info regarding micro g can be found here. https://microg.org/
Can you provide some additional information on how each step was done?
I'm specifically curious about the changes to Privacy Guard, changing the default DNS, and not submitting IMEI/IMSI/phone number on GPS requests
Thank you!
MXIIA said:
Can you provide some additional information on how each step was done?
I'm specifically curious about the changes to Privacy Guard, changing the default DNS, and not submitting IMEI/IMSI/phone number on GPS requests
Thank you!
Click to expand...
Click to collapse
The source code is linked in the OP (the link leads to the local build manifest) - you will find the commits for the features you've asked for always in the 'lin-15.1-microG' branch of my frameworks/base fork, for the sensors in PG additionally in frameworks/native and to make the PG switches visible, obviously packages/apps/Settings, always the 'lin-15.1-microG' branch.
Location services doesn't seem to be working and trying to access the location settings just fc the settings app.
Ahki767 said:
Location services doesn't seem to be working and trying to access the location settings just fc the settings app.
Click to expand...
Click to collapse
I am using this build myself w/o issues. Do you have a log?
One general advice: After 1st install, you should enter the microG settings and perform the setup as described in the link "LineageOS for microG" in OP. (I'll add a line telling this to the installation instructions)
EDIT: In short, click on 'unified NLP' and configure the location providers. Afterwards go to 'Self test' and click on each "unchecked" item and follow the instructions.
Huge thanks for the extra effort you gave to this. I was so excited when I week ago found this thread and yesterday got my Oneplus 3T and installed this.
Few questions: When I activate Iptables block script it breaks Spotify. I know spotify tries to connect graph.facebook.com so is this the cause? And can I edit iptables script somehow? I am quite newb with this stuff. Or maybe just disable script and edit Hosts file to add graph.facebook.com (its not there)? Though I would like to use this script.
eightfiveseven said:
Huge thanks for the extra effort you gave to this. I was so excited when I week ago found this thread and yesterday got my Oneplus 3T and installed this.
Few questions: When I activate Iptables block script it breaks Spotify. I know spotify tries to connect graph.facebook.com so is this the cause? And can I edit iptables script somehow? I am quite newb with this stuff. Or maybe just disable script and edit Hosts file to add graph.facebook.com (its not there)? Though I would like to use this script.
Click to expand...
Click to collapse
graph.facebook.com is FB's track&spy server, so unless you use an "original" FB product like their spy app or one of their messengers, there is no reason to allow any connection to FB. (OK, some people also allow their Login services spying on them...)
The reason, why Spotify breaks, is that Spotify is hosted on Google servers. I may think about adding the Spotify app to the exception list for Google (from its permissions however, this app seems also quite invasive, so not sure yet) This would mean that this app would still send tracking data to the Google trackers Ads, Crashlytics and DoubleClick and others (Spotify uses 9 trackers, according to Exodus, which is a lot!)
Yes, you can edit the script, but for this you need a root shell (e.g. via adb) - the script file is /system/bin/z_iptables and you would need to add the line com.spotify.music into the list under list_apps()
Regards, M.
MSe1969 said:
graph.facebook.com is FB's track&spy server, so unless you use an "original" FB product like their spy app or one of their messengers, there is no reason to allow any connection to FB. (OK, some people also allow their Login services spying on them...)
The reason, why Spotify breaks, is that Spotify is hosted on Google servers. I may think about adding the Spotify app to the exception list for Google (from its permissions however, this app seems also quite invasive, so not sure yet) This would mean that this app would still send tracking data to the Google trackers Ads, Crashlytics and DoubleClick and others (Spotify uses 9 trackers, according to Exodus, which is a lot!)
Yes, you can edit the script, but for this you need a root shell (e.g. via adb) - the script file is /system/bin/z_iptables and you would need to add the line com.spotify.music into the list under list_apps()
Regards, M.
Click to expand...
Click to collapse
Thanks for the info! I edited z_iptables to bypass Spotify and now its working. I also added graph.facebook.com to hosts file and to the z_iptables (graph.facebook.com IP is 31.13.71.1 and it was missing from iptables) and now its blocked (dont know which one is blocking it). Btw what does the number after IP mean? Example 31.13.24.0/21
But I still get some calling to settings.crashlytics.com, app.adjust.com and clients3.google.com according to my Pi-hole (which are blocked in it).
Might have to add them too.
Though my adb pull command for the Hosts file stopped working... (freezes in 14%) Any ideas why? This is first time I am doing anything like this so I'm bit nervous.
eightfiveseven said:
Thanks for the info! I edited z_iptables to bypass Spotify and now its working. I also added graph.facebook.com to hosts file and to the z_iptables (graph.facebook.com IP is 31.13.71.1 and it was missing from iptables) and now its blocked (dont know which one is blocking it). Btw what does the number after IP mean? Example 31.13.24.0/21
But I still get some calling to settings.crashlytics.com, app.adjust.com and clients3.google.com according to my Pi-hole (which are blocked in it).
Might have to add them too.
Though my adb pull command for the Hosts file stopped working... (freezes in 14%) Any ideas why? This is first time I am doing anything like this so I'm bit nervous.
Click to expand...
Click to collapse
Be careful!
The "/21" in 31.12.24.0/21 means range 31.12.24.0 . . . 31.12.31.255 and the also specified blocking entry 31.13.64.0/18 means 31.13.64.0 . . . 31.13.127.255, which includes 31.13.71.1 - further explanation of the subnets can be found e.g. here
Therefore, if you could still reach graph.facebook.com resolving to 31.13.71.1, the iptables config may not be effective at all (the calls to adjust and goole indicate so)! Please open a browser on your device and simply enter 'facebook.com' as address - if you are redirected to FB for logon, the firewall-blocking is inactive - in that case, please try to deactivate and reactivate the iptables block script and try again. If it persists, open an adb root shell, cd to /system/bin and execute the command ./z_iptables set and watch out for error messages.
MSe1969 said:
Be careful!
The "/21" in 31.12.24.0/21 means range 31.12.24.0 . . . 31.12.31.255 and the also specified blocking entry 31.13.64.0/18 means 31.13.64.0 . . . 31.13.127.255, which includes 31.13.71.1 - further explanation of the subnets can be found e.g.
Therefore, if you could still reach graph.facebook.com resolving to 31.13.71.1, the iptables config may not be effective at all (the calls to adjust and goole indicate so)! Please open a browser on your device and simply enter 'facebook.com' as address - if you are redirected to FB for logon, the firewall-blocking is inactive - in that case, please try to deactivate and reactivate the iptables block script and try again. If it persists, open an adb root shell, cd to /system/bin and execute the command ./z_iptables set and watch out for error messages.
Click to expand...
Click to collapse
Yes you were correct. Script was inactive but after I removed the IP I added the script started working again. Thanks again!
Hi,
Thank you for your work! I just have two questions: do you spread updates via normal OTA or do we have to go to this thread to check for updates? I will definitely root it too with Magisk, would I need to redo this after every update?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS With MicroGWith the rise of Big Tech and the encroachment of government on our lives, I felt more of a desire to move away from Google and the like. Samsung S7 Flat / Edge was built with microG and LineageOS source and is fully functional.
What it is. It's LineageOS with all of Google's closed-source binaries removed and replaced with microG. I.e. no Play services or GAPPS. UnifiedNLP is used as the networking location provider instead of Google's NLP. Aurora Store and F-Droid is installed by default and provides an alternative app store. However, with the Aurora Store, you cannot install all Google Play Store apps such as buy apps.
Other information Google Play Store Alternative If you want to have full access to normal Android Play Store apps, After opening Aurora Store, select the appropriate option. usually option number 1 is the most commonly used with this ROM, unless changed by the user. After setup, you will have access to all apps as usual. Some apps require Play Services and cannot be used.
After installation - Open the microG app --> self-check sections should be successful. Location Services - By default, LocalGsmNlpBackend, which uses the NominatimGeocoderBackend, and NominatimNlpBackend, which uses Mapquest's Noninatim service, are disabled. Open the microG app --> location modules and enable the modules you want. Then restart the device.
It is strongly advised not to install GApps as this ROM includes a replacement for them.
Disclaimer:
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Working features:
Wi-Fi (including hotspot)
- Sound
- Mali driver
- USB tethering
- HW secured video playback
- Ril (mobile data, calls, SMS and more)
- Sensors
- Buttons
- Bluetooth
- MTP
- 2D and 3D GPU acceleration
- HW encoding/decoding
- HWcomposer (HWC)
- Charging with device off
- camera
- GPS
- Fingerprint sensor
- Mobicore
- SW codecs
- Camera
Not Working on LineageOS 20.0 (13)
- Storage Encryption (WIP switching to FBE from FDE since FDE was removed in 13)
- Network trafic monitoring (WIP, same reason as bellow, uses BPF)
- BPF specific functions like fancy new GPU monitoring in Android 13
instructions (if coming from another ROM or Android version )
- Perform a backup of your current ROM (Optional)
- Install a compatible Recovery
- Wipe data & cache partitions and FORMAT DATA from TWRP (required !).
- Download the ROM
- save to internal memory or sd-card
- Flash ROM.
- Flash magisk (if needed)
- Reboot
Clean flash
Installation Via twrp
- Download the ROM from the website.
- Back up your data (recommended)
- Remove custom encryption pins/passwords (recommended)
- Boot into twrp go to Delete /Advanced - Wipe system / data / cache .
- back to the main menu go to install and find the location where you saved the rom.
- Flash the ROM
- Flash magisk (if needed)
- Reboot
Dirty flash (Update)
1) via OTA
2) Manual method
- Back up your data (recommended)
- Download the ROM from the website.
- Reboot to TWRP
- Flash the ROM
- Flash magisk (if needed)
- Reboot
how to boot into twrp from lineageos 19 system
settings>system>buttons> down to menu point Power menu
then activate Advanced restart.
now press the power button right , select reboot a second menu appears,
there you can select Recovery from and it will automatically boot into twrp.
Other information
Note that many features of LineageOS are not yet finished, this is not a device bug and please do not report them,
also do not file bug reports for known problems or bug reports without the correct
Do not publish bug reports without specifying logs (logcats) or steps to reproduce the bug.
a) Logcat
b) proc/last_kmsg
(or proc/kmsg)
c) data/tombstones
d) dmesg
Update monthly
Downloads or via OTA
Samsung S7 Flat = herolte
LineageOS 16.0 (9)
LineageOS 17.1 (10)
LineageOS 18.1 (11)
LineageOS 19.1 (12L)
LineageOS 20.0 (13)
Downloads or via OTA
Samsung S7 Edge = hero2lte
LineageOS 16.0 (9)
LineageOS 17.1 (10)
LineageOS 18.1 (11)
LineageOS 19.1 (12L)
LineageOS 20.0 (13)
If you would like to support the project,
feel free to buy me a coffee or beer.
PayPal
ROM Developer
Exodusnick
Device Maintainer:
ivan_meler
microG Source code :
android_vendor_partner_gms
docker-lineage-cicd
LineageOS source code :
https://github.com/LineageOS
Kernel:
android_kernel_samsung_universal8890
All credit goes to
@Ivan_Meler , @expressluke
@danielk43 for support and help.
Telegram Channel
Support for german users
Root / Custom-ROM's - Los-Legacy
Deine Android Community
forum.los-legacy.de
INFO
current ROM changelog
lineagos 20.0 (06/05/2023)
Spoiler: Changelog
06/05/2023
Build Date: 06/05/2023
changelog
=================
- Merged May 2023. Security update
- Synced with LineageOS source
changelog mircoG
=================
24.04.2023
changelog
- Switched to more source built components from new Exynos 850/Linaro BSP
hwcomposer
memtrack
libion_exynos
libGrallocWrapper
gralloc
libcsc
libexynosscaler
libexynosgscaler
libhwjpeg
Whole OMX stack (libOMX.Exynos.*) and stagefrighthw
- Cleaned up source and got rid of libutils vndk32 workaround
- Performance, stability and battery life improvements
- Updated selinux and removed neverallow rules to make device more secure
- Fixed some issues introduced in QPR2
big thanks to @Ivan_Meler
- Merged security update from April 2023
- Synced with LineageOS source source
20.03.2023
Changelog
many thanks to ivan_meler
- Added aptX HD support
- Misc performance and stability improvements
------------
- Merged March 2023 Security update
- Merged QPR2
- Synced with LineageOS source
Changelog microG
--
19.02.2023
Changelog .
- Synced with LineageOS source
- Merged Feb. 2022 security update
from ivan meler
- Improved UI performance
- Misc stability improvements
- Fixed race condition in rotation that would rarely prevent screen from waking up
Changelog microG
22.01.2023.
- Synced with LineageOS source
Changelog mircoG
- Update FDroid on 1.15.5
- Update on v0.2.27.223616
Releases · microg/GmsCore
09.01.2023
- Merged January 2023. Security update
- Camera app improvements
- Misc performance and stability improvements
- Synced with LineageOS source
Changelog mircoG
- unchanged
19.12.2022
- Synchronized with LineageOS source
- Fix signature spoofing patch restricted to yes,
The default web browser has no rights e.g. for downloads when signature spoofing patch is restricted..
10.12.2022.
- Merged december 2022. security update
- Merged android QPR1 December Update
- Synchronized with LineageOS source
- Update bromite WebView v108.0.5359.109
- Update bromite Browser v108.0.5359.109
02.12.2022
- Synced with LineageOS source
- update Bromite web browser+webviewer
update taken from ivan
- Cleaned up patches for non-BPF kernel
- Performance stability and battery life improvements
20.11.2022
- Synced with LineageOS sources
- Merged November 2022. Security update
- update bromite-WebView v107.0.5304.96
- update bromite Browser v107.0.5304.96
- repaired BT with BT key
https://github.com/lineageos4microg/docker-lineage-cicd/pull/359
27.10.2022
- Synced with LineageOS sources
add ota updater
Changelog mircoG
-
26.10.2022
- Synced with LineageOS sources
- Merged Oktober 2022. security update
- F-Droid in bulid
Changelog mircoG
v0.2.25.223616
NEW: Fido API (#849)
Push notifications
Fix lifting idle restrictions on Android 12. Thanks @grote
Fallback to port 443 in restricted networks. Thanks @matttbe
Exposure Notifications
Add required exports and flags for Android 12 to nearby-core. Thanks @fynngodau
Show weekday for reported exposures (#1743)
Move location permissions out of nearby-core to allow using the neverForLocation assertion in apps using it (#1796)
Device attestation
Add UI listing apps using SafetyNet. Thanks @iTrooz
Client Library
Add play-services-fido, play-services-oss-licenses and play-services-safetynet client library
lineagos 19.1 (22.06.2023)
Spoiler: Changelog
22/06/2023
Build Date: 22/06/2023
=================
changelog
- Merged June 2023. Security update
- Synced with LineageOS source
changelog mircoG
Update FakeStore 0.2.0
Build Date: 11/05/2023
=================
changelog
=================
- Misc performance and stability improvements
- Merged May 2023. Security update
- Synced with LineageOS source
changelog mircoG
=================
25/04/2023
changelog
- Switched to more source built components from new Exynos 850/Linaro BSP
hwcomposer
memtrack
libion_exynos
libGrallocWrapper
gralloc
libcsc
libexynosscaler
libexynosgscaler
libhwjpeg
Whole OMX stack (libOMX.Exynos.*) and stagefrighthw
- Performance, stability and battery life improvements
- Synced with LineageOS source
big thanks to @Ivan_Meler
- Merged security update from April 2023
- Synced with LineageOS source
Changelog microG
Update AuroraStore 4.2.1
Update FDroid to 1.16.3
23.03.2023
- Synced with LineageOS sources
- Merged March 2023 security update
Changelog mircoG
--
18.02.2023
Changelog
Update must be installed manually
because I had to generate a new release key.
- Synced with LineageOS sources
- Merged Feb. 2022 security update
Changelog mircoG
--
19.01.2023
- Synced with LineageOS source
Changelog mircoG
- Update FDroid von 1.15.4 FDroid zu 1.15.5
- Update v0.2.25.223616 to v0.2.27.223616
Releases · microg/GmsCore
Free implementation of Play Services. Contribute to microg/GmsCore development by creating an account on GitHub.
github.com
13.01.2023
- Merged January 2023. Security update
- Synced with LineageOS source
15.12.2022
- Synced with LineageOS sources
- Merged Dezember 2022. security update
18.11.2022
- Synced with LineageOS sources
- Merged November 2022. Security update
- update bromite-WebView v107.0.5304.96
- update bromite Browser v107.0.5304.96
Changelog mircoG
-update to v0.2.25.223616
NEW: Fido API (#849)
Push notifications
Fix lifting idle restrictions on Android 12.
Fallback to port 443 in restricted networks.
Exposure Notifications
Add required exports and flags for Android 12 to nearby-core.
Show weekday for reported exposures
Move location permissions out of nearby-core to allow using the neverForLocation assertion in apps using it
Device attestation
Add UI listing apps using SafetyNet.
Client Library
Add play-services-fido, play-services-oss-licenses and play-services-safetynet client library
Translations:
Add simplified chinese.
Update russian and belarusian.
Improvements and bug fixes (as always).
New features
Fido
The newly added Fido API allows using U2F and Fido devices via USB or NFC with supported Browsers (Chromium and Firefox) and to sign into your Google Account in microG. Additionally, on supported hardware and when a PIN/password is configured, the secure key storage can be used as a virtual Fido device. Note that some devices are still not fully supported.
Due to lack of open-source client library, open-source variants of browsers (Bromite, Fennec, etc) currently do not support this API. This release also provides an open-source play-services-fido library, which open-source browsers can use instead of the proprietary Google version to add support for microG's Fido API.
14.10.2022
- Synced with LineageOS sources
- Merged Oktober 2022. security update
- bromite WebView v105.0.5195.147
- bromite Browser v105.0.5195.147
From ivan
- Fixed samsungs bug with gps where it would start acting up over time due to time rollover bug
15.09.2022
- Synced with LineageOS sources
- Merged September 2022. security update
- bromite WebView v104.0.5112.91
- bromite Browser v104.0.5112.91
Changelog mircoG
no changes
22.07.2022
- fixed adb devices (thanks goes to ivan_Meler and daniel)
- remove LineageOS packages_modules_Connectivity
- add GrapheneOS packages_modules_Connectivity
for more information you can read here
GrapheneOS Frequently Asked QuestionsAnswers to frequently asked questions about GrapheneOS.
grapheneos.org
- update bromite-WebView to 103.0.5060.121
- update bromite Browser to 103.0.5060.121
- Synced with LineageOS sources
06.07.2022
add keystore patch from ivan_meler
- Fixed issues with keystore present in a lot of bank/secure apps like binance
- Fixed issue where setupwizard would crash when adding fingerprint due to bug in keystore
- Cleaned up patches required for build and removed unneeded ones
- Synced with LineageOS source
13.06.2022
- clean cache
- Synced with LineageOS sources
- android-12.1.0_r5 -> android-12.1.0_r7
- merged june 2022. security update
- merged June 2022. pixel feature drop (SQ3A.220605.009.A1)
09.06.2022
- clean cache
- Synced with LineageOS source
new security update has not yet been merged from lineageos
Changelog
von ivan_meler
- Improved in-call audio quality drastically
- Addressed few more selinux denials
- Improved general stability and performance
06.06.2022
- Synced with LineageOS source
1 day ago Add group audio to vendor.media.omx service 2022-06-04 15:08 UTC (android_frameworks_av)
2 days ago Camera2: add QR scanner QS tile 2022-06-03 21:15 UTC (android_packages_apps_Camera2)
2 days ago Camera2: add QR code launcher shortcut 2022-06-03 21:15 UTC (android_packages_apps_Camera2)
2 days ago Camera2: import quickReader module from Snap 2022-06-03 21:15 UTC (android_packages_apps_Camera2)
3 days ago lineage: RIP legacy qcom 2022-06-02 15:44 UTC (android)
3 days ago lineage: Move NXP NFC to a different section 2022-06-02 15:44 UTC (android)
3 days ago lineage: Remove Snap 2022-06-02 15:44 UTC (android)
3 days ago lineage: CodeAurora -> CodeLinaro 2022-06-02 15:44 UTC (android)
3 days ago lineage: Update qcom groups 2022-06-02 15:44 UTC (android)
4 days ago overlay: Exclude ImsService from location indicators 2022-06-01 14:47 UTC (android_vendor_lineage)
4 days ago overlay: Also exempt CneApp from location indicators 2022-06-01 14:47 UTC (android_vendor_lineage)
5 days ago overlay: Exempt Bluetooth from location indicators 2022-05-31 18:28 UTC (android_vendor_lineage)
5 days ago Seedvault: Redesign SUW activities for 12 2022-05-31 16:43 UTC (android_packages_apps_Seedvault)
6 days ago lineage: build: Wipe DTB/O OBJs before build 2022-05-30 23:37 UTC (android_vendor_lineage)
7 days ago LineageParts: Improve easter egg activity style 2022-05-29 22:22 UTC (android_packages_apps_LineageParts)
- update bromite-WebView to 102.0.5005.92
- update bromite Browser to 102.0.5005.92
29.05.2022
- update bromite web view 102.0.5005.67
- update bromite Browser 102.0.5005.67
- Synced with LineageOS source
by ivan meler
26.05.2022.
- Updated libexynosdisplay from BSP to comply with some android 12 changes
- Removed unused build.prop entries
- Fixed few selinux denials related to hwc props
- Improved UI performance and stability
- Removed more unneeded patches for device support
lineagos 18.1 (13.06.2023)
Spoiler: Changelog
Changelog 06.13.2023
- Synced with LineageOS sources
- Merged June security update
Changelog microG
Update FakeStore 0.2.0
Changelog 13.05.2023
- Switch to more source-based components from the new Exynos 850/Linaro BSP
hwcomposer
memtrack
libion_exynos
libGrallocWrapper
gralloc
libcsc
libexynosscaler
libexynosgscaler
libhwjpeg
Entire OMX stack (libOMX.Exynos.*) and stagefrighthw
- Performance, stability and battery life improvements
many thanks to @ivanmeler :respect:
- Merged May 2023. security update
- Synchronised with LineageOS sources
Changelog mircoG
-------
Build Date: 25/04/2023
- Synchronised with LineageOS sources
- merged April 2023 Security update
Changelist mircoG
Update AuroraStore 4.2.1
Update FDroid 1.16.3
25.03.2023
- Synced with LineageOS sources
- Merged March 2023 security update
Changelog microG
no changes
17.02.2023.
- Merged February 2023. Security update
- Synced with LineageOS source
update must be installed manually ,
because I had to generate a new release key.
Changelog mircoG
no changes
20.01.2023
- Synced with LineageOS source
Changelog mircoG
- Update FDroid von 1.15.4 FDroid zu 1.15.5
- Update v0.2.25.223616 to v0.2.27.223616
Releases · microg/GmsCore
Free implementation of Play Services. Contribute to microg/GmsCore development by creating an account on GitHub.
github.com
14.01.2023
Changelog mircoG
----
- Merged January 2023. Security update
- Synced with LineageOS source
17.12.2022
- Synced with LineageOS sources
- Merged Dezember 2022. security update
16.11.2022
- Synchronized with LineageOS sources
- Merged November 2022. security update
- bromite WebView v106.0.5249.163
- bromite Browser v106.0.5249.163
Change list mircoG
-update to v0.2.25.22361
13.102022
- Synced with LineageOS sources
- Merged Oktober 2022. security update
- update bromite WebView v105.0.5195.147
- update bromite Browser v105.0.5195.147
from Ivan
- Fixed samsungs bug with gps where it would start acting up over time due to time rollover bug
14.09.2022
- Synced with LineageOS sources
- Merged September 2022. security update
- bromite WebView v104.0.5112.91
- bromite Browser v104.0.5112.91
12.08.2022
- Synced with LineageOS sources
- Merged August 2022. security update
- Added FDroidPrivilegedExtension and FDroid
in system app
F-Droid apps can now be installed automatically ,
if this option is enabled.
- update bromite WebView v104.0.5112.63
- update bromite Browser v104.0.5112.63
14.07.2022
- Synced with LOS sources
- Bump Security String to 2022-07-05
- update bromite-WebView 103.0.5060.121
- update bromite Browser 103.0.5060.121
13.06.2022
- Synced with LOS sources
- Bump Security String to 2022-06-05
- update bromite-WebView 102.0.5005.92
- update bromite Browser 102.0.5005.92
15.05.2022
- Synced with LOS sources
- Bump Security String to 2022-05-05
- update Bromite Browser Version to 101.0.4951.69
- update Bromite WebView Version to 101.0.4951.69
lineagos 17.1 (23.4.2023) no support anymore
Spoiler: Changelog
23.04.2023
no support anymore
16.02.2023
- Synced with LineageOS sources
- Merged Feb. 2023 security update
Changelog mircoG
no changes
20.01.2023
- Synced with LineageOS source
- Merged January 2023. Security update
Changelog mircoG
- Update FDroid von 1.15.4 FDroid to 1.15.5
- Update to v0.2.27.223616
Releases · microg/GmsCore
17.12.2022
- Synchronized with LineageOS sources
- Merged Dezember 2022. security update
15.11.2022
- Synced with LineageOS sources
- Merged November 2022. security updates
- update bromite WebView v106.0.5249.163
- update bromite Browser v106.0.5249.163
Changelog mircoG
-update to v0.2.25.223616
12.10.2022
- Synced with LineageOS sources
- Merged October 2022. security update
- bromite WebView v105.0.5195.147
- bromite Browser v105.0.5195.147
14.09.2022
-Synced with LineageOS sources
- Merged September 2022. security update
- bromite WebView v104.0.5112.91
- bromite Browser v104.0.5112.91
12.08.2022
- Synced with LineageOS sources
- Merged August 2022. security update
- Added FDroidPrivilegedExtension and FDroid
in system app
F-Droid apps can now be installed automatically ,
if this option is enabled.
- update bromite WebView v104.0.5112.63
- update bromite Browser v104.0.5112.63
21.07.2022
Changelog
- Synced with LOS Sources
- Bump Security String to 2022-07-05
- update Bromite Browser Version to 103.0.5060.126
- update Bromite WebView Version to 103.0.5060.126
25.06.2022
Changelog
- Synced with LOS Sources
- Bump Security String to 2022-06-05
- update Bromite Browser Version to 102.0.5005.96
- update Bromite WebView Version to 102.0.5005.96
26.05.2022
- Synced with LOS sources
- Bump Security String to 2022-05-05
- update Bromite Browser Version to 101.0.4951.69
- update Bromite WebView Version to 101.0.4951.69
lineagos 16.0 (23.04.2023) no support anymore
Spoiler: Changelog
23.04.2023
no support anymore
20.02.2022
Changelog
- Mit LineageOS-Quellen synchronisiert
- Merged P_asb_2023-2 Security update
Changelog microG
--
22.01.2023
- Synced with LineageOS source
- Merged P_asb_2023-01 Security update
Changelog mircoG
- Update FDroid von 1.15.4 FDroid to 1.15.5
- Update to v0.2.27.223616
19.12.2022
- Mit LineageOS-Quellen synchronisiert
- Merged P_asb_2022-12 Security update
Changelog mircoG
v0.2.26.223616
18.11.2022
- Synchronized with LineageOS sources
- merged November 2022. security update via backport
bugs caused by version v0.2.25.223616 :
googel SafetyNet crashes in microG settings
as well as add googel account.
The Rom must be installed manually via twrp because the singned.key is not the same ota check fails.
(OTA will only work again with the next update)
Woks
- Singnature Spoofing
- AuronaStore + googel account / all purchase apps
- F-droid
- all basic functions
Changelog mircoG
update to v0.2.25.223616
Release v0.2.25.223616 · microg/GmsCore
Changelog NEW: Fido API (#849) Push notifications Fix lifting idle restrictions on Android 12. Thanks @grote Fallback to port 443 in restricted networks. Thanks @matttbe Exposure Notifications ...
github.com
Reserved
really nice rom, thanks for all the work.
but i have one question, do you have "in pocket detection" activated ?
i´ve read a lot online about this feature build in to lineageos, but it has to be activated by the developer.
because i have the problem, that my phone unlocks or skips music in my pocket every time.
with friendly greetings
Charly Schulte
edit:
also i am missing the microG Settings, can you help me with that ?
@charlyschulte see Attached Thumbnails
what do you mean by that ?
but i have one question, do you have "in pocket detection" activated ?
i´ve read a lot online about this feature build in to lineageos, but it has to be activated by the developer.
Thanks for this new build, it works very well so far.
@Exodusnick How come you provide the builds but @turbolukex5 started the thread? What is the idea behind this setup?
Exodusnick said:
@charlyschulte see Attached Thumbnails
what do you mean by that ?
but i have one question, do you have "in pocket detection" activated ?
i´ve read a lot online about this feature build in to lineageos, but it has to be activated by the developer.
Click to expand...
Click to collapse
I dont have these settings and i dont know why
charlyschulte said:
I dont have these settings and i dont know why
Click to expand...
Click to collapse
But i have lineageos micro g installed
tablord said:
Thanks for this new build, it works very well so far.
@Exodusnick How come you provide the builds but @turbolukex5 started the thread? What is the idea behind this setup?
Click to expand...
Click to collapse
Doesn't matter weir created the thread
@turbolukex5 Is my colleague
charlyschulte said:
But i have lineageos micro g installed
Click to expand...
Click to collapse
see here i just installed clean and the microg settings are available .
Exodusnick said:
see here i just installed clean and the microg settings are available .
Click to expand...
Click to collapse
Weird ... Just flashed it and made the ota update ...
---------- Post added at 08:12 PM ---------- Previous post was at 08:07 PM ----------
Exodusnick said:
see here i just installed clean and the microg settings are available .
Click to expand...
Click to collapse
Should i try dirty flash again? I dont want to loose my data again ^^
charlyschulte said:
Weird ... Just flashed it and made the ota update ...
---------- Post added at 08:12 PM ---------- Previous post was at 08:07 PM ----------
Should i try dirty flash again? I dont want to loose my data again ^^
Click to expand...
Click to collapse
what kind of data ? how did you actually install the rom? did you install clean ?
you can't tell me that you don't have microg settings, I don't think so. post a screenshot of your apps.
Exodusnick said:
what kind of data ? how did you actually install the rom? did you install clean ?
you can't tell me that you don't have microg settings, I don't think so. post a screenshot of your apps.
Click to expand...
Click to collapse
I did a clean install.
charlyschulte said:
I did a clean install.
Click to expand...
Click to collapse
Tried dirty flash newest update again. APP still missing
new update vie ota available
Upload to OTA server
Create MD5 checksum file
Transfer Rom to database
URL: https://www.los-legacy.de/16.0/herolte
Filename: lineage-16.0-20190506-UNOFFICIAL-microG-signed-herolte.zip
Device: herolte
Storage Directory:data/lineageos_updates
os_patch_level 05.04.2019
OS Version: 16.0
2019-05-06 21:01:56
Romtype: unofficial-microg-signed
MD5SUM: 519e596dec93b91171ac28d92bf4ced0
sha256sum: 3c1a511c423ac9bec2709a73ddf95c740c82953c8753f7c4fb7dc4197a7a5ff8
SIZE: 566097431
Changelog
Synced with los source
new build available via OTA-update
Upload to OTA server
Create MD5 / SHA256 checksum file
Transfer Rom to database
URL: https://www.los-legacy.de/16.0/herolte
Filename: lineage-16.0-20190510-UNOFFICIAL-microG-signed-herolte.zip
Device: herolte
Storage Directory:data/lineageos_updates
OS_patch_level 05.05.2019
OS Version: 16.0
2019-05-10 18:10:42
BUILD_TYPE=release
Romtype: unofficial-microg-signed
MD5SUM: c21d9a6ec2e6f3e459f2ade44bf7e4ab
SHA256SUM: 4d8bdeabfe23c25cc862566bd7d3e694bfc54aea0f29c3714376addc4181e46c
SIZE: 566016826
Synced with los source
OS_patch_date 05.04. to 05.05.2019
manifest: android-9.0.0_r35 to android-9.0.0_r37
see Changelog
Great ROM. Excellent battery life. Was seriously happy to get rid of Google. Sincere thanks to you!
My only issue is frequent "microG has stopped" popups.
Also, all my contacts randomly disappear after a couple hours. I have made sure all my contacts save to device and that is the account being used, but all of them disappear hours after I restore them.
Any suggestions?
@cypress16
I'm afraid I have no idea why. However, I do not lose any contacts.
I also don't have any problems with "microG has stopped" popups.
Please remember it's a beta version of Ivan_Meler as there might be some bugs as well. But so far I couldn't find any .
It can also be that microG has to set itself up correctly on the system until everything really works well.
new build available via OTA-update
Upload to OTA server
Create MD5 checksum file
Transfer Rom to database
URL: https://www.los-legacy.de/16.0/herolte
Filename: lineage-16.0-20190517-UNOFFICIAL-microG-signed-herolte.zip
Device: herolte
Storage Directory: data/lineageos_updates
OS_patch_level 05.05.2019
OS Version: 16.0
2019-05-17 11:30:45
Bulid_Type=release
Updated kernel to 3.18.139
Romtype: unofficial-microg-signed
sha256sum:2b1797f5ffb57de030e6e458cbaf956fabfb5faa1f1893d7622f56c37a5e38e1
SIZE: 566201191
Changelog from 17.05.2019.
Synced with los source
https://www.los-legacy.de/herolte/16.0/changes/1558092645/
Hey, it's normal with this ROM that SafetyNet Check doesn't pass ctsProfile? Of course after install MicroG DroidGuard helper?
For now i installed NanoDroid version and it pass SafetyNet without problems.
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 LineageOS 16.0 thread, where you may also find some useful information.
This is the joint effort of 115ek and MSe1969 (contributions welcome).
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
We offer two build variants:
A. Standard LineageOS 17.1 build
This build flavor aims at providing LineageOS 17.1 "as is" with most recent security patches.
If you want to install Google Apps (GApps) you have to use this build variant.
GApps are optional, of course. The smaller the GApps package, the better (pico). If you want "Okay google" support you need at least nano.
Just check the package comparison to see what fits your needs.
B. Pre-installed microG build variant with additional security patches
For the security/privacy focused (more details about below feature list, see here)
Pre-installed microG and F-Droid same as the LineageOS for microG project
Pre-installed AuroraStore
eSpeak TTS engine (FOSS TTS solution)
Bromite as default browser
Additional security hardening features listed below
Cloudflare as default fallback DNS (instead of Google)
Privacy-preferred default settings
Optional blocking of Facebook- and Google-Tracking (Settings - Network & Internet)
Optional disable captive portal detection or choose from various providers (default is GrapheneOS and not Google; Settings - Network & Internet)
Increased max. password length of 64
No submission of IMSI/phone number to Google/Sony when GPS is in use
Default hosts file with many blocked ad/tracking sites
Privacy-enhanced Bromite SystemWebView
Extra control of sensor access for additionally installed user apps (Special access under app permissions)
Firewall (control internet access per app - under Trust)
Constified JNI method tables
Status
List template by AdrianDC
Code:
- Partitions (Data, Cache) : Ext4 and F2FS supported
- Bluetooth : Ok
- WiFi : Ok
- WiFi Hotspot : Ok
- RIL - Phone - Data : Ok
- GPS : Ok
- Camera : Ok
- Camcorder : Ok
- Lights : Ok
- MicroSD : Ok
- Accelerometer : Ok
- Compass : Ok
- Gyroscope : Ok
- Touchscreen : Ok
- FM Radio : Ok (mono)
- ANT+ : Ok
- Vibrator : Ok
- Microphone : Ok
- Audio & music : Ok
- Bluetooth audio : Ok
- MHL: broken
- NFC : Ok
- Kernel : Ok
- Graphics : Ok
- 3D Rendering : Ok
- Clock : Ok
- Offline Charging : Ok
- USB : Ok
- USB OTG : Ok
- Encryption : Ok
- SEPolicies : enforcing
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)
MHL does not work
5 GHz hotspot does not work (2.4 GHz hotspot works fine) (5 GHz option disabled with 2020-03-11 build as it isn't even available on stock)
GPS gets wrong time due to GPS week rollover since 3rd November 2019 (of importance when you record GPS tracks for example). fixed with 20200520 build
Using GApps AND encrypting the device may result in bootloops. More infos here.
Standard Trebuchet Launcher shows small artifacts in the fonts of app names in some situations.
Click to expand...
Click to collapse
Download
SourceForge
Click to expand...
Click to collapse
FAQ
What recovery system to use?
Please use this TWRP if you want to use OTA updates and/or encryption.
Click to expand...
Click to collapse
What about root access?
Root isn't included per default (except root over adb, but it's off by default).
If you want to gain root access to your apps use magisk (everything > 20.4 is broken):
Magisk https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
ANT+ isn't working?
You need the 2 apps:
ANT Radio Service (Github) / (Google play)
ANT+ Plugin Service (Github) / (Google play)
afterwards setting proper permissions is essential!
Go to Apps & Notifications -> See All Apps
Select 'ANT Radio Service'
Select Permissions
Select Additional permissions
Slide switch to allow using of ANT hardware
This refers to those instructions which worked for me
Click to expand...
Click to collapse
I've got problems AND have magisk/exposed installed
We won't support anything related to magisk/exposed/other heavily system modifying things.
If you're encountering problems please make sure you're using a clean installation (at most gapps) to verify/reproduce the issue.
Click to expand...
Click to collapse
Bugreports
You'll find information about logging here.
Please also note how you got the error or how it can be reproduced.
Click to expand...
Click to collapse
Sources
Kernel: https://github.com/lin17-microg/android_kernel_sony_msm8974
Manifest: https://github.com/lin17-microg/local_manifests
Click to expand...
Click to collapse
Credits
SpiritCroc: big thanks to him for maintaining the device trees and a lot of very useful hints
NeoArian: also big thanks to him
rcstar6696
SuperLamic
drakonizer
AdrianDC
munjeni: thanks for tips and tricks
nailyk: thanks for tips and tricks
All the other contributors on sony msm8974 platform
LineageOS team
Click to expand...
Click to collapse
Installation instructions
Please see the OP of our (deprecated) LineageOS 15.1 thread or also here
Click to expand...
Click to collapse
XDA:DevDB Information
Lineage OS 17.1 for Xperia Z1 compact - amami, ROM for the Sony Xperia Z1 Compact
Contributors
115ek, MSe1969, SpiritCroc, NeoArian, drakonizer, rcstar6696, SuperLamic, AdrianDC, nailyk, LineageOS team
Source Code: https://github.com/lin17-microg/local_manifests
ROM OS Version: Android 10
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Stable Release Date: 2020-12-29
Created 2019-11-22
Last Updated 2021-10-11
Changelog
11.10.2021
ASB Security string 2021-10-05
standard build only:
System Webview on 94.0.4606.71
microG build only:
Bromite System Webview and Browser updated to 93.0.4577.83
12.09.2021
ASB Security string 2021-09-05
Kernel: Further sec. patches applied (Divest-OS)
microG build only:
microG 0.2.22.212658-2
07.08.2021
ASB Security string 2021-08-05
standard build only:
System Webview on 91.0.4472.164
microG build only:
Bromite System Webview and Browser updated to 92.0.4515.134
F-Droid updated to 1.13
Fix in WiFi randomization
10.07.2021
ASB Security string 2021-07-05
Kernel: Many sec. patches applied (taken from Divest-OS, thanks to @SkewedZeppelin)
standard build only:
System Webview on 91.0.4472.101
microG build only:
Bromite System Webview and Browser updated to 91.0.4472.146
microG 0.2.21.212158-2
AuroraStore 4.0.7
14.06.2021
ASB Security string 2021-06-05
A few kernel patches
microG build only:
Bromite System Webview and Browser updated to 91.0.4472.102
Upstreamed microG (0.2.19211515-9)
12.05.2021
ASB Security string 2021-05-05
standard build only:
System Webview on 90.0.4430.82
microG build only:
Bromite System webview updated to 90.0.4430.204
Bromite Browser updated to 90.0.4430.204
microG upstreamed (but no new version)
Update: AuroraServices 1.1.1
11.04.2021
ASB Security string 2021-04-05
standard build only:
System Webview on 89.0.4389.105
microG build only:
Bromite System webview updated to 90.0.4430.59
Bromite Browser updated to 90.0.4430.59
F-Droid 1.12
Update: AuroraStore 4.0.4 with AuroraServices 1.1.0
09.03.2021
ASB Security string 2021-03-05
standard build only:
System Webview on 88.0.4324.152
microG build only:
Bromite System webview updated to 88.0.4324.207
Bromite Browser updated to 88.0.4324.207
F-Droid 1.11
microG 0.2.18.204714
07.02.2021
ASB Security string 2021-02-05
misc. kernel patches
microG build only:
Bromite System webview updated to 88.0.4324.141
Bromite Browser updated to 88.0.4324.141
F-Droid 1.10-alpha-234
microG 0.2.17.204714-5
14.01.2021
ASB Security string 2021-01-01
standard build only:
Kernel slightly upstreamed
System Webview: Fix of persistent histogram bug (eating space in some cases)
microG build only:
Bromite Webview on 87.0.4280.131
Updated microG from upstream to 0.2.16.204713-10 (picked until 2f29b93)
Updated F-Droid to 1.10-alpha1-212
29.12.2020
introduce microG build variant (see this post or the OP for more information)
18.12.2020
synced LineageOS sources (security patch level December 05, 2020)
08.11.2020
synced LineageOS sources (security patch level November 05, 2020)
Seedvault is included officially now (inbuilt backup solution)
07.10.2020
synced LineageOS sources (security patch level October 05, 2020)
13.09.2020
synced LineageOS sources (security patch level September 05, 2020)
17.08.2020
synced LineageOS sources (security patch level August 05, 2020)
13.07.2020
synced LineageOS sources (security patch level July 05, 2020)
16.06.2020
further GPS improvements
synced LineageOS sources (security patch level June 05, 2020)
20.05.2020
enable GLONASS (thanks @jason972000)
fixed gps week-rollover problem (thanks @jason972000)
11.05.2020
synced LineageOS sources (security patch level May 05, 2020)
16.04.2020
synced LineageOS sources (security patch level April 05, 2020)
15.03.2020
fixed livedisplay
fixed OTA update URL
11.03.2020
remove 5GHz hotspot option as it isn't available even on stock
start signing builds
enable OTA updates
synced LineageOS sources (security patch level March 05, 2020)
28.02.2020
fixed sony bootlogo
fixed TWRP time bug
25.02.2020
fixed buggy bootanimation
11.02.2020
DRM fix (Netflix and co should work now)
synced LineageOS sources (security patch level February 05, 2020)
01.02.2020
SE enforcing
synced LineageOS sources (security patch level January 01, 2020)
22.11.2019
initial release
Reserved
Can't solve the problem with root access as well as Google sync.
if you install gapps, the navigation buttons will stop working
Slavintir said:
if you install gapps, the navigation buttons will stop working
Click to expand...
Click to collapse
Yes, I can confirm this. I think it's somehow connected to the setup wizard which isn't even starting. Also the lineage setup wizard isn't included at the moment.
So staying calm and wait is the best we can do here.
115ek said:
Code:
- Camera : Ok
[/QUOTE]
Could you provide more info about supported camera features?
(1) What's the maximum resolution you can get?
(2) Can you install the Sony camera app from the official ROM and get 960 fps recording?
(3) Is it possible to support Camera 2 API raw output?
I have a full TA backup of unlocked phone in case it makes a difference.
Click to expand...
Click to collapse
mtrantalainen said:
Could you provide more info about supported camera features?
(1) What's the maximum resolution you can get?
(2) Can you install the Sony camera app from the official ROM and get 960 fps recording?
(3) Is it possible to support Camera 2 API raw output?
I have a full TA backup of unlocked phone in case it makes a difference.
Click to expand...
Click to collapse
1. 5248x3936 pixel which is about 20.7 mpixels
2. Installing the Sony camera: I don't know. But you can try and share your experiences.
Concerning the 960 fps: I highly doubt it. Just consider a small example: depth of colour 24 bit, resolution HD ready (1,280x720=921,600 pixel) and 960 fps.
Then a clip of 5 seconds would eat 3 byte x 960 fps x 5 seconds x 921,600 pixel = 12.4 GiB. Highly unlikely
3. Afaik no. But I'm not that interested in camera things. Maybe there are workarounds. If someone knows more feel free to share.
TA backup isn't of any use in camera related aspects as the DRM keys are not needed anymore (there's a workaround in the kerneldrivers). So you won't get a better image.
EDIT:
These are the supported video profiles if you're interested...
And here are some pictures I've taken with oreo. But the quality should be the same on pie and q
115ek said:
1. 5248x3936 pixel which is about 20.7 mpixels
2. Installing the Sony camera: I don't know. But you can try and share your experiences.
Concerning the 960 fps: I highly doubt it.
Click to expand...
Click to collapse
The official firmware is able to do 960 fps Full HD for 250 ms and 960 fps 720p for 500 ms (960 fps mode is triggered during normal speed video recording by touching an icon on the screen and will be inserted in the final video as individual frames which ends up as super slow motion for the original 250 ms time period). The buffering is done internally by the camera hardware. As far as I know, only the the official Sony camera app knows how to start the capture with this high frame rate and there's no publicly available API to do the same thing. This feature has been pretty good for analyzing LCD display backlight PWM and BFI implementations so I would like to keep that feature when I unlock the firmware.
115ek said:
TA backup isn't of any use in camera related aspects as the DRM keys are not needed anymore (there's a workaround in the kerneldrivers). So you won't get a better image.
Click to expand...
Click to collapse
Okay, thanks for the info about not needing TA backup anymore.
115ek said:
These are the supported video profiles if you're interested...
And here are some pictures I've taken with oreo. But the quality should be the same on pie and q
Click to expand...
Click to collapse
Did those photos have resolution 5248x3936 pixels after capture? If so, it seems to support non-system-installed camera apps better than the official firmware. Do you know any camera app that works with LineageOS that supports setting shutter speed manually?
About the video profiles, if I'm reading that XML file correctly, the mode [email protected] is not supported. As far as I know, the hardware does support that just fine.
mtrantalainen said:
The official firmware is able to do 960 fps Full HD for 250 ms and 960 fps 720p for 500 ms (960 fps mode is triggered during normal speed video recording by touching an icon on the screen and will be inserted in the final video as individual frames which ends up as super slow motion for the original 250 ms time period). The buffering is done internally by the camera hardware. As far as I know, only the the official Sony camera app knows how to start the capture with this high frame rate and there's no publicly available API to do the same thing. This feature has been pretty good for analyzing LCD display backlight PWM and BFI implementations so I would like to keep that feature when I unlock the firmware.
Click to expand...
Click to collapse
Well, I can't give you information concerning this. I didn't even know this feature exists. Maybe some other guys can tell you more. At least the hardware seems to have the capabilities. Then it's "just" a matter of controlling it
Update: Are you really sure the Z1 compact has this feature? I just read about the XZ1 compact having it... Do you have any evidence?
mtrantalainen said:
Did those photos have resolution 5248x3936 pixels after capture? If so, it seems to support non-system-installed camera apps better than the official firmware. Do you know any camera app that works with LineageOS that supports setting shutter speed manually?
Click to expand...
Click to collapse
5248x3936 is shown on my PC if I check the image properties.
I just installed Camera FV-5 Lite and it's capable of changing the exposure time (if you meant that). Sadly the maximum resolution is limited in the free version. But I think there are many apps around that support it
mtrantalainen said:
About the video profiles, if I'm reading that XML file correctly, the mode [email protected] is not supported. As far as I know, the hardware does support that just fine.
Click to expand...
Click to collapse
Yes. Actually it's supported. @SpiritCroc removed it with this change However I don't know what his intention was and why the framerates were lower as he noted in the commit.
115ek said:
Update: Are you really sure the Z1 compact has this feature? I just read about the XZ1 compact having it... Do you have any evidence?
Click to expand...
Click to collapse
Oops, you're right. Z1 compact does not have such feature, only XZ1.
Solving the problem
115ek said:
Yes, I can confirm this. I think it's somehow connected to the setup wizard which isn't even starting. Also the lineage setup wizard isn't included at the moment.
So staying calm and wait is the best we can do here.
Click to expand...
Click to collapse
If you install firmware, reboot. Then set the gapp all the work
Slavintir said:
If you install firmware, reboot. Then set the gapp all the work
Click to expand...
Click to collapse
Confirm that. Installed open_gapps-arm-10.0-pico-20191209-BETA. every thing is fine.
I noticed Battery icon 'text' or 'circle' doesn't work. On default icon show percent also doesn't work.
I am xperia z1 big user -_-
I am sorry for an immodest question. When to wait the following version of an insertion?
sibor55 said:
I am sorry for an immodest question. When to wait the following version of an insertion?
Click to expand...
Click to collapse
Well, actually I wanted to get SE enforcing first. This shouldn't be a huge problem. However it needs some time to put it into proper commits.
And at the moment I haven't got that much time.
I hope you'll see it still in January.
PARESH AHAR said:
Confirm that. Installed open_gapps-arm-10.0-pico-20191209-BETA. every thing is fine.
I noticed Battery icon 'text' or 'circle' doesn't work. On default icon show percent also doesn't work.
Click to expand...
Click to collapse
I can confirm that the "battery icon as text" is not working.
Just a heads up someone made an article on how to get Android 10 on the Xperia XZ1 Compact linking to this thread which is obviously for the Xperia Z1 Compact, not the Xperia XZ1 Compact. I tried making a comment on the article to get them to fix it, but was never approved or was simply deleted.
Not linking directly because these guys don't deserve any clicks, but the URL is:
Code:
https://www.getdroidtips.com/android-10-sony-xperia-xz1-compact/
The offending link is the "Link to forum" link on the article in the "Download Links:" section
Finally SE is running in enforcing mode.
Please consider this as a testing build. Logs and bugreports are welcome. Sony bootlogo is missing and the bootanimation was very buggy for me / didn't show up at all at the first boot. Be patient with it.
Download here
dotted said:
Just a heads up someone made an article on how to get Android 10 on the Xperia XZ1 Compact linking to this thread which is obviously for the Xperia Z1 Compact, not the Xperia XZ1 Compact. I tried making a comment on the article to get them to fix it, but was never approved or was simply deleted.
Not linking directly because these guys don't deserve any clicks, but the URL is:
Code:
https://www.getdroidtips.com/android-10-sony-xperia-xz1-compact/
The offending link is the "Link to forum" link on the article in the "Download Links:" section
Click to expand...
Click to collapse
Thanks. Sadly you won't stop these guys. Just ignore them instead.
115ek said:
Thanks. Sadly you won't stop these guys. Just ignore them instead.
Click to expand...
Click to collapse
Yeah I figured, but I just wanted to make sure you were aware in case you get an influx of people trying to get your ROM working on their XZ1 Compacts