yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9506 Android Development] arter97:
I heavily doubt if that'll all work out properly. It sounds the same to me, you'll figure out what's different between stock kernel source and stable/linux-3.4.y and apply it to stable/linux-3.14 or something.

More importantly, you do not have the resource that the manufacturer has.

There's a lot of CAF commits reverted and workarounded by Samsung, and even some commits that ks01lte's CAF revision don't have but klte's CAF revision have but also reverted. A good example would be the mm/page-writeback.c commit; the latest CAF Git has it but Samsung reverted in klte, probably due to a bug that Samsung's Snapdragon 80x unit has.

And kernel should ultimately stable, no matter what.

If you choose to go with a unstable, non-manufacturer-approved kernel base, I doubt it can be any more stable than the stock kernel source.

That's the main reason why I'm using stock kernel's GPU source with just few extra to make it work with caf-new.

If you're adventurous enough to do that, I wish you good luck, but I also should remind you this - http://wiki.cyanogenmod.org/w/Doc:_Submitting_A_Port
[Galaxy S 4 i9506 Android Development] Kiryo24:
I'm using only dolphin browser but had crashes with other apps like some wikipedia browers now there hasn't been any crashes after i flashes DualJoe's zip
[Galaxy S 4 i9506 Android Development] solk2:
I wont agree with this point of view just coz CM userspace expects different behaviour from stock kernel. As you said you needed few extras to make it work with caf-new.

Samsung have a lot of workaround due to theirs buggy hardware. But that doesn't mean that their workarounds couldn't be implement on caf base. For example BT (bluesleep) that caused crashes and most of workaround to this was in samsung userspace bt libs.

And I know about this page on wiki that you pointed out. But thats why there no official snapshot build yet.
[Galaxy S 4 i9506 Android Development] arter97:
Yeah, it's funny to see some stuffs like BT, Wi-Fi, screen brightness etc is fixed differently than stock Touchwiz.

But what I mean by stability there is something that userspace cannot fix. Like non userspace related kernel panics and such..
[Galaxy S 4 i9506 Android Development] solk2:
Wish i it was simple kernel panic that was fully traced in logs. But this is hard to trace and hardly reproducable bug hard/kernel.

I understand what saying about stability. But the problem that userspace affecting kernel work as well. So for me its better to fit for userspace that i have source of by looking thru diffs of samsungs one and kernel that fits it.

I dont say that mine way of doing better then yours. Both ways have their cons and prons. Its just difderent ways of doing it. And my goal not make a super mega ROM thats second priority. I want to study how things working more.
[Galaxy S 4 i9506 Android Development] Kiryo24:
Don't know what happened. Phone was just sitting there and when i tried to unlock it had rebooted on its own :( (its possible that it froze before i put it away but doubt it)

Ps. Battery was pretty low
[Galaxy S 4 i9506 Android Development] puschel_1:
So, my wife had a reboot some hours ago. I hope file will help, even it is some hours old (I copied it just out of the phone).
[Galaxy S 4 i9506 Android Development] DualJoe:
Now crashed here as well in Chromium (CM browser). Log attached. Longest crash-free period so far since 20141125. Just coincidence?

Would it make sense to raise printk verbosity even more (4->7)? I mean, at the moment we have nothing in the logs. Or maybe injecting some manual printk's for.. whatever?

localhost / # cat /proc/sys/kernel/printk
4 4 1 7
[Galaxy S 4 i9506 Android Development] Kiryo24:
Here it froze in dolphin browser again
[Galaxy S 4 i9506 Android Development] DualJoe:
Nice.. we have a managed kernel oops. Might lead to something...

Can you lookup your /data/dontpanic folder if there are files near the crash time and attach them as well?
[Galaxy S 4 i9506 Android Development] Kiryo24:
Folder is empty...
[Galaxy S 4 i9506 Android Development] solk2:
Unliekly. This oops coz of debuggerd. Was same error in firefox in previous versions. Its debuggerd error not kernel.

Uploaded more fixes to mdss. Should remove splash screen flickering. Maybe more.
[Galaxy S 4 i9506 Android Development] solk2:
If I knew what exactly causes crashed i would do so.

Increasing verbosity is good idea, still will give some sort of trace.
[Galaxy S 4 i9506 Android Development] puschel_1:
Any news how to solve the problem? Thanks in advance.

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 4 i9506 Android Development] DualJoe:
Wait for 20141203 and test that. Should be up in some hours.
[Galaxy S 4 i9506 Android Development] solk2:
Reboots not fully fixed there too. Found that mmc caching is broken too. Had reboot when trying to access installed app. Will fix it tomorrow.
[Galaxy S 4 i9506 Android Development] davidl1983:
Thanks for all the hard work you are doing, trying to fix it. Appreciated!
[Galaxy S 4 i9506 Android Development] solk2:
I hope that 20141204 wont reboot. Waiting for feedback.
[Galaxy S 4 i9506 Android Development] Kiryo24:
Updating now. Keeping fingers crossed :D
[Galaxy S 4 i9506 Android Development] Buda1996:
Hi bros I got the same problem with my test ROM as I was doing research I saw that every function that's is requiring more GPU activities closes
[Galaxy S 4 i9506 Android Development] Kiryo24:
Can't say much yet except looks promising. Been browsing without reboots whole day. Too early to say to be sure though.
[Galaxy S 4 i9506 Android Development] puschel_1:
Same here, 8 hours without reboot ?

Gesendet von meinem GT-I9506 mit Tapatalk
[Galaxy S 4 i9506 Android Development] DualJoe:
Crashed 3 times already here. On bVNC and browser and even quite fast. One session didn't even last 5 minutes. The last hours were stable. Will test it later again...
[Galaxy S 4 i9506 Android Development] solk2:
Damn. Just for the experiment try this libqc-opt.so.

P.s. using bvnc for 15 mins now. Everything ok.
[Galaxy S 4 i9506 Android Development] DualJoe:
Yes, currently it's running fine here as well. Testing the *.so now.

An hour ago i had to delete /data/misc/wifi again as i couldn't enable WlanAP. Log said hostapd.conf couldn't be created (permission denied). After deletion it worked fine again. That's weird as I'm sure I've done that before and WlanAP did work properly before as well. It somehow must corrupt itself.

These permission problems remind me of SELinux. Maybe it's worth to set the rom to 'permissive' and keep an eye on auditd log.

Edit: Crash in browser with alternative 'libqc-opt.so'.
[Galaxy S 4 i9506 Android Development] solk2:
Do e2fsck -y /dev/block/mmcblk0p26 in recovery. And format cache partition.
[Galaxy S 4 i9506 Android Development] DualJoe:
No errors. Even did a -fy as it was 'clean'. Looks like the filesystem doesn't suffer from all the crashes.

That '/data/misc/wifi' deletion reminds me to that 'wifi password lost' bug that you once fixed.
[Galaxy S 4 i9506 Android Development] solk2:
Then was different situation. Config wasnt saved on wifi shutdown.

I hope i found bug what causing reboots this time. It is in cpu shutdown.
[Galaxy S 4 i9506 Android Development] puschel_1:
Here reboot again while typing a WhatsApp message... ?

Gesendet von meinem GT-I9506 mit Tapatalk
[Galaxy S 4 i9506 Android Development] Kiryo24:
Can you post last_kmsg?
[Galaxy S 4 i9506 Android Development] puschel_1:
In one hour 2 further reboots...
[Galaxy S 4 i9506 Android Development] puschel_1:
And one more...
[Galaxy S 4 i9506 Android Development] DualJoe:
Are you on 20141206 (or up) already? That image should have some promising cpu/hotplug fixes.

@ all:

Btw, Cyanogenmod doesn't support any delta diff updates so far, right? Not that i'm missing something here...

All quiet so far, no crashes. Will update to 20141207.
[Galaxy S 4 i9506 Android Development] solk2:
Yes. Better to update to 20141207. I hope that it is fixed there.

Btw my phone felt and amoled panel cracked. So if repairs will cost too much I will buy different phone and won't be able to maintain cm for this phone.
[Galaxy S 4 i9506 Android Development] Kiryo24:
Sorry about your phone and thank you for all the work you done.

Btw What phone you had in mind next?
[Galaxy S 4 i9506 Android Development] solk2:
Oppo find 7 or oneplus one. Don't know yet which one. It's troublesome to get oppo in my country and its more expensive but with qhd. While oneplus is easy to buy and cheaper.

Anyway I'll try to bring up cm 12 for ks01lte.
[Galaxy S 4 i9506 Android Development] lkarus:
had same issue. typing WhatsApp message with SwiftKey gave me 3 reboots in 30min. updated to 20141206. problems solved I guess.
[Galaxy S 4 i9506 Android Development] puschel_1:
Here only 20141206 is available and installed (by cmupdater).

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 4 i9506 Android Development] puschel_1:
So, for me no changes, reboots are still present.

Here a last_kmsg direct after a reboot.
[Galaxy S 4 i9506 Android Development] solk2:
Which version?
[Galaxy S 4 i9506 Android Development] puschel_1:
20141206

Thanks.
[Galaxy S 4 i9506 Android Development] solk2:
Try 20141207 or 09. 1206 don't have all fixes.
[Galaxy S 4 i9506 Android Development] Kiryo24:
I had no problems with 20141204 but today i updated to 20141209 just now had reboot while playing superbrothers sword and sorcery :(
[Galaxy S 4 i9506 Android Development] DualJoe:
I had no crashes so far. If only we could trigger the bug somehow...

Not sure if it would help to spread some printk's all over the kernel that simply say I'm here or there to get some code flow pattern.

Kgdb might catch system exceptions to get a stack trace.

If anyone have access to the SBL console we could try 'setenv PHONE_DEBUG_ON 1'. Maybe it enables some debug output after crash.
[Galaxy S 4 i9506 Android Development] solk2:
Uploaded some battery (charger, regulator) updates now. For me it looks like some race condition while polling status of battery (voltages) and turning on and off CPUs, like polling for current voltage of CPU2 while it is already disabled. Saw thats samsung removed some part of this polling, maybe it will help.

kgdb and sbl won't give more then kmsg. SBL is good only on early boot sequence when you can't get to debug messages via dmesg. kgdb is useless when you don't know where to look for bugs.

At least we getting closer and reboots happens less often.
[Galaxy S 4 i9506 Android Development] DualJoe:
The kernel raises exception on crash triggering breakpoint giving control to kgdb. Unless it goes down the drain as well it will exactly tell you what was going on.
[Galaxy S 4 i9506 Android Development] puschel_1:
One file of several reboots today...
[Galaxy S 4 i9506 Android Development] solk2:
You can try. But i think it wont give you what you expecting coz it more looks like hardware lockup. So kgdb wont catch exception and will just reboot as it now.
[Galaxy S 4 i9506 Android Development] solk2:
Thanks. It always ends same cpu shutdown and battery polling. Try this build. As cm buildbot works a little weird currently.

Edit: sorry. URL Fixed now.
[Galaxy S 4 i9506 Android Development] puschel_1:
I get this error trying to download it: Invalid URL: http://getcm.solk.org.ua/ cm-11-20141210-UNOFFICIAL-ks01lte.zip

Gesendet von meinem GT-I9506 mit Tapatalk
[Galaxy S 4 i9506 Android Development] DualJoe:
There's a space in the url. Use this:

http://getcm.solk.org.ua/cm-11-20141210-UNOFFICIAL-ks01lte.zip
[Galaxy S 4 i9506 Android Development] puschel_1:
Installed and further reboots...

Perhaps I have a hardware issue?
[Galaxy S 4 i9506 Android Development] solk2:
Try this build.
[Galaxy S 4 i9506 Android Development] puschel_1:
Installed and test is running, thank you!

Seems like I am the only / last one with reboots?!

Gesendet von meinem GT-I9506 mit Tapatalk
[Galaxy S 4 i9506 Android Development] solk2:
I think everyone have. On some devices it happens more often.
[Galaxy S 4 i9506 Android Development] DualJoe:
Still crashing...
[Galaxy S 4 i9506 Android Development] solk2:
Here another build with a reverted cpufreq changes and touchbooster back.
[Galaxy S 4 i9506 Android Development] lkarus:
any difference between cm updater and ur linked zip file?
[Galaxy S 4 i9506 Android Development] solk2:
Yes. Builds are different. I didnt commited changes that in this linked build yet.
[Galaxy S 4 i9506 Android Development] lkarus:
updated to 20141212 via updater. no reboots since ..07. so I don't need to try urs right ?
[Galaxy S 4 i9506 Android Development] solk2:
Others had reboots. So most likely you will too but later.
[Galaxy S 4 i9506 Android Development] awicks:
Are these included in the 1213 release?
[Galaxy S 4 i9506 Android Development] solk2:
Still not. Looks like reboots fixed as no one reports them. Looks like bug in touchscreen firmware so there some deadlock occures on lower frequencies. Will push this changes now and cm-11.0 will be closed. Starting to work on cm-12.
[Galaxy S 4 i9506 Android Development] puschel_1:
Atm no reboots here with last unofficial version, but last days no heavy use. I will reply next days again.

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 4 i9506 Android Development] DualJoe:
Can you bring CM11 to a better shape nevertheless? Like disabling touchbooster, re-injecting your mDNIe changes and all the stuff you have reverted for testing purpose? I think i'm not the only one who will not switch to CM12 in the next time especially that there is no replacement for xposed/xprivacy yet.
[Galaxy S 4 i9506 Android Development] solk2:
I cant disable touchbooster as it causing reboots. I just can reimplement it in new devfreq(cpufreq) drivers in cm-12 and merge changes into cm-11 after testing. At least for now. Maybe when samsung relases new kernel it will be fixed there. And what do you mean by mDNIe changes? I thought that all mdss (mdnie) changes are there. There not much reverted. Only mmc and dwc3. Will be putting this back as it goes stable in cm-12.
[Galaxy S 4 i9506 Android Development] DualJoe:
Ah, ok. I thought you reverted much more in the latest builds. But if you say its all there already i've said nothing.

I meant your mdss changes of course, not mDNIe. My fault.
[Galaxy S 4 i9506 Android Development] solk2:
CM-12

Made first cm-12 build. cm-12-20141219-UNOFFICIAL-ks01lte.zip.

Before install you should backup.

I don't know even if it will boot or not.

Feel free to test.

For working gapps you should search for suitable for you package.
[Galaxy S 4 i9506 Android Development] TonskuDaigle:
I was literally just thinking "wish solk released his cm12 already". Your timing couldn't have been better :P

For the Lollipop gapps check GAPPS topic.
[Galaxy S 4 i9506 Android Development] TonskuDaigle:
Yep. Booted fine, but once the CM logo went away problems started.

Took ages to find cellular and in the end it didn't.

Then processes with phone, systemui, settings... After a reboot, started getting consistent error messages so I just booted to recovery for CM11.
[Galaxy S 4 i9506 Android Development] solk2:
Please post logcats (radio, system, main). So i can fix it.
[Galaxy S 4 i9506 Android Development] TonskuDaigle:
First page after the loading boot screen it gives an error "Unfortunately, Settings has stopped.". Then after pressing OK for it, it gives another error "Unfortunately, System UI has stopped.". Then it tries activating cellular service after I selected language.

*** 10mins *** (during this time screen's not frozen, the line moves there. I keep the phone alive instead of screen timing out.)

Skipped the cellular service activation as nothing happened.

Connected WiFi.

Connected Google account.

Set up as new device. Google Now.

Then just installed aLogcat as soon as I got in and played around, but got the errors continuously. Triggered I think by the screen timeout. I honestly have no idea where the logcat file is now :mad:
[Galaxy S 4 i9506 Android Development] puschel_1:
So, tested several days, no further reboots. Once I had a black screen and it was not possible to turn on. Reboot helped.

So are the changes now also in official nightlies included? So I would change from unofficial to official ?

Thanks for good work!

Gesendet von meinem GT-I9506 mit Tapatalk
[Galaxy S 4 i9506 Android Development] DualJoe:
Try 'monitor.bat' (DDMS) from Android SDK.

See here: http://xdaforums.com/showthread.php?t=2304122
[Galaxy S 4 i9506 Android Development] solk2:
Yes. It is in official repo now. Black screen happens sometimes when phone is on heavy load. Usually it goes back to normal when load is lower. I had this when i was formatting sdcard. But when format is finished it turned on normally.
[Galaxy S 4 i9506 Android Development] awicks:
I have just made a clean install of 1218 and an having the issue where the clock is wrong on reboot. Is there any way to fix this?

Thanks.
[Galaxy S 4 i9506 Android Development] hal2100:
How does this "black screen" look? Like the error posted by me in the QA section? If it is this happens if I want to unlock the phone, that should not be heavy load...

The only way to unlock was to reboot, and this happens at least once a day.
[Galaxy S 4 i9506 Android Development] boart:
I was reading that it is a snapdragon bug. Correct me if im wrong

Edit: Ok, seems as if i was wrong :P
[Galaxy S 4 i9506 Android Development] NZgeek:
Have a look in your /system/bin folder for a file called time_daemon. If it's there, delete it. Your time should stay correct on reboot.
[Galaxy S 4 i9506 Android Development] awicks:
I have tried this, and the time just resets to a different time on reboot - still not the correct one :(
[Galaxy S 4 i9506 Android Development] joshkun:
Maybe it's the custom recovery problem I'm using the latest twrp under settings set time zone to the right one and do a clean flash.

I have no time problem like you
[Galaxy S 4 i9506 Android Development] solk2:
This is pretty strange. As time_daemon and libtime_genoff.so wasn't changed after I've fixed time. Look into /data/time. If there any ats_* files? Also which baseband you have?
[Galaxy S 4 i9506 Android Development] solk2:
No. Screen wasn't turning on. Most likely coz it didn't get in time till auto-lock timer expires coz of heavy IO.

So which issue you have exactly like in QA or like I've described?
[Galaxy S 4 i9506 Android Development] solk2:
So anyone was able to get logcats. As mine device is dead so I can't debug it myself.

Need another 60$ to order new panel from ebay.
[Galaxy S 4 i9506 Android Development] awicks:
There is an ATS_1 and a time_log.1 file.

Baseband is I9506XXUBMK7.
[Galaxy S 4 i9506 Android Development] solk2:
Try updating to I9506XXUBMJ2
[Galaxy S 4 i9506 Android Development] awicks:
What's the best way to upgrade the baseband?
[Galaxy S 4 i9506 Android Development] hal2100:
Like in the QA, here: http://xdaforums.com/showpost.php?p=57559393&postcount=28

But I am not sure what exactly is crashing/not starting. I also saw this black clock screen sometimes for a split second when I was waking the phone, but then the background and the normal lock screen appeared. So sometimes they don't appear, or are not shown, then I have to reboot.

Funny enough, if I have this error, I can still tap on the spot where the weather icon would be, and the weather screen starts (phone still locked). Exiting the weather lock screen widget returns to the black clock screen.

On Windows I would say that the draw order of the windows is wrong, and the lock screen seems to be behind this strange black screen, but on Android...

Do Logcat logs survive a reboot?
[Galaxy S 4 i9506 Android Development] solk2:
The best way is to wipe. Flash full stock. Boot into it. Look into properties so that status is set to official. And then flash full stock once again. Thats the only way modem is updated correctly.
[Galaxy S 4 i9506 Android Development] solk2:
This more looks like userspace problem. And if no one else having this problem then its not ROM issue. Post logcats(system and main). I'll look into it.
[Galaxy S 4 i9506 Android Development] awicks:
I flashed back to I9506XXUCNG3 stock and when I re-installed a custom recovery (TWRP) the time displayed in recovery was correct.

However, after installing 1218 the time was reset back to midnight 1st January 2014 in recovery and in the ROM itself. I have tried switching it into airplane mode, setting the time correctly and when rebooting, but it just resets back the time before I updated.

I have also tried updating the time and then removing time_daemon, but upon reboot this just resets the time to 20 minutes ahead, but on 26th July 2014. (that is the last modified date on /data/time/ats_1 and the date/time in time_log.1)

This wouldn't be much of a problem, if Whatsapp didn't keep warning me that my phone time is incorrect and Google auto-back also keeps telling me that I haven't synced for a long time.

Any other suggestions?
[Galaxy S 4 i9506 Android Development] solk2:
You definitely shouldn't remove time_daemon. Try to remove /data/time directory, reboot, set auto time and auto zone and reboot. If this won't help. Post logcats right after reboot.
[Galaxy S 4 i9506 Android Development] solk2:
CM-12

Here is new CM-12 build: cm-12-20141223-UNOFFICIAL-ks01lte.zip
[Galaxy S 4 i9506 Android Development] TonskuDaigle:
No permission to download the file?

EDIT: Now it works.
[Galaxy S 4 i9506 Android Development] awicks:
I replaced time_daemon, removed the /data/time directory and rebooted. It rebooted with a time of 00:00. I set time/date to auto and rebooted again. The time was just after 00:00 and then reset to network time. It does appear to have replaced the /data/time directory.

I have attached (a cut down version of) my logcat - hopefully there is something useful in there. It might show two reboots - I am not too sure.
[Galaxy S 4 i9506 Android Development] joshkun:
Very nice job :good:, some feedback : Boot's fine but starts with too many FCs, setting stop, activating cellular service not working, under settings display and security not working.
[Galaxy S 4 i9506 Android Development] solk2:
Please post logcats.
[Galaxy S 4 i9506 Android Development] boart:
Hi solk. Dont you think a cyanogenmod 12 thread would be a good idea? And if you need help until your device is repaired: just pm me and i will try flash and send you the logs.

And merry christmas
[Galaxy S 4 i9506 Android Development] solk2:
Ok. And what now is happening when you reboot? Post logcat after this reboot if time is incorrect. As looking thru this logs it looks fine.
[Galaxy S 4 i9506 Android Development] solk2:
I'll make this. Maybe tomorrow. By the way here is another build: cm-12-20141224-UNOFFICIAL-ks01lte.zip. Its better that everyone could test it.
[Galaxy S 4 i9506 Android Development] awicks:
It appears to be working fine on reboot - it is flashing that is causing an issue.

On flash it seems to reset system time back to midnight on 01/01/14.

On reboot it loads the system time and then, once connected to a network, updates it to the correct time. If the system time was correct it would be fine.

When I flashed stock it set the system time to the correct time, but when I flashed 1218 it reset. This shows in recovery before I boot into the new ROM for the first time.

I would guess that any number of logcats I post from rebooting it will only show everything working. Is there anyway to get a logcat of when I flash a new ROM?

Andy
[Galaxy S 4 i9506 Android Development] boart:
Here is my logcat... did it the first time with this command, hope it helps:

adb logcat -v long > logcat.txt

Is the long version ok? Or do u just need the shorter version?

Bugs i recognized so far:

Camera doesn't work

No mobile network can be accessed

under settings display not working... but security is working in this build!!!
[Galaxy S 4 i9506 Android Development] DualJoe:
Which recovery are you using exactly?
[Galaxy S 4 i9506 Android Development] awicks:
I have tried a couple - currently TWRP.