yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] FernBch:
Dumb question, is "Keep WiFi on during sleep" set to always? I had that issue some time ago and after checking all the usual I finally reflashed the MDK+NONHLOS package then flashed the modem I was on again and it got better. I still see it but only after extended periods of deep sleep like overnight.
[Verizon Samsung Galaxy S 4] .Ejekt:
Decided to do a clean install of 5/03. Everything is working on my end! If this lasts me all day tomorrow without any errors, I think it may be the last time I flash a ROM on this phone until the "next big thing" comes around.
[Verizon Samsung Galaxy S 4] TheRealStarkman:
Does anyone else find the volume during the call to be rather low? The Icon to increase the volume during a call is not active so I can't go that route.
[Verizon Samsung Galaxy S 4] natec003:
I flashed 5/1 the other day and all was well with Bluetooth while using play music. I then tried to stream Pandora over Bluetooth, but had a return of the Bluetooth share force close. Tried to clear cache/data all the fixes I could think of. Jw if anyone has noticed the same issue or if someone could test it on a newer version... It usually will do ok for a song or 2 then will give me the error.

Sent from my S4
[Verizon Samsung Galaxy S 4] FernBch:
I'm on 5/4 and I still see BT issues using a Jabra earpiece. What is happening is I will get the first call and can hear just fine. When I get another call they can hear me but I can't hear them. I have to hang up and call them back and then all is good. This issue may or may not return during the course of the day and I have not found a pattern to make it repeat at will.
[Verizon Samsung Galaxy S 4] TheRealStarkman:
Is any else able to use the volume control to skip to the next music track. Does not work for me but I dirty flash so I don't really know if it is broken. I am on 5/1 and did not see anything in the change log that might of fixed it.
[Verizon Samsung Galaxy S 4] nanodan:
Doesn't work for me either. On 5/5 as of yesterday, ran 4/23 or something before then.
[Verizon Samsung Galaxy S 4] Blackcircle7:
Try turning off ambient display.
[Verizon Samsung Galaxy S 4] indolent:
Yes, streaming pandora seemed to work for a while, but now I'm getting the same problem as we had before. Streaming from the phone with Play Music is still working fine though.
[Verizon Samsung Galaxy S 4] Cameron_S:
Today I started having 'Bluetooth Share' force closes after being connected to my moto 360 and then attempting to connect to my car :(
[Verizon Samsung Galaxy S 4] TheRealStarkman:
Thanks. That did it. Volume skip tracks now works. Ambient display not that important.
[Verizon Samsung Galaxy S 4] ViperZ28:
I cannot get LTE mode, always says 3G, anyone else seeing this? Any known fixes?
[Verizon Samsung Galaxy S 4] brillb:
Very hot, battery life in minutes

Been running CM12.1 for about 2 weeks now and updating regularly. Biggest problem is that the phone gets crazy hot and battery life is only double digit minutes before it is totally dead. I assume there is some process running amok that is eating the CPU, but I don't know how to find it. I don't have that much extra stuff installed, I don't believe it to be an app, but any pointers on how to find out would be much appreciated.

Also, the camera is super flaky. It takes a long time to register, then I can usually take only 1 photo before freezing the app.
[Verizon Samsung Galaxy S 4] ViperZ28:
I have been dirty flashing this whole time, yesterday I did a full wipe and install and have been having problems ever since.
[Verizon Samsung Galaxy S 4] FernBch:
I have had issues since the change from 5.0.1 to 5.1.1. BT has been acting up again, audio over BT is screwy, and installing any app as a system app is hit or miss (more often a miss). I'm not flashing anything new until I see/hear something that makes me think things are getting better (unless I find something better first).
[Verizon Samsung Galaxy S 4] Slim1023:
I've been getting some random reboots the last couple of days. Also having MMS/group message issues. I was receiving a group message, but then just suddenly got errors. Tried editing APN but didn't work. But resetting APNs to default was a temp fix.
[Verizon Samsung Galaxy S 4] indolent:
Do you know which nightly was the last on 5.0.1?
[Verizon Samsung Galaxy S 4] FernBch:
The last CM12 build was 4/16 and the first CM12.1 build was 4/17. I've thought about reverting but then I go back to poor battery life and I do not know if the fix that got the compass working after being borked for almost a year is in those builds or not.

I have also noticed a new WiFi issue but I don't know when it started or if it has always been present and just not noticed (haven't done this since CM11). It seems now that if you set a WiFi network to not broadcast it's SSID CM12.1 will not connect to it. Since it seems that most ROMs are now built off CM I tried it with a TW ROM and it does work there. I like having my private WiFi "invisible" to the masses for security reasons (just set up a new one) and this is just another deal breaker. Since I do not know if it even worked on CM12 and official bug reporting is not active I have no options to address it at this time other than this forum.
[Verizon Samsung Galaxy S 4] FernBch:
Some time ago I reported an issue with group messaging (MMS) where if you received a group message AND also have an individual message from someone in the group that it would mark all affected messages as unread. The only way to get messages to an unread state was when a message was sent to or received from an affected individual. I have received a group text recently and have noticed that the below posted action I have done seems to have fixed this issue as well. I tried this because there were messages in my history that I did not want deleted because the only known fix was to delete the entire database.

Hole some find it useful.

I finally figured out the "could not send message" error I was getting as soon as I opened Messaging.

Using SQLite Editor I opened Phone/Messaging Storage, then opened mmssms.db. Inside the "PDU" enty I noticed one line had a zero in the read column and all other listings had a one there. I deleted that line only. Now when I open Messaging I no longer get that error.

What was happening was I would get a notification pop up every time I opened messaging saying "this message could not be sent". Opening the message would give a blank, unaddressed message and choosing discard from the menu did nothing but exit messaging.
[Verizon Samsung Galaxy S 4] ctoph0:
I had that same error, could not send messaging. What I rid was turn off notifications for it and it went away, I was still able to see notifications from SMS and MMS
[Verizon Samsung Galaxy S 4] gmp029:
I dirty flashed 5/13 over 5/10 and had repeated system ui crashes after restart. I then dirty flashed 5/12, which seemed to correct the problem.
[Verizon Samsung Galaxy S 4] .Ejekt:
Just chiming in. I'm still on 5/03 and everything is stable. :)
[Verizon Samsung Galaxy S 4] ctoph0:
Is anyone else getting random reboots and than a System UI crash to load a black screen? im on 5/11 but this has happened on older versions too
[Verizon Samsung Galaxy S 4] phonedawg:
What about BT?
[Verizon Samsung Galaxy S 4] indolent:
Bluetooth streaming from an online source as well? I'm debating downgrading but I don't recall when I thought bluetooth was fully working.

I haven't seen any reboots or black screens in a long time.
[Verizon Samsung Galaxy S 4] ctoph0:
I fixed the boot to black screen by messing with the profiles settings that were enabled. switching to default while in airplane mode seams to load the system UI
[Verizon Samsung Galaxy S 4] .Ejekt:
I don't use that functionality so I'm not sure. BT calls work fine though.
[Verizon Samsung Galaxy S 4] eikoo:
5-15 works great BT works, cell network unavailable seems to be fixed.
[Verizon Samsung Galaxy S 4] natec003:
Do you happen to use Pandora for streaming?? I believe I was on 5/2 and BT worked great, but would then force close using Pandora.

Sent from my S4
[Verizon Samsung Galaxy S 4] stackz07:
I lost root when I flashed this.. Then downloaded towelroot but it displays all messed up on my screen, I can't see the make it rain button. I changed my dpi to 440..Still nothing... any ideas?
[Verizon Samsung Galaxy S 4] natec003:
Enable developer options and change the setting for root access... Should do the trick

Sent from my S4
[Verizon Samsung Galaxy S 4] indolent:
I was on 5/15 over the weekend and Pandora still has bluetooth errors.

I saw a couple random reboots on 5/15 over the last couple days as well now.
[Verizon Samsung Galaxy S 4] drt054:
I completely lost gps and bt streaming kept fc. Flashed back to AntareOne's & Alucard's Optimized cm12.1 (i9505 forum) from 5/6 and all is good again.

http://xdaforums.com/galaxy-s4/i9505-orig-develop/exclusive-antaresone-alucard24-s-t3066696

Good build if you need to clean flash to get some functionality back, and you can dirty flash new nightlies without problems.
[Verizon Samsung Galaxy S 4] asharad:
The only problem I'm having is Google Voice search doesn't work. Should I try a different GAPPS package? Which one?
[Verizon Samsung Galaxy S 4] natec003:
Yep, worked for me. Used PA gapps

Sent from my S4
[Verizon Samsung Galaxy S 4] asharad:
I fixed it by updating the app in the Google Play Store
[Verizon Samsung Galaxy S 4] stackz07:
How stable are these nightlies?
[Verizon Samsung Galaxy S 4] lehthanis:
I just flashed 5/25 yesterday and haven't had a single issue. I upgraded from cm11 m12. So it was a big jump. I don't use Bluetooth so I don't know if that's stable or not. Gps works. Haven't tested compass.
[Verizon Samsung Galaxy S 4] FernBch:
Compass has been flawless since invisiblek fixed it.
[Verizon Samsung Galaxy S 4] lehthanis:
Just tested it and yup. Compass is rock solid. Haven't really tired on a compass app since my og droid and its amazing how much smoother the compass sensor is now than back then.

Where can I view change logs from night to night?
[Verizon Samsung Galaxy S 4] FernBch:
Compass is spot on in all my third party apps, too.

Changelogs available here:

http://www.cmxlog.com/12.1/jfltevzw/
[Verizon Samsung Galaxy S 4] tryanDLS:
Screen turns off when making call

Running 5/25 nightly.

When making a call, the screen shuts off and won't come back on until call ends. Pressing buttons has no effect. I've seen some old threads about this and disabling a setting, but I don't see any of the mentioned settings in this version. Nothing under Phone|Settings or Settings|Display&Lights. Haven't found any setting to disable Proximity Sensor either.

Just got this phone so can't say if was working prior to this nightly.

EDIT: updated to 5/27 nightly with no change. Definitely seems like issue with proximity sensor. If I remove case, the screen stays on. With case off, waving a finger anywhere near the top of phone, or covering it complely shuts the screen off.
[Verizon Samsung Galaxy S 4] lehthanis:
I've had this problem for a while. I don't think it's a software issue. It's the proximity sensor itself being clogged with dust. Blow out the earpiece with a can of compressed air and see if it helps.
[Verizon Samsung Galaxy S 4] .Ejekt:
Still rocking 5/15. Anything worthwhile in the recent builds that I should update for?
[Verizon Samsung Galaxy S 4] snakecharmer23:
+1

I had the same issue a while back. A shot of compressed air into the earpiece fixed it for me. Now I do it every month or so as a preemptive fix.
[Verizon Samsung Galaxy S 4] indolent:
I just updated from 5/15 a day or two ago and I can't say I notice much different. I am back to having a video playback issue. Both youtube and embedded videos on websites are jittery or just play for a few seconds and stop. It's not a buffering issue that I can tell because it happens with good service on let or wifi. I had this same issue about a month ago and it eventually went away, but came back. I really should just give up on hoping bluetooth will ever work properly and stop updating when everything else is good enough. I'm just holding out for my upgrade in July at this point.

This was an issue for me about a year ago as well. If the compressed air doesn't work, there was a way to recalibrate the sensor with the terminal that someone found. It was from this thread: http://xdaforums.com/showthread.php?p=42675236

Here is a copy and paste from my notes.

$ su
# echo 0 > /sys/devices/virtual/sensors/proximity_sensor/prox_cal
# echo 1 > /sys/devices/virtual/sensors/proximity_sensor/prox_cal

MANUAL METHOD
##.. FINDING OFFSET ######
cat /sys/devices/virtual/sensors/proximity_sensor/prox_cal

note down the values it returns.. mine is 5,64,100.. you only need the 1st value which is 5.
### FINDING NORMAL STATE ######

cat /sys/devices/virtual/sensors/proximity_sensor/state
note down the value if returns. mine is 64

now ADD OFFSET value + Normal Value
14+71 = 85
Convert in Hexadecimal which is 55.

# echo -en $'\x55' > /efs/prox_cal

then
# chown system:system /efs/prox_cal
# chmod 644 /efs/prox_cal
# sync
# reboot
[Verizon Samsung Galaxy S 4] tryanDLS:
Tried the 1st way with no change. Haven't tried the manual way. Is this a typo?

14+71 = 85

Should be 5+64=71, then converted to hex 47?

Also tried the Proximity Fix app from PlayStore, which doesn't appear to work on this phone.
[Verizon Samsung Galaxy S 4] indolent:
Yeah, the numbers might not be correct in my post. Like I said, it was from my notes in google keep so I probably changed some of them to keep track while I was doing this to my phone. I didn't actually go back and make sure the example looks correct. Just go with whatever numbers your phone shows for those commands.
[Verizon Samsung Galaxy S 4] Tortuga:
Several months back I physically cleaned my proxy sensor. I watched a how to video and the hardest part is removing a series of small screws. It was 0% nerve wrecking. I'd recommend it, as I've been set on all ROMs (AOSP, CM, or TW) ever since.
[Verizon Samsung Galaxy S 4] tryanDLS:
Looks like maybe I missed the part about rebooting. After doing this

$ su

# echo 0 > /sys/devices/virtual/sensors/proximity_sensor/prox_cal

# echo 1 > /sys/devices/virtual/sensors/proximity_sensor/prox_cal

problem seems to be resolved after reboot unless i cover the indicator lights, which is to be expected.
[Verizon Samsung Galaxy S 4] rhricik447:
I'm having the same problem - haven't found a solution yet. I have reflashed CM (currently on 20150529), tried most of the suggestions I have found on Google using "no LTE with Cyanogenmod 12 Verizon", installed the verizon 5.0.1 upgrade (alread rooted) that installed new firmware for modems, nothing I do gets me to LTE. I keep looking...

On the other hand, other than that it has been pretty stable - GPS works, BT works (for what I use it for - UConnect in my Challenger), compass works now, don't use the messaging app ( use 3rd party app instead), the camera is still problematic, but HDR Camera works, so I use that. Since most of my internet activity is still from my laptop, not having high speed data isn't killing me - just couldn't deal with TouchWiz any more, absolutely hated it.

Phone is coming up for replacement soon, considering one of the Nexus ones, just to get to a clean interface and eliminate the magic needed to get root on devices any more, but then I'd miss the memory card...
[Verizon Samsung Galaxy S 4] ViperZ28:
I ended up going to Verizon store and getting a new sim chip, lte is back.
[Verizon Samsung Galaxy S 4] lehthanis:
This. I liked the sound of this and looked it up and it is absolutely easy to pull off. Got my sensor cleaned up and working like brand new. I love it.
[Verizon Samsung Galaxy S 4] SinfulRoad:
Hey, just wondering if I'm the only one who's been having problems updating CM manually from TWRP. Dunno if I missed a memo or anything. I tried to go from 5/21/15 to 5/22/15 just as an example and it just get's stuck at the Samsung screen. I'm pretty sure we're not supposed to fix permissions anymore so I don't do that, and I don't think clearing the cache/dalvik makes a difference (plus lollipop doesn't use dalvik I thought.)
[Verizon Samsung Galaxy S 4] jackburnt:
Anyone missing Trusted Places? I have Trusted Devices, Faces, and Voice, but no Places.

EDIT: Nevermind, it came back! Weird.
[Verizon Samsung Galaxy S 4] phonedawg:
BT issues still exist on 5/31 especially when you use it for media audio. - The first few BT connections after a reboot might work but BT eventually crashes and then BT does not work until a reboot.

Anyone else still seeing the above issues or is it just me?
[Verizon Samsung Galaxy S 4] tryanDLS:
Haven't tested latest yet, but as of 5/27, I was still having issues. Initially my phone paired to my car, but since then it has been unable to again. Will try with latest and see if anything changes.
[Verizon Samsung Galaxy S 4] gmp029:
I'm not sure if this came from google or from cm, but the addition of the camera option to store to SD card is greatly appreciated!
[Verizon Samsung Galaxy S 4] .Ejekt:
What do you think you'll be upgrading to?
[Verizon Samsung Galaxy S 4] indolent:
Honestly, I'm leaning toward the Nexus 6, even though I'm not really sold on the size. Is there anything else even rootable on verizon anymore?
[Verizon Samsung Galaxy S 4] snakecharmer23:
It's from CM.

http://review.cyanogenmod.org/#/c/96221/

http://review.cyanogenmod.org/#/c/96222/
[Verizon Samsung Galaxy S 4] BPHusker:
I thought the M9 was and I think there is a method for the S6. Now regarding unlocking the bootloader, I don't think its possible.
[Verizon Samsung Galaxy S 4] Drake9897:
Also worth mentioning that an APP in the play store called "S4 Sensors" can recalibrate to accommodate for the dirty sensor. I bought the app and my sensor works like new in every ROM!
[Verizon Samsung Galaxy S 4] tryanDLS:
Updated to 6/1 nightly and BT issues seem to be solved, at least as far as I can tell. Phone immediately paired with car and after a reboot, phone kept BT enabled and paired with car again. Only turned BT off/on one more time and it paired again. Can't say for sure if the multiple on on/off cycle problems have been solved.
[Verizon Samsung Galaxy S 4] indolent:
My issue has always been streaming internet radio over bluetooth. 6/1 still has that issue. The phone will pair with bluetooth fine, and start playing, but after one or couple songs, it just stops. The phone still shows it playing, but I can't hear anything. I'm not getting the bluetooth share has stopped error messages anymore, but the stream still isn't working. It doesn't have any issues if I'm playing songs directly from the sd card though.
[Verizon Samsung Galaxy S 4] ViperZ28:
Is it ok to dirty flash nightlies?
[Verizon Samsung Galaxy S 4] FernBch:
Yes. Just make sure to wipe cache and davlik cache. All your data will remain.
[Verizon Samsung Galaxy S 4] indolent:
Well, I just bit on the $150 off on the Nexus 6. My S4 with mdk bootloader will be on swappa pretty soon.
[Verizon Samsung Galaxy S 4] rholm:
Is that a Nexus 6 on Verizon? How much storage did you get? I would miss my extra SD storage.

Cheers,

Rich
[Verizon Samsung Galaxy S 4] indolent:
Yeah, I'm sticking with Verizon. Three of our for lines still have unlimited data. I don't use much storage on my phone, but I went with the 64GB one just in case.
[Verizon Samsung Galaxy S 4] tryanDLS:
OK, had a chance to to go a day without rebooting and can see the problems with BT connection re-appearing. Maybe it gets confused when it can't connect to a device for a while and just crashes. Turning BT off/on doesn't help - have to reboot and it works fine again.
[Verizon Samsung Galaxy S 4] Spookymyo:
Since when did Verizon get the 64gb version? Last time I checked they only offered the 32gb.
[Verizon Samsung Galaxy S 4] indolent:
I mentioned I bought it during the $150 off sale, which is through the google store. All carrier versions are the same so it works with Verizon as well.
[Verizon Samsung Galaxy S 4] jackburnt:
I cleaned the shed yesterday (6 hours, ugh), and I had the same BT issue: I'd listen to one song, then BT would stop working.

However, I dirty flashed 06/06 and it worked fine! So update your ROMs if you're still having the BT issue.
[Verizon Samsung Galaxy S 4] tryanDLS:
6/6 Release seemed to fix BT issues for me too - been working without reboot for 3 days.

Also fixed a problem with POP3 email sync. Ever since I installed 12.1, I could never sync my POP3 email account - 3 other IMAP email accounts synced without issue. Magically after installing 6/6, POP3 started syncing with no further action from me.
[Verizon Samsung Galaxy S 4] indolent:
Tried it today but I still have the same issue. Not sure why its working for you guys.
[Verizon Samsung Galaxy S 4] jackburnt:
It stopped working for me too, which was weird. I then rebooted and it was ok for a bit.

So BT isn't resolved. I'll try to dirty flash today to see if it helps.
[Verizon Samsung Galaxy S 4] phonedawg:
first post in over a week - wow, is S4 dying?

Is BT still screwed ? - I have not updated past 05/31 because later nightlies had issues with Android Auto
[Verizon Samsung Galaxy S 4] FernBch:
It may very well be. I still rock my S4, just running a different ROM. Couldn't deal with the issues and waiting an eternity for fixes.
[Verizon Samsung Galaxy S 4] phonedawg:
what ROM are you using?
[Verizon Samsung Galaxy S 4] dansan382:
this might be a stretch, see if anyone knows.

trying to sell my GS4 and the guy wanted me to keep it with the mdk bootloader and with cm12.1 on it. some reason instead of reflashing the rom and wiping everything out I decided to click the factory reset button within the OS. phone tried to reboot into recovery and now just stays at the teamwin screen, goes back and cycles the teamwin logo. if i pull battery it says in the corner its booting recovery and does the same thing. I can't seem to get back into teamwin to reflash the rom at all. cant boot into the OS and not sure how i can fix this.

my last resort is odin flashing the original MDK file and then starting all over again. any help?
[Verizon Samsung Galaxy S 4] grussinko:
Try removing the battery and booting into download mode holding volume down, then cancel and reboot. I was stuck in a recovery bootloop at one point and that got me out of it.
[Verizon Samsung Galaxy S 4] dansan382:
i can get into download mode just fine. so you're saying do the key press combo to get to download mode, get to that warning screen about download mode. instead of using hitting volume up to get into download mode fully you just hit volume down and restart the phone?
[Verizon Samsung Galaxy S 4] grussinko:
That what got me out of the loop when it happened to me, yes.
[Verizon Samsung Galaxy S 4] dansan382:
thanks for the tip. I'll give it a try when I get home later tonight.
[Verizon Samsung Galaxy S 4] dansan382:
dude... i cant believe it but this worked... you are absolutely awesome. thank you so damn much
[Verizon Samsung Galaxy S 4] grussinko:
No problem, glad it worked! I thought my phone was a goner when it happened to me, luckily it lived to fight another day.
[Verizon Samsung Galaxy S 4] Apokriphos:
This is an amazing Rom, thank you so much for your work. I only have two issues:

Issue 1: Bluetooth sometimes fails when using two devices connected to the phone, such as car speakers and smartwatch.

Issue 2: Phone will heat up quite drastically (no idea why) causing rapid battery loss. A reset fixes this. Battery analysis programs just show that the OS is taking up a large portion of the battery during these times. I only have Gapps and a battery stat program installed on the rom.

I just updated to v 6-18 and will let you know if these problems persist. Thanks for the great work!
[Verizon Samsung Galaxy S 4] FernBch:
#1 has been plaguing CM for some time.

#2 may be caused by Google services. Use Better Battery Stats and the root cause may be identified.
[Verizon Samsung Galaxy S 4] ctoph0:
I'm on 5/12 and have been out of the country for a few weeks. Any new advancements that would suggest and upgrade to a newer nightly?