yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9506 Android Development] frenchbeard:
Hi guys,

I think we might have another (bigger) problem than simply any LED not working, regarding the latest StageFright vulnerability that was discolsed to Google last week, since no nightly build seems to be coming our way.

I wonder what the overall policy regarding security issues such a this one would be in cyanogen : all devices running AOSP based ROMs since 2.2 may (should) be vulnerable to the exploit itself, an not everyone has the possibility to deactivate MMS through their carrier, not to say directly on their devices.

I haven't seen anything from the community as a whole yet, but people still running ROMs that are not built anymore will also want that vulnerability fixed.

Has anyone of you been there while a massive security issue such as this one emerged, and can tell me what Cyanogen's reaction to it was ?
[Galaxy S 4 i9506 Android Development] flaektrem:
I dont understand, whats the problem?
[Galaxy S 4 i9506 Android Development] frenchbeard:
As a new user I cannot post external links yet, but just look up Stagefright, it even got to "classic" press today (and as will be presented in a couple of days at the Black Hat conference in Amsterdam). As a quick explanation, there is a vulnerability existing in the lib named stagefright that handles media in Android, that would allow a simple preview of a crafted MMS containing a video (as a notification would do) to execute malicious code directly on the device.

The vulnerability has been there since SDK 2.2 (quite a while now), and should be a concern for around 95% of devices in the wild, even though Google released a bugfix for all its devices, as long as it is not ported to Cyanogen and we don't have any more nightly, we will keep this huge security hole (thus my concerns and my previous question).

The thing being, even with a stock ROM, there's no guaranty that you will get an update any sooner, especially on old devices.
[Galaxy S 4 i9506 Android Development] MrKalach:
But solk gone, and anybody don't know when he'll come back.
[Galaxy S 4 i9506 Android Development] solk2:
Back. Updated device to cm12.1. Also looks like found root cause of reboots. Should be fixed in cm12.1. At least using for 35 hours without issues. But don't have much time to maintain device further. Will try to keep it in working state, maybe something more (like Doze, livedisplay) if there will be some free time.
[Galaxy S 4 i9506 Android Development] MildlyRegularPerson:
Sounds great. Really looking forward to installing.:D
[Galaxy S 4 i9506 Android Development] morben2:
Really happy to see you again. Hope you'll find some time to build a final release of CM11, even if NeuDLi is doing great. Thanks for all your efforts.
[Galaxy S 4 i9506 Android Development] MrKalach:
Welcome back! :good:

Can I install night builds of CM12.1 over latest stable cm12.1 from arte?
[Galaxy S 4 i9506 Android Development] MildlyRegularPerson:
I don't think so as they need different kernels. You could try and tell us the result tho.

Enviado desde mi GT-I9506 mediante Tapatalk
[Galaxy S 4 i9506 Android Development] flaektrem:
Anyone updated to latest 12.1 and everything working?
[Galaxy S 4 i9506 Android Development] Hobb:
Just updated from CM12.

Initially got problems with Google Play Services FC after boot and Google Play not working but I flashed latest GApps and those were gone. After flashing GApps I got some problems with the Clock app but those were also gone after removing and reinstalling it.

Besides those two hiccups, which are probably logical due to the jump from 5.0 to 5.1, everything is working pretty well so far and it even feels snappier.
[Galaxy S 4 i9506 Android Development] MrKalach:
Just updated, seems work fine. Also root works(supersu).
[Galaxy S 4 i9506 Android Development] flaektrem:
I also updated to 27nd and everything seems to be fine except a couple of random reboots so far.
[Galaxy S 4 i9506 Android Development] zardak:
Not stable. I've got some reboots too and some FCs at startup. Also init.d is not working.

I saved three last_kmsg just in case someone is able to troubleshoot this, i'll send if asked for.

Anyway, is a lot faster than touchwiz.

Noob question: Are these reboots harmful? I mean, do they corrupt data? I'm asking because I always read "No errors detected" on last_kmsg
[Galaxy S 4 i9506 Android Development] leo_bsb:
I've got a lot of random reboots in the last hours.

I can say it is not stable.

Wifi still a problem, sometimes it does not turn on after a restart.
[Galaxy S 4 i9506 Android Development] MrKalach:
I've got just 3 reboots after update. Wi-Fi works fine.
[Galaxy S 4 i9506 Android Development] Hobb:
After a couple of days I have not had a single reboot yet but I am having problems with applications not receiving notifications (WhatsApp).

This did not happen before in CM12, I do not receive any notifications or messages until I open the application.

I have tried to force the WiFi whilst on sleep with wifilock without luck, I have seen some threads mentioning similar problems with CM12.x hinting that it can be IPv6 related.

Any idea?
[Galaxy S 4 i9506 Android Development] solk2:
Which kind of reboots? Soft reboots or hard? Basicly do you see Samsung logo after this reboot or CM immediately after this reboot and do uptime is reset? If its soft reboot please post latest tombstone from /data/tombstones (better look by date and not number) and your baseband version. Coz there was problems with LL GPS blobs. So it can be that baseband needs to be updated as I can't reproduce this.

FCs is not a problem of ROM. Try clean install with latest CM gapps.

WiFi BTW can be stalled coz of such soft reboot coz of file locks.

Init.d support was dropped in CM I think. Can't say for sure.

Soft reboots shouldnt cause any issues with data as kernel is still running and finishing writes to FS. Hard can be if there was some unfinished writes.

Well I have Skype behaving similar. While Facebook messenger works fine no matter what.

Skype have this problem even on iPhone. So most likely this is an app issue rather than ROM.
[Galaxy S 4 i9506 Android Development] MildlyRegularPerson:
[MENTION=5291759]solk2[/MENTION] Since I updated the rom my device keeps soft rebooting, but I don't think I have had any hard reboots.

Enviado desde mi GT-I9506 mediante Tapatalk

---------- Post added at 09:34 AM ---------- Previous post was at 09:33 AM ----------

I will make a new post with tombstone file when I get home.

Enviado desde mi GT-I9506 mediante Tapatalk

EDIT: I've just had a hard reboot. Will post last_kmsg too.
[Galaxy S 4 i9506 Android Development] zardak:
My reboots were all HARD reboots with Samsung logo like when you are powering on the device.

Another strange behavior: when a call is received the whole phone starts lagging like hell and you can't even answer nor reject. It goes normal as soon as the call ends. In this situation I once got a soft reboot.
[Galaxy S 4 i9506 Android Development] Hobb:
It was working fine with the last CM12.0 nightly and it stopped working when I moved to CM12.1, I think is related in some way to the WiFi because it doesn't happen at all when I am on mobile data. If it was the application's fault it wouldn't work regardless of the type of connection used, I imagine.

I have tried forcing the wifi with Wake Lock but it doesn't seem to help.

Is there any log I can send you to help tracking this issue?
[Galaxy S 4 i9506 Android Development] solk2:
That's why it looks like baseband not compatible. Try updating to I9506XXUDOF2.
[Galaxy S 4 i9506 Android Development] solk2:
Looks like whatsapp not handling connection tracking events correctly on android 5.1.1. Thats why they should fix it and not Google or CM. Even more if other apps works fine but this one fails then its defenitly their fault and not ROM.
[Galaxy S 4 i9506 Android Development] zardak:
That's exactly my baseband though.

Actually the calls works fine, if I only manage to get past the lag and answer it..
[Galaxy S 4 i9506 Android Development] solk2:
That's really strange. I need logcats to analyze it (radio and main).

Meanwhile you can try to delete /data/property and update to latest nightly. As there was similar issue with "OK Google", huge lags caused by noise suppression.
[Galaxy S 4 i9506 Android Development] zardak:
Folder deleted. ROM Updated to 31 Aug same problem.

Here the logs radio and main separated (I did two calls)
[Galaxy S 4 i9506 Android Development] solk2:
I see violations on accessing some sqlite db that's seems coming from xposed framework. And lags i assume coming coz of stacktraces regarding it. Try to remove it or better clean install and we will see if it happens on clean ROM.
[Galaxy S 4 i9506 Android Development] zardak:
Removed xposed and seems not to be its fault, i'll wipe and reflash, but before that I have a question: it is possible to disable mobile data before starting a clean install? Looks like CM is bugged because it automatically connect to mobile data at first startup and THEN ask if I want to use it instead of wi-fi. It results in money being wasted.

I've just got a soft reboot while call incoming. I've uploaded the last two tombstones (they had the same timestamp and couldn't tell which was the right one)

I also noticed tombstones mention I9506XXUDOA6 at top, but I'm pretty sure i'm coming from a I9506XXUDOF2 stock ROM. "About phone" confirms its DOF2 too
[Galaxy S 4 i9506 Android Development] solk2:
Just get sim card out of phone and you will defenilty won't use mobile traffic.

You defenitly have something wrong with art and/or cache. So its data problem.

UDOA6 is just a build fingerprint. This is doesn't matter.
[Galaxy S 4 i9506 Android Development] MildlyRegularPerson:
[MENTION=5291759]solk2[/MENTION] , here are my latest last_kmsg and tombstone files(0829 version):
[Galaxy S 4 i9506 Android Development] solk2:
Time_daemon constantly restarts most likely coz of selinux denials which is fixed and will be included in today's build. But soft reboot coz of GPS crash, maybe coz of time_daemon or maybe something else, will look into it.

Which baseband you have?

Hard reboots looks like happening coz of mdss dsi clocks lock. This should be fixed in latest build.
[Galaxy S 4 i9506 Android Development] MildlyRegularPerson:
My baseband is I9506XXUDOD3. Do I need to install another one?

Enviado desde mi GT-I9506 mediante Tapatalk
[Galaxy S 4 i9506 Android Development] solk2:
Better to use UDOF2 as binaries from that version is used. But first install new version and delete /data/time dir.
[Galaxy S 4 i9506 Android Development] MrKalach:
Another bag, GPS doesn't work at all. Can't see adb log now, but using gps test or google maps reboots the phone.
[Galaxy S 4 i9506 Android Development] solk2:
Using GPS without any problems. Which baseband?
[Galaxy S 4 i9506 Android Development] boart:
In my side running for more than 24 hours now. GPS working. BT connected with car will be tested monday

Gesendet von meinem GT-I9506 mit Tapatalk
[Galaxy S 4 i9506 Android Development] MildlyRegularPerson:
Done! Now running for almost 24 h without any issue. Reboots seem to be solved.

EDIT: Just had a hard reboot. Soft reboots have been solved tho. Here's my last_ksmg file:
[Galaxy S 4 i9506 Android Development] solk2:
Try today's build. There was race condition that can cause this. BTW there some app constantly crashing on your phone.
[Galaxy S 4 i9506 Android Development] MildlyRegularPerson:
Actually exchange services app was constantly crashing, so I had to manually configure my outlook account.

Enviado desde mi GT-I9506 mediante Tapatalk
[Galaxy S 4 i9506 Android Development] Frosti1:
Hey can somebody tell me. Does official CM 12.1 run stable? Does it have 4k video? and does nfc,bluetooth and gps work? thank you for reply :)
[Galaxy S 4 i9506 Android Development] zardak:
NFC: ok, but slow on/off

BT: ok

GPS: ok

BT device paired with NFC: bad, lose connection after some time

4k: bad, lag and no difference in video size compared to 1080p

Not very stable, random reboots still happen (7 sep build) but is usable. Better than TW
[Galaxy S 4 i9506 Android Development] solk2:
Didn't noticed that. Turns off in aprox 1 sec maybe less. And turns on in something like 1-2 secs. Pretty same on other devices i have.

What do you mean by "paired with NFC"? BT/NFC turned on together or Android Beam?

It is very slow when you are using SD-card to save videos and works pretty fine when saving to internal storage. And I just tried it and difference in size something like 4 times.

Please post last_kmsg if you had a reboot.
[Galaxy S 4 i9506 Android Development] zardak:
Well, then it's ok I guess. On stock ROM NFC on/off is much faster. Not a real problem though

I have a BT speaker with NFC tag which is used to pair it with the phone automatically. If I use this instead of manually pair with BT settings, after some time BT goes off. I have widely used NFC this way on stock touchwiz rom and didn't experienced this issue.

Concerning Android Beam I didn't manage to get it working, I have tried some times with another device without success.

I was wrong with the size, the camera app I used to test 1080p and 2160p reported almost same size. App fault probably.

Now I have done some tests with the stock camera app using internal storage and yes, the sizes are different, here two sample video: http://www74.zippyshare.com/v/03hZSaUq/file.html

Basically 4k runs at 15FPS and refuses to focus, both auto and manual (touch). Also google camera app FC when 4k recording starts

1080p runs good at 30FPS. I see no options for 60FPS though.

I had 2 reboots lately, and both happened a short while after I have unplugged the phone from a 100% charge, I have no idea if this is related (two last_kmsg attached)

Also Screen Cast is not working. Tested with two samsung TVs. It used to work on touchwiz (Maybe this is CM fault)
[Galaxy S 4 i9506 Android Development] solk2:
Actually it can be just animation and not real turn on.

Hard to say what causing this. But it may be general cm issue in this case. Need logs to see whats happening here. Android Beam isn't user friendly at all. But I was able to use it.

That's what hardware capable of and what present in Samsung camera driver. Not much can be done here.

Trying to fix this. Please report if this happens in builds from 20150909.

Screen cast is Samsung feature and not implemented in CM. There present some other screen mirroring system (don't remember how its called). The one from Google.
[Galaxy S 4 i9506 Android Development] MildlyRegularPerson:
Another reboot here on 07 build.
[Galaxy S 4 i9506 Android Development] solk2:
As always nothing in this log. Anyway try newer build. In this log only some app constantly crashing.
[Galaxy S 4 i9506 Android Development] superpulosu:
The last nightly 09 its working perfect. For now no FC and no reboots. And battery life seems ok.
[Galaxy S 4 i9506 Android Development] zardak:
There is something wrong with the new builds > 07 sep. Device keep bootlooping randomly on CM animation when restarting phone or when trying to upgrade or even on clean install!
[Galaxy S 4 i9506 Android Development] solk2:
I dont have such issue. Anyone else have it?

Post logcats. Maybe wrong gapps or maybe some broken media file (audio,video,photo) on sdcard.
[Galaxy S 4 i9506 Android Development] boart:
As mentioned by superpulosu: 09 build works great. No reboot since i installed that version. [MENTION=5291759]solk2[/MENTION]: Did u find a bug in the version <09 ?
[Galaxy S 4 i9506 Android Development] solk2:
Looks like the root cause was ksm. Which most likely caused some memory corruption in video buffer as there was some logs regarding error in kgsl and this reboots was triggered by scrooling.

There was some missing commits to memory management which fixed this.
[Galaxy S 4 i9506 Android Development] MildlyRegularPerson:
So will we get a stable M build soon?

Enviado desde mi GT-I9506 mediante Tapatalk
[Galaxy S 4 i9506 Android Development] DualJoe:
[MENTION=3646343]NeuDLi[/MENTION] already disabled KSM on CM11 without success.
[Galaxy S 4 i9506 Android Development] solk2:
Beside ksm there was problems with qcrypto that was fixed earlier.
[Galaxy S 4 i9506 Android Development] solk2:
I am not planning to push anything more currently, so maybe.
[Galaxy S 4 i9506 Android Development] zardak:
Looks like it was SuperSU fault, without now it boots. The weird fact is that bootlops does not happen every boot
[Galaxy S 4 i9506 Android Development] zardak:
Bad news...

I got two corrupted last_kmsg using 11 sep build.

Also, manual reboot (both in system and in recovery) generate each time a last_kmsg.

Also, just got a random reboot while scrolling a webpage
[Galaxy S 4 i9506 Android Development] solk2:
Well. Last_kmsg is generated after each reboot with dmesg of previous. So that's normall.

But corrupted last_kmsg is really weird and actually can be caused by some hardware failure or maybe ksm. Anyone else had something similar or at least reboots?

Edit: Are you using CM recovery?

And did phone was rebooted from normal mode to normal mode? As corrupted last_kmsg may be caused by booting non cm kernel or download mode.
[Galaxy S 4 i9506 Android Development] superpulosu:
I got one reboot while scrolling a webpage.

Edit: when I watch online videos the buffering its taking soo much time...
[Galaxy S 4 i9506 Android Development] boart:
I am still on build from 9th september. Still no reboot, but i will go on checking.

Videobuffering on webpages was tested just a minute ago, it was smooth and no buffer problems.

I did make a full wipe of my device before installting 09 build and i am using twrp btw.
[Galaxy S 4 i9506 Android Development] zardak:
Yes, normal mode to normal mode, there was no SAFE MODE text.

I didn't flash any kernel, just the CM zip, but I use TWRP (not the official one, but one I found in a thread here on XDA)

I'm not using download mode since I've rooted long time ago.

Corrupted last_kmsg appeared after simple manual power off and on (not auto reboot), recovery was not involved.

I can't say there was a particular event causing this, because I was using the device as usual, and is not even too much bloated since I did a new clean install with the build.

EDIT:

I think that Doze/Ambient Display besides not working properly (double tap on screen? wake up on notification? lift to wake?), is eating battery. When screen and Wi-Fi both OFF it eats ~1% per hour. After a night I see -10% battery. I remember having very good standby battery with previous builds.

Also, in my opinion this feature is completely useless because we have a physical home button.

EDIT 2:

Meh.. Here two more last_kmsg.

The first one is after a reboot happened when I was scrolling a webpage (again, the same webpage).

The second one is after a reboot happened shortly after I took the first last_kmsg: I was using the terminal e I was scrolling the output.
[Galaxy S 4 i9506 Android Development] solk2:
Powering off explains corrupted last_kmsg as it kept in RAM.

Also twrp can errase it also as I don't know which kernel it uses.

Doze have nothing to do with double tap to wake. It only shows notifications in low power screen mode. And I don't see much power drain on mine device. 9% android system and only 1% screen. Something like 3-5% over night.

Will try to disable ksm and we'll see what will happen.
[Galaxy S 4 i9506 Android Development] hs911:
happy to have you back solk2.

since activity is back on this project, i try to ask again for a favor:

could some please upload the following files from thisbuild?

/system/etc/mixer_paths.xml

and

/system/lib/hw/audio.primary.msm8974.so

or tell me a way to extract these files from firmware image
[Galaxy S 4 i9506 Android Development] solk2:
mixer_paths.xml you can take from device tree and audio hal can be compiled with cm or you can get them from system partition from device. As format of images in LL is changed and I don't know how to extract it from image directly.
[Galaxy S 4 i9506 Android Development] zardak:
Still rebooting on 13 sep build with KSM off
[Galaxy S 4 i9506 Android Development] flaektrem:
MMS doesnt work except when im on wifi.

Ive tried everything with the APNs.

Also mobile data disconnects every 5-10 min and i have to turn off and on mobile data to make it work again.

It have been like this many many nightlies now.
[Galaxy S 4 i9506 Android Development] solk2:
Then its not ksm. Post kmsg maybe something will be there this time.

Interesting that some users report that they don't have any reboots and some have. So please post baseband also and tell if phone was hot or not just before reboot?

Maybe its qcrypto. As two qcrypto devices causes phone to reboot same way but in first 10-15 mins. Worth trying disabling it.

I will post link to test build to try later.
[Galaxy S 4 i9506 Android Development] solk2:
Please post radio, main logcats and tell which baseband you have.
[Galaxy S 4 i9506 Android Development] flaektrem:
Im not on that phone now, will do that later. Thank you
[Galaxy S 4 i9506 Android Development] solk2:
Link to test build with disabled qcrypto device. Please test.
[Galaxy S 4 i9506 Android Development] boart:
Still on build from 9th September. Device running for 110 hrs without reboot. No WiFi or Cellular problems. I use BT in my car and got no errors, too. I will still keep on going testing.

Only problems seem to be microstutters from time to time. Ill try to post my logs soon.

But from my side a big compliment to solk!!!!
[Galaxy S 4 i9506 Android Development] DualJoe:
I think it goes like this. Binaries are in post #2 and #3.

http://xdaforums.com/android/software-hacking/how-to-conver-lollipop-dat-files-to-t2978952
[Galaxy S 4 i9506 Android Development] zardak:
Just to make it clear, every single reboot that I had until now with CM has the following characteristics:

- Screen freezes for about 5-7 seconds

- Any audio playing is immediately interrupted before the freeze without any distortion

- The moment it reboots itself some blue stripes can be seen in the screen for a bunch of milliseconds, then SAMSUNG logo appears

So I had two of them with KSM off: one while scrolling something and the second while playing a video on youtube with headphones without touching the display.

I forgot. I am using I9506XXUDOF2, but can't tell if it was hot, this phone is often hot.
[Galaxy S 4 i9506 Android Development] superpulosu:
Me too on the 09 build, for 5 days and had only one reboot when scrolling a web page. Online video buffering resolved, changed hw decoder to sw in mx player and working great. Only one app ( Sygic) have some random FC.

Great work [MENTION=5291759]solk2[/MENTION]
[Galaxy S 4 i9506 Android Development] flaektrem:
Radio: I9506XXUDOD3 / b260b2c6

Baseband: I9506XXUDOD3

How do i attach the log?
[Galaxy S 4 i9506 Android Development] solk2:
Just make zip or rename logs to .txt extension and attach here or send them to my gmail.
[Galaxy S 4 i9506 Android Development] flaektrem:
I can only attach pics, no files. Maybe because i use tapatalk. Your email?
[Galaxy S 4 i9506 Android Development] solk2:
Its in first post of this thread.
[Galaxy S 4 i9506 Android Development] zardak:
Reboot on Test build too!
[Galaxy S 4 i9506 Android Development] hs911:
this worked perfectly. thanks!
[Galaxy S 4 i9506 Android Development] solk2:
Then its not qcrypto. Another test build. Not touching gpio keys when blanking/unblanking screen.
[Galaxy S 4 i9506 Android Development] zardak:
Already testing this one too, will report if something happens.
[Galaxy S 4 i9506 Android Development] boart:
Same here. I had on 9th September build one reboot finally.

Testing the new build now.

Gesendet von meinem GT-I9506 mit Tapatalk
[Galaxy S 4 i9506 Android Development] zardak:
[MENTION=5291759]solk2[/MENTION]

I've just had a reboot, but this time it was different: the device didn't boot anymore, it was stuck at CM animation boot for about 5 minutes until I forced to reboot again...
[Galaxy S 4 i9506 Android Development] solk2:
Him. Interesting. Last_kmsg? And is phone was hot or not?