yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] .Ejekt:
Looks like Hyperdrive did the trick! Now to reinstall everything...
[Verizon Samsung Galaxy S 4] FernBch:
Flashed 4/1 this morning. I noticed on the splash screen it now says "Powered by Microsoft". Darn, there goes the neighborhood.
[Verizon Samsung Galaxy S 4] snakecharmer23:
Apparently the app drawer icon is Windows logo too. Did you get that?
[Verizon Samsung Galaxy S 4] .Ejekt:
April Fools joke, yo. :silly:
[Verizon Samsung Galaxy S 4] FernBch:
Doh!! :facepalm:
[Verizon Samsung Galaxy S 4] FernBch:
Anyone yaving issues with 4/2? So far today I have had FC's in incallUI. When they happen the ui closes and tge crash report window opens but the call doesn't hangup until I choose OK. Once this happens I can't receive calls either. I have also had issues with data connectivity. So far a reboot seems to fix it at least temporarily.
[Verizon Samsung Galaxy S 4] .Ejekt:
I'm afraid you might be the only active user still flashing each nightly. I finally have everything functioning on 3/24, and until some substantial new features get merged or 5.1 drops with the same functionality that I have now, I don't see myself flashing anything new.
[Verizon Samsung Galaxy S 4] FernBch:
Almost every nightly, but You're probably right. Doesn't matter, though.

4/3 seems better so far. A commit for telephony was reverted and some compilation errors were fixed.

Quite honestly if CyanogenMod would fix the compass/third party app issue and the bugs with SMS and group SMS's CM12 would actually be one of the best out there. I'm not sure what the issue is but these three things have plagued all CM ROMs for a long time.
[Verizon Samsung Galaxy S 4] indolent:
Do you use bluetooth or have any issues with it? I've been dirty flashing nightlies about once a week, but still have issues. I could live with the bugs you mentioned if the bluetooth could be fixed.
[Verizon Samsung Galaxy S 4] fireattack7:
I made the switch about 2 weeks ago from Carbon ROM (CM11 based) to CM12. My battery life extended greatly. I have not had any issues with the compass not pin pointing my location or any Bluetooth issues. I flash the new nightly almost every day.

Everything on my JFLTEVZW is functioning great.
[Verizon Samsung Galaxy S 4] FernBch:
I currently only use BT for a Jabra earbud. There use to be issues with BT share FC-ing but I haven't seen that in over a week.
[Verizon Samsung Galaxy S 4] natec003:
May I ask what build you're running? I've been waiting for that to be sorted out for a while. Thanks in advance!

Sent from my S4
[Verizon Samsung Galaxy S 4] checho408:
Do the recent nightly's still have the yellow tint?
[Verizon Samsung Galaxy S 4] FernBch:
Currently on 4/6. The IncallUI seems to be good again.

Haven't seen that for a couple weeks.
[Verizon Samsung Galaxy S 4] bswides412:
What is the recommended google apps to flash? The link in the OP brings to a thread that is no longer used.
[Verizon Samsung Galaxy S 4] FernBch:
I used this. It's older but Android 5.0 compatible. Any apps can be updated to the latest through the play store.

https://www.dropbox.com/s/ul2drwgxq61j7z6/pa_gapps-micro-5.0-ALPHA1-20141117a-signed.zip?dl=0
[Verizon Samsung Galaxy S 4] bswides412:
Any comments as to how this is running compared the Dan's GPE. I feel like battery has been slipping recently and I am fiddling for a charger more often...
[Verizon Samsung Galaxy S 4] FernBch:
I've never used Dan's GPE so I can't answer. As for battery life it has slipped a little but I still can go all day. Once CM merges the 5.1 changes battery life should improve. That is one of the issues 5.1 is supposed to address.
[Verizon Samsung Galaxy S 4] phonedawg:
I am on 04/06 and weird stuff has been happening. I have my headset connected most of the time. I am not sure if this only happens when the headset is connected

-mutes and disconnects the calls by itself sometimes

-back and menu button actions happen with pressing the buttons
[Verizon Samsung Galaxy S 4] deez00:
4/7 Recommended

Just a heads up to everyone, I've been running 4/7 and it's very smooth. Bluetooth seems to be fixed and I can now run swiftykey. The only problem is still with sms but I just use textra instead. Pretty stable and definitely good enough to use daily.
[Verizon Samsung Galaxy S 4] .Ejekt:
What's your SMS issue? Have you tried editing the APN?
[Verizon Samsung Galaxy S 4] deez00:
Can you point me to the apn instructions please.
[Verizon Samsung Galaxy S 4] FernBch:
I edited the Verizon Internet and the Verizon APNs so they are identical.

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

MMS Port: 80

APN Type: default,supl,mms

All other entries are unchanged. After editing save the changes and reboot. Haven't had any issues since.
[Verizon Samsung Galaxy S 4] codemac:
Has anyone had troubles with incoming calls if they use their sch-i545 phone on networks other than Verizon? I can make outgoing calls, but no incoming calls work. Also - I can't hang up once I make a call, it just sits there saying "hanging up"

I use my phone on T-Mobile, and after upgrading from cm11milestone12 to the 2015-4-6 build, I no longer receive incoming calls, and I can't hang up my phone. It looks a lot like the following bug: CYAN-2362 but I didn't have this issue on CM11, and so I'm having trouble figuring out exactly what to do.

Model: SCH-i545

CyanogenMod version: 12-20150406-NIGHTLY-jfltevzw

Android Version: 5.0.2

Baseband Version: i545VRUFNK1

Kernel version: 3.4.106-cyanogenmod-g2b03d6b build01@cyanogenmod #1 Mon Apr 6 13:38:35 PDT 2015

Build date: Mon Apr 6 13:38:35 PDT 2015

Build number: cm_jfltevzw-userdebug 5.0.2 LRX22G 453094bd49 test-keys

Any tips would be wonderful, and I can move this to a different thread if this is not the correct place to ask.
[Verizon Samsung Galaxy S 4] Jon8RFC:
This is regarding the compass/magnetometer/hall sensor/whatever you want to call it:

Invisiblek may be a bit busy, so I'll post what I sent to him, and if any of you are able to compile/test with the newer open-sourced files from Samsung for sensors and sensorhub (and I have no idea what else ties in to that), that would be a great time-saver for Invisiblek, I'm sure. I'm stuck in that arena, but I've gathered some screenshots showing what the raw data reports, and I'm not sure where to go next.
[Verizon Samsung Galaxy S 4] FernBch:
I'm currently running 4/8 and I have noticed that the brightness slider finally seems to be working 100%. I can now slide it all the way left and watch the screen brightness change. Previously anything beyond the half way mark did not work.
[Verizon Samsung Galaxy S 4] FernBch:
Just saw the CM changelog, it's all full of 12.1 goodness. I wonder when the first 12.1 nightly is gonna drop........
[Verizon Samsung Galaxy S 4] vanberge:
Yeah I'm inpatient. Been thinking about going with skanks 12.1 build
[Verizon Samsung Galaxy S 4] snakecharmer23:
For the past 2 weeks, the majority of changes in CM Code review have been for various 12.1 branches.

http://review.cyanogenmod.org/#/q/status:open,n,z

I'm hoping to see devices being switched over to 12.1 nightlies very shortly.
[Verizon Samsung Galaxy S 4] phonedawg:
I hope we can get the compass working. I think the GPE ROM would be the best place to look - I don't think Google would have the compass broken on its GPE GS4 phone.
[Verizon Samsung Galaxy S 4] rajones19:
I haven't run the GPE ROM in awhile, but last time I did, I do not believe the compass was working. If it were, I'd be running it now. Maybe I'll give it another shot sometime this weekend and see. I would love to be proved wrong.
[Verizon Samsung Galaxy S 4] phonedawg:
An untouched GPE ROM, not one modded with CM code.
[Verizon Samsung Galaxy S 4] rajones19:
The one that's out there definitely has some CM code. Hard to find anything anymore that doesn't have CM code in it somewhere. I'm not even sure Hyperdrive is completely immune. Last time I tried it, compass didn't work either. May try them both today, just for the heck of it.
[Verizon Samsung Galaxy S 4] phonedawg:
We should try asking people with a stock GPE GS4 phone if their compass works
[Verizon Samsung Galaxy S 4] FernBch:
The last time invisiblek commented on the compass issue was way back in post #138 on Jan 29th.

I think our dev's are great. We wouldn't have CM if it wasn't for them. But as far as the compass goes on the SGS4, I'm sorry to have this opinion but, The compass has been borked for a very long time and I would be surprised at this point if it ever gets fixed. It has been talked about by many users in many places. Just seems like it's nowhere near the top of their list. Again, I apologized for posting what I just did but it's only my opinion.
[Verizon Samsung Galaxy S 4] Jon8RFC:
Great indeed. It's something like this where I think we can help out and let them do the more complicated things, I'm just kind of stuck with figuring out where to go next. It seems like it may be a swap out files situation instead of a tweaking situation, like if hello.exe.bak wouldn't run on Windows, changing it to hello.exe allows it to work rather than needing to reprogram anything. I'm just not familiar with compiling (yet), and I don't understand enough of the file hierarchy and dependencies (unless referencing the "includes" in sensors/sensorhub is all that's necessary) to swap in older CM sensor drivers/files or the NC5 sensor drivers/files for testing.

I did some quick searching for a GPE ROM, but couldn't find a vanilla version, as y'all have mentioned. Samsung's vanilla NC5 source files may be just as useful in this situation, and some of them are what look to be in CM currently, but not all. Again, I'm not sure about hierarchies/dependencies, so swapping in the vanilla NC5 files is beyond my understanding at the moment.

As for the comment in the bug report about the compass seeming to sort itself out after 20 seconds, I've looked a bit more at this and found that compared to MDK, CM has a slow response with the accelerometer's x and y axes. The z normalizes quickly, but the x and y take at least 7 or 8 seconds to logarithmically go from detecting significant movement to an essential standstill, so this may be a contributing factor in cases where the magnetometer and accelerometer data is utilized simultaneously. My ex has my other s4 (it's an up-to-date VZW ROM), so maybe I can get that back from her and see how the accelerometer acts on it.
[Verizon Samsung Galaxy S 4] FernBch:
You may be onto something there. The original issue stemmed from, if I remember what I read correctly, was a driver omission/issue on Sammy's part (or something like that). It has manifested into multiple issues that may be the result of one less involved fix. What has made everyone else take notice and talk about the issues is not just the compass being so borked, but how it has negatively affected so many third party apps. I like the innovation that CM started with but am beginning to wonder what other options there may be, including TW if that's my only choice to having third party apps work properly again. It's really such a PITA to restore a TW backup on occasions when properly working GPS/Compass orientation is absolutely needed and required. Either that or carry other devices that do the same thing.
[Verizon Samsung Galaxy S 4] rajones19:
I agree 100% with FernBch - I don't think the compass will ever be fixed, or is much of a priority. Frustrating, because for me this is the only gap in this rom. I did load the GPE ROM yesterday, but it is 'touched' with CM code, and compass is still borked. I also downloaded and flashed the latest HyperDrive TW ROM, but that also has the borked compass. As of right now, the only way I know for sure to get the compass working is to reflash CM11 and Faux123's kernel. Just not ready to go back that far (I think they were from August). My upgrade comes in August of this year, and I look forward to ditching this device.
[Verizon Samsung Galaxy S 4] FernBch:
And so it begins. The final demise of the SGS4. I also will be looking into another device. The only issue is now that CM has gone mainstream, what other choices are there for custom ROMs? They are in for the money now and we aren't the source of it unless we by devices with CM installed.
[Verizon Samsung Galaxy S 4] codemac:
Fixed my VZW / T-Mo issue btw!

If you're looking to use this rom on your sch-i545, but would like to connect to the t-mobile network, then you need some pile of ril files.

Here's what I did:

- flashed jfltevzw

- downloaded the jfltetmo of the same date

unzip *jfltetmo*.zip
sdat2img system.transfer.list system.new.dat system.img
mkdir testmount
mount -o loop system.img testmount
mkdir -p newsystem/{lib,bin}
find testmount/lib -name '*ril*' -exec cp '{}' newsystem/lib ';'
find testmount/bin -name '*ril*' -exec cp '{}' newsystem/bin ';'

And then I made this zip out of it, and I edited the system.prop section of /system/build.prop to look like the tmobile ril settings: github.com/CyanogenMod/android_device_samsung_jfltetmo/blob/cm-12.0/system.prop

Now, I receive calls & can successfully hang up! Here's the .zip I flashed right after my jfltevzw build.prop edits:

mega.co.nz/#!LgRg3BZZ!nmYiYbtu_f8raSJXBNUK8eyu_3RKkh07ukUuuWgEWy8
[Verizon Samsung Galaxy S 4] .Ejekt:
The final demise?
[Verizon Samsung Galaxy S 4] phonedawg:
We need to get the compass fixed. This ROM is otherwise golden. I dont see a need to change to another phone if the compass gets fixed.

I know that invisiblek did not want a bounty to be opened. But I am afraid we dont have any options here.
[Verizon Samsung Galaxy S 4] rajones19:
Correct. Something about which you and I have conversed on numerous occasions [emoji1] . I did have some hope when I read some weeks back that Samsung had released firmware with blobs or something to that effect. I had heard at some point that missing blobs was the root of the problem.
[Verizon Samsung Galaxy S 4] FernBch:
I had heard the same things as well but I never found a definitive answer on what it was going to "fix".

Edit:

Strangely enough though, over the last week my compass seems to be a little less " wonky". It is still slow to respond to direction change when stationary but it has been pointing in a more correct orientation. I haven't tried it when walking yet but will be soon. I have an "itch" for geocaching and haven't recently because of the compass.
[Verizon Samsung Galaxy S 4] rajones19:
Glad I am not cracking up re: hearing about blobs. It is a bit frigid in Michigan for any geocaching right now, but that is one of the key apps I miss with the broken compass. As we have discussed, it does work when you are walking - but when you are standing still with a blank look on your face trying to figure out where to look, it is no help at all! Too bad, since GC has done a pretty good job on their app. I also miss the correct orientation with the astronomy apps - You know something is out of whack when Polaris is due south. I have pretty much given up on the S4 at this time, and expect to jump off to a Nexus 6 if/when they ever show up at VZW.
[Verizon Samsung Galaxy S 4] gonzlobo:
Evidently I'm the only one that's never used the compass. How do I evaluate?
[Verizon Samsung Galaxy S 4] rajones19:
The compass feeds input to other apps, mostly - like the geocaching app, or astronomy apps like Google Sky, anything that requires a directional heading while you are standing still. When you are moving, the GPS provides that information by calculating directional heading based on your changing location. The magnetic compass is supposed to do that while you are standing still. A good app to check it with is GPS Status and Toolbox, free in the Play Store. Since CM11 arrived, the compass points any number of directions, none of which is actually north. The direction it feeds to application is is always 180 degrees off; north becomes south, etc. Extremely frustrating if you are a regular user of those applications. Some of us keep hoping someone will come up with a fix. Last time mine worked with was CM11 M9 (8/4/2014), with Faux Kernel. After that, nada.
[Verizon Samsung Galaxy S 4] FernBch:
rajones couldn't have explained it any better. In a couple months I'll be up for an upgrade. Not sure what it is gonna be but the bootloader needs to be exploitable at a minimum. Unlockable would be ideal. Not sure how well that is gonna work on Big Red.
[Verizon Samsung Galaxy S 4] phonedawg:
I need my phone to adhere to the below checklist. Except GS4, no other flagship phone(including phones releasing in the foreseeable future) fits my needs. I have no option but to use this phone as long as I can

removable battery/extended triple battery

root/bootloader-exploit/cyanogenmod

good camera

world-phone/verizon

one hand operation/good screen-to-body ratio

---------- Post added at 10:25 PM ---------- Previous post was at 10:22 PM ----------

Is the compass also an issue with the GPE 5.0 ROM?
[Verizon Samsung Galaxy S 4] rajones19:
I have precisely the same concerns. I am actually surprised another Nexus device is going to VZW, after the debacle with the Galaxy Nexus, which I suffered through. My wife just retired my old Nexus for a Droid Turbo, which will likely never be rooted (but is a beast anyway).

---------- Post added at 10:32 PM ---------- Previous post was at 10:30 PM ----------

I am not sure. Last time I tried, it did not work; not sure if that was 5.0 or prior.
[Verizon Samsung Galaxy S 4] phonedawg:
Same here. It is frustrating to have a non-functional compass. If someone can get it to work, this ROM will be golden.
[Verizon Samsung Galaxy S 4] drt054:
Yes it is still a problem on GPE 5.0.1, not sure if he has updated since.

On another note, got my GPS lock by flashing AntaresOne's cm12 build then dirty flashed 1/11 nightly over it. Working great now.
[Verizon Samsung Galaxy S 4] Alarbus:
The removable battery is the only problem, but you could get a Nexus 6 and a battery brick and be all set. Which is more or less what I'm going to do once the 64gb phones are back in stock. Battery life on the S4 with CM12 seems pretty good so far, so I'm hopeful that removable batteries become less important.

(I totally remember having three batteries for my Incredible, and burning through all of them in short order. Same for the Galaxy Nexus. Haven't bought any additional batteries for the S4 though!)
[Verizon Samsung Galaxy S 4] gmp029:
Are nightly update using "settings" -> "about phone" -> CyanogenMod Updates" not functional yet?
[Verizon Samsung Galaxy S 4] Alarbus:
Not that I can tell. I've been downloading the rom on my computer and putting it into the cmupdater folder, and it works fine as far as updating from there.

EDIT: Do

not

flash today's nightly without a backup - something seems off. It didn't back up the gapps, and stripping the google account from the phone is causing some apps to chain crash. Good times.
[Verizon Samsung Galaxy S 4] phonedawg:
I updated my checklist to include one handed operation/good screen to body ratio. Nexus 6 is way too big.

I got used to having a lot of juice in my phone. This way, I only charge it overnight regardless of how much I use it.

[IMG="extended triple battery"]http://images.anandtech.com/doci/7163/ZeroLemon-9390_678x452.jpg[/IMG]
[Verizon Samsung Galaxy S 4] T3T3droid:
I fixed the MMS problem if you're interested...

Go to settings, more under wireless and network, cellular networks, access point names and open Verizon Internet. Change the following...

MMSC to*http://mms.vtext.com/servlets/mms

MMS Port to 80

APN Type to default,supl,mms

Then save in the menu and select Verizon Internet as your APN.

This worked for me so I hope it works for you!
[Verizon Samsung Galaxy S 4] crossen0:
I tested it and the picture sent immediately! Thank you so much!
[Verizon Samsung Galaxy S 4] Alarbus:
So. Do not install today's nightly.

I think the issue is that by shrinking the system partition, it doesn't have space to copy the saved gapps back over. I fixed everything, made a backup and tried again, and it still failed. When I immediately tried to install the PA Stock gapps, it errored on insufficient space.
[Verizon Samsung Galaxy S 4] vanberge:
Had this too, even on euroskanks
[Verizon Samsung Galaxy S 4] crossen0:
Oh good. Thought I was alone. But the gapps on CMs page installed for me.
[Verizon Samsung Galaxy S 4] T3T3droid:
Any time buddy! All the roms were having the issue and it was annoying me lol so I spent an afternoon in trial and error and finally got the right combination. Glad I could help!
[Verizon Samsung Galaxy S 4] FernBch:
I know, that was harsh and probably won't happen. The compass issue has got to be one of the biggest and longest running problems users talk about, if not the biggest.
[Verizon Samsung Galaxy S 4] gmp029:
I found a strange glitch on this rom which has been happening to me as long as cm12 has been around. In gallery, the pictures and videos stored on my 32gb SD card would show up in doubles or triples, sometimes with a blank space between the pictures. I can usually correct the problem by unmounting the SD card and rebooting, but it eventually comes back. Any ideas?
[Verizon Samsung Galaxy S 4] FernBch:
I have not seen that one in a long time. I finally backed up my SD card to my PC, then clean installed everything. That clean install included wiping/formatting internal and external storage.
[Verizon Samsung Galaxy S 4] phonedawg:
I asked here - http://forums.androidcentral.com/sa...ormation-needed-compass-working-lollipop.html

If compass works on stock GPE GS4, it should be easy to get the compass in CM12 fixed. Let us see what they say
[Verizon Samsung Galaxy S 4] mangalo2004:
I have the same problem. Been having it since CM11. It only happens after I reboot from recovery. Unmounting exsd and rescanning media is the only solution that I've found.
[Verizon Samsung Galaxy S 4] rajones19:
If you check that forum about 3 threads below your thread, is the following thread *****ing about the compass not working: http://forums.androidcentral.com/sa...ometer-compass-other-sensors-not-working.html
[Verizon Samsung Galaxy S 4] phonedawg:
I saw that but the problem does not appear to be affecting all users - some users were suggesting fixes as if they do not have that issue.

That's why I asked them in my thread to to use a compass app to test their compass.
[Verizon Samsung Galaxy S 4] rajones19:
I saw that too, but the suggestions to reboot and wipe cache are pointless - those are suggestions made by people who don't understand the problem. Also comments about it working when you are in the car are pointless, as the magnetic sensor is overridden by the GPS whenever you are in motion. I think the people in that thread experiencing problems knew they had problems, but the people suggesting fixes had no clue at all. I would LOVE to be wrong - but I believe if there were any easy fix for this problem, it would have been fixed long ago. I believe we are basically out of luck. And I am not by nature a pessimist.
[Verizon Samsung Galaxy S 4] FernBch:
I have all but given up on the compass, too. Everyone who has been elbows deep in the issue knows the compass doesn't work because of the magnetic and gyroscope sensors not working. Stationary just doesn't work at all and walking is a joke because of it. Someone got their attention a couple months ago when a bounty was brought up and we were told it wasn't necessary but...........

This ROM would so rock if it was finally fixed but I know IF is a big word.
[Verizon Samsung Galaxy S 4] FernBch:
Kernel/firmware/magnetometer - you have the rights idea (based on things I have read). I am no dev either and have no clue where to even begin nor do I have the resources to attempt it. Hope you find some success.
[Verizon Samsung Galaxy S 4] rajones19:
I had to crack up when you mentioned OCD and the S4 being like a photo hanging crooked on the wall - I know EXACTLY what you mean.

I agree re: kernel/driver issue. The last time the compass worked correctly for me was on CM11 M9 Snapshot dated 8/4/2014, and that only worked with the Faux123 kernel 018u. I still keep all those builds on my device in case I just have to have the stupid compass working.

Nexus 6 is starting to look really good ..... and looks like I am eligible for early upgrade. I didn't know they even did those anymore.