Related
Here is first attempt to build LineageOS 14.1 for XiaoMi MiPad
Current state is: mostly working
I finally found solution to fix old mipad stock graphic blobs to load on cm13 and Los 14.1. This build is proof of concept to show it is possible to have Nougat on old good MiPad.
What working:
WiFi (better than 12.1, now using opensource wpa_supplicant)
Sensors (autorotation works)
LEDs
audio including microphone
hardware accelerated video playback
camera
What not working:
audio (currently plays only some system sounds, all other failed because of wrong PCM format)
camera
[*]lineage Music add doesnt play anything (3rd paty players seems to work fine)
[*]windevine drm not working (need updated liibs, to be done in next build)
[*]probably hardware acceleration playback (missed symbols for some omx libs)
[*]not enough space to install gapps into /system partition
[*]random crashes going to system ui restart loop
webview crashing with ERROR:gl_fence_egl.cc(63)] Failed to wait for EGLSync. error:EGL_BAD_MATCH (gapps and play market unusable)
Github links:
Device tre (cm-14.1 branch)
Vendors blobs (cm-14.1 branch)
Kernel (cm-14.1 branch)
2017-02-16
Download:lineage-14.1-20170216-UNOFFICIAL-mocha.zip
Changelog:
Initial release
2017-02-20
Changelog:
Audio fixed
Using patched webview, gapps should work now
SD card and usb mounting fixed
Download: lineage-14.1-20170220-UNOFFICIAL-mocha.zip
2017-02-26
changelog:
random crashes and black screens resolved
new Audio HAL based on opensource tinyhal (microphone works now)
big system partition (1.2Gb). You have to install it on merged system1 and system2, if you have already merged just install.
SD card mount fix included (access to SD card from all apps)
hardware accelerated video playback now works
cleaned some useless blobs like powerservice daemon
updated wifi firmware
Download:lineage-14.1-20170226-UNOFFICIAL-mocha.zip
2017-03-03
Changelog:
Fixed mp3 and flac playback in Music app (disabled offloading since it broken for mp3 and enable ffmpeg for other formats)
Updated wvm libs, Widevine DRM L3 now works
Download: lineage-14.1-20170303-UNOFFICIAL-mocha.zip
2017-03-11
Changelog:
KeyDisabler (alow to enable navbar and disable hardware buttons)
Vibrator intensity control
hwui props in build.prop makes screen more stable in browsers (black pixels on screen issue)
Updated LED capabilities (RGB notification, settings for battery and notification colors, button backligth brightness)
Userspace cpuquiet governor by default. Looks like this is best option to get smooth playback. (cores dosnt switches off but only changes its freq)
Fixed offline charging mode. Now shows animaton with current battery level. Also previous 14.1 builds cant be offline charged from PC USB port, now this issue resolved
return glcomposer compositor. Now looks stable, it should be because of hwui right props added. *broken*
Download: lineage-14.1-20170311-UNOFFICIAL-mocha.zip broken
2017-03-12
composer changed back to surfaceflinger. Solves issues with blck screen or reboots in 20170311 build
Download lineage-14.1-20170312-UNOFFICIAL-mocha.zip
2017-04-21
test version with Nexus 9 blobs
webview slow work resolved with new graphic blobs
Browser replaced with Gelllo
lineage code updated up to 7.1.2
Known issues:
Bluetooth broken
Doesnt load proper mac address
Some graphic issues in general user interface
Download: lineage-14.1-20170421-UNOFFICIAL-mocha.zip
Download fixed boot.imgboot-20170429.img - fixes wifi and bluetooth issues on 2017-04-21 lineage 14.1 build.
2017-05-02
Changelog:
camera works now
Browser replaced with Gelllo
lineage code updated up to 7.1.2
Known issues:
this build still uses old graphic blobs, so webview apps is laggy.
if camera doesnt work after dirty flash try to delete /data/nvcam folder from adb root console or root file manager
Download: lineage-14.1-20170502-UNOFFICIAL-mocha.zip
Webview apk is one patched to work on broadcom GPU with same problem as ours: https://github.com/manumanfred/android_external_chromium-webview
2017-09-11 NEW!
Changelog:
Lineage OS 14.1 sources updated
Webview updated and rebuilt with only changes necessary for Mi Pad. Most of webview related issues now resolved. Faster and smoother scrolling in webview based apps, some apps now startings works, like Gogle Books. See webview patch applied below.
device tree cleaned for proper work with proprietary blob files. Now they can be extracted from stock rom or device and makefiles can be properly generated in vendor.
Using opensource version of libbt-vendor - maybe some changes in bluetooth perfomance.
Download lineage-14.1-20170911-UNOFFICIAL-mocha.zip from Google Disk or from MailRu mirror
Webview patch applied:
Code:
diff --git a/gpu/config/gpu_driver_bug_list.json b/gpu/config/gpu_driver_bug_list.json
index b8f5489ce086..6bf7f9250237 100644
--- a/gpu/config/gpu_driver_bug_list.json
+++ b/gpu/config/gpu_driver_bug_list.json
@@ -1,6 +1,6 @@
{
"name": "gpu driver bug list",
- "version": "10.93",
+ "version": "10.94",
"entries": [
{
"id": 1,
@@ -2542,6 +2542,19 @@
"features": [
"rely_on_implicit_sync_for_swap_buffers"
]
+ },
+ {
+ "id": 236,
+ "description": "MiPad Nvidia drivers g_ignore_egl_sync_failures work around",
+ "cr_bugs": [123456],
+ "gl_vendor": "NVIDIA.*",
+ "machine_model_name": ["MI PAD"],
+ "os": {
+ "type": "android"
+ },
+ "features": [
+ "ignore_egl_sync_failures"
+ ]
}
],
"comment": [
special patched webview prebuilts located here https://github.com/HighwayStar/android_external_chromium-webview (branch cm-14.1-mocha)
Merge partitions
Mi Pad by default has 2 /system partition, each 640Mb. It is not enogh to install LineageOS and Gapps. To install 2017-02-25 build and newer you have to merge 2 system partition in one 1.2Gb system partition. To dod this follow instruction http://en.miui.com/thread-118294-1-1.html
Root Access
If you want root access flash addonsu-arm-signed.zip from https://download.lineageos.org/extras
XDA:DevDB Information
LineageOS 14.1 for Xiaomi MiPad (mocha), ROM for the Xiaomi Mi Pad
Contributors
highwaystar_ru, highwaystar_ru
Source Code: https://github.com/HighwayStar/android_device_xiaomi_mocha
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod, LineageOS
Version Information
Status: Alpha
Created 2017-02-16
Last Updated 2017-09-11
Reserved
If you have problem installing newer latest build, or just to be sure it will install fine check you system partition with DiskInfo app. It should show System partition at least 1337564160 bytes.
First! Holy ****, I never thought I'd see the day...
@highwaystar_ru Is there not enough space in /system even after merging system1 and system2?
EDIT: If anyone wants root: https://download.lineageos.org/extras
Unbelievable
Damn dude, you rock....!!
the future of mi pad 1 is getting brighter because of you.....!!
drakonizer said:
First! Holy ****, I never thought I'd see the day...
@highwaystar_ru Is there not enough space in /system even after merging system1 and system2?
Click to expand...
Click to collapse
On merged system it is enogh space, but now /system in rom configured to match stock /system. Not sure for now if it possible to remove LineageOs stock app like browser and email and free some space or just use bigger /system and require to repartition.
Woah
Impressive.
highwaystar_ru said:
On merged system it is enogh space, but now /system in rom configured to match stock /system. Not sure for now if it possible to remove LineageOs stock app like browser and email and free some space or just use bigger /system and require to repartition.
Click to expand...
Click to collapse
We could do that...remove some unnecessary packages from https://github.com/LineageOS/android_vendor_cm/blob/cm-14.1/config/common.mk with a PRODUCT_PACKAGES -= line in the device.mk.
But asking users to repartition to install gApps is better in my opinion, for future official Lineage support. There could be a check in the updater_script to verify the user has repartitioned.
I am pretty sure there is no re-configuration necessary to support repartitioned /system partitions.
Does that mean CM12 development is dropped?
MiliWanili said:
Does that mean CM12 development is dropped?
Click to expand...
Click to collapse
Do you want the latest nougat or old lolipop
OMG... unbelievable....first 7.1.1 on mipad...
Xiaomi, shame on you
and thank you! highwaystar!
AbhaYsinGH007 said:
Do you want the latest nougat or old lolipop
Click to expand...
Click to collapse
Lollipop if it comes faster.
If it possible to make los14.1 run stable and sound working it is better to go with los14.1. At least it has upstream support, and some things here works better. I cant make opensource wpa_supplicant working on 12.1, but here it works. Microphone in cm12.1 is also hard to fix, because there is only LD_PRELOAD for lib and microphone require MonoPipe class from 4.4 to work, but it will break other things. On cm13 or los14.1 it is possible to use LD_SHIM_LIBS to fix only broken libs and not break working.
For now I'm trying what cause los14.1 unstable, sometimes it may work for hours, but when it crashed to black screen and buttons backlight it starts endless bootloop.
Unbelievable
Never expected los14.1 on mi pad.
Awsome,, nice work bro
Xiaomi Mi Pad with the latest OS. Awesome Dev!
Awesomeeeeeee! Highwaystar. You are simply awesome. never expected the lineageOs, that too for Mi pad. and now you are our only hope.
Holy moly... Would be flashing this baby once we get the camera and hardware acceleration sorted out... This is why I LOVE XDA and the developers here....
drakonizer said:
First! Holy ****, I never thought I'd see the day...
@highwaystar_ru Is there not enough space in /system even after merging system1 and system2?
Click to expand...
Click to collapse
Did you tried least gapps.
---------- Post added at 12:26 PM ---------- Previous post was at 12:25 PM ----------
drakonizer said:
First! Holy ****, I never thought I'd see the day...
@highwaystar_ru Is there not enough space in /system even after merging system1 and system2?
Click to expand...
Click to collapse
Did you tried gapps Pico version
awesome awesome awesome unbelievable ::good::good::good::good::good:
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!
{
"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"
}
Introduction
iodéOS is a privacy-focused operating system powered by LineageOS and based on the Android mobile platform. iodéOS aims at protecting the user's privacy with a built-in adblocker and by freeing the smartphone from snitches.
The objectives in the conception of this ROM are threefold:
To keep the stability and security level of LineageOS, by minimizing the modifications made to the system. Apart the system modifications required by the adblocker, we mainly only added a few useful options commonly found in other custom ROMs, made some cosmetic changes, modified a few default settings to prevent data leaks to Google servers.
To ease a quick adoption of this ROM by new users. We especially target users that are concerned by the protection of their privacy, but are not reluctant to still use inquisitive apps like Google ones. We thus included MicroG as well as a coherent set of default apps, and simplified the initial setup of the system. Particularly, an initialization of MicroG has been made with GCM notifications allowed by default, a privacy-friendly network location provider (DéjàVu) pre-selected, as well as Nominatim Geocoder.
To provide a new and powerful way of blocking ads, malwares, data leaks of all kinds to many intrusive servers. We are developing an analyzer, tightly integrated into the system, that captures all DNS requests and network traffic, as well as a user interface (the iodé app). Compared to some other well-known adblockers, this has the advantages of:
Avoiding to lock the VPN for that use. You can even use another adblocker that uses VPN technology alongside our blocker.
Being independent of the kind of DNS server used by the system or set by an independent app: classical DNS on UDP port 53 or any other one, DNS over TLS (DoT), DNS over HTTPS (DoH), ..., as we capture the DNS requests before they are transmitted to the system function that emits the DNS request. What we do not support, is DoH when it is natively built into applications, i.e. when an app communicates directly with a DoH server, without asking name resolution to the system. It would require to decrypt HTTPS packets between such an app and the DoH server, which may create a big security hole.
Precisely mapping DNS requests and network packets to the Android apps that emitted (or received) them.
Deciding which apps have a filtered network usage (by default, all apps), and which ones can communicate with blacklisted servers.
Since its first versions, we added many features to the iodé blocker: several levels of protection, fine-grained control over the hosts that should be blocked or authorized, displaying statistics on a map to see the quantity of data exchanged to which countries, clearing statistics... We are actively developing the blocker, and new functionalities will be regularly added.
Features
Changes in LineageOS to prevent data leaks:
Default DNS server: Google's DNS replaced by Quad9's 'unblocked' servers in all parts of the system.
A-GPS: patches to avoid leaking personnal information like IMSI to supl server.
Captive portal login: connectivitycheck.gstatic.com replaced by captiveportal.kuketz.de for connectivity check.
Dialer: Google default option replaced by OpenStreetMap for phone number lookup.
Pre-installed apps:
We included many useful default apps, but our choice cannot suit everyone; so we added the possibility to remove them. It can be done at the end of the phone setup, or at any time by going to Parameters -> Apps & Notifications -> Preinstalled apps.
MicroG core apps: GmsCore, GsfProxy, FakeStore.
NLP backends for MicroG : DejaVuNLPBackend (default), MozillaNLPBackend, AppleNLPBackend, RadioCellsNLPBackend, Nominatim Geocoder.
App stores : FDroid (with F-Droid Privileged Extension) and Aurora Store.
Browser: our own fork of Firefox (with Qwant as default search engine, many other ones added, telemetry disabled, parts of telemetry code removed) instead of Lineage’s default browser Jelly.
SMS: QKSMS instead of Lineage's default SMS app.
Email: p≡p (Pretty Easy Privacy).
Camera: our own fork of Open Camera, with a few tweaks.
Maps/navigation: Magic Earth GPS & Navigation (the only one free but not open source).
Keyboard: OpenBoard instead of AOSP keyboard.
PDF: Pdf Viewer Plus.
Personnal notes: Carnet.
{Ad/Malware/Data leak}-blocker: iodé.
News: to keep users informed about our developments, as well as a FAQ.
Meteo: Geometric Weather.
Pre-included FDroid repository:
The apps that we tweak or develop (microG services, the browser based on Firefox, the News app, Open Camera ...) are available through a repository that we included in FDroid (check the "Apps for iodéOS" category). For this purpose and to avoid name conflicts of some apps, we also had to make a few changes in FDroid.
Useful options from other custom ROMs:
Smart charging (disables charging when a given level is reached, to protect battery health).
Fingerprint vibration toggle.
Swipe down to clear all in recent apps (Android 10 only).
Installation Instructions
To download and flash our latest build, see https://gitlab.com/iode/ota.
You can also find here direct links to the latest builds.
Supported devices
Fairphone FP3/FP3+
Fairphone FP4
Google Pixel 3
Google Pixel 4
Google Pixel 5
Google Pixel 6
Google Pixel 6a
OnePlus 9
OnePlus 9 Pro
Samsung Galaxy A5/A7 2017 (a5j17lte/a7j17lte)
Samsung Galaxy S9/S9+ (starlte/star2lte)
Samsung Galaxy Note 9 (crownlte)
Samsung S10e/S10/S10+ (beyond{0,1,2}lte)
Samsung Note 10 (d1)
Samsung Note 10+ (d2s)
Sony Xperia XA2 (pioneer)
Sony Xperia XZ1 (poplar)
Sony Xperia XZ2 (akari)
Sony Xperia XZ3 (akatsuki)
Xiaomi Mi9 (cepheus)
Teracube 2e
Xiaomi Mi 10T 5G / Mi 10T Pro 5G
Xiaomi Mi 10 Lite 5G
Sources
iodéOS: https://gitlab.com/iode/os
LineageOS: https://github.com/lineageos
device tree:
https://gitlab.com/iode/os/public/devices/sony/device_sony_akari
https://gitlab.com/iode/os/public/devices/sony/device_sony_tama-common
kernel: https://github.com/LineageOS/android_kernel_sony_sdm845
Bug Reporting
You can post a message in this thread or (preferred) open an issue here.
Credits
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit their Wiki for more details.
This ROM would be nothing without the tremendous work made on MicroG, and all the other open source apps that we included. We are very grateful to their authors.
Contributors
Direct contributors: @iodeOS, @vince31fr
Indirect contributors (too numerous to list): All the people that contributed to the device tree, to LineageOS, and to the included open source apps.
Sponsoring
You can help in the development of this ROM by paying us a coffee here: https://paypal.me/iodeOS.
Screenshots
Downloads : iodéOS
04/04/2023 (build 20230401):
Installation procedure: move to a fastboot script (read instructions: https://gitlab.com/iode/ota)
Blocker: improved use of blocking lists (sub-domains blocking)
FDroid: fixes an issue on apps update
LineageOS synchronized with March security patch included
All apps updated
07/02/2023 (build 20230131):
Upgrade to iodéOS 4.0 based on Android 13 / LineageOS 20
Blocker:
Improved blocking settings. You can now choose 'Standard' blocking (ads, trackers, malwares, etc) or 'Reinforced' blocking (same objective but more extensive), and then select additional categories.
The 'Porn' category has been extended to a wider 'Sensitive content' one, that also includes fake news, gambling, drugs, piracy, torrent..., with mainly child protection in mind.
The 'Extreme' category has been removed, as it is now part of the reinforced blocking.
Improved blocking lists. We merge several acknowledged and up-to-date sources, and have diversified our sources to produce more complete lists. The standard list has however been reduced a bit, to avoid as much as possible interference with apps expected behavior.
Added a new network location provider: Local NLP Backend. It is an improved version of the DéjàVu NLP backend which was already available in iodéOS. Like DéjàVu, it builds a local database connecting localizations learned from other NLP backends and apps using GPS, and mobile antennas/Wifi; but also has an active mode (not preselected) that can trigger GPS requests. To configure it: Settings -> System -> microG -> Location modules
LineageOS synchronized with January security patch included
All apps updated
New devices support: Pixel 3, 6, 6a
16/12/2022 (build 20221215):
Blocker: added multiple selection in settings / domain customization. Long-press on a domain, select several domains or all, apply actions (block all, authorize all...)
PdfViewerPlus: improved security by updating core libraries
Network settings: added a switch to disable connectivity check (and thus captive portal detection)
LineageOS synchronized with December security patch included
All apps updated
New devices support: Pixel 4 & 5, OnePlus 9 & 9 Pro
24/11/2022 (build 20221121):
Improvements in the blocker user interface (iodé app)
LineageOS synced with September security patch included
All apps updated
17/10/2022 (build 20221014):
Blocker:
Network blockings following their type (Wifi, mobile data, VPN) added
Default blockings definition for new apps
Personnalized recipients management improved
iodé's app access restrictions by password added
Search filters added in report and map
Display theme selection
Automatic and 'real-time' refresh of the whole app
Performance and fluidity improvements of the app
LineageOS synced with September security patch included
All apps updated
27/07/2022 (build 20220726):
Upgrade to iodéOS 3.1 based on Android 12 / LineageOS 19.1
SafetyNet certification activated: allows many apps, notably banking ones, to fully work
Setup wizard: the push notifications configuration page now also activates SafetyNet (fine-grained control in Settings->System->microG)
OpenCamera: the 'Use alternative flash method' in photo settings is no more necessary and can be disabled, allowing flash optimization
News app: German translations
LineageOS synced with July security patch included
All apps updated
21/07/2022 (build 20220530):
Setup Wizard: new page to configure push notifications through microG
Lockscreen settings: switch added to disable fingerprint unlock when screen is off
Improved German translations
Bug fixes and improvements
LineageOS synced with May security patch included
All apps updated
02/05/2022 (build 20220408):
News app reworked
Setup Wizard: new iodé introduction
iodé blocker: pull to refresh replaced by automatic refresh in report tab
Teracube 2e 2022 batch released, video playback in browser and video recording fixed
Music app : playlist crash fixed
Open Camera : crash when tapping thumbnail of a newly recorded video fixed, photos and videos now editable
LineageOS synced with March security patch
All apps updated
03/02/2022 (build 20220126):
New iodé blocker map feature
Build mode changed to 'user' (i.e. release) mode): more apps work out-of-the-box and more secure device, but more restrictive recovery
Camera app changed to Open Camera
Wireguard kernel module included
Dark bootanimation
January security patch
Preinstalled apps updated
Beware: Play store Magisk module broken
18/11/2021 (build 20211108):
LineageOS updated (November security patch)
Preinstalled apps updated
Iodé blocker: hosts can now be customized, either globally or by app
10/09/2021 (build 20210828):
LineageOS updated (August security patch)
Preinstalled apps updated
Backup app included: Seedvault
microG now uninstallable: Settings -> Apps & notifications -> Preinstalled apps
New default accent color (clear blue from iodé logo)
03/08/2021 (build 20210729):
Upgrade to Android 11 / LineageOS 18.1
Preinstalled apps UI reworked with the introduction of categories.
Dark theme in the iodé blocker UI (next improvement will be hosts customization).
p≡p (https://f-droid.org/fr/packages/security.pEp/) is now the defaut email client, and replaces lineageOS client which is no longer maintained.
Preinstalled apps updated to their latest version.
LineageOS updated (July security patch).
28/05/2021 (build 20210525):
Different protection levels in iodé's blocker added: in addition to the default standard blocklist, we added three lists (socials, porn, extreme) that can be activated globally or on a per-app basis (more information in the FAQ).
Geometric Weather app added.
Preinstalled apps selection at setup wizard added.
Preinstalled apps including microG updated to their latest version.
LineageOS updated (May security patch).
07/03/2021 (build 20210306):
Blocker UI improved: performance at startup, statistics display (with sortable columns), DNS stream
Preinstalled apps management (uninstall / reinstall) menu added (Settings -> Apps & Notifications -> Preinstalled apps)
Latest lineageOS sources synced
Default apps updated
22/01/2021 (build 20210119):
LineageOS sources synced
Prebuilt apps updated
Activated Camera APIv2 in Snap
Force auto-update of apps in FDroid to keep in sync with iodé apps. It can be disabled.
02/12/2020 (build 20201127):
LineageOS sources synced
Prebuilt apps updated
New default wallpaper
Firefox browser renamed as iodé Browser and logo changed due to trademark restrictions
The iodé blocker can now be correctly coupled with a VPN
17/11/2020 (build 20201113):
Qwant replaced by a customized version Firefox, actually 83.1.0-rc1: Qwant or DDG as default search engine, alternate search engines added, telemetry disabled
iodé app (blocker): app switches replaced by shields around app icons, aggregated apps view in report, historical data deletion for each period by long press on an app line in report, black list updated
LineageOS sources synced
Prebuilt apps updated
Added a iodé category in FDroid, to quickly distribute the apps we customize. We had to fork FDroid for this purpose.
30/09/2020 (build 20200925):
Synced LineageOS sources and device tree
microG updated to v0.2.12.203315 plus commits up to 25/09 (in-app maps now mostly working through Mapbox)
Prebuilt apps updated to their latest version
Welcome to "News": an app to keep users informed of latest iodé developments, as well a a FAQ.
05/08/2020 (build 20200805):
Synced LineageOS sources and device tree
microG updated to v0.2.11.202414 plus commits up to 05/08
AppleNLP backend working again
Prebuilt apps updated to their latest version
25/07/2020 (build 20200725): first publicly available build for akari.
Downloads : add-ons
phonesky-magisk.zip : Magisk module for NanoDroid patched Play Store, for those who really need to get access to their paid apps that don't work with microG. This module can be generally be deactivated when you have installed and ran once the paid apps.
NB : you may have to wait a couple of hours after activating the module for being able to install paid apps.
phonesky-magiskV2.zip : compatibility for the upcoming iodéOS 2.0 based on Android 11. It can ben installed on iodéOS 1.x based on Android 10 too.
IMPORTANT : install this module or deactivate the previous one before installing iodéOS 2.0, or you'll be caught in a bootloop.
is a support for xz2c / dual planned?
shajk-00 said:
is a support for xz2c / dual planned?
Click to expand...
Click to collapse
Not yet, we don't own this device.
Thanks for your work!
hostme said:
Thanks for your work!
Click to expand...
Click to collapse
You're welcome!
There will be a new release in a couple of days that will embed the new release of microG. Stay tuned!
### NEW UPDATE : 05/08/2020 ###
Also available as an OTA update.
Quick changelog:
Synced LineageOS sources and device tree
microG updated to v0.2.11.202414 plus commits up to 05/08
AppleNLP backend working again
Prebuilt apps updated to their latest version
Lemme guess, you work for Vodafone. No sane person would switch to ISP/Telco operated service for security/privacy unless you have insider info that it is indeed private/secure, or you have something to gain from it, aka selling user information. If its the former, that's great, if its the latter, please disclose so and remove any references that you "aim" to be secure and private.
hotcakes_shinku said:
Lemme guess, you work for Vodafone. No sane person would switch to ISP/Telco operated service for security/privacy unless you have insider info that it is indeed private/secure, or you have something to gain from it, aka selling user information. If its the former, that's great, if its the latter, please disclose so and remove any references that you "aim" to be secure and private.
Click to expand...
Click to collapse
Two options: disable AGPS, or at least switch from Google to another provider. We are not alone in the world to make such a choice: see https://www.reddit.com/r/privacy/comments/cldrym/how_to_degoogle_lineageos_in_2019/
*** New update: 30/09/2020 ***
Download here (OTA available)
We are looking for beta testers volunteers!
Hi everyone.
As you may know, before officially deploying each update on all iodé smartphones, our team spends a few days testing that the update functions as expected.
We are thus looking for volunteers to help us testing our updates. The principle is very simple: as a beta tester, your will receive a notification to install each update a few days before the official one. You will only need to install it and report to our team possible anomalies on the use of your smartphone. If you encounter nothing wrong, then just enjoy the update before everyone ?.
If you'd like to become beta tester, feel free to join our 'iodé Beta Testers' Telegram app group.
Thank you and keep your data safe with iodé!
/// New update: 17/11/2020 \\\
Available as OTA (see OP for direct link and changelog)
### New update: 02/12/2020 ###
Available as OTA (see OP for direct link and changelog)
vince31fr said:
Not yet, we don't own this device.
Click to expand...
Click to collapse
Truly really excited to get this going on xz2c. Hope it gets live soon. Have spent the past many days getting the lineageOS4microG going. iodeos seems like the next big step in terms of evolution!
But just to ask anyway...
Do you think flashing Xz2 on Xz2c is likely going to be a problem?
=== New Update : 22/01/2021 ===
Available as OTA (see OP)
- Front camera doesnt work, crashes
- When i use phonesky-magisk.zip, the playstore shows me i have to pay my paided apps again?
- Can i install twrp on the phone?
Thats the only problems i have, overall a very good ROM
Hobbala said:
- Front camera doesnt work, crashes
- When i use phonesky-magisk.zip, the playstore shows me i have to pay my paided apps again?
- Can i install twrp on the phone?
Thats the only problems i have, overall a very good ROM
Click to expand...
Click to collapse
Front camera works perfectly on a clean install. Maybe you installed a magisk module which conflicts with the system ?...
Yes, you can install twrp.
About phonesky-magisk: I don't have problems with it on another phone. Maybe someone could tell if it works on XZ2 ?
vince31fr said:
Front camera works perfectly on a clean install. Maybe you installed a magisk module which conflicts with the system ?...
Yes, you can install twrp.
About phonesky-magisk: I don't have problems with it on another phone. Maybe someone could tell if it works on XZ2 ?
Click to expand...
Click to collapse
I deactivated all magisk modules, restarted the phone, but nothing has changed ... maybe I try again from scratch tomorrow or i just use the "open camera" app, there the front camera works.
How do I install twrp? twrp-3.4.0-0-akari.img no longer works, as soon as iode is installed.
Hobbala said:
I deactivated all magisk modules, restarted the phone, but nothing has changed ... maybe I try again from scratch tomorrow or i just use the "open camera" app, there the front camera works.
How do I install twrp? twrp-3.4.0-0-akari.img no longer works, as soon as iode is installed.
Click to expand...
Click to collapse
About twrp : yes, it is overwritten after iodé installation. You can reinstall it after iodé's installation.
About camera : try also after a factory reset, without installing anything.
About phonesky : it works, after waiting long enough after activating the module (several hours, maybe 10 or more, it depends...).
vince31fr said:
About twrp : yes, it is overwritten after iodé installation. You can reinstall it after iodé's installation.
About camera : try also after a factory reset, without installing anything.
About phonesky : it works, after waiting long enough after activating the module (several hours, maybe 10 or more, it depends...).
Click to expand...
Click to collapse
About twrp: after iode was installed, i couldnt „fastboot boot twrp.img“ cause it was stuck at fastboot, but its working / installed now
About camera: tried a factory reset, wiped the phone, installed the stock ROM again and used the cam at once after iode was installed, but still same problem
About phonesky: Yes ur right, i waited and its working now THX
This thread aims at providing LineageOS 18.1 builds for the Sony Xperia Z1 compact with current security patches.
You can consider this thread as a successor of our LineageOS 17.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 18.1 build
This build flavor aims at providing LineageOS 18.1 "as is" with most recent security patches.
If you want to install Google Apps (GApps) you have to use this build variant.
You could install additional Google Apps if you want to. This has to be done directly after the lineage installation BEFORE the first boot.
The smaller the package, the better in terms of performance. (None is of course the most performant). If you want "Okay google" support you need at least nano. Else I'd recommend pico.
Downloads:
OpenGapps
BitGapps
MindTheGapps (mirror)
Click to expand...
Click to collapse
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:
- Boot : Ok
- Partitions (Data, Cache) : Ext4 and F2FS supported
- Bluetooth : Ok but MAC address is not correctly set (random address)
- 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
- ANT+ : broken
- 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
- DRM: Ok, Widevine L3
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
ANT+ does not work
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/lin18-microg/android_kernel_sony_msm8974
Manifest: https://github.com/lin18-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 18.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/lin18-microg/local_manifests
ROM OS Version: Android 11
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Stable Release Date: 2021-10-14
Created 2020-12-06
Last Updated 2023-06-09
Changelog
09.06.2023
ASB Security string 2023-06-05
standard build only:
System Webview 114.0.5735.58
microG build only:
Mulch Webview 114.0.5735.61
microG updated to 0.2.28.231657-5
FakeStore updated to 0.2.0
AuroraStore updated to 4.2.3
09.05.2023
ASB Security string 2023-05-05
standard build only:
System Webview 113.0.5672.77
microG build only:
Mulch Webview 113.0.5672.77
15.04.2023
ASB Security string 2023-04-05
standard build only:
System Webview 112.0.5615.48
microG build only:
Mulch Webview 112.0.5615.48
Removed Bromite browser and shipped LineageOS' Jelly instead
19.03.2023
ASB Security string 2023-03-05
standard build only:
System Webview 111.0.5563.58
microG build only:
Bromite Webview replaced by Mulch Webview 111.0.5563.58
18.02.2023
ASB Security string 2023-02-05
standard build only:
System Webview 109.0.5414.118
microG build only:
microG updated to 0.2.27.223616-3
Spoof apps installed by G*PlayStore
06.01.2023
ASB Security string 2023-01-05
standard build only:
System Webview 108.0.5359.128
microG build only:
microG updated to 0.2.26.223616-16
11.12.2022
ASB Security string 2022-12-05
standard build only:
System Webview 108.0.5359.79
microG build only:
Bromite Browser and Webview on 108.0.5359.106
microG updated to 0.2.26.223616-2
12.11.2022
ASB Security string 2022-11-05
standard build only:
System Webview 107.0.5304.91
microG build only:
Bromite Browser and Webview on 106.0.5249.163
microG updated to 0.2.25.223616-10
12.10.2022
ASB Security string 2022-10-05
standard build only:
System Webview 106.0.5249.79
microG build only:
Bromite Browser and Webview on 105.0.5195.147
microG updated to 0.2.24.223616-61
09.09.2022
ASB Security string 2022-09-05
Many kernel patches applied
standard build only:
System Webview 105.0.5195.68
microG build only:
Bromite Browser and Webview on 104.0.5112.91
microG updated to 0.2.24.214816-30
Performance improvement (exec spawning OFF by default)
Contacts app slightly 'de-Googled'
06.08.2022
ASB Security string 2022-08-05
standard build only:
System Webview 103.0.5060.71
microG build only:
Bromite Browser and Webview on 103.0.5060.140
12.07.2022
ASB Security string 2022-07-05
14.06.2022
ASB Security string 2022-06-05
standard build only:
System Webview 102.0.5005.78
microG build only:
Bromite Browser and Webview on 102.0.5005.96
microG updated to 0.2.24.214816-11
09.05.2022
ASB Security string 2022-05-05
standard build only:
System Webview 100.0.4896.127
microG build only:
Bromite Browser and Webview on 101.0.4951.53
microG updated to 0.2.24.214816-10
Mozilla Location provider on 1.5.0
12.04.2022
ASB Security string 2022-04-05
standard build only:
System Webview 100.0.4896.58
microG build only:
Bromite Browser and Webview on 100.0.4896.57
15.03.2022
ASB Security string 2022-03-05
Many kernel patches
standard build only:
System Webview on 98.0.4758.101
microG build only:
Bromite Browser and Webview on 99.0.4844.58
microG 0.2.24.214816-2
AuroraStore 4.1.1
22.01.2022
ASB Security string 2022-01-05
18.12.2021
ASB Security string 2021-12-05
standard build only:
System Webview on 96.0.4664.104
microG build only:
Bromite System Webview and Browser on 96.0.4664.54
microG 0.22.214516-21
14.11.2021
ASB Security string 2021-11-05
standard build only:
System Webview on 95.0.4638.50
microG build only:
Bromite System Webview and Browser updated to 94.0.4606.109
14.10.2021
introduce microG build variant (see this post or the OP for more information)
ASB Security string 2021-10-01
standard build only:
System Webview on 94.0.4606.71
microG build only:
Bromite System Webview and Browser updated to 93.0.4577.83
20.09.2021
fixed DRM (ref, ref)
18.09.2021
fixed FM radio (ref, ref)
synced LineageOS sources (security patch level September 05, 2021)
Wifi display is back (ref)
Setup wizard redesigned (ref)
16.08.2021
synced LineageOS sources (security patch level August 05, 2021)
switched to 3.4 kernel with backports
19.07.2021
synced LineageOS sources (security patch level July 05, 2021)
20.06.2021
added livedisplay
synced LineageOS sources (security patch level June 05, 2021)
11.06.2021
fixed fm SE linux denial
26.05.2021
fixed netmgrd SE linux denials (ref)
22.05.2021
fixed NFC settings not shown (ref)
fixed offline charging
15.05.2021
fixed wifi problems when WPA3 is used (ref)
13.05.2021
fixed wifi MAC address readout
synced LineageOS sources (security patch level May 05, 2021)
24.04.2021
enable OTA updates
switch to enforcing SE linux
start signing builds
23.04.2021
synced latest lineage sources
01.01.2021
using snap camera now (instead of camera2)
fixed NFC (thanks @AdrianDC)
19.12.2020
Lineage 18.0 -> Lineage 18.1 (android-11.0.0_r17 -> android-11.0.0_r19)
08.12.2020
fixed screenlock
06.12.2020
initial release
reserved
Thanks @koron393 camera is working now
New build is up.
08.12.2020
fixed screenlock
Furthermore I updated the manifest and build instructions - just in case someone wants to build from source.
It would be nice if you can share your experiences, so that we can complete the status list.
I have already mentioned it in the 17.1 thread but I think it is also good to post it here:
The bad font rendering from 17.1 is gone in this build.
EOL [ROM][Unofficial][10.0][signed][OTA] Lineage OS 17.1 for Xperia Z1 compact
This thread is discontinued - please visit the LineageOS 18.1 sucessor thread This thread aims at providing LineageOS 17.1 builds for the Sony Xperia Z1 compact with current security patches. You can consider this thread as a successor of our...
forum.xda-developers.com
I will wait until I can find and download GAPPS.
tramp20 said:
I will wait until I can find and download GAPPS.
Click to expand...
Click to collapse
BiTGApps
[CUSTOM][GAPPS] BiTGApps for Android
Hi All, Welcome to the official BiTGApps Release thread! BiTGApps is a customized Google Apps Package to sideload Google Apps in Custom Android OS. It comes with many useful features and easy installation. Get features list, instructions...
forum.xda-developers.com
koron393 said:
BiTGApps
[CUSTOM][GAPPS] BiTGApps for Android
Hi All, Welcome to the official BiTGApps Release thread! BiTGApps is a customized Google Apps Package to sideload Google Apps in Custom Android OS. It comes with many useful features and easy installation. Get features list, instructions...
forum.xda-developers.com
Click to expand...
Click to collapse
I tried already this link but they have server problems since 9 days :-(
MOD EDIT: Link Removed
Perhaps someone can upload these GAPPS to Onedrive, DropBox or GoogleDrive.
Search the xda thread carefully!
koron393 said:
Search the xda thread carefully!
Click to expand...
Click to collapse
Thanks.
This one?
[CUSTOM][GAPPS] BiTGApps for Android
Hi All, Welcome to the official BiTGApps Release thread! BiTGApps is a customized Google Apps Package to sideload Google Apps in Custom Android OS. It comes with many useful features and easy installation. Get features list, instructions...
forum.xda-developers.com
New build is up:
Lineage 18.0 -> Lineage 18.1 (android-11.0.0_r17 -> android-11.0.0_r19)
I will share a few first experiences with the build of 19.12.20:
- GPS and compass seem to work (Google Maps constantly crashes, Waze does show the right location and the compass moves when I move the phone. But I can't say for sure if it's maybe just using other sensors and Wifi for that)
- FM Radio : yes (can't judge the quality)
- Microphone : yes
- bluetooth audio : yes
- NFC : greyed out in the control center
Other:
- runs pretty fast for such an early version actually that was a lie, because it runs pretty fast for any version
- once got stuck on the Sony logo, which was fixed by holding power + volume up
- when I used the restart option from the power off menu, when it turned back on it was really slow and the screen flickered slightly. that happened just once though, so probably nothing to worry about
@115ek
thank you for this new ROM.
1. I have only installed BitGAPPS, but in the settings of Play Store I see "device is not certified".
Of course I deleted memory and cache of Play Store (was updated already) and Play Services.
2. Long pressing the power button does not show sreenshot, only power off and restart.
3. Restart to Recovery goes to Lineage Recovery and not to TWRP. How to change this?
I had already flashed TWRP again in fastboot mode.
It seems that TWRP has gone :-(
Has someone successfully installed/flashed Magisk 21.1 and when yes how?
I can flash it without errors but nothing is really installed, no Magisk framework and no Manager :-(
tramp20 said:
1. I have only installed BitGAPPS, but in the settings of Play Store I see "device is not certified".
Of course I deleted memory and cache of Play Store (was updated already) and Play Services.
Click to expand...
Click to collapse
The google certification algorithm changes from time to time and your phone can be classified as "not certified" at any point of time. I'm no gapps user, so unfortunately I can't give any tips here nor know what consequences this certification state really has.
tramp20 said:
2. Long pressing the power button does not show sreenshot, only power off and restart.
Click to expand...
Click to collapse
That's a lineage framework thing and most likely will change in the future.
tramp20 said:
3. Restart to Recovery goes to Lineage Recovery and not to TWRP. How to change this?
I had already flashed TWRP again in fastboot mode.
It seems that TWRP has gone :-(
Click to expand...
Click to collapse
That's also a thing forced by lineage. During the setup wizard you'll now be asked if you want to update the recovery. Don't check this box if you want to keep TWRP. Else you'll end up with lineage recovery.
tramp20 said:
Has someone successfully installed/flashed Magisk 21.1 and when yes how?
I can flash it without errors but nothing is really installed, no Magisk framework and no Manager :-(
Click to expand...
Click to collapse
I hadn't had a look into magisk yet. I'm just using root over adb for development purposes. Going to check that if I find some time.
@115ek,
thank you for all answers.
To lineage recovery : I found this already after some tries, this check box should not be pre-activated.
I saved the TWRP recovery.log after installing the latest Magisk-v21.2.zip.
But nothing is really installed, no Magisk framework and no Magisk Manager :-(
Perhaps you see something in this logfile.
@115ek,
I need a stock boot.img of the Z1c to patch it with the Magisk Manager.
All my tries failed: the ROM is always booting fine but neither Magisk nor Magisk Manager are installed.
This is happening with all Magisk >v20.4.
Every boot.img in the Lineage and AICP ROMs are different. Which one can I use?
I have TWRP backups from Android 5.1.1 but I don't know how to extract the boot.img.
Edit:
In the meantime I could extract the kernel.elf from the original firmware tft and convert this file with Android Image Kitchen to a boot.img. But this is ~ 2 MB bigger than yours in your ROM.
New Build is up:
using snap camera now (instead of camera2)
fixed NFC (thanks @AdrianDC)
tramp20 said:
Perhaps you see something in this logfile.
Click to expand...
Click to collapse
Not a the first sight, unfortunately.
tramp20 said:
This is happening with all Magisk >v20.4.
Click to expand...
Click to collapse
Earlier versions work fine?
tramp20 said:
Which one can I use?
Click to expand...
Click to collapse
None. The kernel needs one specific commit, pre-11 kernels don't have. Else it won't boot.
Besides that, you'd have to add a androidboot.selinux=permissive to the kernel command-line as this 11 build is still permissive.
115ek said:
Earlier versions work fine?
Click to expand...
Click to collapse
Yes, all up to 20.4.
The same problem exist with lineage 17.1.
A happy new year to all and thanks for the builds.