yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] sronweb:
[MENTION=2385005]invisiblek[/MENTION],

I wonder if currently the developer or rom mainteiner for S4 need people to test the nightly to report about the random reboots issue or sending logs or they know already the basic information to investigate. I suppose should be possible to indentify which day the issue has started and which commit is the "guilty". Just to know. Sorry if I miss some information on this thread.

Thanks
[Galaxy S 4 i9505 Original Android Development] !crazy:
For people who switch to M9 because of stability, you can also use the nightly of 6th of Aug, it is rock stable, and has a newer code base.
[Galaxy S 4 i9505 Original Android Development] patrik@xda:
So apparently GoogyMax kernel doesn't work on M9 if you flash the OnePlusOne conversion kit, the phone doesn't boot, could just be me, did maybe someone get another kernel working? Thank you for your response :)
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
jus got my first random reboot on 817 nightly ( default kernel, SwiftKey keyboard.)
[Galaxy S 4 i9505 Original Android Development] s3icc0:
I am still on 0813 nightly and 99% of the reboots happened when typing (aosp keyboard and FLEKSY) going to update and send last kernel message

Anyway - I have problems flashing updates. I did a clean flash (stock TW recovery root then cm11 the 0813 nightly) and now I am not able to flash new nightlies. I already changed recovery, but that is not the problem. I get a log from Philz:

-- nstalling: /sdcard/cm-11-20140817-NIGHTLY-jflte.zip
I:skiping set_bootloader_message: no /misc
Finding update package...
I:Update location: /sdcard/cm-11-20140817-NIGHTLY-jflte.zip
Opening update package...
Installing update...
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: Device or resource busy
about to run program [/tmp/otasigcheck.sh] with 1 args
You have an installed system that isn't signed with this build's key, aborting...
run_program: child exited with status 1
script aborted: Can't install this package on top of incompatible data. Please try another package or run factory reset

Any suggestion??? I know full wipe will help but I do't want to full wipe if possible (I did it like 10 times over past 2 weeks trying different ROMs and you know how this activity sucks)
[Galaxy S 4 i9505 Original Android Development] invisiblek:
If anyone can give me a consistent way to reproduce it, that's about the best information I can hope for right now. The reboots are so random and spaced apart that anything we try to do to fix it, can't be proven right or wrong for at minimum a day. This, as you can imagine, is incredibly time-consuming.

Little background. It's not just a matter of reverting one commit, this particular issue is a side effect of the new kernel base we switched to shortly after the M9 release. We had two reboot bugs (at the time we thought only one). We fixed one (the one that was reproducable within 10-15 minutes), and didn't have reboots for a day or two and said "ok, shipit!". Later we learned we had this other one and its quite a bit tougher to nail down, because we can't make it happen very often. Logs are all the same, its always failing at the same spot, so none of that's really of much help to us.

Rest assured its being worked on. I have some ideas too, but as I said testing is slow because of the nature of this bug.

If you want it stable, stick the M9 (or whatever nightly people are saying works).
[Galaxy S 4 i9505 Original Android Development] sronweb:
Thanks for this important information about the debug status and in general I will install the nightly for testing purpose and hopefully to provide logcat or scenario information.
[Galaxy S 4 i9505 Original Android Development] jumpers:
1.1.5 version is for newer roms, you need the 1.1.4 version to boot on the M9.
[Galaxy S 4 i9505 Original Android Development] invisiblek:
Experimental build here: <bleh, failure, hold tight, will get something else out>

Need testers, report back if you get any reboots (with a /proc/last_kmsg too please)

Do NOT flash anyone else's kernel over this or it completely defeats the purpose of the test.
[Galaxy S 4 i9505 Original Android Development] Kmailknopf:
Link?

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] sronweb:
I guess he mean the official development channel:

http://download.cyanogenmod.org/?type=nightly&device=jfltexx
[Galaxy S 4 i9505 Original Android Development] feraay:
https://download.cyanogenmod.org/get/jenkins/80238/cm-11-20140817-EXPERIMENTAL-MSM-jflte.zip

There u are ^^

Edit :

Sry dont use:

Just wait
[Galaxy S 4 i9505 Original Android Development] Kmailknopf:
Down?

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] invisiblek:
Sorry about that guys, yea, don't flash that experimental rom, you wont get display =P

Here's one to test for real: http://www.invisiblek.org/roms/cm-11.0/jflte/cm-11-20140817-UNOFFICIAL-jflte.zip

last_kmsg from a crash if you get one please!
[Galaxy S 4 i9505 Original Android Development] ZaRBoR2:
Any idea?
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
817 nightly last kernel. 3rd reboot, while using dolphin browser. default kernel. SwiftKey keyboard.
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
which nightly? i had that problem a few nighlies ago, but it went away with latest nightly. also did u wipe cache wipe Dalvik after flash ur ROM?
[Galaxy S 4 i9505 Original Android Development] invisiblek:
Although I probably appreciate logs more than anyone else here, these are all the same at this point. Please try the build I posted a posts up. If you can manage to get a reboot with that build a log could be VERY helpful.
[Galaxy S 4 i9505 Original Android Development] jumpers:
going to try this tomorrow if i have the time. (if it's not too late for a diagnose.)

GSM version of the S4 have the same issues, reported on Cyanogenmod's forum. not only the LTE variant : http://forum.cyanogenmod.org/topic/98350-reboots-randomly-when-apps-are-under-heavy-load/
[Galaxy S 4 i9505 Original Android Development] dmb219:
I'm using the last build you posted (the 1st one didn't go well:p) and it has been running very well so far, have a couple hours of screen time. If that changes I'll let you know. The last time I had a nightly with the new kernel installed it took 2 days for it to reboot. Thanks for your work on this.
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
No problem. downloading now. will test again .

edit: 817 unofficial download taking me ages and 818 nightly out already. will try test both.
[Galaxy S 4 i9505 Original Android Development] 78Staff:
Is there an 0806 nightly for jflte - I don't see it on the d/l page...
[Galaxy S 4 i9505 Original Android Development] 1PATRIK:
You can use xx version.
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
agree. can someone please share link of the 806 nightly?
[Galaxy S 4 i9505 Original Android Development] 1weener:
Running great so far; 5 hours/2 hours screen.
[Galaxy S 4 i9505 Original Android Development] s3icc0:
Hi,

got 2 last_kmsg from random reboots on 0813 nightly both happened when NOT typing.

I have a clean installation with gapps - no 3rd party things.
[Galaxy S 4 i9505 Original Android Development] ZaRBoR2:
Meanwhile, thank you for having responded to me, and I did it anyway even now but the problem persists ...
[Galaxy S 4 i9505 Original Android Development] nommy:
Trying hard to get a rr, but no success since hours [emoji6]

Looks really stable so far...

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] sronweb:
Installed this morning. No reboots so far.
[Galaxy S 4 i9505 Original Android Development] s3icc0:
Is this test build differencies already merged into 0818 nightly?

And one more question:

I did a clean install and flashed 0813 nightly, but for updating recovery is requesting me to perform factory reset. I did factory reset flashed 0817 nightly. Now I am going to flash 0818 nightly but I still cannot flash new nightlies from the same reason.... no dirty flashing for me - why the hell?
[Galaxy S 4 i9505 Original Android Development] NZgeek:
Please note that you won't get support for any random reboot issues if you're using a custom kernel. The CM team don't control the kernel's code, which makes it impossible to verify that CM code is the source of the problem.

A perfect example of this in practice: the quote below, in regard to a fix for the random reboots.
[Galaxy S 4 i9505 Original Android Development] aleksik:
Yea, I know that. I just wanted to report my experience to other users, because I'm sure there are people using the same kernel. I'm sorry if that was inappropriate.

Sent from my GT-I9505 powered by SlimSaberKat & alucard kernel
[Galaxy S 4 i9505 Original Android Development] nadejo:
i must say that i had more reboots using the stock kernel . and less since googy (after m9)
[Galaxy S 4 i9505 Original Android Development] 78Staff:
jfltexx? That stopped getting updated in Feb...unless I'm mis-understanding your reply... :confused:
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
817 UNOFFICIAL is really stable. did all same actions as before, opening 4 apps plus VPNs plus SwiftKey and browsers.. and NO RRs so far... [MENTION=2385005]invisiblek[/MENTION] seems u guys made the fix :thumbup:
[Galaxy S 4 i9505 Original Android Development] Milamber:
Testing 0817 now, will advise.
[Galaxy S 4 i9505 Original Android Development] lauterm:
I have over 13 hours of up-time so far on the 08/17 UNOFFICIAL too. No reboots or other oddities so far.
[Galaxy S 4 i9505 Original Android Development] mundixx:
Does 8/17 use the new graphics drivers?
[Galaxy S 4 i9505 Original Android Development] valenfrank:
I had multiple reboots with 817 and I've already had one with 818!
[Galaxy S 4 i9505 Original Android Development] Bejda:
Currently requested and expected bug report format is last_kmsg which is the file that mostly matters when it comes to hard reboot (complete device restart).

You can copy it after reboot with a root file manager from /proc/last_kmsg or use terminal emulator app and enter "su" first and then "cat /proc/last_kmsg > /sdcard/last_kmsg" (to grab its content>write it on a named as you want [.txt if you prefer] file on sdcard)
[Galaxy S 4 i9505 Original Android Development] sronweb:
Are you talking about the Experimental version?
[Galaxy S 4 i9505 Original Android Development] bobribbon:
MIC problems

Apart from the occasional reboot (running the latest nightly) I'm still 'suffering' from a (or the) microphone bug. When making a phonecall the receiving party can't hear me apart from some crackling and popping. Did I miss a fix somewhere along the line?
[Galaxy S 4 i9505 Original Android Development] valenfrank:
My bad! I decide to revert to a previous backup (August 3) and I cannot extract any log!
[Galaxy S 4 i9505 Original Android Development] invisiblek:
I'm confident we have a winner here.

All changes have been pushed.

Next nightly will have the goods.

Thanks for all the help testing everyone!
[Galaxy S 4 i9505 Original Android Development] lauterm:
I'm trying to troubleshoot the problems that I'm having with my pebble. I've mentioned this before, but the main issues I have are Runkeeper and NavMe cutting out at random intervals. This doesn't happen with TW or GPE ROMs, but who wants to run those. :P I've done some logcats with Runkeeper on a few different nightlies, but I'm not really getting any useful log messages. All I get in either logcat or the pebble logs are a bunch of:

W/PblAndroid( 1365): Failed to send message: {"endpointId":48,"dictionary":{"instance":"BinaryPebbleDictionary"...

How do I dig deeper? Is there a build time option that I can use to make bluetooth logging more verbose? I'm fairly comfortable with repo sync and the build process. I just don't know enough to find where to make this change.

Thanks!
[Galaxy S 4 i9505 Original Android Development] Stransky:
Hi

On 18/8 nightly and still getting RRs also camera app not working, anyone else have this.

On CM stock kernal w/ART

Stransky
[Galaxy S 4 i9505 Original Android Development] LuigiC6:
Turn off Art and wait until tomorrow's nightly for RR fix.
[Galaxy S 4 i9505 Original Android Development] 1weener:
If you look back a couple of pages you will see an unofficial build posted yesterday. That build fixes the random reboots and will be merged into the official build tomorrow.
[Galaxy S 4 i9505 Original Android Development] Cusa:
Upcoming nightly has an adreno blob fix and I'm guessing that's the fix we've all been waiting for? Is that going to fix the RRs?
[Galaxy S 4 i9505 Original Android Development] DaReDeViL:
Not only. The most important part of the fix is in the kernel where [MENTION=2385005]invisiblek[/MENTION] is reverting gpu msm2 driver to samsung driver
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
for those who want

the stable 817 UNOFFICIAL is here http://xdaforums.com/showthread.php?p=54887268.

also another way to get last_kmesg after random reboot is simply use the free Syslog App from play store. click "last kernel log" > "take log" >done.
[Galaxy S 4 i9505 Original Android Development] nadejo:
Can you include this in your next kernel update?
[Galaxy S 4 i9505 Original Android Development] tomurbanowicz:
May I install nightly builds without full wipe on M9 build?
[Galaxy S 4 i9505 Original Android Development] a103:
I think you could. Take a nandroid just in case things don't go right.

Sent from my Galaxy S4 ? ; Hit "Thanks" if I've helped you.
[Galaxy S 4 i9505 Original Android Development] exynoss:
Yes you can
[Galaxy S 4 i9505 Original Android Development] aHcVolle:
got the same problem since i've got my pebble

i have no idea how to debug this problem :<
[Galaxy S 4 i9505 Original Android Development] aro:
8/17 and 8/18 nightlies make my phone randomly lose gsm connection.

anyone else experiencing this?
[Galaxy S 4 i9505 Original Android Development] Mittaa:
Experienced that on 8/14 (Post # 4626) and reverted to M9 after that.

So I don't know if this still is an issue ?
[Galaxy S 4 i9505 Original Android Development] gadgetuk99:
[MENTION=2385005]invisiblek[/MENTION] trying out 8/19 just installed, be back M9 later if get rr's
[Galaxy S 4 i9505 Original Android Development] JTaylor69:
Still noticing that EE is now displaying as T-Mobile UK or Orange whereas before it'd show simply as EE.

I've also noticed sometimes the signal will drop out until the phone is rebooted - happening on all builds after M9.
[Galaxy S 4 i9505 Original Android Development] gadgetuk99:
[MENTION=2385005]invisiblek[/MENTION] Well can't understand why Ir blaster still not working since 08/04 ,so back to M9 for me (I'm using zappir btw)
[Galaxy S 4 i9505 Original Android Development] rodrigoger:
It looks like today's nightly version (2014-08-19), with all changes, seems very good and "quite stable". Since 7 o'clock, until now, no RR.

Enviado de meu GT-I9505 usando Tapatalk
[Galaxy S 4 i9505 Original Android Development] jumpers:
i use Galaxy Universal Remote, working great on the M9, i give you my feedback (edit of this post) when i update to a recent nightly. (Smart Remote works also on M9)
[Galaxy S 4 i9505 Original Android Development] Cusa:
Smart ir remote doesn't work on this rom even on the 8/19th build that includes all the recent fixes. I'm using the latest version of smart ir remote app.
[Galaxy S 4 i9505 Original Android Development] gadgetuk99:
Good to know thanks
[Galaxy S 4 i9505 Original Android Development] nadejo:
Anyone noticed? Gpu drivers got downgraded
[Galaxy S 4 i9505 Original Android Development] 1weener:
Is it a downgrade to lose the random reboots? The new drivers didn't work. Perhaps they'll get them working soon, but for now I'm glad to have the old ones!
[Galaxy S 4 i9505 Original Android Development] sancho_panzer:
[MENTION=4401279]Capt[/MENTION] , [MENTION=667956]gadgetuk99[/MENTION] Smart Remote is working just fine on M9, I'm using 1.7.7 the last non trashy version. Didn't tried 2.0.4 yet.
[Galaxy S 4 i9505 Original Android Development] jumpers:
got a reboot when watching a picture on snapchat, checked for /proc/last_kmsg, but file not present, i have a lot of files (and WTF folders), but not the last_kmsg file. --'
[Galaxy S 4 i9505 Original Android Development] Beefheart:
Latest nightly?
[Galaxy S 4 i9505 Original Android Development] Cusa:
What do you mean the last non trashy version? I'm using 2.0.3 and it doesn't work for me.
[Galaxy S 4 i9505 Original Android Development] sancho_panzer:
Those guys changed app code, I guess to avoid piracy. Since 1.7.7 all versions gave me bugs or failed completely. But even 1.7.7 failed on some nightlies, however those times was something related to CM.
[Galaxy S 4 i9505 Original Android Development] fortesquieu:
I'm on M9 and tried installing the last few nightlies, they all made my phone lost connection (no data, cell coverage etc). Adding APN didn't work too.

Canadian Bell version (I337M)
[Galaxy S 4 i9505 Original Android Development] jumpers:
yes. but it seems that's only a crisis from snaphchat, got ne reboot since that. hoping it stay stable.

edit : sh*t, another one, when talking on Viber (whriting with swiftkey), RR frequence is less, but i got RR. :(

edit : a tirth one in less than an half hour, same conditions that my first edit, but with ste stock AOSP keyboard, i got the last_kmsg this time, http://bass2style.com/XDA/support/last_kmsg
[Galaxy S 4 i9505 Original Android Development] sronweb:
Please can you provide last_kmsg log?
[Galaxy S 4 i9505 Original Android Development] beastobadness:
The latest version of smart ir remote is 2.0.4 and if you send Color tiger an email they will fix it for you as long as it is kosher. It is a problem only present in custom roms!
[Galaxy S 4 i9505 Original Android Development] Jikul:
Guys, I just flashed M9 on my S4, but my wifi is playing games with me. It connects to a network, but if I go to work or somewhere else, it won't connect to the network there. I have to reboot the phone in order to get a connection again?

Any idea what this may be?
[Galaxy S 4 i9505 Original Android Development] 1weener:
Reflash M9. It should work perfectly.
[Galaxy S 4 i9505 Original Android Development] jcasares:
Yes, moved from 08/02 release to 08/19 and today the phone was almost useless. Losing connection every once in a while, and IMO not because of bad signal because I was static. In any case didn't have any RR so far. :)

And IR is not working either.

Anyway going back to old release.
[Galaxy S 4 i9505 Original Android Development] Jikul:
That's it? I will try that. Should I wipe anything?
[Galaxy S 4 i9505 Original Android Development] Rapalax:
+1 ... Canadian version also
[Galaxy S 4 i9505 Original Android Development] fortesquieu:
Don't wipe, just reflash M9.
[Galaxy S 4 i9505 Original Android Development] 1weener:
No, you shouldn't have to wipe A reflash should do it.
[Galaxy S 4 i9505 Original Android Development] subscope:
I saw your last_kmsg file and i found something strange. Are you using stock kernel or GoogyMax?
[Galaxy S 4 i9505 Original Android Development] haloimplant:
I decided it was time for a clean flash on 8/17...bad timing...

Started over again with M9, then dirty updated to 0819 this morning and things seem to be OK so far.
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
819 nightly for me wifi is fine, GSM fine, and no Random reboots for more than 12+ hours so far (default kernel, SwiftKey, wiped cache and Dalvik after install)
[Galaxy S 4 i9505 Original Android Development] 1weener:
Me too. I haven't had a reboot or other problem since the unofficial *fix* posted on he 17th and then moving to the 8/19 build this morning, and that includes more than10 hours of screen time...
[Galaxy S 4 i9505 Original Android Development] 78Staff:
Went from M9 to 8/19 nightly today, went ahead and did a full wipe - doesn't bother me to do a completely clean install every once in a while... also switched to the previously linked CM Recovery for jflte http://cleanimport.xda/index.php?posts/54680147/ as I had been using TWRP forever... not sure if CM recovery is still required or not, but figured better safe than sorry.

No RR's, no real issues, really. Have noticed two minor things - seems like now I can either have nav bar OR hard buttons, but on M9 we could have both - not a deal breaker just confused me for a bit at first. Also, screen touches seem to have a slight delay vs M9, of course I had different Kernel with M9 (Ktoonsez's ASOP for S4), with custom config, so I may just need to tweak around a bit with the included CM kernel (again, assuming still no 3rd party kernel's compatible yet)...

Overall though, running pretty solid so far...
[Galaxy S 4 i9505 Original Android Development] GianPacayra:
Same issue.
[Galaxy S 4 i9505 Original Android Development] Mittaa:
Same 8/19 seems fine, no RR or missing GSM :good:

But missing my IR blaster (using SmartRemote from TigerColor) ... :cool:

---------- Post added at 10:37 AM ---------- Previous post was at 10:33 AM ----------

Yes used to be fine, but something broke along the road ... no IR on nightly 8/19 :eek:

But can't tell for sure if this have to do with SmartRemote 2.0.4 or CM11 ?
[Galaxy S 4 i9505 Original Android Development] Kmailknopf:
Which Gapps i flashed better with this Rom? PA Gapps OK? Or use a other Gapps-Package?

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] ench18:
PA Gapps is fine. That's what I use.
[Galaxy S 4 i9505 Original Android Development] asfpf:
Hi guys, does anyone have a "what is not working" list for cm11?
[Galaxy S 4 i9505 Original Android Development] ViruuZ:
All is working! Lol battery life is better than cm10 for me.

Tapatalk | i9505 | 4.4.2 KitKat | Germany
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Ao compass is working for you?

Gesendet von meinem GT-I9505G mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] ViruuZ:
never used so no idea.

Tapatalk | i9505 | 4.4.2 KitKat | Germany
[Galaxy S 4 i9505 Original Android Development] nommy:
Compass is working fine here in Google maps, Z-DeviceTest and SmartTools. But it does not work in GPS-Status and Kompass (app from market).

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] hust1k:
is there any camera fix for last nightly update?
[Galaxy S 4 i9505 Original Android Development] Ningeal:
Since the camerea broke with 12-16, can I dirty flash 12-14 on top of it or is a full wipe required?

Also on a side, it's rather a minor issue, since CM11 is in its' early stages but I have sound issues with the game Puzzles and Dragons. In fact, I have various issues, which are:

- although my phone is muted, game sound is still present

- game sound itself is really choppy

- though game sound is turned off, sound is still present

I assume it's an issue with CM11, because I run the game on my Nexus 7, which has 4,4,2 aswell, and it's fine there.

As I said, minor issue, so don't bother too much, but any info on that is much appreciated.
[Galaxy S 4 i9505 Original Android Development] tomurbanowicz:
What about mic in voip app, like Skype?

Wysłane z mojego GT-I9505 przy użyciu Tapatalka
[Galaxy S 4 i9505 Original Android Development] jwedda:
The camera causes reboots when recording @ 1080p. If you want a rom that fixed it, look for Omni rom.

Network names do not show up either when roaming. This is not a showstopper though.

Nope, not all is working! Everything YOU require might be working.
[Galaxy S 4 i9505 Original Android Development] footsouljah:
I got the same issues here! =(
[Galaxy S 4 i9505 Original Android Development] themetatron:
Menu overflow button hasn't appeared for about a week and I can't find the option to force it to display anymore.
[Galaxy S 4 i9505 Original Android Development] tanoxxx:
are nightly, can happen, but i hope in next release all of this bus will be fixed :fingers-crossed:
[Galaxy S 4 i9505 Original Android Development] Mittaa:
Anybody?
[Galaxy S 4 i9505 Original Android Development] ignatemanuel:
On the latest update there is no camera.