yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Android Development] Paulicat:
I took a look and I saw some things that were odd but nothing concrete yet.

Here's a link to a new build with some small changes in place that may or may not help the hangouts sms.

Mostly should be the same from last build. I'm trying real hard to stop the logcat spam whether it affects performance or not, it bothers me. :D

I've traced it down to a mismatch between sensors.universal5420.so and the em3323 driver in the kernel.

The proprietary binary has changed but the em3323 driver in the kernel hasn't.

The accelerometer was spamming on the first test build I did, but I noticed the sensors file wasn't updated in KLIMTWIFI as it was in KLIMTLTE.

Once I swapped in the new one from KLIMTLTE, the accelerometer stopped spamming but the lightsensor didn't stop.

Will be trying some changes in the em3323 driver because the sensor file is proprietary so no code.

I can see the exact message that's spamming when I hex edit the sensors.universal5420.so file so that's how I know its coming from there.

Anyways, you can try this build if you want to see if the hangouts sms problem is fixed.

https://www.androidfilehost.com/?fid=457095661767120601
[Galaxy Tab S Android Development] greeg32:
I like the way you think?. I'll test it out ASAP. For the nth time, thank you.
[Galaxy Tab S Android Development] Paulicat:
Good luck!

I appreciate the kind words.

I'm just trying to give back to the community that I've used a fair bit from.
[Galaxy Tab S Android Development] greeg32:
Here's a log for the hangouts attempt with the new build. Now a force close.

http://cloud.tapatalk.com/s/584390d0336d3/2016-12-03_21-39-03.txt
[Galaxy Tab S Android Development] Paulicat:
Crazy stuff! :D

Didn't expect that.

I assume this works on the stock roms?

I wish google would have opened up G voice to Canada...

I'm going to focus on the logcat spam for a couple days before I get back to this problem.

Its really tough to try and fix when I can't test it here.
[Galaxy Tab S Android Development] greeg32:
Makes sense. I appreciate the effort. Yes, works on stock and CM 12.1
[Galaxy Tab S Android Development] Paulicat:
Ok I'll look into the cm12.1 sources to compare.

I figured it only worked on stock which would make it a bit tougher to look for ideas.
[Galaxy Tab S Android Development] Paulicat:
Worked with deadman96385 to sort out the logcat spamming.

This new build is running very very good. Hangouts google voice sms problem is likely still there though.

Also, f2fs works now for data and cache partitions, I'm using it right now.

https://www.androidfilehost.com/?fid=529152257862686635
[Galaxy Tab S Android Development] EyeBalos:
Thanks Paulicat for continuing to update CM13 for this device. I installed the latest build prior to the logcat fix and it is solved 2 problems for me: GPS and high battery consumption. Now the GPS is working with various GPS test apps and the battery drain is more reasonable (but not as good as the IronMan V2.5 ROM). I did a clean flash after upgradging TWRP to 3.0.2.1 (Deadman's latest version dated Dec 2, 2016).

If I need to upgrade to your latest build, can I do a dirty flash? I don't want to redo all my theme and customized settings.

Thanks!
[Galaxy Tab S Android Development] shackf16:
I've been using the 2 Dec build for a couple of days now and my only issue has been the Fox Now app occasionally hanging when watching Gotham. I tried to run Geekbench 4 and it would force close at about 94% complete but never finish. I am not a huge proponent of benchmark apps, but I use them to compare different ROMs. I got the highest score on Antutu yet on a custom ROM, so that is a positive. It's been great to see the rapid development going on for the T700, and I hope it carries over to Nougat in the near future! (That's not an ETA or feature request though.)
[Galaxy Tab S Android Development] EyeBalos:
I just rebooted my SM-T700 awhile ago and now stuck in a boot loop. I can't get into recovery mode via the 3 hardware keys but I can go into download mode.

What is the correct bootloader to use? I rooted my device a year ago before flashing IronMan V2.5. Haven't updated my bootloader since, just TWRP from 2.8.4 to 3.0.2.1.

Any suggestions on how to fix the boot loop? Thanks!
[Galaxy Tab S Android Development] Paulicat:
You should be fine to dirty flash in between builds.

Also, highly suggest going to the build with logcat spam fixed. Its very solid build. I've delayed the Vanir release for a couple days because it was too time consuming flipping back and forth. My changes will get to github tomorrow and deadman96385 will push them up to main. That way I can leave the cm builds and get to unofficial Vanir (and possibly other ROMs!).

---------- Post added at 09:57 PM ---------- Previous post was at 09:56 PM ----------

Very surprised to hear that the three finger boot isn't getting you to recovery. I am using the lollipop bootloader right now and all seems fine.
[Galaxy Tab S Android Development] EyeBalos:
Where can I download the Lollipop bootloader?
[Galaxy Tab S Android Development] Paulicat:
First post.
[Galaxy Tab S Android Development] EyeBalos:
OK, I flashed the Lollipop bootloader from the first post and reflashed TWRP 3.0.2 - both via Odin. I'm still getting a boot loop and cannot get into recovery. I can still get to download mode. I may need to reflash CM13. How can I do this via Odin?
[Galaxy Tab S Android Development] Paulicat:
I'd probably suggest you reflash and entire lollipop odin rom first...

Also apologies to everyone, the bad mixer_paths.xml got into the last build by mistake.

I'm rebuilding now and will post a new link shortly.

Can be dirty flashed for those with the last build on.
[Galaxy Tab S Android Development] Paulicat:
Here's the latest build Dec 05 2016 with fixed mixer paths.

https://www.androidfilehost.com/?fid=385035244224403721
[Galaxy Tab S Android Development] Paulicat:
Santa showed up for you, check my previous post for the build from December 5, all the fixes in place.
[Galaxy Tab S Android Development] EyeBalos:
Hi Paulicat, I was able to boot into recovery when the tablet's battery fully discharged and then recharged it. I installed your Dec 05 build and it's working great! Battery life is very good - doesn't seem to consume any power when the tablet is on sleep with wifi and gpf off. I've upgraded the bootloader as well. Thanks!
[Galaxy Tab S Android Development] Tzuiopue:
Something useful at last, thank you Santa ;)

Excellent work. 12-05 build is running smoothly, no problems so far!
[Galaxy Tab S Android Development] dknk99:
The Dec 05 version is running great for me. I did a clean install, was on stock. I really haven't noticed any issues so far and the battery drain appears similar to stock which is a good thing. Good job....
[Galaxy Tab S Android Development] Paulicat:
Great to hear these positive reports!
[Galaxy Tab S Android Development] kevria:
build 12-05 is running well for me also. Battery drain is at an acceptable level and I havent run into any issues so far other than with Magicka not working.
[Galaxy Tab S Android Development] Paulicat:
Can you get a logcat of the crash?

Have you tried adjusting those MSAA4x settings in develop options?

I don't own that game on android so I can't really test anything.

---------- Post added at 04:55 PM ---------- Previous post was at 04:54 PM ----------

Enjoy, glad to hear its working for you!
[Galaxy Tab S Android Development] koimr:
Nice

Just installed this today, works really well.

Only issue I have is that LastPass won't start up, I am going to guess it's a problem with LastPass and not this ROM though and I can use an older version still that works.

Nice and smooth, good job! :)
[Galaxy Tab S Android Development] kevria:
I have a screenshot of the exception in amabillingclient if you want to see it. Its a NullPointerException in AMABillingClient.setMappingAvailable. I cant find anything online about it so it is probably a game coding issue.
[Galaxy Tab S Android Development] kevria:
I ran into the same problem with Lastpass last night, which version still works?
[Galaxy Tab S Android Development] koimr:
It's 3.2.3 for me and I got it here: https://lastpass.com/releases/lpandroid3.2.3.apk :)
[Galaxy Tab S Android Development] kevria:
That version worked for me but I hadnt realized how old it was. One potential issue is that it thinks I only have 24 days left of a trial period whereas Lastpass is now free for everyone.
[Galaxy Tab S Android Development] koimr:
Yeah, that could be an issue.

I do remember having this problem before with Lastpass on a different ROM (at least a year ago) and I have no idea what I did to solve it. :confused:
[Galaxy Tab S Android Development] hybae:
Hey Paulicat,

I just flashed your 12.5 build last night as I was stoked to read the camera was now working. Everything is running as expected aside from the microphone. It seems as if there is no recognition when using the voice search option for Google or the 'OK Google' command. Also, the volume for the on board speakers remains fairly low. Even when I max out a video. I have to resort to headphones if I want to stream something to the device. Otherwise, I have not run into any issues in the past 24 hrs. Well done to both you and javelinandart!
[Galaxy Tab S Android Development] Paulicat:
You can try the deathly kernel audiutor app in the play store.

It has settings for audio gain.

Mic for ok google I'm not sure about as I don't use the Google launcher. The mic itself does work if you use sound recorder.
[Galaxy Tab S Android Development] koimr:
Looks like we aren't the only ones:

LastPass not loading on CyanogenMod 13
[Galaxy Tab S Android Development] hybae:
Thanks for the quick response and suggestion of that app.

However, I have located the mixer_paths.xml file. I see can the entire 'common digital volume' section is set to 32, which is significantly lower than most files I have researched. I also see the notation warning not to change it. Having next to no background in coding it seems the script in our mixer file is tremendously different than most I have found online. This file is obviously key to both of my issues. Is there something here I can change for louder volume and a more responsive mic?

I know my mic was working properly waaay back on the 5/14 build from the op. This may be a noob question, but is there a way to get a hold of the original file without flashing my way back there? Just curious to see what the difference might be.

Attached is a screen of the Google nonsense not working. Honestly, I don't care about the voice command so much as the voice search feature. Something feels weird about saying OK google. :eek:
[Galaxy Tab S Android Development] SkilesAwaRz:
Hi,

Thanks for your work maintaining our tablets alive :) I'm having a question : does 1080p or 720p 60fps youtube video work ? Does it struggle ? I'm using ASOP 7.0 atm, and It struggles actually...

Sorry if the question was already asked, thanks by advance !
[Galaxy Tab S Android Development] Funky_Giraffe:
It works just fine on mine with the December 5 release. However the microphone is not working for Google voice search/ Ok Google recognition and the feature "tap to wake" is not available.
[Galaxy Tab S Android Development] Paulicat:
YouTube is pretty much flawless in CM13.

---------- Post added at 02:18 PM ---------- Previous post was at 02:16 PM ----------

I will try extracting the mixer file from the 14th build you mention. I'll let you know if it works.

---------- Post added at 02:38 PM ---------- Previous post was at 02:18 PM ----------

Hey so I just took tried this out.

I installed the google search app to test for you.

Found out the problem, you have to go into Settings/Apps/Google App/Permissions and grant Microphone access.

As soon as I turned this on, Ok Google works perfectly and so does voice dictation!

Give it a try, I'll be super surprised if yours doesn't work after this!

---------- Post added at 02:40 PM ---------- Previous post was at 02:38 PM ----------

Check this post, you need to grant Microphone permission to the Google App for Ok Google to start working (along with working voice dictation).

The tap to wake feature I will have to look into further.
[Galaxy Tab S Android Development] SkilesAwaRz:
Thank you very much for your answer guys, just wanted to know if xposed framework could work with this ROM ? (I'm not asking for help or assistance for it) I've just never used it before :) thanks !

Envoyé de mon PLK-L01 en utilisant Tapatalk
[Galaxy Tab S Android Development] Paulicat:
Not sure if you guys have tried/seen my VanirAOSP rom thread but LastPass appears to be working fine in VanirAOSP.

I just installed LastPass, created my account, and I'm in the app with 60 days left of "Premium" features.
[Galaxy Tab S Android Development] koimr:
Good stuff, I will give that one a shot then. :) Thanks!
[Galaxy Tab S Android Development] Funky_Giraffe:
Thank you for your answer Paulicat, I tried it but it does not work even after a clean reinstall. It seems to be just a Google problem though, I tried Bing Search and it worked no problem. Which Gapps did you install?
[Galaxy Tab S Android Development] Paulicat:
I used pico opengapps, install google search app and set up the permissions AFTER the setup wizard.

It should work like this.

If not working here in CM, try my VanirAOSP rom build and see if it works there.
[Galaxy Tab S Android Development] zyguo:
Why every dev release couple days before monthly security update and deactived after that........
[Galaxy Tab S Android Development] razholio:
I don't see any recent builds in the OP, where are you downloading these? thanks.
[Galaxy Tab S Android Development] Paulicat:
Page 53. I link to a build I did on the 5th of December.

---------- Post added at 02:02 PM ---------- Previous post was at 02:00 PM ----------

It can be updated quite easily.

You can always do it yourself, which is exactly why I started building myself.

The sources I used to build the last release are all on GitHub.com/Paulicat, you're more than welcome to go ahead and fork/use them, and build.
[Galaxy Tab S Android Development] razholio:
I've done builds before, and could certainly give a stab at building this one. Do you have a roomservice.xml you would be willing to share? thanks, man.

---------- Post added at 05:44 PM ---------- Previous post was at 05:41 PM ----------

When you say deadman is gonna push to main, does that mean he's gonna start official builds?
[Galaxy Tab S Android Development] Paulicat:
Sorry I don't use a roomservice.xml I just place my device/kernel/vendor into the rom tree and build from there.

Deadman96385 will update the GitHub.com/Exynos5420 repos which are the main repos for this device.
[Galaxy Tab S Android Development] razholio:
Oh, I think I get it. I would just pull that repo and build, right? What would the build commands be? Just brunch?

How do you sync up with cm13?
[Galaxy Tab S Android Development] Paulicat:
Here's a quick rundown:

repo sync the cm source using branch cm-13.0

get device repo here using branch cm-13.0 -> git clone to: device/samsung/klimtwifi

get kernel repo here using branch cm-13.0 -> git clone to: kernel/samsung/exynos5420

get vendor repo here using branch cm-13.0 -> git clone to: vendor/samsung

remove these from cm source tree (if exists): hardware/samsung, hardware/samsung_slsi-cm, hardware/samsung_slsi

get hardware/samsung here using branch cm-13.0 -> git clone to: hardware/samsung

get hardware/samsung_slsi-cm/exynos5420 using branch cm-13.0 -> git clone to: hardware/samsung_slsi-cm/exynos5420

get hardware/samsung_slsi-cm/exynos5 using branch cm-13.0 -> git clone to: hardware/samsung_slsi-cm/exynos5

get hardware/samsung_slsi-cm/exynos using branch cm-13.0 -> git clone to: hardware/samsung_slsi-cm/exynos

get hardware/samsung_slsi-cm/openmax using branch cm-13.0 -> git clone to: hardware/samsung_slsi-cm/openmax

IMPORTANT:

After you get all this source setup, disconnect your vm/pc from internet access so as to prevent cm build to go out to internet because it will/may replace some of the repositories we just replaced above.

Next would be simple steps:

. build/envsetup.sh

brunch klimtwifi

You should have a rom building!
[Galaxy Tab S Android Development] amateurhack:
Thanks for the ROM. Downloaded and installed last night. Working fine so far. Looking forward to running it through the paces.
[Galaxy Tab S Android Development] swazau:
Do you support exposed modules?
[Galaxy Tab S Android Development] amateurhack:
[MENTION=5168758]Paulicat[/MENTION] Thanks for the good work on this ROM. Two days in, and I've had no real issues.

I didn't see any references in the thread to using Viper. Given the warnings in the OP about using exposed, I thought I would check and see about any known issues with Viper before I install it. I know you're not supporting it, but I can't do without it at this point.

Thanks in advance.

-A.H.
[Galaxy Tab S Android Development] Paulicat:
You can always try it and report back for everyone.

I don't use it so I don't personally know.

Here's a new build with December 1, 2016 security patch applied:

December 1, 2016 security patch build.
[Galaxy Tab S Android Development] razholio:
Hey, thanks for these instructions. I was just looking over the list of repos you have there and am wondering, could this be put into a roomservice.xml? My understanding of the CM build process is limited, but that's what this looks like.
[Galaxy Tab S Android Development] Paulicat:
Honestly I am not the most experienced builder...I just do what works for me.

If roomservice.xml is something you know about, give it a shot and report back!
[Galaxy Tab S Android Development] amateurhack:
I have Viper for Android installed and it is working fine so far.

Thanks for the new build. Installing presently.
[Galaxy Tab S Android Development] amateurhack:
Just ran into the hangouts bug. I read the posts, so I know you're already working on it. Just confirmation that it's still there in today's build.
[Galaxy Tab S Android Development] EyeBalos:
Hi Paulicat, just wanted to say that the Dec 5 build is working flawlessly for me and best of all battery life is excellent! During sleep mode with wifi off, it doesn't seem to consume any power. With the previous builds, there was a noticeable drain.

Interested in your VanirAOSP ROM. I understand it's based on CM13 but what extra features does it have? Is PrivacyGuard still retained in VanirAOSP?

Thanks again!
[Galaxy Tab S Android Development] razholio:
Well, yer miles ahead of me. I'll Give that a shot and see. Thanks again!

---------- Post added at 12:49 AM ---------- Previous post was at 12:48 AM ----------

I haven't seen mention of this, do you remember what page it's on? How would you characterize it?
[Galaxy Tab S Android Development] amateurhack:
Just search the thread for hangouts. There's several posts about it.

Right now, hangouts starts up, and I can open a thread of messages and view it, but add soon as you try to type a response, it crashes.
[Galaxy Tab S Android Development] razholio:
Yeah, I was being totally lazy. Didn't realize till after I posted. Thanks for the heads up, tho!
[Galaxy Tab S Android Development] Paulicat:
If you have root, what I would try is grab an apns_conf.xml from any rom and copy it into /system/etc.

Completely and totally guessing here...
[Galaxy Tab S Android Development] amateurhack:
Merry Christmas! Now if you'll just bend over for me: https://www.xda-developers.com/the-death-of-cyangenmod-and-whats-in-store-for-the-future/
[Galaxy Tab S Android Development] swazau:
Will cyanogen leaving the custom ROM scene impact cm13 and cm14 ROMs being updated?
[Galaxy Tab S Android Development] amateurhack:
Yes, though it may continue as LineageOS as the article states. Whatever it is, it can't be called CyanogenMOD.
[Galaxy Tab S Android Development] swazau:
OK cool, I hope some of the tab s cm developer's will continue and use lineageOS
[Galaxy Tab S Android Development] amateurhack:
[MENTION=5168758]Paulicat[/MENTION] If/when the development of this ROM switches over to LinOS sources, will you still maintain it? Will you start a new thread?
[Galaxy Tab S Android Development] amateurhack:
Not a list you want to be on: http://arstechnica.com/staff/2016/12/deathwatch-2017-the-most-endangered-tech-companies/
[Galaxy Tab S Android Development] swazau:
Agreed [MENTION=4272726]amateurhack[/MENTION]
[Galaxy Tab S Android Development] deadman96385:
Sources added to OP sorry about that

Also to everyone that is posting issues this was the first build i declared stable enough for the public use but there are still problems and i will work to fix them.
[Galaxy Tab S Android Development] Venzent:
Deadman, no problem for me, i just report them so You know they exist. So far i'm very happy with this rom and grateful for the time and effort you must put into this.

And for what it's worth, this is the best "1st" release ROM i've seen.
[Galaxy Tab S Android Development] suburbadroid:
Sorry deadman hope I've not annoyed you. The ROM is buzzing dude
[Galaxy Tab S Android Development] Jwoc12:
I love it! Came from AOSP 6.01, wiped, flashed, working! Smooth....so far all the apps I care about are working. Thank you very much! Good job!
[Galaxy Tab S Android Development] zigonneux:
about the battery drain , if you have installed the Facebook app, you should know that this facebook app will drain your battery 20% faster. Use facebook in the browser, not the App. Also, give a break to deadman96385, this is his first alpha MM6 release, so try to explain your problem the best you can without complaining. I'm so happy that he's involved in a new MM6 version. It will be awesome for the T 800 if he ever decide to port it .
[Galaxy Tab S Android Development] deadman96385:
I do not plan to support any device i do not have in front of me i just do not have the time anymore.

New build in OP it has the wakelock bug fixed so the tablet actually goes into deep sleep. The following pictures were my use of it mainly to watch Netflix. So the deeper slopes are of Netflix and then when it almost levels out is when its sleeping.

Obviously battery life will vary depending on what you do with the tablet.

Screenshots:
[Galaxy Tab S Android Development] Venzent:
Great, I suppose we can upgrade from the previous install, no clean install needed?
[Galaxy Tab S Android Development] subaquatic:
For anyone who is wondering if the Lollipop bluetooth issues have carried over, I can confirm that Pandora works over 2.4GHz Wifi with no stuttering and Emby and Kodi stream audio and video perfectly in sync. I think this is the first SM-T700 rom (besides stock) that I've tried that didn't have these issues.

Also, if your device freezes on the Samsung boot screen, you can flash an updated bootloader from this post: http://xdaforums.com/galaxy-tab-s/general/t800-t805-lollipop-bootloaders-t3099362/post63735112#post63735112
[Galaxy Tab S Android Development] atsoca:
Bravo on the new buid!

My blue tooth works awesome thank you

Looking very forward to more builds
[Galaxy Tab S Android Development] deadman96385:
Added it to the op did not know that was needed thanks!
[Galaxy Tab S Android Development] atsoca:
Should we post bugs?
[Galaxy Tab S Android Development] deadman96385:
Yes please other then the ones posted in the 2nd post
[Galaxy Tab S Android Development] atsoca:
ok kewl

first one i noticed is the home screen does not rotate....this is a minor bug i know

sorry for being trivial

Rob
[Galaxy Tab S Android Development] deadman96385:
Long press on the homescreen select the up arrow and select allow rotation
[Galaxy Tab S Android Development] atsoca:
done and done!! awesome thank you
[Galaxy Tab S Android Development] BraianV:
When i do screen mirroing to tv (i have both a Nexus Player and a chromecast 1) the tab does conect to tv bit it shows black screen but sound can be listened (from movies, music, games ,etc)

Its not a nexus Player and chromecast problem because my s4 can mirror well, my tab pro 8.4 with cm13 too, my sister g2 with a g4 rom too, and this tab toó (if i use stock roms like iron rom, etc)

I did try this with a clean rom and only open gapps flashed.

Also supersu doesnt update its binaries