yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] FernBch:
I'm sorry gentlemen, but I must respectfully disagree.

Other than the compass not working properly (Samsung issue not CM) I have no problems with CM11. Yeah there's little quirks here and there, but for me this is a pretty solid ROM.
[Verizon Samsung Galaxy S 4] thestinkinggenius:
Maybe it's been fixed but when I last tried CM11 a couple of weeks ago I was having problems with my bluetooth headset and when I switched bag to AOSP Google Edition everything worked fine - maybe it's time to give it another shot.
[Verizon Samsung Galaxy S 4] jkc120:
I can't say I'm a heavy Bluetooth user, but I've been streaming Google play music over BT to a Chrysler Town and Country via their uConnect (rental car) with no issues at all other than the Google maps turn by turn volume is not loud enough when it lowers the volume of the playing music to cut in and give directions but that's a really minor issue.
[Verizon Samsung Galaxy S 4] thestinkinggenius:
Thanks, I will give it try again in the next couple of days.
[Verizon Samsung Galaxy S 4] rwSN1PER:
I'm running the 6/24 nightly and I'm loving it! The only issue that I'm having is that I cannot record video using my front facing camera while in Snapchat, but that is far from a dealbreaker.
[Verizon Samsung Galaxy S 4] Velocifero:
Does the SOD (Sleep of Death) issue still occur on this ROM? Every TW ROM i've used so far it's happened to, as well as random reboots. But since I've been using CM11 (M7), I haven't had either occur. Just wanted to see if it was only in my head or not.
[Verizon Samsung Galaxy S 4] crossen0:
I most recently tried the 6/18 nightly and I still had the issue where I clicked on a text message notification in the notification pull down but it didn't clear the notification. I had to do it manually by hitting 'mark as read.' Was wondering if anybody else was having this experience?
[Verizon Samsung Galaxy S 4] lordgodgeneral:
Like a couple of others above have said, bluetooth is the biggest issue I'm having. I use it pretty heavily between headsets and my Ford Sync, and the random disconnects and other quirks (audio pausing then playing in fast forward) really make it almost impossible to use for playing music and the audio lag it introduces for videos is just as bad. I haven't ran into any of these issues with stock based ROM's so I'm usually running GPE with Gravity box and try the latest nightly about once a week to see if it's improved any.
[Verizon Samsung Galaxy S 4] sdsurferbob:
Anyone else still having this problem? It started happening to me in early May with the CM nightlies, couldn't find a fix so went to Hyperdrive for awhile, and no issues. Came back to CM last night hoping it would no longer be an issue but it seems like it still is. I blew out the earpiece trying to clear the sensor, but I'm not convinced it's a sensor issue, as at least the sensor/dialer combo in Hyperdrive works just fine. Could it still be a calibration issue in CM?

My issue was when I initiate a call and put the phone to my ear, screen would turn off just fine, but when I took the phone away from my ear, half the time the screen wouldn't come back on by itself, and the other half of the time it would but the dialer would be frozen and I wouldn't be able to press any buttons.
[Verizon Samsung Galaxy S 4] heath2805:
No issues here. Sounds like kernel issues if your getting freezing. Are you on the most recent recovery? And did you try another kernel like KT's?
[Verizon Samsung Galaxy S 4] sdsurferbob:
Yes, tried KT's kernel too. Still using TWRP 2.5.0.2 I think. Would the recovery used to flash the ROM have a material impact like that? My knowledge in that arena is relatively limited, sorry.
[Verizon Samsung Galaxy S 4] heath2805:
Possibly. I was using that same recovery and noticed FC's on couple apps recently. Then updated TWRP through goo manager to 2.7.1.0 and no FC's now. So Its worth a shot. It took me forever to leave 2.5.0.2.
[Verizon Samsung Galaxy S 4] bmcclure937:
I am having this same issue. I disagree with the other comment about the recovery. This should not impact the ROM.

It could be kernel... but I am using the stock CM11 kernel and it should work fine.
[Verizon Samsung Galaxy S 4] FernBch:
Which recovery has been debated for some time. Officially CM recommends and supports CWM, but many have used TWRP without issue. I will agree that if you are having issues that the normal route doesn't seem to help to update your recovery to the latest version. There have been commits in the past few weeks related to recovery handling.
[Verizon Samsung Galaxy S 4] rajones19:
I noticed the adjustment for vibration strength disappeared a few builds ago. Not sure if it was moved, or removed entirely. Has anybody found it? I sure miss it - my S4 doesn't vibrate with enough intensity to scare off a fly.
[Verizon Samsung Galaxy S 4] heath2805:
Vibrator intensity is in settings under sound.
[Verizon Samsung Galaxy S 4] rajones19:
Thank you!! I had been working my way through the settings, but didn't expect to find it under 'Sounds' because I didn't consider it to be one LOL.
[Verizon Samsung Galaxy S 4] sdsurferbob:
I'm pretty convinced it's something CM related, as I just tried the AOSP Google Edition ROM and don't have any of these issues.

I'll try to update/change recoveries and do a clean flash of the latest nightly, as I don't seem to have much to lose by trying it.
[Verizon Samsung Galaxy S 4] Markstache:
I remember reading about someone having this issue earlier in this thread so I just wanted to post for anyone getting audio distortion when playing music (particularly when the screen is off) that no amount of voltage adjustment or clock adjustment settings whether it be OC steps or changing the max clock speed when screen is off would stop the issue, but the only thing that finally resolved the issue was changing the governor from ktoonservatieq. I'm using badass right now and have not had any audio hiccups.
[Verizon Samsung Galaxy S 4] ozymandiaz:
Good info. Thanks!
[Verizon Samsung Galaxy S 4] Sailrace:
I can confirm that this is not just a CM issue. i have recently started using CM11 as my daily driver after coming from the Play Edition ROM. I have experienced many times that the call screen doesn't turn back on after a call on the GPE ROM.

I used some compressed air the other day to blow out the earpiece, and it has certainly helped with the proximity sensor.
[Verizon Samsung Galaxy S 4] FernBch:
I don't have the link handy (in this thread somewhere) but pretty much everyone that has had screen on/proximity sensor issues followed a write up to clean the prox sensor (not by just blowing out the earpiece) and the issue was fixed for them.

---------- Post added at 11:40 AM ---------- Previous post was at 11:31 AM ----------

Found the info. This issue has come and gone for as long as I can remember. Happened on CM10, too.
[Verizon Samsung Galaxy S 4] crossen0:
Does anyone run ART? How is your experience so far, if you do?
[Verizon Samsung Galaxy S 4] whichonespink73:
Been having this issue on every aosp ROM since I got this phone last year and I found a permanent solution (for me at least. Go to this post and follow his instructions, fixed my proximity sensor after trying everything else :),

http://xdaforums.com/showthread.php?p=48468330
[Verizon Samsung Galaxy S 4] sdsurferbob:
Thank you very much, I appreciate the help. I'm not opposed to going this route, but it doesn't explain why I don't have this problem at all on the stock or Hyperdrive roms, only CM and the GPE roms. Could it be simply the sensitivity settings for the prox sensor being different between the two roms?
[Verizon Samsung Galaxy S 4] whichonespink73:
As I said. Do this, problem will go away.

http://xdaforums.com/showthread.php?p=48468330
[Verizon Samsung Galaxy S 4] sdsurferbob:
Sorry, hadn't seen your post before I replied to the other, thanks. I do recall seeing this one as well, but couldn't figure out how to access the special Samsung menu. I'm used to seeing codes like that used in the dialer, but when I tried it that way the phone tried to dial the number, didn't go to any menu.
[Verizon Samsung Galaxy S 4] whichonespink73:
I couldn't either but its unnecessary if you know your sensor is broken. Scroll down and follow his other steps that use the terminal emulator and you will be fine.
[Verizon Samsung Galaxy S 4] sdsurferbob:
THANK YOU!!! I hadn't read that post as carefully as was obviously necessary, I presumed accessing the Samsung menu was necessary before doing the other steps. I went ahead and followed them and have made 2 calls successfully on CM11 and am able to put the phone to my ear, take it way, use the dial pad, put it back, etc. Thanks again!
[Verizon Samsung Galaxy S 4] Erievon:
I updated to the 6/28 nightly last night. I was coming from the 6/14 nightly. I've always left my brightness on "Auto" and it's done a good job of managing brightness for me.

I'm noticing on 6/28 the screen is a whole lot dimmer in the same situations that it used to be fine with. Anyone else having this? It's probably better for battery life, but gets a bit too dim for my tastes. I'm hoping they just don't have it dialed in for 4.4.4 yet, or they are experimenting with lower minimums.

Edit: After all this time I just realized I had control of the auto-brightness settings based on different light conditions. Not sure when this became possible but, I've corrected it to my tastes.
[Verizon Samsung Galaxy S 4] lolminraise:
Just want to say I'm using snapshot m7 and if I unplug the headphones while music is playing, the sound for ringtones, notification, and alarms will turn off. I then have to reset the phone for the sound to come back.

Also, the proximity sensor is not working properly. When I make/receive calls and I put the phone to my face, the screen will blackout like it's supposed to, but then when I pull the phone away from face, it will not turn back on. Yes, I keep my screen clean, and I did not have this problem on stable version 10.1.3.
[Verizon Samsung Galaxy S 4] indolent:
This has been talked about many times. You either have to take the phone apart and clean the dust out (see post 3055) or adjust the prox sensor sensitivity (post 3057).
[Verizon Samsung Galaxy S 4] whichonespink73:
If you bothered to read the last 5 posts you would see I posted a permanent solution that doesn't involve taking your phone apart. Skip the Samsung code part and go straight to the commands.

http://xdaforums.com/showthread.php?p=48468330
[Verizon Samsung Galaxy S 4] space_pimp:
Where can I find the APN settings? Im running build 6/28.

Normally it would be under mobile networks, but I can't seem to find it after the new menu system.

I was roaming earlier today, it must have changed the APN, now it won't revert. Any ideas?
[Verizon Samsung Galaxy S 4] FernBch:
Did you try using the voice dialer and saying "Open APN's"?
[Verizon Samsung Galaxy S 4] space_pimp:
Oh wow, that worked! Thank you!

Always thought voice dialer was a useless preloaded CM app.
[Verizon Samsung Galaxy S 4] jkc120:
On the 7/4 nightly, the software nav buttons have an issue where the menu button keeps re-appearing next to the recents button. I go into settings and reset it to defaults and it's fine for a minute or two, but then reverts back and the menu button appears. Back to my late June nightly I guess.
[Verizon Samsung Galaxy S 4] FernBch:
Also on the 7/4 nightly.

After flashing the status bar is missing and I am unable to restore it. Going through the settings and I am unsuccessful. My wallpaper is also missing. Going into settings, choosing one, and applying it returns no error message but the screen remains with a black background.

I flashed the 6/27 build and now have the same issues with it. Here's a logcat.

https://www.dropbox.com/s/k5i1mqmdyhxoj1b/Log_2014-07-05_08-10-23.txt
[Verizon Samsung Galaxy S 4] FernBch:
I have returned to the 6/25 build (last that had the fewest issues for me).

There are two things I noticed on this build but I do not have a logcat.

Using Google navigation had an issue. It would turn itself off for reasons unknown. I would enter a destination and start driving. Sometimes, after 30 minutes to an hour or so, I would look real quick to see how far from the next turn and navigation was no longer running. I have not determined a pattern or any action that stops it.

I also use Snap Camera HDR. If I leave the camera open too long it would become very sluggish. Especially if the display powers down (sleep mode) on its own. If I take a picture and use the power button to put the phone to sleep I do not have this issue.
[Verizon Samsung Galaxy S 4] tracker01:
is this ever going to support SS any time soon?
[Verizon Samsung Galaxy S 4] Crossoverdoc:
Having the same issue where I can't send text messages. All other data works, including making calls and RECEIVING texts, but I can only send one text, then a reboot is required if I want to send another. Otherwise, the message will just stay in the 'sending' phase. It seems after some research that this affects a lot of Verizon users over a range of AOSP ROMs and there's really no fix for it. It's a shame, because now I'm stuck on TW ROMs.
[Verizon Samsung Galaxy S 4] FernBch:
Unfortunately, no. In order to flash custom ROMs such as CM you need a bootloader that is either unlockable (like a developer device) or one that is exploitable. The bootloader that came with the earliest GS4's on VZW could be exploited with a process called "loki" which allowed the use of custom ROMs. All later releases of the GS4 have had this hole closed and the bootloaders can not be exploited.

Unless someone finds an exploit or an unlock method (dev's have been searching for some time) anyone who has a device that does not have the original MDK bootloader will be limited to SafeStrap ROMs.
[Verizon Samsung Galaxy S 4] Markstache:
There is a fix. Install Google Edition (and make sure it's set to prefer LTE and not eHRPD so you don't lose 4G) before you re-install CM 11.
[Verizon Samsung Galaxy S 4] Crossoverdoc:
Can you elaborate a little more? Do I have to restore from a backup of CM? Or do I install GPE, wipe, clean install CM 11? thanks a lot for the help if you can explain further (:
[Verizon Samsung Galaxy S 4] FernBch:
First question, you say you are stuck on TW ROMs. Is this because TW is tge only things that doesn't give you texting issues or has your BL changed from MDK along the way?

If you have a BL later than MDK you are stuck in a life without CM. If your BL is MDK, I believe this is the tbread you need to read:

http://xdaforums.com/showthread.php?t=2654822
[Verizon Samsung Galaxy S 4] Crossoverdoc:
No no, I'm on MDK, I knew of that issue. Like the above person suggested, I'm going to try the GPE fix in the morning. I'll report back with results. Thanks for the help!
[Verizon Samsung Galaxy S 4] jkc120:
Menu button appearing and getting stuck for no reason is still there in 7/6 build (and I clean flashed to be doubly sure). Can anyone else reproduce this ?
[Verizon Samsung Galaxy S 4] macravin:
Does the ir blaster currently work in CM? I'm looking at flashing it again I'd it still does.
[Verizon Samsung Galaxy S 4] bswides412:
Any news on when the next snapshot will be coming out? I would love a mostly stable snapshot of the progress made on CM. I am currently on GPE but seem to be having some connectivity issues. Some emails, texts, etc. are at times delayed and/or never come in until I open the corresponding app.
[Verizon Samsung Galaxy S 4] FernBch:
As anyone been experiencing sluggishness lately. I have been having issues with apps acting sluggish for the last 10-12 days or so. I notice it the most with Snap Camera HDR and Dolphin Browser. Things act like they are unresponsive or stuck then will "catch up" a few seconds later. It acts pretty much the same way a PC does when memory is low. I have the same apps installed and in use for several months so there is nothing new. I have included a logat for anyone who is interested.

https://www.dropbox.com/s/ac359wnkfpkkpky/Log_2014-07-06_22-11-08.txt

---------- Post added at 01:19 AM ---------- Previous post was at 01:18 AM ----------

No ETA's are given but I would imagine one is in the works and will be posted when the CM team feels it is ready.
[Verizon Samsung Galaxy S 4] DipRip:
7/7 nightly completely screwed up the launcher for me. Cannot access the settings menu, all my settings were restored to default (no sound notifications, battery charger light on, etc.). I updated back to 7/6 and trebuchet is still all screwed up. Going to have to wipe and reinstall 7/6.

I would strongly advise not updating to 7/7 at this time. Especially if you dirty flash like me.
[Verizon Samsung Galaxy S 4] saul1991:
Is there anyway to get the lockscreen notifications in cm??
[Verizon Samsung Galaxy S 4] radpp16:
Whats the download link for M8?
[Verizon Samsung Galaxy S 4] saul1991:
I tried flashing it and it failed. Make a backup because I didn't lol,
[Verizon Samsung Galaxy S 4] deviousmrtaco:
did you check the zip size? kept trying to download it and it was only 127mb
[Verizon Samsung Galaxy S 4] vanberge:
Anyone tried the option "update cm recovery" within developer options?
[Verizon Samsung Galaxy S 4] musicfreak190:
I use NILS... I turn off the Notification panel feature.. Works better in lockscreen widget mode imo.

Set the lockscreen to maximized always in CM lockscreen settings.
[Verizon Samsung Galaxy S 4] Markstache:
Sorry to just now get back to you. Honestly I don't know the exact process as I spent a lot of time on GPE and ran into all sorts of other issues that required completely going back to stock and at one point getting a SIM card change (don't manually update PRL via *228 if you're on Verizon or you lose 4G. No one ever told me that.) I believe just doing a wipe, installing GPE, booting it once and making sure Network mode is set to 4G, rebooting once to made sure it sticks and then wiping and installing CM is enough.
[Verizon Samsung Galaxy S 4] Lw00d:
could anyone mirror with the new chromecast Version 1.7.4??

i dont have the option to cast screen in the chromecast app.
[Verizon Samsung Galaxy S 4] Nath5:
Anyone else having problems with Google keyboard constantly crashing on the newest nightlies. Also the back and settings keys don't work?
[Verizon Samsung Galaxy S 4] riphamilton:
same here.
[Verizon Samsung Galaxy S 4] jkc120:
ditto, no "cast screen" option for me in 1.7.4 chromecast app :(
[Verizon Samsung Galaxy S 4] Lw00d:
what nightly do you guys have?? maybe we need the latest nighly
[Verizon Samsung Galaxy S 4] jkc120:
I'm on the 7/6 nightly.
[Verizon Samsung Galaxy S 4] Lw00d:
yeah, im on a old one too. like 7/2 or something. i will flash the latest nightly on Saturday morning. see if that helps
[Verizon Samsung Galaxy S 4] jkc120:
This works for me to enable cast screen:

http://xdaforums.com/hardware-hacking/chromecast/experimental-enable-mirroring-device-t2812193

But I have no sound :/
[Verizon Samsung Galaxy S 4] Lw00d:
:( the sound is the most in-portent part for me.
[Verizon Samsung Galaxy S 4] edif30:
So what's the deal here? Our device just isn't supported to cast the screen natively with the latest chromecast app? Is this another case of Nexus devices only?
[Verizon Samsung Galaxy S 4] jkc120:
I saw in another thread that once you use the apk and can cast to it, disconnect from it then use the chromecast app to reboot it. That worked for me.
[Verizon Samsung Galaxy S 4] edif30:
Not sure I am following what you are describing. Are you saying to side load the .apk? I am running the latest version. I wonder if my chromecast itself is not updated. Or maybe I'll try a reboot?
[Verizon Samsung Galaxy S 4] jkc120:
No I had the latest apk as well already but sound wasn't working. I casted the screen, then disconnected. Then went k to the chromecsst app on my phone and rebooted the chromecast from there. Then when I connected again sound worked
[Verizon Samsung Galaxy S 4] kyuubi08:
I'm getting issues with my Bluetooth when connected to both my car and headset. The sound would become distorted and I would usually have to disconnect and reconnect
[Verizon Samsung Galaxy S 4] 386:
It does! I had to e-mail colortiger to fix Smart Remote. The app's description on the play store tells about it. They did something to change the IR codes that changed with 4.4.3+ and had to update my account, and if CM ever changes it to the "official" IR implentation I'll have to e-mail colortiger again to fix it. But it works 100%.
[Verizon Samsung Galaxy S 4] edif30:
Rebooted Chromecast, on latest version as well as latest version of the app and no cast screen option.
[Verizon Samsung Galaxy S 4] jkc120:
You still need to use the apk to enable it to work. The process I described was to try to fix the sound.
[Verizon Samsung Galaxy S 4] edif30:
This is the part I'm confused on. I have the latest version that supports casting via the play store. Why would I need to side load an apk of the same version? Is the apk signed for a different phone?
[Verizon Samsung Galaxy S 4] jkc120:
Unless I linked the wrong thing, it's not the chromecast apk you need but the workaround app that modifies something i n /system to turn screen casting on, hence why it needs root.

---------- Post added at 08:34 PM ---------- Previous post was at 08:32 PM ----------

Here's the link from the other thread to enable screen casting: http://www.androidfilehost.com/?fid=23501681358561116
[Verizon Samsung Galaxy S 4] edif30:
OK understood. However I'm just curious as to why a workaround is needed. Back to the original question of "are only nexus devices supported?" If that's the case then I'm good with the workaround. But if not, what is causing this? I just checked a Moto X I have and same thing. Will try the Nexus 7 later.
[Verizon Samsung Galaxy S 4] jkc120:
Typical Google staged rollout I guess, and probably to avoid issues with it prompting complaints for devices not fully tested.
[Verizon Samsung Galaxy S 4] edif30:
Makes sense. I thought it was something to do with this ROM at first. Thanks for the help!!
[Verizon Samsung Galaxy S 4] jkc120:
NP, I thought the same at first bit koush indicated cm11 on some devices worked fine so staged rollout makes sense I guess. Time will tell :)
[Verizon Samsung Galaxy S 4] jackburnt:
Worked for me! There's a half second delay, which is normal. Sound matches up well too, my biggest concern. Wonderful way to show off photos.

And I heard the update for casting is server-side, so that may be why it's not everywhere yet.
[Verizon Samsung Galaxy S 4] indolent:
I get some distorted sound once in a while when connected to my car bluetooth. It is generally fixed by just skipping to the next music track. Not sure if that's the same issue you're having or not.
[Verizon Samsung Galaxy S 4] macravin:
It is supported on the S4 and S5. It works fine in the Google Edition rom. I'm guessing it has to do with some sort of driver that Samsung built in. Maybe the proprietary driver for wireless display. Maybe the S4 is supposed to cast in a different way from the nexus devices through samsung's wireless display driver?

Idk, all I know is touchwiz and gpe work fine while cm doesn't.
[Verizon Samsung Galaxy S 4] ctoph0:
Running the 7/12 nightly and having MMS errors both reviewing and sending.

Sent from a toaster in space
[Verizon Samsung Galaxy S 4] jackburnt:
I don't think toasters are supported yet on 11. May have to rollback to 10.1.

But seriously, try clean installing the latest.
[Verizon Samsung Galaxy S 4] CyberZion:
Is there a volume hack available to make the speaker louder for this ROM? I know there is one for TW.
[Verizon Samsung Galaxy S 4] FernBch:
I don't have the link but there is a thread in the GS4 forum that explains which file needs editing. It has complete instructions including which line and value to edit.
[Verizon Samsung Galaxy S 4] jkc120:
All I know is koush indicated it wasn't a cm11 issue *shrug*