yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Android Development] bask0o:
I have been searching on how to check the bootloader version but didn't find any clear way.

IronRom is:

ROM OS Version: 6.0.x Marshmallow

ROM Kernel: Linux 3.4.x

ROM Firmware Required: SM-T800, SM-T805

Based On: Stock Touchwiz

Also, my TWRP is v2.8.7.0.
[Galaxy Tab S Android Development] McSaarli:
Hi,

right now the flashlight is working again without having done anything.

Next time it fails I will try the solution you provided.

Martin
[Galaxy Tab S Android Development] hachibei:
Which nightly did the mobile data works? I'm using the latest nightly 20180418 and mobile data is broken (clean install + multiple rebooted).
[Galaxy Tab S Android Development] BulldozerHavoc:
I am on 14.1-20180407 and 3G is working fine with Data roaming enabled, try setting prefered network type to 3G. Can't test LTE here..
[Galaxy Tab S Android Development] hachibei:
Finally got LTE and 3G working

So after a day of testing, I finally manage to get LTE and 3G working beautifully :fingers-crossed:.

It seems that the ROM doesn't properly trigger the carrier SMS that send the APN settings (also, this might also relies on the carrier implementations).

Since I have sims from different carriers and a phone running LineageOS 13, here's my finding after some experiments:

1. Sim A when inserted to my phone, triggerred a carrier SMS for APN settings. However when inserted to the tablet which was cleanly flashed with the latest nightly, the APN settings SMS wasn't sent. I have to manually add the APN settings and got mobile data (3G and LTE) working after rebooting.

2. Sim B from a different carrier doesn't trigger the SMS that carry the APN settings. However to my surprise, the APN is already prepopulated on both the phone and the tablet (when tested afterwards) so I'm guessing these APNs probably came on the sim itself. 3G and LTE works without a hitch on this sim.

Therefore, for users that may have trouble getting their mobile data working, they might have to check their APN list via:

Settings > Data usage > Top right Overflow menu > Cellular Networks > Access Point Names

and manually add the APN setting themselves. If they doesn't know what to put into what, try putting the sim on a spare phone and copy the APN configuration manually (screenshot helps).

Side note: This also happens on a different ROM (AICP) so it might not be LineageOS specific.
[Galaxy Tab S Android Development] Hadi99:
I face lag when I install certain magisk modules (or installing them systemly) such as Google Framework. Can anyone confirm. (The exact same setup runs perfectly fine on my G5 running Linage OS version of Android 7.1.2)
[Galaxy Tab S Android Development] fabryxy:
Hello!

First of all I would like to thank you for the great Rom, it works beautifully!

I am running the last build 20180505 and everything works fine except one thing that appear to be under-performing.

With the original rom the tablet was charging at maximum hardware allowed power with a current draw of 1.7A.

Now with this great rom it looks like there is a cap at 1.22A.

I am using the same charger, cable and battery was about 30% when I plugged the unit in. In battery status I see AC mode.

Maybe it is something that has to be tweaked in the kernel?

One other thing that is not rom related and was discussed somewhere else without solution yet....my hardware is SM-T805W, I think Canadian version and in someway the ability to make phone calls has been disabled.

Do you think there is any way to re-enable the feature?

Thank you very much again for the fantastic work!

Fab
[Galaxy Tab S Android Development] visualdrome:
Hello to everyone, I use the tab with a Bluetooth keyboard.

Since I installed this beautiful rom if I don't use the keyboard for 5' I have to reconnect it again opening the menu, not only the notification panel (with the official Samsung rom the keyboard do not lose the connection).

There's a workaround for this annoying behavior?

Thanks
[Galaxy Tab S Android Development] peterpan07:
Check that threat I posted many pages before the battery problem solution that works for me
[Galaxy Tab S Android Development] billybanana:
Flashed my SM-T805Y for the first time yesterday. Nice work lads. Has breathed new life into my ageing tablet.
[Galaxy Tab S Android Development] BulldozerHavoc:
Slower loading times?

Since ver 14.1-20180428 I have noticed slower loading times, anybody else? I am now on 14.1-20180505.
[Galaxy Tab S Android Development] Novembacolor:
Great work guys
[Galaxy Tab S Android Development] kuromusha38:
which su binary should I flash? 14.1 or 15.1?
[Galaxy Tab S Android Development] visualdrome:
https://download.lineageos.org/extras

the first one (addonsu-15.1-arm-signed.zip)
[Galaxy Tab S Android Development] Snopy234:
Why do you want to use the 15.1 SU for Lineage OS 14.1? :confused: ARM is correct :)

Is there any changelog for this nice rom ?
[Galaxy Tab S Android Development] visualdrome:
Ooops:eek:, you right: addonsu-14.1-arm-signed.zip!

Thanks
[Galaxy Tab S Android Development] kuromusha38:
This is the first rom I have installed, it is very laggy. Is this normal? Should I try another rom?
[Galaxy Tab S Android Development] Snopy234:
Please use the latest version of this ROM. Actually this ROM is the latest version: lineage-14.1-20180512-UNOFFICIAL-chagalllte.zip

You can find new versions at the bottom of the list ;)

In my opinion this rom has less bugs than the official :)

Is there a changelist for this rom, because there are no changes in the filesize. It would be glad if I can check the changelist to decide to update or not.
[Galaxy Tab S Android Development] kuromusha38:
I do have the latest unofficial rom, but it is still laggy as
[Galaxy Tab S Android Development] Lumpnhendl:
Yes it is the same for my tab pro 10.1 (sm-t520) with lineageos 14.1. Also camera freezes a lot with reboots. I'm now on lineage 13 which is more stable (no camera issues) and rather fluid. You should give it a try.
[Galaxy Tab S Android Development] W-Zaki:
It's working flawlessly with me. Actually, it's the best rom I've ever used for t805.
[Galaxy Tab S Android Development] LenAsh:
Thread cleaned a little.

Members are reminded that this is a Development thread, not a discussion/debate thread.

Thanks!
[Galaxy Tab S Android Development] peterpan07:
There is not exactly an change log for our device T805 but with the app from the app store "los changelog" you can monitor changes for the T800

Only difference in that log there will be nothing about your mobile connection

---------- Post added at 07:30 PM ---------- Previous post was at 07:24 PM ----------

Thank you that for but really bit more information about why a weekly build stop working for the T805 would be nice and would not start discussions

I did check all other devices and they have been updated.

BTW development, does anyone have also problems CPU gets hot since last build? (No changes in log that explain, and no changes this side)
[Galaxy Tab S Android Development] ThomasOMalley77:
Thank you for the update... :)
[Galaxy Tab S Android Development] peterpan07:
Maybe someone missed my question

Does anyone else also get an overheating device last week's around front camera

Didn't change any settings but happen to me last week's. Tried 052618 build still same
[Galaxy Tab S Android Development] TRNSLN:
No problems here...

SM-T805 cihazımdan Tapatalk kullanılarak gönderildi
[Galaxy Tab S Android Development] BulldozerHavoc:
Yes, on some games it gets really hot (CPU usage?), exactly under the samsung logo, can't assosiate the problem with a build number though, seems like it depends on the game (CPU intensive) and your finger placement to notice it, eg when I play Sky Force Reloaded and my finger gets over that part of the screen I really feel it, but with CSR 2 where my fingers and hands are on the lower side (home button) I never notice it, it get's hot but not as much with this game.... Most probably CPU or Connector Header, will try to open it and find out. Will report back when I do.
[Galaxy Tab S Android Development] peterpan07:
Using that rom for long never had that

Also games didn't change I play

Noticed even surfing the web
[Galaxy Tab S Android Development] sadowling:
Can someone please post a working link to the latest Lineage builds, the 'Jenkins builds' link on the first page doesn't seem to work for me anymore. I searched the forum but nothing came up.
[Galaxy Tab S Android Development] DarkExistence:
It works fine?
[Galaxy Tab S Android Development] ThomasOMalley77:
I can confirm the link to the site didn't work earlier.

It now works again. :)
[Galaxy Tab S Android Development] DarkExistence:
Ah there was some down time with SSL certificates which were fixed once spotted. :)

Glad it works again
[Galaxy Tab S Android Development] fabryxy:
Hello all again,

I have been quickly looking into the issue with "slow" charging when compared to the original rom. I don't know yet what kind of ic this tablet is using for charging but I am sure that with this rom the charging is limited to a current draw of only 1.2A compared to the stock 1.7A.

On a quick look into the kernel source i see the following into max77803_charger.c:

int SIOP_INPUT_LIMIT_CURRENT = 1200;

can this be the reason why we are limited to 1.2A?

Thanks

Fab

---------- Post added at 08:07 AM ---------- Previous post was at 07:57 AM ----------

If the IC is anything close to this http://pdf1.alldatasheet.com/datasheet-pdf/view/879326/MAXIM/MAX77801.html the max supported charging rate is actually 2000ma
[Galaxy Tab S Android Development] peterpan07:
You can change it with the kernel auditor I set it there to max and to apply on boot. Work perfect
[Galaxy Tab S Android Development] fabryxy:
Thanks Peterpan07!

Fab
[Galaxy Tab S Android Development] golfinggino:
i had some issues with my tablet so i did a clean flash of the latest rom and i cant get root no matter what i do - anyone else have this issue and how can i fix it
[Galaxy Tab S Android Development] visualdrome:
Hello, tomorrow I have to show a project at the university but I have some problem with the camera using HP Reveal (an app for the Augmented Reality): the image taken is distorted in any position I turn the device.

I tried to switch auto-rotate / Landscape but nothing change.

There's some setting I can change?

There's some third part application I can install to set the camera in the right way?

Thanks
[Galaxy Tab S Android Development] gellmar:
How does it look like? Can you post screenshot and the link to the app?
[Galaxy Tab S Android Development] visualdrome:
In attachment.

The problem (axes inverted and distorted) it's only with the app (HP Reveal) not using the camera for record video or take a picture.

In the other way the app work fine in all other devices (smartphones).

Thanks
[Galaxy Tab S Android Development] gellmar:
Can you try forcing Portrait mode not Landscape?
[Galaxy Tab S Android Development] visualdrome:
What do you mean with "forcing"?

I tried to change the setting in the notification panel to "portrait" but no changes".

The image is also stretched.

I can turn round the tablet but never I can get the right image; it changes every time
[Galaxy Tab S Android Development] Chaos234:
Hey together,

I am not sure why but this time I can not reduce the sound from any call and in addition I have very often no sound when I try to call but I can't restart my tablet every time this happens so please

take a look into this and fix both problems, thanks.´

Also Google Play Store can't install/update apps and I blame this stupied fused storage for that ... nobody needs this as it causes damage to the SD-Card. It has already destroyed two SD-Cards on my side so please disable/remove it, thanks.
[Galaxy Tab S Android Development] Chaos234:
Is it possible todo this before installing the custom rome or should I wait untill all is finished? I could only remove this entry with Deathly Auditor but wasn't be able to add the # on the linses start.

Maybe setting it to false instead of true or adding a # will work too?
[Galaxy Tab S Android Development] coffee81:
Hi I upgraded last Tuesday from 14.1 20180609 to 20180619.

Since then, when I run an app for automated task, I got a message saying that screen cannot be detected because SElinux is enforcing.

That message only appears in 20180619 version but not beforehand.

I tried to change the SElinux from enforcing to permissive, using like SElinuxmodechanger or the SElinux switch but all in vain.

Any clues to change the SElinux ??

Btw, Thanks all developers and others for contributing to this rom:good::good:
[Galaxy Tab S Android Development] visualdrome:
Hello,

I'd like to upgrade to the last 14.1-20182603

Can you remind me the LOpenGaps t download (https://opengapps.org/):

Platform Arm 65

Android 7.1

variant: ?

Right?

Thanks
[Galaxy Tab S Android Development] DarkExistence:
ARM not ARM64, then Android 7.1 and then choose which ever packages you want. Pico having the least apps etc
[Galaxy Tab S Android Development] gellmar:
Post the output of "adb logcat -d | grep avc | grep denied" please, I will check it and push the changes to team Gerrit.

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

I cannot reproduce the extsd card issue, however about the call - can you please elaborate which call do you get no sound for? Is it a GSM call or Skype / other messenger app call? Is a BT headset attached or wired one? The in-call volume was fixed by me last week, so now both volume change and mic mute work from dialer app interface.

After device reboot I usually press Volume Up button a couple of times so volumes are adjusted and calls are done perfectly afterwards. I will fix it once I understand why the volume is not applied automatically.
[Galaxy Tab S Android Development] DarkExistence:
Can you please provide a logcat of the call so we can attempt to see whats going on? Thanks
[Galaxy Tab S Android Development] Chaos234:
Can you provide me with the correct command please? I think that it must be done on windows in an adb shell?

Also my deveice can't longer read out my SD card (64 GB Transcend, microSD XC I), but I can use it to install the ROM again. But since that time,

I can no longer do any calls because I have no audio output which is worse.

Not sure what went wrong but with the rigth commands and where to execute them I should be able to provide all logs to this.

It was a normal call without any kind of attached headsets (either cabled nor cableless ones). I also wondered, why the audio this time was that loud and why it didn't get reduced after I reduced the corresponding volume. Not sure if it's an error in the ROM or maybe with my device self because since my SD died, like written above, I have no sound when I try to call, whyever this happends but I will also not touch this with "Deathly Auditor" to not damage anything else before the logs not checked out.

The only thing which I use from Deathly Auditor is the Battery Part to charge it at "full speed" since I woundered every time why my power gets drained even with a pluged in power bank (2.4 A max output). Checked with some Battery Apps and noticed that the charge was less then the discharge but since I changed the values now the charge is higher then the discharge. Negative side effect is, that my power is drained a bit faster, not sure why but it is fine. Maybe I should reduce the input a bit more (I can provide a screen if someone can help me out here).
[Galaxy Tab S Android Development] gellmar:
The loudness on speakers is tuned on maximum because I increased it, otherwise calls are very quiet on my daily driver tablet. The question of "why it didn't get reduced after I reduced the corresponding volume" can be answered if you attach the tab to PC (by USB cable), turn on Developer Settings - Android Debug Bridge and post the output of the following command to hastebin:

adb logcat -b radio | grep -i oem > call.log

Also you can run from phone's terminal app as root:

logcat -b radio | grep -i oem > /sdcard/call.log

and make a call, trying to reduce and increase volumes, turn mic on and off etc.
[Galaxy Tab S Android Development] visualdrome:
Last doubt:

I already have lineage rom on my SM-T805; I don't need to flash by Odin; I can just:

1) factory reset the device (Wipe data, cache and dalvik) by recovery (I have the 3.0.2-0: I have to get a new one?)

2) install the lineage zip file (by recovery)

3) install the google apps (always by recovery)

4) finally root the device (if lost).

Right?

Double thanks!!
[Galaxy Tab S Android Development] DarkExistence:
Yep. Which lineage version are you updating from? If it’s pre-14.1 then you have to wipe system aswell (id do it anyway even if it’s from a 14.1 rom just to make sure it’s stable)
[Galaxy Tab S Android Development] visualdrome:
I have Lineage 14.1-20171118.

I have recovery 3.0.2-0: it's ok or I need a new one?

Thanks
[Galaxy Tab S Android Development] gellmar:
Check your DM.
[Galaxy Tab S Android Development] coffee81:
Thanks for reply.

What is DM ?

how to check ?

and what shall I do after checking ?

thanks !
[Galaxy Tab S Android Development] gellmar:
Direct Messages. I sent a kernel I built for you.
[Galaxy Tab S Android Development] Maheshwara:
Hi folks,

I am really wondering why my T805 consumes huge amounts of battery power without doing anything. Please see attached screenshot - last full charging 16 hours ago, all the time only standby, but now only 63% left...??? Any similar experience from your part? Or even better - any solution?

I have already replaced battery, made full reset and only installed very few apps after that, but nothing has changed so far... With Greenify not either... Furthermore, I set up flight mode with WiFi only if screen on.

Any help would be appreciated.

Gesendet von meinem SM-T805 mit Tapatalk
[Galaxy Tab S Android Development] gellmar:
Wow, sounds like a short circuit somewhere, or process like audioserver consuming 100% cpu in background.

1. Make sure you are on the latest 0623 nightly with ROOT access enabled to APPS.

2. Install Termux app (www.termux.sh) and there "pkg install htop"

3. Charge your tablet, turn airplane mode

4. Start Termux, type "su" and as root, type:

export TERM=xterm
htop

Notice the processes consuming most CPU.
[Galaxy Tab S Android Development] coffee81:
Thanks for your file !

But I got an error in your second command, can you help me ?

C:\tools>adb devices

List of devices attached

* daemon not running; starting now at tcp:5037

* daemon started successfully

**001**73*ca**** recovery (* are masked by me)

C:\tools>adb push boot.img /

boot.img: 1 file pushed. 3.8 MB/s (6447121 bytes in 1.625s)

C:\tools>adb shell 'dd if=boot.img of=/dev/block/platform/dw_mmc.0/by-name/BOOT'

/sbin/sh: dd if=boot.img of=/dev/block/platform/dw_mmc.0/by-name/BOOT: not found
[Galaxy Tab S Android Development] gellmar:
Make sure you have latest available TWRP recovery: https://twrp.me/samsung/samsunggalaxytabs105lte.html

Or try replacing both ' with "
[Galaxy Tab S Android Development] Maheshwara:
[MENTION=5214636]gellmar[/MENTION]

Seems to be everything allright [emoji848]... Anyway, although only small issues, I set TisBell and Firefox process not to consume any data in background.

Gesendet von meinem SM-T805 mit Tapatalk
[Galaxy Tab S Android Development] gellmar:
Than possibly a short circuit, but have a look at htop periodically
[Galaxy Tab S Android Development] coffee81:
GG !! it works !!

thanks soooooooooooo much :good::good::good::good::good::good:

FYI, I have been using the latest TWRP. It works after replacing ' to "

here is the log:-

C:\tools>adb devices

List of devices attached

************ recovery (* are post-masked by me)

C:\tools>adb push boot.img /

boot.img: 1 file pushed. 3.6 MB/s (6447121 bytes in 1.688s)

C:\tools>adb shell "dd if=boot.img of=/dev/block/platform/dw_mmc.0/by-name/BOOT"

12592+1 records in

12592+1 records out

6447121 bytes (6.1MB) copied, 0.590268 seconds, 10.4MB/s

My automated app works like a charm now ! No more error !!

SWEET !!

Thanks gellmar so much again !!
[Galaxy Tab S Android Development] Maheshwara:
That means, I need to have a look for a new Tab... [emoji21]

Gesendet von meinem SM-T805 mit Tapatalk
[Galaxy Tab S Android Development] gellmar:
First, flash the latest stock MM and if the batery life is so wrong too, send it to service so they can do initial diagnostics.
[Galaxy Tab S Android Development] Maheshwara:
[MENTION=5214636]gellmar[/MENTION]

I think you are right. It seems to be a hardware defect. Just discovered that sim card reader died ?. Just inserted a sim, not detected, rebooted and still not detected. Cleared cache and still no joy. As I often need mobile data, I will need to buy new tab anyway.
[Galaxy Tab S Android Development] omnikam:
Nice Rom thank you

My only issue so far is call quality, it's very crackly both at my end and the other person's
[Galaxy Tab S Android Development] omnikam:
Anyone else having low volume issue? Or crackly phone call audio with frequent audio Just goes silent and your not able to hear or be heard
[Galaxy Tab S Android Development] peterpan07:
Anyone noticed since when off charging doesn't work? Only noticed since last weekend ROM usual my tab is always on

Edit: looks it's caused by an faulty cable that was working for long at that one. After changed charges well once of, other cable only work as long tab switched on (wonder)
[Galaxy Tab S Android Development] xantiema:
Zips

Edit: Question regarding Kernel and Device Tree zip importance
[Galaxy Tab S Android Development] Maheshwara:
After having changed battery and detected dead SIM card reader, I made a full reset with the result of lost IMEI (baseband and IMEI unknown). Anyway, I decided to also change SIM tray. To get back my IMEI afterwards, I had to go back to stock. After having flashed stock, IMEI was back, new SIM tray worked and suddenly, battery life was like hell with real low idle consumption. Dunno why... Will sort out if immense battery consumption is LOS related.
[Galaxy Tab S Android Development] xantiema:
Are you guys using the linked kernel zip (2017) or the one pre-compiled in the jenkins ROM (2018) ??

Edit: Woah, this sub forum is quite dead :silly:
[Galaxy Tab S Android Development] gellmar:
I am now in progress of making **lte devices LineageOS official (just like ***wifi ones). So, at the moment the latest unofficial build is here: https://download.exynos5420.com and the official kernel will be pushed to LineageOS repo this week.

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

Once you replaced the battery and made a clean wipe, your calibration stats have been reset to 100% and your battery is also 100% capacity, hence the hellish battery life. I did not replace the battery on my tab, but SOT is still good (but please note I use only ~40 apps from F-Droid, which use no idle battery, and 5-6 apps which do use some background traffic).
[Galaxy Tab S Android Development] xantiema:
Just to be clear (newbie here), Once that is done, I am to flash the official ROM then the new Official Kernel, then the Device Tree?

So far it is running on the Jensens LineageOS 14.1 ROM ( which supposedly has a 2018 kernel, but is this the right one that is intended to use?) and the kernel linked under the downloads section is from 2017... this is offsetting. Am I to understand the 2017 variant is tailored to the t805, whereas the new one included in the ROM is not?

Thanks for working on these old bad boy tablets, cheers!

Edit: Currently only running on ROM. Have not flashed Kernel or Device Tree yet - are those intended or not (seems old compared to the ROM)?
[Galaxy Tab S Android Development] Maheshwara:
After having replaced the battery and made full wipe, everything remained the same. Hellish battery life came after SIM tray replacement. Probably, the damaged part caused short circuits at the board...?

Official state for LOS for LTE version - great! Does this mean, we can still hope for LOS 15 as a daily driver?