yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Re FM Radio. After a bit more research, I thik it's not a bug for the tablets that don't have the LTE chipset. See

https://www.makeuseof.com/tag/how-to-unlock-fm-radio-hidden-smartphone/

"The ability to access the radio comes from the Qualcomm LTE modem in smartphones"

For tablets that do have the LTE chipset, then FM radio might work, but since I don't have one, I don't know. The FM radio app does not crash on the 17.1 sm-560nu build and I can see logcat that FM radio is working, but it never finds any stations. And yes there were 2 files not being copied over, but even though I copied the 2 over, it still didn't find any stations.

The 2 files missing were

PRODUCT_COPY_FILES += \

vendor/samsung/msm8916-common/proprietary/lib/vendor.qti.hardware.fm@1.0.so:$(TARGET_COPY_OUT_SYSTEM)/lib/vendor.qti.hardware.fm@1.0.so \

vendor/samsung/msm8916-common/proprietary/bin/fm_qsoc_patches:$(TARGET_COPY_OUT_SYSTEM)/bin/fm_qsoc_patches

For my builds, I'll leave the app in, but just document that I have no way of testing it.

---------- Post added at 07:10 PM ---------- Previous post was at 07:05 PM ----------

Pen and LTE won't work since none of us have the LTE drivers.

Also, if it's anything like my SM-P550 (9.7 inch with s pen), the X-axis will be reversed. Fixing it is easy (once you know where to look and what to do since it's only 1 line of code that needs to be changed). See

https://xdaforums.com/galaxy-tab-a/development/unofficial-beta-lineageos-16-0-galaxy-t4160909

but you have to get nubianprince to either change the code so it looks like

if (spen model)
reverse x-axis
else
normal x-axis

or take his repo, manifest, etc and compile it yourself with my fix in the other thread.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Barrohn:
No Backlight

Hey, so I am successful in installing this rom on two of my four SM-T350s, but the only issue is that there seems to be no backlight?

I can see that the rom is installed and running with the help of an external light.

I am running TWRP 3.1.1.1 on both units.

I followed the steps in the original post to the t as far as I can tell.

This backlight issue has happened three times on the one unit and twice on the other. So I am not sure what I am missing or doing wrong.

Any help is appreciated.

Byron
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen99:
This is a known issue with this device in general, but it only happens on some devices. Nubianprince, you may want to put this in the main post: install this marshmallow firmware with odin3 then flash twrp and the ROM. The marshmallow firmware never needs to boot, it just needs to be installed. https://www.sammobile.com/firmwares/galaxy-tab-a/SM-T350/XAR/download/T350XXU1BPI2/103197

Edit: it looks like it has been archived... Here is a Google drive link https://drive.google.com/open?id=1gjoodMD09sAZJIWM8fVKrBT3cwmqTTSP
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Barrohn:
Awesome Thanks lividhen99, I will give that a try.

So install the marshmallow with odin3, then right after flash twrp, load into twrp and install crDroid?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen99:
Yep!

It has been an issue since android 8 and I'm not sure anybody is 100% sure why. Especially why it's so inconsistent.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Barrohn:
Interesting. The sad part is that I have flashed the stock on both, but no matter if I try ADB or ODIN3 I cannot for the life of me get TWRP to install or load. Very frustrating.

I have tried different versions of TWRP also but no success.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen99:
What version of odin3? If you boot into recovery and factory reset (to ge the system to boot) , try enabling adb in developer options. Also, use a different USB cable and port.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Barrohn:
Hey lividhen99, I just swapped the version of Odin3 i was using and BOOM I'm in to TWRP. And I just finished flashing the ROM onto my son's TAB and it's ALIVE!!!

Thank you so much for your help!! You rock.

Byron
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen99:
Your welcome! I did not figure the black screen issue out, I wss just relaying the info. I'm not completely sure who figured out, but it might have ashyx.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
An alternative for future problems like this might be to use the lineageos recovery.img instead of twrp. The lineageos recovery.img (located in the $OUT directory) might have different defaults and settings that twrp doesn't and vice versa.

It's not as easy to use as twrp, but I'm using it on the P550 because the X-axis is correct on my build of it.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen99:
I think were thinking it's a permission thing, not a setting thing... maybe. It just cant access the back light. The rom's have the issue too. But again, it seems to be random which devices it affects.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] vbprof:
tried TWRP to wipe and then try to install crDroidAndroid-10.0-20200907-gt58wifi-v6.9.zip. It would show an error 7. Not sure what went wrong. Does anyone have similar problem with installation?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Did you try TWRP 3.3.1?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen99:
Error 7 means the updater script in the ROM zip thinks you don't have the correct device. Are you SURE you have an SM-T350? If you are: try using twrp 3.3.1 from nubianprince's profile description. If the backlight won't turn on, install the marshmallow firmware from the previous page using odin3. But first make sure you have an SM-T350 😂!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] vipulkohli:
I was used this rom but there are a lot of hickups and that's quite unstable and just to be sure do we need to install gapps or mind thegpps file because using mind the gapps file on lineage improves it's stability
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen99:
Really? I haven't had any problems with it. What were the issues you were having? Yes, you do need to install gapps if you want google play/near by share/etc. Also, gapps will not improve stability. Its is just GMS (google mobile services) and it may end up reducing stability because it is kind of resource heavy. It will add all the features included in GMS though.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
there is a reason I dont really respond to any of these issues as most people fail to take a few minutes to read the OP, thks [MENTION=9248375]lividhen99[/MENTION] and [MENTION=8726605]retiredtab[/MENTION] for having the patience to respond.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen99:
Fm radio makes sense, but why was audiofx removed?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
This will go back in the next build, some changes I made was causing it to crash.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] bluenote73:
How's the stability and memory management? I'm really happy with the 9 build, but eager to try 10. But I'll wait a bit if 10 has still got growing pains? (Also should I upgrade to latest twrp in the OP?)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen99:
Apps get OOMed / LMKed (grammar? Idk) less frequently. If you do want more apps open at once, you could probably increase it via module. It runs a lot hotter though... Maybe it's just me, but it's typically 65-75 degrees (celcious)... The surfacefinger takes up quite a bit of cpu, and it is switching to higher frequencies, making it hotter... I'm not sure if this is a device issue or a crdroid one, but I think surfaceflinger has to do with the Framebuffer 🤔 so maybe crdroid. This only happens some of the time though. The rom its self is pretty stable, and I am enjoying the gestures, 🤣 there kind of fun.

Edit: hmm... Lowering the clock speed a little seems to make surface finger less angry.

Edit2: I don't feel like this deserves an entirely new comment, but, crDroid seems to have fixed their wired accessory manager, so if you want to build yourself, you no longer have to replace it with the old one. (to fix wired earbuds/speakers)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Youngei:
Can I flash this ROM on SM-P355? I assume the LTE and the S pen is not going to work, is there any suggested ROM for SM-p355? Or is there a way it modify the T350 ROM in order for it to work on P355?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen99:
There is always danger flashing a ROM not specifically made for your device. But you can try flashing your stock boot image after flashing the ROM, which might not work now, because the way the system boots in Android 10 has changed slightly, but I'm not sure how it applies practically. I would be happy to try to build a version for your device, but carriers do not release their source code... Data and s-pen will definitely not work. Try this at your own risk! I would not recommend it.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Youngei:
https://xdaforums.com/galaxy-tab-a/development/rom-galaxy-tab-series-t3514996

This is the only thread I can find on xda,its an old Android 6 ROM but I think it is built for sm-p355, which I don't know how the author got the source code, but anyway maybe this could give u some idea? BTW I'm a really noob programmer, but I would be happy if we can discuss privately if there's anything I can help
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen99:
The way those debloat roms are created, is somebody manually goes trough, deletes everything they need to, create a backup, and have others restore it. No source code is involved. Only the final compiled OS.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Hexrotor:
:)Hey guys, I think I found the cause of the backlight problem in some devices. You may know SM-P350 and SM-T350 have the same hardware so that ROMs of T350 can also be worked in P350. But some P350 devices have the different Screen Panels from T350 devices. These devices use BOE Panels that not have driver in some ROMs, it caused the backlight problem. I saw someone has the same problem as me in T350 devices, so if your backlight not work, you can check your screen panel in Devcheck app to know whether it caused the problem.

(:(Sorry for my bad English.)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] VitaminC2333:
I think it is the correct cause of backlight problem,because i had already test 3 different SM-P350s,ALL BOE DEVICES backlight were not working.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen99:
Does anyone else have an issue where the built in music player (also phonograph off Google play) cannot add songs to Playlists? Both versions can create Playlists and write .m3u Playlist files, but songs cannot be added to them. I did not wipe internal storage (/data/media) when upgrading, so there may have been something left over from android 9 that I can't find that is messing it up...
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
Will see if I can replicate tomorrow
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Works fine on my lineageos build. I can add songs to my playlist using stock music player.

I tried to capture some logcats, but I don't see anything from the stock music player indicating that it's adding a new playlist or song to an existing playlist. I just get

10-05 21:57:23.216 26743 27165 E MetadataRetrieverClient: failed to extract an album art

10-05 21:57:23.216 423 620 E MediaMetadataRetrieverJNI: getEmbeddedPicture: Call to getEmbeddedPicture failed.

because the MP3 (www.bensound.com)I downloaded from the Internet has no picture. It's the same music I used to test the original 2019 mp3 choppy audio problems.

Right now, I can't load crDroid build onto my tablet. I have too many things on it and need to backup all the files if I switch roms.

---------- Post added at 10:14 PM ---------- Previous post was at 10:13 PM ----------

None of us have the P350 so we can't test this personally, but the code at

https://github.com/Galaxy-MSM8916/a...rm/configs/msm8916_sec_gt58wifi_eur_defconfig

shows the kernel is loading BOTH drivers. Specifically line 46 and 47.

#LCD

CONFIG_PANEL_S6D7AA0_LSL080AL03_WXGA=y

CONFIG_PANEL_S6D7AA0_LSL080AL03_BOE_WXGA=y

So both drivers should be in the kernel code. Since we don't have the P350, I have no idea why its not choosing the BOE driver for the P350 (if that's the problem).

I guess one possible way to "force it" is to change

CONFIG_PANEL_S6D7AA0_LSL080AL03_WXGA=N

or comment it out so the only driver is the BOE for the P350?

Or some sort of

#ifdef P350
load BOE only
#elsedef
load non BOE only
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Hexrotor:
:)Thx for your help! There is another one who have the backlight problem on T350 in this post, not just P350.

And another problem is that T350's TWRP 3.2 and above also have the backlight problem on P350 BOE device, but it's no problem with 3.1 and below. Are they using the different drivers? :crying:If not, maybe we can find the problem in other parts.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Techguy777:
So I pulled the tab A and flashed crdroid android 10 to see how it works. So far it works pretty good. Is there any problems. I know so far this tablet runs best on android 6 stock. I always thought the custom roms slowed down a lot after awhile. But now and android 6 is getting old. SO it would be nice to have 10 working great. Thanks to the developer of course.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Hexrotor:
Here is the log of this ROM working on P350 BOE devices. It seems that there is something wrong with the driver.

09-15 02:13:02.368 530 530 I HwBinder:331_1: type=1400 audit(0.0:347): avc: denied { read } for name="msm_fb_panel_info" dev="sysfs" ino=9360 scontext=u:r:hal_graphics_composer_default:s0 tcontext=u:object_r:sysfs:s0 tclass=file permissive=1
09-15 02:13:02.368 530 530 I HwBinder:331_1: type=1400 audit(0.0:348): avc: denied { open } for path="/sys/devices/virtual/graphics/fb0/msm_fb_panel_info" dev="sysfs" ino=9360 scontext=u:r:hal_graphics_composer_default:s0 tcontext=u:object_r:sysfs:s0 tclass=file permissive=1
09-15 02:13:02.368 530 530 I HwBinder:331_1: type=1400 audit(0.0:349): avc: denied { getattr } for path="/sys/devices/virtual/graphics/fb0/msm_fb_panel_info" dev="sysfs" ino=9360 scontext=u:r:hal_graphics_composer_default:s0 tcontext=u:object_r:sysfs:s0 tclass=file permissive=1
09-15 02:13:02.371 331 530 D modemanager: Panel Name: S6D7AA0_LSL080AL03_BOE_wxga_video_mode_dsi_panel
09-15 02:13:02.373 331 530 E modemanager: readXMLOp:Couldn't open OEM XML file!
09-15 02:13:02.373 331 530 E modemanager: retrieveMode: Failed to enumerate modes
09-15 02:13:02.373 331 530 E modemanager: instantiateModeMgr: Failed to update default cache!
09-15 02:13:02.373 331 530 E modemanager: readXMLOp:Couldn't open OEM XML file!
09-15 02:13:02.373 331 530 E modemanager: retrieveMode: Failed to enumerate modes
09-15 02:13:02.373 331 530 E modemanager: in applyDefaultMode fail to retrieve default mode!
09-15 02:13:02.373 331 530 I modemanager: in applyDefaultMode ret = 0 mCurMode = -1
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
[MENTION=11154257]Hexrotor[/MENTION], thanks for the logcat. It makes troubleshooting a lot easier.

See if my build at

https://androidfilehost.com/?w=files&flid=316600

has a working backlight for BOE or not.

The code between nubianprince's build and mine are slightly different. I tried to stay as close to "stock" msm8916 as possible so that changes are minimal and can be easily replicated into 18.0. My changes don't touch any permissions or *.te or sepolicy files.

If the root cause of the BOE not working is due to permissions, I can't see why the code would discriminate against the BOE. If granting permissions fixes the BOE problem, it shouldn't be too hard to add those permissions to the code.

PS. For the life of me, I cannot find where "modemanager" is being called in the code.

PPS. I see nubianprince updated his github repo 5 hours ago with new changes.

---------- Post added at 12:34 PM ---------- Previous post was at 12:23 PM ----------

And if my build doesn't work with BOE panels, please attach a logcat as well so I can see if it has the same error message as nubianprince's crdroid build.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
If permissions is the problem with the BOE, you can try disabling selinux using this patch

https://xdaforums.com/android/software-hacking/mod-kernel-permissive-patcher-android-t3506338

If tablet with BOE panel then works with selinux disabled completely, then the code to allow those permissions can be added.

This all assumes that the problem is with the permissions and that the patch works as intended with Android 10.0. I have used this patch before, but I can't remember under what circumstances and which code base.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Hexrotor:
:)Thank u, I will take the time to try this version(I have no time recently, sorry:crying:)

In fact, I tried almost all the third-party ROMs(included yours) of T350 since Android 9 or lower, the problem always lies in BOE devices without exception. So I guess this ROM maybe have the same problem.

Have you noticed the TWRP problem I mentioned? The problem is probably between ver3.1 and ver3.2 because it cannot work on BOE devices since ver3.2(backlight problem). :)It might be easier to find the problem from here.

TWRP3.1.1 lastest version works on BOE devices: twrp_3.1.1-1_sm-t355_251117

It's for T355 but can also work on T350 and P350.

URL: xdaforums.com/galaxy-tab-a/development/recovery-t3426560
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
[SIZE="3"]HwBinder:331_1: type=1400 audit(0.0:347): avc: denied { read } for name="msm_fb_panel_info" dev="sysfs" ino=9360 scontext=u:r:hal_graphics_composer_default:s0 tcontext=u:object_r:sysfs:s0 tclass=file permissive=1

HwBinder:331_1: type=1400 audit(0.0:348): avc: denied { open } for path="/sys/devices/virtual/graphics/fb0/msm_fb_panel_info" dev="sysfs" ino=9360 scontext=u:r:hal_graphics_composer_default:s0 tcontext=u:object_r:sysfs:s0 tclass=file permissive=1

HwBinder:331_1: type=1400 audit(0.0:349): avc: denied { getattr } for path="/sys/devices/virtual/graphics/fb0/msm_fb_panel_info" dev="sysfs" ino=9360 scontext=u:r:hal_graphics_composer_default:s0 tcontext=u:object_r:sysfs:s0 tclass=file permissive=1[/SIZE]

If, and that's a big if, I'm interpreting the above messages correctly, I believe this code will allow the BOE to access the files in the /sys directories

1. I have never written a sepolicy before, but I believe this to be correct based on examples.

allow hal_graphics_composer_default sysfs:file { getattr read open };

2) I found this line of code at

https://android.googlesource.com/de...ter/sepolicy/hal_graphics_composer_default.te

It allows access to the fb0.

# Access /sys/devices/virtual/graphics/fb0/mdp/caps and maybe others
r_dir_file(hal_graphics_composer_default, sysfs_type)

I don't know which code is necessary so I included both for now. If it works, then we can narrow down which line of code is the correct one.

The build that incorporates the 2 lines of code can be found in my lineageos build dated Oct 8 today. It includes the latest Oct 5 security patches.

https://androidfilehost.com/?w=files&flid=316600

Regardless if it works or not, please get a logcat so I can see messages.

---------- Post added at 06:04 PM ---------- Previous post was at 05:54 PM ----------

Ashyx has no github repo for the gt58wifi. Thus, I can't tell what he did for the BOE panel.

I also participated in that thread and reported a number of bugs with the twrp version at that time.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Hexrotor:
:)Thx you! Now I only have one P350 BOE device and need to use it for work. And I have no computer now. I may have to wait a long time to test it, maybe 10days or later? I'm not sure but I will test it as soon as possible.

I saw [MENTION=6118674]Barrohn[/MENTION] have the same problem on T350, maybe you can ask him for a test.

Hi Barrohn, I hope you can help us troubleshoot screen issues. The backlight problem is related to the BOE panel, you can check your devices' panel in Devcheck app.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lmore377:
It's awesome seeing that there's still active development going on for this device. I'm installing it right now and I'll test everything I can and report back.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Let us know if you have the BOE panel or not. We know the code works on the non BOE panel.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lmore377:
I just have the standard panel and that's working fine. Here's the issues I've encountered so far. I just installed opengapps and Magisk:

- It asks for a SIM card during setup but I just skipped it

- After a reboot it complains that selinux is disabled (I know you can disable the notification)

- SafteyNet just fails out right. I'll try that magisk module later

- WiFi band for hotspot can't be changed (I had this issue with another ROM so it's probably something with the wifi driver)

- It sometimes slows down a lot for a bit for no apparent reason (to the point where I can't open most apps for around 30 seconds to a minute) but setting the cpu governor to performance helps a bit

- ADB is kind of broken. Over USB it just reports that the device is offline and over the network it just allows a connection without asking if I want to trust my PC. Also if the option is off it turns back on after a reboot

- The lockscreen equalizer doesn't rotate with the screen (I know this issue is probably something with crdroid itself)

So far I think this ROM is really good and usable. I'll report back if I find anymore issues
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
It sounds like you are running the crdroid build above.

I don't run the crdroid build so I can't comment, but on the lineageos build, I don't see the SIM card setup. But then I install rom first, reboot into system, then reboot into recovery, then install gapps.

Magisk should work. I tried it before on the lineageos build and it worked so it should work on crdroid.

Never tested wifi hotspot so it could be a bug. Edit. Just tried it on lineageos build and the AP band is just greyed out.

I don't get the 30 seconds to 1 minute slowdown or freeze with 17.1. I used to get it with 16.0 lineageos build from Jul 2019 build. The CPU is overclocked in the 17.1 kernel code from 1.2Ghz to 1.6Ghz and GPU is 650.

Adb is rock solid over usb for me. It's how I did all the troubleshooting with adb logcat, adb shell, etc. I used for almost 3 weeks straight troubleshooting all the stuck at boot logo, boot loops, audio, etc.

Never use lockscreen so I don't know if its a bug or not.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
During the 30 second to 1 minute slowdown, it would help if you get a logcat so we can see what app or process is crashing or possibly causing it.

This assumes your usb adb logcat works.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen99:
ADB is solid for me, works over usb and wifi. I do get the Sim card prompt, but I don't think it matters. Safetynet works for me, with magisk hide turned on. The Hotspot wifi band is greyed out. And I only get that slowdown when connecting to wifi after being offline for a few hours, but it was a bug issue on Android 9. I think the visualizer being locked to the physical bottom of the device is intentional, I'm not sure though, but it looks cool 😆.

Retiredtab I can try to grab a logcat some time soon. But it may not be the same issue for me 🤔. The simtoms are the same, so it could be the same issue.