yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Android Development] :
Hearthstone, Blizzard, Unity

I'm receiving pms since 2 days, indicating that the updates (0315 as well as 0316) on hearthstone break the game on chagallwifi cm-12.1 (at least one user was on offficial cm-12.1, three otners were on unofficial cm-12.1 build). 4.1.10956 is the last version working on chagallwifi cm-12.1. I recommend keeping a backup of 4.1.10956 to have a chance to downgrade, if you accidently update through playstore.

At least one user from this thread has requested support on the issue (that 4xMSSA is mandatory to run this game at all on our devices) at blizzard. This request was completely ignored, as well as my own request directly to unity. Obviously both companies are not interested in solving this issue - in deed they are not interessted in answering at all!(I wouldn't have any problem, if unity3d or blizzard would tell us, that source build roms are not supported, but no answer at all is an answer on its own... :( )

That being said, I decided to recommend hearthstone 4.1.10956.

I want to kindly ask all users of games using unity, to report their issues directly to the vendors.

BTW: since AngryBirds2 (which is using unity, too) works like a charme, we can consider solving the issues in the app is possible.
[Galaxy Tab S Android Development] Richard_10:
http://www.xda-developers.com/xda-external-link/cyanogenmod-fixes-the-black-screen-chromecast-bug/

Edit: it didn't solve my issue with screen cast. I tried casting my screen but after aproximatly 4 minutes the tabs froze again and I had to hard reboot it. It's really annoying. By the way I clean flashed the last official nightly thids time.

If anybody can reproduce the experiment to check if anybody else have the problem besides me, that would be nice , thank you

I should mention that I have xposed 80 installed (only ads removing modules like "minminguard")

Envoyé de mon SM-T800 en utilisant Tapatalk
[Galaxy Tab S Android Development] GoldExperience:
I am without my tab at the moment so I don't know of this issue with Hearthstone. Is the pink screen problem?

Last update made the game unplayable on all Android devices, Blizzard announced that they are working on a fix, meanwhile clearing the app data or reinstalling the game should fix it.
[Galaxy Tab S Android Development] :
I was told about black screen and crash. The logcats I've seen, have the egl error, we have without 4xMSAA.

According to Blizzard the 0316 update should have fixed the broken (on all devices) 0315 build.
[Galaxy Tab S Android Development] :
Your installation is NOT! cm-12.1 any more: xposed replaces system files, which are vital parts of the rom. After installing xposed you have something new, but no cm-12.1 any longer.

As stated many times: if you install xposed and everything is working, you are fine. Before reporting an issue, do a clean install with only gapps and the apk in question installed. Reports without logs are impossible to debug. (see posting #3).

EDIT:

Added the following to OP:

On Xposed

Xposed is not supported in this thread: xposed changes systemfiles, so the resulting system is not the origin rom any longer. I don't want to discourage anybody from using xposed with this rom: if everything works, you are fine. If issues occur, clean flash with only gapps installed and reproduce the issue.
[Galaxy Tab S Android Development] Richard_10:
Ok. Will do. Thank you. I'll give you my feed back once I reproduce it without xposed
[Galaxy Tab S Android Development] :
I forgot to mention:

Since the device is freezing and needs a reboot, you need to modify the procedure a little bit. Before you start reproducing the issue, start this command (on local shell or adb shell):

logcat >/extSdCard/logcat.txt

This will write all logging to logcat.txt till you abort (ctrl c) o you reboot the device, but the file preserves a reboot.
[Galaxy Tab S Android Development] Richard_10:
I did a new flash without exposed and reproduced the issue. it is still present, now it freezes like 2 minutes later.

I tried creating a log file, following the instructions you gave me, but the file doesn't stay after reboot. I checked the file manager before the tablet froze it was there, then after the reboot i found nothing.

can you assist me in creating the logcat dev ? thank you in advance
[Galaxy Tab S Android Development] :
Make sure you can connect through adb. Then "adb logcat" and redirect the output to a file (on linux and mac itßs just ">", propably the same for win, but I don't know). After the reboot completed (it's important to do this on the very next reboot, no recovery boot or offline charging in between) copy the file /proc/last_kmesg.

Also make sure your router and your chagall are configured to use the same country code. Check with WifiAnalyser, if the band and channel you are using is busy. If so, change to an other channel. The channels in 2.4GHz band are quite close to eaxh other: ideally you should use a channel which is not only free, but the neighbor channels should be free, too.
[Galaxy Tab S Android Development] Richard_10:
I am actually a telecom engineer, so I can assure you that I chose the right channel. and even if the was interference in the channel this I suppose chouldn't freeze the device i'm wrong ?

I did exactly as you told me. here you go dev. please tell me what's wrong with my device.
[Galaxy Tab S Android Development] Richard_10:
following you advice, I defined the wi-fi country code, as I let it automatic before. then I'm trying screen cast now, and it's still working more then 10 minutes now. I guess you helped me resolve the issue.

it was the wifi country code All along !!!

thanks dev for your precious advices.

EDIT 1: it froze now. !!!!!!!!!!!!!! my only hope is you now dev.

---------- Post added at 03:01 PM ---------- Previous post was at 02:49 PM ----------

after more than 10 minutes + 5 minutes watching streaming channel. it froze !
[Galaxy Tab S Android Development] :
Actually I can't see any crash in your logs. What happend to the adb session, when the device freezes? From the logcat, I would guess, the device is not freezed, but running. Can you ctrl-c "adb logcat"? Does "adb shell" gives you an responsive shell? What video player apps have you tried? Only mxplayer? Does the (hardware) acceleration settings in mxplayer make a difference? Does it make a difference, if using an other video/audio format? Is there a tombstone (/data/tombstones/) for mxplayer or castscreen?

At least I can see, it's not a logcat from a clean install - some third party apps are starting on system startup.

What happened to the logcat? Is win cutting the lines and droping strings?

Mxplayer starts playing at about 14:10:37, log stops at 14:10:50. I guess freezing occurs this time after 12 - 13 seconds. But I can see no crash in kmesg, nor in logcat. That's strange. Propably the logcat is cripled. The question is: why? Is it cripled because of win or something that happend on the way to the zipfile, or is this another symptom of your issue. I don't know.

of course you are right, at least the linux kernel shouldn't freeze - no matter what a apk does. Bad network connectivity shouldn't freeze a device, either. I haven't meant to offend you when discussing wifi configuration. I was just guessing, because non of my friends could reproduce the freezing.

Does the freezing only occur on screencasting, or also if you stream app to app (youtube or play movies)? Which resolution is your chromecast working at?

[MENTION=2983236]ristokoo[/MENTION]: could you check, if you can reproduce the freezing with mxplayer, with mpeg2 with AAC audio in a transportstream (ts) container. Don't forget to install the ffmpeg package for mxplayer, because mxplayer can't decode AAC hardware accelerated.

At the moment I'm quiet clueless. The cripled logcat does not contain information about the crash/freezing. This is really strange.
[Galaxy Tab S Android Development] Richard_10:
I didn't take it as a offence at all. I mentioned the telecom thing just to let you know that I do understand you requests. You are helping me, so how would I be offended. In the contrary I'm grateful.

As for your questions, there are alot hhh. I'm gonna try to answer the ones I understand at least.

Do you want me to make a new logcat ?

Edit: I also would like to inform you that the device freezes but dosen't reboot, so I hard reboot it myself

Envoyé de mon SM-T800 en utilisant Tapatalk
[Galaxy Tab S Android Development] :
As said above, the logcat looks strange. But what I can see, it's not a clean flash and xposed is still installed. From the log you attached:

Unknown element under <manifest>: uses-permission-sdk-23 at /data/app/de.Maxr1998.xposed.maxlock-1/base.apk Binary XML file line #27
Unknown permission android.permission.ACCESS_SUPERUSER in package de.robv.android.xposed.installer
Unknown permission android.permission.ACCESS_SUPERUSER in package de.robv.android.xposed.installer
Unknown permission android.permission.ACCESS_SUPERUSER in package de.robv.android.xposed.installer

i really suggest to do a clean install without xposed. Wipe system, data, chache and dalvik-cache. Flash only rom and opengapps nano from 1129. When the rom has started go through the first time setup. When the device is up only install mxplayer from playstore and the ffmpeg package inside mxplayer. Start the adb logcat and play the movie in mxplayer till it freezes.
[Galaxy Tab S Android Development] ristokoo:
I don't mind testing but I'm not sure I understood. I would need a video file with the properties you described, can I get such a file easily somewhere?
[Galaxy Tab S Android Development] :
I've got the video's properties from the logcat.
[Galaxy Tab S Android Development] Richard_10:
I flashed the xposed uninstaller. Then I wiped system, cache and ART chache. Then I reflashed cm12.1 and gapps.

I am going to do a clean flash as soon as I get home, make a logcat, so we exclude the exposed factor.

Envoyé de mon SM-T800 en utilisant Tapatalk

---------- Post added at 06:24 PM ---------- Previous post was at 06:21 PM ----------

That is the app I'm using for tv streaming, it opens the streams with mx player

http://doctor-dance.net/wss.apk

Envoyé de mon SM-T800 en utilisant Tapatalk
[Galaxy Tab S Android Development] :
Please consult posting #2: clean flash means wiping system, data(!), cache and dalvik-cache. Then you don't need to run the xposed uninstaller, which obviously doesn't work, as you can see in your logs.
[Galaxy Tab S Android Development] Richard_10:
I just got home now, I'll do a clean flash and report right away
[Galaxy Tab S Android Development] Richard_10:
I did a clean flash. wiped system, art and cache, then I flashed cm12.1 and gapps, after sign in to google I just installed Mx player, chrome cast and WSS 1.6 ( the app the streams channel over mx player).

I cast the screen and after sometime it froze.

I, of course did the logical plus last_msg. here you go dev. hope it help clarify the issue this time

PS: I used hardware decoder this time ( the one you use by default in mx player)
[Galaxy Tab S Android Development] zigonneux:
so we still go there to see the changelog or ? http://www.cmxlog.com/12.1/chagallwifi
[Galaxy Tab S Android Development] ristokoo:
Yes that's right, plus we'll tell you here about the unofficial changes when there are some.
[Galaxy Tab S Android Development] ristokoo:
Seems to be a somewhat popular app but I'm not sure if I want to test it. Correct me if I'm wrong but isn't it for watching commercial iptv streams, for which the "normal" way is to pay for a subscription?
[Galaxy Tab S Android Development] :
You are right. I don't know for Suomi, but for Germany it's an illegal violation of copyrights.

Anyway, with wss some people could reproduce the freezing. What we found out last night:

If you use wss with mxplayer (which is the only way to use it - no way to change the player) without screencast, the playback breaks immidietly on delayed or missing packages: last "in time" frame is shown as still picture. Device is still respomding, so you can use the back button. But if you try to play the stream again, mxplayer will drop out with the message that the stream can't be decoded.

If you cast your screen, while this happens, the device is unrespondable. Not only adb is not working, but usb is entirely dead.

We have two discret issues here:

1. Wss breaks, if packets of the stream are delayed or missing (tcp retransmission should ask for the missing packet, but I think this arrives too late).

2. Device is freezing, if the stream breakage occurs while screen is casted.

Obviously we can't do anything about 1.

The second one is very annoying, because a missbehaving shouldn't be able to freeze the device. Since the logs, kmesg and tombstones doesn't shine any light on this, I have no clue, how to debug this issue.
[Galaxy Tab S Android Development] Richard_10:
at home I have a subscription in my tv box to watch football games, I'm outside the country these past 15 days and here there is no football games ( besides the national ones), no possible subscription, I think here football is not number 1 sport. so this application keeps me be up to date with my team's games.

As for the issue .2 that is what I always thought. an app freezing shouldn't lead to the whole device freezing. I'm wondering if another applications may produce the same effect. that would be really annoying, because the rom is nearly flawless.
[Galaxy Tab S Android Development] :
I don't belive, that it's that easy: every single one of the three involved apps aren't freezing the device. Neither it's freezed by using two out of three of this apps (let esexplorer stream a video file from a cifs server to mxplayer while screen is casted works; as well as casting mxplayer with a local file; as well as wss streaming to mxplayer while watching locally on the device). But this one single combination (wss->mxplayer->castscteen) is freezing the device so suddendly, that you can't see anything (would at least expect to se a kernel panic). Any ideas to get this fixed or get - at least - some debuggimg output are welcome!
[Galaxy Tab S Android Development] Namoi:
Hi all,

Not related to the previous issue i know, but i have a question about wifi connection speed. I noticed my old gs2 connect much faster to the same wifi router than my T800 whith the same settings (both on the same 5ghz channel absolutely not clutered as i am the only one using 5ghz here :D Muahhahahah ! ...sorry) -> no scan for wifi, wifi policy is set to shut down when screen is off.

On my Tab i don't use screen lock btw.

When I pop up my tab it takes alsmost 10s to connect while on my gs2 it takes seconds.

I tried an old app from great dev Chamonix (Better Wifi on/off) which solves the issue but nonethelees i would like to understand if this "lag" is by design and could be modified by a user script (again i don't use lockscreen which could be a clue ).

Thanks for any help on that mater
[Galaxy Tab S Android Development] zigonneux:
@ Namoi here ,my 5 g connect very quickly. My T 800 has a reserved ip though .

-----------

open_gapps-arm-5.1-nano-20160318.zip work fine for me with the latest rom.
[Galaxy Tab S Android Development] zigonneux:
does the CLEAR RECENT APPS button is no longer available ? or where is it located, i don't find it anymore. I know we should not clear the recent apps all the time, but it come a time when it's packed, so no more button ?
[Galaxy Tab S Android Development] ristokoo:
It's not the most intuitive location in my opinion but it's there. On the upper right corner of the program window list :)
[Galaxy Tab S Android Development] Namoi:
Thanks, i will try a fixed IP too.
[Galaxy Tab S Android Development] zigonneux:
Did we had to activate it somewhere in the options because it's not there by default ? maybe it should be ON by default.
[Galaxy Tab S Android Development] ristokoo:
I don't think we need to activate it. The only setting regarding the recents menu I know of is under Display & lights, "Show search bar in recents menu" which seems to do nothing. I have seen the option to change the close all button location in some other ROMs though (or it might have been an xposed mod).
[Galaxy Tab S Android Development] Namoi:
It is here by default for sure. I just performed a very clean flash and got it before even dealing with cm settings. Are you using a theme ?
[Galaxy Tab S Android Development] zigonneux:
yes , using a theme. I've just realized that i was confused with the settings of Dirty Unicorn MM6 for my nexus 7

edit : it's there by default when the theme is not installed yet
[Galaxy Tab S Android Development] Richard_10:
Hello [MENTION=4405529]nvertigo67[/MENTION] , still no idea how I can extract the log that contains infos related to the freezing ?

I'm on fire right now ask me anything [emoji2]

Envoyé de mon SM-T800 en utilisant Tapatalk
[Galaxy Tab S Android Development] zigonneux:
zap
[Galaxy Tab S Android Development] Richard_10:
Hello, I understand you mean well, but I advice you to read the conversation history before posting.
[Galaxy Tab S Android Development] zigonneux:
I understand now why you are talking to yourself... I've been reading the whole saga, you know why you don't have any answers ?
[Galaxy Tab S Android Development] Richard_10:
;) you got it all figured out
[Galaxy Tab S Android Development] ristokoo:
New build

https://www.dropbox.com/s/yvlqikpou...FICIAL-ristokoo-nvertigo-chagallwifi.zip?dl=0

MD5SUM: 73f756cb60c844cde0e18db12281aeaa

As always, if you are interested in what has changed:

http://www.cmxlog.com/12.1/chagallwifi/

Happy flashing!
[Galaxy Tab S Android Development] Namoi:
Well it is calm right here :D

Just to shake it up a little, I just tried Live Display on previous build (not the last one) on automatic mode and it doesn't seem to work. I tried it in a dark room past 22h and the saturation of the screen remains as cool as my fridge.

Can someone confirm?

Ps : I tried to fallback to standard profile to no avails and I am using 24 hours (remember now I didn't try to switch to am/pm btw)
[Galaxy Tab S Android Development] zigonneux:
dead calm :) it's a good sign. About the live display , here it seem to work because i put it at OFF. At night I had a screen that was dull and I don't like it that much since i use F.Lux on my monitor and TV already so I didn't want another reddish screen to look at if i need to read an e-mail or something. I simply turn the luminosity down instead.

So anyway I'll test it again, it's ON now and let's see if it work or not. Note that I'm on the latest build. Just a small note, the longevity of the battery charge is phenomenal,

I'm not using it that much , about 5 times a day for news and mail, but it's on it's 4th day of charge at 59%. Tomorrow i'll report on that live display test.
[Galaxy Tab S Android Development] Namoi:
Thanks for answering,

What i mean is it works when you set it up to on (or off), but automatic mode doesn't seem to change to that redish tone at night (and in a dark room).

To be honest I don't remember to have tried automatic mode on a previous build too, or maybe I just miss something about automatic mode.
[Galaxy Tab S Android Development] ristokoo:
I haven't tested lately but will today. Just to be on the safe side I'll upload a fresh build in a couple of hours. Safe meaning the latest sources, but I'm not sure if the April security updates are in yet.
[Galaxy Tab S Android Development] ristokoo:
New build

https://www.dropbox.com/s/avcbmjzoj...FICIAL-ristokoo-nvertigo-chagallwifi.zip?dl=0

MD5SUM file:

https://www.dropbox.com/s/cajwu1hr6...ristokoo-nvertigo-chagallwifi.zip.md5sum?dl=0

I decided to do some spring cleaning so I did a clean flash (factory reset, format system) and restoring my stuff with Titanium Backup. So far seems good.

Now lets see if this livedisplay thing can do its job. I should see a red screen at 20:01 in the evening if it really knows when the sun sets around here... ;)
[Galaxy Tab S Android Development] zigonneux:
i've not been able to test yesterday , but this feature work with the Automatic date and time option, and not with the amount of light in the room. So, the automatic time and date option have to be ON. with the correct time zone, ....of course.
[Galaxy Tab S Android Development] ristokoo:
As I have understood it should change between night and day modes triggered by sunset/sunrise. For this to work, location must be known. Anyway at least today it didn't work for me. A few weeks ago when I tested it worked. Strange.
[Galaxy Tab S Android Development] Namoi:
Hum, would it be the addition of color profile which could take precedence? It would explain why it is located here in the source (I mean when I spoke of this location Nvertigo said it is bound by the source) .

Could be great to test on a version before the addition of color profile. I don't know if I kept a nandroid that long but maybe yes.

Ps: anyway if I had to choose I would kept color profile ;)
[Galaxy Tab S Android Development] ristokoo:
Well my display changed to night mode automatically some time this evening. So it seems to work but I have no idea how the time of switching the display modes is determined. Anyway in my opinion it would be more useful to be able to set the times manually.
[Galaxy Tab S Android Development] Namoi:
I tried again and it didn't work. I checked and i am on automatic time and date and my time zone is correct. Strange...
[Galaxy Tab S Android Development] Namoi:
Hum, i just read that location settings must be on for it to work on automatic mode. Will give it a shot that night.
[Galaxy Tab S Android Development] ristokoo:
Yes that's right, sunrise and sunset times depend on your location. As I said mine didn't change at correct time yesterday but it did at some time. I wonder if daylight savings could affect, in that case it would be one hour off.

Anyway in reality I don't care about the automatic mode. I have a quick settings tile for toggling the display mode ;)
[Galaxy Tab S Android Development] Namoi:
Tbh me too but my ocd part likes to know it works even if I never use it :P

One nailed.

I have another one for later ;)
[Galaxy Tab S Android Development] Hookmt:
Edit: Never Mind. :rolleyes:
[Galaxy Tab S Android Development] zigonneux:
it work fine here, when I took a look at 10 pm the screen was reddish, i took the automatic OFF and it became more blue
[Galaxy Tab S Android Development] Namoi:
Yeah, it works, but kind of tricky to trigger it : i enabled location but it didn't work that night, so i rebooted and only then it worked. Well, not the most user friendly "uber" feature, but ok it works ;)
[Galaxy Tab S Android Development] ristokoo:
Livedisplay works here too.
[Galaxy Tab S Android Development] ristokoo:
New build

Android security patch level April 1, 2016.

https://www.dropbox.com/s/jpcseqabe...FICIAL-ristokoo-nvertigo-chagallwifi.zip?dl=0

MD5SUM file:

https://www.dropbox.com/s/avz0kb14r...ristokoo-nvertigo-chagallwifi.zip.md5sum?dl=0
[Galaxy Tab S Android Development] corb06:
Android 6.0.1 in the works yet for T800?
[Galaxy Tab S Android Development] ristokoo:
No CyanogenMod development afaik. Schischu has published 6.0.1 for T800, last time I tested (more than a month ago) it worked fine except for the camera.
[Galaxy Tab S Android Development] :
First of all: This is a cm thread. In this thread there will never ever be a android6 rom. [MENTION=2371134]Schischu[/MENTION] has a dedecated thread for android6.

I have worked on cm-13.0 for about 130 h. The result was not good enough for publishing, 'cause all the lib wrapping works only with selinux set to permissive(*) - what is a real security hazzard. Since all regular readers of this thread know, that I have no time for development from March to November, it should be clear, not to expect a nvertigo/cm-13.0 build in the next months.

(*)Running a rooted system in permissive mode, while the device is connected to the internet, is grossly neglient!
[Galaxy Tab S Android Development] salva93:
Anyone could test if Webgl work inside the webview?