yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Android Development] 3DSammy:
Well that was a trip. I tried clean installing the latest build three times and all went well (FC on browser initial during setup) but as soon as I attempted to get Substratum theming to work all hell broke loose in the form of Google services and play FC messages plus numerous other apps. Thank goodness I had a nandroid backup. As other did not have issues with the latest build and a clean install I'll blame something to do with Substratum or how I was applying it (Team BlackedOut theme ready apps).

Finally I did as others had done and dirty flashed over the nandroid restore. Everything worked perfect and I was up and running in a matter of minutes. Even Substratum theming worked. I'm happy but surprised as I clean installed the prior build without any issues at all including Substratum.

One thing I noticed when with clean install was that the battery settings in Deathly Auditor were substantially higher than in the prior build. I felt that the T800's back became warm to the touch, after a while, something that had not happen before. I lowered the settings to what I had on the prior build and all is well with no warmth that I can discern. The dirty flash preserved my LineageOS 14.1 Jan 25th build setting or what I had changed them to be,
[Galaxy Tab S Android Development] DBCAB:
My location mode was set to high accuracy this past test on the feb 4 build I just tested battery saving and device only, device only isn't working. I hadn't realized that high accuracy was set for this build in settings.

As for the build im on it is feb 04 2017 here is screenshot
[Galaxy Tab S Android Development] pnomandk:
That's what I suspected :) Thanks for confirming that GPS isn't working for you either.
[Galaxy Tab S Android Development] gAgNiCk nThViM:
What were the settings out of curiosity? Thanks :)
[Galaxy Tab S Android Development] meduza:
... here either, I'm on last build now.

m.
[Galaxy Tab S Android Development] 3DSammy:
Here is a screenshot of the Feb 4th build clean install battery settings defaults.

The first thing I noticed was that both "AC Charger Current" settings where higher and that the "Screen on Current Limiter" was switched on, plus the "Standard Downstream Port" settings are also much higher. If you did a dirty flash and had changed the settings your changed settings were not overridden.
[Galaxy Tab S Android Development] DBCAB:
On device only is only setting not working for me the other 2 settings work perfectly lock fast etc. so I guess is some small issue, were you able to extract the lib files and fix it yourself as you did the first time just wondering?
[Galaxy Tab S Android Development] pnomandk:
I had a quick peek at this on the previous build (Feb 3rd, IIRC), but didn't succeed getting it to work at first go. As it was the initial build on the new tree, and it is a known issue, I expected it to be solved shortly, and didn't spend more time on it then (due to other commitments). If I get some time, I may try once more and will report back here if I find a work-around again.

- Per.
[Galaxy Tab S Android Development] Nairolf ™:
Videoscaling

Hey.

It seems HQ Videos on YouTube (e.g. 1080p or 1440p) have problems with scaling. They are zoomed in and not scaled properly. Maybe smth with decoding? Installed it twice, still the same problem.
[Galaxy Tab S Android Development] DarkExistence:
Yeah we know about that error. working on a fix :)
[Galaxy Tab S Android Development] DarkExistence:
New build sometime today with the button fix, and some other stuff :)
[Galaxy Tab S Android Development] meduza:
So it can get only better :) I must say, this ROM is definitely the best one, I ever had on my tab and I own in two years :) The best performence, the best battery life and enough features at least all that are important for me :)

m.
[Galaxy Tab S Android Development] DarkExistence:
Well, that was my fault lol. Lineage isnt getting a new build today sorry guys. Button fix post was for LiquidDeath lol. too similar in names.

Lineage is on an automated build schedule now so will be uploaded at different times then RR and LiquidDeath. I will, as usual alert you of any changes and whenever a new build is being published still though :)
[Galaxy Tab S Android Development] pnomandk:
Good that it's now on automated build :) Did you get anywhere with the GPS library problem -- i.e. can we expect this to be working in the next release, or would it still be an idea to find a workaround (if possible) in line with the previous workaround?

- Per.
[Galaxy Tab S Android Development] DarkExistence:
Nope no fix found yet. Tried a few different things to fix it but alas none have worked. WIll keep trying though dont worry. GPS works fine on my Liquid death build. RR is switching to the new device tree today, so it will be interesting to see if it still works on that.
[Galaxy Tab S Android Development] ale_kons:
Just update my Tab S and have to say that is wonderful. I will play around and inform for issues bugs.

Wipe Dalvik,Cache,Data and installed ROM, gappsARM 7.1. stock without any issues.

GPS with google maps tested and working.

Settings page (working) but seems to be designed for phones and not tablet.

Restore applications from google backup working

Google play is working
[Galaxy Tab S Android Development] rabellogp:
Same here... I was using the original Marshmallow ROM and I've just installed the last Lineage hopping that the 1080p YouTube cap would be gone but it's still there. Very frustrating...
[Galaxy Tab S Android Development] soren25:
It's a little bit of hassle to install (unless you have Magisk), but YouTube Vanced gives you manual control of the max resolution shown.
[Galaxy Tab S Android Development] hbkhero:
Searching for a fix

Hey the deathly adiutor doesn't support the kernel of the rom

Anyone have any idea to fix it
[Galaxy Tab S Android Development] gellmar:
Migrate to unofficial Exynos5420 builds or flash the kernel from Exynos5420 build on top of the official build.
[Galaxy Tab S Android Development] Saison2018:
Hi,

2 questions (hope you could answer, I am curious):

- Does moving from Official to Unofficial means clean flash?

- Where do you find kernel for Exynos5420? I made some research and do not find any zip file to flash in TWRP and/or only old threads with "discontinued" mentions

Thanks
[Galaxy Tab S Android Development] gellmar:
-Moving from official to unofficial does not require data,wipe if you follow the instructions I posted in Migration section of T805 official topic - see migrating back to unofficial.

- the kernel is boot.img within exynos5420's zip file for chagallwifi.
[Galaxy Tab S Android Development] Saison2018:
Thanks, was able to find all information

:good:
[Galaxy Tab S Android Development] lurgainn:
Hangouts...again :)

Hi DarkExistence,

lately I saw that the changelog of LineageOS 14.1 has a lot of changes signed by 'exynos5420' and 'chagalwifi'.

So I dare to ask again if there is a chance to see implemented the corrections that will allow Hangouts to work on the T800.

Thank you very much and anyway my best wishes for your final year of school. :)
[Galaxy Tab S Android Development] gellmar:
What is exactly the Hangouts issue?
[Galaxy Tab S Android Development] drahtwurst:
@ Saison2018: did u install deathly boot.img for use with audiutor? r u able to tweak gpu frequency?
[Galaxy Tab S Android Development] lurgainn:
Hangouts...again :)

Whenever you start a videocall, your cam appear just for a moment (while ringing your partner) and then crash. No video call, even if from that moment Hangout report that a call is ongoing, but instead...no call at all. :(

Other guys signaled the same bug and we posted the log. Darkexistence told us that he knew the reason of the problem, but he had no time to release a patch (at last so I understood). You can check searching this thread with "Hangout" or my userid "lurgainn".

Thanks
[Galaxy Tab S Android Development] Saison2018:
I extracted boot.img from unofficial build as advised and flash it in TWRP.

GPU settings are available in Deathly Adiutor.

Everything seems OK.

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

@gellmar

Stupid question (and Sorry if it was already asked) : Do I need to flash kernel after every update?

I am still on Lineageos official build.

Thanks
[Galaxy Tab S Android Development] gellmar:
Yes, you should flash the new kernel every time. But I see no point for you personally to use official build, as official build differs from unofficial with exactly the kernel used. Use the migration-back tutorial in post #1 of 805 topic and be happy.

Anyway after Lineage 16.0 goes official with a first shipped device, all 14.1 builds will be pulled off to free the storage space on official build servers. We tried to influence that decision but our attempt was unsuccessful.
[Galaxy Tab S Android Development] drahtwurst:
[MENTION=8939500]Saison2018[/MENTION]

can you please confirm you have the same settings and use Kernel Adiutor 0.9.11.1? (Cant find Deathly Adiutor seperately). Is it to be installed as system app?
[Galaxy Tab S Android Development] drahtwurst:
@ gellmar: would you please link! your Fingerprint-Solution you wrote about here? https://xdaforums.com/sho...postcount=1376
[Galaxy Tab S Android Development] gellmar:
https://xdaforums.com/galaxy-tab-s/development/rom-lineageos-14-1-sm-t805-t3844415
[Galaxy Tab S Android Development] runekock:
The horror!

By a quick count ~120 phones and tablets are still on LOS 14.1 (versus ~72 on 15.1).

Do you know if it is a money issue?
[Galaxy Tab S Android Development] gellmar:
Very briefly about my conversation with [MENTION=2693412]haggertk[/MENTION] and [MENTION=5795145]javelinanddart[/MENTION] in the Lineage slack: the reason for pulling the devices off is the lack of storage space on the donated build servers (agrippa, iktinos, kallikrates and master) hosted by Umeâ university in Sweden. Today two new buildservers were added (gcc127 and gcc128 donated by member "osuosl") so it is basically needed to bump up the storage on the remaining "old" buildbots. However, the only person who can make these decisions is Tom Powell aka [MENTION=2195612]zifnab06[/MENTION] (/u/zifnab06 on Reddit) as the leader of the project.

So the only way to support the project is to reach Tom personally and discuss what is required. I am not in position to make such decisions.
[Galaxy Tab S Android Development] drahtwurst:
[MENTION=5214636]gellmar[/MENTION]: your solution to get Fingerprint working described here https://xdaforums.com/galaxy-tab-s/development/rom-lineageos-14-1-sm-t805-t3844415 (Thanks for pointing me)

seems identical to the way I described to: "...install Gapps + Root Samsung Galaxy Tab 10.5 T800" including lineage installation within this thread https://xdaforums.com/showpost.php?p=77795970&postcount=1378

using the identical file T800XXU1CRH1_T800EUR1CRG1_HOME.tar.md5 i was using there

and you linked here https://xdaforums.com/showpost.php?p=77774614&postcount=1371

...not nowing it would be identical and not nowing your thread for T805. I found out about it by downloading your linked file in slow mode for 8 hours just now.

Problem is my Fingerprint is still not working. It does only in part, it scans a finger but later it never recognizes the finger anymore to unlock. :confused:

What else to do?
[Galaxy Tab S Android Development] gellmar:
So you flashed the stock ROM, then re-installed Lineage cleanly and enrolled a new finger? Show the logcat then.
[Galaxy Tab S Android Development] TayzGpa:
Quick question. Are the install instructions on the first page still accurate?
[Galaxy Tab S Android Development] Saison2018:
[MENTION=6167888]drahtwurst[/MENTION]: I have exactly the same values as your screenshot.

About Deathly Adiutor (or Kernel Adiutor), I installed it as a normal application (allowing unknown sources).

Sorry for the delay, little busy.

---------- Post added 11th October 2018 at 12:04 AM ---------- Previous post was 10th October 2018 at 11:47 PM ----------

One word: AMAZING.

I did exactly what you said in your thread (https://xdaforums.com/galaxy-tab-s/development/rom-lineageos-14-1-sm-t805-t3844415, Going back to unofficial builds without losing your data) and only runs script and flash unofficial build.

No GApps (re)installation, no clean flash. My applications are still on the tablet and seem to run fine (not tested all).

Thanks a lot.
[Galaxy Tab S Android Development] drahtwurst:
[MENTION=8939500]Saison2018[/MENTION]

Deathly Adiutor and Kernel Adiutor look different here. Deathly Adiutor you installed an app? Where from? I run the unofficial build now, it comes with Deathly Adiutor and that on has a different menu and features than Kernel Adiutor. I installed the whole build because flashing the boot.img would not give me Deathly Adiutor. I wonder how you managed that.

[MENTION=2874155]TayzGpa[/MENTION] - not entierly, see updated links https://xdaforums.com/showpost.php?p=77795970&postcount=1378

[MENTION=5214636]gellmar[/MENTION]

logcat - FP wasnt working with official lineage, so i flashed the unofficial build, still testing (no working FP). i did not reflash the "T800XXU1CRH1_T800EUR1CRG1_HOME.tar.md5". if thats fine, please tell me how i can get you the logcat. if not pls tell me anyways, i reflash again and do a clean install with either build.
[Galaxy Tab S Android Development] gellmar:
Once more. Please clarify, have you flashed T800XXU1CRH1_T800EUR1CRG1_HOME.tar.md5 at least once?
[Galaxy Tab S Android Development] drahtwurst:
:good: positive yes.

i have something to report if it helps finding the reason: booting in download mode from downpowered device gives me chinese characters. that appeared sometime before. since i was testing different bootloaders, ODIN versions+ROMs from XDA something messed that dialoge up.
[Galaxy Tab S Android Development] gellmar:
Can you give me the photo of these in ODIN mode? This might be the reason.
[Galaxy Tab S Android Development] drahtwurst:
here u go
[Galaxy Tab S Android Development] gellmar:
European firmware does not have Chinese literals. Let me give you an ODIN tar with the verified S-BOOT for T800 after I get back home.
[Galaxy Tab S Android Development] Saison2018:
[MENTION=5214636]gellmar[/MENTION]

Maybe you will be able to answer : why does lineageos use so high values for dalvik.vm.heapxxxx, especially dalvik.vm.heapgrowthlimit and dalvik.vm.heapsize?

I have many android devices and I have to change this value each time I update.

For example, on my OnePlus One I had to change values to be able to run theater application (Cineplex).

On my tablet (SM-T800), I have to change values to run Nfs No limits (and other games that I don't use now).

Many custom rooms include this change and until now, never seen any negative sides.

I am not a developer and not sure how much work is needed to implement this change.

Because you seem to be well connected, maybe you could share this information or give me an explanation.

Thanks in advance
[Galaxy Tab S Android Development] gellmar:
https://github.com/LineageOS/androi...aa41f7a#diff-769591f4704dc472c430a773ddae5303 this commit sets the limits we know. I will ask in the slack about your values.

This can be done in our device tree basis.
[Galaxy Tab S Android Development] drahtwurst:
That would be nice.
[Galaxy Tab S Android Development] Saison2018:
I agree that my 2 devices in example are old. Maybe "old" devices need some modifications.

Thanks for sharing information and to give answer.

---------- Post added at 06:39 PM ---------- Previous post was at 06:23 PM ----------

I did a search on Google to find an apk and installed it as normal (with allowing unknow sources).

But this was before going back to unofficial with instruction provided in T805 thread, as indicated by gellmar.

Since I am on unofficial build, I must admit that I did not check settings.
[Galaxy Tab S Android Development] drahtwurst:
[MENTION=5214636]gellmar[/MENTION] can you link me to the ODIN tar please
[Galaxy Tab S Android Development] gellmar:
Load this as BL and let it flash.
[Galaxy Tab S Android Development] drahtwurst:
[MENTION=5214636]gellmar[/MENTION]: thanks, but it did not change the chinese characters. i was just flashing it as BL in Odin 3.13.1_3B_PatcheD with checked auto boot + f.reset time. Fingerprint behaviour also remains about the same. working:nonworking 1:>12

<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 1 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
[Galaxy Tab S Android Development] gellmar:
Then you have probably messed out your PARAM partition (if it exists at all on T800). I have never seen such issues but maybe other people in this thread can share their nandroid dump with you.
[Galaxy Tab S Android Development] drahtwurst:
dunno how. i was using different odin versions, roms, bl's...all found on xda and linked in threads for t800
[Galaxy Tab S Android Development] benoitb85:
Does this work for you on LOS 14.1 ? I got YouTube Vanced installed, and still I'm limited to 1080p.
[Galaxy Tab S Android Development] soren25:
Go to Settings > Vanced Settings > Video Settings and flip the "Resolution Checks" switch.
[Galaxy Tab S Android Development] benoitb85:
I did and still 1080p max.
[Galaxy Tab S Android Development] AtlanGon:
Hi,

I run a very old os-version on my SM-T800. (3.4.113-IronStock_SM-T800_V3.2 Android 6.0.1)

I try to install LinageOS 14.1 like in the instruction on https://wiki.lineageos.org/devices/chagallwifi/install but I'm getting errors. I think because I used ODIN then. (the download mode says odin mode)

The ZAdiag Driver is therefore not working...

Can anybody help me?

Thanks
[Galaxy Tab S Android Development] gellmar:
Look for instructions in T805 official LineageOS topic but use TWRP and ROM zip for chagallwifi.
[Galaxy Tab S Android Development] jdrsk:
Hey.

I've got a question about keyboard layout.

I'm on 14.1 on my T800 and there's no polish keyboard layout in it. I like to work with my logitech keyboard, but I can't without pl layout.

Any solutions for that?
[Galaxy Tab S Android Development] gellmar:
Was it in stock? Is your keyboardbUSB or Bluetooth? If USB, can you give its VID and PID (I assume VID = 046b and PID ?)
[Galaxy Tab S Android Development] jdrsk:
K360 BT keyboard.

In "physical keyboard" configuration there's no polish layout to choose and I can't use special chars...

And yes, pure 14.1
[Galaxy Tab S Android Development] gellmar:
Have you checked "External Keyboard Helper Pro" ?
[Galaxy Tab S Android Development] jdrsk:
Not yet. Thanks I'll look that app.

Installing demo now :)

It's cheap so there's no problem.
[Galaxy Tab S Android Development] Stiii:
Battery issue

All is good but battery drain fast , lineage is installed like 2 Monty ago .... Anyone have this problem ? Clean install , no gaming ,only web and facebook ... Before this Os i drain like 5% for 2hour ~ and now 20% by hour , brightness is lower and all battery option saver is ON .....
[Galaxy Tab S Android Development] Skyh:
I completely uninstalled root, however the DRM Info app still reports my tab as L3, and I seem to be capped at 480 on Netflix. Any ideas? Are you using this ROM and still getting L1?
[Galaxy Tab S Android Development] gellmar:
Nope, allcustom ROMs are L3 atm. Only stock-based ROMs may have L1
[Galaxy Tab S Android Development] gimmeluck2:
guys,

wait

i didit udnerstand this part:

i have official Android6.0.1 and , TWRP 3.2 and root.

and now i will simply open TWRP and install this "Chagallwifi Download" ?

then what are these links for??

Kernel

https://github.com/LineageOS/android...ung_exynos5420

Device Tree

https://github.com/LineageOS/android...ng_chagallwifi
[Galaxy Tab S Android Development] gimmeluck@gmail.com:
Thats what i wonder also
[Galaxy Tab S Android Development] gellmar:
Read first this topic.

Github links are for advanced users willing to build the ROM from sources and/or start contributing.
[Galaxy Tab S Android Development] gimmeluck2:
thank you,

i did it,

all done successfully,

but there are some problems like;

google calendar; is continously closing itssel im possbile to open,

is there such meanningless bugs still with this rom?
[Galaxy Tab S Android Development] gellmar:
Please attach the adb logcat reproducing the error
[Galaxy Tab S Android Development] gimmeluck2:
sorry i dunno what you mean,

but i simply can write that i had 2 problems;

1) from playstore, i installed google calendar and tried to open, and directly " google calendar stopped" window came.

2) i also tried to install whatsup.apk which was wroking with official rom, but it failed.

maybe i had to do more "somre more advanced wipes" before flash? i made twrp simple wipe.
[Galaxy Tab S Android Development] DarkExistence:
if you had read the second post you would see i provide a place for you to easily get logs..
[Galaxy Tab S Android Development] FlavioMadeira:
Audio distorted and battery not charging with screen on

Hello to all,

I made my first custom rom installation yesterday on my Samsung Galaxy Tab S 10, I installed the lineage-14.1-20181205-nightly-chagallwifi-signed.zip, open_gapps-arm-7.1-nano-20181213 and addonsu-14.1-arm-signed using the twrp-3.2.3-0-chagallwifi, and so far seems to be working fine, except for the sound quality on the external speakers, which distorts at medium to high volumes, lacks definition and cracks when video starts even with the sound muted.

Tried disabling the AudioFX, but makes no difference.

Also, the battery doesn't seems to be charging when the screen is on, Ampere app shows 0 mA while using the same charger and cable.

EDIT: After several tests, the battery is charging without any problems, so the only help I ask is to fix the sound problem.

Does anyone have any advice?

Thanks in advance.
[Galaxy Tab S Android Development] surfer300ZX:
I have a Shield tablet running 14.1 and a Nexus 6p running 15.0 , both have L1 security, but L3 on the Tab S. Therefore, your statement is 100% false and misleading to people who want this problem to be fixed.
[Galaxy Tab S Android Development] jleiss:
stuck in loop booting TWRP after downloading 1/5/19 update

Went to install new update build for lineage 14.1 for my SM-T800 as I have in the past but this time after downloading and telling it to install my tablet gets stuck in a loop trying to boot TWRP. The TWRP logo comes up and it sits there for awhile then the screen flashes and reboots, and its stuck this way, only other thing I can do it boot into download mode. I did try to load a newer version of TWRP onto the device with Odin but it didn't change anything. What are my options for resolving this (thinking I can reflash the stock ROM, and then reroot it.. found the stock ROM and downloading it).
[Galaxy Tab S Android Development] risant:
When wll lineage 15.1 oreo fot sm-T805:be release?
[Galaxy Tab S Android Development] Limakos:
Probably never.
[Galaxy Tab S Android Development] meduza:
... someone installed today's update already? I'm not really able to, stucking on the boot animation .... . Could it be the substratum overlays?

I'm on a ROM trip ;) Since AICP seems discontinued and RR`s performance isn't satisfying me at all, I just installed the 05. January build today and feel a performance like I'm used to from AICP :) How comes ... ;) Thank you [MENTION=6663552]DarkExistence[/MENTION] !!

m.

---------- Post added at 07:41 PM ---------- Previous post was at 07:41 PM ----------

... someone installed today's update already? I'm not really able to, stucking on the boot animation .... . Could it be the substratum overlays?

I'm on a ROM trip ;) Since AICP seems discontinued and RR`s performance isn't satisfying me at all, I just installed the 05. January build today and feel a performance like I'm used to from AICP :) How comes ... ;) Thank you [MENTION=6663552]DarkExistence[/MENTION] !!

m.