yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] jkc120:
Please do let us all know if compass is fixed. I'll be staying on this 7/31 build + faux indefinitely if not.
[Verizon Samsung Galaxy S 4] FernBch:
Correct. Officially CM has never supported any recovery except CWM (see the instruction in the OP). Although most users of TWRP have no issues , there was the occasional problem where switching to CWM resulted in no problems. Haven't seen it much since the days of CM10.

I am not sure why the change to drop support for other recoveries but I believe it has something to do with scripting in CM running correctly (or not).
[Verizon Samsung Galaxy S 4] swordmastr54:
The latest nightly shows no service for me didn't matter what I did restored back.
[Verizon Samsung Galaxy S 4] Luk37astic:
I don't know if this is a phone or ROM or app problem, so let me just start by asking here.

Does anyone use a custom lock screen like AcDisplay, Cover, SlideLock, or anything else? And if so, do you experience a problem where if you press the home button and lock the phone, the next time you wake it up, it takes a while for the custom lock screen to load?

Like if you press Home -> Lock -> Unlock, the phone will show the stock lock screen or the home screen before the custom lock screen pops up on screen.
[Verizon Samsung Galaxy S 4] FernBch:
For those of you using TWRP and/or are hesitant to continue to use newer nightlies because of the need for CWM 6.0.5.0. You may want to consider giving it a try. I have updated to it and I must say it is a very nice "touch based" recovery. Swipe up/down to nav the selections, swipe right for enter, and swipe left for back. It is flashable from recovery and you can always flash your previous recovery if you don't like it.

Just a thought.............
[Verizon Samsung Galaxy S 4] swordmastr54:
So no twrp or anything eh? Well that would ruin all of my backups to stock I have so I'll wait hopefully KT can update his.
[Verizon Samsung Galaxy S 4] FernBch:
Unfortunately, yes, it would. It was just a thought on my part for those who may be interested in giving it a try-out. If you do try you could always create a before and after backup. Only hassle would be the only backup that would be good is the after. Again, just a thought and hopefully an update for TWRP can be done and comes soon, for tgose who wish to wait.

Also:

I flashed the 8/9 nightly today and have only noticed two things so far. I use GPS Status & Toolbox. The compass and orientation sensor seems to be working again as the display rotates again and shows my heading in degrees. However, after several seconds I showed no sats and did not have a fix plus East and West are reversed. Using Google Maps I get a lock in just a few moments. Not sure if the compass issue is a CM issue, GPS S&T issue, or a combination of both.

Edit:

After a reboot N, S, E, & W are in the right orientation but no GPS fix.
[Verizon Samsung Galaxy S 4] mangalo2004:
I had the same GPS issue. No satellites or fix.
[Verizon Samsung Galaxy S 4] FernBch:
Pretty sure it's a CM thing at this point. It worked on the 8/3 nightly.
[Verizon Samsung Galaxy S 4] AzureShadow:
Do you have a link to the S4 faux kernel you are using? I am pretty interested in running the latest snapshoot with this kernel to fix the compass.
[Verizon Samsung Galaxy S 4] space_pimp:
Hey guys, just flashed M9 Snapshot, and I have a connection issue.

Every now and then whenever I leave my home and disconnect from my wifi network, my phone cannot establish an LTE/3G connection. Under the quick tiles notifications, it shows the mobile network bars in orange with no LTE or 3G label.

Usually, turning airplane mode on and off will resolve this issue.

Also, whenever this happens, I check my APN settings (need to use voice dialer to "open APNs' because CM now removed that setting) and it has the "LTE - Verizon Internet" selected, which I'm assuming is the correct one.

Wondering what you guys think about this and if this has always been a problem.

I have an MDK phone with an MK2 radio version. Is this the best/most stable radio firmware version?
[Verizon Samsung Galaxy S 4] rajones19:
Here is the link to Faux's thread: http://xdaforums.com/showthread.php?t=2273437. I am running the VZW variant, which is jfltevzw-aosp-faux123-018u. I ran it with the M9 Snapshot, with working compass. I did have one issue that for me was worth living with: FC in Settings | Display & Lights. I typically have to crank up the brightness settings in CM, so had to be sure to flash the rom+GAPPs, set up, adjust the auto brightness to my liking, then flash the kernel. What a relief to FINALLY have a working compass.
[Verizon Samsung Galaxy S 4] swordmastr54:
Twrp from KT seems to work fine with the latest nightly but kts kernel doesn't it Bork's WiFi and data you have to use stock
[Verizon Samsung Galaxy S 4] FernBch:
Cool. That confirms an earlier statement I made.

CM said they are no longer supporting third party recoveries, such as TWRP. They did not, however, say they would not work. No longer supporting, to me, means this: If you are using a third party recovery and have issue related to it support will not be provided. You may use one but you do so at your own risk. Being how some of us are using nightlies instead of "M" releases we are kinda taking the same risk anyway as support is not given for them, either.

I believe they also said something to the same effect about third party kernels, too. I read some of the blog and changelog and the reasoning is, if I understand correctly, was to bring the kernel inline with 4.4.4 source and/or coding. I would imagine that the third party kernels will catch up as many of the ROMs and kernels are based from the same tree.

Hope that made sense.

---------- Post added at 04:25 PM ---------- Previous post was at 04:03 PM ----------

Just had my first issue on the 8/10 nightly. Hit home and went to wake up again and nothing. Screen stayed black and all HW keys were totally unresponsive. Had to do a battery pull and restart. After booting I also opened GPS Status & Toolbox for S&G's. When looking through the logcat I saw quite a few entries in yellow about apps missing metadata, too. I have attached it for anyone who may be interested.

https://www.dropbox.com/s/sab21i64anqqhey/Log_2014-08-10_13-20-11.txt
[Verizon Samsung Galaxy S 4] hlxanthus:
[MENTION=2385005]invisiblek[/MENTION] never once said anything regarding cm not supporting 3rd party kernels or recoveries. All he said was they were rebasing their devices trees off of new Samsung/caf files and moving to a new unified recovery which is manditory. Soon enough kernel and recovery devs will update to accommodate this new standard. But there are some growing pains right now. Get a grip everyone and allow them to catch up.
[Verizon Samsung Galaxy S 4] FernBch:
You should reread the below post copied in it's entirety. Specifically the third sentence. And I stand corrected. Third party kernels are only borked for now. As I said previously, I'm sure KT and other will catch up soon.
[Verizon Samsung Galaxy S 4] gonzlobo:
I take it KT TWCP is a branch of the actual TWCP?
[Verizon Samsung Galaxy S 4] swordmastr54:
Yes its good I've been using it for about 5 months never had any trouble but yes like other people are saying it will just take some time , I just posted how it went for me.
[Verizon Samsung Galaxy S 4] hlxanthus:
You can clearly see he says **variant** recoveries . . as in no more jfltevzw (our Verizon device), jflteatt, jfltecan, jfltexx versions of a recovery will work. Only a unified jflte recovery that works for all i9505 and its variants. It does not say anything about 3rd party recoveries. They may not directly support such 3rd party recoveries but they have never actively campaigned against the use of twrp, philz, cot . . etc
[Verizon Samsung Galaxy S 4] mcconvict:
I hope the twrp has the decency to update their recovery. I miss it already. And the ability to use 3 rd party kernels. This whole thing kinda sucks

Sent from my jflte using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S 4] FernBch:
Never said they were against them. And he did link to CWM 6.0.5.0, previous was 6.0.4.7, and before that 6.0.4.4, etc. All of which worked on jfltevzw, jflteatt, etc..........

And it is possible that my interpritaion is not 100% correct, that said......Can we move on now???

---------- Post added at 05:59 PM ---------- Previous post was at 05:52 PM ----------

Oh, and I never said you can't use other recoveries. Maybe I should just keep my interpretations to myself going forward. I am no expert but have been doing the CM scene for several years now and have seen a few things. I only offer my thoughts and experiences in an attempt to help others get the most out of CM goodness and in no way say my word is "The gospel according to Luke".
[Verizon Samsung Galaxy S 4] hlxanthus:
All is good. This is the problem with forums, friendly conversation can be misunderstood as an attack. Never intended that. Either way you are right. Current 3rd party recoveries don't follow the unified recovery model so they don't work any longer . . hopefully those who actually have a hand in implementing these changes can weigh in and clarify for the masses.
[Verizon Samsung Galaxy S 4] FernBch:
Yes, that would be good. Just like there are "variants" of CWM install files there is a device specific TWRP file, too. Unless I misunderstood what I read the change has something to do with how scripting and coding is handled.
[Verizon Samsung Galaxy S 4] bsimpson1:
These new builds are giving me a headache. The latest 3 wouldn't allow flashing without a complete wipe of /data and /system. They also constantly reboot. Inspecting /proc/last_kmesg after each crash seems to consistently report that each one is caused by something to do with the GPU (I believe the culprit was always "adreno dispatcher", but I am currently on an old backup)
[Verizon Samsung Galaxy S 4] jkc120:
I think it was reported already but wasn't sure if it was for the 8/10 nightly. GPS won't lock, had no issues for a while prior to this :/
[Verizon Samsung Galaxy S 4] FernBch:
Yeah, I reported it already. Even posted a logcat while trying to get a lock hoping it is useful. Compass is a little screwy, too. It seems to report orientation and heading properly but it is very sluggish.
[Verizon Samsung Galaxy S 4] jkc120:
OK thanks, I wasn't sure if it was 8/9 or 8/10. Compass for me is backwards. Again. sigh.
[Verizon Samsung Galaxy S 4] FernBch:
I noticed it on 8/9, the entire compass display was off 180 degrees. clearing cache and data for the app (I use GPS Status & Toolbox) helped with that but I still have no GPS lock. When I open the compass it starts out with the orientation backwards but it slowly (takes like 30 seconds) rotates around to the proper orientation.

I also experienced something I have not seen in several months today, a random reboot. I looked at logcat and it didn't catch why.

And I'm currently running 8/10.
[Verizon Samsung Galaxy S 4] jkc120:
d

check /proc/last_kmsg after it reboots
[Verizon Samsung Galaxy S 4] FernBch:
Just flashed 8/11 and GPS lock is working again. Had a lock in seconds. Thanks CM!!
[Verizon Samsung Galaxy S 4] hlxanthus:
https://github.com/CyanogenMod/andr...mmit/fac21841b7690ac69db575b5a643831d36960342

Looks like they may be reverting the unified recovery assert check within the update.zip
[Verizon Samsung Galaxy S 4] FernBch:
Possibly. Looking at the dependencies it is needed by this "jflte: move libcsd-client to /system/lib", the commit message says " * For some reason this doesn't get picked up when its

in /system/vendor/lib. Result is no audio in-call."

I also experienced a random reboot on 8/11. It seems to be repeatable too. When it happened on the 8/10 nightly I was scrolling the page up and down in another forum app I use. Today on 8/11 it happens when scrolling back and forth in the web browser. I have attached proc/last_kmsg for aanyone who deems it worthwhile.. Logcat did not catch it.

https://www.dropbox.com/s/4nc7dzuhs9c6895/last_kmsg
[Verizon Samsung Galaxy S 4] bsimpson1:
I've been getting them too. It's something to do with the gpu.
[Verizon Samsung Galaxy S 4] bsimpson1:
I'm happy that they've finally added the conservative governor though. It's definitely my favorite general-use governor.
[Verizon Samsung Galaxy S 4] FernBch:
That would make sense. There have been some commits recently mentioning the GPU. Maybe they're layin the groundwork to get it all straightened out.
[Verizon Samsung Galaxy S 4] gonzlobo:
Got 3 random reboots with 0811 (flashed with twcp, so there you go). Back to 0804.
[Verizon Samsung Galaxy S 4] FernBch:
The random reboots are not cased by TWRP, I run CWM 6.0.5.0 and have experienced it, too. I think they may be GPU related but I'm not sure.
[Verizon Samsung Galaxy S 4] jkc120:
Yeah these recent builds sure have been a step backwards. On 8/10: no GPS, random reboots, and have had apps randomly FC'ing, none of which I've had in a while. Hopefully these things are fixed soon (sounds like GPS already is).
[Verizon Samsung Galaxy S 4] FernBch:
Yeah but it'll catch up. They totally revamped the kernel a few builds ago so the kinks will get worked out. Battery life also seems to be pretty decent, maybe even a touch better than before.

I just flashed 8/12 and we'll see how it goes. It did seem like it had a hard time connecting to my WIFI right after the initial boot but all seems good now. Logcat attached.

https://www.dropbox.com/s/0rpi9cltctazvqr/Log_2014-08-12_06-29-53.txt

---------- Post added at 09:45 AM ---------- Previous post was at 09:38 AM ----------

Got another logat to post up.

While updating apps in Google Play it just quit. No FC message or anything just stopped mid download and went back to the home screen.

https://www.dropbox.com/s/42qnd227n0mlsmv/Log_2014-08-12_06-41-32.txt

---------- Post added at 09:51 AM ---------- Previous post was at 09:45 AM ----------

And last but not least, a random reboot (was using Google Play). last_kmsg attached, too.

https://www.dropbox.com/s/4nc7dzuhs9c6895/last_kmsg
[Verizon Samsung Galaxy S 4] Lw00d:
im running M9

i been on it for 4 days iv had two reboots. the screen locks up, then reboot. i did a clean flash, CWM 6.0.5.0.

i dont know whats up. hopefuly they get this ironed out soon , so that i could flash one of the nightly.
[Verizon Samsung Galaxy S 4] gonzlobo:
I agree. 0811 crashed 3 times in the hour I had it installed. Today's build (0812) hasn't crashed at all.

Every crash occurred while I scrolled in tapatalk & plume (those apps are usually solid).
[Verizon Samsung Galaxy S 4] FernBch:
Definitely display related. 8/12 has done it once so far, for me.
[Verizon Samsung Galaxy S 4] suoirotoN:
So I just came back to CM after a couple months away and flashed todays build with latest PA Gapps... only thing wrong so far is my GPS won't lock at all in maps or my weather app. Anyway to fix this?
[Verizon Samsung Galaxy S 4] FernBch:
Not sure. The kernel was revamped a few days ago and GPS lock was not working. After flashing 8/11 it was fixed for me. A few weeks back when GPS lock was broken people reported fixing it by flashing a TW ROM, booting it long enough to get a lock, then flashing CM and it worked. The other option may be to go back to your previous ROM and flash say 8/4 before flashing anything after 8/9. Either way the fix may be a little bit of a PITA.
[Verizon Samsung Galaxy S 4] suoirotoN:
Okay so it just started working randomly. Another issue though is superuser wont grant anything root, like titanium backup for instance.
[Verizon Samsung Galaxy S 4] MustGoFast:
I am seeing this on the milestone build as well.. hopefully a fix otherwise I'm updating to the latest daily and clean flashing again to try to restore it... big problem for me.
[Verizon Samsung Galaxy S 4] FernBch:
Is SU giving the option dialog? I believe the default setting is to prompt you but after 30 seconds it will automatically deny the request.
[Verizon Samsung Galaxy S 4] gunnermike:
Do a Google search for s4 proximity sensor fix.
[Verizon Samsung Galaxy S 4] ctoph0:
I'm on 8/3 and can't press allow root for superuser requests either. Of I back out the system halts and it FC.

Sent from a toaster in space
[Verizon Samsung Galaxy S 4] FernBch:
Did you clean flash or dirty flash? You can also try SuperSU (by chainfire) and see what happens. You can also use a root checker and verify root access.
[Verizon Samsung Galaxy S 4] jkc120:
Well this blows. GPS still doesn't work for me. the recent night lies appear to have corrupted something, so I guess I have to go do the process of flashing TW AGAIN to get GPS back What a PITA.

---------- Post added at 07:56 AM ---------- Previous post was at 07:54 AM ----------

Does anyone have a TW flashable .zip so I don't have to mess around with odin/etc?

---------- Post added at 08:40 AM ---------- Previous post was at 07:56 AM ----------

Restored my backup from before and was able to get a lock there, and upgrading to 8/13 from 8/3 retained GPS so something between 8/4 and 8/10 hoses GPS. At least I didn't have to resort to TW to get a GPS fix.
[Verizon Samsung Galaxy S 4] dansan382:
been following the thread for awhile now but lost track and now im way behind, especially with over 320+ pages. I am currently on M2 (i know dont laugh) and my phone is doing nothing but systemui force closes on start ups. Ended up getting it to boot into safe mode i guess and now its "working" but i need to wipe this thing.

Been reading a lot of problems with these daily builds and also the last few M snapshots were buggy too. Should I flash M8 or is there nothing wrong with M9 that I shouldnt flash it?

wanted to get some input from you guys, tried catching up on this thread but its just so much information
[Verizon Samsung Galaxy S 4] jkc120:
MMS is borked for me in 8/13

So MMS is broken for me in 8/13. I just noticed the group texts I had tried to send were stuck "sending..."

Anyone else seeing this? I'm using SimplyText but it happened for another sms app as well.

1 step forward, 3 steps backwards it seems as of late :(
[Verizon Samsung Galaxy S 4] bsimpson1:
are you using any screen dimmer apps? I know first hand that these apps can prevent certain buttons from being pressed. I assume it's because it works by using overlays, and certain security-critical apps (i know the package installer is one of these apps) disallow the user from pressing any of its dialog buttons when it detects a screen overlay in case the overlay app is using the overlay to trick the user into pressing a button that could have serious consequences.
[Verizon Samsung Galaxy S 4] Train88:
You should always use CM's official gapps on CM... they rely on libs and other things that may or may not be present in other gapp packages.

I'm still on 8/1 build without all these issues. I've downloaded almost every nightly, but I'm not keen on having the issues either lol... If it's not still available, pm me and I'll upload it for you

Team BlackOut... or Back Out
[Verizon Samsung Galaxy S 4] FernBch:
I have tried the official Gapps package twice, each time I flashed it I bootlooped and can't explain why. Using PA Gapps has never caused an issue for me.

On a CM related note, I have had two instances where I can't wake my device. I have to do a battery pull and restart it. Not sure what is causing it. First one happened while running 8/10, second was today on 8/12. Could it be death sleep or whatever it has been called?
[Verizon Samsung Galaxy S 4] jkc120:
Had that happen to me yesterday, too.

I think I'm restoring my 8/3 build and sticking with that until all the instability is under control.
[Verizon Samsung Galaxy S 4] FernBch:
I'll live dangerously, lol. Someone has to be the Guinea Pig to test the nightlies out. Haha
[Verizon Samsung Galaxy S 4] jkc120:
And we're grateful for that! hahah
[Verizon Samsung Galaxy S 4] FernBch:
On a good note, how's battery life since the kernel has been revamped? It's been pretty decent for me.
[Verizon Samsung Galaxy S 4] jkc120:
It could be placebo, but I noticed the same.
[Verizon Samsung Galaxy S 4] pistoffjstr:
My S4 running latest nightly update randomly freezes during typing anything and just reboots any one else have this issue?
[Verizon Samsung Galaxy S 4] Train88:
Please read the last few pages.

Team BlackOut... or Back Out
[Verizon Samsung Galaxy S 4] FernBch:
Several have reported random reboots. Seems to happen in various apps (web browser, different forum apps, typing or not).
[Verizon Samsung Galaxy S 4] dansan382:
thanks for the offer, ended up flashing snapshot 8 last night. didnt need to be on the most recent build especially since i was on snapshot 2 before this

My only problem thus far is the camera app takes on average 5-7 seconds to open up. pretty long if you ask me. anyone have this issue?
[Verizon Samsung Galaxy S 4] orateam:
It's been a long time since i used CM on our S4. Last time was probably a year ago when there were too many bugs such as no IR, HDR on camera, and bugs with the memory card.

But not only are all the bugs gone, but CM looks great too. The new theme area and the themes themselves are just amazing. Blowing away anything i've seen with any other launcher. So wanted to give a BIG thanks! to the CM team. I grabbed a oneplus recently and that was what inspired me to give it a shot on my S4.
[Verizon Samsung Galaxy S 4] MustGoFast:
I'm getting some random reboots too. In the last 2 days it's happened 3 times.

Once when trying to answer the phone, once in a game app, and once in a business app - no common hardware/interface between the 3.

Anyone hear if this is being snuffed somewhere?
[Verizon Samsung Galaxy S 4] FernBch:
Not sure. There were a couple commits for the dialer and incallUI in the 8/13 nightly (I'm on 8/12). I have had a few reboots but not related to the phone. I have found no repeatable pattern to them, either.

I have also noticed some weird behavior today, too. I had some strange screen lag when going home from an app. It's like a 3-5 second delay with a black screen. Since rebooting earlier it hasn't repeated itself. The last time I saw something like this was on a port of CM9 on the Motorola Photon 4G. I remember something about a commit addressing a "memory leak" for that one.

I'm downloading the 8/14 build to flash now. I'll report back later on.
[Verizon Samsung Galaxy S 4] FernBch:
First report on the 8/14 nightly after flashing three hours ago.

I know this may not mean anything but I have tried doing everything I was previously when I would get a random reboot and nothing. I know it may be an unknown random thing going on and I could not reproduce it before but I haven't had one yet.

I have, however, discovered a new bug. I am not sure if it was present on earlier builds. I tried to send an MMS (picture) while on WIFI and it would not send so I tried the following:

Toggled airplane mode off and back on - would not send.

Turned WIFI off and connected to LTE (bars and LTE indicator where white) - would not send.

Toggled airplane mode off and on with WIFI off (bars and LTE indicator were orange) - MMS successfully sent at that time.

So I tried it again with the same steps as above and it would only send when WIFI was turned off and connected to LTE WITH orange bars and LTE indicator. If they are white MMS will not send.

Logcat attached:

https://www.dropbox.com/s/lvf0hm0h1o7kwmp/Log_2014-08-14_20-58-35.txt

That is all at the moment.

---------- Post added at 12:24 AM ---------- Previous post was at 12:07 AM ----------

So much for the random reboot issue, just had one.
[Verizon Samsung Galaxy S 4] orateam:
getting the crazy reboots like others as well. I really like CM though, so i want to know if anyone knows what and where is the latest stable build?

thanks,
[Verizon Samsung Galaxy S 4] Train88:
I said a couple pages ago that I was on 8-1 build without issues... I think the last build without problems was 8-3, but can't remember without looking

Team BlackOut... or Back Out
[Verizon Samsung Galaxy S 4] bsimpson1:
They released an experimental build with Adreno in the name so it looks like theyre at least aware of the reboots assuming that i was right in beleiving that's whats causing them. I havent tried it yet though