[ROM][SM-T820][UNOFFICIAL] LineageOS 16.0 | Android 9.0 20191024

risant

Senior Member
Aug 6, 2016
264
30
28
is there a hope for fixing the bugs in lineage 16 camera, spen ,ub-otg .. if not i will sell my T820 for good ... using tweaked firmware for t 820 laggy... lineage 16 -bugs
 
May 29, 2019
7
1
0
Step by step guide for noob?

Hello,

Is there a step by step guide that explains how to install twrp, make partitions, wipe them, how to flash, installing the ROM properly?

I've never done something like this before and was wondering if anyone can help me out. Thank you.
 

DuncDog

Member
Nov 30, 2014
8
4
0
New Tab S3 Owner

Just got a used SM-T820 a few days ago and had this ROM running on it within 2 hours of opening the packaging with almost no issues. Only snag was to repartition System/Data/Temp to break the encryption and everything since has gone smooth since I made that move.

Everything appears to run fine so far, and the only real oddities I've noticed over the last few days appear to be that the finger print sensor seems a little 'flakey' compared to my Pixel 2 XL's, but that could just be a hardware difference in the sensors so I can't attribute that to the ROM itself. Aside from that, it just seems like this build REALLY doesn't play nice with Google's Official "Wallpaper" app that allows you to install the live wallpapers that ship on the Pixels. They run from the stock launcher when you apply them as a wallpaper and grant all the permissions to get them to work (I'm partial to the "earth" that overlays weather data from Weather.com over a time-synced satellite view of where you are on Earth), but anywhere from 25-45 minutes it seems, the tablet seizes up, and when trying to lock/unlock it, it reboots and defaults to the last regular wallpaper that was set when it comes back.

Second "issue" if you want to call it that, is the same that others have reported where the Adopted Storage appears to just add 128GB to it in the Settings to the formatted SD card, but it reads correctly in proper file explorer apps? Using a 400GB mSD in mine and it is working like a champ.

Miles ahead of my old Shield K1 pretty much across the board. Don't use my tablet as a calling device, a camera, or NFC (I have my aforementioned Pixel 2 XL for all of those needs), so those issues don't really mar the experience for me. Overall, everything else seems to be holding up just fine.
 
  • Like
Reactions: whitedragon33

drt054

Senior Member
Jan 8, 2011
1,012
196
93
Cleveland, OH
Thank you. Okay I'm going to play with it gotta install BusyBox and whatnot I'll report back once finished. In the meantime, other thing I noticed is sometimes after putting my PIN in the screen will dim, it'll freeze, and then reboot itself. I saw someone else posted here with similar issue. Thoughts?

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



I loaded it up picked Samsung "17" and only saw Tab S3 (T825 8.0.0). Didn't see T820. Either way, picked that, no luck.

I almost don't care about passing SafetyNet. What I do care about is having my Play Store sync my Family Library purchases (it's not).
I installed BusyBox through Magisk and changed the device fingerprint to the T825 option, rebooted. My lockscreen kept looping after typing in my pin so I rebooted again and now CTS profile = true and hopefully will be all good for now.
 
  • Like
Reactions: Nosferatu.

Jay22R

New member
Mar 1, 2018
3
0
0
Regarding the crashing: Here's a diagnosis and suggestive fix for OP.

Error code:


Fixes:
In P, Google decided to tighten restrictions on mutex calls by ensuring mutex_destroy
is not called on an already destroyed mutex (which can be potentially dangerous),
however this caused issues because Qualcomm, in their infinite wisdom, decided to
destroy mutexes in a loop, causing them to be 'destroyed' twice
* To fix this, the CBNZ instruction (aka, the break condition) for the loop was moved
to before the pthread_mutex_destroy calls, to prevent double mutex destruction```
From (Sorry, can't post links bc of XDA. I miss the old XDA..)

I hope this is helpful for OP, I appreciate your work. Thanks again.
 
Last edited:

Nosferatu.

Senior Member
Dec 20, 2011
2,252
765
113
Tampa, Florida
Regarding the crashing: Here's a diagnosis and suggestive fix for OP.

Error code:


Fixes:

From (Sorry, can't post links bc of XDA. I miss the old XDA..)

I hope this is helpful for OP, I appreciate your work. Thanks again.
So what exactly are we to do to stop the loop?

I just cannot put this device back on Samsung's ROM it's so snappy on Lineage OS. Only con is audio is low (somewhat fixed by adding Viper4Android FX) and cannot install Netflix. :silly:
 

drt054

Senior Member
Jan 8, 2011
1,012
196
93
Cleveland, OH
I've had to reinstall this ROM 3x now. It keeps getting stuck in a lock screen loop. So I remove the pin and fingerprint and it just gets stuck on Android is starting. This was before and after I changed the device fingerprint. So for now I'm just not turning it off.

I have a stock backup but it's so ridiculously slow.

I gave up on LineageOS for now.. too many problems that probably won't get fixed until Pie is out for this tab. I flashed Tweaked Stock 8.0 for now everything is running as it should be.
 
Last edited:

DuncDog

Member
Nov 30, 2014
8
4
0
Hello guys does adoptable storage or Apps2sd work fine with this rom please?
Yes to Adoptable Storage, as I'm using it with a 400GB mSD in mine as we speak. It DOES add an extra 128GB in the Storage Settings Page for some reason, but inside an actual file management app, or another app that allows access to the amount of "space" on the mSD (~364GB in my case), it has been reading correctly for me.
 

drt054

Senior Member
Jan 8, 2011
1,012
196
93
Cleveland, OH
On 7-7-19 build. Clean flash.. So far I can't finish setting up fingerprint unlock. The progress circle stops after your first finger placement and is just gray. The tablet vibes when touching it so it is registering something. I'm restoring my apps now. I'll add other issues I find here. Rear camera working so far, front force closes. After changing device fingerprint to use magisk hide still get the lock screen looping.
 
Last edited:
  • Like
Reactions: duy_ng and Glitch04