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
Related
In this thread I'll share with you my personal builds of LineageOS 18.1 for the Oneplus One codename: bacon (older builds of 17.1, 16 and 15.1 are still downloadable). This project is inspired by idprophecy's LineageOS builds, to which I want to add my favorite features and, possibly, even more optimizations and improvements.
MAIN FEATURES
LineageOS 18.1 features:
support for MicroG (signature spoofing) - read the 2nd post!
improved & updated libraries: sqlite, zlib, libpng, jemalloc, libvpx, libyuv, freetype
critical system components built with -O3 optimizations (art, SurfaceFlinger, bionic) and ThinLTO
built with Clang 12.0.x
optimized & updated bionic routines
Android RunTime (ART) updates and improvements
several debugging & tracing components are removed from the system
reduced priority of the USB connection type & USB debugging notifications
partial/full screenshot QS tile
Ambient display gestures
deGoogling tweaks (Kuketz/GrapheneOS captive portal URLs, Mulch WebView from DivestOS, pool.ntp.org NTP server, GrapheneOS SUPL server)
in-built F-Droid Privileged Extension
materialized Toasts
support for OTA updates
several minor tweaks and improvements
my custom kernel (features listed below)
Spoiler: Old info about 17.1
LineageOS 17.1 features - development stopped:
all C/C++ components are build with -O3/-g0 flags (maximum optimization, minimum useless debug info)
support for signature spoofing (= MicroG supported) - read the 2nd post!
in-built F-Droid Privileged Extension
native support for WakeBlock by @GioBozza, for more info: WakeBlock on XDA
several updates & improvements to internal components: skia & libjpeg-turbo (temporarily reverted), art, bionic, libpng, sqlite, zlib
several debugging & tracing instructions are removed from the system
custom Screenshot QS tile
deGoogling tweaks: non-Google captive portal server & SUPL server
support for OTA updates
minor miscellaneous tweaks
my custom kernel (features listed below)
Kernel features:
built with GCC 13
CPU underclocking (268 MHz) & max freq. limited to 1,9 GHz by default
several f2fs updates
power-efficient workqueues
cpu_input_boost by Sultanxda
bricked hotplug replaces mpdecision
CPU undervolting
maple I/O scheduler
updated zram and zsmalloc drivers
userspace LMKD replaces the old in-kernel Low Memory Killer driver
DDR bandwidth boost on screen wake
minor adjustments and tweaks
several code updates and security/bug fixes
BUGS
Also present in official LineageOS 18.1/17.1:
kernel panic when changing USB mode to "File transfer" - fixed in the 20200811 build & later official nightlies
notification/charging LED not working - fixed in the 20200811 build & later official nightlies
low in-call microphone if speakerphone is enabled - fixed in the 20200811 build
charging hiccups when using certain 3rd-party chargers/cables - fixed in the 20200912 build
AUX audio output not working - fixed in all builds (unofficial & official) newer than 20200826
wrong time on boot until connected to a network - fixed in the 20201110 build, and in official nightlies starting from 20201224
the Music app is quite messed up (bug is already reported on Gitlab) - fixed by the LineageOS team as of January 2021.
flaky GPS - fixed (or at least improved) in the 20201213 build & official 18.1 nightlies newer than 20210415
manual mobile network scan not working - fixed in the 17.1 20210123 build, also fixed on official LineageOS
NFC not working - fixed in the 20210419 build & later official nightlies
5 GHz hotspot is broken - but there's a workaround here
front camera often affected by overexposure - workaround: restart the app you're using until it's gone
low microphone volume during calls on speakerphone - completely fixed in 20220805 and in official nightlies starting from 20220804
stuttery playback of HD videos in some 3rd-party apps - fixed in the 20211106 build
weird noises while playing flac files if AudioFX's Bass option is enabled (17.1)
high framerate video recording is broken - workaround present in my builds, a proper fix will follow in official ones too some day (as soon as I figure it out)
Bugs that are specific to my builds:
encryption of f2fs-formatted /data partition is broken - fixed in the 20201028 build
corrupted thumbnails and weird visual artifacts in the system's color picker - fixed in the 20201028 build
libjpeg crashes in certain apps (NewPipe, Files, and others) - fixed in the 20201017 build
Telegram's (and, possibly, other apps') in-built camera not working - apparently fixed in the 20200811 build
WiFi issues affecting a minority of users - under investigation
encryption doesn't work - fixed in the 2022-01-13 build
some apps crashing due to permission quirks - fixed partially in the 2022-02-13 build, completely fixed in 2022-03-02
Changelog for LineageOS 18.1:
June 11th:
synced with LineageOS + June's security patches
improvements for the dark theme in Messages and Dialer
Changelog for older LineageOS 18.1 builds:
Spoiler: Changelogs for previous 18.1 builds
May 11th:
synced with LineageOS (incl. May's security patches)
workaround for Snap not being able to record high-framerate videos
disabled zram to check stability
April 15th:
synced with LineageOS + April's security patches
security improvements from ProtonAOSP (many Quick Settings tiles cannot be toggled if the screen is locked)
March 17th:
synced with LineageOS + March's security patches
updated Mulch WebView
updated some drawables (small system icons) from crDroid
improved GPS performance (still WIP, let me know your impressions)
more deGoogling: switched to pool.ntp.org as the NTP server and to GrapheneOS's SUPL server
February 16th:
synced with LineageOS + February's security patches
Mulch WebView replaces Chromium
connectivity checking endpoints changed to privacy-friendly, non-Google alternatives
kernel WiFi driver updates reverted
January 5th, 2023:
synced with LineageOS + January's security patches
WiFi driver updates in the kernel
December 10th - last 2022 build:
synced with LineageOS + December's patches
zram enabled (disksize = 1,5 GiB)
November 8th:
synced with LineageOS + November's security patches
Android Go changes reverted, since they cause issues
October 13th:
synced with LineageOS (incl. October's security patches)
kernel memory routines optimized for Cortex A15 CPUs
September 8th:
September's security patches
some configurations taken from Android Go, to reduce RAM usage but without sacrificing functionality
August 5th:
synced with LineageOS + August's security patches
all microphone/speakerphone issues are fixed also for 3rd party apps
July 23rd:
fixed low volume during calls in speakerphone mode
July 8th:
synced with LineageOS + July's security patches
security fixes in the kernel
kernel logging disabled by default, to reduce overhead
a couple of sepolicy fixes
June 16th:
synced with LineageOS, including June's security patches
materialized toast messages
May 6th:
synced with LineageOS
May's security patches
updated SQLite library
April 6th:
synced with LineageOS
April's security patches
link-time optimization applied to some critical system components
minor updates and tweaks to the core OS
March 10th:
synced with LineageOS
March's security patches
removed rx_wakelock from the WiFi chip's driver (could lead to small power savings without affecting functionality)
March 2nd:
ro.debuggable=0 by default (fixes root detectors reporting system as rooted when it is not)
fix for a permission bug that made apps misbehave when trying to access the phone's sensors
wallpaper zooming has been disabled
synced with LineageOS
February 13th:
synced with LineageOS
fix for apps crashing on startup due to mishandling of the INTERNET permission
a few kernel updates & fixes for an infrequent kernel panic
January 13th:
/data partition encryption is fixed
January 11th:
synced with LineageOS
January's security patches
kernel: debloated WiFi driver
December 12th:
synced with LineageOS + December's security patches
general user interface improvements
build using the latest Clang 12.0.x compiler
minor fixes and updates here and there
November 6th:
synced with LineageOS
November's security patches
fix for laggy playback of HD videos in 3rd-party apps
October 8th:
synced with LineageOS + October's security patches
September 10th:
screenshot QS tile now fixed
September 9th:
synced with LineageOS
September's security patches
screenshot QuickSettings tile (first attempt, still broken - will fix it soon)
August 23rd:
synced w/ LineageOS (incl. August's patches)
WiFi display is back (thanks to the Lineage team!)
sporadic camera crashes are fixed (thanks to Nolen, the other bacon maintainer!)
July 10th:
synced with LineageOS + July's patches
DRM fixes (Clearkey support)
June 16th:
GPS improvements (hopefully now it'll work fine!)
June 10th:
synced with LineageOS (incl. June's security patches)
GPS fixes (work in progress)
some kernel updates and improvements
May 7th:
synced with LineageOS (w/ May's security patches)
updates for ART and bionic
April 29th:
synced with LineageOS
updated libyuv and libvpx
-O3 optimizations for critical system components
USB notifications have lower priority
minor miscellaneous tweaks
April 19th:
synced with LineageOS (NFC fix included)
GPS updates and improvements
touch response optimizations
minor tweaks and fixes
April 8th:
synced with LineageOS (w/ April's security patches + fix for display issue)
some kernel updates
lots of debugging code disabled
updates for jemalloc, sqlite, bionic, libcore and libpng
March 9th:
synced with LineageOS (w/ March's security patches)
some kernel updates
encryption is now working
February 27th:
synced with LineageOS
minor kernel updates
February 9th:
synced with LineageOS (with February's security patches)
some kernel fixes & updates
fix for the Gallery showing the previous photo instead of the new one, immediately after taking one
Ferbuary 3rd:
bootloop fix
February 2nd:
synced with LineageOS
WiFi hotspot fixed
Dynamic processing audio library
in-built F-Droid Privileged Extension
Dual-channel SBC codec for bluetooth headphones/speakers (untested, must be set in Developer Options)
minor tweaks to reduce memory usage (with negligible impacts on performance and/or graphic quality)
my custom kernel has been implemented
January 21st:
synced with LineageOS
updated & improved sqlite library (huge performance boost)
optimized zlib library
improvements for ART's memory usage
support for OTA updates
January 6th:
synced with LineageOS (January's security patches)
January 3rd:
synced with LineageOS
lockscreen PIN possibly fixed? Please confirm
December 26th:
fixed signature spoofing
synced with LineageOS
December 21st:
added support for signature spoofing (MicroG) and UnifiedNLP
December 14th:
initial build
DOWNLOADS
Starting from April 2023 my builds are moved to Github: https://github.com/Tomoms/bacon_releases/releases
Recommended Gapps package (official MindTheGapps): here
Spoiler: older 2020-2023 builds
Unified download link for both 17.1 and 18.1: SourceForge
Older 18.1 builds are available here: AFH
Previous 17.1 builds are available either on AFH or on MEGA (17.1) / on MEGA (18.1).
A BIG "THANK YOU" TO
the whole LineageOS team, and the multitude of great developers of the Android custom ROM scene, such as kdrag0n, kerneltoast (Sultanxda), nathanchance, flar2, franciscofranco, frap129, the MSM-Xtended project, the crDroid project. I hope I have not forgotten anyone.
POST-INSTALLATION ADVICE
GAPPS COMPATIBILITY
Only use MindTheGapps.
SETTING UP MICROG
Signature spoofing is supported but not enabled out of the box. There's no switch to enable it in Settings, you must grant its permission to each app that needs it. In particular, if you install MicroG (either via the apks or via MinMicroG), you must run these commands in a root shell:
Code:
pm grant com.google.android.gms android.permission.FAKE_PACKAGE_SIGNATURE
pm grant com.android.vending android.permission.FAKE_PACKAGE_SIGNATURE
then make sure all the checkboxes in MicroG's status screen are ticked and reboot.
SETTING UP VIPER4ANDROID
If you follow these steps carefully, you'll manage to install Viper4Android while keeping Enforcing SELinux, and it will survive across ROM updates too
Since XDA Labs has been dead for a while, I've reuploaded Viper4Android's apk installer here: https://mega.nz/file/htFikD6Y#HpcdSMSa6fPdB5EXhGnyYI4uoxA7R4TnzhAZD_J_jrk
PASSING SAFETYNET
Passing SafetyNet is quite easy. You need to have Gapps installed, though. Flash Magisk, enable Magisk Hide in its settings, reboot. Now you should pass SafetyNet.
GRABBING LOGS
If you have faced an issue, please provide logs when reporting it.
If the issue involved a random reboot of the device -> let the phone boot up again and immediately grab a copy of /proc/last_kmsg (important: don't turn off or reboot the phone a second time, otherwise it'll be useless).
If the issue did not involve a random reboot of the device, but instead some "softer" crash (e.g. an app crashing, a SystemUI restart...) -> grab a logcat using any app such as Logcat Reader or plug the phone to a computer and pull it using the adb logcat > logfile.txt command.
Reserved
First! I'm happy to finally see a real thread for this.
Perfect combination Sultans camera and idprophecy ROM.
question- can charging rate be varied using kernel auditor mod app?
Because whenever I'm installing a ROM having sultan customisation included my OPO charges very slowly(180mA).
kunalshgkr said:
Perfect combination Sultans camera and idprophecy ROM.
question- can charging rate be varied using kernel auditor mod app?
Because whenever I'm installing a ROM having sultan customisation included my OPO charges very slowly(180mA).
Click to expand...
Click to collapse
I don't know if KA mod has that feature. However it's possible to change the maximum charging current intensity with any text editor, check the second post of Neon kernel's thread: I've explained how to do it. However is the problem occurs only on sultanized ROMs, it might also be that the different battery driver thinks that your cable is faulty, and so it reduces the charging speed. I've had a similar issue when using the Linux 3.10 kernel on my phone.
Tomoms said:
I don't know if KA mod has that feature
Click to expand...
Click to collapse
KA mod sure has that feature if kernel has support for it
FSadino said:
KA mod sure has that feature if kernel has support for it
Click to expand...
Click to collapse
OK, the kernel supports it, so there should be no problem tweaking that value.
Tomoms said:
I don't know if KA mod has that feature. However it's possible to change the maximum charging current intensity with any text editor, check the second post of Neon kernel's thread: I've explained how to do it. However is the problem occurs only on sultanized ROMs, it might also be that the different battery driver thinks that your cable is faulty, and so it reduces the charging speed. I've had a similar issue when using the Linux 3.10 kernel on my phone.
Click to expand...
Click to collapse
Thanks for the reply. On your ROM my OPO is charging normally. Actually I was asking can the charging rate be varied in your kernel because in most of the kernel it is disabled. By the way I just installed this ROM awesome ROM but I'm experiencing slight lag in UI.
I've tested v10 of your kernel last weekend. I also had lags while scrolling. Did you remove cpu and touch boost? Couldn't find settings in cpu section of adiutor mod. Or are they managed in governor settings?
@Tomoms
Nice of you to share your work. I was just crying about for a ROM (Sultan base + OMS) and a good person linked me here. As it's relatively new I'm very optimistic
I have a couple of questions:
Have you tried your ROM with Xposed? (I just switched to Nougat (ViperOS) and the SOT is terrible. I'm trying to see what the cause is)
Is this version of your ROM based on Sultan's Oct 22 release?
I have only one phone at the moment and can't risk it with testings. My choices are reliant on your answers and the Epic XDA Community. Thanks in advance...
Wa.Sobchack said:
I've tested v10 of your kernel last weekend. I also had lags while scrolling. Did you remove cpu and touch boost? Couldn't find settings in cpu section of adiutor mod. Or are they managed in governor settings?
Click to expand...
Click to collapse
CPU boosting is present but KA doesn't support it, so it looks like it's missing but it's actually working in the background.
secretkloud said:
@Tomoms
Nice of you to share your work. I was just crying about for a ROM (Sultan base + OMS) and a good person linked me here. As it's relatively new I'm very optimistic
I have a couple of questions:
Have you tried your ROM with Xposed? (I just switched to Nougat (ViperOS) and the SOT is terrible. I'm trying to see what the cause is)
Is this version of your ROM based on Sultan's Oct 22 release?
I have only one phone at the moment and can't risk it with testings. My choices are reliant on your answers and the Epic XDA Community. Thanks in advance...
Click to expand...
Click to collapse
Nope, I don't use Xposed nor have I tried it.
The release doesn't include all the changes brought by Sultan in the 22nd October build (it includes one out of two of them), however this is not a problem, because the change I left out is a small reversion related to in-call volume that was made by him only because "users were not amused" by the improvement. So the only thing this build doesn't include is not a fix for a bug, just a small volume adjustment decrease that was made because nobody noticed the increase that was brought in the Spetember 30th build, so there's nothing to be worried about. This build is just as good as Sultan's last one.
Hey just to clarify is this based on sultan lineagos? I can see stuff committed by sultan
DeadFox-xda said:
Hey just to clarify is this based on sultan lineagos? I can see stuff committed by sultan
Click to expand...
Click to collapse
Read OP.
DeadFox-xda said:
Hey just to clarify is this based on sultan lineagos? I can see stuff committed by sultan
Click to expand...
Click to collapse
Yup, with his personal kernel and substratum support..!!
murti52 said:
Yup, with his personal kernel and substratum support..!!
Click to expand...
Click to collapse
And f2fs support too!
zalamandra said:
And f2fs support too!
Click to expand...
Click to collapse
Looks like that's been removed, but another file system looks like it's being implemented (at least partially).. #sdcardfs
Massive overnight battery drain
I'm so excited that my two favorite bacon ROMs have been merged together! Thanks for the effort.
Two things I have noticed for now:
- Camera appears to crash when snapping an HDR photo (similar to LineageOS camera's behavior)
- Quick unlock for four-digit PINs doesn't seem to work
Setting.Out said:
Looks like that's been removed, but another file system looks like it's being implemented (at least partially).. #sdcardfs
Click to expand...
Click to collapse
They are two different things, and both are present in my ROM+kernel.
Code:
/*
* Your warranty will be VOID after installing a custom ROM.
*
* Get notified yourself that 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.
*/
# LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
# What's working
Display/Touchscreen
LiveDisplay
Audio playback
Quad speakers
Headphone/Headset
Bluetooth audio
Video playback
HDR
Camera
Microphone
Sensors
Fingerprint sensor
GPS
LTE (SM-T825)
WiFi
WiFi display
Hotspot
Bluetooth
DRM
Widevine L1
USB ADB/MTP/OTG
Samsung Doze
S-Pen
Palm rejection
Hardware Encryption
MDFPP
SD Card
Power-off mode charging
# What's not working
SELinux permissive
Please see the "Known issues" part of this post
# Downloads
## LineageOS 18.1
Galaxy Tab S3 LTE (gts3llte, SM-T825)
Galaxy Tab S3 WiFi (gts3lwifi, SM-T820)
## Google Apps
OpenGApps
NikGApps
BiTGApps
Others may also work but not tested
## TWRP Recovery
You can use mine, please visit this thread.
You can use F2FS file system for cache, data partitions with my TWRP recovery.
[RECOVERY][SM-T820][SM-T825][UNOFFICIAL] TWRP for Galaxy Tab S3
# How to install
Unlock the bootloader.
Download TWRP and flash the recovery image via Odin.
Download LineageOS 18.1 for Galaxy Tab S3.
Be aware of the board name.
Download GAPPS for Android 11 and the others you want to flash.
Only OpenGApps is tested. (open_gapps-arm64-11.0-pico-20210130-TEST.zip)
Enter TWRP recovery.
The first boot to TWRP might be very slow because of the unmatched file systems.
Format the whole system, data, cache partitions using the format menu.
You will type `yes` to do that.
Flash the images.
If you're going to install GApps or something, you have to install the LineageOS first.
Reboot the system.
Done.
# Known issues
OTG drives may show nothing even if it mounted
The side button on S-Pen is working but you must use the proper application that can handle the button event
Fast charging works but it doesn't notify properly
Thank all of you for the feedback
# Sources
Device Tree
gts3l-common: https://github.com/awesometic/android_device_samsung_gts3l-common
gts3llte: https://github.com/awesometic/android_device_samsung_gts3llte
gts3lwifi: https://github.com/awesometic/android_device_samsung_gts3lwifi
Kernel: https://github.com/awesometic/android_kernel_samsung_msm8996
Vendor: https://github.com/awesometic/proprietary_vendor_samsung
# Telegram Groups
If you are interested in developing this potential machine, please tell me through PM then I will send you the invitation link.
If you need a general discussion channel for this potential machine or want to share the news of its Android projects from anyone to everyone, you can join our discussion group chat.
Galaxy Tab S3 General Discussion
# Buy me a coffee
If you like my efforts or would like to support me, please don't hesitate to buy me a cup of coffee.
https://www.paypal.com/paypalme/awesometic
# Credits / Special thanks to
Android Open Source Project
LineageOS Team
@Valera1978 for his amazing previous work including his MSM8996 kernel
@supermike86 and @samsuffit for testing LineageOS 18.1 for T820, which is I don't have one
@bmwdroid and @cherepanov for confirming the LTE works
@sebmue for letting me know that the useful information for palm rejection, and @ghostwheel for sharing its working source codes on Android 9
@switchgott for helping me in the development discussion and creating Telegram groups
All from our Telegram discussion channel, @EonOfBlack , Sands, David Becker, ...
@LuK1337 for giving me a hint to fix the quad-speakers.
## Changelogs
2023. 6. 17
gts3l-common: Syned with the latest LineageOS source
Applied the new security patch on June 5, 2023
2023. 5. 10
gts3l-common: Fix camera torch-related weird behaviors
It doesn't occur at least for me now. Please tell me if it occurs
Thanks to @Ivan_Meler
gts3l-common: Add support for Signature Spoofing
gts3l-common: Add support for OTA update
2023. 4. 16
gts3l-common: Applied the new security patch, March 5, 2023
gts3l-common: Properly implement MDFPP Keymaster set
gts3l-common: Enable Samsung DAP on boot, the Dolby effect
It just works automatically and there is no setting option for switching this feature
But you won't feel like disabling this since it isn't harmful at all
gts3l-common: Updated awesometic's kernel to v0.12
Spoiler: Changelogs in 2022
2022. 5. 8
gts3l-common: Applied the new security patch, April 5, 2022
gts3l-common: Switched to use only the MDFPP Keymaster set
gts3l-common: Fixed the fingerprint sensor recognition issue on some third-party application
gts3l-common: Fixed the Vulkan not activated
gts3l-common: Updated awesometic's kernel to v0.9
Disabled CPU AutoSMP, as known as CPU auto hotplug
Improved stability
2022. 3. 1
gts3l-common: Synced with the latest LineageOS source
gts3l-common: Fixed the broken hardware button settings
2022. 2. 23
gts3l-common: Applied the new security patch, February 5, 2022
gts3l-common: Enabled triple buffering of SurfaceFlinger
gts3l-common: Enabled partitions on loop devices
gts3l-common: Implemented thermal HAL, so that we can get the correct temperature from each hardware components
gts3l-common: Changed default CPU governor to blu_schedutil
gts3l-common: Changed the schedutil properties
gts3l-common: Set the default GPU frequency level to 6, which is 133 MHz in idle
gts3l-common: Enabled msm_irqbalance, which is from oneplus3
gts3l-common: Updated blobs
Updated Adreno libraries to v415, which is from daisy firmware (Android 10)
Changed media blobs to daisy firmware (Android 10)
Changed perf, thermal libraries to oneplus3 one
gts3l-common: Reduces ROM size
Removed unused camera firmwares
Removed unused Samsung specific OMX libraries
gts3l-common: Updated awesometic's kernel to v0.8
Cherry-picked lots of common upstream patches from LineageOS kernels
Added support for WireGuard
gts3llte: Fixed ipacm binary working
2022. 2. 9
gts3l-common: Applied the new security patch, January 5, 2022
gts3l-common: Fixed fingerprint working on a third-party app
gts3l-common: Updated built-in blobs to T825UBU3CUF1 by ZTO (from Brazil)
gts3l-common: Changed dynamic_stune_boost to 10 from 15
That value indicates a kind of reactivity of the CPU frequency of the schedutil governor. Generally, 10 to 20 is recommended, but in my test setting that 10 is enough to use the tablet smoothly and also can expect better battery and thermal.
Spoiler: Changelogs in 2021
2021. 12. 19
gts3l-common: Applied the new security patch, December 5, 2021
gts3l-common: Fixed aptX, aptX HD working
gts3l-common: Fixed WiFi display working
gts3l-common: Fixed a download fail problem for some games
gts3l-common: Changed the default CPU governor to schedutil
gts3l-common: Changed the default I/O scheduler to bfq
gts3l-common: Added Dolby audio effect
Added that library successfully but don't sure it is working, will investigate that too
gts3l-common: Added FlipFlap package for better handling of flip cover flips
gts3l-common: Added software navigation bar feature
gts3l-common: Enabled ZRAM for 2GB for a 4GB device
gts3l-common: Updated awesometic's kernel to v0.6
Merged EAS-Project/msm-3.18 and successfully migrated to EAS based kernel
Enabled EAS, WALT, Schedtune, Schedutil, ...
Added blu_schedutil CPU governor
Updated sdfat driver to 2.4.5
Updated camera driver
Imported/enabled ZRAM with LZ4 compress
Imported/enabled BFQ I/O scheduler
Optimized memory performance
Fixed a flip cover working
Maybe more...
2021. 11. 30
gts3l-common: Synced with the latest LIneageOS source
gts3l-common: Fixed Bluetooth input working including a Bluetooth keyboard
gts3l-common: Now it starts to use my custom kernel, awesometic's kernel v0.3
Merged android-linux-stable/msm-3.18, which is including up to Linux 3.14.140 patches
Merged LA.UM.7.6.r1-07800-89xx.0 CAF tag
Replaced the built-in WLAN driver into the CAF one from LA.UM.7.6.r1-07800-89xx.0 tag, which is the latest version
Disabled most of Samsung-specific flags including TIMA, KNOX, RESTRICT, ...
Enabled F2FS file system
Added AutoSMP CPU hotplug feature and enabled by default for better battery consumption
Added AdrenoBoost and enabled by default for better GPU performance
Added Anxiety I/O scheduler for better I/O performance
Enabled TCP Westwood congestion window control by default for better network stability
Set CONFIG_HZ to 300 which is recommended in Android devices and it improves overall interactivity and UX with no power cost
Now the S-Pen palm rejection is implemented in the kernel rather than the Android frameworks
Maybe more...
To get the detailed information, please see the third post of this thread
2021. 11. 16
gts3l-common: Applied the new security patch, November 5, 2021
gts3l-common: Fixed the external keyboards' arrow keys working
2021. 10. 29
gts3l-common: Applied the new security patch, October 5, 2021
2021. 9. 22
gts3l-common: Applied the new security patch, September 5, 2021
gts3l-common: Fixed the power-off mode charging using the Samsung LPM binary
gts3l-common: Switched to QTI USB HAL, version 1.2
gts3l-common: Cleaned up the keyboard layouts and added the layouts from the latest firmware for Samsung products like the book cover keyboard
gts3l-common: Improved power management
2021. 9. 1
gts3l-common: Fixed the camera working
gts3l-common: Resolved lots of SELinux warnings
gts3l-common: Added some props to optimize the video and media performance
gts3l-common: Added proper power profiles for better power management
gts3l-common: Added a proper thermal-engine config for better thermal management
gts3l-common: Change the hotspot location of the pointer arrow
2021. 8. 13
gts3l-common: Applied the new security patch, August 5, 2021.
gts3l-common: Fixed the quad-speakers working.
gts3l-common: Disabled WiFi display feature.
gts3l-common: Added support for Adaptive Fast Charge.
gts3l-common: Added LiveDisplay HIDL to switch the screen modes.
gts3l-common: Added the button backlight control menu.
gts3l-common: Added the advanced reboot menu.
gts3l-common: Changed to the Light HIDL completely.
gts3l-common: Changed the stylus pointer icon to the smaller one.
2021. 7. 29
gts3l-common: Fixed headphone jack working.
gts3l-common: Fixed Bluetooth audio playback working.
gts3l-common: Fixed microphone working.
gts3l-common: Fixed AudioFX working.
gts3l-common: Made hardware touch key, LCD, Touchscreen, S-Pen disabled when the screen turns off.
gts3l-common: Fixed DRM working.
gts3l-common: Disabled connecting to WPA3 WiFi.
gts3lwifi: Fixed Bluetooth working.
gts3lwifi: Fixed vibrator working.
2021. 7. 14
gts3l-common: Applied the new security patch, July 5, 2021.
gts3l-common: Added support for palm rejection for S-Pen.
gts3l-common: Added support for the Freeform Window mode of AOSP.
gts3l-common: Removed the "Serial console enabled. Performance is impacted..." message.
2021. 7. 4
gts3l-common: Changed the default DPI value to 320.
gts3l-common: Added new pointer arrow icon for S-Pen.
gts3l-common: Moved fingerprint sensor location when the preview screen that is before the actual enrollment a fingerprint.
gts3l-common: Enabled automatically brightness by default.
gts3l-common: Enabled adjusting haptic feedback intensity menu.
gts3llte: Fixed LTE working.
2021. 6. 28
gts3l-common: Separated the device tree into 3 parts, common, LTE, and WiFi.
gts3l-common: Changed the default DPI value to 360.
gts3l-common: Fixed fingerprint sensor working.
gts3l-common: No more adsprpcd errors on the logcat.
gts3llte: Added missing RIL-related binaries, init scripts and could check the RIL initialized properly. But an error still repeated on the logcat so I think it won't work yet.
gts3lwifi: Added support for Galaxy Tab S3 WiFi variants.
2021. 6. 17
Initial release
## About quad-speakers
Spoiler: Found things to make quad-speakers working
I have lots of tries to make quad-speakers working and finally, I think I found a way we should ahead.
I think the important parts for working quad-speakers are in the Samsung SoundBooster libraries. We can check this on the logcat easily.
Code:
12-31 13:28:24.101 708 708 I SoundBooster_plus: Use HardCoding Values
12-31 13:28:24.101 708 708 I SoundBooster7: SetPar()-whole parameter
12-31 13:28:24.101 708 708 I SoundBooster_Inner: SetPar()-partial parameter
12-31 13:28:24.101 708 708 I SoundBooster7:SoundBooster_Multiplexer: [mInstanceID:0]SetPar() SPK_0_OnOff : 1 , SPK_1_OnOff : 1 , SPK_2_OnOff : 1 , SPK_3_OnOff : 1
12-31 13:28:24.101 708 708 I SoundBooster_Inner: SetPar()-partial parameter
12-31 13:28:24.101 708 708 I SoundBooster7:SoundBooster_Multiplexer: [mInstanceID:1]SetPar() SPK_0_OnOff : 1 , SPK_1_OnOff : 1 , SPK_2_OnOff : 1 , SPK_3_OnOff : 1
12-31 13:28:24.101 708 708 I SoundBooster7: SetVolumeTable()
12-31 13:28:24.101 708 708 I SoundBooster7: SetOrientation( 0 )
12-31 13:28:24.101 708 708 I SoundBooster_Inner: SetOrientation( 0 )
12-31 13:28:24.102 708 708 I SoundBooster7:SoundBooster_Multiplexer: [mInstanceID:0]SetOrientation(0)
12-31 13:28:24.102 708 708 I SoundBooster7:SoundBooster_Multiplexer: [mInstanceID:0]Set_Orientation_Update_Flag() flag : 1
12-31 13:28:24.102 708 708 I SoundBooster_Inner: SetOrientation( 0 )
12-31 13:28:24.102 708 708 I SoundBooster7:SoundBooster_Multiplexer: [mInstanceID:1]SetOrientation(0)
12-31 13:28:24.102 708 708 I SoundBooster7:SoundBooster_Multiplexer: [mInstanceID:1]Set_Orientation_Update_Flag() flag : 1
Yes, I cannot really sure it initializes quad-speakers, but the name like SPK_#_OnOFF looks really interesting.
So if it is the one who makes quad-speakers working, then it looks quite easy; Use SoundBooster libraries.
But it is not that easy to use that library, properly.
The libraries, the vendor binaries, in other words, have a lot of dependencies on other libraries, each other. It sounds like it can be so complicated and you are right, sometimes it becomes so complicated to use.
Each library contains a list of which library it must go together so it is easy to supplement them. But we don't know which configuration files and the other libraries called by hardcoded code are needed because it is a binary file. Even the directory structure can be a matter.
For this reason, I could call the SoundBooster libraries like the above messages by using the many many prebuilt libraries but could not get the quad-speakers working so far. In the logcat the audio stuff annoys me about the lack of backend entries and something but I don't know what I am missing.
Plus, maybe it isn't a good idea to cover errors using shims or something because we still don't know which part needs to get the quad-speakers working.
I really hope the fully working speakers on the custom ROMs but it may take time.
### Update on 2021. 7. 29
Finally, I can enable the vendor audio HAL that comes with that SoundBooster to work. But so far no good for the quad speakers.
Even though the quad-speakers do not work yet, I think that the SoundBooster library is needed anyway. Because I saw the speaker rotation codes for the quad-speakers in that library.
So maybe the speaker itself is ready now, but something doesn't seem to be filled.
I have no idea for now, so I will update this post as soon as I find something.
### Update on 2021. 8. 13
Finally, I could get the quad-speakers working.
Actually, the answer was so close to me. The key factor is even I saw before but I didn't think that it is so important.
In short reports, the Samsung libraries do their work but somewhat partially. I could check how each speaker configured using tinymix tool and found that the upper speakers' I2S channel must be set manually in our case.
So we have to have the vendor libraries for audio anyway. It should work without them, but we have to find lots of configurations to fit into our devices. So, it may be best to keep the libraries.
Enjoy the quad-speakers.
## About the camera
Spoiler: The reason why the camera is not supported so far
## Why the camera doesn't work? It works on the previous LineageOS on this forum
Right, it does. I think it may be related to the vendor files. Before starting the development LOS 18.1, I have to update vendor files from the latest firmware. But after that, the previous definitions for the camera on `device.mk` began not to work.
So, I should start again from scratch. Have to find out how many files the vendor files require, or how can I build the camera binaries from the sources.
Before all, I won't fix that right now. Since I think the camera is not that important as the others like the audio or the kernel, in general. It is an old tablet, having a just-could-be-used camera. Sorry for who loves its camera.
### Update on 2021. 9. 1
Yeah, now we have the working camera too.
For now, our builds use the vendor's pre-built camera libraries so that it may not be optimized for a custom ROM. But in our use case it works really nice..... except for some bugs.
Maybe the default camera daemon has slightly different settings for the flashlight. If I use a camera at least once, maybe, the turning on the flashlight by the toggle button on the quick panel no longer works. It looks like a protocol problem between the Android SystemUI and the prebuilt camera daemon, so I don't know how to fix that neatly for now.
And sometimes using a camera app reduces the UI performance for a launcher app and the animation when pulling down the quick/notification panel. Also, I don't know why this behavior happens. The most strange thing is that this reducing performance only appears with the launcher app as far as I have seen.
So, anyway, for this reason we should build ours from the AOSP/LOS source codes someday.
But, I can say that it works like a charm now. It will be doing much better if you use Open Camera from PlayStore.
I'm not advertising it, just to share the experience.
Code:
/*
* All done. Enjoy the camera and audio!
*/
## About the kernel
### Update on 2021. 12. 20
Spoiler: First release of the Galaxy Tab S3 custom kernel
Finally the first release including my custom kernel is published, as of December 3, 2021.
Now all the later releases will have my kernel.
This kernel is based on CTD1 firmware, and I have done the following jobs so far;
Merged android-linux-stable/msm-3.18, which is including up to Linux 3.14.140 patches
Merged LA.UM.7.6.r1-07800-89xx.0 CAF tag
Replaced the built-in WLAN driver into the CAF one from LA.UM.7.6.r1-07800-89xx.0 tag, which is the latest version
Disabled most of Samsung-specific flags including TIMA, KNOX, RESTRICT, ...
Enabled F2FS file system
Added AutoSMP CPU hotplug feature and enabled by default for better battery consumption
Added AdrenoBoost and enabled by default for better GPU performance
Added Anxiety I/O scheduler for better I/O performance
Enabled TCP Westwood congestion window control by default for better network stability
Set CONFIG_HZ to 300 which is recommended in Android devices and it improves overall interactivity and UX with no power cost
Now the S-Pen palm rejection is implemented in the kernel rather than the Android frameworks
Maybe more..?
But we have still some limitations.
It still uses the legacy camera driver from CTD1 firmware so unfortunately there are the same bugs on the camera as before
The screen on/off using a flip cover is broken for an unknown reason. The system recognizes how the flip cover status changed but actually not working
Cannot upgrade to the next CAF tag because of some old blobs we have, I believe
Maybe more..?
This is the first version of mine, so there might be some more upgrades on later.
I think the most meaningful thing about this job is now we can edit the kernel on the full Linux kernel commits.
Enjoy.
Hello all.
Finally, I successfully enabled EAS (Energy Aware Scheduler) so that we can expect a more fast and reliable system.
What is EAS: Linux Kernel | Energy Aware Scheduling (EAS) – Arm Developer
And I solved most of the problems that occurred while I merged the CAF tag, including fixing the flip cover working. Also, I have improved the kernel in various aspects.
So I would like to say that it gets much more useable than before.
But I think it won't fix some problems like supporting the PS4 controller through Bluetooth and some system bugs because these problems might be solved with the new AOSP kernel changes from Google. But I didn't merge that yet.
The next will be that part, I hope I could solve that.
Sweet!
Unfortunately my wife uses out tablet for work too so I can't really mess with it.
Plus ours is 820 (non-LTE), so I'm not sure if the alpha will work anyway.
But I am quite curious to try some time.... maybe I'll just get a more recent work-tab
elchmartin said:
Sweet!
Unfortunately my wife uses out tablet for work too so I can't really mess with it.
Plus ours is 820 (non-LTE), so I'm not sure if the alpha will work anyway.
But I am quite curious to try some time.... maybe I'll just get a more recent work-tab
Click to expand...
Click to collapse
Thanks for your interest.
I believe I can create a WIfi version without the actual machine. It will be uploaded in a few days I think comes with implementing the common device tree.
Awesometic said:
Code:
/*
* Your warranty will be VOID after installing a custom ROM.
*
* Get notified yourself that 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.
*/
# LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
# What's working
Display/Touchscreen
Audio playback (only bottom speakers)
Video playback including HDR
Sensors
GPS
WiFi
Bluetooth
USB ADB/MTP
Samsung Doze
S-Pen
SD Card
# What's not working
Audio (quad speakers)
Bluetooth audio playback
Microphone
Camera
LTE
DRM
SELinux permissive
Hardware encryption
Fingerprint sensor (recognized but enrollment failed)
Lots of things I couldn't find...
# Downloads
LineageOS 18.1: https://drive.google.com/drive/folders/1JfPpFpSHXywzV3lw0rnEVVCXJxI5iw0X?usp=sharing
OpenGApps for Android 11: https://sourceforge.net/projects/opengapps/files/arm64/test/
# How to install
Unlock the bootloader.
Download TWRP and flash the recovery image via Odin.
Download LineageOS 18.1 for Galaxy Tab S3.
Be aware of the board name.
Download GAPPS for Android 11and the others you want to flash.
Only OpenGApps is tested. (open_gapps-arm64-11.0-pico-20210130-TEST.zip)
Enter TWRP recovery.
The first boot to TWRP might be very slow because of the unmatched file systems.
Format the whole system, data, cache partitions using the format menu.
You will type `yes` to do that.
Flash the images.
If you're going to install GApps or something, you have to install the LineageOS first.
Reboot the system.
Done.
# Notes [2021. 6. 17]
Some annoying messages are repeated on the logcat, which I think the tiny stutters may cause for this reason.
Fingerprint and some other minor things may be fixed soon but not sure about audio and camera.
For now, it may not be good for the daily driver. Please be aware that this is a test version yet. I have no responsibility for your data.
The device tree sources will be separated into two types of boards for better maintaining.
# Sources
Device Tree: https://github.com/awesometic/android_device_samsung_gts3llte
Kernel: https://github.com/awesometic/android_kernel_samsung_msm8996
# Buy me a coffee
If you like my efforts or would like to support me, please don't hesitate to buy me a cup of coffee.
https://www.buymeacoffee.com/awesometic
# Credits / Special thanks to
Android Open Source Project
LineageOS Team
Valera1978 for his amazing previous work including his MSM8996 kernel
Click to expand...
Click to collapse
Thank You !
Thx, i also have a wifi version you are doing this community a huge favor
Hi, any chance to add support for LTE?
warlord2045 said:
Hi, any chance to add support for LTE?
Click to expand...
Click to collapse
The authors device is lte based....so it would naturally have support lmao
Edit: My Bad, i was sleep deprived and dump
sm00th4f3 said:
The authors device is lte based....so it would naturally have support lmao
Click to expand...
Click to collapse
I installed but no LTE so i went back to Lineage 17
warlord2045 said:
I installed but no LTE so i went back to Lineage 17
Click to expand...
Click to collapse
Right, LTE isn't working yet because there're other things I have to fix first.
But LTE will be fixed for sure because it is why the LTE version exists.
Awesometic said:
Right, LTE isn't working yet because there're other things I have to fix first.
But LTE will be fixed for sure because it is why the LTE version exists.
Click to expand...
Click to collapse
Looking forward to test out
I'm really eager to start using this as a daily driver, thank you
Will you also be working on the t820, because i see this id for t825?
LedgendaryEpics said:
Will you also be working on the t820, because i see this id for t825?
Click to expand...
Click to collapse
Yes, I'm working on T820 now, actually, it's a little late because I tried some things including fixing the fingerprint working.
And I saw some interesting strings are in the audio.primary.msm8996 binary. I have tried using this but doesn't work so far.
If the quad-speaker can be enabled by that binary file, we should use that file on the fly.
But for now, it seems to take a lot of time, so I will upload the image for T820 before working on the quad-speaker.
Any volunteer to test LineageOS 18.1 for T820?
It may need clean install. It'd be someone who can erase all of his data.
Please test this image and let me know it works or not. If it works, I will update the thread.
- https://drive.google.com/file/d/1yMq8wAsJKIXf5C6iBF5kZCK6lngkDPwN/view?usp=sharing
Awesometic said:
Qualche volontario per testare LineageOS 18.1 per T820?
Potrebbe essere necessaria un'installazione pulita. Sarebbe qualcuno che può cancellare tutti i suoi dati.
Prova questa immagine e fammi sapere che funziona o meno. Se funziona aggiornerò il thread.
- https://drive.google.com/file/d/1yMq8wAsJKIXf5C6iBF5kZCK6lngkDPwN/view?usp=sharing
Click to expand...
Click to collapse
Proverò e ti farò sapere
Edit:
the installation was successful, even with the installation of the nano gapps. wifi is working properly. for other bugs among those mentioned I have not had the opportunity to test yet. but in my opinion the system is very good and fluid, great job. it would be great to have this rom for daily use! thank's for your job!
Awesometic said:
Any volunteer to test LineageOS 18.1 for T820?
Click to expand...
Click to collapse
I don't use this tablet anymore because of the reset time after reboot bug and lack of basic functions, like 4 speakers or stylet with alternative roms.
With my minimal needs and without Google Apps, it's working good. I'll spent few days on it and I tell you more.
Awesometic said:
Any volunteer to test LineageOS 18.1 for T820?
It may need clean install. It'd be someone who can erase all of his data.
Please test this image and let me know it works or not. If it works, I will update the thread.
- https://drive.google.com/file/d/1yMq8wAsJKIXf5C6iBF5kZCK6lngkDPwN/view?usp=sharing
Click to expand...
Click to collapse
I installed it from the link in the first post with OpenGapps Nano (also from the first post), and so far so good.
This is really much much faster than the "Tweaked" ROM! It feels like a new tablet.
I don't use the camera, so for me it’s already very usable. I didn't notice any problem with audio. There is only sometimes a short popup appearing (a few milliseconds) and disappearing. Also, if you enable "Trust" it complains about SELinux and some stuff.
Anyway I will keep this fast ROM, great work, thank you!
EDIT: There is also a notification saying : "Serial console enabled. Performance is impacted. To disable, check bootloader" which i didn't understand the meaning...
You are so good! Thanks so much.
I do have 2 of the WiFi tablets and will test after my holiday.
The original firmware is really crap and so slow, hope that this is faster.
The only problem is I need it as daily driver, but will make a complete backup.
Greetings from Bavaria
Kirisakura-Kernel for the Sony Xperia 1 III
Hello everyone,
To keep it short: Here is Kirisakura - Kernel for the Sony Xperia 1 III aka Sagami. Sagami is the internal codename for this years development platform of Sony Mark III devices. Please note this kernel is made to run only on Xperia 1 III.
I would appreciate if everybody that flashes the kernel, reads at least once through this opening post and the following ones.
Kirisakura - Kernel is designed to bring a handful of beneficial features to the device, while ensuring excellent performance and smoothness to get you safely through the day!
If you expect a custom kernel to magically improve your devices battery life manifold and this is your only priority then this might not be the right place for you.
However the kernel is built to keep battery life close to the same as you would experience the on stock kernel while being tuned to perform better in various UI related benchmarks. The same benches are used by google to verify and ensure UI smoothness on the Pixel devices.
There´s also a cpu-battery saver mode that cuts back the CPU max- freqs, but without the disadvantages like delayed notifications from built into the system user-space power-saving modes.
If that got your curious, I welcome you to continue reading if you´re still interested!
The kernel includes a lot of improvements and contributions from other developers as well. Without this kernel would not exist.
A big part of improvements originate from @arter97´s, @kdrag0n´s and @Sultanxda´s work. Many others contributed in some way or another to this kernel.
A big thanks to all of them at this place!
Now lets continue with a list of features in the next paragraph!
Main Features:
- Based on latest kernel sources from Sony for Android 12 and intended to be used on the latest Stock-Firmware
- compiled with Clang 14.0.7 and built with -O3 speed optimizations
- Linux-Stable-Upstream included to 5.4.202
- upstreamed CAF base for the Snapdragon 888 (qcoms internal codename "lahaina")
- CPU-Battery saver to be able to restrict max cpufreqs on the fly, without enabling powersaving modes that might cause missed notifications (more info here)
- include important fixes/improvements from kernel/common
- reduce power consumption during deep sleep
- remove logging while device is suspended
- add SSG-IO scheduler from samsung (less overhead, better tuned towards android)
- disable various debugging mechanisms for drivers which are not needed on a perf build (e.g. binder)
- disable selinux auditing (we don´t have to adress selinux denials running a stock rom)
- disable unnecessary CPU errata for our specific SoC
- implement LRNG (thanks @arter97, see arter kernel OP for more info )
- Flashing the kernel will keep root!
- Flashable via EXKM, FKM or TWRP (if available) on a rooted system!
EAS related features:
- Implement dynamic WALT-Window size depending on current FPS, collecting information about CPU-Load to provide more precise information for the scheduler
- EAS implementation patched up to latest CAF state
- updates from kernel/common
- scheduler updates from sd888/ 5.4 kernel
CPU related features:
- Power saving workingqueues enabled by default (toggleable in EXKM)
- Change various drivers (WLAN, MM, audio, charger, power, thermal, glink etc) to use power efficient workingqueues. This compliments EAS in general
- improvements to cpufreq/times/stats
- vdso32 patches as found on Google Pixel devices (brief documentation here) (CAF 5.4 default, keep for documentation)
- remove event debug logging
- disable broken irq detection, disable debugmon
- improve suspend/resume from audio driver (caf-upstream for audio-kernel)
- cpuidle: wake only cpus for which qos has changed (this allows cores to keep idle states better)
- disable debugging during sleep states as per qcom recommendation
- remove RTB logging to reduce overhead
- disable trace_printk as it shouldn´t be used on production/perf kernel builds
- enable suspend_skip_sync to save power during suspend/resume
- disable edac and coresight (following google on the pixel kernels)
- disable jtagv8 debugging as recommended by qcom for perf builds to avoid potential power, performance and memory penalty
- disable s2idle in favor of deep idle state -> improves deep sleep drain (google initially used 2idle for improved suspend/resume latency on pixel 3 and pixel 4, but disabled it on pixel 5. qcom followed suit for sd 888, but apparently didn´t see google reverting it on pixel 5. Other OEMs such as Xiaomi or OnePlus already disabled s2idle on their SD888 devices in favor of deep- read more about s2idle vs deep here)
GPU related features:
- GPU driver updated to latest CAF-State
- gpu/kgsl improvements from pixel 4/pixel 5 kernel
- add low_prio_worker thread for gpu driver (Improves performance when tearing down processes (eg, via LMK) and not blocking currently running UI from submitting work to the GPU
File System related features:
- upstream BFQ-MQ to latest state in linux-mainline and default to 128KB readahead
- improve memory allocations in kernfs
- ufs improvements from pixel 4/ pixel 5 kernel
- improve GC as to not interfere while user interaction is happening and prevent possible jitter or latency spikes
Network related features:
- Wireguard Support (Details)
- advanced TCP algorithms enabled
- use bbr as default TCP congestion algorithm (fasted algo according to this excellent research from @kdrag0n found here )
- improved networking drivers from caf-upstream (especially wifi)
- remove unnecessary wakelock from WLAN driver to reduce thousands of very short wakeups during a 7 hour deep sleep period
- improved bluetooth performance (¹, ²)
- Enable support for TTL spoofing
Memory related features:
- Speculative Page Faults left enabled (1. 2) (CAF 5.4 default, keep for documentation)
- Fix various memory leaks in different subsystems
- improved mm with patches from mainline
- patches from kernel/common
- improve memory allocations in various subsystems, video encode/decode, kernfs, cgroup
- Backport to enable CONFIG_HAVE_MOVE_PMD (see here) , thanks @arter97
- Backport to enable CONFIG_HAVE_MOVE_PUD (commit here) , thanks @arter97
- free more RAM by removing unused reserved memory regions
- mm: Micro-optimize PID map reads for arm64 (improves game performance, especially unity based games such as genshin impact)
- MGLRU added (info here and here
Security related features:
- Control-Flow-Integration (CFI) and Link-Time-Optimization (LTO) (CAF 5.4 default, keep for documentation)
- Use ThinLTO which was first used in the Pixel 4 XL Android R-Kernel instead of full LTO (CAF 5.4 default, keep for documentation)
- Shadow Call Stack (SCS) Security-Feature ( 5.4 default, keep for documentation)
- enable init_on_alloc for even more security, more information can be found in the commit message (CAF 5.4 default, keep for documentation)
Misc Features:
Wakelock Blocker:
- advanced wakelock blocker with the ability to block any wakelocks (dangerous, use with caution)
- please read [URL="https://arstechnica.com/gadgets/2018/08/p-is-for-power-how-google-tests-tracks-and-improves-android-battery-life/"]this for further info
- blocking a kernel wakelock should only be done in case of firmware incompatabilities (WiFi network at work (can´t be changed) causes deep sleep to not work on the phone.) That´s the only use case I see for this feature. The kernel does not features this to improve battery life!
Other features:
- clean up asus drivers and fix a few warnings in kernel log
- disable logging and debugging to make the kernel more lightweight in various places (includes binder, mm, vma, gpu, ipa etc)
- fix several coding issues detected by newer Clang-Toolchains
- enlarge dmesg size to ease debugging
Flashing Guide, Download and Changelog
Requirements:
- unlocked Bootloader
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries
- working adb and fastboot environment
- magisk root
- a backup of stock boot.img or your magisk patched boot.img in case you want to go back to stock.
How to flash the Kernel:
1. Download the latest kernel.zip and make sure you have properly updated to the latest matching Firmware (check the feature list for the current firmware the source is based on). When there´s an OTA update for the Sony Xperia 1 III it takes Sony a while to release the source code for the new OS and me a while to build a new kernel. If you don´t want to face any issues, wait until I either release an updated kernel or give green light because there were no kernel changes.
If you want to be sure there are no issues, always make sure to run the firmware the kernel is built for!
If you feel adventurous and try in advance, make sure you have a backup ready!
2. Flash the kernel.zip via latest TWRP (if available), EXKM or FKM app and do a full reboot.
3. Reboot and profit.
DOWNLOAD:
Download is located always in this folder:
https://www.androidfilehost.com/?w=files&flid=331114
Or attached to the release post starting with Android 13 as AFH is currently not working correctly
Important: Read after Download
Please take a look at the second post after flashing the kernel!
Changelog:
Android 11
1.0.0 Initial Release
1.0.1 https://forum.xda-developers.com/t/...xperia-1-iii-aka-sagami.4377449/post-86140929
Android 12
2.0.0
[Kernel][02.07.2022][Android 12] Kirisakura 2.0.0 for Sony Xperia 1 III aka "Sagami"
Kirisakura-Kernel for the Sony Xperia 1 III Hello everyone, To keep it short: Here is Kirisakura - Kernel for the Sony Xperia 1 III aka Sagami. Sagami is the internal codename for this years development platform of Sony Mark III devices. Please...
forum.xda-developers.com
Android 13
3.0.0 https://forum.xda-developers.com/t/...xperia-1-iii-aka-sagami.4377449/post-88048199
3.0.1 https://forum.xda-developers.com/t/...xperia-1-iii-aka-sagami.4377449/post-88404445
Donations:
Donations are not mandatory but very welcome if you want to support development or just buy me a coffee/tea
If you like my work: http://paypal.me/freak07
Credits:
Sony for the development device, giving me the opportunity to create this project!
@osm0sis for all his work, including the ak3 installer!
@tbalden for being the best HTC, Pixel, OnePlus and now Asus wingman!
@LeeDroid and @mwilky for their awesome roms and work I used on multiple devices!
@Captain_Throwback for all the mentoring and guidance!
@Eliminater74 for bringing me into the game and the Inspiration
@nathanchance for his upstream guidance and assistance
@RenderBroken for helping me out
@flar2 for all his work
@joshuous for all the help he provided to me in the past!
@arter97 for giving me advice
@kdrag0n for his help and advices!
@topjohnwu for magisk!
Source Code: https://github.com/freak07/Kirisakura_Sagami
F.A.Q:
Question: Is root preserved when flashing this kernel?
Answer: Yes, the AnyKernel.zip will detect root and keep it.
Question: Safetynet does not pass on my phone since I unlocked the phone, why is this so?
Answer: Google introduced hardware backed attestation recently. Unfortunately the old kernel tricks to still get safetynet passing won´t work. Instead you will have to rely on some magisk modules. Short guide in post #4 below.
Question: How do I return back to stock or another kernel.
Answer: Extract boot.img from the matching firmware you are on (you can do so by using this tool or similar ones found on XDA and when googling around) and flash them via fastboot. If you want to keep root flash back the magisk_patched_boot.img. Or dirty flash your rom and re-root.
Question: Why is having Magisk installed mandatory for this kernel?
Answer: The kernel uses a ramdisk overlay to apply some settings after boot. If you are not rooted these settings will not get applied and you miss some of the optimizations.
Question: How to report bugs properly?
Answer: Have a look at post #3 in the linked thread. The linked guide is a pretty good starting point.
Before reporting any bug make sure you´re running on a stock configuration. That´s means you´re not using any mods, tweaks in kernel managers or other root tweaks , magisk modules, scripts or other modifications that alter various functions like sound mods, data traffic, sleeping behaviour, scheduler, magical battery tweaks etc.
Try to describe the issue as detailed as possible! Give your exact setup, like rom, magisk version, kernel version.
Is the issue reproducible? Does it happen frequently?
Please make sure to meet the points described above, provide logs as detailed in the link above, otherwise debugging is a lot more time consuming and harder. (kernel flashing apps usually support exporting logs of flashes too) If these requirements aren´t met and I don´t find time to either reproduce the issue myself or I´m not able to reproduce the issue myself, reports might just be ignored. If you can already reproduce the issue and provide logs it greatly limits the amount of time I have to spent until I figure out how to reproduce it.
If the device force reboots/randomly reboots (that means you see the bootloader unlocked screen!) provide a .zip of /asdf.
Easiest way is immediately after booting up, with a root explorer navigate to /asdf. Copy the contents to your internal storage, zip it up and send it to me.
If the issue happens while the device is running provide a dmesg plus a logcat that you take while/shortly after the issue happens. This will log what´s running in the current session. Try to be as detailed as possible what´s happening when the issue appears. It will also help me in reading the log!
Feature Documentation:
Here´s a brief documentation about some of the features included in the kernel that can be changed as the user desires.
They can be accessed via either terminal, scripts or for example EXKM manager ( tools -> user settings).
CPU-Frequency Limiting:
Another option is CPU-Freq Limiting. You can now limit the CPU frequency to a few different levels with a sysfs interface. Original implementation is from @tbalden, I only changed it to be accessible via traditional root methods.
Main Switch:
sys/module/cpufreq/parameters/batterysaver
Set this option to "1" to enable the feature
Max-Frequency Selection (Input boosts, such as scrolling boost or app launching boosts will still apply, if touch boost restriction is not set to 1)
sys/module/cpufreq/parameters/batterysaver_level
Set this to "1" to restrict the max CPU-Freqs to 1,7GHZ/2,1GHZ/2,49GHZ (Little Cluster/Big Cluster/Prime Core)
Set this to "2" to restrict the max CPU-Freqs to 1,6GHZ/1,7GHZ/2,0GHZ (Little Cluster/Big Cluster/Prime Core)
Set this to "3" to restrict the max CPU-Freqs to 1,49GHZ/1,4GHZ/1,6GHZ (Little Cluster/Big Cluster/Prime Core)
Touch-Boost Restriction
sys/module/cpufreq/parameters/batterysaver_touch limiting
Set this to "1" to restrict the powerhal from boosting over the limit defined in batterysaver_level
Set this to "0" to allow the powerhal to boost above the values defined in batterysaver_level, but only during interaction with the Phone!
Screenshots:
View attachment 5309899View attachment 5309901View attachment 5309903
This is for example very useful during gaming to prevent additional heat, if not the highest performance from the CPU is required. Check if the game is running fine on level 1 or 2, and you´ll notice much less heat. Powerdraw will be reduced as well.
Another very useful trick while doing video calls or long extended navigation sessions with google maps to preserve battery or keep the phone from heating. Especially during summer if the ambient temperatures are high.
This is a very easy way to preserve battery or reduce heat without toggling the battery save mode in settings as that restricts background data usage, which can lead to delayed notifications.
How to pass Safetynet after unlocking the bootloader
With the introduction of hardware backed safetynet attestation, passing safetynet has become a lot more complicated.
Some probably remember a while ago, flashing a kernel that forced some flags was enough to pass it. However these days are gone.
Below is a short guide how to pass safetynet on phones that are flagged to use HW attestation (such as the ROG 5).
1. Make sure you´re running latest magisk canary.
2. In Magisk Manager enable both zygisk and deny list.
4. Download the latest Universal Safety Net Fix from @kdrag0n ´s github for zygisk cand flash it in Magisk Manager. Reboot.
5. Profit
this one is the last one
Freak07,
Please not this kernel is made to run only on Xperia 1 II
Click to expand...
Click to collapse
I guess it should be "Please note this kernel is made to run only on Xperia 1 III"
By the way, is there any plans to make same kernel for 5 III ?
Source Code: https://github.com/freak07/Kirisakura_Sagami
Click to expand...
Click to collapse
Leads me to nowhere (404).
dron39 said:
Freak07,
I guess it should be "Please note this kernel is made to run only on Xperia 1 III"
By the way, is there any plans to make same kernel for 5 III ?
Leads me to nowhere (404).
Click to expand...
Click to collapse
Fixed the typos and the link.
No, I only have the Xperia 1 III to work on.
Amazing work mate, very meticulous tuning. Would love to have this kernel on the 5 III. I understand the device architectures are quite similar?
treff89 said:
Amazing work mate, very meticulous tuning. Would love to have this kernel on the 5 III. I understand the device architectures are quite similar?
Click to expand...
Click to collapse
I asked the same question above
And unfortunatelly Freak07 do not support 5 III because he doesn't have it. Hope someone else could transfer his patches and things to 5 III.
Thanks for the kernel. However after installing the kernel my SD card gave an error. It says issue with the SD Card tap to fix and then asks me to format it?
BlazingKahn35 said:
Thanks for the kernel. However after installing the kernel my SD card gave an error. It says issue with the SD Card tap to fix and then asks me to format it?
Click to expand...
Click to collapse
I see. Thanks for the report!
I think i know whats up. They use a proprietary driver for exfat formatted sdcards ( I assume yours is formatted as exfat?) so it's not included in the source i build the kernel from.
I don't use a sdcard, that's why I missed it.
treff89 said:
Amazing work mate, very meticulous tuning. Would love to have this kernel on the 5 III. I understand the device architectures are quite similar?
Click to expand...
Click to collapse
dron39 said:
I asked the same question above
And unfortunatelly Freak07 do not support 5 III because he doesn't have it. Hope someone else could transfer his patches and things to 5 III.
Click to expand...
Click to collapse
They are similar, but I can't support a device i don't own. I also lack the time to do any remote debugging.
The phones however are similar as you mentioned, so if somebody is interested in starting to work on it all my work is up on GitHub. That might make it a lot easier than it would be otherwise.
Freak07 said:
I see. Thanks for the report!
I think i know whats up. They use a proprietary driver for exfat formatted sdcards ( I assume yours is formatted as exfat?) so it's not included in the source i build the kernel from.
I don't use a sdcard, that's why I missed it.
Click to expand...
Click to collapse
Yes mine is exfat since it's 256gb but not a big issue. I just transferred all my files to PC formatted the SD and transferred back now it works.
Also I'm using forced 4K all the time. But the only downside is the slowing down of the FP sensor. I think it's a kernel panic can you look in to that also maybe? (It was also slow on stock kernel)
Dear developer, if there is an opportunity, I would like to receive a kernel for PRO-I products!
I promise to donate
Update to 1.0.1
Good morning everybody,
thanks to @BlazingKahn35 ´s report exfat formatted sdcards are now working fine again.
Included an open source driver, that spoofs texfat support (the proprietary exfat driver) once an exfat sdcard is detected.
Download link can be found in the OP.
BlazingKahn35 said:
Also I'm using forced 4K all the time. But the only downside is the slowing down of the FP sensor. I think it's a kernel panic can you look in to that also maybe? (It was also slow on stock kernel)
Click to expand...
Click to collapse
Not sure what you mean. A kernel panic crashes the device so that it reboots.
The fingerprint scanner works fine for me. I place my finger on it, it scans and proceeds to unlock. It's not the fastest around, but it's quick enough for me.
Also used the adb commands to enable 4k and the speed of the fingerprint sensor stayed the same on my end.
I noticed just as I woke up that my phone was charged to 100%. Did you removed battery care from the kernel?
Freak07 said:
Not sure what you mean. A kernel panic crashes the device so that it reboots.
The fingerprint scanner works fine for me. I place my finger on it, it scans and proceeds to unlock. It's not the fastest around, but it's quick enough for me.
Also used the adb commands to enable 4k and the speed of the fingerprint sensor stayed the same on my end.
Click to expand...
Click to collapse
For me there is a big delay sometimes. Do you have AOD enabled?
BlazingKahn35 said:
I noticed just as I woke up that my phone was charged to 100%. Did you removed battery care from the kernel?
Click to expand...
Click to collapse
Not intentionally no. It might be not enabled the way I built the source or i need to see if the drivers is available somewhere else to be able to build it in.
I'll play around with it the next few days, see if I can reproduce the issue and find what's missing or broken. Thanks for the report again.
BlazingKahn35 said:
For me there is a big delay sometimes. Do you have AOD enabled?
Click to expand...
Click to collapse
Not constant AOD. Only waking to AOD screen when lifting the phone is enabled.
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.
This is LineageOS 19.1, which is based on Android 12L, for variants of the Samsung Galaxy Tab A 10.1" (2016), which have models and codenames as follows:
SM-T580, with codename gtaxlwifi
SM-T585, with codename gtaxllte, along with SM-T585N0 and SM-T585C
SM-P580, with codename gtanotexlwifi, along with SM-P583
SM-P585, with codename gtanotexllte, along with SM-P585M, SM-P585Y, SM-P585N0, and SM-P588C
LineageOS doesn't need much of an introduction - It's a well-known custom firmware/Android distribution.
Some useful information for devices from China (SM-P583, SM-T585C, SM-P588C, and SM-T580 on the CHN CSC) - For unlocking the bootloader before installation, an app, "CROM Service", would need to be opened and the prompt from it accepted so that it can be unlocked, after enabling the "OEM unlock" setting in developer options. It should be available from the Galaxy Store, although I can't be 100% sure about it. In any case, an APK of it should be easy to find.
As was the case with LineageOS 18.1, I've taken over maintaining 19.1 for gtaxlwifi from @followmsi, and my 19.1 builds continue on from his 19.1 builds that were intended for use by users. To update from his builds, my builds can simply be installed on top of an existing install from his builds without doing anything further (or "dirty flashed").
For those running 18.1 or 17.1, upgrading to 19.1 is possible through the procedure I've explained before here and here (except with 19.1/Android 12 and 18.1 rather than 18.1/Android 11 and 17.1 for that second post). I highly suggest backing up any important data before trying to upgrade. In the unlikely case the upgrade fails, and it doesn't boot, data would need to be formatted.
For those who used WiFi-only variant builds on an LTE variant device, installation of a proper LTE variant build on top of an installation from a WiFi-only variant build is possible, except for a small issue you may encounter after doing so. See issue 3 in the "known workarounds and issues" section below for it.
LineageOS 19.1/Android 12 usability fixes
For those wanting to disable the widely disliked taskbar (the grey bar at the bottom with the 3 navigation buttons and shortcuts for apps docked at the launcher): Instructions for doing so are in the first section of my post here.
For enabling lockscreen rotation: Instructions for doing so are in my post here.
For those needing Google apps: Do not use heavy Google apps packages, as otherwise, you WILL have severe performance issues. Instead, use the most minimal variant of your chosen package. For example, for OpenGapps (no longer maintained officially, with no Android 12L packages, so use @ipdev's latest unofficial build available here), that is the pico variant, and for NikGapps (note that it now seems to more often be problematic, probably better using something else), that is the core variant.
Build downloads - All from 20230603 with security patch level 20230505
For gtaxlwifi: https://drive.google.com/file/d/15f1R3z-pbBTxhix8d_fBzwI1NOPHN6Bl/
For gtaxllte: https://drive.google.com/file/d/1Ba3whNROBXFn7vnpIHlWi9e9pkWR5BbA/
For gtanotexlwifi: https://drive.google.com/file/d/1MMhxvs1jNPHAgU5kDy4kaJ7AZ3MSXcLg/
For gtanotexllte: https://drive.google.com/file/d/1aDGexOX56dazYwAclICju977NAqYpAPH/
Note: If you have a revision 7 gtaxllte device (which are apparently exclusively for 2020 students in Egypt), for the current gtaxllte build to boot, the boot image here is required. It won't be needed for future builds.
For all other revisions, which are 99.9% of all devices (with the 7th revision having just that exclusive usage), the current gtaxllte build will work fine as-is.
Recoveries to use
Use my unofficial TWRP builds:
For gtaxlwifi: Image here, tar for Odin for AP slot is here.
For gtaxllte: Image here, tar for Odin here.
For gtanotexlwifi: Image here, tar for Odin here.
For gtanotexllte: Image here, tar for Odin here.
Folders for builds
Along with current builds, these contain text files with SHA256 checksums for builds, and folders containing few previous builds.
For gtaxlwifi: https://drive.google.com/drive/folders/1S3NRiTP2jr9gRtSMKoKoaoMu75g_FJM4
For gtaxllte: https://drive.google.com/drive/folders/1ZFkGkVkIohsNFDi0jNF2-Yhz7Sbg5GT4
For gtanotexlwifi: https://drive.google.com/drive/folders/11pcp9NZf0ovelvT7oxfhoem6-utpSao8
For gtanotexllte: https://drive.google.com/drive/folders/1AICJ1UcnZ5a-slcgd-iGQ9mpk9J8Evmd
Changelogs
Builds for 20230603:
Latest changes from LineageOS, including the 20230505 Android security updates.
Support for revision 7 gtaxllte devices, which were apparently exclusively for 2020 students in Egypt, has been added. (Note: Boot image here required for a change needed to boot on the 7th revision for the 20200603 build, the change will be included in all future builds making it unnecessary for them.)
Previous releases
Builds for 20230419:
Latest changes from LineageOS, including the 20230405 Android security updates.
Linaro's new SLSI BSP (Board Support Package, containing sources for HWC and some other stuff) sources are now used - Much more up-to-date than the previously used sources, and there's possibly a small improvement in performance.
The OMX hardware video decoder and encoder libs are now built from the new Linaro BSP sources - With that, playback of HEVC videos is fixed in Chrome and other Chromium-based browsers.
Some updates from the 4.9 Android common kernel as of March have been applied to the kernel.
The wireguard kernel module has been added back - I silently removed it in the previous builds since it was unusable due to a now fixed device lockup bug that caused almost total unresponsiveness after enabling a wireguard VPN.
Builds for 20230128:
Latest changes from LineageOS, including the 20230105 Android security updates.
[LTE variant-specific] Issues with mobile networking not working have been fixed.
[gtanotexllte-specific] Additional issues with bootlooping and rebooting during the boot animation have been fixed.
Open source aptX encoder libraries, from sources adapted from Qualcomm's recently upstreamed to AOSP open source code, are now used.
Builds for 20221231 and 20230101:
Latest changes from LineageOS, including the 20221205 Android security updates.
Some more miscellaneous cleanups have been done.
Initial builds for gtaxllte and gtanotexllte.
Many updates from the 4.9 Android common kernel have been applied to the kernel.
Builds for 20221127:
Latest changes from LineageOS, including the 20221105 Android security updates.
Builds for 20221020:
Latest changes from LineageOS, including the 20221005 Android security updates.
Performance of animations has been improved slightly further.
Configuration files for media codecs and profiles have been updated from Samsung's M105FDDS4CVG1 firmware, and audio codec support might be improved slightly (as the Codec 2.0 media codec framework has been fixed and is now used).
Some updates from the 4.9 Android common kernel have been applied to the kernel.
Builds for 20220929:
Latest changes from LineageOS, including the 20220905 Android security updates.
The torch has been fixed.
Performance of animations and responsiveness has been improved slightly.
Some updates from the 4.9 Android common kernel have been applied to the kernel.
[SM-P580/gtanotexlwifi only, already fixed in T580 builds long ago] An issue where the displays backlight would be turned off completely when setting very low brightnesses, causing nothing to be visible on the display (unless very faintly if you shine a torch or a different bright light source on it), has been fixed.
The WiFi drivers RX wakelock feature has been disabled - Heavy battery drain that occurred in sleep when connected to certain WiFi networks due to "qcom_rx_wakelock" wakelocks has been fixed.
Builds for 20220824:
Latest changes from LineageOS, including the 20220805 Android security updates, and a fix for "Intent Filter Verification Service" crashes that occurred in few/some cases with no Google apps or with MicroG.
Some things that appeared that are only relevant for devices with mobile networking (such as the baseband version and SIM status sections in About tablet in settings) no longer appear.
The ZRAM size has been increased to 2GiB, and the swappiness is now set to 100.
A higher frequency (1246MHz, was 902MHz previously) is now set for the interactive CPU governors "hispeed_freq" value - This improves responsiveness slightly.
The sepolicy containing device-specific SELinux rules has been improved slightly.
Yet more miscellaneous cleanups have been done.
Some updates from the 4.9 Android common kernel have been applied to the kernel.
Builds for 20220724:
Latest changes from LineageOS, including the 20220705 Android security updates.
Some updates from the 4.9 Android common kernel have been applied to the kernel.
Builds for 20220620:
Latest changes from LineageOS, including the 20220605 Android security updates.
Network traffic monitoring now works (as some changes reverting the removal of the old, non-eBPF, method of doing it that the old 3.18 kernel only supports have been applied, thanks to @rINanDO for them!).
One of Lineage's changes to the default keyboard, likely to be causing a problem where the keyboard appears full screen with no keys in very few cases, has been reverted.
Many updates from the 4.9 Android common kernel, and some from a few other sources, have been applied to the kernel.
The issue where trying to power off, or reboot to recovery or download mode, would sometimes cause a normal reboot has been fixed.
A small fix to the kernel has been applied that fixes occasional soft reboots, that were caused by a change I made a very long time ago that had only started causing such soft rebooting problems with Android 12.
Builds for 20220523:
Latest changes from LineageOS, including the 20220505 Android security updates and an option for disabling the taskbar.
The problem where enabling the "Enable on-screen nav bar" option at Settings -> System -> Buttons caused touchscreen input to be disabled has been fixed.
Native support for IPsec tunnels has been enabled.
Support for Vulkan compute is now declared.
A new custom version of the open source Samsung audio HAL from Lineage's android_hardware_samsung repository is now used, rather than the stock, heavily-patched, proprietary Samsung audio HAL, with some fixes for a problem that made it unusable before where occasionally, audio would get outputted from both the speakers and the headphone jack.
The playback and low-latency capture period sizes have been reduced to 128 in the open source audio HAL, which reduces audio latency.
Pro audio support is now declared, since with the reduced period sizes, as well as with the use of the open source audio HAL, round-trip audio latency has been reduced enough for it.
Many updates from the 4.9 Android common kernel have been applied to the kernel.
Several fixes to the Sony HID driver in the 4.9 Android common kernel have been ported over to the kernel - Sony DualShock 4 controllers should now work properly.
Initial builds for 20220416 (This changelog continues on from @followmsi's last 19.1 build that was intended for use by users):
Latest changes from LineageOS.
SELinux is now set to be enforcing after having addressed new SELinux denials with 12.
Assisted GPS has been fixed.
ADB is no longer enabled by default or on boot.
The tablet product characteristic has been added back after being mistakenly removed - Places where the device was referred to as a phone (such as the "About phone" section in settings) will now refer to it as a tablet again.
The Widevine DRM blobs have been updated to 1.4 blobs from the latest stock firmware for the Google Pixel 3a XL.
A new wcnss_filter binary built from sources is now used to properly fix an issue where Bluetooth couldn't be re-enabled after enabling and disabling it once, and the old workaround for it has been removed.
Some other miscellaneous cleanups have been done.
There are a few updates from the 4.9 Android common kernel and Samsung's A600FNXXU9CVB1 kernel sources to the kernel.
An issue where the displays backlight would be turned off completely when setting very low brightnesses, causing nothing to be visible on the display (unless very faintly if you shine a torch or a different bright light source on it), has been fixed.
Known issues and workarounds/fixes (if any)
Issue 1 - Squashed (rear) camera previews, and videos at some resolutions: 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: Use resolutions at which there are no issues with squashing from 16:9.
Issue 2 - LTE variants - In-call echo: There may be echoing that can be heard by the person you're calling while using speakers.
See my post here for more on this issue.
(Temporary) Issue 3 - APN issues on LTE variant devices - after installation of a proper LTE variant build on top of an installation previously from a WiFi-only build: On an LTE variant device, after installing a proper LTE variant build on top of an existing installation from a WiFi-only build, when going to APN settings, at Settings -> Network and Internet -> SIMs -> Access point names, an error is displayed that APN settings cannot be changed by the current user (or something similar).
Fix: Tap the 3-dot menu at the top right, and select "Reset to default", and then select the relevant APN.
(Minor cosmetic) Issue 4 - Incorrect model displayed on devices with region-specific model numbers
I'll take a look at fixing this issue up later on.
Issue 5 - LTE variants - Bluetooth calling doesn't work: There isn't any call audio over Bluetooth audio devices. Any call audio with a Bluetooth audio device connected will be routed to the built-in speakers.
Issue 6 - LTE variants - No VoLTE support: VoLTE currently can't work on any Samsung devices due to Samsung's proprietary implementation in stock firmwares not working on AOSP.
Something notable is that with Android 12, encrypted data can't be decrypted in TWRP recovery. That problem can only be fixed within TWRP, but with the fixes only being in Android 12L TWRP sources, which we can't build our TWRP builds from due to issues, it continues to exist.
To report further issues, get a log from logcat and dmesg. If you're unsure on how to get either, there's good documentation out there for how to do so.
Sources
A manifest containing all of the necessary repositories to make builds for all of the variants is in the repository here on branch lineage-19.1.
Thanks to:
@Valera1978 - for all of the previous work for the T580 and T585 long ago.
@followmsi - for fixes to various issues and other improvements, for useful information, and for working with me on much of this stuff.
Anyone who has previously tested anything new I've put up for testing, reported results, and provided information needed for me to get it working if it was necessary.
The Lineage team - for the Android distribution itself.
...and everyone else who has worked on anything that is in use.
TALUAtXDA said:
Changelogs:
Initial releases for 20210416 (This changelog continues on from @followmsi's last 19.1 build that was intended for use by users):
The tablet product characteristic has been added back after being mistakenly removed - Places where the device was referred to as a phone (such as the "About phone" section in settings) will now refer to it as a tablet again.
The Widevine DRM blobs have been updated to 1.4 blobs from the latest stock firmware for the Google Pixel 3a XL.
Click to expand...
Click to collapse
That's great news TALUtXDA! Congrats on 19.1!
I had been hoping for the Widevine L1 on 18.1. And I was also noticing the "About phone" thing, on 18.1
I guess those fixes were only possible on 19.1
Just curious, does 19.1 fix that crash when we click on settings from the quick pulldown?
Gorilla Daddy said:
That's great news TALUtXDA! Congrats on 19.1!
I had been hoping for the Widevine L1 on 18.1. And I was also noticing the "About phone" thing, on 18.1
I guess those fixes were only possible on 19.1
Just curious, does 19.1 fix that crash when we click on settings from the quick pulldown?
Click to expand...
Click to collapse
Thanks!
It isn't possible to have the L1 Widevine security level. It would be possible to get L1 to appear to work (meaning L1 is reported to be the security level), but it would actually just get dropped down to L3.
For that "About phone" thing, that small problem was just caused by a mistake I made. For 18.1, it only exists in my last builds since only those are affected by it. It'll be fixed in the same way I've fixed it in my new 19.1 builds in my next 18.1 builds.
Yes, the crashes that happened when tapping on the settings button or holding the quick settings tiles on the notifications pulldown once after boot in 18.1 no longer occur under 19.1.
TALUAtXDA said:
It isn't possible to have the L1 Widevine security level. It would be possible to get L1 to appear to work (meaning L1 is reported to be the security level), but it would actually just get dropped down to L3.
Click to expand...
Click to collapse
I think stock Android 6 on the tablet had Widevine L1. Didn't it? I don't know how it all works, but I do wonder what is missing. When you posted that you had used the Pixel 3a blobs, I had thought that was whatever blackbox did the widevine L1. I see I was wrong. I guess whatever blobs and whatnot from Android 6 aren't compatible with our LineageOS setups?
If you could explain a bit more of the Widevine internals as it relates to L1 on these tablets, just to cure my ignorance, I'd appreciate it. I've been wondering about it for a while. I can program in assembly language and C, so don't pull any punches.
This is great, thx so much!
One question for installation: you described how to switch from followmsi's 19.1 build to your's but if coming from your last 18.1 (!) build what steps are needed to upgrade to your 19.1 build?
Happy Easter!
I am new to these ROM but am looking for one that will run games better. I play Final Fantasy Brave Exvius and the game continues to need more power to run it. I have a Samsung Galaxy Tab A T580 and was wondering if this ROM will run the game faster? The only app I installed is the game. Besides that, I use Chrome for web browsing but nothing else. In the past, resetting the tablet to factory would help a little but not anymore. Will this help for what I am looking for? If not, I am open to all suggestions short of buying a new one at this time. Thanks
Good work. Upgrade from 18.1 worked flawlessly except for this that appeared and dont know how to remove it.
What is this bottom bar?
{
"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"
}
rapidm said:
Good work. Upgrade from 18.1 worked flawlessly except for this that appeared and dont know how to remove it.
What is this bottom bar?
View attachment 5590777
Click to expand...
Click to collapse
Hi rapidm, could you describe plz how you exactly updated from 18.1?
Uluru25 said:
Hi rapidm, could you describe plz how you exactly updated from 18.1?
Click to expand...
Click to collapse
See https://forum.xda-developers.com/t/...d-sm-p580-gtanotexlwifi.4274293/post-86744403
Uluru25 said:
Hi rapidm, could you describe plz how you exactly updated from 18.1?
Click to expand...
Click to collapse
I did those steps: https://forum.xda-developers.com/t/...rdroidandroid-12-1-v8-4.4190313/post-86754819 but with the lineage os 19 build.
Gorilla Daddy said:
I think stock Android 6 on the tablet had Widevine L1. Didn't it? I don't know how it all works, but I do wonder what is missing. When you posted that you had used the Pixel 3a blobs, I had thought that was whatever blackbox did the widevine L1. I see I was wrong. I guess whatever blobs and whatnot from Android 6 aren't compatible with our LineageOS setups?
If you could explain a bit more of the Widevine internals as it relates to L1 on these tablets, just to cure my ignorance, I'd appreciate it. I've been wondering about it for a while. I can program in assembly language and C, so don't pull any punches.
Click to expand...
Click to collapse
It would also work on the Android 8.1 stock firmware.
The Widevine DRM HAL, which is what I updated, is part of it. There's also a liboemcrypto.so blob, and Mobicore/the Trustonic TEE, along with relevant "trustlets" for it. WIth a working combination of the Widevine DRM HAL, liboemcrypto blob, Mobicore blobs, and "trustlets", it would be possible for the Widevine security level to be reported as L1. But, still, it would be dropped down to L3.
The commit message for the commit here removing the liboemcrypto blob and also replacing two other DRM-related blobs for Exynos 7580 devices describes, in actuality, Samsung as disabling L1 on devices that are modified in any way. Who knows how that happens or where along the line it does, seeing as all low-level device-specific stuff is, of course, undocumented.
I don't think it's worth continuing discussion on that topic. It's dead-end and I personally have a very poor understanding of it all, as I imagine almost everyone else does. There's no getting back the L1 security level.
rapidm said:
Good work. Upgrade from 18.1 worked flawlessly except for this that appeared and dont know how to remove it.
What is this bottom bar?
Click to expand...
Click to collapse
That's the new, pretty intrustive and seemingly also buggy, taskbar in Android 12L.
The only way to somewhat get rid of it is to switch to gesture navigation. Oddly, there's no three buttons for navigation on your taskbar there, so I'm not sure if you have it enabled already, and just need to hold down on it to switch to a navigation "pill".
That can most easily be done by running this command in an ADB shell or a shell with root access otherwise (run `su` in any other type of shell, such as one through an app, to get root access):
Code:
cmd overlay enable com.android.internal.systemui.navbar.gestural
With it, a small white pill, along with some space around it, replaces the taskbar for navigation. Holding it down would switch back to a taskbar, and holding it down again would switch back to that pill. Note that as it's gesture navigation, you'd have to get used to either using the gestures or ignoring that they're there, especially since they interfere with some gestures in some apps.
Unfortunately, at the moment, we don't have anything else besides switching to gesture navigation to get around it. This all came down from Google/AOSP (the Android Open Source Project) itself. Here's hoping Lineage makes improvements or improvements are made under AOSP to this navigation stuff.
TALUAtXDA said:
See https://forum.xda-developers.com/t/...d-sm-p580-gtanotexlwifi.4274293/post-86744403
Click to expand...
Click to collapse
Hi TALUaAtXDA, might be beneficial for other users to have this very valuable info already given or at least linked in your very first post, don't you think so?
Uluru25 said:
Hi TALUaAtXDA, might be beneficial for other users to have this very valuable info already given or at least linked in your very first post, don't you think so?
Click to expand...
Click to collapse
My Sam Galaxy Tab A T580 is totally stock and updated. Will this ROM work for me? Also, will it help with gaming? Sorry I am a newb when it comes to this stuff. Sorry, I am confused by all the bulds and if I need to install a certain one before I can install the newest build.
@ TALUAtXDA and @followmsi thank you for your hard work for this tablet, i hope lineage find a way to remove this nav bar, everything seems to work for the moment
rapidm said:
Good work. Upgrade from 18.1 worked flawlessly except for this that appeared and dont know how to remove it.
What is this bottom bar?
View attachment 5590777
Click to expand...
Click to collapse
This is a big problem for me too. I've already tried using the command with su in a terminal and it doesn't work at all.
charcutero said:
This is a big problem for me too. I've already tried using the command with su in a terminal and it doesn't work at all.
Click to expand...
Click to collapse
Long click makes it a line but if you click the hardware buttons then it returns to the default full form.
rapidm said:
Good work. Upgrade from 18.1 worked flawlessly except for this that appeared and dont know how to remove it.
What is this bottom bar?
View attachment 5590777
Click to expand...
Click to collapse
I guess that's the taskbar which was introduced in Android 12L. Android 12L is designed for foldables and devices with large screens, so with a taskbar, you could speed up multi-tasking.
I found a way to remove the taskbar. Go into Developer Options, go to Minimum Width, and set it to any value below 600 dp, which is the minimum value to trigger the taskbar. Please post the outcome.
SupremeKing5810 said:
I found a way to remove the taskbar. Go into Developer Options, go to Minimum Width, and set it to any value below 600 dp, which is the minimum value to trigger the taskbar. Please post the outcome.
Click to expand...
Click to collapse
400 dpi 640 dpi
It does not save any DPI data for me, it returns to 640.
Even if you hide the bar, it reappears randomly.
The ROM is going great, but android 12 is a bit cumbersome. Buttons and slide very large.