yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
crDroid has OC in the Mar 31 build. See my comments there.

https://xdaforums.com/showpost.php?p=79239262&postcount=33

OC has its pros and cons. Running the CPU at 1.6Ghz over long periods of time may result in instability, crashes, hardware failures, etc.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] bluenote73:
Not to worry, I'm an old hand and understand the downsides. That's fantastic, what a pleasant surprise. Maybe jfuginay will be able to pull those changes. (Err, but not max overclock at boot by default!) :) Thanks for the tip
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Depending on what you do with your tablet, you can make it speedier by using alternative applications. It's not always about raw CPU horsepower.

For example, instead of Chrome, use Brave that has a built in ad blocker. Install Magisk and install an adblocker using hosts file.

If you don't need google play, don't install it. You can use apps from f-droid or sideload apk assuming you have no personal or confidential information on your tablet.

These are just examples as I have no idea what you use your tablet for.

---------- Post added at 06:44 PM ---------- Previous post was at 06:42 PM ----------

I looked at the OC 3 commits. There is nothing complicated with them. The hard part is putting in code so that the CPU defaults to stock 1.2Ghz and then the user has to adjust to his liking.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] iesous-kurios:
I might experiment with that after I fix the flip flap issue. (Or port in somebody else's fix for the flip flap, I'm hardly skilled enough to call myself a dev yet lol)

If I do, I won't cook it straight into the ROM as I'd like it to stay as close to lineage as possible.

I'd start another thread with a flashable zip for enabling over clock.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
I just posted my results in the crDroid thread 30 seconds ago.

Agreed, it makes maintaining code a lot easier in the future and possible migration to Q.

I'm still not sure how to default to 1.2Ghz. It might take code, but even if its 5 lines of code, where does it go inside the millions of lines of Android code?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] iesous-kurios:
Probably in the kernel. I'll play around with it and see what happens :)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] iesous-kurios:
I don't see any recent changes on github regarding flip flap, must not have pushed his local changes yet.

I found that removing the flip flap app altogether still lets the screen turn on when lid is lifted.

I tried putting the dependencies in the same area my note 3 has them but that didn't work, so still trying to figure that out.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Yes, that always worked. Just putting the tablet to sleep was the issue.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] iesous-kurios:
Implemented that config file fix from what you and nubianprince were discussing.

New build up with all things working :)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] leomattel:
TWRP still seems to be finicky on SM-350

Hello, [MENTION=4899305]ashyx[/MENTION] and [MENTION=8726605]retiredtab[/MENTION] - The only TWRP that seems to work on my Galaxy A Tab SM-T350 seems to be the one for Nougat (twrp_3.1.1-1_sm-t355_251117), I have tried 3.2.1-lineage-15.1 (below from Austcool), 3.2.3-0 (from here) and 3.2.3-1 (earlier reported by [MENTION=8726605]retiredtab[/MENTION] as non-functional) all takes me to a blank screen and does not allow me to go past it to the system itself. Is there any specific odin to use to get the TWRP to play well? I want to try either lineageOS 16 or the CDDroid. Both of which cannot be installed with "twrp_3.1.1-1_sm-t355_251117". Your help is very much appreciated. I currently have a blank SM-T350 which ideally can be a paperweight. :(
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
[MENTION=5172756]leomattel[/MENTION] what firmware is your device on, the newer versions of TWRP will not work well on older firmware.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] leomattel:
Thanks, [MENTION=6865385]nubianprince[/MENTION] - I am on "T350XXU1CQJ1". The latest one seems to be "T350XXU1CQJ5". Should I be on the latter? Is there any other place that I can download the firmware apart from here --> samdb.org [/] download [/] GALAXY__Tab__A__ [/] 753v [/] XAR [/] T350XXU1CQJ5 [/] T350XAR1CQJ5?

Update: Never mind. I was lazy and did not look up properly. I found one here (I am not allowed to post external links until 10 posts - newbie rules)--> updato.com [/] firmware-archive-select-model [?] q=SM-T350+&exact=1&r=&v=Nougat%28Android+7.1.1%29&rpp=15. Will the latest one help?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] leomattel:
Update2: I downloaded the latest firmware (XAR --> T350XXU1CQJ5), flashed it as well. Flashed all TWRPs - the only one that works is - without going to blank screen is twrp_3.1.1-1_sm-t355_251117.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
[MENTION=5172756]leomattel[/MENTION] If you are already on CQJ1 (I believe this is nougat firmware) that should be fine try flashing this in TWRP TWRP 3.2.3 If you are still having issues there could be something wrong with a partition on the device.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] leomattel:
More context regarding my installation

I carried out the steps detailed here. In summary -

Using Odin3_v3.12.3 flashed "T350XXU1CQJ5_T350XAR1CQJ5_HOME.tar.md5" for firmware

Again using Odin, flashed twrp "twrp_3.2.3-1_sm-t350_23319.tar"

Booted to TWRP, followed steps 2 and 3 under "Installation/Flashing the ROM with TWRP" from here. Quoting the steps from that post below

"Reboot in to TWRP, and do Data Format [Wipe]/[FormatData], type "yes", and once it done, go back to main screen again.

In TWRP main screen, go to -->Wipe-->Advanced Wipe, and check only; "System", "Data", "Cache", and "Dalvik/Art cache" - do NOT select any other options!, once it done, go back to main screen."

Flashed "lineage-16.0-20190406-UNOFFICIAL-gt58wifi.zip". Did not install GApps, as [MENTION=8726605]retiredtab[/MENTION] stated that there is a problem.

Rebooted to system

After the initial Samsung screen, tablet goes blank.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] katochwa:
Jfuginay, thank you for the rom, every thing work very good, now only the mp3 problem left.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
Earlier you stated twrp_3.2.3-1_sm-t350_23319 wasn't booting, now you say it does?

As I stated earlier, if you are having blank screen issues booting to TWRP built with Lineage kernel and blank screen with Lineage OS then the common factor is the Lineage kernel.

You likely have one of those finicky Samsung devices.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
[MENTION=5172756]leomattel[/MENTION] let us take this in stages, first let us see if we can get the latest TWRP flashed (Do not flash the ROM).

I suggest starting with an older version of TWRP 3.1.0-1 by ashyx flash using odin then reboot back to recovery and flash TWRP 3.2.3 Reboot back to recovery.

Let us know if that works
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] iesous-kurios:
Temporary work around is downloading vlc player
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
[MENTION=5172756]leomattel[/MENTION]

Does this boot?:

https://androidfilehost.com/?fid=1395089523397935892
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] leomattel:
Thank you, [MENTION=6865385]nubianprince[/MENTION]. Here are my results. I had formatted and wiped all of it (well, I had nothing anyway apart from the latest firmware) before starting the test -

With Odin3_v3.12.3

twrp_3.1.0-1_sm-t350_18317.tar	- Blank Screen

twrp_3.1.0-1_sm-t355_16317.tar	- Stays on the Samsung boot screen forever - Galaxy Tab A with message at the top saying "Set bot warranty: recovery"

twrp_3.1.1-1_sm-t355_251117.tar	- Goes to recovery

TWRP-3.2.1-lineage-15.1_j1_20180418_gt58wifi.tar	- Blank Screen

TWRP-3.2.3-0.tar	- Error: dev_type. Comment: I tried tar the img to push via Odin, but it kept failing with the said error. I tar'd it on both Windows and ArchLinux

TWRP-3.2.3-0.img	- I flashed "twrp_3.1.1-1_sm-t355_251117.tar" and then installed the image through that recovery and after reboot to recovery, it still was on Blank screen. .

---------- Post added at 08:57 PM ---------- Previous post was at 08:50 PM ----------

No, [MENTION=4899305]ashyx[/MENTION] - When I try to flash it, I get an error from both Odin and recover install: Size of image is larger than target device.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
[MENTION=5172756]leomattel[/MENTION] that is a lot of information, there is a reason I mention doing this in stages that way it will be easier to troubleshoot.

Have you tried the TWRP 2.8.7 by ashyx?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] leomattel:
Oops! I thought you wanted me to try from 3.1 to 3.2 in steps. Apologies. I'll give 2.8.7 a try.

---------- Post added at 11:22 PM ---------- Previous post was at 10:28 PM ----------

[MENTION=6865385]nubianprince[/MENTION] - Tried. Error. Recovery is not Seandroid enforcing.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
Ah damn, though it would be too large.

Can you remind me what is the size of the recovery partition?

Also can you confirm if my twrp_3.2.3-1_sm-t350_23319 build boots?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] leomattel:
Apologies, [MENTION=4899305]ashyx[/MENTION] - I do not know how to find the size of recovery partition. :( The TWRp binaries that flashed well are between 11950kb and 14300kb. Yes, "twrp_3.2.3-1_sm-t350_23319" boots to recovery. The tar file was flagged as a potential virus and Windows kept deleting it. I had to download in my ArchLinux, extract the img and re-tar it to flash via Odin.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
Don't worry about the partition size.

I'm guessing it was Windows defender giving the false positive as usual? . :rolleyes:

I can assure you all my files are clean.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
The April 6 build works with camera, bluetooth, smart cover (see below), deep and sleep, google play store.

It does have the same problem with the flipflap app as I stated in

https://xdaforums.com/showpost.php?p=79279514&postcount=62
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Things to try.

1) Download heimdall from

https://glassechidna.com.au/heimdall/

It doesn't matter linux or windows. For all my flashing of TWRP and roms, I have been using linux and heimdall.

2) Put tablet into download/odin mode. Hookup tablet to usb

From the command line do a

heimdall print-pit --verbose

Upload results so we can see the partitions.

This verifies that heimdall is talking to tablet in donwload/odin mode.

3) If twrp_3.1.1-1_sm-t355_251117.tar works for you, then you need to modify the lineageos or crDroid zip file so that

/META-INF/com/google/android/updater-script

the assert line removed (it's the 1st 3 lines).

The first line should be

ui_print("Target: samsung/gt58wifixx/gt58wifi:7.1.1/NMF26X/T350XXU1CQJ1:user/release-keys");

By removing the assert/getprop, you are telling the script NOT to check for the SM-T350 model number. The older versions of TWRP don't support the assert or getprop function.

This should allow the zip installation to proceed.

4) Instead of using odin to flash TWRP 3.2.3-0, using heimdall and flash the img file like

heimdall flash --RECOVERY sm-t350-twrp.3.2.3.recovery.img

I renamed the img file above so it's easier for me to recognize. Make sure to use the one I specified in my link and check the md5 hash to ensure the download is correct.

With heimdall, what do you get? TWRP or blank screen?

5) With 3.2.3-1, if it boots into recovery, then install/zip the custom rom and then go back to the main menu and tell TWRP to boot into download mode.

Once tablet boots into download mode, run

heimdall print-pit --verbose

Tablet will automatically reboot and hopefully into custom rom. The reason for following this procedure is that the command "reboot system" is broken in 3.2.3-1 as I discovered. Reboot system always boots the tablet into recovery mode and

never to custom rom mode. Hopefully, by booting into download mode and running a print-pit will trick the Samsung bootloader into booting the custom rom.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
That probably happened because you used some sort of utility or adb to reboot to recovery.

For some reason the reboot flag doesn't get cleared. Samsungs kernel does something odd to cause this.

As long as only the hard keys are used to boot to recovery then rebooting to system from TWRP should work as expected as confirmed by another user.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] vin_001:
As so do I, this is not just a single person issue....
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen99:
So, now that I have finally gotten around to flashing this, now confused because of all the twrp problems, assuming it all goes as normal should I use twrp 3.1 or the 3.2 posted earlyer in the thread? And also where is 3.2.3 - 0, I could not find it:silly:

Edit: Found it! It was on pg 16, :p I'm so blind sometimes. So just confirming, flash using 3.2.3?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] iesous-kurios:
Thanks for testing. I never knew that option was there.

Maybe if I put flipflap back in and rename it to smartcover?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
Take a look at these

https://github.com/Nubianprince/gt5...0/overlay/frameworks/base/core/res/res/values

https://github.com/Nubianprince/gt58wifi/tree/lineage-16.0/overlay/packages/apps

https://github.com/Nubianprince/gt58wifi/tree/lineage-16.0/product

And remove FlipFlap from packages/apps

That should get rid of that smartcover option.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] leomattel:
Thank you, [MENTION=8726605]retiredtab[/MENTION]

There begins the problem. I thought this should be straightforward. Well, nothing seems to be. The binaries of Heimdall for Windows seems to be from 2013's. That clearly did not work - ended up with "libusb error -7 whilst receiving packet", so I tried to search for a ArchLinux version and unfortunately there were no builds for armv7 (Pi). Bummer! The only option was to compile and build this on Windows. In order to build a 1meg file, I had to install a linux-substem-like thing called "msys2" (10gigs) - got it from the GitLab readme notes of Heimdall. After finally making the binary, I ran the command; after few glitches with additional dll dependencies, I got it to work. I have attached the output with this thread.

Unfortunately, the new modded zip file did not work. TWRP kept saying "invalid zip file" - not sure if I was missing a checksum.

I did use Heimdall to flash but I used 3.2.3-1, it took me to the recovery screen.

Nope, this did not work too. I tried the whole thing with CRDROID too, as [MENTION=4899305]ashyx[/MENTION] says here, it seems to be the base lineage kernel with this Samsung unit. It just goes to blank screen.

One thing to note: Before I started this whole process, the tablet was put to charge, and it had the lineage16 installed (but never went beyond the "Blank Screen"). When I removed the power cable, I heard a "todoink" sound from the tablet. So, it looks as though there is a display issue with this ROM, the reason I am saying this is: When I installed Samsung's Firmware "SM-T350_1_20171031201753_ry6mrit198.zip", it booted and displayed the screen for the OS.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
The print-pit output is identical to mine.

I'm also using the samsung version boot loader.

Modifying the zip file should work. I have done it many times. I'm using archive manager that is built into lubuntu. I make the change to updater-script and then save the changes and archive manager updates the zip for me. I can then successfully flash the new zip.

I see you are from Canada. We likely have the same hardware then, same bootloader, same print-pit. Not sure why mine works?

Does your tablet load unofficial 14.1 or 15.1? Those images don't have working speaker/bluetooth/camera, but see if they at least boot?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen99:
OK, is the backlight on when the screen goes black? If it is not, wait the amount of time it would take twrp / lineage (however far you got) to boot, then shine a bright flashlight on the lcd right below the camera. If you see stuff, this may be simalir to the lineage 15 glitch where you had to flash an official Marshmallow build first. If the backlight is on iv got no clue...

Edit: You could also try flashing a marshmallow firmware first unless anyone advises otherwise.

Mind thoughts at 1 am: I really do wonder what the problem is, is it selunix on the nougat kernal? Is it an odd hardware defect? I hope someone is able to figure this out... Do we have anymore cheesecake left? :eek: M' hungry...
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] xxbeanxx:
I also get a blank screen after flashing the ROM. It's a backlight issue—I can see something on the display if I shine a flashlight on the screen.

Canadian SM-T350 purchased at Costco some time ago.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
For all people with black screens, see if the backlight is turned off as lividhen is referring to

https://xdaforums.com/galaxy-tab-a/development/rom-lineageos-t3826672/page3

https://xdaforums.com/galaxy-tab-a/development/rom-lineageos-t3826672/page4

It's worth a try to go back to marshmallow stock as above.

---------- Post added at 07:00 PM ---------- Previous post was at 06:05 PM ----------

Another tip for those with black screens when loading the custom ROM,

open a terminal window in DOS or linux and type

adb logcat

When the tablet boots, it should send all its messages to the terminal indicating that it is trying to boot.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] xxbeanxx:
I will give this a try when I have time, but that might not be for days or even weeks as I'm kinda busy with life. I did try flashing Nougat before LineageOS yesterday (purely by accident—I thought I had downloaded Marshmallow), but that didn't help.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen99:
:p i dont remember which firmware it was, i guess il start with BPE3 then try the rest if that doesent work...
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen99:
BOOP!

https://www.sammobile.com/firmwares/galaxy-tab-a/SM-T350/XAR/download/T350XXU1BPI2/103197/

---------- Post added at 08:27 PM ---------- Previous post was at 08:26 PM ----------

This got twrp to boot, now flashing lineage.

Edit: Yazzz! i have pie, with gapps! this should work if your haveing trouble.

---------- Post added at 10:10 PM ---------- Previous post was at 09:27 PM ----------

The only thing that doesn't work is restoring a google cloud backup from another device. I will give a log later.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] duanim:
you said install the original firmware and after install pie with gapps,which version of twrp are you using and no black screen meaning that its booting from twrp.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] leomattel:
Hello, [MENTION=8726605]retiredtab[/MENTION] - I bought the tab in US, but moved to Canada recently. I am on vacation for the next 3 weeks and left the tab behind back in Canada. Once home, I'll give the tab a try with Marshmellow base and then with unofficial 14.1 and 15.1 too. Thanks for your suggestions.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
From recent posts, it looks like if you flash Marshmallow stock that somehow allows twrp to work. Then go directly to pie.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen99:
OK so flash twrp 3.1.1.1 for nougat, go to wipe then advanced wipe. Wipe system, data, internal storage and cache/dalvic cache. Go to reboot then download, flash the firmware through odin (make sure to uncheck auto reboot then force shut off when done). After android installs the update, go back to download mode flash this https://androidfilehost.com/?fid=962339331458992706, then repeat the wiping posses, then install lineage gapps and magisk if you want to pass saftynet. After that wipe dalvic cache then reboot! There's probably a simpler way to do it but those are the steps I took.

---------- Post added at 07:21 AM ---------- Previous post was at 07:18 AM ----------

Oh! And don't forget to make a backup of your stuff if you want it.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] duanim:
Thanks if have time this weekend I will try
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen99:
Haha! Just tried a music app called pulsar, IT SOUNDS LIKE A TAZER! I never tried the default music app but, oh my gosh it was loud! VLC is the only one that works correctly that iv found so far, I wonder why. :(

Edit: ha, ha! I'm lovin' it! It's buttery smooth and it's been off the charger 45 minutes and is at 99%, thank you lineage + greenify! (that was my wierd way of saying there are no random performance or battery glitches when you have a finicky device.)
[Android Head-Units] TundraTech0054:
I ordered an Eonon GA2168K yesterday before I realized the Quad Core processor (A7) and ram (2GB) was potentially outdated. I like that it’s running 8.1 and the looks of the mount/ swivel feature to the 10.1” screen are more appealing to me.

However, I’m now considering sending that one back and ordering the Xtrons TE103AP. While I don’t love the looks of the screen mount as it appears to stick out way further than the Eonon (and only pivots vertically). I’m wondering if it would be best to have the upgraded Octa Core processor (A53) and ram (4GB). Is is really going to preform that much better to justify the additional $100? It’s also currently running 8.0 as opposed to the Eonon running 8.1.

I’m in over my head trying to gauge processors and ram specifications and just want to make sure I’m making the best decision for the money. The Eonon is $100 less which is more inline with my current budget but if the extra specs are far superior then I can prob justify the extra $100.

I don’t plan to do anything crazy with the head unit. Most intensive activity would probably be running videos on the unit for the kids on long road trips.

Thanks so much for any and everyone’s help with this. I’m freaking out trying to make the right call!
[Android Head-Units] TundraTech0054:
Insight?

Can anyone please provide some logic behind the processors and ram differences? I’ve been reading that even with an OctaCore processor it’s all about the app developers and if they’ve actually written the app to actually take advantage of the 8 cores properly. With that said maybe it’s the ram that’s more important.m but as I mentioned before I’m new to all of this.

Any comments are beyond appreciated!
[Android Head-Units] TundraTech0054:
Back at it!

Back at it again researching. I’ve actually been reading about more know issues with the Xtron unit that the Eonon in the last 24 hours. It appears the screen issue is pretty common which I’m wondering know if it has anything to do with the only vertical pivot mount and connector that I don’t really love.

I’ve also read that while the tech keeps advancing app developers have not gone back and rewritten apps to actually take advantage of the Octa core processor. In some cases people say the ovtacore units are not as fast as the quad core units because the apps are not optimized. Could this be true?

Still so torn. Really hope I can get some feedback on this thread. Maybe from some people who actually have the units and or units that utilize the same ram and processors...

Thanks again in advance for any comments.
[Android Head-Units] TundraTech0054:
Anyone?

Bump for some comments?