yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Android Development] amateurhack:
I tried it not rooted, rooted, still doesn't work. No majisk on my Tab. Is all good., not a big deal. I was just seeing of anyone ends had issues before we call it a bug.

When the first N ROMs came out, there were similar issues among all of the streaming apps, and the YouTube videos as mentioned. At some point those issues all seemed resolved, but I was not on CM/Lineage at that time. Is just the one app, so who knows what the issue may be. If a Dev wants to take it up fine, but I'm not sweating it.
[Galaxy Tab S Android Development] amateurhack:
I've tried it rooted and not rooted. I don't have majisk. Back when the first N ROMs first came out, there were lots of issues with video streaming apps including YouTube. At one point the issues seemed to have been resolved, but I wasn't using CM/Lineage at that time.

This is not a big deal for me. I was just verifying the issue in case a dev wanted t to take it up. If not, I'm good. Sorry if the pining for a new tablet made it seem otherwise.
[Galaxy Tab S Android Development] amateurhack:
Oops. Sorry for the double post. I sent it, but then it didn't show up so I typed a new version later.
[Galaxy Tab S Android Development] CHGICEMAN:
Hello, does the transfer to the TV work with you?
[Galaxy Tab S Android Development] KingUsman:
Is it possible to enable fast charging on this tablet?
[Galaxy Tab S Android Development] richardfeb2@gmail.com:
Yes ! i use my Motorola Phone Turbo Charger , and it charges in half the time it would take with its own charger.
[Galaxy Tab S Android Development] boardwarp:
Currently I've got an SM-T700 running CM12.1 just fine, but when I try upgrading to Lineage OS, it gets stuck on the "Samsung Galaxy Tab S SM-T700 Powered by Android" boot screen. I can then flash it back to CM12.1 no problems, but no matter what I try I can't seem to get Lineage working.

I'm using the 20 September 2017 build

I'm using GApps 7.1 ARM mini

I'm going into advanced wipe in TWRP and wiping everything except the external SD each time

I'm wiping the cache and dalvik after each installation

Any ideas?
[Galaxy Tab S Android Development] SkilesAwaRz:
Just upgrade your tab to the lastest stock rom, it'll update your bootloader. You can do it through odin.

With this rom, you must have MM bootloader.

Envoyé de mon PLK-L01 en utilisant Tapatalk
[Galaxy Tab S Android Development] KingUsman:
Anyway to stop the capacitive buttons from lighting up every time I touch the screen?
[Galaxy Tab S Android Development] GoodDude82:
I'm an amateur player, could you post this rom to T705, thank you
[Galaxy Tab S Android Development] deadman96385:
https://download.exynos5420.com/LineageOS-14.1/klimtlte/
[Galaxy Tab S Android Development] GoodDude82:
Thank you!
[Galaxy Tab S Android Development] lollo78:
Just installed. During a simple web browsing system freezes. Nice, but not "stable"
[Galaxy Tab S Android Development] KingUsman:
Hoping for LineageOS 15
[Galaxy Tab S Android Development] smirren:
Sure. Just go into "Settings -> Buttons -> Backlight" and set Button brightness to 0%.

---------- Post added at 09:59 AM ---------- Previous post was at 09:42 AM ----------

I'm also having trouble with the tablet freezing or crashing, especially when browsing the web using Google Chrome.

Does anyone know if these issues have been adressed to the developers of this otherwise great ROM?
[Galaxy Tab S Android Development] lollo78:
I downloaded the first ota update, but if I hit OK, system doesn't reboot into recovery (I use twrp) to install it.

I'm doing something wrong or it is a known issue?
[Galaxy Tab S Android Development] KingUsman:
I only want the backlight to turn on when I touch the capacitive buttons and not the screen, I don't want to turn it off completely
[Galaxy Tab S Android Development] thejase:
Mine has done this the entire time. I'm not sure why but no big deal. I just update it manually by finding the download directory in TWRP. If I remember right it's under data\lineageos_updates.
[Galaxy Tab S Android Development] :
Thought i'd give it a go as my Tab S seemed to get slower every week on stock MM . . What a difference :)

Its like a new tablet . No crashes or reboots after 2 days of usage , although i have noticed playing various movies ( in various formats ) stored on SD card with mx player ( using HW decoder ) seem to be a bit jerky , but switch to SW decoder and everythings fine :)

Excellent job .
[Galaxy Tab S Android Development] Vinchester1986:
Hi, deadman. Big thanks for you work making our tablet actual and still well usable. I have a question about Oreo. Can we expect Lineage 15 build for T700?
[Galaxy Tab S Android Development] lollo78:
After some days all works fine.

But adaptive brightness stutters. It's not "fluid".

Do you also notice the same thing?
[Galaxy Tab S Android Development] Vinchester1986:
Same problem with adaptive brightness. Turned it off.
[Galaxy Tab S Android Development] ZimriTech:
Nvm, I did things fine.
[Galaxy Tab S Android Development] grgart:
Hello,

I can't fond the settings to change Name of the device.

Is it posible to change/set name for my SM-T700 with this ROM?

Thank you.
[Galaxy Tab S Android Development] KingUsman:
File transfer with pc is not working on latest update, neither is otg
[Galaxy Tab S Android Development] Pingu_3D:
Yes I experience the same fluctuating brightness and also suffer from WiFi cutting out even though I am near the router. Nothing else near me suffers WiFi drops so I think it is the tablet.
[Galaxy Tab S Android Development] galaxy411:
Why is there no fingerprint lock anymore after 14.1? I have a galaxy tab s SM-T700. Now I lost the fingerprint option to unlock. Only options is a PIN/PW.?????
[Galaxy Tab S Android Development] Vinchester1986:
Known issue. No plans to make it working.
[Galaxy Tab S Android Development] galaxy411:
wow thanks for the clarification. so everyone is having this issue and doesn't care? Do any custom roms have the fingerprint? I would think this is a major defect.
[Galaxy Tab S Android Development] Vinchester1986:
It's impossiple to maintain this functionality by developers in Lineage/AOSP Roms at least for Andtoid 7 due to missing source code from Samsung as far as I know. Deadman already posted an answer somewhere in this thread.

Honestly used FP sensor didn't work well even in original ROMs so I think it's not big loss.
[Galaxy Tab S Android Development] galaxy411:
That's already true. I hated it and never worked great. thanks, so far the ROM is great and so fast with barebones apps.
[Galaxy Tab S Android Development] canned_polar_bear:
i'm glad that time isn't being spent on the fingerprint stuff.. it seems to be very flaky and a huge time sink better spent elsewhere.. at least that's my impression from a build on a different device.
[Galaxy Tab S Android Development] certainOblivion:
Hey guys, has anyone tried out an MHL adapter to see if it works? Just thought I'd ask here before I buy it and try it myself :)
[Galaxy Tab S Android Development] vecna:
First of all sorry if I am posting incorrectly since this is a support thread, if this post is incongruous please say, and I will delete it.

Ok I am beginning to understand the fingerprint issue, all the fp hardware runs in trust zone and everything communicates via mobicore.

https://sensepost.com/blog/2013/a-s...one-os-and-trustlets-in-samsung-galaxy-phone/

Its all a frigging nigthtmare if working from scratch, but we are not working from scratch.

This mobicore implementation does work https://github.com/Schischu/android_chagall_klimt but has been broken by the new hardware tree. I have been told its due to mobicore version mismatch, which I am trying to fix, but its still just above my skill level.

The fp hardware DOES work well, at least in my stripped down stock rom. If there are problems they come from the other Knox components and processes, which if removed no longer cause problems.

Likewise it works quite well in Schischu's rom.

Now I don't wat to be controversial here, but deathly kernel has swallowed a hell of a lot of effort, and ok on paper and to the programmers it should be so much faster and more stable with less amps used. In real world benchmark tests ( antutu, geekbench, and 3dx ) you can see zero performance gain, likewise power is only improved significantly in certain use cases.

I'm not really a code Guy, so maybe I'm missing something, but why the hell is the team working on android 7, with android 8 test builds, when the android 6 branch still has outstanding bugs? Samsung vendor blobs are now at android 6 , which to me means we can get the mm branch working propperly with minimal effort, squash all the framework related bugs, and call it a release.

that's what we do in the Linux distro world, otherwise end users get pissed :)
[Galaxy Tab S Android Development] canned_polar_bear:
dunno why you quoted me. it was my just personal opinion. i guess, in my own clumsy way, i was expressing how very happy I am with the quality of this rom and grateful for the fact that it has extended the useful lifespan of this device by several years already.
[Galaxy Tab S Android Development] vecna:
No reason mate, :) just putting my 2cents in about the fingerprint thing.
[Galaxy Tab S Android Development] DarkExistence:
Well, the fingerprint sensor does work on our CM-13.0 (Marshmallow/Android 6.0) builds and it took a hell of a time to get it working on that, even though we had the Android 6 blobs from Samsung. In Android 7 there are a ton of bugs that need fixing, and that we are constantly looking into (atm we are trying to figure out this whole freeze crap the tabs are having every now and then). Oreo is far from ready, at least for the Tab S devices. N1awifi working, ha3g working, v1 works, k3gxx works. Chagallwifi/chagalllte does not have wifi, klimtwifi hasn't booted yet.

We stopped working on Android 6 because Lineage moved on from Android 6. We are LineageOS developers after all so we follow them. Of course we could still try to build it but why would we when its still cyanogenmod, something totally dead. The code is availableon our github for you to use freely whenever you want to, as long as you credit it. Linux distro world is different then the Android world. Android users want the latest and greatest most of the time. We plan on supporting CM-14.1 for as long as possible.

We spent months on fixing bugs with the android 6 blobs from Samsung, and that can be seen in our trees. Deadman and Tincho worked hard on the kernel and vendors, along with the rest of the team working on the various device trees, frameworks etc. So we aren't not using them. We are using them to their best ability.

Yes, the fingerprint sensor is a pain to fix. Its a totally out-dated sensor with crappy blobs which yes, do have performance implementations on the ROM following our extensive testing, so we booted it. In our ROMS the fingerprint sensor will not, and will never be enabled. Again feel free to do what you want with our code.

As for deathly, the governor mode (interactive) has been fine tuned for months by our own tincho, and is at the best it can be. We have tried multiple different performance modes and this is the best we can get and the most stable we can get it for now. The other modes have not been tuned for our kernel at all, and this is actually the only governor that has been fine tuned for our SOC. You can access the others only because he messed with some stuff. Apart from that, the Power HAL can only work on the interactive governor.

So even though we don't reply to a lot of stuff on here, we are always doing stuff behind the scenes. We do read everything here. We do read all the logs that are provided. And yes, we do this for free. So we don't have to focus on Android 6 if we don't want to. We do this for fun, its our hobby. We just want the latest on our tablets and we mainly just want to get them working. That is the difference between this, and a linux distro.

Dark
[Galaxy Tab S Android Development] HijoProdigo:
Dark, thank you very much for explaining. It gives us users, if you could call us that, a little glimpse of what goes on behind the scenes. Can't imagine all the work it takes, and I for one very much appreciate it!
[Galaxy Tab S Android Development] vecna:
[MENTION=323462]Dark[/MENTION]

Thanks for the info mate.

Its very much like the Linux world, but you guys are upstream and distro at the same time, weird since the two have very different objectives at times.

Yes in a few months I will fork the cm13 branch , for Fenris 2. And spend my "android time" on fixing any remaining bugs and applying monthly security patch level updates, and trying to integrate decompiled code from stock features I like. I just need a stable bug free, and most importantly security patch updatable base to build fenris on top of.

If I ever do anything useful ( unlikely since I'm still lightyears behind where I should be) will push it upstream as is usual.
[Galaxy Tab S Android Development] hamelg:
I need the permissive mode to mount NFS share. It seems the current policy doesn't allow any processes to modify enforcing mode (see the selinux boolean secure_mode_policyload). I've tried to modify the boot.img to add the linux kernel parameter androidboot.selinux=permissive, but it has no effect. I don't understand where the kernel parameters are setup. I don't find the parameters in /proc/cmdline.
[Galaxy Tab S Android Development] galaxy411:
how do i upgrade the lineageOS as I see there is a new update now? I dont want to lose any of my current information. I have that TEAM PROJECT software.
[Galaxy Tab S Android Development] meboy:
Does cast to Google Chromecast work?
[Galaxy Tab S Android Development] bustr85:
Quick question: Is there a working fix for Netflix on this Rom?
[Galaxy Tab S Android Development] esjames:
Netflix works fine for me, rooted using Magisk.
[Galaxy Tab S Android Development] SkilesAwaRz:
Just download the apk from the Netflix website and not the play store

Envoyé de mon PLK-L01 en utilisant Tapatalk
[Galaxy Tab S Android Development] hamelg:
Hello,

I encounter an issue with the wifi. When using adb remote or a ssh server on the device like simplesshd, the keytroke is extremly laggy. It seems the tablet doesn't reply back immediately. To see the issue, open a remote connection via adb :

On the device : Parameter >> Developer options >> Enable ADB over network

On a remote client : adb connect <IP> && adb shell

A tcpdump on the remote client shows the packet sent and the reply delay.

10:54:31.103609 IP pc.lan.59940 > mytabs.lan.personal-agent: tcp 30
10:54:31.826666 IP mytabs.lan.personal-agent > pc.lan.59940: tcp 0
10:54:31.829406 IP mytabs.lan.personal-agent > pc.lan.59940: tcp 0
10:54:31.829434 IP mytabs.lan.personal-agent > pc.lan.59940: tcp 0
10:54:31.830988 IP mytabs.lan.personal-agent > pc.lan.59940: tcp 24

1s to receive the reply !

Is it a known issue ? how to fix that ?

On the other side, the wifi works fine and the throuput to transfert bulk data is ok.

---------- Post added at 11:39 AM ---------- Previous post was at 11:05 AM ----------

To get the permissive mode, you must rebuild the kernel with this setting :

CONFIG_CMDLINE="androidboot.selinux=permissive console=ttySAC2,115200n8 vmalloc=512M androidboot.console=ttySAC2"
# CONFIG_CMDLINE_FROM_BOOTLOADER is not set
CONFIG_CMDLINE_EXTEND=y
CONFIG_SECURITY_SELINUX_DEVELOP=y

and apply this patch on the source kernel tree :

--- arch/arm/kernel/setup.c.orig 2013-08-02 12:30:00.467880848 +0200
+++ arch/arm/kernel/setup.c 2013-08-02 12:12:01.659851483 +0200
@@ -669,9 +669,11 @@
static int __init parse_tag_cmdline(const struct tag *tag)
{
#if defined(CONFIG_CMDLINE_EXTEND)
+ char tmp[COMMAND_LINE_SIZE];
+ strlcpy(tmp, default_command_line, COMMAND_LINE_SIZE);
+ strlcpy(default_command_line, tag->u.cmdline.cmdline, COMMAND_LINE_SIZE);
strlcat(default_command_line, " ", COMMAND_LINE_SIZE);
- strlcat(default_command_line, tag->u.cmdline.cmdline,
- COMMAND_LINE_SIZE);
+ strlcat(default_command_line, tmp, COMMAND_LINE_SIZE);
#elif defined(CONFIG_CMDLINE_FORCE)
pr_warning("Ignoring tag cmdline (using the default kernel command line)\n");
#else

see :

https://wiki.ubports.com/wiki/When-the-Bootloader-Decides-to-Override-your-Command-Line
[Galaxy Tab S Android Development] h3ok:
Dirty flash...
[Galaxy Tab S Android Development] tnimk:
Installed this a few days ago and it's running pretty good but I do notice that the battery seems to die a lot faster now. Like at least 30% faster.

Is the first few days needed for things to "settle in"?
[Galaxy Tab S Android Development] chibot75:
Been using this rom as a daily driver for a while and found that I needed to charge the battery daily. Watching YouTube for an hour chewed through 30 to 40 per cent battery. Sometimes it gets to 20% and then just dies really quickly. Have now gone back to stock and whilst it doesn't have the bells and whistles of lineage, the battery life is excellent. One hour of YouTube only consumed 15% battery and can now charge the tablet every two or three days.

There is definitely something around the display that is causing the battery drain.
[Galaxy Tab S Android Development] richyg81:
Any ideas if the newly disclosed MediaProjection vulnerability will be patched in the next update?
[Galaxy Tab S Android Development] KingUsman:
Can someone add this commit? It stops the capacitive buttons lighting up when touching the screen

https://github.com/LineageOS/android_device_samsung_klimtwifi/pull/2
[Galaxy Tab S Android Development] hamelg:
I did some additional tests.

The behavior is the same with the MM stock rom, so it is not a bug in the lineage rom.

There is something wrong with the wifi powersave mode. When switching off the powersave mode, the issue disappears but comes back after few seconds. So, I have found out a workaround : I execute this script in background :

while : ; do iw wlan0 set power_save on ; iw wlan0 set power_save off ; sleep 3 ; done

Is it possible to fix that ?
[Galaxy Tab S Android Development] DelphinusMinor:
Is the battery issue still an issue with the latest nightly?
[Galaxy Tab S Android Development] C0derbear:
After just a couple days, the current build seems better on power than 2 iterations ago, but it's too early for me to say for sure how it's doing.

I had skipped one build because when I tried it (11/22 build) I continually had crashing from Google Play after boot (using current Beans GApps).

Had the same Google Play crash problem with the current build (11/29) so went and fetch the current OpenGApps 7.1 Nano package and tried that, and all is well behaved.

I may try Beans again in the future, but it's now quite out of date as the last build was July 25.
[Galaxy Tab S Android Development] PcOliveira:
Mine does not como off the "ball slide" animation in the first boot.
[Galaxy Tab S Android Development] F3AR420:
I have no wifi after installing
[Galaxy Tab S Android Development] bjrr:
Does this rom support adoptable storage natively? Has anyone tried?
[Galaxy Tab S Android Development] izimen:
Nice rom for my T700 fast, good battery life.

Good job to the developper
[Galaxy Tab S Android Development] kevria:
Does anybody know what the file location is that the lineage update utility downloads rom images to? The utility doesnt properly reboot my table for an update so Im wondering whether the images are getting deleted/cleaned up because my tablet keeps complaining about being out of space yet it shouldnt be.
[Galaxy Tab S Android Development] C0derbear:
/data/lineageos_updates/

I use Root Explorer to move the file from there to my SD card where I keep a directory of the most recent 3 releases, along with google apps bundle ( BeansGapps and openg_gapps, just 'cause ) and the Lineage "addonssu-arm-signed.zip" so that I have them all in one place for use in recovery.
[Galaxy Tab S Android Development] bplzip:
The rom image is downloaded to /data/lineageos_updates.
[Galaxy Tab S Android Development] kevria:
That freed up 650mb, thanks.
[Galaxy Tab S Android Development] HKSpeed:
does anyone experience lag with this rom?
[Galaxy Tab S Android Development] solaris1972:
Only 4 cores?

Just installed this week, the rom is great and is giving my old TM700 a happy new life.

However, I found a log of lags and slowdowns and today I just found that only 4 of the 8 cores are being used and I suspect it's the power efficiently ones from big.LITTLE.

Is this a bug or just lack of support from Sammy (blobs?) that's preventing the devs from using the full power of the device?

Thanks in advance
[Galaxy Tab S Android Development] mrcet007:
How stable is this room? Will the developer release a RC build or the latest nightly good enough?

What's are the bugs associated with this one? Lag, battery drain etc? Want to make sure it's stable before moving away from Samsung stock rom
[Galaxy Tab S Android Development] amateurhack:
I think most of those questions are pretty well answered throughout the thread, and, like all custom ROMs (especially on aging hardware like the T-700) YMMV.

Happy flashing!
[Galaxy Tab S Android Development] ZimriTech:
edit - I decided to stay with LineageOS and I fixed my issues
[Galaxy Tab S Android Development] DarkExistence:
Thats always the case, even on stock. Exynos 5420 is an 8 core processor, but Samsung only activate 4 cores for some reason and there is nothing we can do about that sadly. Waste really, but it was once of the first 8 core processors so most likely wasn't very good.
[Galaxy Tab S Android Development] C0derbear:
I may clearly be not remembering correctly, but wasn't our SOC design NOT to activate all 8 cores, ever - but to only use the set appropriate for the current load, and favor the smaller / lower-power set when possible to minimize power consumption?

This was IIRC one of the misleading marketing spins of the whole mobile multi-core device sequence that frustrate me and confuse the general public - "N core" devices rarely if ever *used* all N cores for current activity (8 core systems really were only 4 core at a once, etc.).

I've honestly lost track of current state though.
[Galaxy Tab S Android Development] HibikiTaisuna:
Are there any new information concerning Lineage OS 15.1 support? And will you release a new build today or during the weekend including the newest security patch level? As it does have some critical patches for Spectre it would be good to roll out the update as fast as possible.
[Galaxy Tab S Android Development] DarkExistence:
Lineage 15.1 isnt coming anytime soon for our devices. And a new build will be released when it is our turn on LineageOS build system, the usual build date.
[Galaxy Tab S Android Development] :
Hi,

I got this Tab T700 today with Android 6.0.1 and I was expecting it a little less laggy,

is it less laggy with this rom?

thanks :)
[Galaxy Tab S Android Development] amateurhack:
Just of the top of my head, I think you're correct. The CPU would pick the appropriate core based on load, and there would never be a situation where both cores were activated at the same time.
[Galaxy Tab S Android Development] R3van:
Hi,

i have dynamic brightness activated and when i turn on the display it stays for roughly 5-10 secs quite dark until the brightness will be adjusted.

Is that normal behavior or can i speed up the process?
[Galaxy Tab S Android Development] DarkExistence:
normal, the tabs have crappy light sensors.
[Galaxy Tab S Android Development] sesser:
Flashed this few days ago, why this rom is so slow? Its not very stable either.... :/
[Galaxy Tab S Android Development] C0derbear:
Doesn't seem to be a common situation, I know it works fine on my device and I'm pretty sure there'd be more complaints if it was a more wide spread situation.

I can't speak for the LOS team and I am sure no guru, but I'll go ahead and ask if you did a full clean flash and which gapps you used, just to get the info.

fwiw, I've been using opengapps again as i ran into some quirky behavior with bean's ... but I haven't looked for an update of either since oct or nov last year and the situation may have changed, IIRC the LOS team suggest bean's gapps.