yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Android Development] meduza:
... that's what I thought first too but the other guy doesn't use substratum and theming at all ...

So stay where you are, don't update and be happy ;)

m.
[Galaxy Tab S Android Development] gellmar:
Logcat welcome!
[Galaxy Tab S Android Development] meduza:
Here please.

m.
[Galaxy Tab S Android Development] meduza:
Workaround

Maybe it`s somehow for someone useful: it's possible to enter settings by long pressing the WLAN tile, so the WLAN settings opens, from there it's possible to enter the detail settings categorys :)

m.
[Galaxy Tab S Android Development] gellmar:
You have the "suggestion" corrupting your settings. Suggestion is the green pane on top of main screen like do Not disturb mode activated etc. Try clearing data of Settings Provider (Apps - Show System Processes- Settings Provider) from your WiFi workaround.
[Galaxy Tab S Android Development] meduza:
Great! It worked! Thank you!

m.
[Galaxy Tab S Android Development] SkOrPn:
Yeah, my tablets has fallen apart after the last few updates. Clock always force closes and the SOC stays at 1900, never ever idling, and last night I noticed that the settings now refuses to open, with several other error popups etc. I un-installed as many unused apps as possible just in case that was it but nothing worked. I started using the Fingerprint sensor about a week or two ago for two different banking apps and ever since it seems the device just gets worse ever day. For the past 3 or 4 days the speakers stop working in the evenings and I have no clue why.

I guess I will provide a logcat below and try clean flashing to an earlier build? How do you use MatLog again for a reboot and record of Logs? Tons of errors in my logcat showing up to, lol.

EDIT: Figured out how to do a logcat, lol. It's been years since I've done one of those.

EDIT2: Latest changes that I can think of on my side is the fact that I installed the latest TWRP 3.3 and I also started using the Fingerprint reader because I am sick and tired of forgetting my banking app passwords, lol. I have since disabled Fingerprints and not using a lock screen anymore. Also again, I keep losing my speakers (like they don't exist), especially in the late evenings, no sound what so ever. A reboot sometimes fixes it, but I had to flash 5/11 in order to get it fixed last, but the speakers died again even after that. Not sure what to make of that issue. Battery is dying FAST on 5/11 and the SoC seems to stay at 1900 at all times, sometimes 1800 Mhz. I see no SoC idling when looking at the Mhz via CPU-Z. I enabled Deathly just to see if that would fix it but nope. Thanks
[Galaxy Tab S Android Development] meduza:
... you could flash the last stock ROM via Odin, check if everything is working, if not could be something with the hw ...

m.
[Galaxy Tab S Android Development] SkOrPn:
Just to let you know that I also tried this workaround and it fixed the corrupt settings force close issue. However, none of the other issues were fixed. So I flashed back to mid march build and so far everything seems fixed, SoC is now idling as expected, battery is much better device running cool and just need some time to see if the speakers continue to work. But so far going back to March 16 build seems to have fixed all my issues. I will report if anything further happens. Thank you again.

Anyone know what the last known working build is before these issues started? My last known working build before May 11 was 3/16, so that's why I went back to it. :good:

Also, in logcat I get tons of "Sensors E Accelerometer: unknown code (code=x)" errors, tons of them constantly. Is that normal?
[Galaxy Tab S Android Development] kaodd:
remember a similar issue month ago, fixed it with the hard way, means stock - root - twrp - custom rom!
[Galaxy Tab S Android Development] SkOrPn:
Stock Samsung rom isn't an option until I am selling it.
[Galaxy Tab S Android Development] meduza:
[MENTION=5214636]gellmar[/MENTION] ,

Since you're a part of the exynos team, maybe you could tell me, where to find the changelog for the Saturday builds ... ?

Btw. the other user in our German forum could solve his issue too by using the method you posted. But it looks to me, like there is something wrong with the ROM when different people suffer from that corruption ... .

m.
[Galaxy Tab S Android Development] meduza:
Today's update

So far everything seams o.k. ... .

m.
[Galaxy Tab S Android Development] gellmar:
Changelogs was the [MENTION=4817899]thompatry[/MENTION] 's job to add on Exynos5420 website. You can check, however, the LineageOS Gerrit:

https://review.lineageos.org/q/status:merged+branch:cm-14.1

and Exynos5420 Gerrit:

https://review.exynos5420.com/#/q/status:merged

To be honest, I keep building the "official" branch of LineageOS. So I have not touched Exynos builds for >1year. Exynos builds do ship LineageOMS patches too, and they can cause settings corruption as it is advanced theming.

Same for [MENTION=500006]SkOrPn[/MENTION] errors, I have never seen issues with idling on "official" kernel. If you want, I can build T800 firmware with test-keys so it can be flashed over Exynos build.
[Galaxy Tab S Android Development] DarkExistence:
Right, apologies about this guys I had no idea the builds were suddenly broken? Very strange. I won’t be able to help for the next few weeks as my exams start in 2 weeks time but [MENTION=5214636]gellmar[/MENTION] will try his best and will keep me updated.

Thanks a lot [MENTION=5214636]gellmar[/MENTION] for dealing with these issues while I can’t, appreciate it :)
[Galaxy Tab S Android Development] DarkExistence:
Right, apologies about this guys I had no idea the builds were suddenly broken? Very strange. I won’t be able to help for the next few weeks as my exams start in 2 weeks time but [MENTION=5214636]gellmar[/MENTION] will try his best and will keep me updated. Please have patience as it’s basically a one man team at the moment with people moving jobs and my exams, so he will be dealing with issues one at a time but it may take a while due to his every day life aswel.

Thanks a lot [MENTION=5214636]gellmar[/MENTION] for dealing with these issues while I can’t, appreciate it :) I’ll be back soon to help!
[Galaxy Tab S Android Development] meduza:
At the moment everything feels stable!

m.

---------- Post added at 08:38 PM ---------- Previous post was at 08:36 PM ----------

Wish you success and a good portion of luck for the exams!!

m.
[Galaxy Tab S Android Development] SkOrPn:
Yeah I would like to wish you good luck with your exams too. I remember those days all too well, lol.

[MENTION=5214636]gellmar[/MENTION], if you need a test dummy let me know please, lol. I currently flashed back to the 3/16 build and everything seems spot on, no issues what so ever. So somewhere in April or May something broke as my speakers just up and started dying on me for no apparent reason, and then I noticed the device was getting very hot and battery not lasting at all. So something broke and I just don't know exactly when or what build it started on. Sorry for not having better info. I will wait for any instructions. Thanks
[Galaxy Tab S Android Development] chillywilly77:
ME TOO! I clean installed the latest unoffical at the time (04/13 I think) and got it setup fine for my elderly relative. The settings menu worked fine for me when setting it up. She's been using it for weeks, but last week has encountered this 'Settings' force close/unable to open. She uses literally no apps other than her browser + YouTube.

Rebooting didn't fix. Reboot + clear cache and dalvik from inside TWRP didn't help.

I will have the tablet in my hands in the upcoming days so will be able to provide a logcat at that point.

Can anyone confirm that this issue was fixed in a build since 04/13? Or is this still affecting people right up to the current version??

Much appreciated folks.

EDIT: I see after scanning through the last few pages, it appears there might be a temporary fix I can try. Hopefully it's something an elderly person can perform, or I'll have to opt to use the latest official build where this didn't seem to be an isssue.

+Love
[Galaxy Tab S Android Development] meduza:
Cleaning settings data did it for me on last week build and all is nice on the last build. But in my case it was settings only.

m.
[Galaxy Tab S Android Development] gAgNiCk nThViM:
Did you test google maps with device only (GPS) location mode?
[Galaxy Tab S Android Development] ale_kons:
Yes this is what i did.
[Galaxy Tab S Android Development] robhug:
I don't know if it is possible, but when nougat was released on pixel c (don't know what it's like now) the recent apps in landscape were wider and larger like in portrait mode, (see screenshot) and I would be beautiful to have it. But absolutely don't know if it's possible :)
[Galaxy Tab S Android Development] DarkExistence:
Oh wow thats nice lol. I don't think its possible to add on LD since Its meant to be a stockish type rom, but LiquidDeath.. maybe. I'll talk to the team about it
[Galaxy Tab S Android Development] robhug:
I love it too ! Fingers crossed :)
[Galaxy Tab S Android Development] DarkExistence:
good news.

GPS has been fixed! Woo.

New build tomorrow.
[Galaxy Tab S Android Development] pnomandk:
Woah! New build just popped up at the download link :)
[Galaxy Tab S Android Development] meduza:
Yep :) Downloaded already, will install later ... .

m.
[Galaxy Tab S Android Development] pnomandk:
Just installed here. So far so good, but the two libsec-ril. so and libxml2. so are still missing from system lib, and need to be copied manually. But then GPS works :)
[Galaxy Tab S Android Development] DarkExistence:
You shouldn't have to. GPS is working fine for me without needing to do anything.
[Galaxy Tab S Android Development] pnomandk:
Interesting! I dirty-flashed (but the entire system is of course flashed), and gpsd spits out error messages in logcat unless I I copy the libraries to /system/lib. I'm puzzled it works for you and not for me 'out of the box'. A dirty-flash should not be able to cause such differences, as far as I can tell.

Need to investigate a bit more here then.
[Galaxy Tab S Android Development] DarkExistence:
Try a clean flash and see.
[Galaxy Tab S Android Development] Carlosk1966:
Clean flash today. GPS not work for me too.
[Galaxy Tab S Android Development] DarkExistence:
Logs from you guys please.
[Galaxy Tab S Android Development] nozeit:
Dirty flashed the last two builds. GPS works now after the Feb 11 build. Thanks!
[Galaxy Tab S Android Development] meduza:
Dirty flash, GPS seems not to work but I don't care because I don't need it momentarily .... ;)

m.
[Galaxy Tab S Android Development] DBCAB:
I dirty flashed and my gps works fine with google maps took a sec longer to lock at first but is working, are people testing this with a clear view of the sky? outside or near window that might help.
[Galaxy Tab S Android Development] pnomandk:
Tested it and got no lock in GPS-Status. Saw errors in logcat, and copied the missing libraries (on the live system) and went back into GPS-Status and got visible satellites and a lock shortly hereafter. No more errors in logcat either.

So not a problem with satellite view but something related to libraries - here. Not sure why it's different for me (and maybe others). Maybe related to API interface, depending on which app we use to test with?

Does GPS-Status work for you?

If you look into your logcat, do you see any errors reported related to GPS?

Do you have the files libsec-ril.so and libxml2.so in your /system/lib?

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

EDIT: My full flash sequence is lineage, open gapps nano and SuperSU. Nano does not contain Google Maps - maybe ypu flash another version which happens to contain other libs?
[Galaxy Tab S Android Development] DBCAB:
I installed Maps from the play store I originally used micro gapps on install I had clean flashed the initial release of this rom, dirty flashed updates followed by SR2-SuperSU-v2.79
[Galaxy Tab S Android Development] chillywilly77:
Awesome, thanks for that! The latest version you say is working good?: lineage-14.1-20190518 OR lineage-14.1-20190511

Did you need to do a clean install to fix the bug? Or a regular dirty/upgrade flash good enough?

Much appreciated!!
[Galaxy Tab S Android Development] SkOrPn:
Hey guys I just realized that I am in the wrong thread. I been talking about my T700 in the T800 thread and that might have confused some, sorry. All my issues are on the SM-T700, so it looks like I have to go post over there now, lol.
[Galaxy Tab S Android Development] gellmar:
Meh... Here is the unofficial build from official LineageOS tree (ie - stable kernel, no deathly stuff and no LineageOMS): https://mega.nz/#F!WzIQwQ6Z!jStz42chfWtQ_Hm_X0JFAg One can install it without wipe over Exynos5420 build.

The security string is May 2019 and there are some additional kernel CVE patches not yet uploaded to Gerrit.

UPDATE: The link has ALL latest builds from ORIGINAL LineageOS tree!
[Galaxy Tab S Android Development] SkOrPn:
[MENTION=5214636]gellmar[/MENTION], did you mean to quote me? That link you gave me above is for chagallwifi, and I have the klimtwifi. That is why I apologized for being in the wrong thread to begin with. I don't have a T800, but I wish I did, lol. Again, sorry again for posting in the wrong thread, not sure how I did that as I have over a decade of XDA experience and yet I still messed up, haha. :p
[Galaxy Tab S Android Development] gellmar:
This is for T800 users willing to use "official" flavor. If it works for them, I convince the team to start building these separately from "deathly" flavor.

I will add T805 and T700 to the same link. The files will be there for 7 days.
[Galaxy Tab S Android Development] meduza:
Both builds are working good after the fix. Dirty update flash.

m.
[Galaxy Tab S Android Development] kaodd:
soo, i should install the latest build and just flash the fix dirty?
[Galaxy Tab S Android Development] meduza:
There is no fix to flash, it's a workaround. After I fixed the issue regarding settings, I flashed Saturday's build dirty.

m.
[Galaxy Tab S Android Development] kaodd:
oki thx buddy
[Galaxy Tab S Android Development] meduza:
... you could try gellmar`s build also: https://fex.net/s/0lomadl

I haven't check it out, because not necessary at the moment ... .

m.
[Galaxy Tab S Android Development] kaodd:
is a official build?
[Galaxy Tab S Android Development] SkOrPn:
It was officially built by gellmar yes, but is not an official build by Lineage. No Exynos5420 stuff or Deathly etc, and no OMS.
[Galaxy Tab S Android Development] meduza:
https://xdaforums.com/showpost.php?p=79553989&postcount=1583

m.
[Galaxy Tab S Android Development] gellmar:
For those willing to continue using builds from official LineageOS sources (without Deathly additions!), here is the latest ROMS for ALL supported models: https://mega.nz/#F!WzIQwQ6Z!jStz42chfWtQ_Hm_X0JFAg

These builds can be flashed DIRTY over Exynos5420 builds - all data will be saved!

Migrating from official LineageOS builds (built and signed by LineageOS themselves!) requires the migration I described here:

https://xdaforums.com/galaxy-tab-s/development/rom-lineageos-14-1-sm-t805-t3844415 (paragraph Going back to unofficial builds without losing your data (if necessary):)

If there is a stable demand for it, I will convince the team to provide "official" builds on weekly basis on par with "deathly" ones.
[Galaxy Tab S Android Development] chillywilly77:
Thank you very much! Flashed over top, and it seems to be working awesome!! I really like how this one seems to be a bit more 'vanilla' than the previous builds. Wasn't even sure what 'Deathly' was for anyways (disabled it, and no root).

[MENTION=4662107]meduza[/MENTION] - that bypass/fix did indeed work perfectly, thank you so very much!

:)
[Galaxy Tab S Android Development] parkyh:
Hello.

I am using official build(it works fantastic). And seems like there is no more security update so I was trying to flash latest 20190519 unofficial build, however I couldnt. I see error 7. Am I missing something?? Thanks in advance.
[Galaxy Tab S Android Development] meduza:
When coming from official to unofficial you med to perform a full wipe, means including data position.

m.
[Galaxy Tab S Android Development] Saison2018:
Or use Migration script (Official to unofficial and vice-versa).

Here information quoted from another thread :

Going back to unofficial builds without losing your data (if necessary):

0. DOWNLOAD MIGRATION Script (https://raw.githubusercontent.com/Li...n/migration.sh )

1. BOOT INTO RECOVERY, UNLOCK THE DATA PARTITION IF IT ENCRYPTED AND ATTACH USB CABLE

2. PUSH THE MIGRATION SCRIPT TO THE TABLET: adb push migration.sh /migration.sh

3. OPEN ADB SHELL ON PC AND PERFORM THE MIGRATION: chmod +x /migration.sh sh /migration.sh unofficial

4. FLASH THE UNOFFICIAL ROM

5. WIPE DALVIK AND CACHE

6. REBOOT

But clean flash would be recommended to avoid future problems.
[Galaxy Tab S Android Development] Saison2018:
Tablet Reboot itself and Bootloop

Hi,

Please, if I am not clear, tell me, I will add more information. I really hope someone will help me.

I am on Lineageos from many years with this tablet, and I use Unofficial build from many months, updating firmware usually every 2 weeks.

Problem started this week when my tablet reboot during installing update (MiXplorer, through XDA App). From this time, I can barely use my tablet: Sometime I can boot into Lineageos or (more often) tablet reboots just after "Samsung Galaxy Tab S" logo (I could not see lineageos loading animation). And when I am not lucky, tablet reboot even in TWRP. Only "stable" mode is Download mode.

What I have done:

Wiped, factory reset

Formatted every partitions

Tested f2fs, rolled back to ext4

Clean flash Unofficial Lineageos latest release (over Unofficial Lineageos, firmware from same month)

Clean install (with Odin) latest original firmware for my tablet

"Upgrade" from Samsung to Unofficial Lineageos latest release

Try to use "low power mode" in battery

Switch from 5Ghz to 2.4Ghz wifi (this morning, as a last attempt to find a solution)

At this moment, my tablet has Unofficial LineageOS (lineage-14.1-20190518-UNOFFICIAL-chagallwifi.zip).

I was able to use my tablet 1 hour yesterday evening, leave it charging during the night but tablet rebooted this morning when I started to use it. After some reboot/shutdown/download mode/wipe cache in TWRP, I was able to use it during another 1 hour before leaving to work (wifi on 2.4Ghz).

I could not see what to do next, any advise will be appreciated

Thanks
[Galaxy Tab S Android Development] meduza:
1.) Did this happen when you were on the stock ROM?

2.) Did you always clean install (wiping data) especially your current ROM?

m.
[Galaxy Tab S Android Development] Saison2018:
Thanks for replying

Answers are "yes" for all, it was happening also on the stock ROM and I always did a clean install (wiping, factory reset and/or format).

Only on my last installation, when I upgrade from stock to LineageOS, I only performed a factory reset before installing LOS over stock rom.

But my truly first test (when problems began) was to format every partition and install LOS. I wanted to eliminate any remaining stuff from my faulty previous installation.
[Galaxy Tab S Android Development] meduza:
... on stock also ... , that sound isn't good ...

Maybe someone of our advanced guys could have a lock at your logs ... . Definitely last kernel message after auto reboot.

m.
[Galaxy Tab S Android Development] Saison2018:
Next time tablet will reboot, I can try to get logs (with SysLog application).

But as you said, someone with more knowledge need to take a look.

Thanks a lot for your help, it seems I have done a lot of job on my side, but it is better to ask, sometime you miss a step, just because you are to much involved in the process.
[Galaxy Tab S Android Development] gellmar:
Please grab /proc/last_kmsg - i suspect it is flash ROM hardware failure.
[Galaxy Tab S Android Development] alefoi:
big.LITTLE ?

Is big.LITTLE supported by any of these roms? I am on the last official and based on what is reported by HW-info apps only the four big cores are detected. Apologies if this is a trivial question, but I could not find any information anywhere. Thanks!
[Galaxy Tab S Android Development] gellmar:
Yes, it is working in LineageOS ROMs:

chagalllte:/ # cat /sys/devices/system/b.L/b.L_core_stat
0 1 2 3 L2
[A15] 0 0 0 0 0
[A7] 1 1 1 1 1

chagalllte:/ # cat /sys/devices/system/b.L/b.L_info
cluster : LITTLE
switch count : 66951
switch time : 1760542 ns
min time : 435083 ns
max time : 86269083 ns
avg time : 1510316 ns

chagalllte:/ # getprop ro.build.display.id
lineage_chagalllte-userdebug 7.1.2 NJH47F 0e63351a59
[Galaxy Tab S Android Development] meduza:
Yesterday's build works great and has a new security patch :)

m.
[Galaxy Tab S Android Development] Saison2018:
Here is the "last_kmsg" attached in a zip file.

Tablet reboots itself and it takes some attempts to get into TWRP.

Hope file will give you some clue.

Thanks a lot for your help.
[Galaxy Tab S Android Development] gellmar:
Are you on Exynos build or my build? By log, the root cause is overwritten with TWRP boot…
[Galaxy Tab S Android Development] Saison2018:
I use builds from OP (https://download.exynos5420.com/LineageOS-14.1/chagallwifi/).

I can use your build to test, if this could help I will more than happy (don't want to buy another tablet, mine was ok until this problem and I love it).

Regarding logs, as I said, it was difficult to get the file: when the tablet rebooted, I was not able to land in TWRP immediately because tablet rebooted some times on first logo (Samsung Galaxy Tab S).

Is it possible to retrieve the file from "Download Mode"? This mode seems easier to get, compare to TWRP (and booting into LOS is almost impossible when tablet start to reboot).

I will do my best to give you useful information.

Thanks a lot for your help, this is greatly appreciated.
[Galaxy Tab S Android Development] runekock:
[MENTION=8939500]Saison2018[/MENTION]

Does the reboot frequency seem to depend on the tablet's temperature? I wonder if the processor chip has lost contact with its heatsink, and overheats?

Anyway, everything points to some kind of hardware problem. I think you're wasting your time looking for a software solution.
[Galaxy Tab S Android Development] Saison2018:
Temperature: It could be at the beginning, but not now because if I start tablet after night been stay power off, it reboots anyway

Hardware: Could be, but why an application upgrade could cause that kind of trouble? (but my hope for a solution is fading)
[Galaxy Tab S Android Development] gellmar:
Try my build for a week then. If no reboots in a week, then keep flashing "nightly" builds I will provide.
[Galaxy Tab S Android Development] Saison2018:
Does your post #1594 (https://xdaforums.com/showpost.php?p=79557988&postcount=1594) is the one to start to download files and give it a try?

If yes, i will try and keep you posted.
[Galaxy Tab S Android Development] gellmar:
Right, that one.
[Galaxy Tab S Android Development] Hookmt:
Yes, very sweet. Took me less than an hour to rebuild after a complete wipe from the Feb Official build. No problems at all. :good:
[Galaxy Tab S Android Development] bouwew:
Thank you, yes, I would like to stay on "official" LineageOS.
[Galaxy Tab S Android Development] jjcdennis:
I've been running on LineageOS version 14.1-20190205-nightly-chagallwifi, build # lineage_chagallwifi-userdebug 7.1.2 NJH47F and haven't paid attention to all the changes within this thread. If I remember correctly this was an official LineageOS build and maybe the last one before the change to unofficial..

With all the changes and problems detailed in this thread I'm confused as to what I should flash to update this tablet.

My question is, can I dirty flash the new official LineageOS build, or am I into a complete wipe of the system? I'd prefer to not have to reload all of my apps/data and perhaps Titanium may not be able to do this.

Would appreciate some help.