[ROM][UNOFFICIAL][11][EAS][SM-T820][SM-T825][2022-05-08] LineageOS 18.1 for Galaxy Tab S3

Search This thread
By:
Advanced…
Awesometic

Awesometic

Senior Member
Jul 30, 2017
152
391
Home, work, home, work, cafeteria, home, work...
Samsung Galaxy Note 5
Xiaomi Redmi Note 4
KeepingItCuttingEdge said:
I'm still getting the Google drive file from 11-30, not 12-3 when I click the OP link -- or does 11-30 include the new kernel you referred to in the 12.3.2021 update?

Is everyone using the 20211130 ROM who's posting about it?
Click to expand...
Click to collapse
Yeah, 20211130 is the latest version now. I'm sorry for the ambiguous titles.
Will change them to the same date. 😀
 
  • Like
Reactions: am2013 and KeepingItCuttingEdge
X

xpil

Senior Member
Nov 14, 2016
92
9
First of all I would like to thank Awesometic for the excellent job. I have installed the previous to the last rom and my t825 works continuously for 1 month without any problems at all. Two things I had to change were to follow a procedure I found on the internet for otg to work properly ,and a procedure I found (using magisk) to make the t825 pass safetynet tests. Now my tablet is certified and fully functional.

I need though your help PLEASE. I want to update the tablet with the latest ROM. The one with the new kernel. I saw that I have to wipe system and cashes. Do I have to reinstall and gapps because of this? Is the tablet going to be certified after the installation? Or I have to repeat the procedure to recertify t825?
Thanks in advance...
 
bmwdroid

bmwdroid

Senior Member
Mar 8, 2014
1,456
1
626
"I am a Berliner" JFK
Samsung Galaxy S4 Mini
Samsung Galaxy Note 10.1 (2014 Edition)
xpil said:
... saw that I have to wipe system and cashes. Do I have to reinstall and gapps because of this? Is the tablet going to be certified after the installation? Or I have to repeat the procedure to recertify t825?
Thanks in advance...
Click to expand...
Click to collapse
At least I did flash them together with the ROM.
You could try without of course.
I don't care about "safety net" so idk.
 
A

am2013

Member
Dec 27, 2012
30
4
@Awesometic : I still have the same issues with the secondary/non admin user as described in my post https://forum.xda-developers.com/t/...-18-1-for-galaxy-tab-s3.4293069/post-85588047

Will you be able to fix this issue somehow. It looks like a permission issue for non primary users as the system shows that there is unsufficient space. As a hint which may help to localize the issue. When trying to start amaze file manager as a secondary user it will instantly crash with a file I/O exception. Please have a look. I can provide additional information if needed.

BTW, with the last version the WIFI MAC was changed. Not sure if this is on purpose or not.
 
X

xpil

Senior Member
Nov 14, 2016
92
9
Awesometic, Could you please suggest how to flash your latest ROM over the previous one??
Thanks again for your dedication and the excellent job!
 
Awesometic

Awesometic

Senior Member
Jul 30, 2017
152
391
Home, work, home, work, cafeteria, home, work...
Samsung Galaxy Note 5
Xiaomi Redmi Note 4
am2013 said:
@Awesometic : I still have the same issues with the secondary/non admin user as described in my post https://forum.xda-developers.com/t/...-18-1-for-galaxy-tab-s3.4293069/post-85588047

Will you be able to fix this issue somehow. It looks like a permission issue for non primary users as the system shows that there is unsufficient space. As a hint which may help to localize the issue. When trying to start amaze file manager as a secondary user it will instantly crash with a file I/O exception. Please have a look. I can provide additional information if needed.

BTW, with the last version the WIFI MAC was changed. Not sure if this is on purpose or not.
Click to expand...
Click to collapse
Ah okay, will reproduce that issue on my device too.
But for now I'm focusing on the kernel upgrades for battery improvement and better UI experience. Through that work, I might fix the Android OS side issues too. So please test again later with the upcoming kernel versions. :)
 
Last edited:
Awesometic

Awesometic

Senior Member
Jul 30, 2017
152
391
Home, work, home, work, cafeteria, home, work...
Samsung Galaxy Note 5
Xiaomi Redmi Note 4
sebvalmont said:
Sorry but I could not find how to update in the post you sent neither in the posts close to it.

Is there some set of instructions? I really want to update mine.
Click to expand...
Click to collapse
xpil said:
Awesometic, Could you please suggest how to flash your latest ROM over the previous one??
Thanks again for your dedication and the excellent job!
Click to expand...
Click to collapse

Dirty flashing will work. This means, just flash the new version using TWRP, and wipe caches.
But moving to F2FS requires you to format the current data partition. So please be aware of that before continuing. Currently, F2FS is an option that has better I/O performance but a little bit unstable than EXT4, very relatively.

Quoted here what "dirty flashing" means from a Reddit post.
A "dirty flash" refers to the process of flashing a new version of your ROM over the top of the one you have, without using the "Wipe Data/Factory Reset" option in recovery. Even if you intend to dirty flash the update, you should always wipe cache and dalvik cache.

  1. Wipe Data/Factory Reset: This option erases all data on the device. Every application, and all data generated by those applications, will be erased. If you do not wipe data, all the data files generated by every app on the system will persist through an upgrade. This includes the data files generated by core system apps, like the phone dialer, the Android UI, its option menus and core features. Remember, everything you do on Android is an application that generates data! NOTE:The storage you see when you connect to USB will not be erased.
  2. Wipe Cache: Every application on the system, even those that run things like your UI and the options menus, generates cache files. These cache files are more or less unique to the current installation of Android you are using, and are generated dynamically. These cache files help Android load and run faster. When changing ROMs or updating to a new version of a ROM, you should always wipe the cache partition, or you're gonna have a bad time: Force closes, boot loops and sluggish performance are just some of the perils that await you.
  3. Wipe Dalvik Cache: Android executes programs inside of software system called the "Dalvik Virtual Machine." The DVM interprets and runs APK files for Android. Dalvik maintains its own cache to again improve performance for your device by offering faster app loading and execution. The Dalvik Cache is again unique to the current installation you are running, and it should always be wiped whether you're installing a new ROM or simply updating versions.
Click to expand...
Click to collapse
 
  • Like
Reactions: namitutonka
X

xpil

Senior Member
Nov 14, 2016
92
9
Awesometic said:
Dirty flashing will work. This means, just flash the new version using TWRP, and wipe caches.
But moving to F2FS requires you to format the current data partition. So please be aware of that before continuing. Currently, F2FS is an option that has better I/O performance but a little bit unstable than EXT4, very relatively.

Quoted here what "dirty flashing" means from a Reddit post.
Click to expand...
Click to collapse
Performed dirty flash but kept EXT4. Everything works fine till now.
Thank you very much for the perfect ROM and your help
 
UberMorgott

UberMorgott

New member
Dec 9, 2021
2
0
Great job. All 4 working speakers have brought life to this tablet.
Found something else that doesn't work:
The cover is a book. The screen does not go out and does not light up when opening and closing the lid.
 
Awesometic

Awesometic

Senior Member
Jul 30, 2017
152
391
Home, work, home, work, cafeteria, home, work...
Samsung Galaxy Note 5
Xiaomi Redmi Note 4
UberMorgott said:
Great job. All 4 working speakers have brought life to this tablet.
Found something else that doesn't work:
The cover is a book. The screen does not go out and does not light up when opening and closing the lid.
Click to expand...
Click to collapse
Yeah, while I was upgrading the kernel to merge the upstream patches seems like I broke that feature. I'm using a flip cover case too, so that is quite an annoying bug :confused:

I found which function handles that flip cover flips, and checked that function does listen to the status (opened and covered), but the screen is not actually responded by that function. I'd like to fix this issue too.
 
  • Like
Reactions: Anderleanderle
UberMorgott

UberMorgott

New member
Dec 9, 2021
2
0
Awesometic said:
Yeah, while I was upgrading the kernel to merge the upstream patches seems like I broke that feature. I'm using a flip cover case too, so that is quite an annoying bug :confused:

I found which function handles that flip cover flips, and checked that function does listen to the status (opened and covered), but the screen is not actually responded by that function. I'd like to fix this issue too.
Click to expand...
Click to collapse
Thank you for the answer, we are all following your progress!)
 
F

franzli

Senior Member
Mar 15, 2010
302
64
Hi, this sounds like a great ROM!

I've got one question regarding Wifi Display/Miracast. The changelog mentions Wifi Display was removed in v. 2021.8.13. Is this a temporary state of affairs or is it a general restriction (maybe due to Google pulling support for Miracast in stock Android)?
I'm asking because I rely on Miracast when using my tablet for teaching, so if this feature is permanently disabled, unfortunately I won't be able to use this ROM. But if there's a chance the feature comes back at some point, I'd love to try it out!

It's so annoying that Google decided to abandon Miracast claiming that "it's not widely used" and that one should use their stupid Chromecast instead, when the Chromecast clearly doesn't allow you to do what Miracast can do, namely connect to any Miracast enabled device (or use the Wireless Display dongle) and directly cast to it without the need for internet access. Sorry for ranting, but I just want preempt suggestions of Chromecast as an alternative - I got one of those and it doesn't work without connecting it to some sort of network first, which makes it largely useless in most mobile teaching environments. Using a phone as a hotspot is, to my mind, no alternative - why should I burn through battery (and data?) on an extra device when there should be no need for internet access in order to project local data to a local device in the first place? (Imagine an HDMI cable that only works as long as it can access the google servers :p )
 
Last edited:
You must log in or register to reply here.

Similar threads

ashyx
[RECOVERY][ROOT]TWRP 3.2.1-1 Samsung Galaxy Tab S3 SM-T820/T825
Replies
2K
Views
293K
E
echoxxzz
R
[ROM] SM-T820 TWEAKED....................[rom] sm-t820 tweaked
Replies
1K
Views
148K
lartomar2002
lartomar2002
V
[ROM][SM-T820][SM-T825][UNOFFICIAL] Lineage 17.1 | Android 10 Q | 20200211
Replies
259
Views
70K
Sage
Sage
V
[ROM][SM-T820][UNOFFICIAL] LineageOS 16.0 | Android 9.0 20191024
Replies
167
Views
41K
BenG7
BenG7
R
[ROM] SM-T825 TWEAKED.........................[rom] sm-t825 tweaked.
Replies
375
Views
51K
bozkurtum
bozkurtum

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 6
    Awesometic
    Awesometic
    Hello all,

    I updated LineageOS and HavocOS and uploaded them to the forum.
    In this update, besides the latest Android sources, I added some more fixes including the fingerprint recognition issue.

    Please check the update changelogs, thanks. :)
    View
    5
    Awesometic
    Awesometic
    bmwdroid said:
    @Awesometic thx for the info and your time for our device but even with the existing bugs I'll keep my T825 on your LOS19.1.
    Click to expand...
    Click to collapse

    I do have a plan to fix the major bugs on my LOS 19.1, I hope I can fix them soon. 😅
    View
    1
    bmwdroid
    bmwdroid
    Mortus06 said:
    ....... , when I tried to turn it on for the second time, it got stuck in a bootloop.
    P.S.: I can't access recovery
    Click to expand...
    Click to collapse
    Download mode still accessible?
    If yes it might be worth trying to just flash TWRP via Odin and, when rebooted to recovery, to make a clean flash (incl format data) from SD but this time with LOS19.1 which imo is much better anyway as being more stable.
    View
    1
    F
    fates13
    Awesometic said:
    Hello all,

    I updated LineageOS and HavocOS and uploaded them to the forum.
    In this update, besides the latest Android sources, I added some more fixes including the fingerprint recognition issue.

    Please check the update changelogs, thanks. :)
    Click to expand...
    Click to collapse
    Thanks for the update! My wifi tab s3 was having black screens after trying to unlock the screen from sleep on the previous version. Seems to be fixed now.
    View
  • 40
    Awesometic
    Awesometic
    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
    • SD Card
    • Power-off mode charging

    # What's not working
    • Fast charging
    • SELinux permissive
    • Hardware encryption
    • Please see the "Known issues" part of this post

    # Downloads

    ## LineageOS 18.1

    ## Google Apps

    ## TWRP Recovery

    # How to install
    1. Unlock the bootloader.
    2. Download TWRP and flash the recovery image via Odin.
    3. Download LineageOS 18.1 for Galaxy Tab S3.
      • Be aware of the board name.
    4. 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)
    5. Enter TWRP recovery.
      • The first boot to TWRP might be very slow because of the unmatched file systems.
    6. Format the whole system, data, cache partitions using the format menu.
      • You will type `yes` to do that.
    7. Flash the images.
      • If you're going to install GApps or something, you have to install the LineageOS first.
    8. Reboot the system.
    9. 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 won't work properly, it sometimes works but most of the time it won't
    • Sometimes turning on the flashlight via the quick panel doesn't work after using a camera app
    • Using a camera app may cause reducing the UI performance on a launcher app
    • The tablet rarely reboots with a GMS related error
    • Unlocking the lock screen can make tablets not usable sometimes (black screen)
    • Thank all of you for the feedback

    # Sources

    # 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.

    # Buy me a coffee

    # 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.
    View
    12
    Awesometic
    Awesometic
    Hi all,

    Finally, I can take a picture with my Tab S3 :)

    But still, there are some annoying bugs about the picture resolution, a flashlight behavior, ... but yeah it is usable when I take something using slightly lower resolution without the flashlight.

    Also, for now, both the LOS camera app and Snap camera are not working well while Open Camera and Google Camera seem to be working well.

    For now, the major problem is that if I use a flashlight in the camera app at least once, the overall GUI animations slow down even I closed the camera app.

    So, when I publish the camera fixed version, at least I will fix this most bothering thing even though I can't fix it all for the camera.
    View
    11
    Awesometic
    Awesometic
    ## Changelogs
    • 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.
    • 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
    View
    11
    Awesometic
    Awesometic
    Hello all.

    I uploaded the new version, including fixing the power-off mode charging.
    I'm using the LPM binary that is from Samsung for the power-off mode charging. When you plug in the charging cable while the tablet turns off, you can see the original charging screen you might see in the stock firmware. :)

    And I tried to fix the Bluetooth inputs and the OTG drives issues but I couldn't. I can reproduce these problems but I cannot find how to fix them for now. But I can confirm that the wired input devices are working such as a keyboard and a Playstation 4 controller.

    Please check out the first post of this thread. :)
    View
    11
    Awesometic
    Awesometic
    Great news here. The next release will include the fully-working quad-speakers. :D
    And I also have implemented the audio rotation codes for the screen rotation.

    Actually, I already have used it for about 3 days, and I think it looks working flawlessly.
    And, for the alternatives of the Dolby Atmos, I have tested with the Dolby Digital Plus module with Magisk and I can say that it is awesome. :cool:

    The new release will be uploaded before this weekend. :)
    View

New posts