yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] FernBch:
X2 on the yellowish tint. GPS lock works on dirty flash. I have had random issue with WiFi not auto connecting after extended periods of deep sleep.

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

Question. CWM has always been the "official CM supported" recovery through CM11. Does this hold true for CM12? On the unofficial builds I would get messages about fixing root upon reboot. The last version I know of is 6.0.5.0. The messages do not appear in TWRP. If CWM is still preferred is the a later version out for the I545? If not then I guess this is another issue to report. I prefer CWM and want to come back to it.
[Verizon Samsung Galaxy S 4] crossen0:
I haven't experienced yellow tint whatsoever with official and euroskanks builds. My only thing is that MMS is wonky. And Bluetooth will shut off WiFi momentarily while trying to connect.
[Verizon Samsung Galaxy S 4] Alarbus:
So, that blue light on boot is pretty annoying. On the 1/10 build, it wouldn't go off after boot, or a reboot. I finally had to send myself emails until it triggered a new notification, and clearing the email turned off the light.
[Verizon Samsung Galaxy S 4] crossen0:
That's odd. It's never done that to me before. Always stops once the phone is booted.
[Verizon Samsung Galaxy S 4] rajones19:
Yes, please!!
[Verizon Samsung Galaxy S 4] drt054:
Pretty sure the Compass hasn't worked on ANY ROM in the last couple of years.. or I am just flashing the wrong ROMs. I think Samsung dropped the ball on this one. But if anyone can fix, it's [MENTION=2385005]invisiblek[/MENTION] :D No pressure!!

Is the blue light really that big of a deal when the phone is booting up?? My blue light stops the moment the phone is finished booting. I think this is the least of our problems right now.
[Verizon Samsung Galaxy S 4] FernBch:
Yes, Sammy did drop the ball on the compass. Many devs of third party apps talked about it with the release of 4.4. It was firmware related to the magnetic sensor and has never been truly fixed. It was big news too. There were articles about it on G+, at Andriod Central, and other places, too.

And for the blue led at boot, if it is now borked it should be fixed. Granted it is the least of the issues but it is an issue none the less. File a report at JIRA for the CM12 nightly regressions and be sure to include a logcat. If no one cares about the smaller issues then the bigger ones may seem less important, too. The compass is a good example of this. This report was created for CM11 and is still open today. Many people reported compass issues in the CM11 thread and I linked this jira report in the thread when I created it but very few others added info to it.

https://jira.cyanogenmod.org/plugins/servlet/mobile#issue/NIGHTLIES-258

This thread is a great place, don't get me wrong. It gives us a place to post up and talk about our issues and any workarounds we find. The developers may also visit it from time to time as well but these forums are not their main "go to place" for bug reports. There are too many forums out there. BUT, if you really want to improve the chance of fixing something it should be reported where it will be tracked. Who knows, maybe there is a place over at Sammy where people can report about the compass. I would like to think they are aware of it but.........

I am not saying to flood jira with a bunch of stuff. There are guidelines for how jira works, what it is for, and what to include in a report. Be smart about it and it can benefit everyone. If something is posted to jira and is missing required items, is not in the proper format, or is not kept up with it will be closed so don't think it can be reported and forgotten.

Invisiblek may be the maintainer for the GS4 but he is not assigned every issue for it, especially if the issue affects more than just the SGS4. Some issues go more widespread because of what component of CM they affect.
[Verizon Samsung Galaxy S 4] Alarbus:
I'm guessing that the boot led will get fixed as other things get cleaned up, if not I'll open a JIRA ticket.

The annoying part is that I was reading the gerrit discussion on that when it merged, no one thought it was important except for the unique snowflake who submitted it. It doesn't DO anything. Why do you need a blue led when the screen is going through the boot process? It doesn't have a point except to add more complexity.
[Verizon Samsung Galaxy S 4] FernBch:
Pretty much sums it up. Someone thought it would be cool or whatever so it was added. Other than that it really serves no real point, IMHO.
[Verizon Samsung Galaxy S 4] gonzlobo:
If course it's entirely possible it lights a different color for diagnosing issues.
[Verizon Samsung Galaxy S 4] thedoman:
Deleted post - was thinking about GPS issues some Roms had. Obviously my head was somewhere else. Sorry
[Verizon Samsung Galaxy S 4] rajones19:
Wow, this would be fatastic. So this fixes it so the compass always points north, when standing still, and reports north to applications that access the magnetic compass sensor? Not sure the magnetic compass is at all related to GPS. GPS provides correct direction in the compass when you are moving, but the magnetic compass has been borked forever when you are standing still.

---------- Post added at 04:23 PM ---------- Previous post was at 04:19 PM ----------

As expected, no affect whatsoever on the compass.
[Verizon Samsung Galaxy S 4] FernBch:
The compass issue is caused by lack of firmware from Sammy.
[Verizon Samsung Galaxy S 4] .Ejekt:
Glad to know I wasn't the only one. Now if only someone would be able to recreate my inability to install certain apps.
[Verizon Samsung Galaxy S 4] FernBch:
I did get MMS working and I have had no issues since that post. Look back a page or two, I linked to the post that has what worked.

Which apps are you having trouble with?
[Verizon Samsung Galaxy S 4] T3T3droid:
Glad my fix has been helping people ? it took me a while to figure out the correct things to change so I decided to post it... Lots of trial and error lol Didn't know if anyone but the guy you linked to used it.
[Verizon Samsung Galaxy S 4] Nydalxy:
Yeah, that has been the way I've been doing it since cm11. I'm a little confused why this still isn't built into the apn settings for at least vzw phones
[Verizon Samsung Galaxy S 4] T3T3droid:
Totally agree... It's not like it's an uncommon, un-replicated, unconfirmed issue with no fix.
[Verizon Samsung Galaxy S 4] Loop4zil:
Thanks for sharing this. Does this fix need to be applied after a dirty flash?
[Verizon Samsung Galaxy S 4] .Ejekt:
Here's the list so far. These aren't apps that use often, but after I noticed that one wouldn't successfully install I decided to see what else wasn't working. Sometimes, the apps will install and I'll be able to run them, but after a reboot they'll disappear.

(All from the Amazon App Store or the HumbleBundle app)

- Hitman Go

- Threes!

- Enigmo

- Guardians of the Galaxy: The Universal Weapon

- Minecraft - Pocket Edition

- Orbital

- Prince of Persia The Shadow and the Flame

- Unpossible

- AaaaaAAaaaAAAaaAAAAaAAAAA!!!

- Splice
[Verizon Samsung Galaxy S 4] T3T3droid:
No problem! Never checked cause I've been clean flashing but all you have to do is check the APN after boot and change if it's not right
[Verizon Samsung Galaxy S 4] dansan382:
whats the latest version of TWRP? rom installer is showing 2.6.3.0 for me, is that right?
[Verizon Samsung Galaxy S 4] Hawksfire:
2.8.4.0
[Verizon Samsung Galaxy S 4] Nydalxy:
I don't mean to spam the thread but considering this is a thread for a Verizon phone, I figured I'd help you guys out. Anyone that's on Verizon's More Everything plan with a lower data tier (1gb-4gb) can save some money today... http://www.droid-life.com/2015/02/03/verizon-more-everything-discount/
[Verizon Samsung Galaxy S 4] FernBch:
Don't know what happened, but something is definitely up with today's build (2/5). All of the sudden it just went haywire. Extreme lag, apps freezing, launcher crashes. It seems like a reboot is needed frequently so it stays stable.

Logcat:

https://www.dropbox.com/s/bkmljzqzfgf4ar9/Log_2015-02-05_19-36-43.txt?dl=0
[Verizon Samsung Galaxy S 4] gonzlobo:
Well that's odd. About 4 nights ago, I had the same issue with fitsnugly's build, but it cleared up on Tuesday-ish. I wonder if one of those cherrypicks made it into the official build as well? If so, it might clear up tomorrow or so.

After that laggy build, my BT became *perfect*.
[Verizon Samsung Galaxy S 4] FernBch:
I see Developer Options now has an option for updating the Cyanogen recovery with system updates. Does that even work with our variant?
[Verizon Samsung Galaxy S 4] phonedawg:
How is 02/06 doing?
[Verizon Samsung Galaxy S 4] FernBch:
So far 2/6 seems pretty good. 6 hours in an I haven't noticed any weird behavior yet.
[Verizon Samsung Galaxy S 4] rajones19:
I wiped and clean-flashed today. Battery seems to be dropping like a rock; hopefully it will settle down. Last couple weeks battery life has been fantastic, IMO.
[Verizon Samsung Galaxy S 4] FernBch:
7 hours since unplugged and down to 71% with normal usage.
[Verizon Samsung Galaxy S 4] rajones19:
That falls into my personal category of fantastic battery life. Maybe better.
[Verizon Samsung Galaxy S 4] JDecker91:
HELP!!

I tried to flash this ROM using SafeStrap 3.72 and it appears to have completely wiped my phone. When I try to boot my phone it just boots into Recovery Mode and I cant do anything. When I boot into Safestrap, I can't flash any of the other ROMs that I have on my SD card. When I try to do anything in safestrap it tells me:

E:Unable to mount '/system'

E:Unable to mount '/systemorig'

Again...HELP!!!!
[Verizon Samsung Galaxy S 4] FernBch:
You cannot flash this ROM with Safestrap. This can only be flashed on a device with the MDK bootloader. That bootloader is the only one that can be exploited to allow the installation of a custom recovery such as ClockworkMod or TWRP. Do like the OP instructs you to and run ro.getprop.bootloader from a terminal program and you will have your answer.
[Verizon Samsung Galaxy S 4] FernBch:
Up and running on 2/8. All seems good.
[Verizon Samsung Galaxy S 4] fernandw:
The 2/6 lag is present on 2/8 after 30hrs of uptime. GPS lock seemed better on 2/6. BT issue present on 2/8 but not as bad. Camera works smoother on 2/8.?.?

This is my new daily driver!
[Verizon Samsung Galaxy S 4] FernBch:
The last few nightlies have been pretty decent, no real issues to speak of (none that I have noticed). I flashed 2/12 today and am noticing a 2-3 second lag from receiving a call to when the screen lights up. Anyone else notice this?
[Verizon Samsung Galaxy S 4] thorrules:
This isn't that important, but I wanted to know that it is something that the developers are aware of. The IR blaster does not work in cm 12. Can someone else confirm this please?
[Verizon Samsung Galaxy S 4] andyc2d:
Works fine for me.
[Verizon Samsung Galaxy S 4] thorrules:
Oh really? What app do you use for IR blaster? Thanks.
[Verizon Samsung Galaxy S 4] thorrules:
CM12 on GSM (T-mobile)

Last night I switched over from Verizon to Tmobile and I have noticed 2 issues:

1. When WiFi is ON, the GSM signal keeps dropping intermittently (every 5 seconds or so). At this time if someone calls, it always goes to voicemail. However, when I turn OFF WiFi, everything works normal I can make and receive calls, no dropping GSM signal.

2. I cannot disconnect a call from my end. The call hangs up only when the other party hangs up. I use the workaround by changing to airplane mode to disconnect the calls.

Both the above issues are very annoying, has anyone had these issues or know what can be done? (I am on the CM 12 nightly 2/15 build).
[Verizon Samsung Galaxy S 4] phonedawg:
This is a long standing issue. This along with the compass issue are the only major issues with this phone - https://jira.cyanogenmod.org/browse/CYAN-2362

This was the CM11 workaround - http://xdaforums.com/showpost.php?p=50205933&postcount=13 . I would suggest trying it. Let me know how it works.

I am hoping invisiblek can fix both these issues and incorporate them into the ROM.
[Verizon Samsung Galaxy S 4] FernBch:
Is anyone having root issues lately? Over tge last two days I have had SuperSU and Root Checker report I do not have root access.

I have installed the latest nightly and have had root on initial boot only to discover later that it was no longer present. I am still in the process of trying to track it down so I unfortunately have no other info at the moment.
[Verizon Samsung Galaxy S 4] .Ejekt:
I've had this issue a few times with prior builds. Started flashing the latest SuperSU after the nightly through Cyandelta and haven't had root issues since.
[Verizon Samsung Galaxy S 4] thorrules:
It did not work. I dirty flashed the gsm zip file and phone wouldn't connect to the gsm network at all. For now I have forwarded all calls to my dumb phone. I think it's time to move on to a gsm phone.
[Verizon Samsung Galaxy S 4] phonedawg:
The post I mentioned does NOT instruct you to flash the GSM zip file. Does it?

The poster clearly said that he did NOT flash the GSM zip. All he did was edit one line in build.prop manually.

---------- Post added at 07:51 PM ---------- Previous post was at 07:44 PM ----------

No issues with 02/14. I still use CWM Recovery and manually reboot to recovery to flash the zips. The update functionality in settings does not work. I think it has compatibility issues with CWM Recovery.

After flashing, I also choose 'yes' when CWM Recovery asks me if I want to fix a file that can affect root access.
[Verizon Samsung Galaxy S 4] FernBch:
I do the same as you. Also use CWM (6.0.5.0). It's just weird. The last couple nightlies install fine, choose yes to fix root upon reboot, and it boots fine. Sometime afterwards it goes south and I have to restore my nandroid. I have a copy of SuperSU 2.45, I'm gonna cleanup 2.46 and revert and see what happens.
[Verizon Samsung Galaxy S 4] phonedawg:
I am also assuming that you allow apps root access in developer settings.
[Verizon Samsung Galaxy S 4] FernBch:
Root access is set for apps and ADB. I'm currently thinkin it's SuperSU related, it showed up after upgrading to 2.46. I updated normally and had to restore my nandroid cause it reported no root after. I had to do the cleanup for fresh install to get it to succeed.
[Verizon Samsung Galaxy S 4] phonedawg:
I would uninstall all apps that enable root access like SuperSU or superuser. In CM12, root access is enabled/managed by Privacy Guard - http://review.cyanogenmod.org/#/c/83759/
[Verizon Samsung Galaxy S 4] FernBch:
I have reverted back to SuperSU 2.45 and so far all is good. I have used SuperSU on CM12 for several weeks without issue (like the settings better). I'll see how it is tomorrow and go from there as I'm holding off on new nightlies until I get this sorted out.
[Verizon Samsung Galaxy S 4] illadelphatic:
F2FS Support?

I've read through most of this thread and didn't see any mention of F2FS support, but someone on the AntaresOne thread mentioned that CM12 official has supported F2FS partitions since the 2/11 nightly.

Can anyone confirm or deny? I'd like to switch to CM12 official nightlies but would prefer to dirty flash over AntaresOne's Optimized ROM.
[Verizon Samsung Galaxy S 4] FernBch:
You mean this?

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

It's in 2/12.
[Verizon Samsung Galaxy S 4] Alxoom33:
Yes, tried flashing with latest SuSuperuser. Don't have root. 2/15 nightly

---------- Post added at 11:04 AM ---------- Previous post was at 10:53 AM ----------

What's cyandelta?
[Verizon Samsung Galaxy S 4] illadelphatic:
Thanks. I'm not too great at searching gerrit...does CM12 support f2fs on the system partition? Your link specifies /cache and /userdata.
[Verizon Samsung Galaxy S 4] FernBch:
I honestly don't know. That is the only mention of F2FS I saw in the changelog
[Verizon Samsung Galaxy S 4] Chadwick108:
Forgot to Flash Super user at install

Had a time finding the correct zip for superuser for 5.0.2. When I found it had to install manually in recover but now all is well!

Liking the ROM so far!!
[Verizon Samsung Galaxy S 4] FernBch:
Which version or location of zip? I was using SuperSU without issue but it looks like something changed with CM in the last 3-4 nightlies. I can no longer use SuperSU without losing root.
[Verizon Samsung Galaxy S 4] Chadwick108:
supersu that fixed root issue for me

direct download link

(which was found by binging beta-supersu-v2.42 chainfire)

click thanks if it helped!!
[Verizon Samsung Galaxy S 4] bjbinc:
I'm unable to receive any phone calls...on the other end it just rings and then goes to voicemail. I'm able to place calls, but unable to hang up. I experience this problem on any ROM built from CM12...not just this rom.

I'm using a prepaid AT&T sim card. Any ideas?

Thanks!
[Verizon Samsung Galaxy S 4] rajones19:
On VZW here, but experiencing no such issue on 2/17 build. Will flash 2/18 shortly.
[Verizon Samsung Galaxy S 4] thorrules:
Please read the discussion that happened just a few posts back. Cm seems to have issues with gsm, I am on tmobile and I have same problem. No known solution yet (at least not in cm12), so I am moving on to a gsm device.
[Verizon Samsung Galaxy S 4] FernBch:
I have been doing some seriously thinking of late and I think I am going back to stock and start over to return to CM12. Today because of the issue I am having with root, SU, and CM12 I decided to do a factory reset and try to start over. Problem was when I rebooted I had SuperSU, TiBu, and Root Checker all report that root was lost (I believe it said not properly installed). This has been going on for almost a week and I am tired of it. If this doesn't work I will probably have to go all the way back to out of the box, re-root, etc, etc. I'm not exactly sure what happened but something went on when I upgraded either CM after 2/12 or SU to 2.46. I'm hopin that the clean uninstall method to switch SU app works and I don't have to go all the way back.
[Verizon Samsung Galaxy S 4] FernBch:
It seems I have been able to make an improvement with my SU issue without starting over. I uninstalled SuperSU (clean up to switch su app) and rebooted. On reboot SU was lost. Rebooted into recovery, wiped cache and davlik, dirty flashed 2/12, and rebooted. SU access has returned. I have also successfully flashed a nightly after 2/12 AND maintained root access. Not sure why but it seems I can no longer use SuperSU........
[Verizon Samsung Galaxy S 4] vanberge:
FYI fern I've had zero issues with super su 2.42
[Verizon Samsung Galaxy S 4] FernBch:
Has anyone been having issues with MMS lately? It seems to be borked somewhere in the last couple nightlies.

If I use the default setting for the Verizon Internet APN it will send and receive the notification of a new one but it will not download it. If I edit the APN like in this post it will receive but not send.

http://xdaforums.com/showthread.php?p=58574078

Anyone know how to fix?
[Verizon Samsung Galaxy S 4] rajones19:
I can confirm MMS not working, but no clue how to fix it. I have gone back as far as the 2/17 build and still no go. Another issue cropped up for me beginning with the 1/19 build - AudioManager Pro is no longer able to enable/disable my notifications. I was able to fix that by going back to 1/18, but no luck with MMS. I am going to keep moving backwards until I find success.
[Verizon Samsung Galaxy S 4] FernBch:
I figured out my MMS issue. In he APN settings there is an APN for Verizon Internet (VZWINTERNET) and on for Verizon (Internet). I played around with them and discovered they must be set the same. I edited them with:

MMSC

http://mms.vtext.com/servlets/mms

MMS Port

80

APN Type

default,supl,mms

After editing I saved both and immediately rebooted. The Verizon Internet is the selected APN. All seems OK since doing this.
[Verizon Samsung Galaxy S 4] rajones19:
No luck here. Restoring nandroid, once again.
[Verizon Samsung Galaxy S 4] FernBch:
I have noticed an issue with the WiFi settings. I'm using the 2/20 nightly, any WiFi that I set to not broadcast the SSID I cannot connect to, even if it is on my saved network list. Once I set a particular WiFi to broadcast it's SSID I can connect to it. If connected and I go to the WiFi's settings and hide the SSID it will disconnect. Anyone else see this?
[Verizon Samsung Galaxy S 4] andyc2d:
I'm currently running on the 2/22 nightly with a completely fresh install and it seems to randomly run into rough patches where almost everything lags like crazy for a while then it doesn't go away until a reboot or if you wait long enough, has anyone else encountered this?

https://play.google.com/store/apps/details?id=com.remotefairy

Seems to work fine.
[Verizon Samsung Galaxy S 4] Spookymyo:
Every TW rom I've used has had a working compass, verified with a real compass.
[Verizon Samsung Galaxy S 4] phonedawg:
invisiblek was working on fixing the compass. I hope he finds a way. This is the only issue that still exists along with the GSM issue.
[Verizon Samsung Galaxy S 4] .Ejekt:
Did 2/27 wreck cell data for anyone else?
[Verizon Samsung Galaxy S 4] Markstache:
Wanted to share this for anyone else experiencing a similar situation. I was getting absolutely horrid battery life (about 8 hours after being unplugged with light usage and it would be dead, and it was always hot to the touch) and my camera did not work. Everything was fine when I was on an early February nightly flashed using Philz. I had since switched to the latest TWRP 2.8.5.0 and dirty flashed to a late February nightly (I tried several but I don't remember the dates), and after doing those things I was experiencing the aforementioned problems.

I was becoming very frustrated, and last night I decided to see if TWRP still had the function to fix permissions, and it does so I did it, and now my battery life is back to being fantastic (current estimate in Battery stats is about 24 hours left), phone is no longer warm to the touch, and my camera is working like normal.

I don't know if this was a fluke or not, but I figured I'd share.
[Verizon Samsung Galaxy S 4] FernBch:
Anyone having issues with BTshare FC-ing? It seems to happen when I am using an app that uses GPS (Google Maps, Trimble, Oruxmaps).

Logcat:

https://www.dropbox.com/s/12hc19uoito77pc/Log_2015-02-28_13-45-22.txt?dl=0
[Verizon Samsung Galaxy S 4] RustyNailz:
Yes on the BT share fc issue. For me it happens when turning BT off and on. Also when reconnecting to my car's BT.
[Verizon Samsung Galaxy S 4] gonzlobo:
I'm on a similar ROM. BT Share FCs alot, especially when I FF through audio to the next song/podcast.
[Verizon Samsung Galaxy S 4] .Ejekt:
If I had working GPS I'd test it out :P
[Verizon Samsung Galaxy S 4] indolent:
I'm not really getting any force closes, but I am having other bt issues.

Many times it thinks it is connected, and the icon says it is, but still plays sound out of the phone speaker rather than through bluetooth.

I'm also getting the frequent skipping or "yips" again. I previously solved this by having tasker set the governor to interactive and raised the minimum frequency. This doesn't seem to be working anymore.
[Verizon Samsung Galaxy S 4] fireattack7:
I'm having issues with the 3-1 and 3-2 nightly not accepting the custom ringtones I set. If I set a custom ringtone as my general ringtone, it will play some built in tone when a call comes in. Upon reboot, all my tones are gone and replaced with a random number.
[Verizon Samsung Galaxy S 4] FernBch:
I remember having this issue on CM10. I fixed it by placing the tones in /system/media/audio/ringtones and setting permissions and ownership to the same settings as the tones already in the directory. Everything stuck after a reboot but had to be redone after flashing a newer nightly.
[Verizon Samsung Galaxy S 4] fireattack7:
If I assign ringtones to a specific contact, it will stay. My Gmail custom tones stay as well. It only applies to the general ringtone.

I will try. I thought Lollipop fixed the SD Card issues. My custom tones are on my external SD Card.