yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Android Development] lionheartk:
Chover no molhado fits perfectly and we use it here too haha.

Kudos for the francesinha tip, it was really awesome.

Soon, the old and useless 5.1.1 sex build will be up, stay tuned. :p
[Galaxy Tab S Android Development] Falcon204:
New release works great! No problems but only noticed a lower volume on this new Rom but fixed it with a volume booster that worked better than expected.

Here is the link in the playstore if anyone else is having low volume

https://play.google.com/store/apps/details?id=mobi.omegacentauri.SpeakerBoost

Sent from my SM-T800
[Galaxy Tab S Android Development] lionheartk:
Now that we have the exact changelogs, we can pinpoint the probable culprits:

*Ethan Chen - audio: Convert libaudioamp to audio_amplifier HAL

*Ethan Chen - hal: Convert libaudioamp to audio_amplifier HAL

Don't see a reason to revert it tho...
[Galaxy Tab S Android Development] airmaxx23:
Just curious if anythings been figured out as far as why I have no lag plugged into a charger but have lag when unplugged.
[Galaxy Tab S Android Development] lionheartk:
Seems that only you have this problem, at least I asked and nobody else confirmed having it? I don't. Strange.
[Galaxy Tab S Android Development] Brazooka:
You can add me to the count as well. Never had this problem.
[Galaxy Tab S Android Development] Zootopia:
Good to hear about the francesinha. :)

Didn't know "chover no molhado" was also used in Brasil. [emoji1]

Btw, the sex build is the best for me to date, stability, responsive and very fluid!

Using latest slimzero gapps, no issues.

Great work, thanks! [emoji106] [emoji108]
[Galaxy Tab S Android Development] Falcon204:
I was playing a MLB game just a while ago and the tablet is super hot near the Samsung logo. First time I ever noticed a over heat issue ?

Sent from my SM-T800
[Galaxy Tab S Android Development] diegocr:
Look temperature with cpu-z or another app, in mine I have seen 94 degrees centigrades :(

Now I have max cpu speed at 1500.
[Galaxy Tab S Android Development] rookie12:
I am having the same problem in cm 12.1 on the T700 so if I lower the max CPU it will not get so hot anymore?
[Galaxy Tab S Android Development] diegocr:
In theory less hot, but at start when optimized apps cpu is at stock speeds.
[Galaxy Tab S Android Development] Zadeis:
I also have this problem and it seems like we are in the minority. It isn't anything I am installing since I only installed CM with no gapps or anything of the like. Just flashed it, went through the setup, and I experience this. I tried explaining this problem way back in april and upon trying the most recent build it does the same. That also goes for any CM based Lollipop rom. The old Kit Kat CM rom doesn't have this problem. The lag isn't super noticeable but it's definitely there. It also isn't this particular tab since I exchanged one tablet for my current one (for a different reason both a T800) testing both on this rom and both had this problem.

The lag is very quick but makes pretty much any animation choppy for the first quarter to half a second if you keep interacting with the tablet it is fine until you let the hardware clock down due to little activity happening. It's not a CPU problem since you can set the cpu to 1ghz and it does the same thing. This means it is a GPU problem though I don't have the means of "forcing" the GPU clock above what it idles at to test this theory.
[Galaxy Tab S Android Development] jodvova:
Oh guys, forget about resolving this kind of issues.

The main dev for this tablet has left the building! It's time to jump the ship.
[Galaxy Tab S Android Development] lionheartk:
Zadeis, that's strange. I asked here twice about this and the majority of users don't have this bug. Interesting that you have it on both tablets. Since you said "That also goes for any CM based Lollipop rom." then I'm afraid we'll have to wait untill the CM12 team fixes this... check on their bugtracker if anyone reported it on other devices.

jodvova,

The main dev is busy with his work currently, he explained it multiple times in the thread. I'm filling in meanwhile doing what I can to provide builds with the CM12 commits to keep you guys on the bleeding edge.

We do what we can, in our spare time, to provide you guys with this ROM free of charge. You are free to use any other ROM that pleases you, coming here to say this kind of things Isn't doing any good to anyone.

This is especially insulting to whoever donates his/her time to make this ROM happen and keep it updated and running. What I can tell you is, instead of whining and mocking just make a better ROM then. Or hire a team of developers to fix the issue and kindly post the patch here so I can commit it to the ROM. This would make you and whoever has this bug happy.

If you can't or won't, then at least don't troll. We appreciate the bug reports and will do what we can, but there is a limit to everything.
[Galaxy Tab S Android Development] Zadeis:
Now when I say "any CM based ROM" I mean any CM based ROM for the T800 like blisspop not other devices. I just want to be make sure that is understood.
[Galaxy Tab S Android Development] diegocr:
Add wifi symlinks to updater-script without "repackrom"

On device/samsung/chagallwifi/

Add at the end of # Wifi section on BoardConfig.mk

TARGET_RELEASETOOL_OTA_FROM_TARGET_SCRIPT := device/samsung/chagallwifi/releasetools/ota_from_target_files

Create releasetools directory and add extra_script (without blank lines)

ui_print("");
ui_print("Making symlinks for Sammys wifi driver mimik and for libOpenCL.so.1.1");
ui_print("");
mount("ext4", "EMMC", "/dev/block/platform/dw_mmc.0/by-name/SYSTEM", "/system", "");
symlink("/system/etc/wifi/bcmdhd_apsta.bin", "/system/etc/wifi/bcmdhd_apsta.bin_4354_a1");
symlink("/system/etc/wifi/bcmdhd_apsta.bin_a0", "/system/etc/wifi/bcmdhd_apsta.bin_4354_a0");
symlink("/system/etc/wifi/bcmdhd_ibss.bin", "/system/etc/wifi/bcmdhd_ibss.bin_4354_a1");
symlink("/system/etc/wifi/bcmdhd_ibss.bin_a0", "/system/etc/wifi/bcmdhd_ibss.bin_4354_a0");
symlink("/system/etc/wifi/bcmdhd_mfg.bin", "/system/etc/wifi/bcmdhd_mfg.bin_4354_a1");
symlink("/system/etc/wifi/bcmdhd_mfg.bin_a0", "/system/etc/wifi/bcmdhd_mfg.bin_4354_a0");
symlink("/system/etc/wifi/bcmdhd_sta.bin", "/system/etc/wifi/bcmdhd_sta.bin_4354_a1");
symlink("/system/etc/wifi/bcmdhd_sta.bin_a0", "/system/etc/wifi/bcmdhd_sta.bin_4354_a0");
symlink("/vendor/lib/egl/libGLES_mali.so", "/system/vendor/lib/libOpenCL.so.1.1");
unmount("/system");

and ota_from_target_files

#!/usr/bin/env python
#
# Copyright (C) 2008 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

import sys

if sys.hexversion < 0x02040000:
print >> sys.stderr, "Python 2.4 or newer is required."
sys.exit(1)

import imp
import os

RELEASETOOLS = os.path.realpath(os.path.join(os.path.dirname(__file__), "..", "..", "..", "..", "build", "tools", "releasetools"))
sys.path.append(RELEASETOOLS)

imp.load_source("ota", os.path.join(RELEASETOOLS, "ota_from_target_files"))
import ota
ota.OPTIONS.extra_script = os.path.realpath(os.path.join(os.path.dirname(__file__), 'extra_script'))

if __name__ == '__main__':
try:
ota.main(sys.argv[1:])
except common.ExternalError, e:
print
print " ERROR: %s" % (e,)
print
sys.exit(1)

SlimLP tested, in CM should work

[MENTION=4405529]nvertigo67[/MENTION] & [MENTION=1409248]lionheartk[/MENTION] no more repackrom ;)
[Galaxy Tab S Android Development] airmaxx23:
Same thing here, any CM based ROM had the same lag.
[Galaxy Tab S Android Development] lionheartk:
Thanks diegocr! Will test it in the next build.

About the lag thing, maybe you guys could try and peek at the logs to see if it spits any error while it lags? And then see if the error disappears while plugged?
[Galaxy Tab S Android Development] Bushcrafter:
+1 :good::good::good::good::good:
[Galaxy Tab S Android Development] diegocr:
Tablets with lag what bootloader version have?

Can read it with Phone INFO ★Samsung★
[Galaxy Tab S Android Development] Falcon204:
I wonder if those that have lag are getting root back by flashing... I know for me I didn't flash to get root back all I did was goto about in settings then clicked on the build area 6 times which gave me developer options then from there I clicked enable root on the list of options, once that was done I reinstalled supersu from the playstore then launched it and picked normal install and that's it after restart. I had no lag at all on the tablet, only thing I had which alarmed me was the extreme heat I was experiencing while playing games or watching a movie.

Sent from my SM-T800
[Galaxy Tab S Android Development] Zadeis:
Since I'm not 100% sure... Where do I find this info?
[Galaxy Tab S Android Development] diegocr:
search on google play Phone INFO ★Samsung★ or cpu-z
[Galaxy Tab S Android Development] Zadeis:
The bootloader version I have is T800XXU1BOE2
[Galaxy Tab S Android Development] deadman96385:
I don't usually like to post other roms in a rom specific thread but because this community is small hopefully you will be ok with it lol. I know i said i would not build LiquidSmooth for the other tab s variants but i at least wanted to get them setup and ready so its easy for someone that has the device to build them or if no one does i can blind build them from time to time

http://xdaforums.com/galaxy-tab-s/general/liquidsmooth-t705-t800-t805-testing-t3135196
[Galaxy Tab S Android Development] diegocr:
5.0.2 bootloader. no problem

I have T800XXU1BOCC

---------- Post added at 06:53 AM ---------- Previous post was at 06:51 AM ----------

Used the same kernel sources for chagallwifi and klimtwifi ?

I have read at your post that t800 wont boot
[Galaxy Tab S Android Development] diegocr:
Bye bye media patches :good:

On device/samsung/chagallwifi/ edit device.mk and change this lines

device/samsung/chagallwifi/media/media_codecs_ffmpeg.xml:system/etc/media_codecs_ffmpeg.xml \
device/samsung/chagallwifi/media/media_codecs_google_video.xml:system/etc/media_codecs_google_video.xml \

Create media directory and copy patched media_codecs_ffmpeg.xml and media_codecs_google_video.xml
[Galaxy Tab S Android Development] diegocr:
dmesg while antutu cpu test, Failed to soft-reset GPU :crying:

<6>[ 3376.190233] [B0: kworker/0:0: 12175] thermal_sys: [TMU_POLLING] polling_delay=300ms, temperature=91
<6>[ 3376.290242] [B0: kworker/0:0: 12175] thermal_sys: [TMU_POLLING] polling_delay=300ms, temperature=92
<3>[ 3376.388722] [B2: mali-renderer: 18191] Failed to soft-reset GPU (timed out after 500 ms), now attempting a hard reset
<3>[ 3376.398314] [B2: mali-renderer: 18191]
<6>[ 3376.400316] [B0: kworker/0:0: 12175] thermal_sys: [TMU_POLLING] polling_delay=300ms, temperature=90
<6>[ 3376.417308] [B0: kworker/0:0: 12175] thermal_sys: [TMU_POLLING] polling_delay=300ms, temperature=91
<6>[ 3376.417367] [B0: kworker/0:0: 12175] [TMU-IRQ] IRQ mode=2
<6>[ 3376.471052] [B0: kworker/0:0: 12175] thermal_sys: [TMU_POLLING] polling_delay=300ms, temperature=90
<6>[ 3376.471143] [B0: kworker/0:0: 12175] [TMU-IRQ] IRQ mode=2
<6>[ 3376.524705] [B0: kworker/0:0: 12175] thermal_sys: [TMU_POLLING] polling_delay=300ms, temperature=87
<6>[ 3376.524817] [B0: kworker/0:0: 12175] [TMU] COOLING START: temp_level=75, clip_max=1800000
<6>[ 3376.525132] [B0: kworker/0:0: 12175] [TMU-IRQ] IRQ mode=1
<6>[ 3376.787072] [B0: kworker/0:0: 12175] tmu temperature state 6 to 5
<6>[ 3376.787150] [B0: kworker/0:0: 12175] thermal_sys: [TMU_POLLING] polling_delay=300ms, temperature=80
<6>[ 3376.787235] [B0: kworker/0:0: 12175] [TMU-IRQ] IRQ mode=1
<6>[ 3376.834792] [B0: kworker/0:0: 12175] thermal_sys: [TMU_POLLING] polling_delay=300ms, temperature=82
<6>[ 3376.834858] [B0: kworker/0:0: 12175] [TMU-IRQ] IRQ mode=1
<6>[ 3376.983911] [B0: kworker/0:0: 12175] tmu temperature state 5 to 6
<6>[ 3376.983968] [B0: kworker/0:0: 12175] thermal_sys: [TMU_POLLING] polling_delay=300ms, temperature=91
<6>[ 3376.984032] [B0: kworker/0:0: 12175] [TMU] COOLING START: temp_level=90, clip_max=1700000
<6>[ 3376.984829] [B0: kworker/0:0: 12175] [TMU-IRQ] IRQ mode=2
<6>[ 3377.001795] [B0: kworker/0:0: 12175] thermal_sys: [TMU_POLLING] polling_delay=300ms, temperature=91
<6>[ 3377.001863] [B0: kworker/0:0: 12175] [TMU-IRQ] IRQ mode=2
[Galaxy Tab S Android Development] lionheartk:
diegocr, I didnt test yet but will those fixes you posted be gone when doing the source sync?
[Galaxy Tab S Android Development] diegocr:
I think the local changes are kept, I have not checked because I created a own repository for SlimLP
[Galaxy Tab S Android Development] Zootopia:
Let me second that please. [emoji2]
[Galaxy Tab S Android Development] Bushcrafter:
Just downloaded your latest build and taking it for a test drive as I type this. So far so good!:good:

P.S. How do you change the lock screen wallpaper in the setting menu?
[Galaxy Tab S Android Development] :
You have to wait. Cm has no sepperate setting for lockscreen wallpaper for now - it is set together with desktop wallpaper.

Sometimes I regret I havn't sticked to my plan to start on cm12 not before M2 for supported devices!

cm12 is upstream under heavy development. Perhaps a 10 % of the features of cm11 has been transfered to cm12. If you want a complete cm go for my cm11 build. If you want more features in a L build go for bliss.

In my personal oppinion I love the way the cm-team is porting: slow but solid. For my milage they could be even slower, if that would avoid breaking the builds some time.... But thats my oppinion - yours may varry.
[Galaxy Tab S Android Development] :
IMPORTANT NOTICE to crossflashers

First of all: Sorry for all non-"T800 16gb owners". I'm really sorry for not fullfilling your needs, expectations and dreams. But as said and explained so many times: I will only build for chagallwifi. I want to flash a zip before publishing to community. I know other developers have a different approach and I really respect and appriciate those devs. But I want to do a minimal testing of quality. My build - my decission.

I'm always inviting people to help developing and/or cherry-pick from my work to get a build up.

That all said: I receive quite some pms about flashing chagallwifi roms (yeah, even from other roms for other devices, that does not even begin with chagall... ...funny...) to chagalllte. The flashing has entirely changed on L. When on K the flashing of a rom was basicly a recusive copy of /system, now there is a large data block that gets dumped to the system partion. I've not examined this in detail, 'cause I'm still more than busy with ironing out issues on cm12 build for chegallwifi. So I don't know why the crossflashing fails, nor if there is a simple way of doing the trick.

Again, I feel sorry for everyone with an device I do not support, but that's the way it is:

I build only for chagallwifi - and I try my best to deliver a high quality port on this!

I will try my best (as time permits) to support others in making their own builds (whatever device, mod or whatever)

I will try my best (as time permits) to support the users of this rom.

That's it - no more, no less.

Sorry and thanx for your understanding, NVertigo
[Galaxy Tab S Android Development] Bushcrafter:
Thanks for your reply to my question. The reason I asked the question was that I downloaded a couple of themes for cm 12 and in the process of of using them my lock screen wallpaper has changed. I guess that from your reply that there is no way of changing it at this moment without using a theme apk.
[Galaxy Tab S Android Development] Kennay:
Well i noticed they added lockscreen wallpaper to the latest nightly a few days ago, so i guess maybe it will make its way into these builds as well soonish?
[Galaxy Tab S Android Development] Bushcrafter:
+1 :good:
[Galaxy Tab S Android Development] lionheartk:
As promised, my first Tuesday build is live!

Contains all the CM12 source commits up to 1 hour ish ago, and all commits Nvertigo may have spoke of on this thread between my last build and this one.

cm-12-20150127-UNOFFICIAL-lionheartk-chagallwifi.zip 233.7 MB

cm-12-20150127-UNOFFICIAL-lionheartk-chagallwifi.zip.md5sum 144 B

Dirty flashed on my T800 and working for me. Next build on Friday!

EDIT: Take a look at the theme option, seems you can change the lockscreen wallpaper, boot animation and whatnot by unchecking the Use system Default option. Didn't have time to test yet, please report if it does work!

Have fun!
[Galaxy Tab S Android Development] Bushcrafter:
Thanks for all your hard work lionheartk! Without you and nvertigo67, all of newbs like me would be out of luck!:cyclops:
[Galaxy Tab S Android Development] lionheartk:
You are all welcome, credit goes all to nvertigo tho! :D
[Galaxy Tab S Android Development] Bushcrafter:
Yep works like a charm! Byebye crappy lock screen wallpapers! :good:

---------- Post added at 12:23 PM ---------- Previous post was at 11:59 AM ----------

@lionheartk Is the cm version # suppose to change with your new build in the about tablet section? Mine still says 0126.:confused:
[Galaxy Tab S Android Development] lionheartk:
It follows whatever is on the CM 12 repo I suppose...
[Galaxy Tab S Android Development] :
The version string is composed of several parts. One part is the date. I f the script that generates run on 0126 it will be 0126. For publishing I always make "clean builds". That means:

time (make clean && make clobber && breakfast chagallwifi && brunch chagallwifi) >make.log 2>&1

Of course command one and three are redunfant to two and four - but I'm paranoid. And ya know: Beeing paranoid does not mean they(*) are not behind you... ;)

(small ugly build-gremmlins fed after midnight)

BTW: I fixed the gps selinux issues (will update git tomorrow) - init.d still open, but I'm on my way. We get closer...

BTW2: Thank you very much for building - perhaps someone can help me out in english phrases: how do we call this builds? I was thinking of bi-weeklies - but that would mean a build every two weeks, wouldn't it? OK, Im getting giddy and OT - have to send myself to bed.

Good Night, NVertigo
[Galaxy Tab S Android Development] lionheartk:
Ahh I'll try and use your command for now on, thanks!

Haha I don't know what to call it either. Maybe twice-a-week builds? LOL!
[Galaxy Tab S Android Development] barth2:
^^^ confusingly, biweekly could mean twice a week or every two weeks, but usually it's the latter. For example, if your boss tells you he'll pay you biweekly it probably means you'll get a check every two weeks, not twice a week :)

You could say semi weekly, which I think most people will understand as twice a week.

More confusingly, bi and semi may also used interchangeably, so biannual and semi annual could mean the same thing, twice a year.

Also, each industry makes up its own convention. If a magazine says it publishes bimonthly it probably means every two months. If your bank says your mortgage is due bimonthly it probably means twice a month. Not to be confused with biweekly which is every two weeks (unless it's twice a week :)
[Galaxy Tab S Android Development] Bushcrafter:
Lol!!!!:silly:
[Galaxy Tab S Android Development] armyms25:
i was on Barracuda's CM and there was the option to turn on the on screen buttons. I flashed Lionheart's CM yesterday, maybe im just having a stupid moment. If i am than i apoligize for the dumb question. is there no option in your rom to turn on the on screen buttons?
[Galaxy Tab S Android Development] :
Oh, man, wonderful explanation! Like it so much to learn about English language. You all have realized I'm not a native English speaker/writer. And this posting really tought my something from real live. Thanx.
[Galaxy Tab S Android Development] :
I don't support disabling of capacitive buttons, 'cause it is not possible (remember: [MENTION=4193974]Barracuda77777[/MENTION] has disabled capacitive buttons alltogether by eliminating the driver from the kernel, which lead to some side effects). Therefor I don't support onscreen navbar. Wasn't there on my cm11 builds either. As soon as disabling capacitive buttons is possible I will put back onscreen navbar.

You can help: http://xdaforums.com/galaxy-tab-s/h...-t800-t700-t3002774/post58172081#post58172081
[Galaxy Tab S Android Development] diegocr:
-10 degrees temperature all trigger levels ,max cpu temp 90º :o

<6>[ 735.822913] [B0: kworker/0:0: 4] gpu temperature state 0 to 2
<4>[ 735.823023] [B0: kworker/0:0: 4] [G3D] GPU_THROTTLING_90_95
<4>[ 735.823114] [B0: kworker/0:0: 4] [G3D] Lock max clk: 533
<6>[ 735.823373] [B0: kworker/0:0: 4] thermal_sys: [TMU_POLLING] polling_delay=300ms, temperature=90
<6>[ 735.823514] [B0: kworker/0:0: 4] [TMU] COOLING START: temp_level=90, clip_max=600000
<6>[ 735.922844] [L0: kworker/0:0: 4] gpu temperature state 2 to 0
<4>[ 735.922909] [L0: kworker/0:0: 4] [G3D] Unlock max clk
<6>[ 735.923093] [L0: kworker/0:0: 4] thermal_sys: [TMU_POLLING] polling_delay=300ms, temperature=89
<6>[ 735.923167] [L0: kworker/0:0: 4] [TMU] COOLING START: temp_level=85, clip_max=1200000
<6>[ 736.022833] [B0: kworker/0:0: 4] gpu temperature state 0 to 2
<4>[ 736.022896] [B0: kworker/0:0: 4] [G3D] GPU_THROTTLING_90_95
[Galaxy Tab S Android Development] airmaxx23:
I have the same bootloader as you and have lag.
[Galaxy Tab S Android Development] Kenokin:
Hi everybody! Kill me if I'm wrong but I couldn't find an solution for my issue in this topic.: I have SM-T800 unit with NVertigo rom on board. Since first install every time when i want to dirty flash of new build my tablet stucks on samsung logo during boot. Only full wipie do the job. It is working but restoring apps and settings is painful and long lasting.

Can anybody help me with some clues what I'm doing wrong?

I'm open for any suggestions - maybe not necessarily "Use search option you lazy bastard! ?

Wysłane z mojego SM-T800 przy użyciu Tapatalka
[Galaxy Tab S Android Development] diegocr:
What recovery have ?
[Galaxy Tab S Android Development] Zadeis:
I don't think the bootloader is the culprit then. Which is why I would like to look into the GPU somehow since it seems the maybe the GPU is being more conservative while on battery compared to while on the charger.
[Galaxy Tab S Android Development] jodeltje:
I assume you guys already looked at the differences in 'minimum processor clockspeed' between charging and not-charging? Change the minclockspeed to 400, is there still lag?

(Sorry, if what I said was stupid.. Not actually on this ROM)
[Galaxy Tab S Android Development] diegocr:
On SLimLP with modified kernel (-10º temp triggers levels) CPU-Z read

Discharging

CPU 200 MHz GPU change 24 -100 MHz

Charging

CPU 200 MHz GPU always 100 MHz
[Galaxy Tab S Android Development] lionheartk:
So the lag is coming from the GPU "waking up" it seems. What's weird is, only a minority is experiencing the problem.
[Galaxy Tab S Android Development] Kenokin:
TWRP 2.8.6.2
[Galaxy Tab S Android Development] Bushcrafter:
What's weird is, only a minority is experiencing the problem. +1 Seems very odd to me too.:confused:
[Galaxy Tab S Android Development] Zadeis:
Are the GPU clock speeds that are being reported the same speeds that would occur on the stock touchwiz rom?
[Galaxy Tab S Android Development] diegocr:
Errors in dmesg when is laggy?

adb shell dmesg > lag.txt
[Galaxy Tab S Android Development] Zadeis:
I can check later tonight when I am home.
[Galaxy Tab S Android Development] jrock60:
For anyone experiencing video audio sync issues when on Bluetooth and wifi with streaming videos I have found a solution. The first thing as mentioned earlier in this thread is to use 5hz wifi band which fixes the video to play smoothly but there are still audio sync issues by like half a second. Using bsplayer fixes the sync problem. This was my only issue with the rom up till now and this solution completely fixes it.