• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][SM-T350][UNOFFICIAL][crDroidAndroid-11.0][v7.10][ANDROID 11] Galaxy Tab A 8.0

Search This thread
I am not responsible for bricked devices, or any other hardware malfunctions that comes as a result of flashing this ROM, Please do some research if you have any concerns about features included before flashing it, this ROM was built for the SM-T350 if you choose to flash this on any other device do so at your own risk!

>> crDroid Features <<



-Installation instructions-

1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (TWRP recommended).
3. Do a full backup of your device
4. Wipe the System, Cache, Data and ART/Dalvik cache. (Recommended)
5. Flash the ROM Zipfile.
6. Flash the GApps (optional, needed for e.g. Google Playstore to work).
7. Flash the root solution of your choice (optional).
8. Reboot your device.


TWRP 3.5.2 SM-T350 DOWNLOAD

TWRP 3.5.2 SM-T350 ODIN DOWNLOAD

TWRP 3.3.1 SM-T350 DOWNLOAD






If you are having problems flashing this ROM you are most likely running into issues other members were having with the device most of which were already solved, please spend some time reading through this post of other posts related to this device.

-Backlight issues-
Read this post https://forum.xda-developers.com/showpost.php?p=83488241&postcount=41



Thanks
CrDroid Team
Evervolv Team

XDA:DevDB Information
crDroid Android, ROM for the Samsung Galaxy Tab A series

Contributors

nubianprince
ROM OS Version: Android 11
ROM Kernel: Linux 3.10.x
Based On: crDroidAndroid

Version Information
Status:
Stable
 
Last edited:
  • Like
Reactions: bluenote73
Reporting Bugs
  • DO NOT Report bugs if you're running a custom kernel
  • Grab a logcat right after the problem has occurred. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
  • If it is a random reboot, grab /proc/last_kmsg.
  • What is the issue?
  • Attach or link the file.
Working
  • Audio (Tested)
  • Bluetooth (Tested)
  • Wifi (Tested)
  • Face Unlock (Tested)
  • Camera (Tested)
  • Netflix (Tested)
Not Working
You tell me

F.A.Q

1: Can I flash this on my SM-P355 tab
The ROM was built for the SM-T350 device (you can edit the updater script and flash at your own risk, a lot can go wrong)

2: Is this for Samsung Tab A 8.0 (2019)
The 2019 tablet is a SM-T290 device this ROM was built for the SM-T350

3: I get an error 7 when flashing this ROM
Install the TWRP image in the main post

4: Will you build for the SM-P355, SM-T290, SM-P350?
No I am only building for the devices that I own, feel free to use my device tree to build for your device
 
Last edited:
Changes

2021-06-18
- May Security Patches

2021-06-21
- June Security Patches
- DRM fixes

2021-06-24
- Overclocked Kernel & GPU
- Added missing vendor blobs to fix drm issues

2021-06-27
- Cleaned up sensor spamming
- Some sepolicy fixes

2021-07.07
- Fix for UI blur issues
- Some sepolicy fixes

2021-07.08
- Fix for live display

2021-09-19
- September Security Patches
 
Last edited:

retiredtab

Senior Member
Nov 16, 2017
856
437
Two bugs.

1) sensors not working

Code:
  2557  12-16 15:23:13.580   372   372 E Sensors : couldn't find 'accelerometer_sensor' input device
  2558  12-16 15:23:13.581   372   372 E Sensors : couldn't find 'accelerometer_sensor' input device
  2559  12-16 15:23:13.581   372   372 E Sensors : Couldn't open accelerometer_sensor.
  2560  12-16 15:23:13.581   372   372 E Sensors : AccelerometerSensor: undefined chip spec()
  2561  12-16 15:23:13.581   372   372 E Sensors : couldn't find 'light_sensor' input device
  2562  12-16 15:23:13.581   372   372 E Sensors : couldn't find 'light_sensor' input device
  2563  12-16 15:23:13.581   372   372 E Sensors : Couldn't open light_sensor.
  2564  12-16 15:23:13.581   372   372 E Sensors : LightSensor: undefined chip spec()
  2565  12-16 15:23:13.582   372   372 E Sensors : couldn't find 'grip_sensor_wifi' input device
  2566  12-16 15:23:13.582   372   372 E Sensors : couldn't find 'grip_sensor_wifi' input device
  2567  12-16 15:23:13.582   372   372 E Sensors : Couldn't open grip_sensor_wifi.

For my build, I found that sensors have to be in passthrough mode and sensors.msm8916 has to be removed. That is, manifest.xml

Code:
    <hal format="hidl">
        <name>android.hardware.sensors</name>
        <transport arch="32">passthrough</transport>
        <version>1.0</version>
        <interface>
            <name>ISensors</name>
            <instance>default</instance>
        </interface>
    </hal>

and msm8916.mk

Code:
# Sensor HAL
# RT sensor needs to be passthrough and sensors.msm8916 needs to be removed in order to work
PRODUCT_PACKAGES += \
    [email protected] 
#    [email protected] \
#    sensors.msm8916


2) drm not working
Code:
 2527  12-16 15:23:13.530   364   364 E [email protected]: Failed to lookup symbol createDrmFactory in library /vendor/lib/mediadrm/libwvdrmengine.so: dlopen failed: cannot locate symbol "_ZN6google8protobuf8internal13empty_string_E" referenced by "/system/vendor/lib/mediadrm/libwvdrmengine.so"...
You are missing a commit like


===

Since you are using evervolv's kernel code, I suggested to them that they consider overclocking the CPU/GPU and gave them the commits, but they haven't or decided not to implement them.
 
Two bugs.

1) sensors not working

Code:
  2557  12-16 15:23:13.580   372   372 E Sensors : couldn't find 'accelerometer_sensor' input device
  2558  12-16 15:23:13.581   372   372 E Sensors : couldn't find 'accelerometer_sensor' input device
  2559  12-16 15:23:13.581   372   372 E Sensors : Couldn't open accelerometer_sensor.
  2560  12-16 15:23:13.581   372   372 E Sensors : AccelerometerSensor: undefined chip spec()
  2561  12-16 15:23:13.581   372   372 E Sensors : couldn't find 'light_sensor' input device
  2562  12-16 15:23:13.581   372   372 E Sensors : couldn't find 'light_sensor' input device
  2563  12-16 15:23:13.581   372   372 E Sensors : Couldn't open light_sensor.
  2564  12-16 15:23:13.581   372   372 E Sensors : LightSensor: undefined chip spec()
  2565  12-16 15:23:13.582   372   372 E Sensors : couldn't find 'grip_sensor_wifi' input device
  2566  12-16 15:23:13.582   372   372 E Sensors : couldn't find 'grip_sensor_wifi' input device
  2567  12-16 15:23:13.582   372   372 E Sensors : Couldn't open grip_sensor_wifi.

For my build, I found that sensors have to be in passthrough mode and sensors.msm8916 has to be removed. That is, manifest.xml

Code:
    <hal format="hidl">
        <name>android.hardware.sensors</name>
        <transport arch="32">passthrough</transport>
        <version>1.0</version>
        <interface>
            <name>ISensors</name>
            <instance>default</instance>
        </interface>
    </hal>

and msm8916.mk

Code:
# Sensor HAL
# RT sensor needs to be passthrough and sensors.msm8916 needs to be removed in order to work
PRODUCT_PACKAGES += \
    [email protected]
#    [email protected] \
#    sensors.msm8916


2) drm not working
Code:
2527  12-16 15:23:13.530   364   364 E [email protected]: Failed to lookup symbol createDrmFactory in library /vendor/lib/mediadrm/libwvdrmengine.so: dlopen failed: cannot locate symbol "_ZN6google8protobuf8internal13empty_string_E" referenced by "/system/vendor/lib/mediadrm/libwvdrmengine.so"...
You are missing a commit like


===

Since you are using evervolv's kernel code, I suggested to them that they consider overclocking the CPU/GPU and gave them the commits, but they haven't or decided not to implement them.

I already started a new build to fix the sensors with June security patches... I will look into drm thought I had that fixed
 

retiredtab

Senior Member
Nov 16, 2017
856
437
I use devcheck by flar2 to check sensors and drm. When I click on the system menu in devcheck, my build with DRM shows Version 14.0.0, security L3 and clearkey 1.2. On your June 18 build, the same app shows nothing for DRM because of the error message that I included.
 

retiredtab

Senior Member
Nov 16, 2017
856
437
TCP/IP errors.

With Android 11, you also need a patch to fix TCP/IP errors. I found these in my build back in March 2021 and you have them too in your build.

Code:
03-24 08:08:09.674  1059  1653 E TcpInfo : parsing error.
03-24 08:08:09.674  1059  1653 E TcpInfo : java.lang.IllegalArgumentException: Length 104 is less than required.
03-24 08:08:09.674  1059  1653 E TcpInfo :     at com.android.networkstack.netlink.TcpInfo.<init>(TcpInfo.java:118)
03-24 08:08:09.674  1059  1653 E TcpInfo :     at com.android.networkstack.netlink.TcpInfo.parse(TcpInfo.java:143)

To fix, see


and


I opted for the DerpFest fix at


since I didn't want to touch the msm8916 kernel code.

Thanks to Henrik Grimler for pointing this out to me back in March 24, 2021.
 

retiredtab

Senior Member
Nov 16, 2017
856
437
Henrik Grimler submitted those kernel changes to msm8916 gerrit a while back after discovering it, but gerrit been down for days and I don't know when it will be up.

Again, I opted for the DerpFest fix, but I'm following the msm8916 kernel, not evervolv, so if Henrik's changes get merged into 18.1, I can revert the DerpFest fix.
 

retiredtab

Senior Member
Nov 16, 2017
856
437
@nubianprince , the June 21 build still has problems with DRM and sensors.

1. DRM
Your DRM shows clearkey 1.2 now using devcheck by flar2, but is mssing the widevine other info as I wrote in post #7.
Code:
  2434  12-19 09:31:43.905     0     0 I [1:           init:    1] init: starting service 'vendor.drm-hal-1-0'...
  2435  12-19 09:31:43.913     0     0 E [1:           init:    1] init: File /vendor/bin/hw/[email protected] (labeled "u:object_r:vendor_file:s0") has incorrect label or no domain transition from u:r:init:s0 to another SELinux domain defined. Have you configured your service correctly? https://source.android.com/security/selinux/device-policy#label_new_services_and_address_denials  
  2474  12-19 09:31:44.041   363   363 E [email protected]: Failed to lookup symbol createDrmFactory in library /vendor/lib/mediadrm/libwvdrmengine.so: dlopen failed: cannot locate symbol "_ZN6google8protobuf8internal13empty_string_E" referenced by "/system/vendor/lib/mediadrm/libwvdrmengine.so"...

2. Sensors are still broken. As you can see in trace, it's starting and then dying (signal 9).
Code:
   339  06-21 13:01:47.743     0     0 I [3:           init:    1] init: starting service 'vendor.sensors-hal-1-0'...
   340  06-21 13:01:47.761  2841  2841 E [email protected]: Couldn't load sensors module (Unknown error -2147483648)
   341  06-21 13:01:47.761  2841  2841 D RefBase : RefBase: Explicit destruction, weak count = 0 (in 0xa6f00114)
   342  06-21 13:01:47.761  2841  2841 W RefBase : CallStack::getCurrentInternal not linked, returning null
   343  06-21 13:01:47.761  2841  2841 W RefBase : CallStack::logStackInternal not linked
   344  06-21 13:01:47.762  2841  2841 E LegacySupport: Could not get passthrough implementation for [email protected]::ISensors/default.
   345  06-21 13:01:47.790     0     0 I [0:           init:    1] init: Service 'vendor.sensors-hal-1-0' (pid 2841) exited with status 1
   346  06-21 13:01:47.790     0     0 I [0:           init:    1] init: Sending signal 9 to service 'vendor.sensors-hal-1-0' (pid 2841) process group...
   347  06-21 13:01:47.790     0     0 I [0:           init:    1] libprocessgroup: Successfully killed process cgroup uid 1000 pid 2841 in 0ms
 
Last edited:

retiredtab

Senior Member
Nov 16, 2017
856
437
Pictures from devcheck to illustrate what I'm describing. The file names tell you which screenshot is what. You can see the difference between my build and yours. I didn't take a picture of crDroid sensors, but yours only has temperature whereas mine as 2 more.
 

Attachments

  • crdroid-drm.jpg
    crdroid-drm.jpg
    80.4 KB · Views: 86
  • lineageos-drm.png
    lineageos-drm.png
    64.5 KB · Views: 87
  • lineageos-sensors.png
    lineageos-sensors.png
    31.7 KB · Views: 88

retiredtab

Senior Member
Nov 16, 2017
856
437
So your June 21 build is completely missing the widevine information in the screenshot above. And yes, clearkey info is at the bottom of that crdroid screenshot. It cannot scroll any farther down in case you were wondering. The adb logcat error message I included also tells you that something is still wrong.
 

retiredtab

Senior Member
Nov 16, 2017
856
437
@nubianprince , June 24 has overclock for both CPU and GPU. DRM and sensors both are fixed as viewed by devcheck app.

While the sensors work in devcheck, adb logcat still shows something is not quite 100% as it continually spams
Code:
  9184  06-24 14:27:53.969     0     0 I [1:           init:    1] init: starting service 'vendor.sensors-hal-1-0'...
  9185  06-24 14:27:54.000  2879  2879 I sensors_hal_wrapper: Initializing wrapper for Samsung Sensor-HAL
  9186  06-24 14:27:54.002  2879  2879 E Sensors : couldn't find 'accelerometer_sensor' input device
  9187  06-24 14:27:54.002  2879  2879 E Sensors : couldn't find 'accelerometer_sensor' input device
  9188  06-24 14:27:54.003  2879  2879 E Sensors : Couldn't open accelerometer_sensor.
  9189  06-24 14:27:54.003  2879  2879 E Sensors : AccelerometerSensor: undefined chip spec()
  9190  06-24 14:27:54.003  2879  2879 E Sensors : couldn't find 'light_sensor' input device
  9191  06-24 14:27:54.003  2879  2879 E Sensors : couldn't find 'light_sensor' input device
  9192  06-24 14:27:54.003  2879  2879 E Sensors : Couldn't open light_sensor.
  9193  06-24 14:27:54.003  2879  2879 E Sensors : LightSensor: undefined chip spec()
  9194  06-24 14:27:54.003  2879  2879 E Sensors : couldn't find 'grip_sensor_wifi' input device
  9195  06-24 14:27:54.003  2879  2879 E Sensors : couldn't find 'grip_sensor_wifi' input device
  9196  06-24 14:27:54.003  2879  2879 E Sensors : Couldn't open grip_sensor_wifi.
  9197  06-24 14:27:54.003  2879  2879 E Sensors : GripSensor_wifi: undefined chip spec()
  9198  06-24 14:27:54.003  2879  2879 E Sensors : couldn't find 'meta_event' input device
  9199  06-24 14:27:54.004  2879  2879 E Sensors : couldn't find 'meta_event' input device
  9200  06-24 14:27:54.004  2879  2879 E Sensors : Couldn't open meta_event.
  9201  06-24 14:27:54.004  2879  2879 D Sensors : sensors_poll_context_t: sensor list: 0
  9202  06-24 14:27:54.006  2879  2879 E HidlServiceManagement: Service [email protected]::ISensors/default must be in VINTF manifest in order to register/get.                                                                                                                                                
  9203  06-24 14:27:54.006  2879  2879 E LegacySupport: Could not register service [email protected]::ISensors/default (-2147483648).
  9204  06-24 14:27:54.033     0     0 I [2:           init:    1] init: Service 'vendor.sensors-hal-1-0' (pid 2879) exited with status 0
  9205  06-24 14:27:54.033     0     0 I [2:           init:    1] init: Sending signal 9 to service 'vendor.sensors-hal-1-0' (pid 2879) process group...

Do a grep for "vendor.sensors-hal-1-0" in your device tree and/or vendor tree to what is calling it.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    I am not responsible for bricked devices, or any other hardware malfunctions that comes as a result of flashing this ROM, Please do some research if you have any concerns about features included before flashing it, this ROM was built for the SM-T350 if you choose to flash this on any other device do so at your own risk!

    >> crDroid Features <<



    -Installation instructions-

    1. Download the ROM and GApps and transfer them to your device.
    2. Boot to recovery (TWRP recommended).
    3. Do a full backup of your device
    4. Wipe the System, Cache, Data and ART/Dalvik cache. (Recommended)
    5. Flash the ROM Zipfile.
    6. Flash the GApps (optional, needed for e.g. Google Playstore to work).
    7. Flash the root solution of your choice (optional).
    8. Reboot your device.


    TWRP 3.5.2 SM-T350 DOWNLOAD

    TWRP 3.5.2 SM-T350 ODIN DOWNLOAD

    TWRP 3.3.1 SM-T350 DOWNLOAD






    If you are having problems flashing this ROM you are most likely running into issues other members were having with the device most of which were already solved, please spend some time reading through this post of other posts related to this device.

    -Backlight issues-
    Read this post https://forum.xda-developers.com/showpost.php?p=83488241&postcount=41



    Thanks
    CrDroid Team
    Evervolv Team

    XDA:DevDB Information
    crDroid Android, ROM for the Samsung Galaxy Tab A series

    Contributors

    nubianprince
    ROM OS Version: Android 11
    ROM Kernel: Linux 3.10.x
    Based On: crDroidAndroid

    Version Information
    Status:
    Stable
    1
    New build uploaded (2021-06-21) with a few fixes @lividhen that app you couldn't get to work in the android 10 build should work in this build.
    1
    Small selinux thing, when enforcing the lcd brightness cannot be changed through settings. It can be turned on and off, and the brightness can be changed by manually writing to /sys/devices/soc.0/1a00000.qcom,mdss_mdp/qcom,mdss_fb_primary.133/leds/lcd-backlight/brightness, but by any other means it does not work.

    I have noticed (unrelated to selinux), this rom seems to run a lot cooler (40-70 rather than 50-80) than the Q one. The speaker is louder too 👍.

    (Happy 4th Of July to those who live in the US too!)
    1
    live display should now work in build 2021-07-08
    1
    Ota updates only work for officially maintained crdroid roms. This one is unofficial, so you can just download the new zip, and flash it in twrp. You don't need to wipe data if you are staying on the same android version (and are not switching to another rom.). I would recommend wiping cache/dalvik cache though.
    Yeah, I’ll probably wipe the caches before flashing with TWRP. Thanks for the help!

    I’m staying on this rom, so I assume I’ll only need to wipe the caches.