{
"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/samsung/device_samsung_crownlte
https://gitlab.com/iode/os/public/devices/samsung/device_samsung_universal9810-common
kernel:
(iodéOS 1.x) https://github.com/LineageOS/android_kernel_samsung_universal9810
(iodéOS 2.x) https://github.com/synt4x93/android_kernel_samsung_universal9810
(iodéOS 3.x) https://github.com/universal9810/android_kernel_samsung_exynos9810
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 3.x / 4.x
Due to an incompatibility in the data encryption method, a factory reset is required to migrate from iodéOS 2 to iodéOS 3 or later. It can be installed as OTA by using this updater. Backup your data before proceeding.
The data format must be performed with iodé's recovery, not TWRP, which can be found here.
04/04/2023 (build 20230401):
Upgrade to iodéOS 4.1 based on Android 13 / LineageOS 20
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):
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 20221512):
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
Downloads : iodéOS 2.x
24/10/2022 (build 20221024):
Hotfix build for keyboard not showing in decryption page.
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):
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/2021 (build 20220129):
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
03/12/2021 (build 20211129):
Fixes DRM (downgraded from L1 to L3)
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
Data partition encryption is now automatically triggered on non encrypted devices. Backup your data first, some users reported that their data has been wiped. We're very sorry for the inconvenience.
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)
Bixby key now configurable (short press only, Settings -> System -> Buttons)
10/09/2021 (build 20210828):
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 20210121):
LineageOS sources synced (AOD and glove mode now available)
Prebuilt apps updated
Activated Camera APIv2 in Snap
Added AudioFX
Added fast charge disabler
Disabled broken widevine DRM L1, now fallback to L3
Force auto-update of apps in FDroid to keep in sync with iodé apps. It can be disabled.
25/12/2020 (build 20201224): first publicly available build for Samsung Galaxy Note 9.
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.
[/LIST]
CSM Fol said:
I have a question: All AOSP-based Android 10 ROM's are plagued with this issue: There is massive touch delay/sensitivity issues when playing mobile games (Source 1, Source 2).
And because this ROM is based on AOSP, is this bug also present? I don't have time to try out any custom ROM's now, so I kindly ask.
Click to expand...
Click to collapse
Get your Nope4 back
ps: how's life Steve?
how do i decrypt this?
bobwhite11 said:
how do i decrypt this?
Click to expand...
Click to collapse
How do you decrypt what ?
nice, definitely gonna try this
bobwhite11 said:
how do i decrypt this?
Click to expand...
Click to collapse
To avoid forced encryption on first boot and make it optional to enable from device settings with official lineage or roms based on the official trees like this. You should use vendor_overlay for a modified fstab, or modify your stock vendor fstab.
Something like this synt4x93/android_device_samsung_universal9810-common/commit/67db1379fc6850228310525ffb1f4ec8df95f26e
vince31fr said:
How do you decrypt what ?
Click to expand...
Click to collapse
I assume he is talking about decrypting /data in recovery and is unable to do so because of forced encryption.
=== New Update : 22/01/2021 ===
Available as OTA (see OP)
when i try to start a call, doesnt appera call screen
so i cant stop a call or use speakerphone on samsung Note 9
So far so good - everything seems very stable and I haven't encountered any annoying bugs after roughly a day of use. Only issues I've had are as follows:
1. Developer mode
It says it has worked after tapping the build number repeatedly but then I don't see any Developer Options available in the settings. Am I missing something?
Scrap that, I finally found it. Under Settings -> System -> Advanced -> Developer options. Looks like the only 'problem' was my unfamiliarity with LineageOS changes to settings menus.
2. Limited USB connectivity
I can't see the phone at all when connected to a PC via USB cable and booted normally. I've gone into Developer Settings and set default USB mode to 'file sharing' but it still doesn't show up and I don't get any option to change the mode as I would normally expect. The device is detected fine in bootloader and recovery modes. I've tried different USB cables and a different laptop to help rule those possibilities out. Has anyone else encountered this problem?
3. Forced encryption
Synt4x.93 said:
If any users want to do this without recompiling, just put the modified fstab from that commit in /system/product/vendor_overlay/29/etc/fstab.samsungexynos9810 and set the usual permissions and format /data again.
Click to expand...
Click to collapse
Direct file link for anyone else with the same need: https://raw.githubusercontent.com/s...8df95f26e/rootdir/etc/fstab.samsungexynos9810
To access /system I assume you need root access. Typically I would do this by flashing Magisk but I can't flash anything from recovery without a full wipe when the data partitions are encrypted. How does one get around this chicken-and-egg problem?
Fixed with a generic script
FerretallicA said:
So far so good - everything seems very stable and I haven't encountered any annoying bugs after roughly a day of use. Only issues I've had are as follows:
1. Developer mode
It says it has worked after tapping the build number repeatedly but then I don't see any Developer Options available in the settings. Am I missing something?
Scrap that, I finally found it. Under Settings -> System -> Advanced -> Developer options
2. Limited USB connectivity
I can't see the phone at all when connected to a PC via USB cable and booted normally. I've gone into Developer Settings and set default USB mode to 'file sharing' but it still doesn't show up and I don't get any option to change the mode as I would normally expect. The device is detected fine in bootloader and recovery modes. I've tried different USB cables and a different laptop to help rule those possibilities out. Has anyone else encountered this problem?
3. Forced encryption
Direct file link for anyone else with the same need: https://raw.githubusercontent.com/s...8df95f26e/rootdir/etc/fstab.samsungexynos9810
To access /system I assume you need root access. Typically I would do this by flashing Magisk but I can't flash anything from recovery without a full wipe when the data partitions are encrypted. How does one get around this chicken-and-egg problem?
Click to expand...
Click to collapse
2. Connect Phone to PC then press "Charging this device via USB" from notification the choose file transfer
3. i flash the Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip it disable the forced encryption
the only bug i found is from front camera when "selfie mirror" is enabled the camera app will crash after capture
If anyone else wants to get their Note 9 up and running with this ROM with minimal hunting around, here's what I'd suggest (assuming coming from a stock firmware). You will end up with iode + Magisk + no 'data' encryption (so for example you can still access your Data partition from recovery).
You will need:
Odin installer from https://odindownload.com/download/
Tested with: https://odindownload.com/download/Odin3_v3.13.3.zip
(there is a newer version 3.14.1 but I already had 3.13.3 so tested with that)
TWRP installer in .img.tar format from https://twrp.me/samsung/samsunggalaxynote9.html
Tested with: https://dl.twrp.me/crownlte/twrp-3.5.0_9-1-crownlte.img.tar.html
lode ROM from https://github.com/iodeOS/ota/releases/tag/v1-crownlte
Tested with: https://github.com/iodeOS/ota/releases/download/v1-crownlte/iode-1.1-20201224-crownlte.zip
Magisk zip installer from https://github.com/topjohnwu/Magisk
Tested with: https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-v21.4.zip
Disable DmVerity ForceEncrypt fix from https://github.com/Zackptg5/Disable_Dm-Verity_ForceEncrypt
Tested with: https://androidfilehost.com/?fid=17248734326145725184
and also a PC for running the Odin software.
Summary of install steps
Update phone to latest official firmware
Restart phone in bootloader mode and flash TWRP with Odin. If you've never done this before there is a decent guide here: https://www.droidthunder.com/install-twrp-recovery-on-samsung
Restart phone in Recovery mode (TWRP).
Use Wipe -> Format to completely wipe the existing Data partition.
Copy the iode, Magisk and 'disable forced encryption' zip files to your phone. Then from TWRP install them in order of iode, Magisk and "Disable DmVerity ForceEncrypt". Do not restart the device in between each step.
andrikv said:
2. Connect Phone to PC then press "Charging this device via USB" from notification the choose file transfer
3. i flash the Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip it disable the forced encryption
Click to expand...
Click to collapse
2. it doesn't work. There is no such prompt on the phone. It's weird because I can see the phone just file and transfer files in recovery mode, just not when booted into the main OS. It works on pretty much every other Note 9 ROM i've tried for more than 5 minutes.
3. Thanks, I went by that route too in the end.
Having used this for over a week now, just reporting back that it has been rock solid and I get around 2.5 days of fairly average use between needing to charge.
Regarding the not showing up PC connection issue, it started working when I flashed the no-encrypt patch immediately after flashing the main ROM image. I'm not sure if it is directly related but I'm happy it's working anyway.
This is going to be my daily driver for the foreseeable future. Thanks to both Lineage and iode teams for making it easier than ever to have a stable and functional Android device with as little Google snoopery as possible. Great work!
Is there any way to add additional rules to the iode blacklist? It's all very well having a built-in firewall of sorts and dashboard showing blocked traffic but it's kind of useless if you can't easily add things to it (e..g Facebook tracking URLs which aren't blocked by iode by default)
FerretallicA said:
Is there any way to add additional rules to the iode blacklist? It's all very well having a built-in firewall of sorts and dashboard showing blocked traffic but it's kind of useless if you can't easily add things to it (e..g Facebook tracking URLs which aren't blocked by iode by default)
Click to expand...
Click to collapse
Hi,
not yet possible but we will add blocklists in march, and the possibility to tweak your own hosts in the following months. You can also join our beta tester group if you want to get updates a little sooner than official OTAs
iodeOS said:
Hi,
not yet possible but we will add blocklists in march, and the possibility to tweak your own hosts in the following months. You can also join our beta tester group if you want to get updates a little sooner than official OTAs
Click to expand...
Click to collapse
Where can I apply for beta testing?
Rubennino said:
Where can I apply for beta testing?
Click to expand...
Click to collapse
You'll find a telegram link in the news app (FAQ 'how to contribute')
=== New Update : 07/03/2021 ===
Available as OTA (see OP)
Related
GravityBox - all-in-one tweak box - Xposed module for devices running AOSP Oreo
Version 8.6.0 [Oreo]
Version for JellyBean is available in this thread: https://forum.xda-developers.com/showthread.php?t=2316070
Version for KitKat is available in this thread: https://forum.xda-developers.com/showthread.php?t=2554049
Version for Lollipop is available in this thread: https://forum.xda-developers.com/showthread.php?t=3037566
Version for Marshmallow is available in this thread: https://forum.xda-developers.com/showthread.php?t=3251148
Version for Nougat is available in this thread: https://forum.xda-developers.com/showthread.php?t=3653953
READ THIS POST CAREFULLY BEFORE PROCEEDING ANY FURTHER
Introduction
The app utilizes amazing Xposed framework coded by recognized developer rovo89 which, briefly, provides interface for injecting code into any app, including system services, allowing modifications of applications and system services at run-time. One of the biggest advantages of GravityBox is that it is not bound to any specific device. Actually, it should run on any device having vanilla Android 8 (ROM close enough to AOSP).
This project wouldn't be possible without rovo's Xposed framework, so huge kudos to him.
Feature highlight
--- Lockscreen tweaks
--- QuickSettings tile management with additional tiles
--- Statusbar tweaks
--- Navigation bar tweaks
--- Pie controls
--- Power tweaks
--- Display tweaks
--- Phone tweaks
--- Media tweaks
--- Hardware/navigation key actions
--- GravityBox Actions - interface for 3rd party apps
--- Notification control (per-app notification LED/sounds/vibrations)
--- Fingerprint launcher
--- Advanced tuning of Framework and System UI parameters
... and many more
Compatibility
GB's main concept is to make most of the preference changes to be done on the fly without need to reboot a device to achieve custom-ROM like experience.
This means it is not possible to "completely deactivate" particular feature if it causes trouble on your device or if you installed GB because you want to use only one particular feature you can't find elsewhere.
This results in issues on ROMs/devices that have parts that are diverting from default Android implementation too much, or are running heavily modified custom ROMs.
If you experience weird issues after installing GB, even if you didn't activate a particular feature, it is not because of GB is broken, it is because it is not compatible with your ROM.
It is very similar to a situation when you installed ROM built from source for Nexus to some Xperia device - it won't work.
GB is a complex module and is not suitable for 1 purpose scenario. This means, if you are running custom ROM built from source, and you are missing a certain feature, your best option is to go ask creators of those ROMs to implement those additional features. Supplementing missing features on well-known custom ROMs built from source by installing xposed modules (especially complex ones) is definitely not a good way to go and can cause more trouble than good.
GB being a complex module, it shouldn't be combined with other complex modules often racing for the same goal. They can conflict/fight on the same playground and there's no way you can deterministically say which one's going to win. They can even lose both.
So in summary:
- this module is designed to run on vanilla or close-to-vanilla Android 8 (AOSP)
- officially supports devices/systems it was developed and tested on
- Samsung Touchwiz, HTC Sense, MIUI, LeWa, Xperia, Lenovo, etc. are NOT supported. It is not guaranteed this module will work on these at all so try at your own risk. This module is simply too complex to support all kind of ROM brands that were vastly modified by vendors.
- DO NOT USE WITH CUSTOM ROMS MODULE WAS NOT EXPLICITLY DESIGNED FOR
- I will not implement any exceptions that will adapt this module to a specific custom ROM. Please, do understand, it is unmanageable.
- I will not provide any support for devices violating these compatibility rules
GravityBox [O] has been designed for and tested on
- Nexus 5X running stock 8.0
- Nexus 5X running stock 8.1
- OnePlus 3T running official OOS 5.0.1
Reporting bugs
If you experience problems with certain feature, provide the full-detailed info that can help me
to reproduce the bug and attach error.log file you'll find in:
/data/user_de/0/de.robv.android.xposed.installer/log
In case you experience SystemUI crashes or other apps Force Closing, or device soft reboots, attach logcat from time
crash occurs. (use adb logcat *:E or your favorite logcat app from Play Store).
Please, don't attach big logs. Only the portion where error is clearly seen.
Disable all other xposed modules before reproducing bug to make sure it is really GravityBox related
Remember, this app was developed and tested on one particular device so it is not guaranteed that it will work flawlessly on yours.
Click here to read additional, more detailed info on Reporting bugs provided by @trjlive
Multilanguage support
Volunteers are welcome to translate GravityBox to other languages.
Simply download this file: https://github.com/GravityBox/GravityBox/raw/oreo/res/values/strings.xml
Use Notepad++ to edit strings and then send me edited file so I can include translations into next release.
Source code
GravityBox is opensource. Sources are available in my gihub: https://github.com/GravityBox/GravityBox/tree/oreo-as-edxposed
If you're a dev and have some ideas for additional features, feel free to fork it, work on it and send the pull requests.
Copyright notice
https://github.com/GravityBox/GravityBox/blob/oreo/NOTICE
Support development
Coding, maintaining and supporting this project costs me a lot of my precious time. If you find this project useful, you are more than welcome to support its development via donation. This form of support is meant to compensate for my time dedicated to the community + eventually, help me to afford newer device to keep up with AOSP evolution thus providing continuous support as Android evolves. Thanks!
Info about premium features and PayPal transaction ID verification system
1) Those who supported development via PayPal donation can use their PayPal transaction ID to unlock premium features.
As of v2.9.5, there are two premium features:
- Backup/restore of GB settings.
- Ultimate notification control
2) If you contributed to the project by providing translations, code fragments, or by any other way
you can apply for a free transaction ID by contacting me via PM.
3) Be aware that there's a system that can identify potential transaction ID
abuse. E.g. when one ID is being used by more users. Such IDs will get blocked automatically.
This can also happen when you previously exposed your ID in public forum and other users took
advantage of it. If this is the case, contact me via PM so I can issue new, special ID.
In case you own more devices, you can use one transaction ID on up to 10 of them.
4) If you are using your own custom builds of GB for personal use, you will get hash mismatch
upon verifying your ID as verification system accepts requests only from official releases of GB.
If you want to be able to verify IDs with your custom build, contact me via PM so I can setup
a special hash for your build.
If you are using a custom build that you provide for broader group of users (e.g. in a custom ROM),
it is necessary to ask for new hash everytime your new custom version is released for public use.
These rules are based on mutual trust so please, do not violate them.
Credits
- @bgcngm for his code contributions to the project
- @MohammadAG for Xperia specific contributions to the project
- @rovo89 for his ultimate Xposed framework and "Volume keys to skip track" mod
- @peptonib for starting me up with this project
- @simmac for app icon
- @romracer for Motorola specific code contributions
- @firefds for Samsung specific code contributions
- CyanogenMod project
- ParanoidAndroid project
- Slim, RootBox, AOKP, OmniROM projects
- Sergey Margaritov for ColorPickerPreference
- All those who provided translations for different languages (Mr.Premise, peptonib, kidmar, ch-vox, romashko, Indiant, lelemm, oicirbaf, unavix, LuHash, WedyDQ10, mp3comanche, awaaas, liveasx, samsonbear, Eric850130, xtrem007, benjoe1, asmb111, Fatih Firinci, ...)
- and finally, all those who keep the project alive by supporting me via donations (you know who you are)
Changelog
https://github.com/GravityBox/GravityBox/blob/oreo-as-edxposed/CHANGELOG.txt
Changelog 8.6.0 - 14/02/2021
- Added compatibility with EdXposed v0.5+ and LSPosed
- Added support for LSPosed module scope feature (auto-whitelist)
- Maintains backwards compatibility with EdXposed v0.4 and OG Xposed Framework
--- moving from old OG Xposed Framework to EdXposed/LSPosed is now strongly recommended, though!
- Does not require Xposed Resource Hooking support to be enabled anymore!
- Resource replacement:
--- redesigned for better compatibility and performance
--- implemented support for aliased resources pointing to Framework resources
--- Added support for resource overlays:
------ improves Advanced Tuning compatibility with systems using Theme overlays
------ fixes "Remove corner padding" option on Nokia (and other) devices
------ fixes hiding navigation bar by disabling "Enable navigation bar" option in Navbar tweaks
- StatusbarClock: respect time zone changes when showing seconds
- StatusbarClock: keep master switch for Clock tweaks off by default (thanks to aviraxp)
- Media: improved compatibility of More music volume steps feature
- Keys: improved reliability of Torch on power long-press
- ImagePicker: use dedicated library for cropping images instead of unreliable camera CROP intent
- About: added references to EdXposed and Riru
- Fixed XSharedPreferences Unexpected EOF errors showing in Xposed log
- Fixed layout/scaling of all GravityBox view elements affected by DPI change when screen resolution changes
IMPORTANT: Module settings are reset when framework is upgraded from EdXposed v0.4/OG Xposed to EdXposed v0.5.1+/LSPosed
due to changes in preferences storage location for modules in EdXposed v0.5/LSPosed
It is recommended to create a backup of GravityBox settings before upgrading the framework.
Developed and tested on:
- Nexus 5X running stock 8.0
- Nexus 5X running stock 8.1
- OnePlus 3T running stock OOS 5.0.1 and Beta
Download
Release 8.6.0 · GravityBox/GravityBox
Added compatibility with EdXposed v0.5+ and LSPosed Added support for LSPosed module scope feature (auto-whitelist) Maintains backwards compatibility with EdXposed v0.4 and OG Xposed Framework --- ...
github.com
EdXposed / LSPosed
Modules is compatible with EdXposed as well as LSPosed
Required whitelisted packages
- Android System (android)
- System UI (com.android.systemui)
- Call Management (com.android.server.telecom)
- Download Manager (com.android.providers.downloads)
- Phone (com.android.dialer or com.google.android.dialer)
- Phone (com.android.incallui) (OxygenOS only)
Important info about GravityBox and Oreo
Preferences and SeLinux
Although there is a limitation in current beta of Xposed Framework which prevents modules from reloading preferences within Android process,
GravityBox has been redesigned to overcome that limitation. This means enforced SeLinux is fully supported and thus it is not necessary to run Permissive.
Navigation bar tweaks on Pixel devices running proprietary Google SystemUI plugin
As I currently don't own any Pixel device I didn't have a chance to test nor adjust related features for such scenario.
I cannot tell how their plugin affects the way module works but let's wait for some feedback.
It is also possible that Navigation bar tweaks is not the only place where incompatibilities may show up.
Expanded Desktop in Oreo 8.1
Expanded Desktop is currently not fully supported in Oreo 8.1 (seems to be working fine in 8.0, though).
Despite there are almost no differences in related Android system parts between 8.0 and 8.1, I didn't manage to fix it, and I am currently not sure what's causing a differnt behavior.
There are only 2 modes available in 8.1 - Hide navigation bar and Semi-immersive (which is also temperamental)
Data activity indicator for Cellular icon
Due to changes in stock signal cluster layout type it is no longer possible to put activity indicators on top of a signal icon.
Therefore this feature has been redesigned to place narrov view containinig indicators right beside the signal icon.
WiFi is OK - there were no changes in layout type.
Notification drawer style in Oreo 8.1
Custom wallpaper/color for notification drawer is currently not supported in 8.1.
QuickSettings management
QS management has been massively redesigned for compatibility with stock SystemUI tuner back in Nougat and the same approach is taken for Oreo.
GB doesn't provide tile reordering functionality anymore. It only provides interface for enabling/disabling GB specific tiles and setting their protected mode (and other settings).
There are 2 checkboxes for each tile in the list - the first checkbox is for enabling/disabling tile, the second one is for protected mode.
There are also several stock tiles in the list with only the second checkbox - for setting protected mode (prevents using tile when device locked).
SystemUI tuner shows only those GB tiles that are enabled in GB QS management.
Use stock tile management to drag and drop GB tiles to desired slots.
Settings from Nougat
It should be possible to restore backup of the settings made in N version of GravityBox.
Full history of changes for transition from N to O
https://github.com/GravityBox/GravityBox/compare/v7.0.6_n...v8.0.0-beta-1_o
Nice work!
Yeah Doe!!!!
Looking forward to test this! Great job!
I just tried this on my Google Pixel on Android 8.1 and I know you were asking this in the OP but all of the navigation bar tweaks I tried work perfectly! Every single tweak I tried works. If you would like me to test anything out for you on my Pixel, let me know.
Thank you so, so much for this. You have no idea how extruciating it was waiting for Xposed to get ported to Oreo and then GravityBox. It is my most-used mod and hoenstly the only thing keeping me using Android. You have no idea how much better of a phone experience I have with GravityBox.
You are amazing. Thank you again.
Absolutely fantastic work mate! So cool we can enjoy the great GB so soon!
Battery icon position not correct please fix this
I "finally" worked out all of the bugs with the N rom I am using on my OnePlus 5 and then you release this most awaited gem today... HALLELUJAH! :highfive:
nice work!
What a sight of relief!
Thanks
thank you for your work! i donate when i get it to work?
my Problem : systemless xposed on pixel2xl, gravitybox dont recognize xposed.. - "waiting on gravitybox system framework" - > "framework closed" :S
Blooddrunked said:
thank you for your work! i donate when i get it to work?
my Problem : systemless xposed on pixel2xl, gravitybox dont recognize xposed.. - "waiting on gravitybox system framework" - > "framework closed" :S
Click to expand...
Click to collapse
Make a full reboot after enabling the module
Sent from my Google Pixel 2 XL using XDA Labs
@C3C076 is there any way to get some type of extended SystemUI tuner function? Like how on stock you can get rid of certain status bar icons. Custom ROMs have all icons exposed so you can get rid of them. Like the VPN key for instance. Thanks so much for this. Definitely gonna be making a donation ?
Prattham said:
Make a full reboot after enabling the module
Click to expand...
Click to collapse
i did
Blooddrunked said:
i did
Click to expand...
Click to collapse
My setup is same and it works fine
Sent from my Google Pixel 2 XL using XDA Labs
What are the Tweaks under fingerprint launcher ? Do it enables fingerprint gestures ?
Nice work though
Sahib Pandotra said:
What are the Tweaks under fingerprint launcher ? Do it enables fingerprint gestures ?
Nice work though
Click to expand...
Click to collapse
You can define action for each enrolled fingerprint independently. Thus you can use different fingers for different actions + one quick tap action.
It's just my "must have" what a release! Thank you!
Ps:working like a charm on S4 i9505 Oreo 8.1 AOSP JDCTeam.
GravityBox - all-in-one tweak box - Xposed module for devices running Android Pie
Version 9.2.1 [Pie]
Version for JellyBean is available in this thread: https://forum.xda-developers.com/showthread.php?t=2316070
Version for KitKat is available in this thread: https://forum.xda-developers.com/showthread.php?t=2554049
Version for Lollipop is available in this thread: https://forum.xda-developers.com/showthread.php?t=3037566
Version for Marshmallow is available in this thread: https://forum.xda-developers.com/showthread.php?t=3251148
Version for Nougat is available in this thread: https://forum.xda-developers.com/showthread.php?t=3653953
Version for Oreo is available in this thread: https://forum.xda-developers.com/showthread.php?t=3739929
READ THIS POST CAREFULLY BEFORE PROCEEDING ANY FURTHER
Introduction
The app utilizes Riru and EdXposed Magisk module which uses original Xposed Framework API created by rovo89.
!!!!!! WARNING !!!!!!
This module utilizes EdXposed Framework which is still in early development stage and may contain bugs or might not be fully compatible with system of your Android device. I take no responsibility for any issues arising from using GravityBox with EdXposed and strongly recommend creating a full backup of your device before activating the module.
Requirements
- Magisk v17 or later
- Riru v16 or later
- EdXposed v0.3.0.0-beta2 or later
- EdXposed Installer v2.2.1 or later
Installation
This procedure assumes you have working Magisk installation.
1) Install Riru and EdXposed modules using Magisk Manager
2) Install EdXposed Installer app
3) Reboot and open EdXposed Installer app to check if EdXposed works and is active
4) Install GravityBox and enable it in EdXposed Installer
5) Reboot
Required whitelisted packages
In case you use blacklist/whitelist functionality of EdXposed make sure all the following packages are whitelisted (not blacklisted respectively) for full GravityBox experience.
- Android System (android)
- System UI (com.android.systemui)
- Call Management (com.android.server.telecom)
- Download Manager (com.android.providers.downloads)
- Phone (com.android.dialer or com.google.android.dialer)
- Phone (com.android.incallui) (OxygenOS only)
Feature highlight
--- Lockscreen tweaks
--- QuickSettings tile management with additional tiles
--- Statusbar tweaks
--- Navigation bar tweaks
--- Pie controls
--- Power tweaks
--- Display tweaks
--- Phone tweaks
--- Media tweaks
--- Hardware/navigation key actions
--- GravityBox Actions - interface for 3rd party apps
--- Notification control (per-app notification LED/sounds/vibrations)
--- Fingerprint launcher
--- Advanced tuning of Framework and System UI parameters
... and many more
Compatibility
GB's main concept is to make most of the preference changes to be done on the fly without need to reboot a device to achieve custom-ROM like experience.
This means it is not possible to "completely deactivate" particular feature if it causes trouble on your device or if you installed GB because you want to use only one particular feature you can't find elsewhere.
This results in issues on ROMs/devices that have parts that are diverting from default Android implementation too much, or are running heavily modified custom ROMs.
If you experience weird issues after installing GB, even if you didn't activate a particular feature, it is not because of GB is broken, it is because it is not compatible with your ROM.
It is very similar to a situation when you installed ROM built from source for Nexus to some Xperia device - it won't work.
GB is a complex module and is not suitable for 1 purpose scenario. This means, if you are running custom ROM built from source, and you are missing a certain feature, your best option is to go ask creators of those ROMs to implement those additional features. Supplementing missing features on well-known custom ROMs built from source by installing xposed modules (especially complex ones) is definitely not a good way to go and can cause more trouble than good.
GB being a complex module, it shouldn't be combined with other complex modules often racing for the same goal. They can conflict/fight on the same playground and there's no way you can deterministically say which one's going to win. They can even lose both.
So in summary:
- this module is designed to run on vanilla or close-to-vanilla Android 9 (AOSP)
- officially supports devices/systems it was developed and tested on
- Samsung Touchwiz, HTC Sense, MIUI, LeWa, Xperia, Lenovo, etc. are NOT supported. It is not guaranteed this module will work on these at all so try at your own risk. This module is simply too complex to support all kind of ROM brands that were vastly modified by vendors.
- DO NOT USE WITH CUSTOM ROMS MODULE WAS NOT EXPLICITLY DESIGNED FOR
- I will not implement any exceptions that will adapt this module to a specific custom ROM. Please, do understand, it is unmanageable.
- I will not provide any support for devices violating these compatibility rules
GravityBox [P] has been designed for and tested on
- Nexus 5X running Pixel Experience Android Pie 9.0
- OnePlus 3T running OxygenOS
- OnePlus 7 Pro running OxygenOS
- Pixel 3a running Google OS
Reporting bugs
If possible, please use Github issue reporting interface for reporting bugs.
If you experience problems with certain feature, provide the full-detailed info that can help me
to reproduce the bug and attach error.log file you'll find in:
/data/user_de/0/com.solohsu.android.edxp.manager/log
If you use different manager or there is no log file present, use ADB to capture log: adb logcat -s EdXposed-Bridge
In case you experience SystemUI crashes or other apps Force Closing, or device soft reboots, attach logcat from time
crash occurs. (use adb logcat *:E or your favorite logcat app from Play Store).
Please, don't attach big logs. Only the portion where error is clearly seen.
Disable all other xposed modules before reproducing bug to make sure it is really GravityBox related
Remember, this app was developed and tested on one particular device so it is not guaranteed that it will work flawlessly on yours.
Click here to read additional, more detailed info on Reporting bugs provided by @trjlive
Multilanguage support
Volunteers are welcome to translate GravityBox to other languages.
Simply download this file: https://github.com/GravityBox/GravityBox/raw/pie/GravityBox/src/main/res/values/strings.xml
Use Notepad++ to edit strings and then send me edited file so I can include translations into next release.
Source code
GravityBox is opensource. Sources are available in my gihub: https://github.com/GravityBox/GravityBox/tree/pie
If you're a dev and have some ideas for additional features, feel free to fork it, work on it and send the pull requests.
Copyright notice
https://github.com/GravityBox/GravityBox/blob/pie/NOTICE
Support development
Coding, maintaining and supporting this project costs me a lot of my precious time. If you find this project useful, you are more than welcome to support its development via donation. This form of support is meant to compensate for my time dedicated to the community + eventually, help me to afford newer device to keep up with AOSP evolution thus providing continuous support as Android evolves. Thanks!
Info about premium features and PayPal transaction ID verification system
1) Those who supported development via PayPal donation can use their PayPal transaction ID to unlock premium features.
As of v2.9.5, there are two premium features:
- Backup/restore of GB settings.
- Ultimate notification control
- Advanced tuning
2) If you contributed to the project by providing translations, code fragments, or by any other way
you can apply for a free transaction ID by contacting me via PM.
3) Be aware that there's a system that can identify potential transaction ID
abuse. E.g. when one ID is being used by more users. Such IDs will get blocked automatically.
This can also happen when you previously exposed your ID in public forum and other users took
advantage of it. If this is the case, contact me via PM so I can issue new, special ID.
In case you own more devices, you can use one transaction ID on up to 10 of them.
4) If you are using your own custom builds of GB for personal use, you will get hash mismatch
upon verifying your ID as verification system accepts requests only from official releases of GB.
If you want to be able to verify IDs with your custom build, contact me via PM so I can setup
a special hash for your build.
If you are using a custom build that you provide for broader group of users (e.g. in a custom ROM),
it is necessary to ask for new hash everytime your new custom version is released for public use.
These rules are based on mutual trust so please, do not violate them.
Credits
- @bgcngm for his code contributions to the project
- @MohammadAG for Xperia specific contributions to the project
- @rovo89 for his ultimate Xposed framework and "Volume keys to skip track" mod
- @peptonib for starting me up with this project
- @simmac for app icon
- @romracer for Motorola specific code contributions
- @firefds for Samsung specific code contributions
- CyanogenMod project
- ParanoidAndroid project
- Slim, RootBox, AOKP, OmniROM projects
- Sergey Margaritov for ColorPickerPreference
- All those who provided translations for different languages (Mr.Premise, peptonib, kidmar, ch-vox, romashko, Indiant, lelemm, oicirbaf, unavix, LuHash, WedyDQ10, mp3comanche, awaaas, liveasx, samsonbear, Eric850130, xtrem007, benjoe1, asmb111, Fatih Firinci, ...)
- and finally, all those who keep the project alive by supporting me via donations (you know who you are)
Changelog
https://github.com/GravityBox/GravityBox/blob/pie/CHANGELOG.txt
Changelog 9.2.1 - 07/03/2021
- Added support for LSPosed module scope feature (auto-whitelist)
- BatteryPercent: fixed percent text injection not working on some systems
- BatteryPercent: follow status bar clock appearance
- Clock: reverted to old hooking strategy for better compatibility
- Dialer: adjusted for compatibility with the latest Google Dialer
--- fixes muting Dialpad tones during UNC Quiet Hours
Developed and tested on:
- Nexus 5X running Pixel Experience ROM
- OnePlus 3T running OxygenOS
- OnePlus 7 Pro running OxygenOS
- Pixel 3a running Google OS
Download
https://github.com/GravityBox/GravityBox/releases/tag/v9.2.1_p
Also available in official Xposed Repository as well as LSPosed repository.
Required whitelisted packages
In case you use blacklist/whitelist functionality of EdXposed make sure all the following packages are whitelisted (not blacklisted respectively) for full GravityBox experience.
- Android System (android)
- System UI (com.android.systemui)
- Call Management (com.android.server.telecom)
- Download Manager (com.android.providers.downloads)
- Phone (com.android.dialer or com.google.android.dialer)
- Phone (com.android.incallui) (OxygenOS only)
Commit history
Full commit history for transition from 9.2.0 to 9.2.1
Full commit history for migration from Oreo to Pie
Don't know if it's still a thing.. but first! Great job btw! Many, many people were waiting for this. Keep up the good work and thank you for all the work you've done and continue to do for the XDA family!
Finally ?️
Thank you for great works and your effort! ??️
Fair play to you lad...hats off to you!
Thank you for your amazing hard work down through the years here on Xda
...you bring pleasure to our phones...
??
-Center clock mode does not working and when I turn it on, send me to the lock screen.
-Volume step increaser seems just added more steps cause it automatically start again same as 0 to 15th and 16th to 30.
-Lock screen tweaks also not working for me.
-Battery stats works fine
-Status bar brightness control works fine
Great works! Thank you??️
SM-G955F with one ui
At last, finally, thanks dev for your hard work ?
Thanks ?
Sent from my Galaxy S8 using XDA Labs
Wew great work hats off to you :good:
Thank you kind sir!
Working great on latest as of today Canary magisk.
Pixel 3xl stock rooted.
Congratulations for your hard work!
When I updated from Nougat to Oreo I backed up and restored GB settings successfully. Have you tested if it's possible to do the same for Oreo - > Pie?
Sent from my OnePlus 5 using XDA Labs
Kudos to dev for this. Some of the problems i am facing:
Selecting battery bar to show at bottom edge shows just below the status bar.
https://drive.google.com/file/d/1fNzk1RuMuz675FdteahCUNjXNJaKhqLe/view?usp=drivesdk
Data traffic monitor hiding status bar icons when selecting right as location.
https://drive.google.com/file/d/14ZQ8Tacy6HwesCBmZnd9WbS1ui6fPI4b/view?usp=drivesdk
On overriding navigation keys action for back and recents i lose vibration feedback.
Power key long press for torch on screen off doesn't work.
When i toggle system network speed indicator icon the system battery icon is flashed for a little bit and then cancelled.
https://drive.google.com/file/d/1_mG80UM1P-YlYo0WLxnHwxItASj0F_iE/view?usp=drivesdk
Some questions:
The location tile provides battery saver, devuce inly, high accuracy. But google has removed these types in android pie. Does the option work as their names suggest or they have all the same function??
Some requests:
Additonal quick settings row.
Separation of ring and notification volume.
Oneplus 5 Stock OOS
Thanks again for your awesome work. It speaks for itself that so many people have been waiting for exactly this module to be ready for Pie, right @sjamie? So GB and XE are ready, are you?
Anyway, I have literally gone through almost each and every possible setting and I have to state, that GB has never worked so flawlessly before. Not even under Oreo with latest xposed.
I am running stock OOS (9.0.4), Magisk 18.1, latest EdXposed and latest riru and Pi Kernel.
At last, I'd be nice if you could add a PayPal link to the OP, so I can send another donation. Coz through the app the amount is limited to 3 euros and that is simply not enough!
Wow… great efforts
One note
Advance reboot menue does not work. Nothing happen when activated
Thanks a lot
Thank you OP. This projects encourages lot of users to stick with android.
No bugs thus far for what I'm using.
First of all, a big thank you for making this work on pie!
This is the one module that I had no hesitation getting the premium unlock. This is a must have, at least to me!
Okay so I gave it a try as soon as I saw the post of the first beta for pie, and as expected (for note 9) it was working partially. I'm not encluding any logs for now because I'm not expecting you to fix stuff for samsung at the moment or even afterwards (let me know in case you are thinking of supporting One UI someday down the road). So this is more about informing you how good it is on note 9 (korean version N960N), as a tester.
-when I have music visualization enabled and whenever I lock or unlock the screen, the sound effect of V4A stops and return as the visualization appears (poweramp playing music as I'm doing this). The same happens when toggling visualization for navbar; as I'm toggling it on and off the sound effect turns off very very briefly and comes back on. It's like a refresh thingy.
-advanced power menu is not working at all (even after reboots).
-circular battery is working but the percentage inside it looks weird sometimes and sometimes the stock battery icon appears alongside the circular one.
-data traffic indicator works without issues.
-status bar brightness control works only when adaptive brightness is turned off (I guess that's normal?).
-download progress seems to work only for google play downloads (I guess it's normal as well?).
-trusted Wi-Fi works like a charm.
-pie control works but I haven't tinkered will all the options. So far so good.
-one last thing, the color of icons/indicators from gb on status bar always look grey-ish? No matter the status bar color change. So sometimes they are hard to see.
That's all I have tested for now.
You are awesome!
Sent from my SM-N960N using XDA Labs
Thanks, being beta bugs are to be expected. I started with what I use most frequently - will add as I check
Fingerprint actions not working on any of the 5 selected slots (be it apps/shortcuts) - "No app/ action assigned" toast message pops up. Toggle enabled and rebooted. Also disabled from Installer, enabled and rebooted. Didn't help
Stock MiA1 (Android one)
Dropbox ? for EdXposed logs https://www.dropbox.com/s/8lg28md759crgw4/xposed_error_20190308_232340.log?dl=0. I can't see any logs in com. Solohosu....
If you need logs using laptop, it will take a few days
Edit : Same result with GB as only module
Installer log https://www.dropbox.com/s/07bqhhg15xxkv2u/xposed_error_20190309_005557.log?dl=0
Edit 2: Surprisingly, quick tap action works for both shortcuts and apps so it's not a fingerprint issue
Edit 3: Toggling config-fingerprint-support-gestures from false to true and reboot didn't help
Don't know if i'm doing something wrong but i can't get past the framework check at the beggining. Using EdXposed and Magisk 18.1
Moto G6Play
Thank You!! GB is even working fine with v0.2.9.8-beta1
The only thing I miss is
"Swap Volume Buttons in Landscape"
Great Effort, you are a Genius
MIUI 12 is Here!
You have several options to choose from, whether it's the latest and greatest Miui 12 via weekly Xiaomi.EU builds, or the original Beta builds you have several options ( see "Options" below)
___________________________________________________________________________________________________________________
Latest Miui 12 Xiaomi.EU Beta based on Android 10 and with Google Services already included. ( June 18 build see link below)
Miui 12 Xiaomi.EU Stable Beta :Xiaomi.EU globalized version of China Beta Stable with Google Services already included. ( new 11.0.8 - see link below)
China Weekly Beta , Raw unaltered China beta build without Google Services ( Updated yesterday! June 17 build see link below)
China Miui 11 Stable, Raw unaltered China beta build without Google Services ( new 11.0.8 - see link below)
The Xiaomi.EU Stable/ beta builds , include Google services and are deodexed and localized for Western Markets.
{
"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"
}
Option 1
Updated : June 18, 2020
Xiaomi.EU Miui 12
Xiaomi.EU presents Miui 12
DOWNLOAD MIUI 12, 20.6.18 BETA
AFH Link: https://androidfilehost.com/?fid=8889791610682873491
SourceForge Link: https://sourceforge.net/projects/xi...aomi.eu_multi_MI8_20.6.18_v12-10.zip/download
CHANGELOG MIUI 12.0 - 20.6.18
Lock screen
Fix - Incorrect date format for English (UK) locale
Security
Fix - Request dialog for custom permissions were not displayed
Calculator
New - Added more currencies in the currency calculator
Screen time
Fix - Chinese locale was being randomly forced on the app
One-handed mode
Fix - One-handed mode was unavailable when any Accessibility service is active
Themes
Optimization - Remove online content in Settings -> Display -> System font, Settings -> Wallpaper and Settings -> Themes
Fix - Font search results were not visible in dark mode ( Worked fine on the Mi8)
Fix - "Choose online ringtone" option was opening China ringtones channel
Health
New - You can write basic information about your health to be able to show it to health care providers in case of emergency now
New - You can delete data sources now (except of current phone and data sources which have been added manually)
Fix - Inaccurate standing detection and incorrect calculation of exercise intensity during running issues
Fix - Removed "Version" preference in Health app (opened a Xiaomi Market web page, version can still be checked in About)
Fix - Crashes on any screen other than the main screen (Turkish only)
Announcement:
From September 5th, the beta will end for the following devices:
Mi 8, Mi 8 Explorer Edition, Mi 8 Pro (UD), Mi 8 SE, Mi 8 Lite, Mi Max 3, Mi Mix 3, Mi Mix 2S
LIST OF CHANGES VS Miui 11 - Click to reveal
On Monday, April 27 this year, Xiaomi presented the twelfth installment of its overlay on Android phones to the world, i.e. MIUI 12, of course. Since then, our Xiaomi.EU builds have been tested. Today we can present you with screenshots comparing the changes between MIUI 11 and MIUI 12 in the version from Xiaomi.eu. The following phones were used for the presentation: Redmi K30 (MIUI 11, 20.3.26) and Redmi Note 7 (MIUI 12, 20.4.27). On the left, there will be screenshots from the MIUI 11 version, on the right - from the 12th.
Not all changes that were included in the Chinese version will be included in this Rom - Some of those changes were intended only for China and are not well adapted to global conditions, while others have problems with the work with our software - they will be added when it is possible. Without extending, let's start!
Desktop, recent applications, wallpapers
The launcher has not undergone significant changes between versions - the desktop still has a flat form; you can also switch to the application drawer depending on your preferences. One of the biggest new products is certainly the so-called "Super wallpapers" that imitate the appearance of Mars and Earth, creating a very nice and effective animation. Unfortunately, I am not able to demonstrate this function to you, because Redmi Note 7, which I use every day, does not support this functionality (an example from another device is attached below). Currently, the Xiaomi.eu team is not planning to unlock wallpapers for devices other than supported ones.
Update to MIUI 12. This update must be downloaded manually.
The updater will not download it; and an error will be displayed. Next, please also watch for bugs that may appear after the upgrade - some basic recommendations are below the list of changes.
Below are changes recorded between March 26 and April 30, based on applications that appeared during this period, as well as the Chinese changelog:
System Appearance
Novelty- dark theme version 2.0.
According to Xiaomi announcement, it is to, among others, automatically adjust the thickness of the font or contrast to the prevailing conditions
Novelty - a new look for all views
Novelty - new animations
Novelty - the possibility of using floating windows
Novelty- greater focus on user privacy (virtual ID, rigorous control of application permissions, notifications regarding the use of permissions)
Notification panel and switches
Novelty- division into parts only with notifications (dragging from the left) and part only with switches (Control center, dragging from the right). Split can be turned off in the status bar settings
Novelty- new Control Center, including the new appearance of the Time on-screen switches
optimization- visual changes, the new appearance of functions and statistics
App Changes
Camera
Novelty- a new look for the Camera. Currently, it is only available in selected devices - the next ones will receive support gradually as part of the update (according to Xiaomi until the end of May).
Scanner
Novelty - the ability to generate a QR code from the application level (in the settings - gear icon) and save it
Novelty- the ability to enable the history of scanned SMS items
Novelty- the new look of the weather contact selection menu
Novelty- a new look of the Gallery application
Novelty - more sky styles (static and dynamic)
Novelty- the ability to choose transitions between videos as part of the video editor
Changes based on translation - may not be present yet in version 20.4.30
Health
Novelty - the new look of the application
Novelty - dark theme support
Novelty- Xiaomi Watch support (under Data Sources)
MIUI Assistant
Novelty- a card that allows you to view the battery charge status in connected devices via Bluetooth
Safety Guard
After the update, the device memory will contain an image file containing a copy of your / persist partition.
This Precaution was made because of the Xiaomi.EU developers do not know when Google activates new changes in SafetyNet, which will cause the SafetyNet test to be unsuccessful on newer phones.
When these options are activated, the only possibility for SafetyNet to continue to work will be the need to clear the / persist partition, and thus - in the case of new phones - to lose the Widevine L1 certificate (necessary e.g. for watching Netflix in HD quality).
Therefore, the copy is a safeguard against you being able to restore your original / persist and keep your L1 certificate if necessary. The backup will not restore the certificate if you already cleaned the / persist partition and you do not have the Widevine L1 certificate before performing it.
Xiaomi.EU ROMs features that are not in Global):
Based on China Stable / Weekly builds
Enabled search gesture (swipe up) on the desktop
3 way reboot menu (in dev settings)
Dark Mode (Night Mode) for all devices
Removed ads in MIUI system apps
MIUI Dialer and Messages apps
Face Unlock for all devices
Vertical clock widget on lockscreen
Steps counter in Assistant screen
More shortcuts on left lock screen
Wake up gestures for all devices
AI preloading option in MIUI Lab for all devices
Fullscreen gestures for all devices
Option to auto-expand first notification
Notifications priority settings
More edit options in Gallery app
Enabled MiDrive in File Explorer
Added landscape mode for SMS app
Sunrise/Sunset in the weather app
Google apps support integrated
Removed 5GHz region restrictions
Confirm calls from call logs
Morning report on alarm at morning
More apps supported for AOD notifications
More styles for AOD screen
Raise to wake gesture
AOD notification received animation
Default volume control stream toggle
Tap fingerprint sensor to wake toggle
More Camera features
Double tap to lock screen
Battery AI scenes
Allowed disabling specific system apps
Importing theme .mtz from zhuti.xiaomi.com via ThemeManager
No useless Chinese bloatware apps
More free RAM due to less background processes
Unified flat style app icons for both system and 3rd party apps
Advanced menu with color icons
No any Chinese character under the full system
Mi Video, Mi Music, Mi Browser: No any useless Chinese content
No possibility to re-lock bootloader accidentally with flash any xiaomi.eu release
Added real 27 languages translation made by Official MIUI Fan Sites and MIUI Fans
Added EU T9 dialer support
Added charging sound switch
Added Screen-OFF animation
Optimized GPS settings for EU
Optimized Battery consumption
Optimized RAM consumption
Added 3D Touch to MI5S 3GB RAM version
Added GSM alphabet into SMS app options
Added more icons grid layout 4x5, 4x6, 4x7, 5x5, 5x6, 5x7 (depends on device)
SafetyNet passed (Google Pay)
Play Store Certified
Deodexed
Added automated tasks in Security app
Added game speed booster
Added erase module (magic elimination) to Gallery photo edit options
Fixed low volume sound via headphone
Charging screen for all devices
Widevine L1 (for supported devices)
And more, and more made by our 9 years MIUI mods experience.
Xiaomi.eu Multilang Project Leader
___________________________________________________________________________________________________________________
Option 2 - Get the essential details here
Miui 12 Stable - Updated May 28, 2020
Xiaomi.EU Stable 11.0.8 updated has been posted :
Possibly the best battery life of any Miui 11 based rom.
Updated : May 28, 2020
Xiaomi.EU Stable Release Miui MI8 Version 11.0.7.0-
DOWNLOAD MIUIv11.0.7.0 STABLE: xiaomi.eu_multi_MI8_V11.0.7.0.QEACNXM_v11-10
AFH Link: https://androidfilehost.com/?fid=4349826312261810300
SourceForge Link: https://sourceforge.net/projects/xi...lti_MI8_V11.0.8.0.QEACNXM_v11-10.zip/download
Changelog still has not been published.
__________________________________________________________________________________________________________________
Important
These are recovery based roms which means you install them in recovery, for the absolute best performance, and to avoid issues make sure that you have the most recent firmware installed on your device. Get it here: https://xiaomifirmwareupdater.com/firmware/dipper/
Important
Additionally ensure that you always have a full Recovery backup, that includes the persist partition. The link below is for the latest Orange Fox and for the older LR Team version of TWRP both of which will allow you to backup persist separately.
Personally I use the most recent stable version Alpha Orange Fox and in my opinion is now the best recovery for the Mi8.
_________________________________________________________________________________________________________________
Xiaomi.EU Install instructions Here
[/B]GET ORANGE FOX HERE: https://orangefox.download/en/device/dipper
If you prefer a traditional styled version of TWRP, I also recommend TWRP for Xiaomi Mi8 by WZSX150
Official Build : https://dl.twrp.me/dipper/ ( Does not decrypt encrypted data)
Magisk : Magisk Stable and Canary work fine without issues : https://github.com/topjohnwu/magisk_files/tree/canary
Having trouble? follow my instructions here: https://forum.xda-developers.com/showpost.php?p=81390261&postcount=384
Common Courtesy : If myself or anyone else spends their time helping you, do the right thing and return the courtesy by clicking the thank you button. Don't clutter the thread by saying thanks, just click the button.
________________________________________________________________________________________________
Option 3
Updated : June 11, 2020
Miui 12 Q Chinese beta ( Google Services are not pre-installed)
China Closed Beta 20.6.17 : Update : June 17, 2020
If you want to use the Original Miui 12 Q China beta build, and you do not mind the additional setup of Google Services, or simply want reliable use sans Google, this rom is for you..
[DOWNLOAD WEEKLY 20.6.11 ( The most up to date Miui rom available - Currently built on Android 10, is expected to upgrade to Android 11 in late August.)
Miui 12 Weekly beta Build https://hugeota.d.miui.com/20.6.17...iui_MI8_V11.0.8.0.QEACNXM_b6e3f68a98_10.0.zip
Install Google Services by using Google Installer 3.0
link : https://xiaomifirmware.com/download/8105/ or follow steps below
This method works on all unaltered China Roms - Stable and Beta
Open the Settings app.
Click Additional settings'
Click 'Privacy ( bottom of page)
Click Special App Access
Click Install unknown apps
Allow Mi App Store.
Alternate Steps
Open the Mi App Store.
Search for 'Google'
Tap Install next to the top result, may be in Chinese look for Playstore Logo
Once installed press Open, and sign in , once signed everything else needed for Google services will automatically download.
Be sure to give Google apps all of the needed permissions.
_________________________________________________________________________________________________________________
Posting for the convenience of XDA members, all credits and praise should be directed towards the Xiaomi.EU staff
While myself and others are happy to try and help you, I would strongly suggest that you report any unresolved bugs and provide logs file here : https://xiaomi.eu/community/forums/bugs.20/
All credits due go to ingbrzy along with Igor Eisberg, Mark Huk and any other Xiaomi.EU developer or translation contributor that I may have missed.:
https://github.com/ingbrzy
https://github.com/IgorEisberg
https://github.com/vimutter
No ostriches were harmed during the the making of this thread.
Just dirty flash over 9.9.3 and everything is working fine now
I make also dirty flash on .eu stable rom and it's working. However i can't run Antutu bench.
Hi guys
To flash the eu rom should i unlock the bootloader?
Currently i'm with the global beta (june update)
xandreasx said:
Hi guys
To flash the eu rom should i unlock the bootloader?
Currently i'm with the global beta (june update)
Click to expand...
Click to collapse
Yes, unlocked bootloader to install via TWRP
Gustavo RD78 said:
Yes, unlocked bootloader to install via TWRP
Click to expand...
Click to collapse
Thank you
Umh i think that i'll wait the global stable (i hope that it will be released at the same time of china stable)
does this have ARB? I am currently on CR Droid but want to try Miui 11, If I don't like Miui 11, can I still go back to a Pie based rom?
@tsongming i am curious is there any mod / tweak or app to control AOD features? Or is there a way to use AOD as notification lite like when there is a notification it stays lit otherwise off?
Sent from my MI 8 using Tapatalk
ammaralidj said:
@tsongming i am curious is there any mod / tweak or app to control AOD features? Or is there a way to use AOD as notification lite like when there is a notification it stays lit otherwise off?
Sent from my MI 8 using Tapatalk
Click to expand...
Click to collapse
Actually there is a built in AOD notification, with options. it is separate from the AOD clock but within the same area of settings Ambient Display & LockScreen/ "When Notifications come and the screen is off" / Click show animations and then choose one of the 4 new options...this is a cool new feature, that improves upon the miui 10 feature that came on previous builds ( Not sure if that was ever available on the Stable rom) Check it out, it's a sweet option
I will post some screenshots
ammaralidj said:
@tsongming i am curious is there any mod / tweak or app to control AOD features? Or is there a way to use AOD as notification lite like when there is a notification it stays lit otherwise off?
Click to expand...
Click to collapse
Here are some screenshots of of the notification option. These flashes actually flash larger but it was hard to capture in a screenshot.
tsongming said:
Here are some screenshots of of the notification option. These flashes actually flash larger but it was hard to capture in a screenshot.
Click to expand...
Click to collapse
Yes this option is pretty cool also.
[emoji3590] from [emoji1191]
tsongming said:
Here are some screenshots of of the notification option. These flashes actually flash larger but it was hard to capture in a screenshot.
Click to expand...
Click to collapse
One more question please
Is there a way to use Studio Effect (sky change) feature in AOSP roms
View attachment 4832559
ammaralidj said:
One more question please
Is there a way to use Studio Effect (sky change) feature in AOSP roms
View attachment 4832559
Click to expand...
Click to collapse
I couldn't see your attachment, and I am not sure if Mi-Gallery will work on AOSP, it could definitely be modded to work.
V2 update
Any battery life review there
Battery life is horrendous, getting half of what I got with pixel experience and even less compared to MIUI 10.
94burns said:
Battery life is horrendous, getting half of what I got with pixel experience and even less compared to MIUI 10.
Click to expand...
Click to collapse
Not quite sure if you are talking about latest xiaomi.eu 9.9.27 release, because this one is on par if not better than 10 regarding battery life. Keep it running for few days of normal use.
I had few teething issues with notifications, and automatic brightness still quite problematic (autobrightness app removed as pain in the a&&), themes are of limited choice for now, but apart from that it's all good. I'm waiting for new havoc though...
It's a great rom I did not notice any problem until now just the fingerprint issue.
It's not working for me
Thanks for posting about this great update @tsongming - you are always helping users which is always appreciated!
I have started running this from the .EU Miui 11 ROM since the second update. First time trying .EU in since last year. The ROM is so fluid smooth, i might just stay on it for a while. Still disappointed it's based on 9, but hopeful the conversion will happen soon. I am amazed at all of the eye candy and useful features they have incorporated over Global Stable 10.3.5.
I don't have any fingerprint issues that i can find. I did a fresh install over Global 10.3.5 complete with wipe and format originally. The only thing i didn't like about .EU ROMs originally was the lack of encryption for data storage (such a huge risk). HOWEVER, i was able to edited the FSTAB file and enabled it. I had to re-format and setup again, but small price to pay for now fully enabled encryption. I also am running full root (yes still have Gpay working). If there is any interest, I can make a patch to enable encryption for those that would like it, but you have to re-format and setup device again after enabling. There are still some tweaks to gps and a a tiny debloat that could be done, but loving it all so-far.
:good:
Agimax said:
Thanks for posting about this great update @tsongming - you are always helping users which is always appreciated!
I have started running this from the .EU Miui 11 ROM since the second update. First time trying .EU in since last year. The ROM is so fluid smooth, i might just stay on it for a while. Still disappointed it's based on 9, but hopeful the conversion will happen soon. I am amazed at all of the eye candy and useful features they have incorporated over Global Stable 10.3.5.
I don't have any fingerprint issues that i can find. I did a fresh install over Global 10.3.5 complete with wipe and format originally. The only thing i didn't like about .EU ROMs originally was the lack of encryption for data storage (such a huge risk). HOWEVER, i was able to edited the FSTAB file and enabled it. I had to re-format and setup again, but small price to pay for now fully enabled encryption. I also am running full root (yes still have Gpay working). If there is any interest, I can make a patch to enable encryption for those that would like it, but you have to re-format and setup device again after enabling. There are still some tweaks to gps and a a tiny debloat that could be done, but loving it all so-far.
:good:
Click to expand...
Click to collapse
That would be very useful
This is LineageOS 17.1, which is based on Android 10, for the WiFi-only variant of the Samsung Galaxy Tab A 10.1" (2016), codenamed gtaxlwifi. LineageOS doesn't need much of an introduction - It's a well-known custom firmware/Android distribution.
I started these builds because the LineageOS builds from @Valera1978 had 2 particular significant bugs in them that were always being mentioned in posts in that thread: display backlight brightness not changeable from full brightness and the touchscreen appearing to not respond after putting the tablet to sleep. Those bugs had existed for quite a long time. @followmsi has some changes in his 17.1 device tree that fixed those 2 bugs.
These builds really became a continuation of Valera's builds after he unfortunately discontinued work on this device due to an (understandable) lack of interest, with many improvements and additional features.
I've now discontinued these 17.1 builds.
I've long ago moved onto LineageOS 18.1 and 19.1.
Very important note for those upgrading from the releases from 20210523 and 20210413 in this post: https://forum.xda-developers.com/t/lineageos-17-1-for-sm-t580-gtaxlwifi.4059571/post-85106105
Note: I've never had any builds for the LTE variant. However, builds for the WiFi-only variant boot and work on the LTE variant, only without mobile networking (of course), GPS and vibration, so since I've allowed installation on the LTE variant in the last several builds, you can try to use my builds on it if you can go without any of that functionality.
Downloads:
Latest build from 20211116 (with security patch level 20211105):
https://drive.google.com/file/d/14ZCYYcT5b6E9zWiFNgwUP3Kxlvf-dyVn
Folder for these builds (which includes text files with MD5 and SHA256 checksums for the final build, and another folder within it containing some previous builds): https://drive.google.com/open?id=1UiUlSbfj3agDvt-4f_YLIS0Xyuz5RtFC
Changelog:
Final release for 20211116:
Latest updates from LineageOS, including the 20211105 Android security updates.
The WiFi driver has been switched from being a kernel module to being built into the kernel. This may improve reliability for enabling and disabling WiFi and the WiFi hotspot very slightly.
The rewrite of the sepolicy containing all of the SELinux rules that I did for 18.1 has been ported over to 17.1, and so it's now of much better quality.
The audio outputted from the audio jack while playing media will now be noticeably louder, as the headset "DAC1 playback volume" for media has been increased to the maximum of 175 from 162.
An issue where there was additional extremely quiet high-pitched noise from the right speaker has been fixed.
The ZRAM size has been increased to 768MiB.
The BSP sources have been redone to closely match what has been done with the new exynos7880-specific part of Lineage's BSP sources, and with that, there are now more exynos7870-specific changes to the open source gralloc that is in use.
Some miscellaneous cleanups have been done.
The qcom_cfg.ini configuration file for WiFi has been imported from Samsung's A720SKSU5CTL2 firmware - A change within it appears to have made WiFi more reliable.
The system image size has been increased from 3072000000 bytes to 3145728000 bytes, which is the size of the system partition on Korean and Chinese variant T580s and T585s, and the smallest system partition size out of all T580s and T585s.
Some proprietary blobs have been updated as follows:
WiFi and Bluetooth firmwares from Samsung's T390XXS9CUG1 firmware
libexynoscamera3.so library from Samsung's P580ZSS1CTI1 stock firmware - This improves the situation with the issues with stretched/squashed camera previews for images and stretching/squashing in videos at some resolutions
MFC (Multi-Format Codec) firmware from Samsung's A305FDDU6CUI3 firmware
sensors.universal7870.so library from Samsung's P580ZSS1CTI1 stock firmware
As the oldest proprietary blobs are now as in Samsung's P580ZSS1CTI1 stock firmware (with a few exceptions), the vendor security patch level has been increased to 2020-09-01, which is the security patch level that firmware has.
The 32-bit wcnss_filter binary, used for Bluetooth, that was used previously has been replaced with the 64-bit wcnss_filter binary from Samsung's A520FZTU4BRB1 firmware.
Configuration files for media codecs and profiles have been updated from Samsung's T580XXS5CTK1 stock firmware.
There are many (final) updates from the (unfortunately now deprecated so no longer updated) 3.18 Android common kernel, many updates from Linux 4.4, and some updates from a few of Samsung's newer kernel sources to the kernel, and also some other various changes.
A few changes have been imported to the MMC block device driver in the kernel from Samsung's M105GDXS6CUD4 kernel sources that specifically fix extremely rare kernel panics that occurred when there was an error with a MMC device (mainly with SD cards).
Some unnecessary drivers have been disabled in the kernel.
The sdfat driver in the kernel, which is used for exFAT filesystem support, has been updated to version 2.4.5.
The fix for an issue where the duration of videos that are taken is lengthened by the time spent in deep sleep/suspended that was previously used has been replaced with a better fix in the Exynos fimc-is2 driver in the kernel.
Previous releases:
Release for 20210530:
Latest updates from LineageOS.
File-based encryption has been disabled after I left it enabled by mistake after testing FBE before moving onto LineageOS 18.1.
Release for 20210523:
Latest updates from LineageOS, including the 20210505 Android security updates.
Some changes have been imported to libbt-vendor from https://github.com/LineageOS/android_hardware_qcom_bt on branch lineage-18.1-caf (same as branch lineage-17.1-caf).
The rampatch_tlv_tf_1.1.tlv firmware for Bluetooth has been updated from Samsung's stock T585XXS6CTJ7 firmware.
There are some updates from the 3.18 Android common kernel and Linux 4.4 to the kernel.
A workaround that was used to get USB tethering and Bluetooth tethering to work is no longer used, and has been replaced with a proper fix (enabling CONFIG_NETFILTER_XT_TARGET_CT in the kernel).
Release for 20210413:
Latest updates from LineageOS, including the 20210405 Android security updates.
There are some updates from the 3.18 Android common kernel and Linux 4.4 to the kernel.
Release for 20210313:
Latest updates from LineageOS, including the 20210305 Android security updates.
There are some updates from the 3.18 Android common kernel and Linux 4.4 to the kernel, many changes to the rcu, locking and btrfs code from 4.4, and a few changes from Samsung's M105GDXU6CUA1 kernel to the kernel.
The exynos part of the BSP has a few changes from Lineage's 18.1 branch for HWC and memtrack.
Release for 20210207:
Latest updates from LineageOS, including the 20210205 Android security updates.
SELinux denials that caused the torch feature to not work have been addressed.
The issue where videos that are recorded have a duration that is lengthened by the time spent in deep sleep has been worked around - It looks like Samsung did something wrong in the camera HALs for Exynos 7870 devices.
There are some more updates from the 3.18 Android common kernel and Linux 4.4 to the kernel, and a few changes from Samsung's M105GDXU6CTL3 kernel.
Release for 20210116:
Latest updates from LineageOS, including the 20210105 Android security updates.
The custom camera provider HAL has been removed, and the camera provider HAL has been binderized - this fixes camera glitches when there is motion.
Quota support has been enabled on userdata, so that storage usage statistics can be gotten more quickly.
The Widevine DRM blobs from the Pixel 3 XL's last Android 10 firmware are now used.
The MFC (Multi Format Codec) firmware has been updated from Samsung's M105FDDU3CTK3 firmware, and the camera.vendor.universal7870.so library has been updated from Samsung's latest stock firmware (version T580XXS5CTK1).
There are some more updates from Linux v4.4 and the 3.18 Android common kernel to the kernel.
Release for 20201223:
Latest updates from LineageOS.
Address hal_graphics_composer_default SELinux denials on video_device - fixes issues with video playback with SELinux set to enforcing. (Thanks to @Kostareka for providing logs with the SELinux denials)
Release for 20201221:
Latest updates from LineageOS, including the 20201205 Android security updates.
I've prepared new BSP sources, based on Lineage's SLSI BSP sources, and the BSP libraries are now built from those sources. (Thanks to @Valera1978 for providing his old BSP sources! Without them, this wouldn't have been possible.)
Samsung's proprietary audio libraries, adapted by @Valera1978, are now used, to workaround an issue where audio will be outputted to both the 3.5mm audio jack and the speakers quietly when something is connected to the audio jack.
The build fingerprint has been changed to an older Android 8.1 fingerprint for the Google Pixel C. (For information on why we can't use the fingerprint from the stock firmware, see: https://github.com/TALUAtGitHub/android_device_samsung_gtaxlwifi/issues/1 )
Installation on the LTE variant (SM-T585, codenamed gtaxllte) is now allowed - apparently, builds for the WiFi-only variant boot and work on the LTE variant, only with no mobile networking (of course) and GPS.
There are a few minor cleanups.
Version 2 of the AOSP bluetooth audio HAL has been enabled.
FIFO UI scheduling has been enabled.
The camera libraries have been updated from Samsung's latest stock firmware, version T580XXS5CTK1.
There are a few other miscellaneous improvements.
There are some updates to the kernel from the Android 3.18 common kernel and Linux v4.4, and there are updates to some of the drivers from Samsung's M105GDXU5CTI3 kernel.
Release for 20201121:
Latest updates from LineageOS, including the 20201105 Android security updates.
The sepolicy has been improved - many unnecessary SELinux rules have been removed and a few SELinux denials have been addressed.
The init.power.rc script is now actually used to set some parameters for the interactive CPU governor to make it less aggressive.
The GNSS and sensors HAL are now compiled from source in the device tree with necessary modifications. (Thanks to @followmsi for some very useful information regarding this!)
As many vendor blobs as possible have been updated from Samsung's T580XXS5CTD1 and A520FXXUGCTI9 stock firmwares, the gpsd shim has been removed as it's no longer necessary after updating gpsd from T580XXS5CTD1 and a few unused vendor blobs have also been removed.
cbd/cpboot-daemon has been removed, because it, along with the modem_v1 driver in the kernel, no longer works with the latest bootloader and spams the kernel log with error messages, I have very little idea of what it does for the WiFi-only variant and it's unnecessary.
Made a few other miscellaneous improvements.
Many more updates to the kernel from Linux v4.4 and the 3.18 Android common kernel, some miscellaneous improvements and many changes to the f2fs filesystem driver from newer Android common kernels and mainline Linux.
The kernel is now compiled using the clang compiler after having applied the many necessary changes to it to do so.
Release for 20201022:
Latest updates from LineageOS, including the 20201005 Android security updates.
Enable config_setColorTransformAccelerated - LiveDisplay colour calibration and reading mode is now available. (Thanks to @followmsi for finding this fix.)
Add FlipFlap for flip covers. (Note that FlipFlap only works if the timeouts in Settings -> Connected devices -> Connection preferences -> Smart cover are set to 'immediately')
Fix a typo in the power profile.
More updates to the kernel from Linux v4.4 and the 3.18 Android common kernel.
Apply/backport some changes to zram and the lz4 compression algorithm from mainline Linux for faster compression and decompression, and add a backport of the zstd compression algorithm from the 4.9 Android common kernel which can be used as the compression algorithm for zram (lz4 is still the default compression algorithm).
Release for 20200915:
Latest updates from LineageOS, including the 20200905 Android security updates.
Increase microphone gains.
Many more updates from Linux v4.4 and android-3.18 and a few improvements to the kernel.
Release for 20200821:
Latest updates from LineageOS.
A few more updates from Linux v4.4 and android-3.18 and improvements to the kernel.
Revert 2 changes to the kernel related to hotplugging - should fix an issue where the device doesn't wake up after a while of deep sleeping in certain cases, and a hard reset is needed.
Release for 20200814:
Latest updates from LineageOS, including the 20200805 Android security updates.
Update the Mali graphics blob to r28p0 from r22p0.
Make a few changes for GPS that fix Assisted GPS, and switch to different XTRA servers with HTTPS.
Fix OpenCL.
Symlink libGLES_mali.so to libOpenCL.so, libOpenCL.so.1 and libOpenCL.so.1.1 instead of copying - saves a significant amount of space in /system and makes the installation zip slightly smaller.
Change media volume control to be in 25 steps rather than 15 steps.
More updates from Linux v4.4 and android-3.18 to the kernel and some improvements.
Release for 20200711:
Latest updates from LineageOS.
Android security updates from 20200705, manually applied to skip the wait for them to be merged. ('repopick -t android-10.0.0_r40')
Disable window rounded corner animations.
Reduce ZRAM size to 512MB.
Enable debug.sf.disable_backpressure.
A few more updates to the kernel from Linux v4.4 and android-3.18.
Port over/import zsmalloc, zram, zswap, zbud and zpool from Linux v4.4.
Fix the issues with hanging/freezing that were present in the previous release.
Release for 20200703:
Latest updates from LineageOS.
Enable support for using USB for MIDI.
Fix/workaround issues with USB tethering.
Remove sswap and use ZRAM.
Latest update from @Valera1978 - "update audio_policy_configuration.xml from SM-A600FN q stock"
Many more updates to the kernel from v4.4, android-3.18 and a few from v3.16.
Disable the Exynos hotplug governor again. (in the kernel)
Release for 20200608:
Latest updates from LineageOS including the 20200605 Android security updates.
Use userspace lmkd.
Enable Always On Display. (Thanks to @followmsi)
Address a few more SELinux denials.
power_profile: change names as per pie naming changes.
Switch to [email protected]g. (Thanks to @followmsi)
Fix freeform window moving/resizing doesn't work (In my new fork of LineageOS' android_frameworks_base repository).
Add back support for Miracast using the changes from https://review.lineageos.org/q/topic:%22ten-aosp-wfd%22 (In my new fork of LineageOS' android_frameworks_av repository).
More updates to the kernel, including many updates from Linux v4.4 and v3.16 and general updates. There are also improvements to downstream drivers.
Release for 20200512:
Latest updates from LineageOS including the 20200505 Android security updates.
Address more SELinux denials.
Remove the ro.enable_boot_charger_mode property and revert "gtaxl: workaround for offline charging".
Remove some useless services for non-existent binaries in init files.
Hide sRGB toggle in developer options.
More updates to the kernel, including many updates from Linux 4.4 and to the kernel-based wireguard implementation.
Release for 20200411:
Latest updates from LineageOS including the 20200405 Android security updates.
Update the cpu.speeds array in the power profile for 1.69GHz, 449MHz and 343MHz frequencies.
Make the power profile aware of the big.LITTLE cluster.
Address more SELinux denials and remove duplicate rules.
Use an up-to-date Samsung hardware repository based on LineageOS' repository, and make changes to the device tree for it. ((Thanks to @followmsi for changing the sepolicy to accommodate for modem/macloader having been moved to /vendor and mentioning that the Exynos hidl power HAL has to be used after the old power HAL was removed)
Enable secure ADB and set persist.sys.usb.config to none.
Use pool.ntp.org for the NTP servers.
ramdisk: cleanup the init files and fstab for readability.
ramdisk: init.samsungexynos7870.rc: only start gpsd after booting - fixes GPS when encrypted.
More updates to the kernel, including many updates from Linux 4.4, general updates (such as updates to the wireguard kernel module) and fixes.
Use sdfat for exFAT support.
Add toggle for disabling newly added USB devices.
Release for 20200309:
Latest updates including 20200305 security patches
Upgrade android.hardware.keymaster to 4.0.
lineage-gtaxlwifi_defconfig: disable CRYPTO_FIPS to get encryption partially working.
sdfat: update to version 2.3.0.
Update the BFQ IO scheduler to v8r12 using a port.
Release for 20200303:
wireless: add back Samsung's 'temporary' workaround due to qcacld-2.0 page allocation errors. Looks like this is actually necessary. Works around issues with WiFi not being possible to be enabled after some time again due to page allocation failures that still exist.
Revert duplicate "signal/ptrace: Don't leak unitialized kernel memory with PTRACE_PEEK_SIGINFO". We already had this commit as in Linux v3.18, the content of this reverted commit are useless.
Release for 20200301:
Fix a few SELinux denials. (including app_zygote denials, sepolicy in post 5 no longer needed for this build at all and also shouldn't be used anymore as more denials beyond just the app_zygote denials have been fixed)
Release for 20200229:
Initial release.
Known issues and workarounds (if any):
Issue 1: adoptable storage is reported to not work correctly.
Somewhat of a workaround to issue 1: format and use your micro SD card with the exFAT filesystem.
Issue 2: Camera previews for images to be taken at resolutions with aspect ratios other than 16:9 using the rear camera are squashed from 16:9 (while final saved images at any resolution are unaffected by any squashing), and videos taken at some resolutions are affected by similar issues with squashing in previews, and, in a smaller set of resolutions, also in final saved video files. (Note that these issues don't affect the front-facing camera)
Somewhat of a workaround to issue 2: Use resolutions at which there are no issues with squashing from 16:9.
Issue 3: the on-screen navigation bar feature that can be enabled with the option at Settings -> System -> Buttons -> "Enable on-screen nav bar" doesn't work properly.
To report issues, get a log from logcat and dmesg. If you are unsure of how to get both, there is good documentation out there for how to do so.
Sources:
A manifest containing all of the necessary repositories to make a build is in this repository on branch lineage-17.1: https://github.com/TALUAtGitHub/gtaxlwifi-manifests
Thanks to:
@Valera1978 - for all of the previous work for these devices, and for providing his old BSP sources without which the previously used open BSP sources wouldn't have been possible.
@followmsi - for fixes to various issues and other improvements, for useful information, and for working with me on much of this stuff.
LineageOS - for the Android distribution itself.
...and everyone else who's worked on anything that is in use.
No build for sm-t585?
Echo_2000 said:
No build for sm-t585?
Click to expand...
Click to collapse
Unfortunately not, as I mentioned in the original post.
Sorry.
Edit on 2020/12/22: for anyone who is reading this post and has missed my new note in the original post, installation is now allowed on the LTE variant in my latest build, so you can try my build on it.
TALUAtXDA said:
Unfortunately not. As I mentioned in the original post:
Sorry.
Click to expand...
Click to collapse
Too bad, bad no problem.
I installed this, mostly seemed to work OK, but although I could install Chrome from Play Store it would simply disappear (no error) every time I opened it. Tried Chrome Beta instead and same issue.
I don't know if Gapps related. I used Bit gapps for what it's worth.
Gone back to old build.
Thanks anyway.
Glenn2 said:
I installed this, mostly seemed to work OK, but although I could install Chrome from Play Store it would simply disappear (no error) every time I opened it. Tried Chrome Beta instead and same issue.
I don't know if Gapps related. I used Bit gapps for what it's worth.
Gone back to old build.
Thanks anyway.
Click to expand...
Click to collapse
Hi,
The issue was caused by SELinux denials. I've fixed these denials in this commit: https://github.com/TALUAtGitHub/and...mmit/0ec43a448795230a3d2d8576cd93c5b156468e21
I was able to get the SELinux denials you were experiencing as you told me how you encountered them. Attached is a zip archive named 'sepolicy_and_precompiled_sepolicy.zip' containing 2 files: 'sepolicy' and 'precompiled_sepolicy'. This is a new sepolicy containing the rules to fix the denials. If you decide to use my builds again, extract the zip archive and copy the 'sepolicy' file to /system/ and 'precompiled_sepolicy' file to /system/system/vendor/etc/selinux/ in TWRP with system mounted. You may want to run SELinux as permissive for now, though keep in mind that this will ignore denials. To set SELinux to permissive, run:
Code:
setenforce 0
I never caught these denials as I don't use Chrome, and use Bromite web browser which doesn't seem to trigger these denials. I'll probably upload a new build tomorrow containing a sepolicy with the new rules. Also, I've put this in the original post for reporting SELinux denials:
TALUAtXDA said:
There maybe more issues due to SELinux denials. If something doesn't work, test it with SELinux set to permissive:
Code:
setenforce 0
If the issue is no longer reproducible, it's due to SELinux denials. Get logs by running:
Code:
dmesg | grep "avc: denied" > dmesg_selinux_denials
logcat | grep "avc: denied" > logcat_selinux_denials
while SELinux is permissive after doing whatever triggered the denials in a shell and upload the files 'dmesg_selinux_denials' and 'logcat_selinux_denials'. It would also be preferable to report what triggered the denials. In some rare cases, SELinux has to be set to enforcing to get certain denials, which would unfortunately mean that every denied action isn't logged and it takes multiple tries to get every denied action causing issues. Don't report any random denials that don't cause any issues. I won't fix some denials (such as proc_version denials, which should be denied and it causes no real issues) and I'll only fix denials that cause unintended issues.
Click to expand...
Click to collapse
Thanks I will try it again soon.
Did as suggested, seems ok now! Thanks.
Good evening,
God bless you and thank you very much for fixing this beautiful rom.
I have a request and a question.
Request: I am using sm-t580. When I was using stock rom, I was able to cast my screen to my Samsung TV. I am aware that LOS and Pixel have removed this ability. Would you consider please to re-enable "smart cast". I would love to enjoy your ROM on my sm-t580 and be able to cast to Samsung TV.
Question: I am unable to edit build.prop or other system files. I tried to re-mount root but probably doing something wrong. Not very good with this. Could you walk me through how to remount and what do I need to use (what terminal inside your rom). I have root access with Magisk and in twrp used shell terminal with your command "mount -o rw,remount /" without success. Then I downloaded some some terminal app and tried. No use... I get "/dev/block/platform/13540000.dmmmc0/by-name/system" not user moutable in fstab. Thank you.
Thanks for building a rom with selinux enforced. I used encryption on 14.1 but it doesn't seem to work here. Some more denials to add, or maybe I need a newer recovery to format data with first?
Jet T said:
Good evening,
God bless you and thank you very much for fixing this beautiful rom.
I have a request and a question.
Request: I am using sm-t580. When I was using stock rom, I was able to cast my screen to my Samsung TV. I am aware that LOS and Pixel have removed this ability. Would you consider please to re-enable "smart cast". I would love to enjoy your ROM on my sm-t580 and be able to cast to Samsung TV.
Question: I am unable to edit build.prop or other system files. I tried to re-mount root but probably doing something wrong. Not very good with this. Could you walk me through how to remount and what do I need to use (what terminal inside your rom). I have root access with Magisk and in twrp used shell terminal with your command "mount -o rw,remount /" without success. Then I downloaded some some terminal app and tried. No use... I get "/dev/block/platform/13540000.dmmmc0/by-name/system" not user moutable in fstab. Thank you.
Click to expand...
Click to collapse
Hi,
You're welcome, though kudos to followmsi of course.
Smart cast seems to be a Samsung specific, proprietary feature. But we do have the generic casting feature available in Settings -> Connected devices -> Connection preferences -> Cast. Casting to wireless displays can be enabled through the 3 dot menu and then the "Enable wireless display" option and your TV should be detected. However, this doesn't work. A TV either doesn't connect or there's a soft reboot. I also have a Samsung smart TV with which I could test it with. The TV gets detected as "[TV] Samsung", and selecting it makes it say that it's connecting but it either stops trying to connect or it soft reboots and the TV displays an "loading" message that's infinite.
I found this while searching for "MediaPlayerService: listenForRemoteDisplay is no longer supported!" (this seems to be the main error): https://pastebin.com/s4utSi6c It seems like this issue has been reported before and existed at least a few months (though most certainly more) before my builds. I'll try finding a way to fix this, but my knowledge is unfortunately quite limited at this moment.
To do a mount command like that, you need to be root. To get a root shell, run "su", grant your terminal app root access and then run any commands needed to be run as root in that shell, such as that mount command.
EDIT: found this: https://forum.xda-developers.com/galaxy-tab-a/development/rom-t4006261/post81782081#post81782081 The replies say that you need to go back to Android 8 to use Miracast. I'm not sure if that's true but that's apparently how it is. There's probably nothing that can be done. Since smart cast is proprietary and Samsung specific, you'd only find it in Samsung ROMs. Also found this: https://forum.xda-developers.com/showpost.php?p=81369313&postcount=143 saying that support for Miracast is no longer available in Android 9 and 10.
I had another device where encryption didn't work. Turned out to be twrp writing incorrect (encryption?) footer when formatting data partition. But here encryption on 14.1 worked. Maybe encryption changed 14.1 to 17.1 with different footer, or maybe encryption on the los 17.1 base is broken on all devices. Difficult.
TALUAtXDA said:
Hi,
You're welcome, though kudos to followmsi of course.
Smart cast seems to be a Samsung specific, proprietary feature. But we do have the generic casting feature available in Settings -> Connected devices -> Connection preferences -> Cast. Casting to wireless displays can be enabled through the 3 dot menu and then the "Enable wireless display" option and your TV should be detected. However, this doesn't work. A TV either doesn't connect or there's a soft reboot. I also have a Samsung smart TV with which I could test it with. The TV gets detected as "[TV] Samsung", and selecting it makes it say that it's connecting but it either stops trying to connect or it soft reboots and the TV displays an "loading" message that's infinite. I captured a logcat at a time when it soft rebooted:
I found this while searching for "MediaPlayerService: listenForRemoteDisplay is no longer supported!" (this seems to be the main error): https://pastebin.com/s4utSi6c It seems like this issue has been reported before and existed at least a few months (though most certainly more) before my builds. I'll try finding a way to fix this, but my knowledge is unfortunately quite limited at this moment.
To do a mount command like that, you need to be root. To get a root shell, run "su", grant your terminal app root access and then run any commands needed to be run as root in that shell, such as that mount command.
EDIT: found this: https://forum.xda-developers.com/galaxy-tab-a/development/rom-t4006261/post81782081#post81782081 The replies say that you need to go back to Android 8 to use Miracast. I'm not sure if that's true but that's apparently how it is. There's probably nothing that can be done. Since smart cast is proprietary and Samsung specific, you'd only find it in Samsung ROMs. Also found this: https://forum.xda-developers.com/showpost.php?p=81369313&postcount=143 saying that support for Miracast is no longer available in Android 9 and 10.
Click to expand...
Click to collapse
I appreciate your answer!
I have now installed EX Kernel Manager as I had previously purchased it anyway when I (briefly) used the ElementalX kernel on my Pixel 3a.
I can see that we lose half the CPU permanently after the device goes to sleep, as you described, by looking at the dashboard.
Under Tools/User Settings I added a setting for /sys/devices/system/cpu/cpuhotplug/enable with a value of 0 as you suggested (to apply on boot) and this has cured the issue. It explains why I sometimes had smooth and sometimes not so smooth performance on the old rom! Now it's just always smooth.
Interestingly, I could not write to this value once the problem had occurred and the CPU was half disabled. The '0' value would not save, it stayed at '1'. It was not writable - is that a clue to the cause? I had to reboot and put the setting in EXKM before the device had been to sleep. Now it is fine even after reboot.
Thanks.
Thanks for your work and contributions to this device.
Many thanks for your work. Your ROM is working perfectly. No screen freeze.
Thank you for the rom!
I flashed it because it should have signature spoofing, but actually microG self-check doesn't tick signature spoofing permission and correct signature for play services and play store. Can anyone help me?
Jamess27 said:
Thank you for the rom!
I flashed it because it should have signature spoofing, but actually microG self-check doesn't tick signature spoofing permission and correct signature for play services and play store. Can anyone help me?
Click to expand...
Click to collapse
Hi,
It should be possible to select the "System grants signature spoofing permission" option in the MicroG self-check menu to get a dialog asking if you'd like to allow signature spoofing. Otherwise, you can grant the signature spoofing permission using a root shell or ADB with these pm commands:
Code:
pm grant com.google.android.gms android.permission.FAKE_PACKAGE_SIGNATURE
pm grant com.android.vending android.permission.FAKE_PACKAGE_SIGNATURE
TALUAtXDA said:
Hi,
It should be possible to select the "System grants signature spoofing permission" option in the MicroG self-check menu to get a dialog asking if you'd like to allow signature spoofing. Otherwise, you can grant the signature spoofing permission using a root shell or ADB with these pm commands:
Code:
pm grant com.google.android.gms android.permission.FAKE_PACKAGE_SIGNATURE
pm grant com.android.vending android.permission.FAKE_PACKAGE_SIGNATURE
Click to expand...
Click to collapse
Thanks for the fast response! I got the permission with the dialog in MicroG, but apps still don't find google play services
Jamess27 said:
Thanks for the fast response! I got the permission with the dialog in MicroG, but apps still don't find google play services
Click to expand...
Click to collapse
You're welcome. Now, the signature spoofing permission is granted to microG, but from what you describe, it's likely that play store (or fake store) doesn't have the signature spoofing permission. You can check if this is the case by opening the MicroG self-check menu and checking if the "Play Store (Phonesky) has correct signature" item is checked. If play store doesn't have the signature spoofing permission granted, you need to run this one pm command in a root shell or using ADB:
Code:
pm grant com.android.vending android.permission.FAKE_PACKAGE_SIGNATURE
LineageOS 20.0 64-bit for Samsung Galaxy Tab A 10.5 (2018) WiFi
Your warranty is now void. I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Click to expand...
Click to collapse
By using this ROM, you acknowledge that you understand what running work-in-progress software means. You might lose all your data stored on the device due to a bug, the device might freeze / crash at any time, nothing is guaranteed; you are basically a beta tester. Also, this is my personal project which I decided to share here, I'm not a developer but an average user like you. Most likely I can't and will not solve your issues with VoLTE not working, Angry Birds crashing, etc.
Installation:
-----
Notes for SM-T595 users
The ROM has been modified to work on the LTE variant too, with the same level of functionality as the WiFi-only variant. This means that the LTE modem will not be usable in this ROM, and the device will appear as SM-T590 everywhere.
Also, SM-T595 has lots of hardware versions with different partition sizes, so there is a possibility that the installer will fail with one of the following error messages: E1001: Failed to update system image / E2001: Failed to update vendor image.
In case it fails, I will need the output of the following commands to make the installer compatible with that specific version too:
adb shell blockdev --getsize64 /dev/block/by-name/system
adb shell blockdev --getsize64 /dev/block/by-name/vendor
-----
- Reboot the tablet in download mode
- Flash TWRP in the AP slot using Odin
- Right after Odin finished flashing, hold Volume Up while the tablet is rebooting to get into TWRP
- Skip the warning by swiping to allow modifications
- Wipe -> Format Data -> type yes and confirm
- Reboot -> Recovery
- Skip the warning again
- On your PC, open a command prompt and copy LineageOS to the device using adb push lineage-20.0-20230514-UNOFFICIAL-gta2xlwifi.zip /sdcard/
- Alternatively, you can use a Micro SD card or USB OTG, MTP isn't recommended- In TWRP, select Install -> lineage-20.0-20230514-UNOFFICIAL-gta2xlwifi.zip and swipe to confirm
- Optionally, you can install Magisk now, make sure to use the latest version from GitHub
- Optionally, you can install GApps now but Aurora Store with MicroG is a better alternative, they use way less RAM than Play Services
Downloads:
LineageOS 20.0:
https://github.com/UDPSendToFailed/OTA/releases
TWRP 3.7.0:
https://github.com/UDPSendToFailed/twrp_device_samsung_gta2xlwifi/releases
Changelog:
2023. 05. 14.
Edit: Not recommended to download. This build has issues with WiFi after reboot because of the in-kernel WLAN driver change which I did as an attempt to fix the randomly occurring kernel panics. As it turned out, the WLAN kernel driver has nothing to do with the random reboots, so I will revert to the previous configuration in the next build.
- Switched to in-kernel WLAN driver
- Synced with the latest LineageOS sources (https://review.lineageos.org/q/branch:lineage-20.0+status:merged+after:2023-04-17+before:2023-05-14)
- May security patch
Spoiler: More changelogs...
2023. 04. 17.
- Synced with the latest LineageOS sources (https://review.lineageos.org/q/branch:lineage-20.0+status:merged+after:2023-04-05+before:2023-04-17)
- April security patch
2023. 04. 05.
- Synced with the latest LineageOS sources (https://review.lineageos.org/q/branch:lineage-20.0+status:merged+after:2023-02-27+before:2023-04-05)
- Switched to LineageOS-UL for frameworks_av and frameworks_base
- March security patch
2023. 02. 27.
- Synced with the latest LineageOS sources (https://review.lineageos.org/q/branch:lineage-20.0+status:merged+after:2023-01-24+before:2023-02-27)
- February security patch
2023. 01. 24.
- Synced with the latest LineageOS sources (https://review.lineageos.org/q/branch:lineage-20.0+status:merged+after:2022-12-28+before:2023-01-24)
- January security patch
2022. 12. 29.
- Synced with the latest LineageOS sources
- December security patch
2022. 11. 15.
- Synced with the latest LineageOS sources
- November security patch
2022. 10. 05.
-----
!TWRP update and data wipe is required to enable FBE!
Steps to update from previous versions:
- Download TWRP 3.7.0
- Update TWRP using Odin
- Boot into TWRP -> Wipe -> Format Data -> type yes and confirm
- Reboot -> Recovery
- Flash the latest ROM zip (20221005)
-----
- Enabled FBE (File-Based Encryption)
- Fixed some Bluetooth-related issues
- New camera app with video recording support
- Synced with the latest LineageOS sources, most of the features from 19.1 have been merged
- October security patch
- TWRP: Updated to the latest 12.1 branch
- TWRP: FBE decryption support
2022. 09. 30.
-----
LineageOS 19.1 (Android 12L) builds are now discontinued as it would be complicated to keep testing an older version, and I don't have a build server to store and update the source code either. Personal builds can still be done by anyone who wants to keep using 19.1, all the required sources are available on my GitHub.
-----
- Added Signature Spoofing support, LSPosed and FakeGApps aren't required anymore for MicroG
- Added Natural and Boosted display color profiles
- Extended Night Light color temperature range
- UI and color flickering has been fixed
- The Restrict USB option under Settings -> Privacy -> Trust is now working properly
2022. 09. 16.
- Significantly improved multitasking performance with proper ZRAM setup
(Random reboots might still happen, please report them with a description of what caused the crash and /proc/last_kmsg & logcat output attached)
- Added KTweak script (more info here and here)
- Added Dolby Settings
- Added Memory Usage stats to App Info in Settings
- Added audioloader
(Experimental quad speaker mode, can be enabled with running audioloader in Terminal Emulator or adb shell. To revert the temporarily set parameter, restart the tablet. Ideas on how to fix the sound quality are welcome)
- Fixed Network Speed indicator and Data Usage stats
- Disabled ALAC codec support as it had a critical CVE vulnerability
- Reverted to SkiaGL renderer as SkiaVK had issues with WebView v104+
- Removed some LTE-only features
- September security patch
2022. 08. 14.
- Added System Navigation options under Settings -> System -> Gestures
- Added theme color customization under Settings -> Wallpaper & Style
- Merged changes from various msm8953-based device trees
- August security patch
2022. 07. 12.
- Added CRT screen off animation
- Added tinymix (in case anyone wants to experiment with fixing the quad speakers)
- Added hidden and protected apps feature to the launcher
- Added pure black theme option
- Light theme changes
- Removed Audible app (Samsung bloatware from the odm partition)
- July security patch
2022. 06. 12.
- Headphone jack fixed
- Microphones fixed
- Double Tap to Wake should work reliably now
- Switched to Vulkan renderer to improve the smoothness of the UI
- June security patch
2022. 05. 29.
- MTP fixed
- Widevine DRM fixed
- Removed the "internal problem" warning on boot
- TWRP updated to 3.6.2
2022. 05. 25.
After a long time without updates, a new, non-GSI version is here!
- Freezes and crashes have been eliminated
- Keystore is fixed so you can use a screen lock
- This update will give your device an extra 106MB of RAM (by freeing up the memory that was allocated for the non-existent modem)
- MSM hotplug is enabled by default to improve the battery life by dynamically powering down cores based on CPU load
- May security patch
2022. 04. 08.
- Device type changed to tablet
- April security patch
Known issues:
- WiFi hotspot crashes
- Bluetooth audio
- 2 of 4 speakers are working
- GPS
- Freezes / crashes with some SD cards, in case the ROM installation fails with black screen or the setup process keeps freezing, try removing the SD card
- SELinux permissive
32-bit vs 64-bit mode performance comparison:
https://browser.geekbench.com/v5/cpu/compare/15116230?baseline=14600296
Thanks to:
lsswizard for the 64-bit kernel, this all wouldn't be possible without his work
lsswizard for the TWRP tree
@quent1du58 for the commits to the device tree
LineageOS team for the base ROM
LineageOS-UL team for keeping the camera HALv1 patches alive
Sources:
Kernel: 3.18.140
64-bit vendor libraries from Galaxy A20s firmware (A207FXXU2BUD4)
https://github.com/UDPSendToFailed/
https://github.com/LineageOS
https://github.com/LineageOS-UL
https://github.com/TeamWin/android_bootable_recovery
looking forward to see flashable zip for deleting keystore.mdfpp.so and keystore.msm8953.so from /vendor/lib/hw
aIecxs said:
looking forward to see flashable zip for deleting keystore.mdfpp.so and keystore.msm8953.so from /vendor/lib/hw
Click to expand...
Click to collapse
They are already removed from the provided vendor.img but sadly that didn't fix the problem, I will look for a solution.
{
"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"
}
Many thanks for all your work. My SM-T590 is running on it for almost a day now (with MicroG and Magisk). Installation was not straightforward (I've had to factory reset after flashing LineageOS since the setup process kept freezing), but definitely easier than with the other GSI images. Not really sure if it is also related to the 32 vs 64 bits kernel, but the tablet definitely feels snappier than with BloatUI OneUI.
I've found only three problems so far:
The tablet does indeed randomly freeze from time to time. It does seems related to Magisk, but definitely not a huge deal since it rarely happens. I'll try to pinpoint the problem with a logcat if I have some time.
Only half of the speakers are working (but still not a deal breaker).
My book cover does not wakes up or put the tablet into sleep. It seems that one of the sensors is not working properly.
quent1du58 said:
Many thanks for all your work. My SM-T590 is running on it for almost a day now (with MicroG and Magisk). Installation was not straightforward (I've had to factory reset after flashing LineageOS since the setup process kept freezing), but definitely easier than with the other GSI images. Not really sure if it is also related to the 32 vs 64 bits kernel, but the tablet definitely feels snappier than with BloatUI OneUI.
I've found only three problems so far:
The tablet does indeed randomly freeze from time to time. It does seems related to Magisk, but definitely not a huge deal since it rarely happens. I'll try to pinpoint the problem with a logcat if I have some time.
Only half of the speakers are working (but still not a deal breaker).
My book cover does not wakes up or put the tablet into sleep. It seems that one of the sensors is not working properly.
Click to expand...
Click to collapse
Thanks for the feedback!
I'm working on a non-GSI variant since I couldn't fix the keystore errors and other issues on GSI.
However I have no previous experience on Android builds, and our device has no custom ROMs or device trees to begin with, so it might take a long time to fix everything. Also the 3.18 kernel is really old for Android 12.
Currently basic functionality like WiFi, Bluetooth, OpenGL, sensors, and lock screen are working, but there is still a lot more left like DRM, cameras, audio, GPS, etc.
As for your 3rd issue, I would suggest enabling double tap to wake in Phh Treble Settings.
That's some great news. I've also tried to port LineageOS to this device (mostly as a way to learn new things, since Android/LineageOS/kernel aren't really my areas of expertise) using both Rupansh and heavily customised Xiaomi Redmi 5 (Rosy) sources trees without any success.
Have you managed to boot a non GSI build? I've tried to compile LineageOS 19 Using your device and kernel trees, plus Rupansh vendor tree. Build went fine, I've even managed to flash and to boot into recovery (which needs fstab fixes), but no way to boot a freshly flashed zip for now. I'm going to continue my research and will share any progress.
quent1du58 said:
Have you managed to boot a non GSI build? I've tried to compile LineageOS 19 Using your device and kernel trees, plus Rupansh vendor tree.
Click to expand...
Click to collapse
Yes, currently my tablet runs a build based on my device tree on GitHub but it's highly experimental. Basically I use GitHub only to have some revisions of the device tree for backup and testing purposes, that's why all the commits are named asd.
I guess your issue will be that you use vendor files from Rupansh (since that's missing 64-bit stuff from Galaxy A20s vendor), here I have uploaded the ones I'm using: https://mega.nz/folder/zXZzVZaL#95t8V7DSr0rX7W0lTZmhHQ
Copy them to a folder named ~/system_dump for example, create a subfolder named system and another subfolder named vendor under the previously created system folder. Then you can use the commands below to extract the required proprietary files from system.img and vendor.img. Assuming you have everything in ~/system_dump folder:
sudo mount -o loop,rw system.img system
sudo mount -o loop,rw vendor.img system/vendor
Then go to your downloaded LineageOS source/devices/samsung/gta2xlwifi and run:
chmod +x extract-files.sh
chmod +x setup-makefiles.sh
bash extract-files.sh ~/system_dump/
Also you will need to apply some patches to the LineageOS 19.1 source to bypass eBPF requirement which is not available on our 3.18 kernel. Download Treble patches from here: https://github.com/phhusson/treble_...ases/download/v413/patches-for-developers.zip
Apply patches/platform_system_bpf/0001-Support-no-bpf-usecase.patch to system/bpf and patches/platform_system_netd/0001-Support-no-bpf-usecase.patch to system/netd in the source using git apply /path/to/.patch. You can also apply the Camera2 API patches mentioned in the first post but the camera doesn't work anyway currently.
The resulting build is barely usable, working stuff are mentioned in my previous comment. Feel free to try different versions in device.mk and add / remove stuff in proprietary-files.txt, I guess I messed up lots of things since I never built a device tree before.
Thank you for all those details, I've managed to build a working image. I still experience the same problems so far:
UI crashes a lot shortly after rebooting
Inserting a SD card freezes the system
But since I now have a way to build my own releases, I'll try to fix things. Since I've forked your repositories on Github, I'll send you pull requests when needed.
Glad you managed to get it work!
Yep, the UI hangs and crashes are happening here too, haven't found the cause yet. Logcat shows a blocked state and dumps tons of lines from the kernel. The interesting part is that sometimes, like in 2 of 10 reboots it starts up correctly without any freezes.
If I have some time I will continue fixing the tree as there are lots of randomly added and unfinished stuff which I did for testing purposes.
I tried to flash twrp in the download mode but it showed "only official binaries are allowed to be flashed". What's wrong?
seeiu said:
I tried to flash twrp in the download mode but it showed "only official binaries are allowed to be flashed". What's wrong?
Click to expand...
Click to collapse
You need to flash TWRP using a patched version of odin.
Thanks for the great tutorial. The Rom runs so far quite well.
But when I want to flash microG_Installer_Revived with TWRP I get a 235 error.
When I connect the tab to the PC, the internal memory and SD card is not shown to me on the PC.
Although, the tab is recognized by the PC.
Is there a trick or do I have to live with it.
DerSammler said:
But when I want to flash microG_Installer_Revived with TWRP I get a 235 error.
Click to expand...
Click to collapse
I just updated the first post with some instructions about MicroG. Basically you will have to flash it as a Magisk module, also use FakeGApps to have Signature Spoofing support.
DerSammler said:
When I connect the tab to the PC, the internal memory and SD card is not shown to me on the PC.
Click to expand...
Click to collapse
Yea, that's a known issue with both GSI and non-GSI variants, it'll be fixed as I find the cause. Alternatively you can use adb or some wireless file transfer app like AirDroid.
What do I do if I want to go back to stock Rom?
Can I simply flash with Odin original Android 10? Or is there anything else I need to consider.
Thank you very much.
DerSammler said:
Can I simply flash with Odin original Android 10?
Click to expand...
Click to collapse
Exactly, it's enough to flash the latest stock ROM with Odin to revert the changes.
I have installed lineage-19.1-20220525-UNOFFICIAL-gta2xlwifi according to the new instructions
unfortunately, when I start the tab, I get a red message—kernel is not seandroid enforcing -.
Afterwards, when the tab is started, I also get the following message on the home screen
Android System
There is an internal problem with your device. Please contact the manufacturer regarding this.
Are these two messages normal? Or am I doing something wrong. I have now installed LOS_19.1_64 again. Thank you very much.
DerSammler said:
Are these two messages normal?
Click to expand...
Click to collapse
Yes, these messages are completely normal in the ROM's current state and can be ignored, they won't cause any further issues.
The kernel message is related to the SELinux permissive state which is listed under known issues, the other one shows up simply because I haven't patched the LineageOS source code to hide it.
Disable AVB check · phhusson/[email protected]
This avoids the message "There's an internal problem with your device. Contact your manufacturer for details." on some AVB 1.0 devices. Change-Id: Ia54b857a3e98e2639d6bcc0ba713809704...
github.com
Thanks a lot for your help.
I find the Rom really great, super work you do. The system is really faster.
To transfer data I have MyPhoneExplorer and that works very well with it.
I'm curious what there will be updates for this Rom.
Wish you a quiet Sunday.
Greetings: Dirk
DerSammler said:
I find the Rom really great, super work you do. The system is really faster.
Click to expand...
Click to collapse
Thanks for the feedback!
DerSammler said:
I'm curious what there will be updates for this Rom.
Click to expand...
Click to collapse
Yea, I'll try to improve things but as I stated in my previous posts, I'm just an average user with no Android porting experience, so it might take a while. I'll post new releases with monthly security updates from Google and maybe some fixes.
Also please note that the ROM isn't secure yet, the lock screen can be easily bypassed with TWRP since encryption isn't enforced, and adb with root access is enabled by default for debugging purposes.
I have a question about the GSI Roms?
Which roms can I flash on the Galaxy Tab A (T-590).
The roms must be Binder compatible, I know that.
Can I only flash Binder a64, or can I also use the Binder arm 64 Rom?
Thank you very much.