yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen99:
Hmmm, that's really weird! I have changed none of the vendor files form the ROM in the OP so the only thing that could be messing things up is the crdroid part of the ROM. You can look at the github to try to see if there is anything that would mess up the storage. Is it just the latest build? If you go back one does it work? Nubianprince hasn't built for Android 9 in a while, and I ran out of space on my drive so i'v just stuck to experimenting with android 10. I haven't had this issue, has anyone else reported it? How did you install the ROMs? Does twrp report any errors during the flash, and which version of twrp are you using?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] D1ab70:
sorry for the late update, had some things I needed to do this week.So I got around to tinkering with this things my mom keeps asking me about her tablet lol.Ok so i got the august update of 9.0 Rom and It worked no problem then I tried september update again and flashed it same way and it also works.So i am scratching my head here because I been flashing them all same way.Using the latest twrp here (think 3.3.1??).What I do is go into recovery I wipe all partitions but internal and sd then I reboot it back into recovery tho not sure if it needed step but for heck of it since it asks me to.All the zip files I have in twrp folder (internal partition).I choose install > then select the zip with the rom I download ( I verify all zip files with hashes after downloading)> then i press add more zips then selects gapps pico (arm pico)> then i swipe to install (for testing I don't flash magisk yet)> after it done I wipe davlik cache then reboot> when it boots to initial screen i wait like 5 min then I go through setup.Only error I get is one attached but it seems it is nothing.

I have also tried 10.0 variant again and it seems to work this time (file transfer through usb works too).So i do not know what the issue was other day but it seems to sort itself out.Apologies for false alarm but thank you for addressing my posts nontheless.

Tho Android 10 is nice, afraid I gonna have to roll back to 9.0 not because any bugs but because the device itself is memory limited 10.0 seems to eat more memory so by the time I install some things it already begins to go sluggish which is the reason I cleaned it out in the 1st place.I do hope 9.0 updates continue for now as for now it less memory usage and more smoother and fewer prospect for bugs.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen:
XDA is going through a big change, and is having some "growing pains". A bunch of threads are currently missing and I have no idea when they'll be back. One of those missing threads includes nubianprince's crdroid 6 for the SM-T350. If you would like to download it now, because I'm not sure when the thread will be back, I have a build on androidfilehost. Hopefully nothing is broken 🤣. I've been using it and it seems fine.

crDroidAndroid-10.0-20201126-gt58wifi-v6.12.zip | ROM by livid_hen for Galaxy Tab A 8.0

Rom built with nubianprince's device trees from github. https://github.com/Nubianprince

androidfilehost.com

PS. Again, this is the android 10 version of crdroid, if you want to upgrade from android 9 treat it like an entirely new rom. No dirty flashing.

PPS. I am lividhen99, I just can't login with my Google account, because of said growing pains.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] firestone1:
I'm trying to enable encryption on the device, however, it shows the green Android robot for a few seconds then the screen goes black (I notice screen is still backlit) and it brings me back to the home screen.

Has anyone been able to successfully enable encryption on crDroid 5.11 (Android Pie) Rom?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen:
You might be able to use adb shell. Make a backup first because I am not sure if this will brick it. I think it would be adb shell recovery --set_encrypted_filesystem=on. Do this at your own risk, I have not tried it.

You may have to do --wipe_data --set_encrypted_filesystem=on, then maybe you can get your stuff back with migrate, but i am not really sure.

Wipe data/Factory reset through ADB

Basically this is my problem/ I have 200+ phones running stock Android that need to be wiped (in the Wipe Data/Factory Reset way) and then a new ROM installed with some additional apks. Currently...

stackoverflow.com

Using this as a reference, sort of.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] chakrapw:
Do you have the custom ROM for SM-P355 (4G/LTE w/ S-Pen), please? I need to use android 8 or more.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen:
I don't think we have access to the source code for that device... So I'm not sure a custom rom in the traditional sense can be built for it... Maybe a touchwiz/oneui rom can be ported from another tab a, but I'm not sure if, any have simaler enough hardware (s-pen might be fine, I'd worry about modem)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Kernel source code for P355 is at

Samsung Open Source

opensource.samsung.com

I found it a couple of months ago when I was trying to build the spen P350 and looking for clues with respect to the kernel configuration parameters.

However, I will never build any LTE version. I don't want to hear the inevitable complaints from people about dropped calls, volume too low/high, distorted voices, latency, lag, etc when I have no control over the carrier's network and the Samsung blobs which will never get updated again.

If people want a P355 build, they can build it themselves using the resources that we have provided through the 17.1 source code. I have documented all my source code changes in my own threads. And/or people can look at nubianprince's repos on github.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
I will be closing this thread soon no sense keeping it open
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] chakrapw:
Could you please help me for P-355?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Badger50:
Ping me back if you want it closed. Thanks. (y)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
@Badger50 you can go ahead and close this thanks.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Badger50:
Thread closed per OP request.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Evervolv has a patch for the google play store. See

https://xdaforums.com/showpost.php?p=79198628&postcount=158
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
Thanks, I already did new build with the changes and will update shortly
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
OK, my most recent crDroid build with the current changes done by [MENTION=2219132]elginsk8r[/MENTION] fixed the playstore issues but the audio went back to being broken

Will do another build with the same blobs and make sure I didn't miss anything

OK, figured out what I was doing wrong hope to have a new build posted in a few hours.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Downloading as I write this.

I will verify audio, google play store and test for battery sleep.

Thanks for creating this build.

PS. For future builds, can you please include a md5 or sha256 since the file is close to 400MB? This will help rule out bad downloads or incomplete files.

---------- Post added at 11:05 PM ---------- Previous post was at 10:34 PM ----------

1. Google play works. I can see Clash Royale, Clash of Clans and Google Chrome.

2. Audio works.

3. Camera works.

4. Bluetooth does not. There is a reproducible bug.

Choose settings, connected devices, connection preferences, bluetooth, slide to ON, pair a new device. No devices are found. Hit back button. Bluetooth is turned off for some reason when it should be ON.

5. Quick settings to turn on/off bluetooth also doesn't work. If you turn it on, it gets turned off right away.

---------- Post added at 11:16 PM ---------- Previous post was at 11:05 PM ----------

There are messages in logcat with bluetooth warning and errors. Those might help narrow down the problem?

I won't upload them since it is probably faster for you just to hookup a PC and adb shell in to see the logcat.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] elginsk8r:
I might suggest picking this commit https://github.com/Evervolv/android...mmit/d72dd2ccff024ed4e0faba4852ab1dbd0832cc9d
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
Thanks.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
More results with March 26 build.

1. Changing display brightness through settings display does not work. It appears to be the same brightness at 0 or 100%. I think this worked March 18 build as I find the default brightness level too bright and I was able to lower it on the March 18 build.

Display brightness is also not working evervolv March 27 build.

2. Cdroid with airplane mode ON, wifi/bluetooth off and location off in sleep/standby mode loses 1% over a 12 hour period. That is, no problems.

---------- Post added at 10:26 AM ---------- Previous post was at 10:15 AM ----------

3. Turning on battery saver takes about 5 to 7 seconds. Same for turning off. For comparison, evervolv build March 27 takes about 2 seconds for on/off.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
Build 2019-03-28 uploaded, should have most of the previous bugs fixed.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
So far my test T350 has been regularly switching from evervolv to lineageos to crdroid, but after some more testing with the Mar 26 build, everything seems to be working okay aside from the bugs that are already fixed in the Mar 27 and 28 build.

The Mar 26 build still can't pass the ctsProfile test in magisk manager, but I have full access to google play store. I think I can trick the ctsProfile by loading a known good fingerprint, but for now, I'm not too worried. This could be a big problem in the future if google changes something on the play store end.

Someone asked a question about overclocking the T350. I noticed these commits over at github

https://github.com/Galaxy-MSM8916/android_kernel_samsung_msm8916/commits/lineage-16.0-oc

The 3 by vince2678 dated May 2017 look easy enough to pull and test?

Obviously, there are pros and cons to overclocking the CPU.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Using magisk, magiskhide props config, I can spoof the fingerprint and pass ctsprofile check. When I then sign into google play, crdroid and sm-t350 show up as device certified.

I chose to spoof a Samsung Galaxy S9.

https://www.didgeridoohan.com/magisk/MagiskHideSafetyNet
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
I have an idea that may pass the majisk safenet test, I am pretty sure one of my previous builds passed it, will run another build to test..

Build 2019-03-31 uploaded, should pass Majisk Safenet check
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Downloading. Will test safetynet, OC and other bug fixes and report back later.

Obviously with OC, I can't predict what will happen long term on the CPU, but I will do simple tests to see if the extra frequencies are enabled.

---------- Post added at 11:31 AM ---------- Previous post was at 11:08 AM ----------

BTW, thanks for the MD5. Downloading big files especially over wifi, for me, with at least 20 other wifi signals around me, often results in timeouts, retries, etc. So having the MD5 helps knowing a 400MB downloaded correctly.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Results with Mar 31 build.

1. screen brightness control - FIXED

2. Bluetooth turning off after being turned on - FIXED

3. OC frequencies show up. I was surprised it defaults to 1.6Ghz at bootup. I thought, perhaps naively, that it would start at 1.2Ghz (stock) and by using a kernel auditor or similar tool, the user would then set max CPU at 1.6Ghz or whatever.

I'll take a look through github to see if there is another commit to pickup to set the default to 1.2Ghz. BTW, I'm not the one who asked for this feature. I just saw the commits and they looked easy enough to add.

I suggest putting a big red font text next to the OC build that your tablet may not boot at a default of 1.6Ghz. Just because it booted at 1.6Ghz for me doesn't mean it will boot for others.

I will experiment with 1.4Ghz to test for stability first and then try other frequencies later over the next few days. I'm going to use SmartPack Kernel Manager to set the CPU speed.

https://xdaforums.com/android/apps-games/app-smartpack-kernel-manager-t3854717

I have not yet looked at the GPU OC at all.

4. Deep sleep still works with the OC. Verified with BBS and SmartPack Kernel Manager.

5. Battery saver still takes about 7 to 8 seconds to switch back over, but this could be a crdroid implementation thing?

6. Your fingerprint patch works for ctsprofile in magisk. It passes ctsprofile and google play sees my device as certified. I see spoofed the original stock 7.1.1 fingerprint. I can see Clash Royale, CoC and Google Chrome.

7. Opening the smart cover wakes the tablet, but it doesn't put the tablet to sleep when closing. Adding FlipFlap (smart cover) might fix this?

https://github.com/jfuginay/android_packages_apps_FlipFlap
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
[MENTION=8726605]retiredtab[/MENTION] thanks for doing the testing, I started these pie builds with bare bones device tree, I had FlipFlap in my oreo builds will started add some of those to the pie builds.

The Battery Saver is working fine for me I do not see any delays when I toggle it on or off, I did notice that crDroid disables a lot of things in the background when switched on. I will do a clean flash to see if I can replicate the issue.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
It's not a big deal. When I'm testing functionality, I'm just toggling back and forth to make sure it goes on/off. In real life, if I enable battery saver, I would just do it once and leave it alone.

With the Mar 31 lineageos build, toggling battery saver takes only 2 to 3 seconds so crdroid is doing something extra.

Perhaps crdroid's battery saver implementation is better than lineageos? That is something that would be hard to test and replicate.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
Ok cool, running a build right now to include FlipFlap as well as some tweaks to improve internet speeds and enable quick power on.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
Current build(2019-03-31) includes FlipFlap and some performance tweaks (net speeds + quick power on)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
I verified that crDroid Mar 18 smart cover on/off works, but not the second Mar 31 build. See

https://xdaforums.com/showpost.php?p=79240774&postcount=181

So whatever is in the Mar 18 build, that is the patch we need.

---------- Post added at 11:26 PM ---------- Previous post was at 11:07 PM ----------

I also verified that there is a problem playing MP3 file format. I get static, but can hear the music. Music sounds like it is played at 75% of its normal speed.

WAV works fine.

Since crDroid and Lineageos use evervolv's sound audio fix/patch, it probably needs to be fixed there.

I'll post in evervolv's thread to confirm.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
[MENTION=8726605]retiredtab[/MENTION] I tried playing a MP3 file with VLC and it played fine but got the static when I tried other audio apps will try a few things as for FlipFlap I forgot to include a few config files I will add those and see if it solves the FlipFlap issues.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Some more results.

Mar 23 build - smart cover doesn't work

Mar 31 build #2 - built in audio player doesn't play MP3

Mar 31 build #2 - using VLC, playing MP3 works
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
I do not have the smart cover so can't test FlipFlap [MENTION=8726605]retiredtab[/MENTION] do you mind testing build 2019-04-01 and let me know if flipflap works? I will be trying some tweaks to try and fix the MP3 playback issues.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
I will download this later at night.

To test flipflap, get a strong magnet and put it in this area where I marked in red. That is where the hall sensor is.

Put it down in the red spot. Lift up. It should wake tablet. Put magnet back in same spot, tablet should goto sleep.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] bluenote73:
Overclocking. Swoooooon! Thank you Nubian!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
I downloaded Apr 1 build and flipflap works, but not instantly. Normally, closing the cover puts the tablet to sleep generally within 1 second.

Closing the cover on the April 1 build takes about 5 to 6 seconds before the tablet goes to sleep. So it works, but not instantly like stock.

With this new info, I retested

Stock 7.1.1 - instant

crDroid Mar 18 - instant

crDroid Mar 31 (2nd build) - 8 seconds

crDroid April 1 - 5 seconds

Lineageos Mar 31 - no sleep when closed (waited 30 seconds)

Personally, I don't need instant so if 5 seconds is the best, it's good enough for me.

Sorry, I didn't notice the sleep delay on the Mar 31 build. I'm used to instantaneous and didn't expect a 8 second delay.

---------- Post added at 10:04 PM ---------- Previous post was at 09:26 PM ----------

@nubianprince, silly question.

On the Mar 18 build, what app or setting controls the smart cover?

On the April 1 build, I can see the flipflap app in the settings (show system).

Just wondering why the Mar 18 build seemingly has it built in whereas April 1 build requires an external app?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] bluenote73:
Just trying this out and really liking it. I also thought the default 1600 mhz top cpu speed might not be good to be enabled from the start, but, it's completely stable for me so far. I wonder if I just got lucky on the binning or whether these chips are reliably over-engineered.

I have one complaint, and that is "Roboto" makes me want to poke my eyes out as a font. I changed it, but for some reason Chrome still wants to use it as the default. Is anyone aware of how I might fix that?

Thx
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
[MENTION=8726605]retiredtab[/MENTION] the only difference was that I imported the FlipFlap packages from lineageos, that has been removed from my current build.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
I will change that in the next build :)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
I'm not a big fan of the Roboto font either. In addition, can you change the default

"settings", developer options, "minimum width"

to 768 dp?

With the current Roboto and the dpi, the keyboard sometimes blocks out the "ok" or "cancel" button in certain applications.

---------- Post added at 02:37 PM ---------- Previous post was at 02:33 PM ----------

I found the commits through this thread.

https://xdaforums.com/showpost.php?p=71883660&postcount=8

vince2678 who authored the commits says

"I've been using it myself for about a month with no adverse effects.

I chose 1612Mhz because it's fast enough without risking instability."

Personally, I'm still undecided to go with stock, 1.4 or try 1.6 long term. I will make a decision once the remaining bugs get worked out. I'm leaning towards 1.4.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
So I started with a clean April 1 build (wipe dalvik, cache, system data) and now the spoofed stock 7.1.1 signature doesn't work in google play store. It shows "device is not certified".

I tried wiping google play store cache, data, etc.

Not a big deal, but I will retest this in future builds. I'm using the same tablet and same userid.

PS. Another possible tweak is to turn off window animation, transition and animator duration. It gives the appearance of making the tablet faster in the menu UI.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Ran into my first serious problem with April 1 build.

Tablet worked fine. Left it sitting in sleep mode for about 4.5 hours. Hit the home button to wake it (I'm not using the smart cover right now) and it would not go to home screen.

Tablet showed a blue box with the time in the upper screen, but would not respond to any touch. Tried power off, but that didn't work. I had to disconnect the battery. With this test tablet, I learned to leave it only 1/2 snapped in so I can disconnect battery to reset.

That blue box with the time is what I see when flipflap shuts down the tablet in 5 seconds.

The bigger brother, T550, suffers from the same problem. See

https://xdaforums.com/showpost.php?p=79033884&postcount=82

https://xdaforums.com/showpost.php?p=79082476&postcount=91

The "fix" is to use the smart cover

https://xdaforums.com/showpost.php?p=79145298&postcount=104

We should be monitoring the T550 threads for similar problems and fixes since it's the big brother of the T350 and share the same hardware platform.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
Uploaded build 2019-04-03 I removed the FlipFlap package and just compiled with the config files

.

I usually follow virsys thread to see what changes he is implementing.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
Newest build 2019-04-03 reverted Roboto back to default, I also changed the screen denisty and additional tweaks for faster scrolling etc.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Do you mean this?

config_lidcontrolssleep

<!-- Indicate whether closing the lid causes the device to go to sleep and opening

it causes the device to wake up.

The default is false. -->

<bool name="config_lidControlsSleep">true</bool>

---------- Post added at 03:00 PM ---------- Previous post was at 02:36 PM ----------

With April 3 build, waking tablet works, but putting it to sleep fails with smart cover.

For now, I can just let it time out to goto sleep or double tap the status bar.

---------- Post added at 03:40 PM ---------- Previous post was at 03:00 PM ----------

April 3 build. Camera doesn't work.

Click on camera and it says

"Camera keeps stopping"

It doesn't matter if you deny or allow Camera access to location. It still says "Camera keeps stopping".

---------- Post added at 04:00 PM ---------- Previous post was at 03:40 PM ----------

Camera is also broken on April 1 build with same error message.

Last working camera was Mar 31 build #2.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] katochwa:
The best is 3/18 build, everything work find (I am not use Google framework)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
A clue wrt to the smart cover? This

<!-- Indicate whether closing the lid causes the device to go to sleep and opening

it causes the device to wake up.

The default is false. -->

<bool name="config_lidControlsSleep">true</bool>

isn't present in the evervolv file at

https://github.com/Evervolv/android...rameworks/base/core/res/res/values/config.xml

---------- Post added at 11:44 AM ---------- Previous post was at 11:32 AM ----------

Maybe putting in that parameter to

android_device_samsung_gt58wifi/overlay/frameworks/base/core/res/res/values/config.xml

will solve the sleep cover problem?

---------- Post added at 11:53 AM ---------- Previous post was at 11:44 AM ----------

That would go into your repository at

https://github.com/Nubianprince/gt5...rameworks/base/core/res/res/values/config.xml
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
[MENTION=8726605]retiredtab[/MENTION] already included this in my latest build will upload when it is complete.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
No rush. I'm going to be travelling this weekend with no internet so I won't get much done.