[ROM][OFFICIAL][T813][8.1] LineageOS 15.1

LuK1337

Recognized Developer
Jan 18, 2013
8,103
16,369
253

schickel

Senior Member
Mar 30, 2009
995
439
93
Munich
Sorry, if I'm boring.....

Battery life is a horror, look at Screenshot. 4 hours without wifi, all apps closed, only 7 minutes screen on time and after 4 hours 25% loss of battery? It's a tablet, with 5800 mAh battery and with normal usage I can't get over a day without charging, and this very slow.

I don't now how to help to get a solution for this. My old nexus 9 get with lineage without using the tablet over a weak and battery live was with round about 5 to 6 hours with sot...

Why this ROM eats so much battery? Can't find anything with better battery stats. Everything else is great with this ROM. But the essential thing.... Don't like stock Samsung TouchWiz, but I need battery life, an it seams I must revert to the old nougat ROM
 

Attachments

  • Like
Reactions: moloko01

moloko01

Senior Member
Nov 21, 2013
152
18
0
Sorry, if I'm boring.....

Battery life is a horror, look at Screenshot. 4 hours without wifi, all apps closed, only 7 minutes screen on time and after 4 hours 25% loss of battery? It's a tablet, with 5800 mAh battery and with normal usage I can't get over a day without charging, and this very slow.

I don't now how to help to get a solution for this. My old nexus 9 get with lineage without using the tablet over a weak and battery live was with round about 5 to 6 hours with sot...

Why this ROM eats so much battery? Can't find anything with better battery stats. Everything else is great with this ROM. But the essential thing.... Don't like stock Samsung TouchWiz, but I need battery life, an it seams I must revert to the old nougat ROM
Yes, and for me with last update it tooks a very long time to charge. Something about 10% in 6 hours. And if screen on it discharges when it is plugged in. Anyone else got this problem, too?
Could a dirty downgrade to an earlier version fix that problem?
 
Last edited:

LuK1337

Recognized Developer
Jan 18, 2013
8,103
16,369
253
YouTube video playback is lagging on the latest build (worked back in Feb). MX player says hw+ not supported.

EDIT: it also lags in chrome.
Try to flash latest stock ROM firmware and see if it works again.
( heimdall flash --APNHLOS NON-HLOS.bin --ABOOT aboot.mbn --MODEM modem.bin --RPM rpm.mbn --SBL1 sbl1.mbn --TZ tz.mbn )
 
Last edited:

Mygod Studio

Senior Member
Apr 30, 2013
341
126
73
Suzhou
mygod.be
Try to flash latest stock ROM firmware and see if it works again.
( heimdall flash --APNHLOS NON-HLOS.bin --ABOOT aboot.mbn --MODEM modem.bin --RPM rpm.mbn --SBL1 sbl1.mbn --TZ tz.mbn )
XAR-T813XXU2BRB2-20180313152922 is the latest one I can find for my model and it's still not working. Or should I use the one for other countries? (if so could you drop me a link, thanks :) )
 

LuK1337

Recognized Developer
Jan 18, 2013
8,103
16,369
253
XAR-T813XXU2BRB2-20180313152922 is the latest one I can find for my model and it's still not working. Or should I use the one for other countries? (if so could you drop me a link, thanks :) )
I believe that I use T813XXS2BRC2. It seems to work just fine, no issues with video decoding here.
 
  • Like
Reactions: Reynald0

Mygod Studio

Senior Member
Apr 30, 2013
341
126
73
Suzhou
mygod.be
I have no problems with T813XXU2BRD1.tar, but you would need to add it to board-info.txt ;)
Hmm I tried this firmware and the issue is still there. Here's some logcat...

(YouTube)
W AudioTrack: dead IAudioTrack, PCM, creating a new one from getPosition()
D AudioTrack: Client defaulted notificationFrames to 4714 for frameCount 14144
(loops forever)

(Chrome lags not as bad)
D AudioTrack: Client defaulted notificationFrames to 1178 for frameCount 3536
W AudioTrack: dead IAudioTrack, PCM, creating a new one from obtainBuffer()
W AudioSystem: ioConfigChanged() closing unknown input 51606
D AudioTrack: Client defaulted notificationFrames to 1178 for frameCount 3536
W AudioTrack: dead IAudioTrack, PCM, creating a new one from processAudioBuffer()
W AudioSystem: ioConfigChanged() closing unknown input 51630
(loops forever)

(MX Player)
W MX.Player.Joint: HW decoder is rejected automatically due to danger.

EDIT: It seems to work fine if I wipe data.

EDIT: It seems like the issue is that media server keeps crashing. Anyway I reverted the update since I don't feel like wiping all my data.
 
Last edited:

schickel

Senior Member
Mar 30, 2009
995
439
93
Munich
@LuK1337 Now I post in the correct thread.

I've make again a clean clean clean clean flash, after formatting more than one time all partitions. Flashed latest LOS, Magisk and Mini-Gapps. After this I've installed BetterBatteryStats and WLD, shutdown the tablet charched it up to 100%, started it.

After looking England vs Tunesia my Tablet have 80%. I've make screenshots before I put the Tablet on the desk, no Apps are open, fingerprint not enabled, Display off and only WiFi active. On 21:50 I have 80%, in the morning 7:04 34% (11 hours after full charge and only 37 minutes SOT remaining 34%). What the hell drains the battery?

See the screenshots. On the left side the evening and on the right in the morning. WLD and BBS saying, it was in deep sleep. But my understanding and experience of deep sleep is really deep sleep - minimal battery drain up to maximum 5% over night, or I'm wrong? My Nexus 9 also with LOS is now 10 days after full charge on with WiFi endabled and have 3 hours SOT and remaining 23% - THIS is REAL deep sleep.

So, what can we do? I'm ready to support you, to make tests and helping to solve this "deep sleep". Because I can't use this tablet as a daily driver, it could be used for testing to find out the real issue(s).

Greetings from Munich ;)

EDIT:

"Wifi On" and "Wifi Running" have the same time? Is this correct?

And "No or Unknown Signal" also full time after charging completed. Also correct?
 

Attachments

Last edited:

LuK1337

Recognized Developer
Jan 18, 2013
8,103
16,369
253
@LuK1337 Now I post in the correct thread.

I've make again a clean clean clean clean flash, after formatting more than one time all partitions. Flashed latest LOS, Magisk and Mini-Gapps. After this I've installed BetterBatteryStats and WLD, shutdown the tablet charched it up to 100%, started it.

After looking England vs Tunesia my Tablet have 80%. I've make screenshots before I put the Tablet on the desk, no Apps are open, fingerprint not enabled, Display off and only WiFi active. On 21:50 I have 80%, in the morning 7:04 34% (11 hours after full charge and only 37 minutes SOT remaining 34%). What the hell drains the battery?

See the screenshots. On the left side the evening and on the right in the morning. WLD and BBS saying, it was in deep sleep. But my understanding and experience of deep sleep is really deep sleep - minimal battery drain up to maximum 5% over night, or I'm wrong? My Nexus 9 also with LOS is now 10 days after full charge on with WiFi endabled and have 3 hours SOT and remaining 23% - THIS is REAL deep sleep.

So, what can we do? I'm ready to support you, to make tests and helping to solve this "deep sleep". Because I can't use this tablet as a daily driver, it could be used for testing to find out the real issue(s).

Greetings from Munich ;)

EDIT:

"Wifi On" and "Wifi Running" have the same time? Is this correct?

And "No or Unknown Signal" also full time after charging completed. Also correct?
>"Wifi On" and "Wifi Running" have the same time? Is this correct?
I guess so.

>And "No or Unknown Signal" also full time after charging completed. Also correct?
Yes, they don't hide that on wifi-only devices.

Maybe you should check kernel wake locks although you seem to be having normal deep sleep so I doubt you'd see anything interesting there.
 

Malstrond

Senior Member
Dec 1, 2010
53
10
0
Power consumption and dual band

I had two of the problems mentioned ITT: High power consumption when the screen is off (3-4%/hour) and an unstable WiFi connection (reconnects even while using the network, at full signal strength).
I have an AP (Ubiquiti UniFi AP AC LITE) and its 2.4GHz and 5GHz radios were set to the same SSID.
I changed it to have a different SSID for each band and connected the tablet to the 5GHz one. This solved the unstability and really improved the power consumption.
It's still a bit higher than stock, but not by much and I'm not really seeing excessive wakelocks.
Maybe the firmware spent its time hopping between the bands when it should be in deep sleep?
The stock firmware doesn't have this problem when using the same SSID for both bands . The stock firmware even follows band steering while it seems to fight it on Lineage.
 
  • Like
Reactions: OhioYJ

OhioYJ

Senior Member
Feb 25, 2011
1,369
658
133
I had two of the problems mentioned ITT: High power consumption when the screen is off (3-4%/hour) and an unstable WiFi connection (reconnects even while using the network, at full signal strength).
I have an AP (Ubiquiti UniFi AP AC LITE) and its 2.4GHz and 5GHz radios were set to the same SSID.
I changed it to have a different SSID for each band and connected the tablet to the 5GHz one. This solved the unstability and really improved the power consumption.
It's still a bit higher than stock, but not by much and I'm not really seeing excessive wakelocks.
Maybe the firmware spent its time hopping between the bands when it should be in deep sleep?
The stock firmware doesn't have this problem when using the same SSID for both bands . The stock firmware even follows band steering while it seems to fight it on Lineage.
Very interesting find. I've just been telling my wife and son to leave the wifi off on their tablets when they set them down for any length of time. I'll have to try changing the SSID on the router and see if I get the same results on our tablets.
 

moloko01

Senior Member
Nov 21, 2013
152
18
0
I use the screensaver for nightclock. Since an Update from, I think May, it discharges the battery while it is plugged in. It is impossible to charge if Screensaver is enabled.
 

Deltadroid

Recognized Contributor
Apr 19, 2013
3,767
9,884
263
I had two of the problems mentioned ITT: High power consumption when the screen is off (3-4%/hour) and an unstable WiFi connection (reconnects even while using the network, at full signal strength).
I have an AP (Ubiquiti UniFi AP AC LITE) and its 2.4GHz and 5GHz radios were set to the same SSID.
I changed it to have a different SSID for each band and connected the tablet to the 5GHz one. This solved the unstability and really improved the power consumption.
It's still a bit higher than stock, but not by much and I'm not really seeing excessive wakelocks.
Maybe the firmware spent its time hopping between the bands when it should be in deep sleep?
The stock firmware doesn't have this problem when using the same SSID for both bands . The stock firmware even follows band steering while it seems to fight it on Lineage.
In regards to unstable Wifi, you could try disabling fast roaming. This might be an issue with certain AP's that are not patched for Krack vulnerability.

Code:
--- a/WCNSS_qcom_cfg.ini
+++ b/WCNSS_qcom_cfg.ini
@@ -66,6 +66,9 @@ InfraUapsdBkSrvIntv=0
 # Flag to allow STA send AddTspec even when ACM is Off
 gAddTSWhenACMIsOff=1
 
+# Disable RSSI FW filtering
+gEnableFWRssiMonitoring=0
+
 # Make 1x1 the default antenna configuration
 
 gNumRxAnt=1
@@ -171,11 +174,12 @@ gEnableDFSMasterCap=1
 
 # ESE Support and fast transition
 EseEnabled=1
+FastTransitionEnabled=0
 ImplicitQosIsEnabled=0
 gNeighborScanTimerPeriod=200
 
-gNeighborLookupThreshold=76
-gNeighborReassocThreshold=81
+gNeighborLookupThreshold=82
+gNeighborReassocThreshold=88
 
 gNeighborScanChannelMinTime=20
 gNeighborScanChannelMaxTime=30
@@ -184,12 +188,12 @@ gMaxNeighborReqTries=3
 # Legacy (non-ESE, non-802.11r) Fast Roaming Support
 # To enable, set FastRoamEnabled=1
 # To disable, set FastRoamEnabled=0
-FastRoamEnabled=1
+FastRoamEnabled=0
 
 #Check if the AP to which we are roaming is better than current AP in terms of RSSI.
 #Checking is disabled if set to Zero.Otherwise it will use this value as to how better 
 #the RSSI of the new/roamable AP should be for roaming
-RoamRssiDiff=3
+RoamRssiDiff=0
 
 # If the RSSI of any available candidate is better than currently associated
 # AP by at least gImmediateRoamRssiDiff, then being to roam immediately (without
 

schickel

Senior Member
Mar 30, 2009
995
439
93
Munich
Some additional researches regarding battery drain

@Deltadroid
@LuK1337

I've found out the reason for my extreme battery drain:

Turned off the Tablet and in the mornig battery was completly drained - There MUST be something wrong with the hardware. So I make a RMA and get a brand new Tab S2.

Draining is here not so extreme. But I've make some testing and want to share my findings (I've istalled lineage-15.1-20180702-nightly-gts210vewifi-signed.zip) :)

I charged the tablet to 100% and rebootet it have 1h and 4m display on time. After that I don't not use the Tab. With activated WiFi the draining is up to 50% faster as with disabled WiFi - you can see this at THIS screenshot.

One thing is confusing me:
In the screenshot you can see, that there is 1d 21h 39m idle time.
In THIS screenshot from BBS I have only 2h 11m deep sleep and 1d 18h 16m awake time - this could not be only enabled WiFi.

So I've cheked all other settings in BBS.
Kernel Wakelocks seems to be fine
Partial Wakelocks also fine

Alarms are interesting:
com.google.android.gms have a lot of wakeups. The question is: Are so many wakeups normal?

The other google(problem?):
Sensors / Google Play Services i 1d 4h active. Also here the question: Is it normal?

I've created also some BBS dumps, if this could help for further investigations.

As I said before, draining with active WiFi is defenitly an issue. But also with deactivated WiFi something went wrong with google play services, the reason for that I can't find, if the play services are a reason for draining with deactivated WiFi.

Maybe someone wih more insight can take a look on this and give some hints. I'm also here for testing and debugging.
 
  • Like
Reactions: kdrkdr

BillTheCat

Senior Member
Jun 17, 2008
1,851
669
0
Milford, PA
Can You Help?

I'm a little late to the game here, but I want to flash LOS 15.1 on an 813VE. I've downloaded the ROM, and I have tried to flash with TWRP 3.2.1-0, with this error...

Updater process ended with ERROR: 7
This device has bootloader T813XX22APJ1

Hope someone can get me pointed in the right direction.

Thanks!
 

grandma_p

Member
Dec 21, 2016
13
5
0
@Deltadroid
@LuK1337

I've found out the reason for my extreme battery drain:

Turned off the Tablet and in the mornig battery was completly drained - There MUST be something wrong with the hardware. So I make a RMA and get a brand new Tab S2.

Draining is here not so extreme. But I've make some testing and want to share my findings (I've istalled lineage-15.1-20180702-nightly-gts210vewifi-signed.zip) :)

I charged the tablet to 100% and rebootet it have 1h and 4m display on time. After that I don't not use the Tab. With activated WiFi the draining is up to 50% faster as with disabled WiFi - you can see this at THIS screenshot.

One thing is confusing me:
In the screenshot you can see, that there is 1d 21h 39m idle time.
In THIS screenshot from BBS I have only 2h 11m deep sleep and 1d 18h 16m awake time - this could not be only enabled WiFi.

So I've cheked all other settings in BBS.
Kernel Wakelocks seems to be fine
Partial Wakelocks also fine

Alarms are interesting:
com.google.android.gms have a lot of wakeups. The question is: Are so many wakeups normal?

The other google(problem?):
Sensors / Google Play Services i 1d 4h active. Also here the question: Is it normal?

I've created also some BBS dumps, if this could help for further investigations.

As I said before, draining with active WiFi is defenitly an issue. But also with deactivated WiFi something went wrong with google play services, the reason for that I can't find, if the play services are a reason for draining with deactivated WiFi.

Maybe someone wih more insight can take a look on this and give some hints. I'm also here for testing and debugging.
I'm still running lineage-15.1-20180528-nightly-gts210vewifi and battery drain during sleep is OK for me (see screenshot).

Where there significant changes to the ROM between these versions or is it device/installed apps related?
 

Attachments