yashsingh1/xdaforums huggingface dataset:
[HTC Tornado] ianmills:
You can delete this post too ;)

but why don't you let us know WHY the problem is happening in your original post?

There's no need to be secret about it, especially if you expect us to give us our personal information. Otherwise, I have no interest in giving you my information...
[Galaxy Tab S Android Development] javelinanddart:
Bugs:

Camera

My Local manifest this will allow you to build any of the tab s variants

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CM-Tab-S/android_device_samsung_klimtwifi" path="device/samsung/klimtwifi" remote="github" />
<project name="CM-Tab-S/android_device_samsung_klimtlte" path="device/samsung/klimtlte" remote="github" />
<project name="CM-Tab-S/android_device_samsung_chagallwifi" path="device/samsung/chagallwifi" remote="github" />
<project name="CM-Tab-S/android_device_samsung_chagalllte" path="device/samsung/chagalllte" remote="github" />
<project name="CM-Tab-S/android_device_samsung_chagallltetmo" path="device/samsung/chagallltetmo" remote="github" />
<project name="CM-Tab-S/android_kernel_samsung_klimtwifi" path="kernel/samsung/klimtwifi" remote="github" revision="deathly_cm-13.0" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" />
<project name="CyanogenMod/android_hardware_samsung_slsi-cm_exynos" path="hardware/samsung_slsi-cm/exynos" remote="github" />
<project name="CyanogenMod/android_hardware_samsung_slsi-cm_exynos5" path="hardware/samsung_slsi-cm/exynos5" remote="github" />
<project name="CM-Tab-S/android_hardware_samsung_slsi-cm_exynos5420" path="hardware/samsung_slsi-cm/exynos5420" remote="github" />
<project name="CyanogenMod/android_hardware_samsung_slsi-cm_openmax" path="hardware/samsung_slsi-cm/openmax" remote="github" />
<project name="CyanogenMod/android_external_stlport" path="external/stlport" remote="github" />
<project name="deadman96385/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-13.0-common" />
<remove-project name="platform/prebuilts/qemu-kernel" />
<project path="prebuilts/qemu-kernel" name="platform/prebuilts/qemu-kernel" clone-depth="1" remote="aosp" revision="refs/tags/android-6.0.1_r31" />﻿
</manifest>
[Galaxy Tab S Android Development] javelinanddart:
Reserved
[Galaxy Tab S Android Development] deadman96385:
Enable rotation on the homescreen:

Long press on the homescreen select the up arrow and select allow rotation
[Galaxy Tab S Android Development] Ridilen:
Sweet. Will try this evening.
[Galaxy Tab S Android Development] haimann95:
When do you plan making a build for the T705 (klimtlte)? I already tried my luck with building. The kernel booted, but I didn't boot completely up. This is my new device tree which I unfortunately can not test, because I have to redownload the sources: https://github.com/haimann951/android_device_samsung_klimtlte
[Galaxy Tab S Android Development] MarcoLK:
oh yeah!

i will give it a try!
[Galaxy Tab S Android Development] Zhafon:
Thanks for this man ! Will try to install and will report back in a few minutes ;) [MENTION=4222965]deadman96385[/MENTION]
[Galaxy Tab S Android Development] deadman96385:
Soon, i have a klimtlte being shipped to me now. Once it arrives i will release a build.
[Galaxy Tab S Android Development] MarcoLK:
I installed the rom and i said "WOW!"

its not 100% smooth but it is very good for a first build.

one question: how can i change the background in lock screen?
[Galaxy Tab S Android Development] suburbadroid:
Thanks dead man, been waiting on a cm13 for the tab s. Judging on your other work I bet this is great. Downloading as I write
[Galaxy Tab S Android Development] rookie12:
Does heat issue in gaming and dast battery drain stil presist in cm13 because it was in cm12.1 and thats the only thjng that kept mi away from CM
[Galaxy Tab S Android Development] deadman96385:
Currently there is a wakelock issue but before i had that bug there was no heating or battery drain issues.
[Galaxy Tab S Android Development] rookie12:
So 40•C is normal when playing games and battery drains from 100 t0 p in 1 or 2 hours?
[Galaxy Tab S Android Development] deadman96385:
Chill man i mean't on cm-13.0 on builds that i did not release, so once this wakelock bug is fixed your heating and power problems will be solved.
[Galaxy Tab S Android Development] Venzent:
Bootloop when installing Beta-SuperSU 2.50.

Installed CM13 and Gaps, booted to android. configured first time. Rebooted to recovery and installed SuperSU, bootlooping....

Update:

Solved by installing UPDATE-SuperSU-v2.65-20151226141550.zip
[Galaxy Tab S Android Development] deadman96385:
Why flash supersu when there is root built in?
[Galaxy Tab S Android Development] Venzent:
Maybe my lack of knowledge, I'm not that deep into custom builds, but I thought SuperSU is always needed to provide root access when apps requesting it? (the always allow or ask again within 15 minutes question).
[Galaxy Tab S Android Development] deadman96385:
If you unlock developer settings by tapping the build number in about tablet and then go to developer settings find the Root access option and select Apps only and you will have the same option as supersu it will prompt you when somthing wants to have root with an option to always allow it.
[Galaxy Tab S Android Development] Venzent:
Thanks, didn't know that.....

And thanks for the ROM also of course ;)

---------- Post added at 08:31 PM ---------- Previous post was at 08:03 PM ----------

Ok,

(very) first findings.

ROM is fast, smooth, no problems so far, heating and/or battery drain must be waited for in the upcoming days (if exists).

2 issues, Facebook FC's, directly at startup, and when an app that uses FB starts, it gives the CF error as well (like Candy Crush).

KPN iTV online (local televison provider, streaming application), gives black screen in app instead of the stream itself.
[Galaxy Tab S Android Development] marmo:
[MENTION=4222965]deadman96385[/MENTION] Marshmallow build has been released for Galaxy Tab S2. Maybe it could be helpful and you can reuse some drivers for our loved Tab S. Hope it helps.

Tab *S2* build: http://www.sammobile.com/firmwares/download/70049/T815XXU2BPD6_T815OXA2BPD6_DBT/
[Galaxy Tab S Android Development] deadman96385:
Snap is currently not stable for our tablet and its low on the to do list to fix because the aosp camera and google camera work fine

The mic's are too quiet because the levels need to be tweaked now that the noise suppression is properly working they were lowered long ago because it was too loud because the suppression was broken

Sadly the tab s2 uses an exynos 5433 with a newer mali gpu so almost none of it will be useful.
[Galaxy Tab S Android Development] franzli:
[MENTION=221356]Deadman[/MENTION]

I'm trying to compile the ROM myself, but just starting to learn. I have successfully built temasek's ROM for lt03wifi before, but I must be missing something in my local manifest. Would you mind sharing what I may have to add to the local manifest on top of the two github repos you link in the OP? Last thing I tried was adding several of Schischu's repos, but I guess I either added something too much or am still missing something. Before that I tried it with the slsi-cm modules I used for my lt03wifi, but that didn't seem to work either. A short pointer as to how I can find out myself what I'm missing would also be much appreciated!

This is my current manifest which obviously has something wrong:

Many thanks in advance!

PS: Or do I just add your two linked repos and do "repo sync" and then "breakfast klimtwifi" to get everything? For lt03wifi I had to include the repos manually that's why I thought it wouldn't work here either seeing it's not an official build yet?
[Galaxy Tab S Android Development] macs:
Thanks, bro! Waiting for it!
[Galaxy Tab S Android Development] deadman96385:
I fixed your manifest based on my own now all you need to do is lunch it and build or just brunch klimtwifi

Edit: I have also added mine to op it includes the device trees for T700 (klimtwifi), T705 (klimtlte), T800 (chagallwifi), T805 (chagalllte), T807T (chagallltetmo)

<?xml version="1.0" encoding="UTF-8"?>
<manifest>

<remove-project name="platform/prebuilts/qemu-kernel" />
<project path="prebuilts/qemu-kernel" name="platform/prebuilts/qemu-kernel" clone-depth="1" remote="aosp" revision="refs/tags/android-6.0.1_r31" />﻿

<project name="Joshndroid/android_device_samsung_lt03wifi" path="device/samsung/lt03wifi" remote="github" revision="cm-13.0" />
<project name="Joshndroid/android_kernel_samsung_lt03wifi" path="kernel/samsung/lt03wifi" remote="github" revision="cm-13.0" />
<project name="Joshndroid/android_vendor_samsung_lt03wifi" path="vendor/samsung/lt03wifi" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="package/apps/SamsungServiceMode" remote="github" revision="cm-13.0" />

<project name="CyanogenMod/android_hardware_samsung_slsi-cm_exynos" path="hardware/samsung_slsi-cm/exynos" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_hardware_samsung_slsi-cm_exynos5" path="hardware/samsung_slsi-cm/exynos5" remote="github" revision="cm-13.0" />
<project name="CM-Tab-S/android_hardware_samsung_slsi-cm_exynos5420" path="hardware/samsung_slsi-cm/exynos5420" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_hardware_samsung_slsi-cm_openmax" path="hardware/samsung_slsi-cm/openmax" remote="github" revision="cm-13.0" />

<project name="CM-Tab-S/android_kernel_samsung_klimtwifi" path="kernel/samsung/klimtwifi" remote="github" revision="deathly_cm-13.0" />
<project name="CM-Tab-S/android_device_samsung_klimtwifi" path="device/samsung/klimtwifi" remote="github" revision="cm-13.0" />
<project name="deadman96385/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-13.0-common" />
<project name="CyanogenMod/android_external_stlport" path="external/stlport" remote="github" revision="cm-13.0" />
[Galaxy Tab S Android Development] Lightn1ng:
What ended up being the fix for the screen freezing? (Was it a kernel problem?) Also can you in the latest build not released select text in Chrome without a system reboot?
[Galaxy Tab S Android Development] Lightn1ng:
Just curious: if I compile this from source, will there be a chance of hardbricking?
[Galaxy Tab S Android Development] franzli:
Great, thanks a lot for the fix of my manifests! Building now, curiuous if it's gonna work.
[Galaxy Tab S Android Development] Lightn1ng:
Keep me posted as I'm wanting to do this myself but paranoid about a hard brick

---------- Post added at 11:51 PM ---------- Previous post was at 11:38 PM ----------

So how's the new build coming along? :fingers-crossed:
[Galaxy Tab S Android Development] deadman96385:
You can not hardbrick your device by flashing a rom zip the worst that can happen is you get a bootloop and you have to go back into recovery and restore a backup

It had to do with using outdated gralloc settings
[Galaxy Tab S Android Development] Lightn1ng:
Thank you
[Galaxy Tab S Android Development] khanfuze:
For some reason the volume for paying some movies is very low for this Rom compared to cm12. Music is fine. YouTube is fine. Some movies mkv and mp4 are very faint but xvids play at normal volume.

Edit: mixer_paths.xml has volume settings I think but I don't know how it works.
[Galaxy Tab S Android Development] _Negan_:
Hi dev, it will work fingerprint scanner in next release? I find it working very well in the other marshmallow aosp rom here in this section on xda. Thanks
[Galaxy Tab S Android Development] deadman96385:
What app are you using to play the mkv and mp4 files, so i can try and reproduce it

Please search the thread before asking

http://xdaforums.com/showpost.php?p=66531048&postcount=175
[Galaxy Tab S Android Development] Lightn1ng:
I don't think he has this planned.
[Galaxy Tab S Android Development] _Negan_:
I read this but i didn't understand what you mean because sensor works very well
[Galaxy Tab S Android Development] deadman96385:
The sensor works fine on aosp, but it does not work well on cm so i am not working on it.
[Galaxy Tab S Android Development] khanfuze:
It's quiet with both vlc and the native player. I tried shutting off hardware acceleration in vlc but that made no change.
[Galaxy Tab S Android Development] Lightn1ng:
Sorry if newb comment but isn't the only driver-wise difference between AOSP and CM the slsi-cm vs slsi-insignal?

or is that completely unrelated
[Galaxy Tab S Android Development] deadman96385:
Thank you I will see about fixing it

They are related but I have mobicore functioning on the slsi-cm variant and I do not have the same bugs that aosp has while using the slsi-cm variant. The main difference is that cm has modified the fingerprint implementation some and that is causing problems somehow. The implementation that aosp and a few other Samsung devices use isn't coded the best which is why I am waiting on the better verison that is in development.
[Galaxy Tab S Android Development] Lightn1ng:
The S5's CM13 build has a working fingerprint scanner, and if I read correctly, they're the same sensor as on the Tab S

Maybe you could decompile the S5 build and see how they did it there?
[Galaxy Tab S Android Development] deadman96385:
That is the implementation that aosp is currently using and it isn't very good.
[Galaxy Tab S Android Development] Lightn1ng:
Interesting, what's wrong with it? Seems to work fine on my S5

---------- Post added at 02:02 PM ---------- Previous post was at 01:12 PM ----------

He's started to upload the updated version for klimtlte and chagalllte! :D

Hopefully klimtwifi is soon! :D :D :D :D :D :D :D
[Galaxy Tab S Android Development] franzli:
Thanks again for your help, I managed to build the ROM without problems! Very nice!

I also managed to build temasek's ROM for klimtwifi too, using the same local manifest, which I found pretty cool! (For some reason compiling stops with an error today, maybe some incomplete changes in the sources, don't know). An advantage of the temasek ROM seems to be that rotation works fine there, whereas on the vanilla cm it only rarely auto-rotates (if at all?). Just thought I'd mention that, though I haven't tried it for longer periods yet.
[Galaxy Tab S Android Development] khanfuze:
Auto rotate stops working sometimes. A soft reset fixes it.
[Galaxy Tab S Android Development] zztop10:
Yes, auto rotate stops for me also.
[Galaxy Tab S Android Development] deadman96385:
Yeah i am looking into it i think it is an upstream bug affecting us because i have not messed with sensors at all.
[Galaxy Tab S Android Development] Lightn1ng:
[MENTION=4222965]deadman96385[/MENTION] how's the new update coming along for klimtwifi?
[Galaxy Tab S Android Development] tylt:
Autorotation

I was having a look at this problem this morning, and it looks like this problem has popped up elsewhere. Although take it with a pinch of salt because it refers to a Snapdragon-based phone. I guess there's a small chance that it's related.

Because I'm a newb, it won't let me post links. Grr. Sorry bout that. But it is quite easy to find -- search the cyanogenmod forum for "CM13 auto rotate not working except in camera", then find the post with "changelog"; seems like there were some changes to variable names related to timers for autorotation.

But more importantly, thanks for the ROM -- been running it for a couple of days and it's very smooth. :good:
[Galaxy Tab S Android Development] deadman96385:
Thank you very much i have found the change you have mentioned and will try it out shortly

I should have a build sometime this week.
[Galaxy Tab S Android Development] Lightn1ng:
Thanks for the hard work! :D
[Galaxy Tab S Android Development] sarky1:
Appreciate the work also!
[Galaxy Tab S Android Development] franzli:
I haven't been able to compile the ROM for the last one or two weeks. Is this expected because you are working on the sources, [MENTION=4222965]deadman96385[/MENTION]? Otherwise, I'll have to see if I changed anything in my manifest or other config by mistake.

It usually breaks in one of two ways. Either I get a problem with the kernel configuration, last couple of lines output here:

I have tried a few times to set the config manually (going to kernel directory, "make cyanogenmod_deathly_klimtwifi_defconfig"), in which case it starts compiling but then stops at compiling some module (don't know right now which one, but can check back once I get to that point again).
[Galaxy Tab S Android Development] deadman96385:
Yes revert the last 2 commits in the kernel i will move them off the main branch soon they are a incomplete kernel merge
[Galaxy Tab S Android Development] marmo:
[MENTION=4222965]deadman96385[/MENTION] I'll be alone at home this weekend, no girlfriend around. That would be a great opportunity to play around with a new build...Any chance to get it? :P
[Galaxy Tab S Android Development] franzli:
Thanks, that's good to know, so it's not my mistake. Took me a moment to figure out how to revert properly (good opportunity to learn a bit about git), but reverting those two commits did indeed allow me to compile just fine again (I have only tried temasek's version, but suspect the same holds for plain CM13).
[Galaxy Tab S Android Development] Lightn1ng:
excitement building up...
[Galaxy Tab S Android Development] deadman96385:
I have added a new build in the op

Changelog:

Enabled Noise suppression

Hopefully fix rotation problems

Enabled OpenGL ES 3.1 (Might fix Hearthstone)

Misc fixes
[Galaxy Tab S Android Development] sneyder97:
Just did a clean install. Rotation is working fine but now there's this weird bug that won't let me pull down the quick settings.

Edit: Now that I tried some apps, it seems that the notifications are not working at all

Enviado desde mi SM-T700 mediante Tapatalk
[Galaxy Tab S Android Development] franzli:
Great, will be curious to try! Would you mind sharing if the changes necessary for the rotation issue are in the device or kernel, i.e. in the sources from you added in the local manifest, or if you made changes to the cm base anywhere? I'm just asking because I'm running the temasek version of cm with the hello of your kernel and device tree and wonder if it'll be enough to just do a repo sync or if I'll have to change something in the sources.

Sorry if this is a trivial question, just learning about these things.

---------- Post added at 09:51 AM ---------- Previous post was at 09:49 AM ----------

Have you made sure you used the latest gapps? I once had this issue on another device, and it was because I had used gapps that were three days old.
[Galaxy Tab S Android Development] Lightn1ng:
Yeah I would love to know what is causing this bug. Happened on my S5 as well.

---------- Post added at 05:43 AM ---------- Previous post was at 05:41 AM ----------

Thanks :D may want to be more specific on what misc fixes is...
[Galaxy Tab S Android Development] <galaxylove>:
deadmen can you also make an android n build when it comes out for the t700 :D
[Galaxy Tab S Android Development] Lightn1ng:
This ROM isn't fully featured yet. Let's wait for N to come out and see ;)
[Galaxy Tab S Android Development] <galaxylove>:
thats why i said "when it comes out" :)
[Galaxy Tab S Android Development] Lightn1ng:
Let's leave his MM threads free of any N-talk :p
[Galaxy Tab S Android Development] sneyder97:
That worked. Thanks!
[Galaxy Tab S Android Development] tebra:
This rom is really good. No bug for now. Thank you
[Galaxy Tab S Android Development] tebra:
Hi [MENTION=4222965]deadman96385[/MENTION]

I try the following app to check if doze function is enable on T700 with this rom.

http://xdaforums.com/showthread.php?t=3374265

As you can see on the screenshot there is a missing motions sensor. Can you fix this?
[Galaxy Tab S Android Development] deadman96385:
We do not have a significant motion sensor and making a virtual one causes a lot of battery drain.
[Galaxy Tab S Android Development] stormy_gale:
Deleted
[Galaxy Tab S Android Development] koda von chrome:
Damn, went to try the new build (was on 4/11) and reset as per instructions.. now stuck on a teamwin reboot loop.

ADB and ODIN cannot see/connect to the Tab S any longer.

Ive let it run out of power till it dies just now but I still cannot get it to recovery as once I put power into it again it starts the loop again.

Is it bricked?

EDIT

Somehow, by repeatedly trying different timings of putting in the power adapter and the recovery button combo's I got it in ODIN mode and reflashed TWRP.

Appears it might be working, if I can charge it again.

What can I do to avoid this problem in the future?

EDIT2

After resetting with Wipe in TWRP and flashing both 5/14 and GAPPs its now stuck on CM13 boot logo!!

Argh, frustrating!
[Galaxy Tab S Android Development] tebra:
Hi [MENTION=4222965]deadman96385[/MENTION]

Is it normal that default camera app is missing/hidden and other camera app said that there is no camera on this device?
[Galaxy Tab S Android Development] sneyder97:
This is happening to me too.
[Galaxy Tab S Android Development] deadman96385:
ugh i guess something broke the camera again i'll look into it, i can reproduce it locally.
[Galaxy Tab S Android Development] tebra:
Hi [MENTION=4222965]deadman96385[/MENTION]

can I help you to fix the camera bug on T700?

Are you going to release a new CM13 build?
[Galaxy Tab S Android Development] franzli:
I still cannot build anymore, even when reverting the final two commits to your kernel. Not sure if there's something wrong in my setup, but my error messages mention something about the camera, so I'm posting them here just in case they're of any use:

device/samsung/klimtwifi/sepolicy/mediaserver.te:6:ERROR 'unknown type camera_prop' at token ';' on line 13799:
allow mediaserver system_server:unix_stream_socket { read write setopt };
allow mediaserver camera_prop:property_service set;
checkpolicy: error(s) encountered while parsing configuration
external/sepolicy/Android.mk:85: recipe for target '/media/georg/1de6a47b-131d-4240-887e-5e4480138c4b/temasek-cm13.0/out/target/product/klimtwifi/obj/ETC/sepolicy_intermediates/sepolicy' failed
make: *** [/media/georg/1de6a47b-131d-4240-887e-5e4480138c4b/temasek-cm13.0/out/target/product/klimtwifi/obj/ETC/sepolicy_intermediates/sepolicy] Error 1
make: *** Deleting file '/media/georg/1de6a47b-131d-4240-887e-5e4480138c4b/temasek-cm13.0/out/target/product/klimtwifi/obj/ETC/sepolicy_intermediates/sepolicy'
make: *** Waiting for unfinished jobs....
/media/georg/1de6a47b-131d-4240-887e-5e4480138c4b/temasek-cm13.0/out/host/linux-x86/bin/checkpolicy: loading policy configuration from /media/georg/1de6a47b-131d-4240-887e-5e4480138c4b/temasek-cm13.0/out/target/product/klimtwifi/obj/ETC/sepolicy.recovery_intermediates/policy_recovery.conf
/media/georg/1de6a47b-131d-4240-887e-5e4480138c4b/temasek-cm13.0/out/host/linux-x86/bin/checkpolicy: policy configuration loaded
/media/georg/1de6a47b-131d-4240-887e-5e4480138c4b/temasek-cm13.0/out/host/linux-x86/bin/checkpolicy: writing binary representation (version 30) to /media/georg/1de6a47b-131d-4240-887e-5e4480138c4b/temasek-cm13.0/out/target/product/klimtwifi/obj/ETC/sepolicy.recovery_intermediates/sepolicy.recovery
make: Leaving directory '/media/georg/1de6a47b-131d-4240-887e-5e4480138c4b/temasek-cm13.0'