yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9506 Android Development] DualJoe:
I would have done that immediately if it would have been possible. Proper mounting never worked for me even though CM included a fix long time ago (restricted slave mountspace).

But on another try 5 minutes ago it did finally work properly out of the box indeed so i will drop --mount-master of course. If it doesn't change anything i will test omitting CIFS completely.

There were some people reporting similar crashes but i don't think they've done the same stuff i do with CIFS. We will see...

MDSS could be a good point either. When the screen freezes and goes dark you can notice some white horizontal lines on screen (a proper shutdown doesn't show this behavior). That somehow always reminds me on initialization phase on bootup right before the bootanim starts. There, the screen sometimes comes up with a 50% screen filled cyan flicker. But who knows, that's just a wild guess so far...
[Galaxy S 4 i9506 Android Development] DualJoe:
I think i've found the cause for the audio lag. It seems to be MX Player itself on H/W+ mode only. Using H/W mode seems to work properly. The H/W+ mode can amplify the volume up to 200% so i guess the '+' means they are additionally preprocessing the streams that causes the lag. Pffff.....

Btw, i tested CM screen recording ('screenrecord' binary). It works wonderfully (nearly no lag or frame drops). It just needs some extensive bitrate for pristine quality (i've picked 32Mbit/s) as its AVC/Baseline@L4.2 only.

Edit: Is it just me or is the 'clock' not working (fc) in landscape mode?
[Galaxy S 4 i9506 Android Development] solk2:
Hm. So it looks like theirs audio preprocessing. Maybe coz of qc sound effects.

There is patch commited yesterday for clock.

Found a fix for blue screen beam and iommu page faults for now. Will look more in mdss code.
[Galaxy S 4 i9506 Android Development] ode_:
[MENTION=5291759]solk2[/MENTION], is there some place where I can leave proposal for new CM feature?

I'm missing one Jolla feature, temporarily lock screen rotation.

On Jolla it work by tap and hold screen while rotating phone, keeps current screen positioning until rotating again, this would be nice feature on Android too.
[Galaxy S 4 i9506 Android Development] DualJoe:
CyanogenMod Jira bug tracker has feature requests.
[Galaxy S 4 i9506 Android Development] DualJoe:
Crashed again at playing games. No special --mount-master this time. I will update to 20141116 and setup a logcat now. Did it not crash at least once on your side yet?
[Galaxy S 4 i9506 Android Development] davidl1983:
Crashes

It has been very unstable for me lately. Crashes a few times a day.
[Galaxy S 4 i9506 Android Development] DualJoe:
At least good to know there are others who also have the crashes so it shouldn't be an isolated problem on my side.

Full dmesg is running. I hope it gets synced before crash and leads to some useful informations.

Will report back...
[Galaxy S 4 i9506 Android Development] solk2:
Damn. I forgot completely that I've update EGL libs in my home builds. Maybe thats EGL. Then it would explain why I don't have these reboots. But anyway I am reworking mdss driver currently. And have some updates in current build thats could be a reason too. And as I understand phone crashes only when frames is updated on screen.
[Galaxy S 4 i9506 Android Development] puschel_1:
Here also several crashes per day, but not really reproducable..

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 4 i9506 Android Development] DualJoe:
Yes, that's correct. It also never crashed on screen-off.

New dmesg didn't led to anything useful. Its trimmed before critical part.

Respect. You probably know what you're doing. ;)
[Galaxy S 4 i9506 Android Development] davidl1983:
Yeah, it must be something you changed not too long ago. I did not experience the reboots the first weeks I used the rom.
[Galaxy S 4 i9506 Android Development] kornelius1982:
Hi all, I want to buy this device and want to know how`s CM11 working on it?

Is it stable enough for daily usage?

Are there any device maintainers to proceed further development of CM?

Thanks in advance for any helpful replies!
[Galaxy S 4 i9506 Android Development] davidl1983:
I have found the official CM to be stable for daily use and a great rom. Right now the newest dailies are not completly stable. Some code got changed that caused random reboots.

There is also another unofficial CM made by arter97 ( which I am using while waiting for the problems to be solved with the official one.) It is completly stable. He has uploaded a working lollipop CM, which is not yet good enough to be a daily driver, but shows promise.
[Galaxy S 4 i9506 Android Development] puschel_1:
Is the arter97 CM really for GT-I9506?

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 4 i9506 Android Development] ode_:
Yes, there is also 330 series roms, but definitely there is working gt-i9506 too, you just flash cm-fix after Rom+ kernel+ gapps flash.
[Galaxy S 4 i9506 Android Development] kornelius1982:
Yeah, that`s pretty good for a few reason so far. First and major is that i9506 is based on AOSP friendly snapdragon, and IMHO this device is best on the market with price/performance ratio.
[Galaxy S 4 i9506 Android Development] solk2:
EGL

Can someone test if phone crashes with these EGL libs. Just to be sure.
[Galaxy S 4 i9506 Android Development] DualJoe:
Yes, will do it.
[Galaxy S 4 i9506 Android Development] davidl1983:
Is no news, good news Dual?
[Galaxy S 4 i9506 Android Development] DualJoe:
Its running fine so far. Too early to tell though. I usually have a crash between 24-48h.
[Galaxy S 4 i9506 Android Development] davidl1983:
Great, fingers crossed then.
[Galaxy S 4 i9506 Android Development] DualJoe:
Still crashing. Looks like it's not Adreno drivers..
[Galaxy S 4 i9506 Android Development] hou$$:
with cm-11-20141119-NIGHTLY-ks01lte.zip

Everything Works Fine !!

but UMS mode doesn't Work

I think IRDA port doesn't work too

on Antutu test I have a score of 42818 !!

S-view Cover Work's too
[Galaxy S 4 i9506 Android Development] solk2:
Then must be mdss. I'll commit update today. Will see.

And still nothing in logs?
[Galaxy S 4 i9506 Android Development] solk2:
UMS disabled in KK by google.

IRDA works with apps that comply google IR API.
[Galaxy S 4 i9506 Android Development] DualJoe:
On a first look still nothing. Will clean it up once i'm on my desktop system. Its full of CIFS errors (unexpected lookup error) and 'sec_debug_check_crash_key'.
[Galaxy S 4 i9506 Android Development] solk2:
If it is full of errors then it could be watchdog bite. I had same with usb with bad port. Errors in controler caused watchdog bite and reboot.

So maybe you should try without cifs.
[Galaxy S 4 i9506 Android Development] DualJoe:
KMSG is 16025 lines (932KB).

CIFS errors 10920 lines:

[ 2552.238893] CIFS VFS: Unexpected lookup error -20

'sec_debug_check_crash_key code' 2487 lines:

[25126.394999] sec_debug_check_crash_key code 172 value 0 state 0 enable 0
[25126.395074] sec_debug_check_crash_key code 114 value 0 state 0 enable 0
[25126.395144] sec_debug_check_crash_key code 115 value 0 state 0 enable 0
[...]

'samsung_dsi_panel_event_handler : unknown event' 1539 lines:

[25147.467943] samsung_dsi_panel_event_handler : unknown event

Remaining 1079 lines (67KB).

Will try without using CIFS now. Watchdog bite sounds reasonable. There are 31 minutes between last CIFS error and last kmsg line though. We will see...
[Galaxy S 4 i9506 Android Development] solk2:
Cifs error most like coz of nmblookup failure.

Sec debug crash kay is triggered by every power press.

31 mins means that it is not watchdog.

Is screen was on and what app was opened?
[Galaxy S 4 i9506 Android Development] DualJoe:
Yes, screen on and playing game "Where's my water" (maybe for 20min). It didn't crash on MX Player with CIFS yet.

I'm not sure when the bug actually came up for the first time. Maybe as you fixed the brightness bug, maybe later. I guess we should try your mdss fixes next.
[Galaxy S 4 i9506 Android Development] solk2:
Yes. At least for now i didn't saw any buffer underruns (blue screen artifacts) yet.
[Galaxy S 4 i9506 Android Development] DualJoe:
It's still there, just earlier. The bootloader framebuffer is flashing now (shifted/moved) instead of cyan beam. Testing new mdss now...
[Galaxy S 4 i9506 Android Development] solk2:
I know. The interesting part that if fix this then brightness bug will return. Maybe i can workaround it somehow.
[Galaxy S 4 i9506 Android Development] DualJoe:
No, it's not mdss. Still crashing.

Maybe it's just coincidence but it always seems to crash only after several hours (overnight). Maybe charging is involved? This time it survived like 30min after charging. Will test that...
[Galaxy S 4 i9506 Android Development] solk2:
I still thunk that it is mdss. Last commit to it is included only in 23-11 build.

Edit: Nope. Looks like EGL. Got crash when playing around with google maps. I'll commit update tomorrow.
[Galaxy S 4 i9506 Android Development] DualJoe:
Running 20141125. Let's see if it works...

How could you tell it's EGL? Did you find something in the logs?
[Galaxy S 4 i9506 Android Development] pille1:
When are we going to see the first builds with Lollipop?
[Galaxy S 4 i9506 Android Development] solk2:
Coz crash happens only when screen is on. Moving screen around. And I saw they made same on bacon coz of bugs. Its even not egl. Its gralloc. Coz with this egl libs it was working fine till cm splitted gralloc hal for new drivers.
[Galaxy S 4 i9506 Android Development] solk2:
Maybe in a couple of days or maybe in a couple of weeks. Want to fix startup screen glitch before switching to cm-12.
[Galaxy S 4 i9506 Android Development] Kiryo24:
I'm trying out 20141125 as well. Lets hope for the best
[Galaxy S 4 i9506 Android Development] awicks:
I had another crash this morning running 20141125. Same as normal - screen on and then a reboot.
[Galaxy S 4 i9506 Android Development] solk2:
Please post last_kmsg. There still some problems with new mdss driver. But at least there errors in logs about that.

Edit: Damn. Just looked thru code and found some faulty merged places which can cause hardware lockups.
[Galaxy S 4 i9506 Android Development] puschel_1:
So in which nightly can we test a fix? ?

Gesendet von meinem GT-I9506 mit Tapatalk
[Galaxy S 4 i9506 Android Development] solk2:
Pushed some fixes now. I just don't know when buildbot pulls them. Today or tomorrow.
[Galaxy S 4 i9506 Android Development] DualJoe:
b20141125 crashed in browser.

Even though it lasted quite long this time i rebooted more often as well.
[Galaxy S 4 i9506 Android Development] solk2:
Looks like I found source of this reboots. Looking thru logs. It looks like it always crashes on max77803_get_input_current. And the only things I have changed there is dwc3 driver. Reverted all changes to it now. Will see. If it helps. I'll put back some reverted optimizations. Hope it will get into todays build.
[Galaxy S 4 i9506 Android Development] puschel_1:
Tried nightly from today and had 2 reboots again...

Gesendet von meinem GT-I9506 mit Tapatalk
[Galaxy S 4 i9506 Android Development] DualJoe:
Is it possible that you charge quite often or use USB port otherwise (car audio) or something? For me it seems it never crashes that fast. It always needs some time.

So far, 20141129 is running fine here. No crashes yet. But it's just running for some hours yet.. Usually needs more time.

20141127 was crash-free as well here. Not sure if it was stable already.
[Galaxy S 4 i9506 Android Development] puschel_1:
No, phone gets only charged during night or if battery is empty. But it is in heavy use by my wife...

Gesendet von meinem GT-I9506 mit Tapatalk
[Galaxy S 4 i9506 Android Development] boart:
No reboot so far with nightly from 29th. Will report if it reboots.

Gesendet von meinem GT-I9506 mit Tapatalk

Edit: Smartphone rebooted right now. If i get a reboot, its when i try to scroll in a Browser :(
[Galaxy S 4 i9506 Android Development] z0nic:
No reboots here on 29th either. However, there's a yellow-ish tint on the screen. I've experienced this since the 26th.

Has anyone else experienced this?

I tried clean install, but that didn't help.
[Galaxy S 4 i9506 Android Development] DualJoe:
I cannot notice any tint. Maybe check in 'system settings/display/color calibration' that values are 'default' indeed. There might also be some access to mDNIe by sysfs (not sure) if necessary. It's also possible that the tint only comes up on clean/wiped systems. We had something similar with a WiFi bug in the past.

No crashes here as well so far...
[Galaxy S 4 i9506 Android Development] puschel_1:
Here the same. Most reboots during browsing in Chrome.

Is there a previous nightly with working camera and no reboots?

If so, where can I get it? Thanks!

Gesendet von meinem GT-I9506 mit Tapatalk
[Galaxy S 4 i9506 Android Development] davidl1983:
The M10 on the frontpage did not give me bootloops, the camera was also working. You could also use the arter one until the loops are fixed
[Galaxy S 4 i9506 Android Development] puschel_1:
I think problem has something to do with scrolling. Scrolling in Browser or Facebook results sometimes in reboots, perhaps a hint...

Gesendet von meinem GT-I9506 mit Tapatalk
[Galaxy S 4 i9506 Android Development] DualJoe:
Please don't forget to post '/proc/last_kmsg' after crash/reboot.

I don't want to call it fixed but it runs suspiciously well atm here. It doesn't want to crash lately...
[Galaxy S 4 i9506 Android Development] z0nic:
Hi, I just installed todays build (20141130), and I noticed the same tint.

To get things looking normal, I have to change Green (in colour calibartion) to 30%.

This was while upgrading from 20141125 (which doesn't appear to have this issue) to 20141130.

I've tried a clean install previously, same issue.

One thing I noticed this time, it doesn't turn green/yellow-ish until AFTER the "Upgrading apps" message.

Any ideas resulting in a fix would be appreciated ;)
[Galaxy S 4 i9506 Android Development] xinu:
thanks for your work solk2, hope this will be usable soon :)

P.S. donation send for some coffee :)
[Galaxy S 4 i9506 Android Development] TonskuDaigle:
To me it's more than usable already. As the audio jack got fixed, I now run this full-time and off the top of my head, I can't come up with any bigger or medium problems that would bother me.
[Galaxy S 4 i9506 Android Development] xinu:
realy?

gonna try myself at home
[Galaxy S 4 i9506 Android Development] solk2:
Last uploaded version had bug with bluetooth calls. I'll upload new build and then it will be available to download.
[Galaxy S 4 i9506 Android Development] solk2:
Fix and uploaded new version.
[Galaxy S 4 i9506 Android Development] diegodu27:
Did you fixed black screen when locked ? I got this error on 4.2.2 bootloader
[Galaxy S 4 i9506 Android Development] faffaz:
Here is all info!

I flashed the boot-modem-keys.tar.md5 from the 4.3 stock I9506XXUBML6_I9506VDSBML2_VDS.zip (from sammobile) with odin, both v1.87 and 3.09.

No change.

Copied the keymaste *.mtd, .b00, .b01, .b02 and .b03 to /firmware/image as instructed. Fixed the issues except the black screen untill reboot, well until screen turned of and stayed totaly dark with only button lights on!!!

Reboot borked everything again, phone unuseable.

The files present in my /firmware/image before pushing the keymaste-keys are the following (will attach them if ever needed):

*cmnlib.b00

*cmnlib.b01

*cmnlib.b02

*cmnlib.b03

*cmnlib.mdt

*isdbtmm.b00

*isdbtmm.b01

*isdbtmm.b02

*isdbtmm.b03

*isdbtmm.mdt

*mc_v2.b00

*mc_v2.b01

*mc_v2.b02

*mc_v2.b03

*mc_v2.mdt

*playread.b00

*playread.b01

*playread.b02

*playread.b03

*playread.mdt

*sshdcpap.b00

*sshdcpap.b01

*sshdcpap.b02

*sshdcpap.b03

*sshdcpap.mdt

*venus.b00

*venus.b01

*venus.b02

*venus.b03

*venus.b04

*venus.mdt

*widevine.b00

*widevine.b01

*widevine.b02

*widevine.b03

*widevine.mdt
[Galaxy S 4 i9506 Android Development] solk2:
Interesting. You have only half of what i have in mine. Try to put them all from attached archive with replacement. If this wont work then try this one stock ROM.
[Galaxy S 4 i9506 Android Development] faffaz:
Will try my best. By the way, I have trubble ADB pushing files to /.....cos of "only readable system. Not even ADB root will do it.
[Galaxy S 4 i9506 Android Development] solk2:
Thats coz this is userdebug build. Copy file in recovery
[Galaxy S 4 i9506 Android Development] DrDee:
My understanding is this ROM *needs* the 4.3 bootloader, both of DeHawks ROMs use the 4.2.2 bootloader to get around knox or something.

You would need to flash the full stock 4.3, flash custom recovery, root and trip knox to be able to use this ROM.
[Galaxy S 4 i9506 Android Development] finnince:
It seems that your kernel is semi-working with arter97's CM11 ROM and Android 4.4.2 bootloader on my SHV-E330S.

I flashed only boot.img extracted from your ROM. Singal / baseband / camera is normal, but the call won't go through. It will stick at DIALING. When I try to hang up the call it will stick at HANGING UP. The min frequency is set to 1190MHz. Didn't test others things like wifi / bluetooth because I don't want to miss a call.....

And the memory got smaller?

Anyway, I guess there's a way to make your rom work normally both on GT-I9506 and SHV-E330S. :o
[Galaxy S 4 i9506 Android Development] solk2:
It is better not to use my kernel on SHV. Coz it different in hardware configuration. You can try to use my ROM with arters kernel. But you need to change ota asserts in update script and probably you have to change ril binaries.
[Galaxy S 4 i9506 Android Development] xinu:
is there a way to install some Samsung Apps in cyanogen? like SHealth or 4K camera
[Galaxy S 4 i9506 Android Development] TonskuDaigle:
Can't say for sure that it'd work, but for SHealth check http://www.appbrain.com/app/s-health/com.sec.healthdiary and for 4K camera http://xdaforums.com/showthread.php?t=2711239.
[Galaxy S 4 i9506 Android Development] you5urf:
keep up the good work and you shall be rewarded handsomely!! I was really just about to dithch this phone. That has got to be worth something right? I am also available for testing if need be
[Galaxy S 4 i9506 Android Development] hs911:
i dont think this works for camera because there are missing framework files. just tried this on a sony phone with no success. but maybe someone tries :)
[Galaxy S 4 i9506 Android Development] xinu:
i tried, it didnt work, even other cameras like from sony (moded for cyanogen) didnt work for me...
[Galaxy S 4 i9506 Android Development] xinu:
I have problem with sounds, it wont play any... even sound notifications dont work and youtube force closing...

anyone have idea whats wrong?
[Galaxy S 4 i9506 Android Development] solk2:
I don't know. Please post logcats. Or try new version.
[Galaxy S 4 i9506 Android Development] DualJoe:
Never heard of an "Upgrading apps" message. You might have installed some app doing this. If you want to do a complete wipe you have to delete '/system/addon.d' folder, reinstall the rom and wipe /data (without sdcard).
[Galaxy S 4 i9506 Android Development] z0nic:
My apologies, It might be my explanation skills that confused you.

After upgrading to a newer build.. after the boot-screen => "Android is upgrading... optimising app xxx of xxx.".

When the text change from "Optimising app..." to "Starting apps", the screen flickers and the tint appears.

I've tried deleting '/system/addon.d' folder, wipeing /data (without sdcard) and reinstalling the rom.

I even tried reverting back to stock rom to get a "clean start".

This issue started with build 20141126.

As it seems, I'm the only one with this issue. But I cannot see where I'm doing wrong.
[Galaxy S 4 i9506 Android Development] DualJoe:
That's the point where brightness and such stuff gets initialized indeed. I can clearly see that point as well as its switching to lowest brightness on my side. If you're using 'auto-brightness' try to disable it and reboot (just for testing). Solk2 worked on that lately indeed if i don't get it wrong.

You get that tint on stock rom as well?

Edit: Probably not.. just for "clean start" i guess.
[Galaxy S 4 i9506 Android Development] z0nic:
Hi, thanks for the quick reply!

Just upgraded to todays build (again). Turned off Auto-brightness and played around with the slider. At some levels (low brightness) the tint appears, but when I set it to almost-full/full brightness, the tint disappears.
[Galaxy S 4 i9506 Android Development] puschel_1:
Of course, is there a how to hold I can get this file?

Gesendet von meinem GT-I9506 mit Tapatalk
[Galaxy S 4 i9506 Android Development] DualJoe:
I have a slight color jitter as well when i move around in brightness spectrum. If it's that what you mean its not a new problem i think. Even the Galaxy S3 had slight color jitter on different brightness steps if i reckon correctly. Maybe a sideeffect of rounding errors, LookUpTable conversion or something.

You can directly pick that file for attachment with the smartphone/browser itself. When you click 'manage attachments' (on XDA/Post Reply) a selection window should pop up. Choose 'documents' and you should get a list of available file browsers to pick the file (/proc/last_kmsg). Needs root file browser. The CM builtin one should be ok but maybe needs to be root activated in its options first.

Take note that "last_kmsg" gets replaced on every reboot so just post the file right after a crash. If you rebooted (again) in the meantime the file is lost already (overwritten).
[Galaxy S 4 i9506 Android Development] Kiryo24:
I had reboot just now with 20141129 while browsing xda with dolphin browser.
[Galaxy S 4 i9506 Android Development] DualJoe:
Log is good. Thanks.

[MENTION=5291759]solk2[/MENTION]:

The last log entry reminds me of this. Maybe it has side-effects and the libs are running wild.

Edit2:

Let's give it a try...

Anyone with crashes try the attached fix (flash zip in recovery). It reverts the above commit.
[Galaxy S 4 i9506 Android Development] Kiryo24:
Flashing now. reporting back any changes.
[Galaxy S 4 i9506 Android Development] boart:
Installed the fix, but had a reboot right now. I was scrolling in chrome again. No chance to get the log today :(

Gesendet von meinem GT-I9506 mit Tapatalk
[Galaxy S 4 i9506 Android Development] solk2:
I don't think that sensor can cause this. But can't say for sure. I didn't had any reboots since I reverted dwc3 changes. Will try to play around with temphumidy sensor. Maybe there can be problem too. But it is unchanged and same as in stock.

I am aware of this screen tint issue. Still fixing bugs of new mdss.
[Galaxy S 4 i9506 Android Development] arter97:
If I were you, I'd rebase the kernel and merge CAF graphics by picking up only the necessary mdss & drivers/gpu patches(which my kernel already does).

And btw, I also have that max77803, SSP kmsg message.
[Galaxy S 4 i9506 Android Development] solk2:
Well I am doing just opposite. rebased at CAF and merging samsung specific code, manually. I can learn of how it works like that and will be easier to implement new features (like doze) and fix bugs later. There not much left to do to get it working properly now. Already fixed that splash flickering, but not commited yet.

This kmsg message should be there. Just max77803 was asking for current status of input power sources and dwc3 as power source caused some lockup. But I have no idea why DualJoe and I am don't have this crashes while others do now.
[Galaxy S 4 i9506 Android Development] boart:
What browser do you use? I get the crashes with chrome

Gesendet von meinem GT-I9506 mit Tapatalk
[Galaxy S 4 i9506 Android Development] solk2:
Built-in. Just installed chrome to test it. The only two things that came into my mind is libqc-opt.so which I have different from TheMuppets. But thats doesn't explain why DualJoe don't have crashes. And maybe kernel is not updated somehow.