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
Guess right now only @Valera1978 could answer that.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
Try hereHello,
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.
Try playing around with the included Audio FX app, made a difference on my S3.love the ROM only problem is audio is too low compared to stock ROM any trick to make it sound better?
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.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).
From (Sorry, can't post links bc of XDA. I miss the old XDA..)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```
So what exactly are we to do to stop the loop?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.
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.Hello guys does adoptable storage or Apps2sd work fine with this rom please?
As the rom hasn't been updated since "20190518", that would be a no.Still no solutions for camera , s pen , usb - otg bugs?
Did you try to delete /data/system/users/0/settings_fingerprint.xml (and potentially /data/system/users/0/fpdata/users.db)?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.
Directories are there but not the files.Did you try to delete /data/system/users/0/settings_fingerprint.xml (and potentially /data/system/users/0/fpdata/users.db)?