yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Original Android Development] dknk99:
Music cracks and pops when screen is off

More on the performance settings as I have been having pops/crackles when playing music via the built in speakers and screen is off. If you go to Settings -> Performance -> Processor -> CPU governor. The default is "interactive", leave that alone and try setting the "Minimum CPU frequency" option to 300 MHz instead of the default 100 MHz, maybe 100 MHz is a bit too low. That way you get to keep "interactive" which I assume is the best option for battery life and performance (guessing). If 300 MHz doesn't work for you, bump it up more. Seems to work OK for me at 300 MHz.
[Galaxy Tab S Original Android Development] fraser.dk:
I thought the hardkeys went zombie after I unlocked my device once. Was pretty high & could be misremembering tho. Your rom is nearing perfection with each iteration amigo :D heck I get an extra 1h SoT with 0207 compared to TW/CM11, what's better than that?
[Galaxy Tab S Original Android Development] eousphoros:
Mind trying 200?
[Galaxy Tab S Original Android Development] dknk99:
200 seems to be OK, switched between 100 and 200 while streaming a podcast. Could hear the cracks at 100 (again it's not super noticeable but it's there).
[Galaxy Tab S Original Android Development] :
Yes and the oscilating between 100 (which is indeed 200) and 200 (which is indeed 400 MHz) also needs more battery than sticking to 400 (in settings 200 MHz). (on MHZ: sammy has halfed the "naming" of the freq steps of A7 cores, so that A7 and A15 cores does not have overlapping freqs - for an in dept discussion see my conversation with [MENTION=3511708]UpInTheAir[/MENTION] in cm11 thread)

Therfor I have init.d support in my builds, which sets cpu min freq to 200 (400 MHz) in 01systemtuning.

OT: if one wants to take a commit by an other author, but wants to change something in the diff or comment while maintaining athorship and git history:

cd to/git/dir
git remote add arbritrary_local_name url://to.git/of_other_dev
git fetch arbritary_local_name
git log --graph --all #to find the hash of the wanted commit
git format-patch -1 --stdout [hash_of_comit] >/tmp/tmp.diff
# edit /tmp/tmp.diff
cat /tmp/tmp.diff |git am

If you don't want to import an other git to your tree, you can use subshells to do just the same:

cd /to/where/ever
git clone url://to.git/of_other_dev
cd /to/git/dir
(cd /to/where/ever/of_other_dev; git log --graph --all) #to find the hash of the wanted commit
(cd /to/where/ever/of_other_dev; git format-patch -1 --stdout [hash_of_commit) | git am

Hope this helps.

It's much easier for future uses and compares to keep git's history. To keep authotship is just respectfull. You can see that for example in my kernel git.
[Galaxy Tab S Original Android Development] Satorikn:
Is it T-705 compatible?
[Galaxy Tab S Original Android Development] Enddo:
I don't think so
[Galaxy Tab S Original Android Development] revendel:
Didn't work on my 705. I guess only for t700. Mega Bummer
[Galaxy Tab S Original Android Development] Enddo:
You are correct. Custom ROMs for one specific model should never be flashed on another. Even if it seems logical that they would be using similar hardware. There are bound to be differences inside the code
[Galaxy Tab S Original Android Development] eousphoros:
Kicked off a new build that will likely be the next release. The only fix that wont be in there is the touchkey stuff as that ended up being a little more complicated then I initially thought. I'll update this post when its finished.

Still no word from CM about the official status. Could still be another week or so if their 3 week timeline is accurate.
[Galaxy Tab S Original Android Development] dcshoes23:
[MENTION=2346758]eousphoros[/MENTION] could you put somewhere in the first post in bold that this build does not work on the SM-T705? Seems that every week someone asks if it works on it.
[Galaxy Tab S Original Android Development] eousphoros:
I have it in the title SM-T700. Can't help people being wishful.

SM-T705 != SM-T700
[Galaxy Tab S Original Android Development] dcshoes23:
I know, but some people need it laid out for them :)
[Galaxy Tab S Original Android Development] eousphoros:
https://blck.io/cm-12-20150211-UNOFFICIAL-klimtwifi.zip

Move to sd card fixed (Thank you [MENTION=4405529]nvertigo67[/MENTION] for pointing me in the right direction)

GPS fixes

Kernel tweaks which hopefully will resolve the audio static but since I can't hear it I will need confirmation from those that do.

Repo sync

(And I am sure there are other things that I am forgetting at the moment)

Enjoy
[Galaxy Tab S Original Android Development] dknk99:
Looks good, sound is working without pops when screen is off. The CPU Frequency looks pegged at 250 GHz minimum. I see the kernel is labeled "dirty". I'm guessing you just edited "arch/arm/configs/klimtwifi_01_defconfig"? CONFIG_HZ= ...
[Galaxy Tab S Original Android Development] :
Wow - that's fast! How do you cool your device? ;) SCNR.

It's not that easy. You have to mess with sammy's exynos code to change freqs. I have done some changes there to make chagall more battery friendly. I've also unlocked mali's 533 MHz freq step. These changes has been tested on cm11, and I have come to the conclusion that for interactive governour 400 MHz (in settings 200) gives best performance and battery live, but for ondemand 200 MHz (in settings 100) is better....

In cm11 there was official init.d support, so I invented 10systemtuning to make standard settings for interactive.

In cm12 the cm team don't want shell executes in init.d (meaning no effective init.d script support any longer). I found a quite brute force way to put it in again - and use it for my chagall builds. [MENTION=2346758]eousphoros[/MENTION] wants to get official nightlies for you, so my way is no way for him. Even though he had not published his current commits to the kernel, I would guess, that he has reverted the above mentioned changes.

If you are interested in the kernel changes in question look in [MENTION=5616109]euo[/MENTION]sphoros or my kernel-git.

[MENTION=2346758]eousphoros[/MENTION]: if you have to merge a running chagall/klimt kernel in exynos5420 before going officialy nightly, you have to merge all the differences (mainly arch/arm/mach-exynos and the sick synaptics_dsx stuff) with #ifdef in crpalmers kernel. Watch out: sammy has managed to use CONFIG_XXX in complete others contexts and meanings compared to picassos source....
[Galaxy Tab S Original Android Development] interfreak:
Anyone else having issues with the YouTube app? I can't get videos to play at all on the latest build.
[Galaxy Tab S Original Android Development] dknk99:
Didn't get a chance to try YouTube out. Switched back to previous build. I was having weird issues with steaming music (wobbly sound a couple of times and strange extsd card removal while system was running). Overall things seemed to smooth out after awhile. Not sure if its the build or what. Anyway, I'll do the same things on old build, see if same issues crop up. Hey, its all in good fun, I like trying out new things and the damm weather up here is nasty, so it keeps me from looking out the window.
[Galaxy Tab S Original Android Development] hhairplane:
Xposed for Lollipop is ready to go.... http://xdaforums.com/showthread.php?t=3030118
[Galaxy Tab S Original Android Development] danny19901:
Yeah I know but not much is working for it I'm using it on my Xperia Z shame I can't get LP for my T705 though
[Galaxy Tab S Original Android Development] pinoy_ako07:
Plex playback isn't working on the latest build. How do I fix? Other than that great build
[Galaxy Tab S Original Android Development] eousphoros:
I suspect a faulty SD card. I haven't been able to reproduce this.

Youtube also seems fine.

Plex for android seems also to be working for me.

I am going to need more details about the issues you all are encountering since I can't reproduce any issues mentioned
[Galaxy Tab S Original Android Development] dknk99:
Could be, it was a strange thing and only happened the one time. Used the build for a few more hours with no issues before reverting back to previous build. I streamed several hours of music today, no problems. May try the new build again, I'm not afraid ;)
[Galaxy Tab S Original Android Development] interfreak:
I resolved the issue by force quitting the app and restarting it. :)
[Galaxy Tab S Original Android Development] miscom:
I finally switched from CM11 to CM12.

All is working great. No issues. Buttery smooth.
[Galaxy Tab S Original Android Development] Seph32:
I'm not sure if anyone else has reported this but when using Skype calls sounds are fine, but after 10 min or so sounds start to get very distorted and microphone stops working. I've tested this a few times but the same event occurs.

This is on the latest build with a clean install.
[Galaxy Tab S Original Android Development] dknk99:
I've used Skype for over 45 mins on a previous build, no problems. You might want to capture the logs and dmesg while its happening to give to dev. Appstore - Catalog and Terminal Emulator.
[Galaxy Tab S Original Android Development] sweetandsoursauce:
I have a Xperia Z as well, what exactly is Xposed? is it a kernal? and how good is it for the phone?

and if I were to root and install CM12 on my SM-T700, how easy is it to get updates for the rom? would I have to reinstall the rom over and over again?
[Galaxy Tab S Original Android Development] danny19901:
Xposed is a mod for all rooted devices it has a lot of modules stuff like YouTube adaway, YouTube background playback and a lot of other stuff like gravity box which allows you to mod tons of stuff for CM or stock based ROMs I love flat coloured status bars it's amazing .

Flat coloured status bar mod http://xdaforums.com/showthread.php?t=2925521

Xposed for lollipop http://xdaforums.com/showthread.php?t=3030118
[Galaxy Tab S Original Android Development] sweetandsoursauce:
Cool, I'll definitely check it out more! thanks!

btw

if I install CM12 on my T700, is it easy to install updates afterward? or do I need to reinstall the whole rom again?
[Galaxy Tab S Original Android Development] Enddo:
Depending on what type of change has happened in a newer build, you might just have to download the new build to the device and do a dirty flash(aka install the new one on top of the old one). Dirty flashes are never guaranteed though. If there is an issue after dirty flashing then you'll either need to restore from a backup and not update, or you'll need to wipe the proper partitions and install/setup the whole ROM again
[Galaxy Tab S Original Android Development] sweetandsoursauce:
yeah exactly what I was afraid of doing so, rather than jumping on cm12 unofficial i'll probably use stock for now and wait until official one come out
[Galaxy Tab S Original Android Development] SS2006:
Thanks op for the latest release. Just to make sire it'd not just me ,the vibration is not working on the back and recent keys right ?
[Galaxy Tab S Original Android Development] Enddo:
That definitely sounds like the safer bet. Even though I'm perfectly happy with the unofficial one. I haven't even updated mine in weeks because it does everything that I need it to already.

I am curious to hear what CM says once they respond to the OP though
[Galaxy Tab S Original Android Development] fedecape:
I'm running 0207 and everything seems to be working fine. Why should I update?
[Galaxy Tab S Original Android Development] Enddo:
Updates will contain the latest changes from CM12 nightlies. Some of these are optimizations, some of them are features. Update if you want though. I doubt anyone is going to spend much time trying to convince you to update or not
[Galaxy Tab S Original Android Development] kipue:
Hello Peop,

very new to the tab s 8.4, but I want to install this rom.

Just want to check something, is there anything special to do when coming from stock TW rom?

Aside from the usual wipes and such, I'm thinking maybe a specificity like a firmware version or something could be necessary?

If not, great, and thanks for the help :)

EDIT:

Got it installed and running.

First boot is like a lightning, I was afraid I forgot to wipe the previous rom ^^

Sorcery!

No issue to report yet.

Stock running time for the tablet : 2 hours, héhé
[Galaxy Tab S Original Android Development] fedecape:
Thanks. Ha, I know nobody cares. It's just my way of asking for advise :P
[Galaxy Tab S Original Android Development] eousphoros:
https://blck.io/cm-12-20150218-UNOFFICIAL-klimtwifi.zip

Latest cm12 sync.

Now can obtain 3d gps fix
[Galaxy Tab S Original Android Development] kisypher:
Coming from the previous build, is it OK to dirty flash?

«Sent from my not-so-stock T700»™
[Galaxy Tab S Original Android Development] eousphoros:
Should be fine. I dirty flashed it. Though you void your warranty with that dirty flash ;)

I have also updated my vendor/kernel/device repos
[Galaxy Tab S Original Android Development] kipue:
Guys, I've tried the DPI value of 360 (I think it's still at the limit for a tablet), and it's pretty good balance between the default small UI (for example in the notif panel), and screen real estate :)

Try it if you like ^^ (btw, 320 is default DPI)
[Galaxy Tab S Original Android Development] djmax81:
HI.!!! From Note 3 N900 community :) would be glad if you can help us with porting CM12 correctly for Universal 5420 .

Seems our dev's are outnumbered + Can great if you can Contribute lill to all of Us :good:

thread : http://xdaforums.com/galaxy-note-3/...droid-development/rom-cyanogenmod-12-t2999486

kernel Source : https://github.com/flashka07/android_kernel_samsung_exynos5420

Devise tree source : https://github.com/flashka07/android_device_samsung_ha3g

You can send folk request or any kind of help would be welcomed and appreciated :laugh:

Cheers
[Galaxy Tab S Original Android Development] eousphoros:
My repos are public. Your devs are welcome to use them. I don't do dev for devices I don't own. Sorry.
[Galaxy Tab S Original Android Development] djmax81:
Thats Alright.!!! i can understand that But would be Glad if you push us in right direction .:cowboy:

Major issue tho most dev's got no devise but great skills for identical Hardware :angel:

cheers

thanx
[Galaxy Tab S Original Android Development] eousphoros:
https://blck.io/cm-12-20150219-UNOFFICIAL-klimtwifi.zip

Repo sync

More SD card fixes from picassowifi

USB otg stuff

This will probably be the last build I do before official.
[Galaxy Tab S Original Android Development] kisypher:
Have you heard anything yet from CM about becoming official? Just curious.

«Sent from my not-so-stock T700»™
[Galaxy Tab S Original Android Development] eousphoros:
Not yet, I just pinged a side channel so hopefully that will get some movement
[Galaxy Tab S Original Android Development] minieod:
What's the verdict on vibration? I just came over from bliss since be is shutting down support.

I like the capacitive feedback and typing feedback (seems this is on but at like 1% strength)

Thanks guys!
[Galaxy Tab S Original Android Development] eousphoros:
The feedback is supported but not enabled. You will need to modify the sec_touckey.kl file to turn that on.
[Galaxy Tab S Original Android Development] kipue:
Yep, for those interested, use an explorer with root (I use root explorer)

Go to system > user > open sec_touchkey.kl

After each line add " VIRTUAL" (that's 9 spaces after BACK and APP_SWITCH).

Save and reboob

Tested and working :)

Cheers
[Galaxy Tab S Original Android Development] :
Does Titanium work with the changes in init.universal5420.rc for move to sdcard from picassowifi for your device? On chagall I get both (move2sd and Titanium) only working, without the -w option to sdcard.

Does lpm power off charging work for your device when selinux is enforcing? On chagall it works nice with permissive, but I couldn't figure out what additional sepolicy entrys I need - so I switched to healthd power off loading - works great with enforcing.
[Galaxy Tab S Original Android Development] flyduffer:
Hi,

I have problems with the mounting of the external SD card.

From time to time, maybe after sleep of the device or when not used for long time - when I start the Spotify application - it loads too long - like 5-10 minutes or more. Its files are placed on the external SD cards as I can see from File Explorer.

Also when I go into File Explorer or ES Explorer and I browse the external SD card - it opens the folders really slow. For example "android>data" and inside.

Seems a problem with the driver for the SD card or maybe the mount functionality.

After it mounted properly, after 10-15 minutes - everything is fast and working.

Are these "More SD card fixes" going to fix that?

Also from time to time I think that the integrated root is making issues. It's slow or delaying stuff.

And one more - battery draining. Last night I used Skype on the tablet and a call with video for 10-15 minutes drained the battery from 35% to 0% and it shut down.

When playing games - for example "Type:Rider" from Humble Bundle - it drains the battery a lot - every 10 minutes - 10%. And it is interesting that, for example it states that it is 17% and when I restart the tablet - it marks it to be 33% or something more than the current after game play.

I'll check with other games too.

Any suggestions?
[Galaxy Tab S Original Android Development] dknk99:
Titanium does not work for me on the Edit: Feb18 build using the SD card as storage. It can restore backups but can't create new backups (actually it does create a new backup file in the SD card storage folder but for some reason Titanium thinks there is a problem). The Titanium error is "backup failed, storage is full" or something similar to that. The SD card is definitely not full. If I move my SD card backups to the internal storage, everything works as it should. Seems the SD card fix broke some things. I also get occasional SD card missing errors on Google music, I use SD card for cache and downloaded music files. It's occasional, not all the time.

Edit: Removed the -w option from init.universal5420.rc, reboot. Titanium now works correctly using the SD card. Restores and backs up with no problems.

-service fuse_sdcard1 /system/bin/sdcard -u 1023 -g 1023 -w 1023 -d /mnt/media_rw/sdcard1 /storage/sdcard1

+service fuse_sdcard1 /system/bin/sdcard -u 1023 -g 1023 -d /mnt/media_rw/sdcard1 /storage/sdcard1

---------- Post added at 07:36 AM ---------- Previous post was at 07:29 AM ----------

In reading your last change in the kernel repo for CPU frequency, it seems to me that you got rid of min 250(500)GHz and reverted back to old - min 100(200)GHz? But in the latest build the min CPU frequency still seems to bottom out at 250(500)GHZ? Changing to 100 does nothing... Am I misunderstanding something? Edit: I'm using the Feb 18 build from the first page, I see you've posted a Feb 19 build.
[Galaxy Tab S Original Android Development] eousphoros:
I am still running without selinux. Personally I hate it and won't have it enabled unless they require it for official.

As for titanium I don't use it but it sounds like a lot of people do so I will start testing it.

I haven't seen those issues with the sd card, have you tried a different sdcard to see if it has the same issues?

I wasn't able to follow most of this, a little too stream of conscious.

As for the kernel change I reverted a change that disabled 250 MHz and enabled 100/200 by nvertigo that was causing instability and audio artifiacts. 250 MHz is the lowest freq the kernel supports (same as stock)
[Galaxy Tab S Original Android Development] :
Hihi... if there is a club of sepolicy-haters, count me in... I'ventried to fix ums mode lately: works only with selinux=permissive, but even then I don't see any audit log entries in dmesg...
[Galaxy Tab S Original Android Development] dknk99:
What do yah mean? it's clear as mud...:)

Got it..
[Galaxy Tab S Original Android Development] eousphoros:
Have you ever decompiled the stock sepolicy? That thing is almost a million entries long.
[Galaxy Tab S Original Android Development] :
No, never. I'm stuck at learning external/sepolicy/*te by rote... (intentionally no emoticon!) When I'm done with that I will compare it with a decompiled sepolicy... ;)

To get init.d support running shell scripts again, I patch the compiled sepolicy to get a rule in, thats violates a neverallow rule...

I struggled getting lpm mode charging up - replaced it with healthd charging. lpm runs fine with permissive...

(and even if people laugh about it: I'm f..... proud to run with enforcing!)
[Galaxy Tab S Original Android Development] walkerl:
I hated this tablet until i install Cyanogenmod 12 on it.... I was wishing I kept my Nexus 7.
[Galaxy Tab S Original Android Development] eousphoros:
And you should be proud, selinux is a whiny little monkey on androids back. I would prefer something like apparmor though.
[Galaxy Tab S Original Android Development] kipue:
Guys, talking about the SD card read/write for TB, I simply tried to apply one of the apps from market "SD card fix".

It's normally for KK, but it worked for me here :) Just search any of them on the market.
[Galaxy Tab S Original Android Development] dknk99:
I'm glad that you have possibly resolved your write issue. But, since I think the dev is trying to create a workable rom, this is not the answer. Can you name the app you used and better yet, what exactly it did (what file modification it made, etc). This info would be valuable and possibly the change could be implemented into this ROM "if" it is determined to actually fix some issue after the dev reviews it. Just throwing my humble opinion out there.....) Feel free to ignore....
[Galaxy Tab S Original Android Development] kev0153:
Is this ROM still being maintained?
[Galaxy Tab S Original Android Development] :
Yes. Of course. I kindly suggest trading the thread. Ore at least the last 5 pages...
[Galaxy Tab S Original Android Development] kipue:
Hey, yes you are right, but I am just a user, I have no good grasp of what those apps do. I suppose they change the permissions as shown by another user on last page of the thread?

Anyhow, the name of the app is "NextApp sdfix" (there are many others, this is a random choice).

Quick search returned this explaination of the problem, and also what's "fixed".

https://plus.google.com/+TodLiebeck/posts/gjnmuaDM8sn

Thanks to the guy who took the time to write that ^^

Cheers
[Galaxy Tab S Original Android Development] lucky_515:
can someone plz give me a mirrior??..all links are broken..for the recovery,and for the rom download link..tried on tablet,and the pc
[Galaxy Tab S Original Android Development] Enddo:
The links in the OP work for me. . .
[Galaxy Tab S Original Android Development] lucky_515:
i just tried again..not downloading..the cm recovery just shows bunch of code when clicking the link,reliaze this is the browser trying to open zip instead of download,i gues..but the rom download doesnt download at all,sanme on the device and pc..also tried other links threwout the thread,they just download in seconds,ba download..gues illl try another browser?..do you have the latest lolipop cm file allready downloaded?can you just send it to me,ive got the sm-t700 8.4 wifi galaxy tab S ...

---------- Post added 23rd February 2015 at 12:03 AM ---------- Previous post was 22nd February 2015 at 11:58 PM ----------

thank you!! for the android file host download..this is only download link ive got to work..been searching the thread for while now!!!..works everytime with this host..thanks again now i can finially flash this bad boi
[Galaxy Tab S Original Android Development] eousphoros:
That is not my build so I won't support it fwiw.
[Galaxy Tab S Original Android Development] dknk99:
I agree, I have noticed things similar and when streaming music. I'm thinking that until sammy-sung release their optimized kernel for lollipop, this will be the case. I can't seem to keep a ROM for too long. Currently back on stock kk with Skyhigh kernel, rooted and lots of Sammy stuff removed. Its a pretty smooth setup. I'll be back on lollipop when I get bored with this. (Which probably won't be too long...)