Related
Hey Fellow XDA Developers.....Sorry I've to start this thread due to a reason that I've toggled everywhere in existing guides & Threads but I'm fed up that none of them is comprehensive or Correct...
OK I want some of the answers to (I guess extremely silly) questions
Q.1:: So I want to Develop a Custom Kernel on Backbone of Aurora and stock Linux kernel. Any possible way how can i extract, mod ;
edit and add and recompile it.... any specific tools,links.(already visited android authority)
Q.2::Can anyone tell me where i can find additional "".KO"" files(Kernel object libraries/kernel expander)
Q.3::Since most apps have a <uses sdk> so it means somewhere in /root directory the sdk is save right so latest android like
lollipop has new revision of sdk. is his possible to copy kitkat and lollipop sdk files to system from Android studio(I know this
is the worst joke or some sort of question asked by a fool but still out of curiosity of my never ending thirst of development)
Q.4::Nowadays I'm in a Quest to develop a Custom ROM since my phone is "NOT EVEN UNOFFICIALLY PORTED".I tried finding
my phones stock ROM[Panasonic P81][Xda Forum of P81 is totally Crap](Some stupid guy modded and made it worst than
sh!t).I heard Rumour that my clone "Cool pad 7320" has CM 6 or 11 Successfully installed/flashed but referring to the website
I tried and Bricked it. (Ironically I'm now using that modded coolpad ROM by Xdafirmware.com)
Q.5::Can U Tell if I can flash Stock Marshmallow Nexus image on my phone!!!!!!!![greatest question] I'M Die Hard Fan Of
Marshmallow And can Brick my phone infinite times getting it..
Q.6::What happens if I Replace my Stock kernel with original Linux (the pc one) (that im having.) . Will it work,add functionality ,or
brick it.
=======System Specs=======
Device Name : Panasonic P81
Boot loader : Unknown.(Same for all Panasonic I guess)
Processor : Mediatek MT6592 @ 1.7 Ghz 8 cores 32 bit archetecture
Kernel version: 3.4.39 [email protected] #1
Custom Build : 1012
Android Version: 4.2.2 jellybean apl 17
RAM: 1 GB
MODEL/BUILD ID: EB-90S055P81V1012
Runtime: Dalvik(libdvm.so) version 1.6.0
Motherboard: yulong92_wet_jb9
Radio: MOLY.WR8.W1315.MD.WG.MP.V19.P2
SELinuxermissive by default (stock)
CPU ABI- Armeabi
Features: swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva idivt
BOGO MIPS: 1685.91
Kernel Feature: Entropy & SMP PREEMPT
Toolchain: dcc version 4.6.x-google 20120106(pre release) (GCC)
**NEON SUPPORTED
==eMMC==
Name: K7XVMB
==sensors==
1: BOSCH BMA056 3-AXIS Accelerometer
2:ROHM RPR 410 PROXIMITY SENSOR
3:ROHM RPR 410 LIGHT SENSOR
==GRAPHICS==
VENDOR-ARM
GPU Renderer- MALI 450 MP
OPENGL: OpenGL ES @.0
ShaderpenGL ES GLSL ES 1.00
*****Eagerly Awaiting for answers . Please a positive cheer ups will be appreciated I'm noob here :angel::highfive: [Not that extreme I've enough xp regarding flash,boot loop,recovery,porting etc. ]*****
Most guides for this are found here,
http://forum.xda-developers.com/chef-central/android
If none there are helpful, then I'm at a loss for a suggestion. There's a lot of resources in that link. :good:
You are gonna run into a ton of issues. First off the chip that device uses never releases kernel source. So that will put a stop to your work real fast.
As for some of the other questions.
No you can't put a stock Linux kernel on the device. Kernels are made for each devices. They don't all work on every device.
zelendel said:
You are gonna run into a ton of issues. First off the chip that device uses never releases kernel source. So that will put a stop to your work real fast.
As for some of the other questions.
No you can't put a stock Linux kernel on the device. Kernels are made for each devices. They don't all work on every device.
Click to expand...
Click to collapse
Hey my kernel by default is stock aosp Linux version 2.4.39
Tanmoy Mitra said:
Hey my kernel by default is stock aosp Linux version 2.4.39
Click to expand...
Click to collapse
And the original revision of Linux I'm referring is the one created by Linus torlavads that is backbone of PC platform of Ubuntu, KDE and many other operating system. OK Aurora kernel is out of date and no support is available but I'm impressed by or rather moved by its spects and I feel that it is fantastic kernel to start with....... I just want to modify and continue from where he left a full stop to support. Many user still uses Aurora and there exist a hidden community about it.I WANT TO PROVIDE THE UPDATES AND SUPPORT OR WANTED TO DEVELOP A NEW KERNEL. OK on my 15 day research over kernel I found it is best kernel with a negligible cons and many features to opt within. Tell me which kernel can give me 16+ Governors and 9 scheduler and 6 TCP congestion algorithm to play with. With NEON and selinux support init.d and best battery backup among other kernel without even compromising a bit on graphics and rendering......Tell me
Tanmoy Mitra said:
And the original revision of Linux I'm referring is the one created by Linus torlavads that is backbone of PC platform of Ubuntu, KDE and many other operating system. OK Aurora kernel is out of date and no support is available but I'm impressed by or rather moved by its spects and I feel that it is fantastic kernel to start with....... I just want to modify and continue from where he left a full stop to support. Many user still uses Aurora and there exist a hidden community about it.I WANT TO PROVIDE THE UPDATES AND SUPPORT OR WANTED TO DEVELOP A NEW KERNEL. OK on my 15 day research over kernel I found it is best kernel with a negligible cons and many features to opt within. Tell me which kernel can give me 16+ Governors and 9 scheduler and 6 TCP congestion algorithm to play with. With NEON and selinux support init.d and best battery backup among other kernel without even compromising a bit on graphics and rendering......Tell me
Click to expand...
Click to collapse
I know what you are talking about and it won't work. Each device kernel is different from each other. Android is not the same as a desktop Linux set up. Also kernels differ from one pc to another.
As for those options you will have to add them yourself.
Again without the kernel source For that device being released you are out of luck.
zelendel said:
You are gonna run into a ton of issues. First off the chip that device uses never releases kernel source. So that will put a stop to your work real fast.
As for some of the other questions.
No you can't put a stock Linux kernel on the device. Kernels are made for each devices. They don't all work on every device.
Click to expand...
Click to collapse
Well I set to build it and yes I FOUND THE SOURCECODE FINALLY!!! although not for my board and device... While my device is Panasonic P81 and board is: yulong92_wet_jb9 the source was of Gionee Elife S5.5 same processor and features. But marked as board: vanzo92_wet_jb9
I don't think it will be issue, also found out that my device can support FDD LTE (VoLTE too) but needs a port from mt6595(helio x10)
[MT 6575 = LTE BASEBAND OF MT6590 + OCTA CORE architecture of MT6592 WHICH I USE]
So your help will be appreciated:good::laugh:
Sent from my Panasonic P81 using XDA Labs
Hi
Every time I try to upgrade to LineageOS 16 (Android 9), or any other android version above 7, these are the problems I keep having:
- Microphone from plugged in earphones or headphones does not work. (They work fine on stock android 7 and LightROM android 7 - it's not my hardware)
- Terrible feedback to person on the other end when in a call using speaker (The earphones mic never works, so speaker is the only option. Works fine on android 7 / LightROM)
- GPS usually does not work (always shows me somewhere in the arctic or under china, in an ocean) - I say usually because I haven't bothered testing - whenever I have the earphone problem, the GPS also does not work - but the headphone and speaker feedback thing is most important to me
What I've tried:
- Upgrading baseband/firmware version to latest
- Making sure it's not the hardware. It's not the hardware.
- Checking permissions. They're fine.
- No, I don't have Xposed installed, but when I do, nothing changes
I'll be unimaginably grateful to anyone that helps me solve this...
I've had similar problems even in ResurrectionRemix and LineageOS 15.1 - seems that I have similar problems any time I use a version different than android 7.
Everything else is great, but if the only way I can have a call is by holding the phone up to my ear all the time, no thanks...
bluetooth connections for output or input do not work either...
Here are my android settings currently on LineageOS 16:
Android version
9
LineageOS version
16.0-20190816-UNOFFICIAL-zerofltexx
LineageOS API level
llama (9)
Android security patch level
1 August 2019
Vendor security patch level
1 January 2019
Baseband version
G920FXXU6ESG2
Kernel version
3.10.108-Hyper-flx-gec59af9
#2 Fri Aug 16 03:57:52 UTC 2019
Build date
Fri Aug 16 17:52:49 UTC 2019
Build number
zerofltexx-userdebug 9 PQ3A.
190801.002 eng.enes_a.
20190816.174418 test-keys
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
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this ROM.
Try this build at your own risk. It's likely to have bugs and is EXPERIMENTAL as it is a work in progress. It boots and seems to work fine on my SM-T350, but I have only tested it for 24 hours. Problems will likley surface later?
BACKUP YOUR FILES and have a copy of your working image BEFORE trying my build.
What works.
1. bluetooth
2. wifi
3. brightness
4. external audio
5. GPS
6. audio through headphone jack
7. Google play store - use pico apps
8. flip flap smart cover
9. audio over bluetooth
Note: first initial boot takes a bit longer, be patient.
Known problems.
1. Home screen text may look fuzzy.
Text on home screen looks funny/fuzzy. This only seems to affect the home screen and nowhere else. I have seen the same problem on the SM-T350, SM-T560NU, SM-P550 and Nexus 7 2013.
Problem is with stock trebuchet launcher and/or its fonts. I tried rootless pixel launcher from fdroid as a quick and simple test and see no problems with home screen text. Rootless pixel uses a different font though. A future LineageOS update could resolve the problem?
Rootless Pixel Launcher | F-Droid - Free and Open Source Android App Repository
F-Droid is an installable catalogue of FOSS (Free and Open Source Software) applications for the Android platform. The client makes it easy to browse, install, and keep track of updates on your device.
f-droid.org
OR you can use nubianprince's crdroid 10.0 build for this tablet. He used his 9.0 repos and has no problems with fuzzy fonts/text. See
[ROM][SM-T350][UNOFFICIAL][crDroidAndroid-10.0][v6.17][ANDROID 10] Galaxy Tab A 8.0
Finally this thread is back :)
forum.xda-developers.com
OR you can use a fairly recent 16.0 build which doesn't have the problem.
2. The stock Jelly browser crashes a lot. Use a different browser. There's lots of better options that are more stable and reliable than the built in Jelly browser.
3. FM Radio is not support since this device doesn't have the LTE functionality.
4. Stock camera does not take picture on front facing camera. Use open camera instead. I don't know when stock camera was broken, but when I tested the March 7, 2021 build, it doesn't work.
Open Camera | F-Droid - Free and Open Source Android App Repository
Camera App
f-droid.org
5. BOE panel
For people who get black or blank screens when trying to flash TWRP 3.3.1 or LineageOS or crDroid SM-T350 roms, it's likely you have a BOE sourced panel.
Code:
adb root
adb shell cat /proc/cmdline
The very last parameter will be mdss_mdp.panel. If you see BOE anywhere in that string, then you have a BOE panel. For example,
mdss_mdp.panel=1:dsi:0:ss_dsi_panel_S6D7AA0_LSL080AL03_BOE_WXGA:1:none
There is a fix as documented at
[ROM][SM-T350][UNOFFICIAL][crDroidAndroid-10.0][v6.17][ANDROID 10] Galaxy Tab A 8.0
Finally this thread is back :)
forum.xda-developers.com
Thanks/Credits
Thanks to @nubianprince and @lividhen99 for ideas and suggestions on getting this build to work. I used one of nubianprince's repos for this build.
FAQ - I spent hundreds of hours building this rom. The least you can do is spend a few minutes reading everything before posting.
Q1) Does the build work on xyz?
A1) I have no idea. I only have the SM-T350. You can try it on variations, but don't be surprised if you get bootloop or bricked hardware. In addition, I won't build it for the 355 (LTE) version.
Q2) Application xyz doesnt' work. Can you fix it?
A2) I only fix what I use. If you use app xyz and it doesn't work, then try 16.0 or going back to the last rom that worked for you.
Q3) My tablet hangs or crashes with 17.1. This build is slow and buggy. Can you fix it?
A3) Go back to the last working stable rom for you. 17.1 is a work in progress and will have bugs and frequent changes.
Q4) Do you plan to update the rom?
A4) Yes as long as I have high speed Internet, I wil try to release the rom monthly to incorporate the security patches.
Q5) What TWRP should I use?
A6) TWRP 3.3.1 or 3.5.0.9. Get it from
https://forum.xda-developers.com/galaxy-tab-a/development/rom-galaxy-tab-8-0-t4158163
Q6) What is the difference between this rom and crdroid?
A6) Use this rom, crdriod or stock. It's not a popularity contest, so use whatever fits your needs. I only offer this as an option for those who want or need a new rom. Most of the code is the same between this rom and crdroid, however, the way we implemented the fixes might be slightly different. In addition, if there is a bug in this rom, it may not be in crdroid due to coding differences and how it's fixed.
Q7) Can I turn off the on screen navigation keys?
A7) To turn off on screen navigation, go to settings, system, advanced, gestures, system navigation, gesture navigation.
Q8) Can I build this rom? Where are the source and kernel source files?
A8) Yes. I have uploaded the repo diff and roomservice.xml file. The kernel source files are at
Samsung MSM8916 Devices
Samsung MSM8916 Devices has 68 repositories available. Follow their code on GitHub.
github.com
The repo diff is what I changed compared to "stock" msm8916 code. The majority of the repo diff is because there's a bug in 17.1 WiredAccessoryManager.java and I reverted back to the 16.0 code. The bug prevents audio through the headphone jack. See
https://forum.xda-developers.com/showpost.php?p=83445681&postcount=13
Q9) Where can I download this rom?
A9) You can find the 2020 17.1 and 16.0 builds at
Downloads for : Samsung Galaxy Tab A 8.0 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I'm moving to sourceforge for all 2021 uploads. The main reason is that I would like to see the stats of where this rom is being downloaded from worldwide. All 2020 builds will remain on androidfilehost.
2021 builds found at
retiredtab - Browse /SM-T350/17.1 at SourceForge.net
sourceforge.net
TODO
1. document and upload long list of fixes you need to build 17.1 if you want on your own.Done.
2. mirror nubianprince's repo in case it gets deleted.Done.
3. upload some files, fixes and documentation to github for future.Done.
Dec 13, 2021 release notes
1. Dec 5 security patches as per https://review.lineageos.org/q/topic:Q_asb_2021-12
2. Whatever LiineageOS changed since last November release (about 4,400 files had to be recompiled).
Nov 8, 2021 release notes
1. Nov 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/318647
2. Whatever LiineageOS changed since last October release (about 5,100 files had to be recompiled).
Oct 10, 2021 release notes
1. Oct 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/317410
2. Whatever LiineageOS changed since last Sept release (about 4,700 files had to be recompiled).
Sept 17, 2021 release notes
1. Sept 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/316083
2. Whatever LiineageOS changed since last August release (about 49,500 files had to be recompiled).
Aug 7, 2021 release notes
1. August 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/314572
2. Whatever LiineageOS changed since last July release (about 4500 files had to be recompiled).
July 12, 2021 release notes
1. July 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/313448
2. Whatever LiineageOS changed since last June release (about 4500 files had to be recompiled).
June 15, 2021 release notes
1. June 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/312240
2. Whatever LiineageOS changed since last May release (about 5400 files had to be recompiled).
May 10, 2021 release notes
1. May 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/309564
2. Whatever LiineageOS changed since last April release.
April 12, 2021 release notes
1. April 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/307454
2. Whatever LiineageOS changed since last March release. Nearly 59,000 out of the 70,000 files had to be recompiled due to the last set of changes.
Release notes for March 7, 2021
1. Mar 5 security patches.
2. Whatever LiineageOS changed since last February release.
3. Stock camera does not save picture on front facing camera. Use open camera instead. I don't know when stock camera was broken, but when I tested the March 7, 2021 build, it doesn't work. I never use the camera or video recording on the tablets.
Release notes for Feb 10, 2021
1. Feb 5 security patches.
2. fixed audio over bluetooth. Huge thanks to @nubianprince for helping with suggestions and his repos. The problem was that some of the audio xml files weren't being copied over in 17.1 because of some directory changes to hardware/qcom.
3. Whatever LineageOS changed since last Jan 2021 update.
Release notes for Jan 14, 2021
1. Jan 5 security patches.
2. Changed some error messages to verbose to stop spamming log files.
3. Whatever LineageOS changed since last Dec 2020 update.
4. For some reason after flashing the rom, TWRP 3.3.1 now says "unable to mount storage". I had never seen that before. Nevertheless, if you reboot, the rom will work fine. I test all my builds before uploading.
Release notes for Dec 14, 2020
1. Dec 5 security patches.
2. Changed some error messages to verbose to stop spamming log files.
3. Whatever LineageOS changed since last Nov update.
4. Add timekeep functionality since SM-T350 has no real time clock. This allows the tablet to keep time when not used with a NTP (network time protocol) server. It works in Android OS and TWRP.
Nov 8 release
- Nov 5 security patches
Oct 8 release
- Oct 5 security patches
Sept 13 initial release
- Sept 5 security patches
- initial release for testing and help fixing bugs
- CPU and GPU overclocked to 1.6Ghz and 650 respectively - built into 17.1 kernel code
- based on stock github MSM8916 T350 code with a LOT of bug fixes and using one of nubianprince's repos
Oct 8 build released. See post #4 for changes.
I set the time to Oct 18 but it was changed to Jan 18 after reboot, then October 9. I remember that crdroid have the same issue.
See this logcat:
Code:
01-18 08:52:10.608 680 680 I SystemServer: StartAlarmManagerService
01-18 08:52:10.611 680 680 D AlarmManagerService: Kernel timezone updated to -480 minutes west of GMT
01-18 08:52:10.611 680 680 I AlarmManager: Current time only 1471930611, advancing to build time 1602188073000
01-18 08:52:10.611 680 680 D AlarmManagerService: Setting time of day to sec=1602188073
10-09 04:14:33.001 680 680 W AlarmManagerService: Unable to set rtc to 1602188073: Invalid argument
10-09 04:14:33.006 680 680 D SystemServerTiming: StartAlarmManagerService took to complete: 10ms
Backlight problem is still in my BOE device. I don’t know which logs are necessary, so I kept most of them. The logs about BOEpanel of crdroid are same with Los, but may be different in other places.
Hope it could be solved.
Which TWRP image are you using? I've seen a couple different ones, but since there's no official support over at http://twrp.me/ I'd prefer to use the same one you're using to test this ROM installation...
Hexrotor said:
The logs about BOEpanel of crdroid are same with Los, but may be different in other places.
Click to expand...
Click to collapse
I'll take a look, but right now I have a big project that I need to get finished by mid November so my time for building and troubleshooting roms is limited right now.
reukiodo said:
Which TWRP image are you using?
Click to expand...
Click to collapse
TWRP 3.3.1
Hexrotor said:
The logs about BOEpanel of crdroid are same with Los, but may be different in other places.
Click to expand...
Click to collapse
These messages
D modemanager: Panel Name: S6D7AA0_LSL080AL03_BOE_wxga_video_mode_dsi_panel
E modemanager: readXMLOp:Couldn't open OEM XML file!
E modemanager: retrieveMode: Failed to enumerate modes
E modemanager: instantiateModeMgr: Failed to update default cache!
E modemanager: readXMLOp:Couldn't open OEM XML file!
E modemanager: retrieveMode: Failed to enumerate modes
E modemanager: in applyDefaultMode fail to retrieve default mode!
I modemanager: in applyDefaultMode ret = 0 mCurMode = -1
are from the proprietary module (which is why I couldn't find them in the AOSP code)
system/vendor/lib/libmm-qdcm.so
If you search for those keywords above, they all appear in this module.
At this time, I have no idea what the libmm-qdcm.so does and how it controls the backlight, if at all.
can someone provide link for twrp 3.3.1 for t350? i just can't find it.
spiramedia said:
can someone provide link for twrp 3.3.1 for t350? i just can't find it.
Click to expand...
Click to collapse
From
https://forum.xda-developers.com/galaxy-tab-a/development/rom-galaxy-tab-8-0-t4158163
TWRP 3.3.1 is at
https://drive.google.com/file/d/14T99LQaKtEhGeglFxrUm0kMRw_RKopP5/view
me t350 just shut's down on his own. clean install.
spiramedia said:
me t350 just shut's down on his own. clean install.
Click to expand...
Click to collapse
Works fine for me and others.
@spiramedia Maybe your device is using BOE panel, try to Illuminate the screen with a flashlight.
Hexrotor said:
@spiramedia Maybe your device is using BOE panel, try to Illuminate the screen with a flashlight.
Click to expand...
Click to collapse
mine is BOE. But i have no problem with this. The tablet just shuts down when using it. Maybe it overheats.
spiramedia said:
mine is BOE. But i have no problem with this. The tablet just shuts down when using it. Maybe it overheats.
Click to expand...
Click to collapse
@spiramedia, when asking for help, it helps us if you provide maximum information. For example,
1) What are you running when the tablet shuts down? High performance gaming? Watching youtube?
2) How long does the tablet run before shutting down?
3) Maybe your battery is really old and weak especially if you used it daily for 5 years?
4) If you think it overheats, you can download several CPU apps that tell you the temperature of the CPU like
https://f-droid.org/en/packages/com.kgurgul.cpuinfo/
5) If the battery is old and weak, does it shutdown when you have the AC microusb adapter plugged in all the time?
6) When it shuts down, what is the battery percentage at?
7) Is your battery guage calibrated properly? If it says 30%, maybe it's really 0% and you have to discharge/recharge 2 or 3 times to recalibrate?
As you can see, I asked a lot of questions. The more info you can give, the better.
PS. If you have a BOE panel and backlight works, then I have no idea why my rom works with yours and not Hexrotor.
Hexrotor said:
I set the time to Oct 18 but it was changed to Jan 18 after reboot, then October 9. I remember that crdroid have the same issue.
Click to expand...
Click to collapse
@Hexrotor, does this happen if you date and time setup to "use network provided time".
If I turn "use network provided time" off, then yes, the tablet doesn't keep time properly. I think it's due to the Qualcomm RTC being read only? Searching the Internet, a possible fix might be
https://github.com/LineageOS/android_hardware_sony_timekeep
I might try incorporating that into the next rom build which will likely be sometime mid Nov when the next security patches are released.
I think it's defaulting to Oct 9 because the build date is Oct 8, but in your timezone, it might be Oct 9.
Hexrotor said:
Backlight problem is still in my BOE device. I don’t know which logs are necessary, so I kept most of them.
Click to expand...
Click to collapse
The error messages for the BOE panel are just before the system stops the boot animation and gives the 3 dots and says LineageOS. I find that to be confusing because I would think the kernel would enable BOE backlight at the very beginning so you can see what is on the display. It makes no sense to have the backlight completely dark and then enable it just before the 3 dots that says LineageOS.
And if spiramedia's BOE backlight works with my rom, then I don't know why it doesn't work with yours. Maybe there is something persistent in one of the persist partitions where a prop is set?
Hexrotor said:
Backlight problem is still in my BOE device.
Click to expand...
Click to collapse
@Hexrotor, you didn't specify in this thread or the original crdroid thread whether you tried downgrading the stock to marshmellow and then try crDroid 10 or LineageOS 17.1.
Apparently, it fixes the no backlight for some people? See
https://forum.xda-developers.com/showpost.php?p=83488241&postcount=41
It's possible the marshmallow firmware has something coded into the file system partitions that fixes the BOE? Maybe someting in the aboot partition?
Let me know if you have tried downgrading or not as per above.
retiredtab said:
Apparently, it fixes the no backlight for some people? See
https://forum.xda-developers.com/showpost.php?p=83488241&postcount=41
It's possible the marshmallow firmware has something coded into the file system partitions that fixes the BOE? Maybe someting in the aboot partition?
Let me know if you have tried downgrading or not as per above.
Click to expand...
Click to collapse
Nope, I tried this way but no help. I flashed marshmallow firmware then Crdroid6.9 without clean, it was no display but heated up at boot. I waited for about 10min but it didn't boot complete. Edit: I tried again just now, it booted successfully but still no backlight. Now I'm using official marshmallow.
I don't know why this ROM works with spiramedia's BOE device. I have some friends who have T350/P350 BOE devices and all they have backlight problem with 3-part ROMs, that’s why I am sure that the backlight problem is related to BOE.
For Los 17 and Crdroid, my device has no backlight after the "Samsung Galaxy Tab A", but official marshmallow works fine.
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.