[ROM][SM-T510][UNOFFICIAL] LineageOS 17.1 for Galaxy Tab A 10.1 (2019)

Search This thread

Magendanz

Senior Member
  • Mar 25, 2008
    782
    736
    Issaquah, WA
    www.Vote4Chad.com
    640px-Lineage_OS_Logo.png

    In the spirit of moving custom ROM development along for the 2019 Galaxy Tab A 10.1 [SM-T510], here's a build of LineageOS 17.1 I just created based on the latest OEM stock firmware and @AndyYan's latest LineageOS 17.1 GSI. It's very much a work in progress, but it should hopefully help blaze the trail for even more custom ROMs for this tablet.

    Notes:
    • The current process requires you to reset to factory defaults to remove file-based encryption. Remember to backup your data!
    • Custom kernels are specific to OEM releases, and this one is based on the latest Android 10 release (T510XXU4BUA1).
    • Stock recovery will be replaced with my latest TWRP build for the SM-T510.
    • This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.

    Not working:
    • Support for file-based encryption

    Downloads:
    Build archives:
    Change Log:
    20210526:
    • Based on the latest build of LineageOS 17.1 GSI (20210512) with May 2021 Security Patch.
    • Updated to the latest Android 10 OEM kernel and vendor partition (T510XXU4BUA1).
    20201121:
    • Based on the latest build of LineageOS 17.1 GSI (20201114) with November 2020 Security Patch.
    • Updated to the new Android 10 OEM kernel and vendor partition (T510XXU3BTH4).
    20200812:
    • Based on the latest build of LineageOS 17.1 GSI (20200808) with August 2020 Security Patch.
    • Updated to the latest Android 10 OEM kernel and vendor partition (T510XXU3BTFN).
    20200713:
    • Based on the latest build of LineageOS 17.1 GSI (20200713) with July 2020 Security Patch.
    • Updated to the OEM May 2020 Security Update (T510XXS3ATE3) kernel and vendor partition.
    20200413:
    • Fixed Double Tap to Wake feature (enabled in Phh Treble Settings).
    • Fixed crash on first two attempts to launch Phh Treble Settings.
    • Based on the latest build of LineageOS 17.1 GSI (20200413).
    • Updated to the OEM T510XXS3ATB4 kernel and vendor partition.
    20200321:
    • Switched to latest stable version of ext2simg command for sparse image conversion.
    20200314:
    • Now based on the latest build of LineageOS 17.1 GSI (20200309).
    • Fixed potential image corruption issue from outdated img2simg command.
    20200308:
    • Charging after full shutdown will no longer hang during level-of-charge animation.
    20200301:

    Instructions:
    From OEM stock firmware:
    • Unlock bootloader
    • Hold Vol Up & Vol Down buttons during restart to enter Download mode
    • Install custom ROM tarball (.tar.md5 file) to AP with Odin
    • If TWRP launches, factory reset with Wipe->Format Data and reboot to system. (Not necessary for incremental upgrades.)
    From existing TWRP install:
    • Hold Power & Vol Up during restart to enter TWRP recovery
    • Tap Install, Install Image, select your update (.img file), and then swipe to install
    • Factory reset with Wipe->Format Data. (Not necessary for incremental upgrades.)
    • Reboot to system

    Source:

    Donations:
    • Your support is always appreciated! Just click here.
    • I'm leveraging a ton of work done by @AndyYan and @phhusson for Treble GSIs, so please show them some love here and here!
     
    Last edited:

    andreasoz

    Senior Member
    Mar 29, 2011
    53
    7
    When I try to installing gapps in twrp, twrp crashes and reboots. Using open gapps arm pico. Is there a way to install google apps on this rom?
     

    jaladhjin

    Senior Member
    Jul 13, 2013
    860
    69
    Instructions:
    From OEM stock firmware:
    • Unlock bootloader
    • Hold Vol Up & Vol Down buttons during restart to enter Download mode
    • Install custom ROM tarball (.tar.md5 file) to AP with Odin
    • When TWRP launches, factory reset with Wipe->Format Data. (Not necessary for incremental upgrades.)
    • Reboot to system
    Hiya :)


    Just got this device today.. pretty stoked to get it rooted & Lineage going.. thanks for your projects & info :)


    I'm curious do I need to change any of the Options tab in Odin ?


    Auto Reboot off for example ?


    Auto Reboot & F. Reset Time are checked by default none of the others are.


    At this point in this device's progress assuming I unlocked correctly & get into Download mode.. flash with Odin successfully I should just Auto Reboot right into TWRP & can go from there ?


    NoKnox is a thing of the past ?


    What about Multi-disabler ?


    If I install Magisk & plan to how do I ensure I don't "boot outside Magisk" I keep hearing people say.. where Vaultkeeper & similar things may become problematic or so I've read.


    Someone did offer some advice on not booting outside Magisk a few weeks ago I'm going to go find their message too but yeah I've read a lot of threads here & it seems like since certain packages & older methods like patching TWRP with Magisk are things of the past.. I just want to confirm what all else is :)


    is charging past 80% an issue at all with this ROM ?


    That's one thing I see people mention about custom kernels is they fix that.. well that & EX or Franco would be rad if they exist for this device & rom :)


    /salute
     

    Magendanz

    Senior Member
  • Mar 25, 2008
    782
    736
    Issaquah, WA
    www.Vote4Chad.com
    I'm curious do I need to change any of the Options tab in Odin ? Auto Reboot off for example ?
    Nope.

    NoKnox is a thing of the past ?
    Yep.

    What about Multi-disabler ?
    You still need to run Multi-disabler if you're installing TWRP, but it's baked into this custom ROM.

    is charging past 80% an issue at all with this ROM ?
    No longer an issue with this custom kernel.

    If I install Magisk...
    I don't use Magisk, and so I'm really not the person to ask. Note, however, that custom kernels in boot and recovery partitions are slightly different wrt MTP. Boot kernel uses Google MTP and recovery one uses Samsung MTP to maintain compatibility with OEM system if patched with Magisk.
     
    • Like
    Reactions: jaladhjin

    betacrypt

    Senior Member
    Jan 17, 2018
    289
    141
    Thanks for sharing this and great job! Got it up and running smoothly with gapps and magisk pretty easily.

    Haven't noticed any major issues other than that my SD card can't be read. It keeps showing the notification "Issue with SD Card - Tap to fix". I'm able to format the card successfully but the error returns the sd card isn't readable. Tried it with two different brands and getting the same issue.

    When I try to installing gapps in twrp, twrp crashes and reboots. Using open gapps arm pico. Is there a way to install google apps on this rom?

    OpenGapps won't work. I tried and a few and managed to get it working with BiTGApps for Android 10. You can get it here:
     
    Last edited:

    Warrenchild

    Member
    May 26, 2011
    37
    1
    I successfully installed lineage, but then I had to go back to stock. now when I try to install it again, I am only getting a error; "only official released binaries are allowed to be flashed(BOOT)"

    I cannot get back into lineage :( any advice?

    I used odin and flased the BL AP and CSC nothing is changing, wont even let me install twrp any more
     
    Last edited:

    lewmur

    Senior Member
    Apr 30, 2011
    1,764
    377
    I successfully installed lineage, but then I had to go back to stock. now when I try to install it again, I am only getting a error; "only official released binaries are allowed to be flashed(BOOT)"

    I cannot get back into lineage :( any advice?

    I used odin and flased the BL AP and CSC nothing is changing, wont even let me install twrp any more
    Did you re-enable Developer mode and OEM?
     
    Last edited:

    Warrenchild

    Member
    May 26, 2011
    37
    1
    Did you re-enable Developer mode and OEM?

    it was never locked again to being with. the option was greyed out saying it was already unlocked. but I did relock it then unlock it. no avail. is there a timer or something with these tablets if you mess up?

    I even downgraded to sk1 and then let it do a OTA update while locked
     

    lewmur

    Senior Member
    Apr 30, 2011
    1,764
    377
    it was never locked again to being with. the option was greyed out saying it was already unlocked. but I did relock it then unlock it. no avail. is there a timer or something with these tablets if you mess up?

    I even downgraded to sk1 and then let it do a OTA update while locked
    I'm confused by your terminology. The bootloader is locked or unlocked. Developer mode and OEM are enabled or disabled. I'm assuming you are referering to OEM but I'm not certain. Normally when coming from stock, you enable Developer and OEM and then unlock the bootloader. That will also cause a "factory reset". You then need to reboot and once again enable Developer mode. OEM will normally still be enabled and grayed out. Then you can start the Odin flashing. Also, you shouldn't let it do the OTA because the TWRP needs to match SK1.

    edit: The original instruction are a little confusing. They tell you that after each step you have to boot and enable Dev mode in order to chech OEM enable. The real reason is that you have to enable Dev mode in order to flash anything but stock. Without it enabled, you get the message in red saying that only original firmware can be installed.
     
    Last edited:

    Warrenchild

    Member
    May 26, 2011
    37
    1
    I'm confused by your terminology. The bootloader is locked or unlocked. Developer mode and OEM are enabled or disabled. I'm assuming you are referering to OEM but I'm not certain. Normally when coming from stock, you enable Developer and OEM and then unlock the bootloader. That will also cause a "factory reset". You then need to reboot and once again enable Developer mode. OEM will normally still be enabled and grayed out. Then you can start the Odin flashing. Also, you shouldn't let it do the OTA because the TWRP needs to match SK1.

    I already successfully installed lineage. I was doing it for a business who needs to have the tablet rooted, but the program they needed was finiky with the custom rom, so I tried to go back to factory.

    Where I think I messed up is I flashed all the BL, AP, and CSC, from the stock firmware. how ever I wanted to throw lineage on to test and now when I try to flash lineage again it gives me an error on the tablet.
    Error : "only official released binaries are allowed to be flashed(BOOT)"
    and the flash stalls out on odin.

    So i checked to see if it was boot unlocked still it was. so I reverted to sk1 (my tablet was bought from the store yesterday with sk5) and I let the tablet OTA update, and tried the process again to no avail.
     

    lewmur

    Senior Member
    Apr 30, 2011
    1,764
    377
    I already successfully installed lineage. I was doing it for a business who needs to have the tablet rooted, but the program they needed was finiky with the custom rom, so I tried to go back to factory.

    Where I think I messed up is I flashed all the BL, AP, and CSC, from the stock firmware. how ever I wanted to throw lineage on to test and now when I try to flash lineage again it gives me an error on the tablet.
    Error : "only official released binaries are allowed to be flashed(BOOT)"
    and the flash stalls out on odin.

    So i checked to see if it was boot unlocked still it was. so I reverted to sk1 (my tablet was bought from the store yesterday with sk5) and I let the tablet OTA update, and tried the process again to no avail.
    Did you read my "edit" where I said that was caused by not having enable Developer mode?
     

    [email protected]

    Senior Member
    Nov 10, 2011
    235
    156
    Ulm
    installing
    BiTGApps-arm-10.0.0-R1_signed
    BiTGApps-arm-10.0.0-v0.2_signed
    open_gapps-arm-10.0-pico-20200219
    open_gapps-arm-10.0-nano-20200305

    with twrp will force reboot while installing

    what maybe not work is miracast/widi. i can't find my tv with my tab.
    phh-treble entry in settings does nothing / does not open.
    (both last points also not work with your [ROM][10.0][UNOFFICIAL] Nexus Stock for 2019 Galaxy Tab A 10.1 [SM-T510])
     

    lewmur

    Senior Member
    Apr 30, 2011
    1,764
    377
    installing
    BiTGApps-arm-10.0.0-R1_signed
    BiTGApps-arm-10.0.0-v0.2_signed
    open_gapps-arm-10.0-pico-20200219
    open_gapps-arm-10.0-nano-20200305

    with twrp will force reboot while installing

    what maybe not work is miracast/widi. i can't find my tv with my tab.
    phh-treble entry in settings does nothing / does not open.
    (both last points also not work with your [ROM][10.0][UNOFFICIAL] Nexus Stock for 2019 Galaxy Tab A 10.1 [SM-T510])
    Miracast is no longer supported in Android 9 or 10. It isn't just this ROM. Chromecast is still supported but not miracast.
     

    lewmur

    Senior Member
    Apr 30, 2011
    1,764
    377
    my mi a1 with stock pie and the t510 stock rom still can use it
    Maybe so. But it isn't officialy supported, so if it doesn't work, it doesn't work. I tried it with several apps on several ROMs and could only get it work on my T580 by reverting to an Android 8. Every thing I tried in Pie either froze or caused the tablet to reboot.
     

    Magendanz

    Senior Member
  • Mar 25, 2008
    782
    736
    Issaquah, WA
    www.Vote4Chad.com
    it was never locked again to being with. the option was greyed out saying it was already unlocked. but I did relock it then unlock it. no avail. is there a timer or something with these tablets if you mess up?
    You triggered Samsung's VaultKeeper "feature" when you rolled back to the OEM firmware. In order to prevent that, you need to immediately enable Developer Options while connected to the Internet after setup (before rebooting). If you don't, VaultKeeper places the device in a hybrid state where it looks like the bootloader is still unlocked, but it still won't allow Odin to flash firmware unless it's signed with Samsung's release keys.

    Flashing a known-good OEM firmware should remedy the problem, provided you verify that the OEM Unlocking setting is enabled in Developer Options and go back for a Volume Up long press from the blue warning screen to complete the bootloader unlock. Did you do that after booting while holding the Volume Up & Down with the USB cable attached?
     
    • Like
    Reactions: Warrenchild

    cquilliam

    Senior Member
    Jul 6, 2011
    68
    0
    St. John's, NL
    Thanks for sharing this and great job! Got it up and running smoothly with gapps and magisk pretty easily.

    Haven't noticed any major issues other than that my SD card can't be read. It keeps showing the notification "Issue with SD Card - Tap to fix". I'm able to format the card successfully but the error returns the sd card isn't readable. Tried it with two different brands and getting the same issue.



    OpenGapps won't work. I tried and a few and managed to get it working with BiTGApps for Android 10. You can get it here:

    No luck for me with this, TWRP still reboots when trying to install gapps/bitgapps . I'm not sure what else to try.
     

    Top Liked Posts

    • There are no posts matching your filters.
    • 3
      New build just posted...

      Downloads:
      Change Log:
      20210526:
      • Based on the latest build of LineageOS 17.1 GSI (20210512) with May 2021 Security Patch.
      • Updated to the latest Android 10 OEM kernel and vendor partition (T510XXU4BUA1).
      1
      be aware
      currently MTP is broken (workaround: MIX with SMB for file transfer) and WPA3 isn't working (here ?) (workaround: use WPA2 instead)

      I don't know if this in all GSI's the case or in CAOS only ...
      The problem with MTP is that Samsung uses a proprietary implementation in their kernel. That's one of the main reasons that I have to build a custom kernel and why I have to wait until they publish kernel source for every release. (The other main reason is to disable their Knox boot security features.)

      BTW, I used the CAOS 11 GSI for my Nexus ROMs, and it's quite good!
      1
      Yep, Ubuntu laptop.
      Then there is no reason you can't install Windows. Use the MS "Media creation tool" to download the latest Win 10 iso and then install it in a VirtualBox session. You won't be able to activate it but you won't really need to. You have days to use Odin before you'd need to activate. But that isn't your only option. Linux has a replacement for Odin named Heimdall. A little harder to use than Odin, but an experienced Linux user shouldn't have a problem. VBG
    • 21
      640px-Lineage_OS_Logo.png

      In the spirit of moving custom ROM development along for the 2019 Galaxy Tab A 10.1 [SM-T510], here's a build of LineageOS 17.1 I just created based on the latest OEM stock firmware and @AndyYan's latest LineageOS 17.1 GSI. It's very much a work in progress, but it should hopefully help blaze the trail for even more custom ROMs for this tablet.

      Notes:
      • The current process requires you to reset to factory defaults to remove file-based encryption. Remember to backup your data!
      • Custom kernels are specific to OEM releases, and this one is based on the latest Android 10 release (T510XXU4BUA1).
      • Stock recovery will be replaced with my latest TWRP build for the SM-T510.
      • This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.

      Not working:
      • Support for file-based encryption

      Downloads:
      Build archives:
      Change Log:
      20210526:
      • Based on the latest build of LineageOS 17.1 GSI (20210512) with May 2021 Security Patch.
      • Updated to the latest Android 10 OEM kernel and vendor partition (T510XXU4BUA1).
      20201121:
      • Based on the latest build of LineageOS 17.1 GSI (20201114) with November 2020 Security Patch.
      • Updated to the new Android 10 OEM kernel and vendor partition (T510XXU3BTH4).
      20200812:
      • Based on the latest build of LineageOS 17.1 GSI (20200808) with August 2020 Security Patch.
      • Updated to the latest Android 10 OEM kernel and vendor partition (T510XXU3BTFN).
      20200713:
      • Based on the latest build of LineageOS 17.1 GSI (20200713) with July 2020 Security Patch.
      • Updated to the OEM May 2020 Security Update (T510XXS3ATE3) kernel and vendor partition.
      20200413:
      • Fixed Double Tap to Wake feature (enabled in Phh Treble Settings).
      • Fixed crash on first two attempts to launch Phh Treble Settings.
      • Based on the latest build of LineageOS 17.1 GSI (20200413).
      • Updated to the OEM T510XXS3ATB4 kernel and vendor partition.
      20200321:
      • Switched to latest stable version of ext2simg command for sparse image conversion.
      20200314:
      • Now based on the latest build of LineageOS 17.1 GSI (20200309).
      • Fixed potential image corruption issue from outdated img2simg command.
      20200308:
      • Charging after full shutdown will no longer hang during level-of-charge animation.
      20200301:

      Instructions:
      From OEM stock firmware:
      • Unlock bootloader
      • Hold Vol Up & Vol Down buttons during restart to enter Download mode
      • Install custom ROM tarball (.tar.md5 file) to AP with Odin
      • If TWRP launches, factory reset with Wipe->Format Data and reboot to system. (Not necessary for incremental upgrades.)
      From existing TWRP install:
      • Hold Power & Vol Up during restart to enter TWRP recovery
      • Tap Install, Install Image, select your update (.img file), and then swipe to install
      • Factory reset with Wipe->Format Data. (Not necessary for incremental upgrades.)
      • Reboot to system

      Source:

      Donations:
      • Your support is always appreciated! Just click here.
      • I'm leveraging a ton of work done by @AndyYan and @phhusson for Treble GSIs, so please show them some love here and here!
      5
      New build posted...

      Downloads:

      Change Log:
      20200713:
      • Based on the latest build of LineageOS 17.1 GSI (20200713) with July 2020 Security Patch.
      • Updated to the OEM May 2020 Security Update (T510XXS3ATE3) kernel and vendor partition.
      4
      I read that the lineage-17.1 GSi is updated on 20200607 with security patch June. Can we also expect soon an update for SM-T510?
      Soon. I'm trying to get the adaptive brightness and a few other features working for this next release.
      3
      I'm convinced that Samsung's decision to go with ARM32 (with 64-bit binder) for the SM-T510 was because of the low 2GB RAM in the base configuration. While overall performance is usually better running in 64-bit, RAM-constrained devices will have some serious performance issues that can be avoided by using the 32-bit instruction set. It just has a smaller footprint in memory.

      I would be interested in migrating a 64-bit vendor partition from another Exynos 7904 device, such as the Galaxy A40. It can be a tedious process, however, so I wouldn't undertake it if there was any chance that the Android 10 release coming in September might be 64-bit.

      We need a 64-bit vendor image from Samsung (or someone to adapt it from another Exynos 7904 device like the Galaxy A40). Perhaps the Andriod 10 release (due in September) will be 64-bit.

      I built a 64bit LOS GSI just yesterday and I've been playing with it today, I got it installed and it boots up far enough to be able to access the logs, however it gets stuck looking for the 64-bit `libGLES_mali.so`.

      I tried looking around for the 64 bit version of the libraries for the `universal7885` board or `exynos5` platform but had no luck.

      I don’t think it would be hard to get the A40 vendor partition to work. Biggest hurdle is the partitions all have to be resized due to the extra space required by the x64 binaries.

      If you could point me to a binary-compatible propreitary vendor image with the 64-bit libs I'm missing for this architecture I will be glad to share the modified sm-t510 vendor image if I can get it working.

      Here is the boot stacktrace I'm current looking at:
      Code:
      07-26 09:43:33.144  4222  4222 D RenderEngine: RenderEngine GLES Backend
      07-26 09:43:33.145  4222  4222 F libEGL  : couldn't find an OpenGL ES implementation, make sure you set ro.hardware.egl or ro.board.platform
      07-26 09:43:33.145  4222  4222 F libc    : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 4222 (surfaceflinger), pid 4222 (surfaceflinger)
      07-26 09:43:33.168  4227  4227 I crash_dump64: obtaining output fd from tombstoned, type: kDebuggerdTombstone
      07-26 09:43:33.168  3934  3934 I /system/bin/tombstoned: received crash request for pid 4222
      07-26 09:43:33.169  4227  4227 I crash_dump64: performing dump of process 4222 (target tid = 4222)
      07-26 09:43:33.173  4227  4227 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
      07-26 09:43:33.173  4227  4227 F DEBUG   : LineageOS Version: '17.1-20200726-UNOFFICIAL-'
      07-26 09:43:33.173  4227  4227 F DEBUG   : Build fingerprint: 'samsung/gta3xlwifixx/gta3xlwifi:10/QQ3A.200705.002/eng.robo.20200725.212218:userdebug/test-keys'
      07-26 09:43:33.173  4227  4227 F DEBUG   : Revision: '4'
      07-26 09:43:33.173  4227  4227 F DEBUG   : ABI: 'arm64'
      07-26 09:43:33.174  4227  4227 F DEBUG   : Timestamp: 2020-07-26 09:43:33-0400
      07-26 09:43:33.174  4227  4227 F DEBUG   : pid: 4222, tid: 4222, name: surfaceflinger  >>> /system/bin/surfaceflinger <<<
      07-26 09:43:33.175  4227  4227 F DEBUG   : uid: 1000
      07-26 09:43:33.175  4227  4227 F DEBUG   : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
      07-26 09:43:33.175  4227  4227 F DEBUG   : Abort message: 'couldn't find an OpenGL ES implementation, make sure you set ro.hardware.egl or ro.board.platform'
      07-26 09:43:33.175  4227  4227 F DEBUG   :     x0  0000000000000000  x1  000000000000107e  x2  0000000000000006  x3  0000007fdb9ded80
      07-26 09:43:33.175  4227  4227 F DEBUG   :     x4  fefeff75deeed027  x5  fefeff75deeed027  x6  fefeff75deeed027  x7  7f7f7f7fffffff7f
      07-26 09:43:33.175  4227  4227 F DEBUG   :     x8  00000000000000f0  x9  5684f34d959e7fdc  x10 0000000000000001  x11 0000000000000000
      07-26 09:43:33.175  4227  4227 F DEBUG   :     x12 fffffff0ffffffdf  x13 ffffffffffffffff  x14 0000000000000004  x15 ffffffffffffffff
      07-26 09:43:33.175  4227  4227 F DEBUG   :     x16 00000076dfbd18c0  x17 00000076dfbaf3b0  x18 00000076e1ade000  x19 000000000000107e
      07-26 09:43:33.175  4227  4227 F DEBUG   :     x20 000000000000107e  x21 00000000ffffffff  x22 0000000000000000  x23 00000076dfecd0cb
      07-26 09:43:33.175  4227  4227 F DEBUG   :     x24 00000076e1390020  x25 00000076e035a098  x26 00000076e0357028  x27 0000000000000001
      07-26 09:43:33.175  4227  4227 F DEBUG   :     x28 0000000000000001  x29 0000007fdb9dee20
      07-26 09:43:33.175  4227  4227 F DEBUG   :     sp  0000007fdb9ded60  lr  00000076dfb62f48  pc  00000076dfb62f74
      07-26 09:43:33.193  4227  4227 F DEBUG   : 
      07-26 09:43:33.193  4227  4227 F DEBUG   : backtrace:
      07-26 09:43:33.193  4227  4227 F DEBUG   :       #00 pc 0000000000081f74  /apex/com.android.runtime/lib64/bionic/libc.so (abort+160) (BuildId: bf14cf7a62d1f91755beddd4a937354d)
      07-26 09:43:33.193  4227  4227 F DEBUG   :       #01 pc 00000000000089f8  /system/lib64/liblog.so (__android_log_assert+324) (BuildId: fa7cbba17f5086fc8671eb6757477dd0)
      07-26 09:43:33.193  4227  4227 F DEBUG   :       #02 pc 0000000000025600  /system/lib64/libEGL.so (android::Loader::open(android::egl_connection_t*)+1020) (BuildId: 8e88ab543c9573b9c0f7e94de5c7c70b)
      07-26 09:43:33.193  4227  4227 F DEBUG   :       #03 pc 000000000001c4d4  /system/lib64/libEGL.so (android::egl_init_drivers()+88) (BuildId: 8e88ab543c9573b9c0f7e94de5c7c70b)
      07-26 09:43:33.194  4227  4227 F DEBUG   :       #04 pc 000000000001c770  /system/lib64/libEGL.so (eglGetDisplay+56) (BuildId: 8e88ab543c9573b9c0f7e94de5c7c70b)
      07-26 09:43:33.194  4227  4227 F DEBUG   :       #05 pc 000000000011663c  /system/lib64/libsurfaceflinger.so (android::renderengine::gl::GLESRenderEngine::create(int, unsigned int, unsigned int)+64) (BuildId: 96b996cfa12bca08accd8031151ec993)
      07-26 09:43:33.194  4227  4227 F DEBUG   :       #06 pc 00000000001164c4  /system/lib64/libsurfaceflinger.so (android::renderengine::RenderEngine::create(int, unsigned int, unsigned int)+164) (BuildId: 96b996cfa12bca08accd8031151ec993)
      07-26 09:43:33.194  4227  4227 F DEBUG   :       #07 pc 00000000000d066c  /system/lib64/libsurfaceflinger.so (android::SurfaceFlinger::init()+184) (BuildId: 96b996cfa12bca08accd8031151ec993)
      07-26 09:43:33.194  4227  4227 F DEBUG   :       #08 pc 00000000000031bc  /system/bin/surfaceflinger (main+364) (BuildId: b78b8993428f334aea26a30d4e6545bc)
      07-26 09:43:33.194  4227  4227 F DEBUG   :       #09 pc 000000000007d780  /apex/com.android.runtime/lib64/bionic/libc.so (__libc_init+108) (BuildId: bf14cf7a62d1f91755beddd4a937354d)

      I tried setting the `ro.hardware.egl=mali` prop just in case, but I think this is because it's 64bit looking in `/vendor/lib64/egl` only.

      I have the 32-bit version of the lib:
      Code:
      /media/robo/vendor/lib/egl/libGLES_mali.so: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, BuildID[md5/uuid]=1828d04d5fa0d90064b37369e8a99cb5, stripped
      from the stock vendor image, but there's no `lib64` directory in /vendor at all...

      I don't suppose there's some magic setting or prop I can change to have it load 32-bit libs instead?