yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
This seems to only occur if media files are stored on an external card, if the files are stored on the devices it works files, not sure if that is how that app is intended to function.

Maybe some else can verify this.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
- It asks for a SIM card during setup but I just skipped it Normal

- After a reboot it complains that selinux is disabled (I know you can disable the notification) Normal the kernel is permissive, lineage trust will flag this

- 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) Never known this as an option that can be changed

- 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 Is usb debugging enabled?

- The lockscreen equalizer doesn't rotate with the screen (I know this issue is probably something with crdroid itself) Did this work for you before?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen99:
Ooh, yeah. Just looked, phonograph doesn't have the ext_sdcard permission, and storage access changed in Android 10, right? I presume that would break things, wouldn't it... 🤔😆
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
Poweramp has no problems with playlists when media is stored on external card, I also tried the music app on resurrection remix on ane of my Samsung phones same issues,
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen99:
I'm aware. I just like phonograph. But I'm not against using another media player.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen99:
Has anyone tested data encryption? I know at one point in Android 9 it caused the device to freeze on boot.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Nope. Never use it so never tested it. I don't have anything important on the tablets. Just throwaway email addresses for signon purposes. No personal info and obviously no banking, emails, etc, etc.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] bluenote73:
In case anyone happens to know, is pico gapps required or is that just NP's preference? The, finally going to try this..
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
At some point, there won't be enough free disk space for both the OS and gapps AFAIK. Ideally, you shouldn't install any gapps to get best performance. There's lots of alternatives to gapps and getting the apps that you want running. Search for "degoogle", fdroid, microg, newpipe, youtube vanced, etc.

If you must use gapps, then select pico. It uses the least amount of disk space, ram and system resources.

This article is a bit old, but lineageos developers recommend against opengapps.

https://www.xda-developers.com/gapps-package-recommended-rom-developer/

"So why does LineageOS still recommend MindTheGapps? The reason for that is because there can be issues with using a package that hasn’t been tested by the developer. For example, the LineageOS developers note that removing the stock dialer app (which happens when flashing the “super” or “stock” Open GApps packages) can result in emergency calls failing to work, as the framework relies on a very specific intent to send. Using a different dialer app such as Google Dialer, for example, can break emergency calling functionality."

And yes, for some of my tablets, I'm completely gapps/google free.

I realize it's not for everybody depending on your requirements.

PS. I'm not a "developer". I can compile and fix simple bugs and problems, but that's all.

---------- Post added at 08:28 PM ---------- Previous post was at 08:22 PM ----------

Also, I do have a couple of older Android devices where, luckily, someone has written a zip script to repartition the system to be a bit bigger to fit newer and larger OS with enough room for gapps pico.

There's no way, I would have enough knowledge and confidence to write such a script or utility.

---------- Post added at 08:56 PM ---------- Previous post was at 08:28 PM ----------

More regarding /system

https://github.com/Lanchon/REPIT/issues/56
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen99:
GMS is very heavy on resources, and having more apps installed, taking up space, and running virtually 100% of the time, the worse of an experience you are going to have.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] bluenote73:
notwithstanding I used nano, and I'm pretty impressed how this ROM works :)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
What firmware did you have installed before flashing the ROM? Have you tried flashing the latest firmware(Nougat) for the device and then flash crDroid without gApps or Magisk.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
GApps is optional, I suggested pico for those that need the playstore without installing other Google apps.

But there are other options out there that can be used
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen99:
Defiantly not a big issue at all, but all voip calls seem to default to the wrong speaker. Discord and hangouts default to "phone" but to actually hear you need to change it to "speaker". It's only an extra 2 seconds of time. I just thought I would put the issue out there.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Barrohn:
I had an update ROM, not the latest stock ROM installed.

Once I went back to Nougat I was once again able to install the custom ROM and it then crDroidAndroid-10.0 worked on the two that I installed it on.

The only thing now is that it seems to hang the tablets once in awhile.

Thanks,

Byron
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen99:
Trying to mirror the screen to a wireless display seems to crash something. Either the system or the system ui. I was attempting with a roku TV. I can try to grab a logcat soon.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] bluenote73:
I quite liked the running services pulldown shortcut, any chance that's available and can be put in the next build NP? Btw, running great here with a reboot every so often.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen99:
I grabbed the logcat of the wireless display crash and, uh, it dies quite dramatically 😂. It looks like a permission error to me, but I could be wrong. "listenForRemoteDisplay is no longer supported!" Also looks important maybe.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen99:
Sorry for the double post, using labs app. Here's starting from a bit earlier in the log.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Found numerous references saying that

https://xdaforums.com/t/rom-unoffic...agon-2021-01-05.3591152/page-56#post-79631927

"Native" ScreenCast/MiraCast support has been dropped in Pie.

If true, other posts suggest for qcom devices, there are some custom solutions available.

Gerrit changes show some qcom implementations

https://review.lineageos.org/c/LineageOS/android_device_xiaomi_sdm660-common/+/266513

https://review.lineageos.org/c/LineageOS/android_device_essential_mata/+/273247

Whether it's supported or not, the code should handle it more better without crashing or rebooting.

---------- Post added at 12:27 PM ---------- Previous post was at 12:25 PM ----------

@bluenote73, it that a random reboot or are you manually rebooting for some reason? If random reboot, what was running when it rebooted? How often does it reboot? More details help.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] bluenote73:
Actually I meant a maintenance reboot (for memory I suspect). But now that you ask I've had a handful of straight shutdowns. I suspect this build runs just a hair enough hotter (or I'm configging something a little too aggressively, I'm not sure at this point)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
If it runs too hot, try some kernel auditor program where you can control the CPU. It overclocks the defaults to 1.6Ghz and 650Mhz for the CPU and GPU in the 17.1 kernel code. You can try lowering it to stock 1.2Ghz and 450Mhz which is "stock".

I do notice some lag when I play a mobile game for too long. Once I let it cool down, it returns back to "normal".
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] bluenote73:
Yeah I know it's overclocked. I ran the 9.x OC build flat out though and it was fine, and it doesn't happen enough probably for me to catch it. But I'll try to watch it a little more closely and see if I can determine whether it is in fact heat. (A straight shutdown I think pretty much has to be ...) but it could be that I set some performance option even a little further on top of the OC and that's the difference.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen99:
Hmmm... It looks like the stock rom does not have wdf or any wifi display hals... I wonder if any other tab As have them. who knows, I could be missing something. Or a different solution would have to be figured out or something. Idk.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
I looked at stock 7.1 and there are no wdl files. One could possibly take the code from Android 8 and try it in 10 by looking at the gerrit code changes to remove the feature and reverting those changes.

Even if I did try to use 8.x code and got it to compile without errors in 10.0, I have no way of testing it.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
For s-pen, see

https://xdaforums.com/galaxy-tab-a/development/sm-p350-rom-s-pen-support-beta-testers-t4187731

Only the advanced user should attempt the s-pen build (either crDroid or lineageos) because reverting back to stock may be difficult for a new user. Neither I or nubianprice have a SM-P350 to test on. Adding the s-pen driver code to either crDroid or lineageos doesn't seeem to hurt anything so far.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen99:
Miracast casting now fails, I guess, more gracefully. Still crashes the system, but there is no backlight flickering.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Rahul.raj:
How different are T350 and T355Y (gt58ltedo) devices from each other? Is it possible for a relatively novice guy to adapt this ROM for T355Y? (Or is it a stupid question and the ROM can be used directly?)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
I've played geometry dash using screen cast for 10 minutes without any issues.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen99:
That sounds difficult 😂. Was it using chromecast or, or was it a roku or something similar (have to check the box for wireless display in the top right)?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
Maybe i am misunderstanding this but i am using the built in screen cast or are you using another app?

For me its screen cast(quick settings) choose my TV(Android TV) then select start now
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen99:
There are 2 types of mirroring widely used. Miracast and chromecast. Chromecast is google's proprietary screen mirroring API. Miracast is another API used by everything else (roku, windows, etc). Miracast support was added in Android 4.2 I think, then Google replaced it with thir proprietary chromecast API in Android 6. Almost every other OEM except Google keeped the miracast API along with chromecast until Android 10 when it was removed from the source code. Some Qualcomm devices have abstraction layers specifically dedicated to wifi display using miracast. On crdroid 5 you could use miracast without adding anything else to the OS, as I believe it was done in software. In crdroid 6 that has been removed. You can still see them but trying to cast (I believe) tries to call on the wifi display hal for the miracast API, but fails. So, Chromecast, with chromecasts and antroid tvs will work in software, but miracast is broken.

Wow, sorry, that was long 😅

It's not a super nessisary feature for me, I just noticed it was broken and felt I should mention it.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
BOE panel fix

For people who get black or blank screens when trying to flash TWRP 3.3.1 or lineageos or crDroid SM-T350 roms, it's likely you have a BOE sourced panel. There is a fix as documented with the help of @lpedia. See pages 61 and 62 at

https://xdaforums.com/galaxy-tab-a/development/recovery-t3426560/page61

https://xdaforums.com/galaxy-tab-a/development/recovery-t3426560/page62

The above tells you why the problem exists and how flashing a 1MB aboot.mbn fixes it.

Feb 7, 2021 update. See post #671

https://xdaforums.com/t/recovery-tw...350-355-550-555.3426560/page-34#post-84449941
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] vipulkohli:
Just of curiosity - what are the devices other than this tab are the developers of this rom using??
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Luke357:
Error 7

Everytime i have tried to install the ROM i get error 7 telling me that my device isn't one of the 3 device names in the list. But i know it is because in stock rom it shows that it is a SM-T350 and on the back plastic it also shows that is a SM-T350. Does anyone know what the issue is?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Are you using TWRP 3.3.1 as in post #1?

If yes, what is the exact message on the screen?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Luke357:
I am using an older version of twrp because the one in your signature wouldn't work in odin I haven't been able to replicate the issue because windows decided it didn't want to read the sd card I use to install the os and gapps on. https://photos.google.com/photo/AF1QipP-000S2kWwW3xq9ET31zcfPS4UpFwV9h5U8CPg
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen99:
Read that wrong, let me re write my response 😆

What version of odin is it? Also, have you tried the various odin, I guess, "quirk resolutions" (different USB cable, different port, only plug in the device after odin opens)? As for the sdcard, that's really strange. Is it formated as internal shared storage? If so windows can't read it. Try reformatting as fat32 or extFAT, or if windows won't let you do that, use a camera of some sort, or the tablet it's self. The older versions of twrp won't work on Android 9 and 10. You can remove the verification but I remember there being other bugs.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Luke357:
I have tried different versions of odin I was using 13.1.1 but I also tried version 12.7,12.3, and 11.1 but still had the same issue. I also tried different usb ports and cables but also same issue. Could it be the way I converted the img file to a tar file? I used 7z to convert it to tar. the sd card can be read by windows if I put it in another tablet btw so no issue there.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen99:
Use the old twrp to flash the new img. Make sure to select recovery, not boot.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Luke357:
Thanks! I did that and the OS installed like it should have.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen99:
WOO! Glad i could help!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] IHATEWin10:
Error

I use TWRP 3.1.1-1 and give error. :/

Updater process ended with ERROR: 7

What is the cause of the error?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen99:
Error 7 means the device in the ROM manifest is different than yours. This is sometimes wrong, but make sure you have an sm-t350. 3.1.1 is too old, and can't flash android 10 (or maybe Android 9) roms. Try using the 3.3.1 from the OP.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] IHATEWin10:
Thanks for informations. :)

And how can I update TWRP?

I installed TWRP from the tar.gz file with Odin.

But this file is .img
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
Go 5 or 6 posts back and you will find the answer to your question.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Sahil_Sonar:
Is this for Samsung Tab A 8.0 (2019)?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
No.

SM-T290 = Samsung Tab A 8.0 (2019)

SM-T350 = Samsung Tab A 8.0 (2015)

https://www.gsmarena.com/samsung_galaxy_tab_a_8_0_(2019)-9760.php

https://www.gsmarena.com/samsung_galaxy_tab_a_8_0_(2015)-7121.php

If you want to build lineageos for T290, the PIE source code for the kernel is at

https://opensource.samsung.com/uploadSearch?searchValue=t290
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] bluenote73:
Finally this thread is back :)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Zinnath Ara:
How to know if my device has a BOE panel or not?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
New build uploaded with December security patches check the main post.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
For issues related to this bootbloader fix, you will probably get a better answer by posting to that thread.

you can flash the stock samsung firmware for the device via odin
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Zinnath Ara:
Thanks for your suggestion.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] bank8844:
Does this rom work with SM-P355 ?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
@nubianprince, this why I have a FAQ in my threads.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
:) looks like I have no choice but to do that now
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] bluenote73:
Any of you guys confirm that when using the stock AOSP keyboard included, if you switch to number keyboard you cannot switch back to ABC keyboard?

thx
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Please describe step by step exactly what you are doing so we can try and replicate. An adb logcat while you are doing the above helps.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
New build is up in the main post with 2021-01-05 Security patches, crDroid has been slow with their updates.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
I haven't seen any issues with the AOSP keyboard, switching back and forth between Numeric and ABC works fine
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] bluenote73:
Thanks, maybe its full wipe time. Although I think I would have done that to go to 10.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Dirty flashes can sometimes leave unwanted behaviour especially between major versions of Android like 9 to 10. Also, wipe data is not the same as format data.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
If you still have problems after a wipe/format data, describe the steps exactly and provide a logcat.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
TWRP 3.5.0 for the SM-T350 added to the main post.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Thanks for updating your repo with the twrp. I'm going to try using it to build an updated twrp for SM-T560NU later on by replacing the approriate files.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
DO NOT USE TWRP 3.5.0.10 until nubianprince and I discuss. I found one bug and another potentially serious one that will cause a boot loop and you will have to revert back to stock to fix. For the latter, more research is required to figure out what's going on.

Use 3.3.1, it's what I have used to flash the T350 over 100 times during development.

I already sent nubianprince a PM, but this will take some time to figure out. I know he's busy and 3.3.1 works fine so there's no urgent need to fix this right away.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] bluenote73:
I was just literally going to post that the link is missing. :)

Also, it seems the link to the ROM doesn't work either which is weird.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
For the one bug, 99% of you won't see it because only people developing the rom use it. TWRP allows you to do an adb shell for debugging/troubleshooting purposes, but it wasn't working on my tablet. It does, however, work on nubianprinces. We are discussing this in PM.

For the potentially serious second bug, this may be related to the version of bootloader that you currently have loaded similar to the BOE problem. Right now, I'm downloading the nougat stock rom that was originally on my tablet, but it's going to take 7 hours because it's limiting the speed to 15kbps (if it doesn't fail in between).

I should have results whether it's reproducible in the next few days. If it's not reproducible, then I may have had an "one off" event? Given the history of the SM-T350 and it's quirks with audio and BOE, I'm naturally suspicious. The BOE problem took months to figure out.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
Thanks for the heads up not sure what happened there, fixed now
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Okay, I got my original nougat downloaded, flashed my tablet and went through what I recall are the exact same steps yesterday and I cannot recreate the problem. My rom boots correctly and adb works in TWRP with 3.5.0_10.

So I'm not 100% sure what went wrong yesterday. It could a have been a one-off bad flash. I probably have flashed 400+ times (100+ times per rom that I build) and maybe I was due for a bad flash? If it was a bad flash yesterday, there were no obvious error messages.

If you use any TWRP or rom, as always, make a backup of your files first.

BTW, this is NOT nubianprince's fault or a reflection of his code or testing. He tests all his builds just like I do, but we cannot replicate every possible scenario. So if I did have an "one-off" bad flash, it's not his fault.

In addition, I have run into TWRP bugs on other platforms that I have used in version 3.4.0.0 with adb not working.

Again, the only reason I flagged it with the "do not use twrp" was due to the SM-T350 finicky nature and it's bootloader with respect to BOE panels.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
For those who don't know TWRP 3.5.0 is the major version of the software. The _10 indicates that it's meant for devices that shipped with Android 10. See

TWRP 3.5.0 released with support for devices that launched with Android 10

TWRP 3.5.0 is here, and it finally brings support for devices that launched with Android 10. Read on to know more!

www.xda-developers.com

TWRP 3.5.0_9 where _9 indicates it's for Android 9.0 or lower devices.

I suspect, but have no proof, that it's possible that 3.5.0_10 may have bug in it since it's the first release that supports A/B and system/vendor partitions. Maybe that initial flash wiped out one of my stock partitions by overwriting it with vendor partition or something and that's why reflashing complete stock fixed it since our roms don't flash all the partitions like stock does?

If/when nubianprince finds time to make another TWRP, it will likely be version 3.5.0_9 since the SM-T350 is deemed a "legacy device" in the article above. I think it's safer as well because our device isn't treble based and likely never will.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] vsguru:
Just flashed v6.14 over the top of v6.13 with TWRP 3.3.1. No issues. Runs sweet with only rare lags. Very happy with this ROM!