yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Original Android Development] Barracuda77777:
can also confirm, I can only think of one commit related to video that get symlinked when rom is installed will check and report back if this is what broke chromecast mirror.

Edit

I reverted the commit still black screen, will keep trying ?
[Galaxy Tab S Original Android Development] :
Posted this yesterday in the wromg thread - very exhausted... ...obviously...

I have added HighTouchSensitivity and AdaptiveBacklight. I'm still trying to fix the buttons.

The fact, that I thought I had fixed Buttons but not realizing, that they doesn't stay disanled aftr first standby/wakeup cycle made me think...

The fact, that I don't know, if Camera2 is fixed for everone, or just for me - made me think...

I wonder if one of our builds will run for more than 10 hours without crashing. That made me think...

For me the frequency of publishing roms and kernels is to high. I don't understand any longer, who is talking about what build, kernel or combination of these. So I will real slow down. I will leave my builds to me to have time to test, and only will publish a build when publish frequency has cooled down a bit, and if I have tested my changes for my self first. That does not mean that I abdomn the developing for our loved chagall, nor that I stop supporting you here but only, that I will slow down the publishing of my changes.

Cheers, Nvertigo
[Galaxy Tab S Original Android Development] suzook:
I couldnt agree more. I have been running the oct31st build, and see no reason to reflash. EVERYTHING works on this build. Great job, and in all honesty, slow down. Take a break. Get back to basics.
[Galaxy Tab S Original Android Development] jodeltje:
Fully agree. You don't need to keep pooping out a new build everything you fox something. It is confusing for ROM flashers as well.

I'm on 07/11 and Camera works, Netflix works, YouTube works.

The hiccups I got on the last build are gone (by removing ant?).

Never seen a force close, and is running stable for a couple of days.

Smooth sailing overall :)
[Galaxy Tab S Original Android Development] Gilg@mesh:
I would just focus on the MHL if there is no other bigger problem? :D
[Galaxy Tab S Original Android Development] brando56894:
One of the greatest autocorrects ever lol
[Galaxy Tab S Original Android Development] johoja:
I was looking over the picassowifi - and it turns out that MHL audio output is also broken for that device -- the interesting thing though is that it used to work at one point ( i.e before CM 11.0 - M11 ) so that's something..

http://xdaforums.com/showpost.php?p=55837644&postcount=67
[Galaxy Tab S Original Android Development] UpInTheAir:
SkyHigh kernel

When I return home end of week, not long after, I intend to compile a SkyHigh kernel for this specific ROM.

I intend for it to be a basic mirror of the other kernels plus any new source/ramdisk changes needed. Obviously I'll require the assistance of the ROM devs for testing and their input etc.

Once tested and ready, will release seperately in a CM SkyHigh kernel thread.
[Galaxy Tab S Original Android Development] reubenskelly1992:
I say keep the updates coming:)
[Galaxy Tab S Original Android Development] suzook:
OK, good. Are you gonna do it????
[Galaxy Tab S Original Android Development] reubenskelly1992:
No, I'm not the developer smart ass
[Galaxy Tab S Original Android Development] YusSuF15:
The stock batter Dont try this room save ur time pls

أرسلت من LG-D802 بإستخدام تاباتلك
[Galaxy Tab S Original Android Development] :
We belive to have sorted out, what break the "cast screen". But I don't have a chrome cast to test. I have orfered one - it should arrive in 2 or three days. I would like to test before pushing a new build. Therefore I need your help: what is the exact test szenario? To my understanding I need a helper app here from xda; do I need chromecast app (other then for installing chromecast in my wlan)? Can some please post a step by step test scenario? Thanx in advance.
[Galaxy Tab S Original Android Development] reubenskelly1992:
What?
[Galaxy Tab S Original Android Development] Gilg@mesh:
I think he tried to say that the stock rom is better don't try this, LOL
[Galaxy Tab S Original Android Development] jrock60:
http://xdaforums.com/hardware-hacking/chromecast/app-cast-receiver-app-android-t2900726/post56625676
[Galaxy Tab S Original Android Development] reubenskelly1992:
Ah lol. This is much smoother and customisable than stock!!
[Galaxy Tab S Original Android Development] :
Thanx. This one works. Leapcast on my gentoo box and cheapcast on n10 does not.

OK. Streaming youtube to my n10 acting as chromecast. But I can't see n10 in cast screen. So does that means rom's stile broken. Or does that mean I need mirrorenabler and/or chromecast? I'm really willing to fix that, but please give me a step-by-step test scenario...

---------- Post added at 05:28 PM ---------- Previous post was at 05:20 PM ----------

OK. Mirror enanler installed. At this very moment I see my t800mscreen on n10, running apollo in background on t800, sound comes from n10. Can see me typing also on n10 screen. Does this mean you would consider your casting is not working asmfixed???
[Galaxy Tab S Original Android Development] andresv1989:
The way I set it was by first installing chromecast and setting it up with my tv then install mirror enabler and and under where it says "mirror status" click enable then open Chromecast app and under the tab section the option to cast screen should be available. Once you are connected it should mirror your screen but on there last build 11\07 it did not
[Galaxy Tab S Original Android Development] :
I've installed themrecovery flash version of CastReveiver on my Nexus 10.

I was able to stream youtube from t800 to n10.

Them I installed mirrorenabler and ticked Mirror status enable.

I went to Settings/cast screen, saw n10 and was able to cast screen and sound (with apollo) to n10 - the latter even in background. Without installing chromecast.apk - but I haben't had to configure chromcast devicze, cause I used castreveiver on n10

So I think it's fixed, isn't it? I no one came up with an other test suggestion I wil publish build tomorow morning (UTC +1).

Thanks for pointing me to castreceiver - thank you for describimg test scenario.
[Galaxy Tab S Original Android Development] Barracuda77777:
انا ما كنت اعرف انك جربت الغرفة وكانت صغيرة؟

was the room too small for you?
[Galaxy Tab S Original Android Development] YusSuF15:
هههههههههههه

The Rom was fast than Stock

But the problem battery 5hr screen time

Its bad with battery 7900mah

Stock room 7.30 hr screen time

كل مااريد قوله ان التعديل على النظام الاساسي مضيعه للوقت لايوجد افضل من النظام الرسمي .

نحن نوهم انفسنا لا اكثر

أرسلت من LG-D802 بإستخدام تاباتلك
[Galaxy Tab S Original Android Development] Barracuda77777:
Battery usage varies, I got more than one occasion 9+ hours watching movies, which is why I bought the tablet for, if you play games and the CPU and GPU is at max speed then yes battery will not last as long.

so for that alone, it is not fair for you to say this rom is trash and also to warn people not to use it, for everyone his own, for me, if not for CM this tablet would have been collecting dust.
[Galaxy Tab S Original Android Development] reubenskelly1992:
You using greenify and debloated?
[Galaxy Tab S Original Android Development] YusSuF15:
No i just watching youtube no more

Can u take screen shot on battery screen time?

أرسلت من LG-D802 بإستخدام تاباتلك
[Galaxy Tab S Original Android Development] Barracuda77777:
I don't have any screen shots, will do some in the next couple days but here some Nveritgo took:

http://xdaforums.com/showpost.php?p=56414066&postcount=91
[Galaxy Tab S Original Android Development] YusSuF15:
هاذا غريب حقا

لقد قمت بختبار البطاريه مرتين

في اقصى حصلت على 5.30 ساعه

اعتقد ان الشاشه ومشاهده الفديو تقوم بالقضاء على البطاريه بشكل اسرع

على العموم شكرا لك

واسف على الازعاج .

Thank you .

أرسلت من LG-D802 بإستخدام تاباتلك

---------- Post added at 01:52 AM ---------- Previous post was at 01:51 AM ----------

No

أرسلت من LG-D802 بإستخدام تاباتلك
[Galaxy Tab S Original Android Development] reubenskelly1992:
That would be a good start to extend your battery life
[Galaxy Tab S Original Android Development] Barracuda77777:
Can you please edit your post with english translation, so other users can understand what you are saying,

anyhow here is the traslation to YusSuF15 reply:

this is really stange

I tested the battery twice and the most I got was 5 and half hours.

I think watching videos drains the battery more.

thank you very much and sorry for the disturbance,

thank you
[Galaxy Tab S Original Android Development] danny19901:
XDA is English only forum I believe if you don't know English best translate before posting as your question will probably never be solved or you may not gain help everyone who posts different language get told the same thing
[Galaxy Tab S Original Android Development] YusSuF15:
Iam not need any help just shre my test for all

Thank you anyway GoodNight.

أرسلت من LG-D802 بإستخدام تاباتلك
[Galaxy Tab S Original Android Development] maxrdlf95:
Is this good??

LOL
[Galaxy Tab S Original Android Development] DUHAsianSKILLZ:
How much screen time on do you get?
[Galaxy Tab S Original Android Development] maxrdlf95:
2 hours but I downloaded some torrents like 6 GB on the tablet
[Galaxy Tab S Original Android Development] barth2:
That would explain why your android system is using do much battery. Usually the screen is the most power hungry.
[Galaxy Tab S Original Android Development] :
Yeah. Having wifi not only active but having hravy traffic on it takes power - it is the same on my n10 and s3. You can check settings/wlan/advanced there is an option to optimize energy consumption when wifi is active - of course this does not really help on heavy use (if interface sends with 0.xx Watt its has to power the 0.xx Watts), but it helps when wlan is active, but no or nearly no traffic is on.

Disable background scan for location.

An other great battery saver is only use that google syncs that you really need: I use only contacts and calendar (email is completly done in k9, syncing allm30 minutes).

Use apps with dark backrounds (and themes by that mean). Deinstall (system-)apps, you don't use, i.e.: I use nova-launcher, so I deinstall (with titanium) trebuchet. Some apps (like trebuchet) run in background - even if not used.

My 11+ h Display-Time was done without greenify or other battery saver tools. I use bettethatterystats to find battery drainers.

---------- Post added at 08:03 AM ---------- Previous post was at 07:31 AM ----------

1111 build

I've undone the optimizations when ironing out the cast issue. Not included at this build:

biomic otimization

deadline optimization

Don't block flusher on IO

New Features:

High Touch Sensivity (aka Globe Mode; for some mystherical reason it's in Languahe/Input)

Adaptive Backlight (don't know if it has great effect, if you are using autobrightness, but it does no harm when using both of them)

Fixes:

cast screen (thanx to barracuda helping me to find the commits, that brake it; thanx to the user pointing me to castreceiver for making my n10 to a chromecast for testimg)

Disable Buttons when softkeys are active now working

Regressions:

When using Buttons they will flash on standby. At the moment I can either get the disabling when using softkeys to work (staying disabled after standby and reboot) or I can get rid of the flashing. It's some strange interaction with sensorlib [this is settings lights on and imidietly off again and makes the flashing] I had to do further inverstigation.

Still not working:

xbmc

ANT+

MHL

MD5: 711a4eaefb6ff1720dd9364e8258b505

ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-11-20141111-UNOFFICIAL-nvertigo-chagallwifi.zip

Happy flashing.

EDIT: As a side note: I will continue improving this rom.
[Galaxy Tab S Original Android Development] Barracuda77777:
so here is the battery usage that I promised, as I said I get around 9 hours, watching Netflix, with auto brightness on.

cheers :)

by the way I am not running any battery saving apps.
[Galaxy Tab S Original Android Development] ares.:
Can i ask the quick question about the capacitive buttons

No matter i disable it or not or make the 'illusion disable'

the light of capacitive buttons keep flashing when i turn the screen off

I'm using the 1111 build

Thanks so much
[Galaxy Tab S Original Android Development] :
Barracuda build: read OP; flash disable keys kernel.

Nvertigo build: Read #5 or announcment: no flashing when using softkeys - at the moment flashing when using buttons. I'm working on a workaround - looks promissing, probably coming later today.
[Galaxy Tab S Original Android Development] :
Woraround for flashing Buttons

This is only tested for cm-11.0-20141111-UNOFFICIAL-nvertigo:

When using softkeys buttons are disabled, stay disabled and there is no flashing.

Flashing accurs only (again: this is for 1111 build from nvertigo) when using Buttons. To reduce this flashing to the minimum follow step-by-step:

Go to settings/Buttons

Set everything to your millage (background light disabled ormenabled, duration of background light [of course only when enabled]). Once set don't touch it again, especially don't switch between Buttons and Softkeys!

Download and unzip attached file.

Copy power.exynos5.so (it's from sammy NH1; will be in the next build) to /system/vendor/lib/hw/ with root-enabled filemanager of your choice.

Set permissions of power.exynos5.so to 0644 (-rw-r--r-- for that matter).

reboot to recovery

In recovery: wipe cache (you can also wipe dalvik-cache; will nor hurt - but it's important to wipe cache).

reboot to system.

Now the Buttons background lights will only flash on lock screen and wake up screen. If you change the Buttons settings to softkeys everything will ne fine - if you change back it's important that you change the background light enable/disable once (means: if backgroundlight is enabled switch it off and on again; if backgroundlight is disbled switch it on and off again) and redo steps 6, 7 and 8.

The attached zip contains full path so you can also open a shell and (this is unzip and copy combined):

su
cd /
mount -o remount,rw /system
unzip </patch/to/downloaded/>power-exynos5-so.zip
mount -o remount,ro /system
[Galaxy Tab S Original Android Development] bxmoney181:
i can't get nvert's build 1111 to get passed bootanimation.

i did a clean flash with twrp 7.1.1.
[Galaxy Tab S Original Android Development] andresv1989:
Has anyone been able to get hulu to work?
[Galaxy Tab S Original Android Development] :
Workatound does NOT work

When taking up tab s this morning flashing was back. :( So this "Workaround" is only working a couple of hours... Drives me crazy... :(

---------- Post added at 07:49 AM ---------- Previous post was at 07:35 AM ----------

That's strange. It was working here with dirty flash (wiped only /system, cache and dalvik-caache), I've tested rom for many hours befor publishing. Any messsges while flashing? You refer to the circling arrow as boot-animation aren't you? Tried factory-reset (wipe data) and "fix permissions" from recovery? What rom do you come from?

Can anyone confirm that 20141111-UNOFFICIAL-nvertigo boots up normal?
[Galaxy Tab S Original Android Development] bxmoney181:
No messages. Yes, I'm referring to the circling arrow. I will try that and see if that fixes it. I'm coming from stock based NJ5 rom, Basic Rom to be exact.
[Galaxy Tab S Original Android Development] Crimsonthunder:
For me it boots fine. No problems.
[Galaxy Tab S Original Android Development] bxmoney181:
Still can't get passed the boot animation. ?
[Galaxy Tab S Original Android Development] suzook:
I am using your 10/31 build, and no flashing buttons. Any idea what's different???
[Galaxy Tab S Original Android Development] ares.:
i can confirm that 20141111-UNOFFICIAL-nvertigo boots up normal

and after i use your fix for bottom flashing, it is help, but after reboot, the flashing is back, need to wipe again
[Galaxy Tab S Original Android Development] Anthony820:
Good. Good in that I had the same problem last night when I finally decided to try this. CM logo was running for a solid 10 minutes. Tried wiping things - although I did a very clean install - and still nothing. After restoring non of my apps could write any data, but I reckon that's a twrp issue.
[Galaxy Tab S Original Android Development] :
No messages at all??? Nothing? Twrp installation broken.

---------- Post added at 02:55 PM ---------- Previous post was at 02:53 PM ----------

Yes. I know that works without flashing for button users - but disabling Buttons and using softkeys does only work til first lock/unlock cycle.

---------- Post added at 03:26 PM ---------- Previous post was at 02:55 PM ----------

Ok. Finally I understood the problem with softkey/Buttons:

We need a file in /sys/class/sec/sec_touchkeys/keypad_enable. At the moment I use /sys/class/input/input8/enable - but this is always set to enabled, when wakeup (after lockscreen) accurs. This is behind my abbilities. Sorry. But if someone with exporience in hacking kernelmdrivers and sysfs interfaces is around help would be very welcome!!! The driber in questionmis dribers/input/keyboard/tc300k.c.

I really need help on this.

For next build I will fall back to the solution where using Buttons is ok without flashing. I will providema seperate kernel without Buttons (like barracuda did for his builds) to completly disable Buttons and usemonly softkeys.
[Galaxy Tab S Original Android Development] ares.:
i dunno is it work or cannot do like that

is it possible just disable the lights under the bottom, i mean don't give the lights power

BTW Really really thanks for making this rom
[Galaxy Tab S Original Android Development] Gilg@mesh:
flash this

http://charlesingo.mine.nu/ftp/barracuda/no_capacitive_buttons_chagallwifi_CM_8_11_2014.zip
[Galaxy Tab S Original Android Development] reubenskelly1992:
Gone back to stock mainly for the multi windows features. Enjoyed using this great rom for a couple weeks:)
[Galaxy Tab S Original Android Development] hurray:
Hmm, a few days ago [MENTION=4193974]Barracuda77777[/MENTION] has written a multi window workaround for CM11 which works fine for me. But I can't find the post anymore...
[Galaxy Tab S Original Android Development] danny19901:
[MENTION=4193974]Barracuda77777[/MENTION] I have T705 and I know I'm going off topic but I'm getting a build server soon and was wondering as T705 doesn't have a proper CM11 but T700 ROM works fine would it be possible to use T700 kernel and sources to build with also I was thinking making liquid smooth or something if that would work and it if it works I could build for T800 also but as I don't have it I can't test

TAPATALKED WITH MY TAB S 8.4

My Z3 app Ports to all devices
[Galaxy Tab S Original Android Development] Barracuda77777:
you can certainly try, just follow their build guidelines and make the changes needed to build, by the way I sent you you a pm.
[Galaxy Tab S Original Android Development] danny19901:
Ok hopefully I should have a build server sometime next week or possibly tomorrow and will try build other roms from sources also messaged you back and thanks very much

Just been looking and CM12 is on one+one also seen a few gits of cm12 branch in your github is this something your working on ?

TAPATALKED WITH MY TAB S 8.4

My Z3 app Ports to all devices
[Galaxy Tab S Original Android Development] Sony_Black:
works really good, are u gonna make this ROM work good or will you work more on an cm12?
[Galaxy Tab S Original Android Development] Barracuda77777:
yes, this is just preparing, I don't think there will be a cm12 rom anytime soon.
[Galaxy Tab S Original Android Development] :
Build 1115

Build 1115

This is a kind of stable release. I incorperated everything what proved to be stable or working. No new features, one bugfix. Mainly I'vemgone back to the congiguration where the capacitive buttons aren't flashing when active - to avoid reactivating of capacitive buttuns after first lock/unlock cycle when using softkeys (aka,on-screen-keys) flash this kernel. REMEMBER to activate softkeys BEFORE reboot to recovery and flashing kernel without tc300k driver!

To get back the capacitive keys flash this one.

Capacitve keys work as they should: they don't flash on standby - backlight is configurable.

Bugfix:

increased dalvik.vm.heapminfree from 512Kb to 2Mb for our large display

MD5: e32f3dde7948373b4061003afd535951

ROM: cm-11-20141115-UNOFFICIAL-nvertigo-chagallwifi.zip

Kernel without capacitive keys driver: chagall-20141115-wo-tc300k.zip

Original kernel from 1115 rom with capacitive keys driver: chagall-20141115.zip

You find all of the above as always at the end of #5.

Xbmc, mhl and ant+ are still broken. At the moment I've stoped investigating here. Time will show.

I'm still not working on cm12. I've tried a build with new blobs and aosp import of device tree for my manta: it's not booting. As I said before: I will start t800 cm12 build when M1 or M2 for cm12 is out. So here again: time will show.

Currently I try to set up a cm11 build where ext4 is completly replaced by f2fs - if this shows to be possible and usefull (aka as stable as ext4 but considerable faster) I will share of course.

Today I tried the cwm based recoverynfrommthe build I published her (in preparation of f2fs) if anyone is interested in testing I can share a link.
[Galaxy Tab S Original Android Development] tahlsr:
Thank you for a fantastic ROM. Have been using it for a couple of days now and it's really smooth. Does anyone out there use a wired xbox 360 controller with this ROM and have it working? Any tips? I believe I have the proper cable and was hoping it was just going to be plug and play but it doesn't seem to be. Thanks for any tips.
[Galaxy Tab S Original Android Development] Robin M:
I'm a little confused by "capacitive keys". When you say "capacitive keys" , you are referring to the hardware capacitive buttons, not the on-screen capacitive buttons that you can turn on in settings. Is that correct?

Also, when you say "backlight is configurable", where do you configure it? I looked in settings > buttons and could not find any way to configure the back light on the hardware buttons there. (I am using the latest build 1115 and standard kernel , not the alternative kernel.)

Thanks for uploading this latest stable build.
[Galaxy Tab S Original Android Development] bxmoney181:
Sorry. I should have been clearer. There were no abnormal messages in twrp. I was able to flash 1115 perfectly fine though. I still have no clue why 1111 was not booting for me, but 1115 boots fine and is running smoothly.

---------- Post added at 08:40 PM ---------- Previous post was at 08:37 PM ----------

I can confirm hulu works perfectly fine on nvert's 1115 build.
[Galaxy Tab S Original Android Development] UpInTheAir:
Hi Devs.

As you are aware that my spare time for developing is extremely limited these days. As I've just received my new device (Samsung Galaxy Note Edge SM-N915S Exynos 5433), I will be spending that free time to develop for that unique device. This ultimately means; without your device model in hand, I don't have time to collaborate and build a bug free SkyHigh kernel for you. Without having device model, it's too time consuming and difficult. Sorry.

BUT !!

Due to the above stated reasons, you have my permission to use my kernel: built in-line or outside of ROM, packaged with or without ROM, and also to make any source changes needed for effective use in this project. :)

All I ask please is that a small credit and link to my original work in your OP. ;)

Those users wishing to see another SkyHigh TW kernel will see future update, but only if new source is released or I bother to add new feature. It's stable, fast and battery friendly, with plenty of features/options for the tweakers ;)

Best of luck with your project.

Cheers

UITA