yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Android Development] j1gga84:
Okay,

most of the problems I solved by searching on my own :good:

Navigation buttons still flash very shortly when screen is off about every 15 seconds in newest build :(

Another "small" issue (Viper4Android runs with some workarounds):

I wanted to set SELinux to moderate but when I set it from strict to moderate in settings and chose "set on system startup" it is back to strict after a reboot..

has this something to do with deathly kernel because kernel is not in moderate (permissive) SELinux mode?

And I asked concerning the "arm" folders that are normally present only on a odexed system:

http://xdaforums.com/showpost.php?p=64550297&postcount=427

But I guess AICP is deodexed!?

the message that system has a problem and that I should contact the manufacturer is still present, I guess this will remain forever :p

besides of that the ROM is running excellent :good:

Please keep up the good work.

regards
[Galaxy Tab S Android Development] thermskin:
Yes that message on every reboot is annoying but don't have time to investigate more. I remember that on different build server that message does not show so just ignore it [emoji2]

As for flashing buttons I just clean installed today's build and don't see flashes.

I had a strange problem with tablet. Left for couple of days without using it and battery was empty and after that I couldn't start tablet it just stayed on Samsung logo. So had to pull out nandbackup. Then decided to clean install who gives a fu*k?.

So let's see how this build behave.

T.
[Galaxy Tab S Android Development] j1gga84:
Okay, I will ignore that message ;)

Hmm, I also installed previous build clean but I had these flashes also in older build :confused:

In key settings I disabled backlight illumination.. And in kernel adiutor you cannot set illumination seperately :confused:

So I ask myself where this can come from..

It is like BLN when you receive a message (flashing every 10-15 seconds) but I have no message and BLN is not supported..

okay, that is strange but I also had the same issue on a stock ROM I guess :confused:

btw. where do you get the code for this ROM from? because T-805 is not officially supported by CM and AICP I guess, or?

regards
[Galaxy Tab S Android Development] thermskin:
I have disabled hardware keys and enabled navigation bar and no flashing.

Source is part from cm and aicp all is on github and device tree is on my github.com account.

You can try clean install today build.

T.
[Galaxy Tab S Android Development] thermskin:
I have a major wakelock on latest build. Tablet is constantly on highest CPU and battery drain is unbelievable :)

Don't know if it is because of different kernel. Will try to fix it.

T.
[Galaxy Tab S Android Development] j1gga84:
Hmm, I checked BBS and found 2 alarm wakelocks that kept my device awake, maybe it is the same problem, I will attach screenshot when I am at home.

In the previous build I think I did not have this wakelock.

Besides of that and the blinking keys everything is fine :)

Maybe the blinking comes from an app, I don't want to re-flash the ROM just because of this little issue :D

Could you reproduce the issue and it was gone after a clean flash or did you never have this blinking keys?

Regards

Sent from my SM-G900F using german Tapatalk 4
[Galaxy Tab S Android Development] meduza:
...so this is for T805 only ?

m.
[Galaxy Tab S Android Development] thermskin:
Yes,

only for T805.

T.
[Galaxy Tab S Android Development] meduza:
:(

;) m.
[Galaxy Tab S Android Development] j1gga84:
[MENTION=3788878]thermskin[/MENTION]

do you have the same wakelocks like mine in attachment?

regards
[Galaxy Tab S Android Development] SmooK_LV:
Yeah, I also appear to have wakelocks on some apps, but a battery manager app is taking care of it for me for now.

I have a bigger issue - as I don't have a phone, I use my tablet for calling and issue is that you can make only one successful call before you better make a restart of the device. If you don't restart, the next time you call the microphone or speaker might not work or the device just randomly reboots itself. This is really annoying issue that interferes with my daily life.

P.S.-If anyone is willing to gift me their old phone or something, I would be very happy as tablet is not the most comfortable thing to call from.
[Galaxy Tab S Android Development] thermskin:
No I had much worse battery life so switched to my version of kernel in new build and now tab sleeps like a baby ?

Will upload tomorrow new build.

T.
[Galaxy Tab S Android Development] thermskin:
Build12/1

This is a new one with stock (CM) kernel.

Build 12/1 md5: 5f68b2874cd511cfb86645580fce05a0

Recommended is clean flash if you notice any hiccups after dirty flash :)

T.
[Galaxy Tab S Android Development] j1gga84:
Many thanks for the update [MENTION=3788878]thermskin[/MENTION]

besides the kernel change, any other changes?

I guess with stock CM kernel I cannot user kernel audiutor anymore? :confused:

Why did you remove deathly kernel? Just because of the wakelocks? Are you sure they were kernel related?

maybe you could upload flashable stock CM kernel and deathly kernel, if anybody wants to change the kernel back to deathly?

I really hope that we will get a custom kernel for our Tab S, that would be awesome for further tweaking..

regards
[Galaxy Tab S Android Development] thermskin:
Well you can use kernel adiutor. On AICP side development for LP stopped long ago so only small changes from CM are included in ROM.

For me even double tap to wake wasn't working and bloody wakelock so switched to cm kernel with my cherry picks. Also tablet was charging very slow and now it is normal.

T.

Sent from my LG-H815
[Galaxy Tab S Android Development] NeWONEx:
Did you think i can use your kernel in CM 12.1 ?
[Galaxy Tab S Android Development] thermskin:
Sure why not, sources are on my github.com/ssehovic so go ahead ?

T.

Sent from my LG-H815
[Galaxy Tab S Android Development] SmooK_LV:
Hey, thanks for the new build. Wakelocks are gone and throughout this day calls didn't bug out at all - I believe my main issues are fixed. I hope I'm not wrong.

Thanks again!
[Galaxy Tab S Android Development] thermskin:
Glad to hear that. So you are using tab for phone calls? I don't have sim for it so can't test it out.

T.

Sent from my LG-H815
[Galaxy Tab S Android Development] SmooK_LV:
Yeah, I'm using it for calls as my my phone broke. Something's up with the mic, but it might not be the ROMs fault.. Will see how everything works on days ahead.

Thanks for the work. I'm so satisfied, that I don't know what to do with it anymore - I put my favourite theme as a final touch, turned down animation time and there's nothing left to do.
[Galaxy Tab S Android Development] SmooK_LV:
I believe I had a headset at home - when I get there, I'll try it out.

But I had reboots and crippled audio on previous build - I don't have that on this build (Although I'm not sure about crippled audio yet).

EDIT: I don't have the headset anymore. Sorry. Either risk it or wait, your call.
[Galaxy Tab S Android Development] thermskin:
New build 15/1

Here it is.

Build 15/1 md5: d7bcbf8569099f7753ba4b97d81f04c1

T.
[Galaxy Tab S Android Development] j1gga84:
Many thanks for the update, I think I will flash it clean on the weekend and hope that softkey flashing will dissappear ;)

Another good news, also for us I think if it will become true?

http://xdaforums.com/showthread.php?p=64820820

Regards

Sent from my SM-G900F using german Tapatalk 4
[Galaxy Tab S Android Development] ymlik:
hi [MENTION=3788878]thermskin[/MENTION],

Could you build a version for T800 please?

Regards.
[Galaxy Tab S Android Development] thermskin:
Sorry, don't have time to build for third device.

T.

Sent from my LG-H815
[Galaxy Tab S Android Development] ymlik:
ok , I understand , I had AICP on my galaxy SIII and I love this rom.

Regards.
[Galaxy Tab S Android Development] NeWONEx:
All changes in unofficial CM 12.1 are included in this rom ! I mean driver and etc.. Right ?
[Galaxy Tab S Android Development] thermskin:
Yes all from cm.

T.

Sent from my LG-H815
[Galaxy Tab S Android Development] j1gga84:
I did a full wipe and installed the newest build clean, installed latest open gapps (pico) and rebooted.

I did not install any apps and the softkey illumination is still activated, guess what, the softkeys still blink very shortly after about 15 seconds when screen is off, no matter if softkey illumination is activated or deactivated??

I don't understand why only I seem to have that issue..

Regards

Sent from my SM-G900F using german Tapatalk 4
[Galaxy Tab S Android Development] thermskin:
Not only you ;)

I have it also and cherry-picked fix for that but apparently bug is still here.

I must have missed something.

T.
[Galaxy Tab S Android Development] j1gga84:
awesome, thanks in advance :) :good:

In latest build with deathly kernel it was not possible to change SElinux status out of system settings (it was resetted after reboot), does this work now? I guess it was because deathly kernel resetted it.

Would you suggest to wait with flashing until the new update or can we dirty flash it over current build?

regards
[Galaxy Tab S Android Development] Levistras:
I noticed last night that my softkeys were flashing every 10 seconds or so when plugged in to charge.

I didn't unplug it to see if it kept happening. I'm about to dirty flash up to the 1/15 build and will report back if I still see it.

My biggest issue right now is that this thing doesn't seem to charge (or charges VERY slowly) when powered on and plugged in. I left it charging over night (device on) and it went from 40%->55%. I turned it off and charged it for another 3 hours and the battery was full. Weird that it only gained 15% overnight.

EDIT:: After updating to 1/15 build, I no longer see the flashing softkeys. Next test is to drain the battery enough so I can see how it reacts to charging now.

EDIT2:: Forgot to drain the battery, left it plugged in with screen mostly off during my work day.. finished the day with 15% less battery than I started. That charger was more than enough to charge it up through my light to moderate usage before, and now it seems to go the other way. Will keep an eye on things I might have draining battery but my setup hasn't changed too much recently. Good news is the battery usage while tablet is unplugged while idle seems to be fairly flat. Left it for a few hours after work and picked it up and it had only dropped 1% since last check.
[Galaxy Tab S Android Development] Levistras:
Seems I can confirm after a couple days of testing that the Tab S running this rom can not keep itself charged while plugged into the stock Samsung 2A charger. Even with the screen off, it only holds current charge. Whenever the screen is on it slowly discharges and battery level goes down.

Have tried a couple different charges and cables, results always seem to be the same. Tablet needs to be powered down in order for charge level to rise.
[Galaxy Tab S Android Development] NeWONEx:
I don't think this issue because of kernel. I'm already use it with CM 12.1 and it is work very well and charging without any issue !
[Galaxy Tab S Android Development] Levistras:
Can you confirm if you start under 80%, plug it in to charger and watch some youtube or netflix on the tablet... the tablet will charge up and gain %age while you are using the tablet and the screen is on?

Mine seems incapable of doing this. :(

Today I'm running a few battery and wakelock monitoring apps, hoping to find an issue with my installed apps (so I can stop blaming the rom) however nothing has showed up suspicious thus far.
[Galaxy Tab S Android Development] NeWONEx:
I will test it now my battery is 40% ....
[Galaxy Tab S Android Development] Levistras:
Actually... You can forget about the youtube/netflix part. Just confirm, if you can, that the battery %age is capable of going upwards while the tablet is on. Even in a sleeping state where I haven't turned the screen on for an hour, with airplane mode enabled, I can't get the tablet battery percentage to increase while connected to a charger.
[Galaxy Tab S Android Development] NeWONEx:
Now it's became 50% . it charged 10%. I used only Wi-Fi and don't have sim with Youtube and browsing.
[Galaxy Tab S Android Development] Levistras:
That's really weird. Using a 2A Samsung charger?

I disabled everything I could.. uninstalled any app I didn't need. Turned off wifi, went into airplane mode. Left the screen off... plugged it in at 95% and left it for an hour.

After 60 minutes it made it to 96%! BetterBatteryStats claims that I am gaining 1.2% battery every hour at this rate.

So it seems I can get it to charge while powered on... but just barely, and extremely slowly. I'm curious how you were able to get 10% charge within that hour... something's not right here.
[Galaxy Tab S Android Development] NeWONEx:
Yeah! I used samsung A2 charger ! Check your bootloader and try to do clean flash and charge it without install any apps only Gapps, may it help you!
[Galaxy Tab S Android Development] Levistras:
Alright, screw it, I'll just wipe everything and do a clean install of the 1/15 build and see how that goes. (currently I've been using a clean 1/12 build with a dirty 1/15 flash overtop)

EDIT: Home now, did the full wipe and clean install of 1/15. Tablet is at 91% charge, sitting on my 54W 5 port charger ( http://www.amazon.ca/gp/product/B00LSKPN94?psc=1&redirect=true&ref_=oh_aui_detailpage_o04_s00 ), and is doing the initial setup/restore/download of apps. Lets hope this works :)

EDIT2: Over 2 hours later, tablet left on charger, I am now at 87% :( Stock rom didn't have this issue, and it charges just fine when it is powered off. Not sure where to go from here.
[Galaxy Tab S Android Development] bibihub:
Hi [MENTION=3788878]thermskin[/MENTION] ! I am on t800 and I didn't update since the 12/17 build. Your build always has been compatible with the t800 but if I understand well, it is not the case anymore because of the change of kernel, right ? I could try but I don't want to mess my device because of an incompatible kernel (not sure if it would brick it).
[Galaxy Tab S Android Development] thermskin:
New build 21/1

Hello there :)

Build 21/1 md5: 41c392db7c6a5b243b1cf300f5e013d1

T.
[Galaxy Tab S Android Development] thermskin:
Not new kernel just switched back to CM one.

If you have flashed previous AICP builds I don't see reason to brick your T800.

T.
[Galaxy Tab S Android Development] NeWONEx:
Can you give us what is new !

And thanks for your work ! [emoji1]
[Galaxy Tab S Android Development] thermskin:
Yust follow CM gerrit :)

T.
[Galaxy Tab S Android Development] j1gga84:
[MENTION=3788878]thermskin[/MENTION]

Many thanks for the update :)

did you get the patch for the blinking softkeys working or is it not yet included in latest update?

regards
[Galaxy Tab S Android Development] NeWONEx:
Is it normal to have "Android System" in recent list?

And when I click on it become

Any suggestion !
[Galaxy Tab S Android Development] Levistras:
Is this using the most recent Jan 21st build? I don't see Android System on my device in the apps list thus far.

(Still trying to get to bottom of my charging issue. Have engaged Samsung to get replacement charger and cable to isolate those. In mean time trying to meet up with a friend who also has a Tab S to borrow his charger/cable to see if that makes a difference.)
[Galaxy Tab S Android Development] thermskin:
I had a similar problem when I built it with different kernel then switched to stock cm with cherry picks and now all is fine.

Check your data and cache partition type if it's ext4 if you are on f2fs try to change it to ext4.

T.

Sent from my LG-H815
[Galaxy Tab S Android Development] NeWONEx:
I don't know really ! But I'll try to do Clean flash without restore backup by Titanium
[Galaxy Tab S Android Development] thermskin:
Unfortunately BT is broken I can't pair my Samsung BT keyboard with tab.

Edit: I had odex file with .gz extension in /system/app/Bluetooth/arm. Renamed it and BT connects to my keyboard.

T.
[Galaxy Tab S Android Development] Joker87:
Still no luck with Bluetooth audio when connected to wifi, still no problem with it when connected via sim card, just like previous builds...
[Galaxy Tab S Android Development] Tyrion74:
i can not telephone
[Galaxy Tab S Android Development] Levistras:
Pairing my Dell BT Travel Mouse and Apple Wireless Keyboard over BT seems to have no issues with latest build.
[Galaxy Tab S Android Development] thermskin:
New build 26/1

Here it is.

Build 26/1 md5: 7473db34a8b26446f4360be02a5382bc

I recommend OpenGapps. I had problems with TKGapps so switched to OpenGapps.

T.
[Galaxy Tab S Android Development] j1gga84:
Thanks for the update :)

Softkeys still blink when screen is off :(

Will there be any fix soon?

And concerning security patch level, it is still from december 2015, is it possible to bring it to january 2016?

Regards

Sent from my SM-G900F using german Tapatalk 4
[Galaxy Tab S Android Development] Levistras:
Mine stopped doing that a couple builds ago. Have you tried a clean install?
[Galaxy Tab S Android Development] j1gga84:
Yes, I did a clean install but [MENTION=3788878]thermskin[/MENTION] mentioned some posts ago, that he also faced this issue which obviously affects not everybody!?

EDIT:

I found an issue: when changing the volume with VOL UP/VOL DOWN buttons you cannot put the device from loud to vibration only and mute it, you have to click on vibration and from vibration mode you cannot activate speakaers again, only when pulling down the status bar and set it.

Regards

Sent from my SM-G900F using german Tapatalk 4
[Galaxy Tab S Android Development] thermskin:
New build 01/02

Here we go again.

Build 01/02 md5: 0d8a54c4705cb27aca1fbb33db83a336

T.
[Galaxy Tab S Android Development] j1gga84:
[MENTION=3788878]thermskin[/MENTION]

Many thanks for the update, the volume up and down bug is solved :)

What about the blinking softkeys and what about Android Security Patch level? In this ROM it is 1.December 2015 but I think last one is 1.January 2016 and February 2016 will follow :)

Edit:

Android 5.1.1_r34 is out: https://android.googlesource.com/platform/cts/+/android-5.1.1_r34

Would be nice :)

Regards

Sent from my SM-T805 using german Tapatalk 4
[Galaxy Tab S Android Development] Levistras:
Thanks! I just saw the blinking softkeys thing again. Doesn't seem to happen all the time to me, but on occasion when I glance at it while charging it happens.

By the way, your "Donate to me" button doesn't work: "Your recipient is not able to receive funds at this time. Your recipient must first set up his or her account to receive funds."
[Galaxy Tab S Android Development] Levistras:
I'm trying to use Citrix Receiver on this ROM and am running into some video profile (mime type?) issues. This was working fine back on TW. Is this something that can be fixed? Here's the log error from Citrix Receiver:

2-02 15:28:52.723 W/SSLSDKJW( 7362): [===> Loaded Android ICS+ keystore. Implementation provided by HarmonyJSSE

02-02 15:28:53.386 W/SSLSDKJW( 7362): [===> Current FIPS status is DISABLED

02-02 15:28:53.521 I/HttpClientHelper( 7362): SslSdkProtocolNumber value is 0x2 from user's settings

02-02 15:28:53.521 W/SSLProxy( 7362): [===> Calling connect port=<<redacted>>.com with protocol bitmask 0x2

02-02 15:28:54.136 W/VideoCapabilities( 7362): Unrecognized profile/level 32768/2 for video/mp4v-es

02-02 15:28:54.148 W/VideoCapabilities( 7362): Unrecognized profile/level 32768/2 for video/mp4v-es

02-02 15:28:54.177 W/VideoCapabilities( 7362): Unsupported mime video/mp4v-esdp

02-02 15:28:54.195 I/VideoCapabilities( 7362): Unsupported profile 4 for video/mp4v-es

02-02 15:28:54.212 I/OMXClient( 7362): Using client-side OMX mux.

02-02 15:28:54.282 W/AHierarchicalStateMachine( 7362): Warning message AMessage(what = 'omx ', target = 1) = {

02-02 15:28:54.282 W/AHierarchicalStateMachine( 7362): int32_t type = 0

02-02 15:28:54.282 W/AHierarchicalStateMachine( 7362): int32_t node = 43

02-02 15:28:54.282 W/AHierarchicalStateMachine( 7362): int32_t event = 3

02-02 15:28:54.282 W/AHierarchicalStateMachine( 7362): int32_t data1 = 1

02-02 15:28:54.282 W/AHierarchicalStateMachine( 7362): int32_t data2 = 117440527

02-02 15:28:54.282 W/AHierarchicalStateMachine( 7362): } unhandled in root state.

02-02 15:28:54.315 E/ACodec ( 7362): [OMX.Exynos.AVC.Decoder] ERROR(0x80001001)

02-02 15:28:54.315 E/ACodec ( 7362): signalError(omxError 0x80001001, internalError -2147483648)

02-02 15:28:54.315 E/MediaCodec( 7362): Codec reported err 0x80001001, actionCode 0, while in state 6

02-02 15:28:54.320 D/TUI ( 7362): onDriverShutdown
[Galaxy Tab S Android Development] thermskin:
Donate button should work.

T.
[Galaxy Tab S Android Development] thermskin:
That depends on CM if they push it we will have it:)

Regarding blinking softkeys I have no idea how to solve it. Unfortunately don't have much time to poke around.

T.
[Galaxy Tab S Android Development] Levistras:
It really doesn't :(

Buying you a beer is apparently difficult!

"Your recipient is not able to receive funds at this time. Your recipient must first set up his or her account to receive funds."
[Galaxy Tab S Android Development] thermskin:
Have a nice weekend:)

New build is here.

T.
[Galaxy Tab S Android Development] j1gga84:
Dirty flash ended in a bootloop for me :(

Regards

Sent from my SM-G900F using german Tapatalk 4
[Galaxy Tab S Android Development] Levistras:
Has anybody else tried yet? If this is going to bootloop me too I'll pause first and do a decent backup, I've been using the Tab S quite a lot recently.

( Can you confirm, Did you later try a clean flash, and that worked? )
[Galaxy Tab S Android Development] j1gga84:
I have not yet tried a clean flash because I have not the time for that..

I cannot do a fullwipe with every update :(

If I do so, I will inform you here.

EDIT:

In the build of 01.02. I got soft reboots everytime when opening the Facebook app, what could be the reason for that?

Regards

Sent from my SM-T805 using german Tapatalk 4
[Galaxy Tab S Android Development] thermskin:
Just flashed latest build and no bootloop and Facebook works fine.

Maybe you should flash opengapps?

T.
[Galaxy Tab S Android Development] j1gga84:
I use open gapps already but I flashed the build again dirty and it worked, I just have to wait longer as usual until the system booted up.

Concerning Facebook, I reinstalled the app and now it works fine :)

Regards

Sent from my SM-G900F using german Tapatalk 4
[Galaxy Tab S Android Development] Levistras:
No issues on my end performing a dirty flash.
[Galaxy Tab S Android Development] j1gga84:
Guys,

take a look here: http://xdaforums.com/showpost.php?p=65452789&postcount=435

I am the only one who is smelling official CM support for T805 finally, the last device of the Galaxy Tab S family that still misses official CM? :fingers-crossed:

Please help deadman96385 to get this done hopefully :)

regards
[Galaxy Tab S Android Development] zyklotrop88:
But Why ist this going to be on CM12.1 instead on CM13 immedately? All others have it already. KlimtWIFI, KlimtLTE and ChagallWIFI.
[Galaxy Tab S Android Development] j1gga84:
All others have CM12.1:

https://download.cyanogenmod.org/?device=chagallwifi

https://download.cyanogenmod.org/?device=klimtlte

https://download.cyanogenmod.org/?device=klimtwifi

So it would be logical to bring out CM12.1 for chagallte and after that ALL together to CM13 ;)

And I was talking of official support, not unofficial ;)

Also AICP would benefit of that :)

regards
[Galaxy Tab S Android Development] zyklotrop88:
Thank you. I See, the cm13 are all inofficals.

Gesendet von meinem SM-T805 mit Tapatalk
[Galaxy Tab S Android Development] thermskin:
I am playing with cm-13.0 and so far camera, ril don't work. Don't have data sim so can't test properly. What I see is a good start!

There are some fstab problems with access to external sdcard but not show stopper. Probably bad mount points.

T.