yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] Danvdh:
gravitybox took over if you chose CDMA options im guessing?

WOW YOU JUST TIPPED ME OFF HUGE!!!! take a look at this in google dialer

<string-array name="preferred_network_mode_choices">

<item>LTE / WCDMA</item>

<item>LTE</item>

<item>Global</item>

<item>GSM/WCDMA/LTE</item>

<item>CDMA + LTE/EvDo</item>

<item>CDMA/EvDo/GSM/WCDMA</item>

<item>EvDo only</item>

<item>CDMA w/o EvDo</item>

<item>CDMA/EvDo auto</item>

<item>GSM/WCDMA auto</item>

<item>WCDMA only</item>

<item>GSM only</item>

<item>GSM/WCDMA preferred</item>

</string-array>

<string-array name="preferred_network_mode_values">

<item>12</item>

<item>11</item>

<item>10</item>

<item>9</item>

<item>8</item>

<item>7</item>

<item>6</item>

<item>5</item>

<item>4</item>

<item>3</item>

<item>2</item>

<item>1</item>

<item>0</item>

i simply need to change this to my teleservice values!
[Verizon Samsung Galaxy S 4] bswides412:
Regular ol' Verizon S4. This ROM was ported over from the GPE and modified to work with the Verizon S4 with MDK boot loader.
[Verizon Samsung Galaxy S 4] maddog00:
I'm having the same issue. Is this a lollipop issue?
[Verizon Samsung Galaxy S 4] krypto1300:
I'm having this issue on one of my MDK's. The other one is just fine. They've both been running pretty much the same ROM's since I got them. So strange?

I've tried a bunch of different fixes except flashing back to TW and Odin back to stock. Going to try flash TW first and see if that fixes it.
[Verizon Samsung Galaxy S 4] Alxoom33:
It' for the MDK version of the VZW S4.

Yeah, what he said.[emoji106]
[Verizon Samsung Galaxy S 4] AzureShadow:
It doesn't seem to be. Shortly after posting this problem last night, I downloaded the latest CM12 and flashed it. No problems with GPS at all there.

I tried flashing back to a touchwiz rom (hyperdrive) getting a lock there, and then flashing back and that did nothing for me. I also thought about trying to Odin to stock, get a lock, and then flash back, I just haven't had time. If you do, let me know how it goes.
[Verizon Samsung Galaxy S 4] Kenpachi 91:
I had this issue when I flashed the Christmas build. However, I reverted back to my nandroid backup (Bonestock v1.1.3 which is TouchWiz based), got a GPS lock, and actually drove around a bit to make sure it was fully working lol. I had all the options checked in the location settings. Rebooted with maps open (so I knew I had a lock), flashed the rom, and I've had no issues since.
[Verizon Samsung Galaxy S 4] AzureShadow:
I had a little bit more time than I was expecting today, so I took the time to completely unroot and Odin back to full stock. Rerooted and everything. Then downloaded GPS Status and Toolbox, got a lock, rebooted to recovery while GPS status and toolbox was running, then installed and that seemed to finally solve my GPS issue. I had done the same thing with a touchwiz based rom (hyperdrive) and it didn't work, don't know why.
[Verizon Samsung Galaxy S 4] bswides412:
Everything seems to be working well. MMS does work, but it seems to have a bit of a lag when sending and receive messages. Has anyone else experienced that?
[Verizon Samsung Galaxy S 4] mjdavis871:
I use Google voice as my primary number, and as of late, I can't call out with GV. ..I can call out using my cell number, but the dialer crashes or hangs up and doesn't complete the call with GV.

Sent from my Eclipsed Galaxy S4
[Verizon Samsung Galaxy S 4] krypto1300:
Thanks, I'm just going to try Odin then. Now that I think of it, the MDK S4 that GPS works has been Odin'ed back to stock once before. Maybe that's why its not having any issues.
[Verizon Samsung Galaxy S 4] jackdubl:
Does anyone know of an easy way to REMOVE the carrier label from the notification tray?

Free storage from Copy:

https://copy.com?r=cScoov
[Verizon Samsung Galaxy S 4] Kenpachi 91:
I only see the carrier in the upper left corner on the lockscreen, no where else
[Verizon Samsung Galaxy S 4] jackdubl:
When you pull down the notification tray, at the bottom of the screen.

Free storage from Copy:

https://copy.com?r=cScoov
[Verizon Samsung Galaxy S 4] Kenpachi 91:
Not for me. First pull down states “no notifications" (it's almost 3am by me) and another pull down just shows the quick toggles. Screenshot?
[Verizon Samsung Galaxy S 4] jackdubl:
Oh, sorry, my bad. This is a question about the 4.4.4 rom.

Free storage from Copy:

https://copy.com?r=cScoov
[Verizon Samsung Galaxy S 4] sbradley07:
You can change it under the GravityBox Status bar tweaks. Put in a space to make it empty.
[Verizon Samsung Galaxy S 4] jackdubl:
Any way without Gravity Box? Maybe a build prop edit or something? I don't want to use Gravity Box just for that.

Free storage from Copy:

https://copy.com?r=cScoov
[Verizon Samsung Galaxy S 4] rdefino:
I thought you needed Xposed framework for gravity box to work on lollipop? Is there a supported frame work out there?

Thanks
[Verizon Samsung Galaxy S 4] TheLoonyRebel:
Not as of right now. This thread on github will explain what is going on and what not.

Let me quote the post by rovo89 in this thread....
[Verizon Samsung Galaxy S 4] sbradley07:
I was responding to jackd's question about his 4.4.4 ROM
[Verizon Samsung Galaxy S 4] rdefino:
So is anyone else having awfull battery life with 5.01?

I noticed that the Mediaserver process use most of the battery. I googled and searched and cannot figured out how to resolve this.

I removed my sd card, and did a factory reset and loaded not apps other than GSam Battery monitor you can see by my screen shot , the process is still sucking up most of the battery.

Any thoughts?
[Verizon Samsung Galaxy S 4] rdefino:
Ok ,thanks. I got all excited and thought I could use gravityBox. :)
[Verizon Samsung Galaxy S 4] el6006:
I have the same problem. I can dial out using my Google Voice number if I use the Hangouts Dialer. Regular dialer closes unless I call using my carrier number. Weird.
[Verizon Samsung Galaxy S 4] crovax33:
ROM has been running flawlessly since I flashed on the 12th... Until today. Don't know if this is ROM related but maybe you guys can help.

Out of nowhere, my phone kept shutting off. Couldn't use it for more than a minute after booting before it would turn off completely. Battery was charged so I was kind of like 'wtf'. Then all of a sudden it wouldn't even get to the swirling colors screen. It would shut off halfway though the Samsung Custom logo. ****. Tried plugging it in and pulling the battery multiple times.

I can't even boot to recovery! The blue text shows in the upper left but then it will go off again.

It's plugged in now but not showing the battery screen.

Am I ****ed? Is this thing bricked? Super random because I changed NOTHING this morning and it was fine yesterday. Can anyone save my life here?
[Verizon Samsung Galaxy S 4] CarvedArt:
Sounds like the battery. Can you try a different charger/cable?
[Verizon Samsung Galaxy S 4] rdefino:
How can I tell if I have the rom from the 12th or the 5th installed?

thanks
[Verizon Samsung Galaxy S 4] CarvedArt:
By the build number under "About phone" 20150105 or 20150112
[Verizon Samsung Galaxy S 4] natec003:
I was having the same issue with gsam... However I don't think the media server is actually draining anything. If you go to the built in battery stats it doesn't show up on the list. Also if you download better battery stats its not actually causing a wake lock. It may be an issue with the app itself. I have been getting great battery life with the rom >1day life with >3 hours screen on time. I just chose to live with the app reporting that way lol

Sent from my S4
[Verizon Samsung Galaxy S 4] CarvedArt:
Try unchecking any syncs under your Google account that relate to media. Then enable them one at a time until you figure out the culprit. I'd start with Google music.
[Verizon Samsung Galaxy S 4] rdefino:
Thanks, I checked under settings-accounts and didn't find anything related to Google music.

I found app data, contacts, gmail, people detail and sound search for google play.

Am I in the right section?
[Verizon Samsung Galaxy S 4] CarvedArt:
Yup, you could try Sound search.
[Verizon Samsung Galaxy S 4] Gosimer4:
I noticed 2 strange things today. During a clean install of 1/12 , when I skipped wifi setup, it would not connect to Googles servers. It would default to setting up a new account. I wiped and installed again with the same result. When I enabled Wi-Fi, it had no problem and asked for my account name for gmail. I had done the same thing when I first set up 1/12 least week without Wi-Fi and had no problems. I thought it was odd when I tried to set up AdAway next. It would hold on downloading until I turned on Wi-Fi. As soon as I did, it connected. Chrome worked regardless without a problem. Any ideas? Could I have a setting wrong? It happened with both global and LTE on Verizon.
[Verizon Samsung Galaxy S 4] Nhawk:
Yes, but hangouts dialer uses data and thus is more jittery. I have the same issue with GV BTW.
[Verizon Samsung Galaxy S 4] mjdavis871:
What is weird is that it worked in the beginning and it just stopped

Sent from my Eclipsed Galaxy S4
[Verizon Samsung Galaxy S 4] Jrowe820:
Note 4 sm-n910p lollipop update?
[Verizon Samsung Galaxy S 4] arcane spade:
I tried to test to see if working for me, it's not. I set up google voice to ask which number to dial out with. When I place a call the option comes up to select carrier or google number but the call was already in progress on carrier number while the option to select was still up on the phone.
[Verizon Samsung Galaxy S 4] onemandeep:
MMS / APN

Im still on the 12/24 5.0 build. Initially tested MMS while on/off wifi and had no issue receiving or sending. Lately i have lost the ability so send/receive. Before I can take the most recent update I have an mms I need to DL and it expires on the 22nd. I have tried flashing the the Slimkat apn fix, also tried running the script post here that copies and creates a new APN sheet, and tried manually entering the APN in mobile data settings and rebooting.

No idea how i went from perfect mms to no mms, but Any advice on getting it back is helpful

Edit: You cant forward an undownloaded mms, can I back it up an DL after updating to 5.0.1? And are there MMS issues in the new build?
[Verizon Samsung Galaxy S 4] glicholas:
I noticed that the majority of recent posts have been issues people have been having. I'm not trying to imply that these aren't valid issues, I just wanted to put in a good word from my experience. I flashed the 1/5 build, then dirty flashed the 1/12 build when it came out because I wanted the OnePlus camera. Everything I've tried has worked. MMS, Bluetooth, Google Play Movie Streaming with my Chromecast, Exchange, GPS, etc... If there's anything people have run into that they want me to test, I'd be glad to. This might help with sorting ROM issues from unrelated issues.
[Verizon Samsung Galaxy S 4] joshua_:
no sound?

Hi all,

I installed this ROM last night, and after getting over some issues with flashing with CWM (and moving to TWRP), I got it to boot happily. Everything seems to work well, except for one issue: the phone is incapable of making any sound!

This is a very pleasant experience in general, but when people need to reach me, it can get problematic. (This is a clean flash.)

In particular, pressing the volume buttons makes no 'boop! boop! boop!' noise, and when I do that, I get the following in logcat:

V/AudioPolicyManager( 293): setStreamVolumeIndex() stream 2, device 0002, index 7
V/AudioPolicyManager( 293): setStreamVolumeIndex() stream 8, device 0002, index 15
V/AudioPolicyManager( 293): setStreamVolumeIndex() stream 7, device 0002, index 7
V/AudioPolicyManager( 293): setStreamVolumeIndex() stream 5, device 0002, index 7
V/AudioPolicyManager( 293): setStreamVolumeIndex() stream 1, device 0002, index 7
E/AudioPolicyManager( 293): getDeviceForStrategy() speaker device not found for STRATEGY_SONIFICATION
V/AudioPolicyManager( 293): getOutput() device 2, stream 2, samplingRate 0, format 0, channelMask 3, flags 0
W/AudioPolicyManager( 293): getOutput() could not find output for stream 2, samplingRate 0,format 0, channels 3, flags 0
V/AudioPolicyManager( 293): getOutput() returns output 0
E/ToneGenerator( 2656): Unable to marshal AudioFlinger
E/ToneGenerator( 2656): ToneGenerator init failed

Ringtones don't work either, and YouTube / Google Play Music refuse to play, too.

I tried both with the normal DSP and with the Cyanogen DSP, and got the same results.

Has anyone seen this? This seems like a great daily driver ROM that I'd love to use!

Thanks.
[Verizon Samsung Galaxy S 4] Neffy27:
Try sending an MMS to someone. My MMS stops working every so often and I send one to my Wife, and the others just happen to follow after. I can't explain it, hope this helps.

---------- Post added at 07:06 PM ---------- Previous post was at 07:06 PM ----------

Any possibility of getting the stock Samsung Internet browser over to this GPE?
[Verizon Samsung Galaxy S 4] parrotheadmjb:
Are insurance replacements MDK?
[Verizon Samsung Galaxy S 4] mcconvict:
Highly doubtful
[Verizon Samsung Galaxy S 4] Shaftamle:
No, deffinitly not. Haven't been for over a year. They started disappearing when me7 hit. Your best chance is swappa.com

Sent from a Shaftamle Galaxy S4

"Thanks Button" is always appreciated!

149ThemedGoogleKeyboards!!!!!!

Eclipse ROM fatness!

MyColorScreen
[Verizon Samsung Galaxy S 4] CarvedArt:
Did you come from CM by any chance? It appears that your sound driver isn't correct.
[Verizon Samsung Galaxy S 4] Nath5:
Is the download for this ROM the same as the one in the unified thread. I am unable to make our receive calls after a clean flash. When I dial a number it takes about a minute for the in call ui to come up. I don't hear any ringing but the calls goes out. Sadly they can't hear me and I can't hear them. Any ideas?

Sounds like I am having the same problem as the prayer above no sound. YouTube fails play music fails. Not sure if that is what is causing the phone call problems.

I came from Antares unified cm12
[Verizon Samsung Galaxy S 4] joshua_:
I came from CM, but I clean flashed and then only restored things I cared about with TiBu.

dmesg does contain a bunch of scary things about media:

<3>[11537.158202] apr_tal:open timeout
<3>[11537.158294] APR: Unable to open handle
<3>[11537.158416] q6asm_audio_client_alloc Registration with APR failed
<3>[11537.158508] q6asm_audio_client_free: APR Common Port Already Closed
<6>[11537.158630] msm_pcm_open: Could not allocate memory
<3>[11537.158660] asoc: can't open platform msm-pcm-dsp
<3>[11537.158721] MSM8960 Media1: dpcm: failed to start FE -12
<6>[11537.162261] tabla_startup(): wrapper substream = subdevice #0 stream = 1 id=2
<6>[11537.162261] =[ES325]=es325_wrapper_wakeup(dai->id = 2) es325 not activated 0 0 0
<3>[11537.172637] pil pil0: q6: Invalid firmware metadata
<3>[11537.172729] APR: Unable to load q6 image, error:-5

It sounds like it's having issues loading the DSP image... could this be APNHLOS-related? I'm running NC5 radio + APNHLOS.
[Verizon Samsung Galaxy S 4] Nath5:
Audio Problems Log Cats

Here are two log cats that I also posted in the unified thread. One is trying to play a song in play music the other is trying to make a phone call.
[Verizon Samsung Galaxy S 4] CarvedArt:
If you Odin back to TW then flash back to this your sound will return. CM is altering the sound driver and GE doesn't overwrite/restore it.
[Verizon Samsung Galaxy S 4] Nath5:
Just to make sure I am clear as I haven't gone back to stock in two years. Since I am on mdk I should use odin to flash the mdk odin file found here http://xdaforums.com/showthread.php?t=2289325. Then re-root, flash twrp again, and then flash this rom?

I still have rooted stock nandroid, would restoring that and then flashing the rom work?
[Verizon Samsung Galaxy S 4] joshua_:
Ok, that is a little tricky, given that I have a Developer Edition device.

Do you know where the sound driver lives? I just tried odin'ing only NON-HLOS (which, in theory, should have all the q6 stuff, but in practice, obviously doesn't, since that didn't solve my problem).

I can try odining a full non-DevEd TW ROM (removing the bootloader, of course) later to see if that helps, but I'm obviously a little nervous to do that and would prefer less drastic measures if I could :)

Also in dmesg, I see a bunch of other concerning things (lots of 'wpa_supplicant (1237): undefined instruction: pc=b6d62908', 'getprop (2384): undefined instruction: pc=b6e3b908', ...). Is this normal?

Thanks so much for your help.
[Verizon Samsung Galaxy S 4] CarvedArt:
In that case can you Odin back to stock Dev? You just need a destructive copy of the stock drivers and instructions. It looks like CM is doing a bit of driver tweaking and redirecting to garner a couple of features. I haven't really delved into where the actual error is deriving from I've just seen it creep up in devices coming from CM. I was going to look a little deeper to figure this one out, but I haven't had an extra minute yet.
[Verizon Samsung Galaxy S 4] Nath5:
Thanks for the suggestion. I went back to tw worth Odin then flashed this ROM and it is working great.
[Verizon Samsung Galaxy S 4] Beefcake550:
Newb alert....

I'm trying to use this ROM and I'm not sure what I did wrong. I was on latest stock Verizon, rooted and had TWRP installed. I then followed the very simple instructions on the first post, full wipe, flash, reboot. The problem is I reboot and now the phone tries to boot, doesn't get past the "Samsung" screen, and then reboots into Android system recovery. Grumble...

any idea what I did wrong?
[Verizon Samsung Galaxy S 4] sinner822:
Everything wrong.

Can't be on latest stock verizon and have TWRP. Can't have TWRP and stock recovery. Can't have TWRP on locked BL. Can't root latest STOCK VZW NK1 without knowing all the other can'ts you did.
[Verizon Samsung Galaxy S 4] Beefcake550:
Ok, so I rooted NK1 following the guide that says to back down to earlier kernel, then use towelroot to root device. Then go back to stock NK1 kernel. That all worked. I used root checker to validate. I then installed busybox followed by Safestrap 3.75 for verizon (says it's TWRP 2.7.1.0). I booted into Safestrap and made a backup and system, data, and cache. After that, I did wipe, flash ROM, and boom.. no work.

So, I then got it back to working with Odin (by doing home+vol down+power) and flashed in NC5 full wipe image. I'm in the process of re-installing safestrap so I can restore the image I made and hopefully be back to normal.

Am I out of luck because I have a phone which has the latest build (NK1) and cant downgrade to something older?

Thanks
[Verizon Samsung Galaxy S 4] sbradley07:
Unfortunately, you are out of luck. This ROM is only for MDK S4s.
[Verizon Samsung Galaxy S 4] Beefcake550:
Gotcha, thanks for that key piece of info.
[Verizon Samsung Galaxy S 4] TheDude:
The safestrap question has been asked a hundred times in this thread and most roms that support safestrap make it pretty evident in the OP.
[Verizon Samsung Galaxy S 4] dust.:
Not sure if this has been asked already but I did a search and couldn't find anything.

I just installed the ROM and everything seemed to go smoothly but now every time I reboot it goes straight into recovery... For info I'm on TWRP 2.5.0.2.
[Verizon Samsung Galaxy S 4] TheDude:
Update to the latest twrp and reflash.
[Verizon Samsung Galaxy S 4] Beefcake550:
Right, it's basically people like me need to realize the "norm" is that a ROM won't work on our phones unless it says so. That is the part that is sometimes hard to realize. It just makes me want to throw my phone out the window....lol
[Verizon Samsung Galaxy S 4] dust.:
This was exactly what was the issue... I feel stupid haha. Thanks for the help!
[Verizon Samsung Galaxy S 4] TheDude:
No problem.
[Verizon Samsung Galaxy S 4] CarvedArt:
Had a few minutes to look into it today... seems it is related to the modem. Which is why flashing back to stock via Odin works and no amount of wiping does. In your case you might try the non-hlos that matches your bootloader and then an updated modem only. In theory this should get your sound back.
[Verizon Samsung Galaxy S 4] joshua_:
Aha, modem, not NON-HLOS! Okay, I'll give that a try!

One more stupid question. I'm running all NC5bits. By "MDK ROM", do you mean that this simply needs to be an MDK (i.e., loki-safe) bootloader, or do I also need an MDK radio and MDK NON-HLOS? (Since I'm running DE, I obviously did not worry about upgrading my bootloader, because it's still safe for me to do so.) If you think I should try flashing MDK modem and apn-hlos, then I can try that, though obviously I would prefer to keep the latest modem in order to get all the latest bands.

---------- Post added at 05:19 PM ---------- Previous post was at 05:11 PM ----------

Sorry for the quick double post -- I just tried flashing NC5 radio (did NC5 NON-HLOS yesterday), but my phone is still incapable of making any sound.

The mystery continues...
[Verizon Samsung Galaxy S 4] CarvedArt:
I'd start back to MDK for both then just update the modem once the sound comes back.
[Verizon Samsung Galaxy S 4] IMMORTALKING69:
I thought the option to not turn on the screen when plugged in or unplugged was added but I can't get it to function after enabling and restarting. Also can I try any modern with 5.0? I seem to not be able to get above 10mb DL anywhere, WiFi works as should.
[Verizon Samsung Galaxy S 4] CarvedArt:
Any modern Retail or Dev just find one that works best for you: http://xdaforums.com/showthread.php?t=2487298 (use the "modern only" versions)
[Verizon Samsung Galaxy S 4] joshua_:
Okay! MDK radio + MDK APN-HLOS did it!

I then flashed NC5 radio, and I still have device that can boop when I hit the volume buttons.

I flashed NC5 APN-HLOS, and my phone then once again forgot to boop.

Finally, I flashed MDK APN-HLOS again, and my phone returned to booping.

MAKE SURE TO REMOVE THE BATTERY FIRST BEFORE FLASHING RADIO OR APN-HLOS. Otherwise, the eMMC's write protection will engage on thoese partitions. I wasted a lot of time with flashes that seemed just not to work.

I think the crux of it is the following:

<3>[11537.172637] pil pil0: q6: Invalid firmware metadata
<3>[11537.172729] APR: Unable to load q6 image, error:-5

Q6 is 'qdsp6', which is the DSP that runs the show on the device for audio. This firmware lives in the APN-HLOS partition; in our world, that's in /firmware/image/q6.*. It sounds then that newer (NC7) QDSP6 images don't work with this kernel.

What source was this kernel based off of? Is this an MDK-based kernel, or newer?

Thanks again so much for your help.
[Verizon Samsung Galaxy S 4] CarvedArt:
Glad to hear you got it all sorted out! Googy's source is here: https://github.com/googyanas/Googy-Max3-Kernel

It's based on Samsung*XXUFNB8 Update5*Sources & patched to*XXUGNG8 Update9.
[Verizon Samsung Galaxy S 4] idrive67elky:
Did you get this figured out? It sounds similar to my issue a while ago... Power button failing. I ended up taking the phone apart and (carefully) prying the power button innards out of the switch on the motherboard. Problem solved...but no power button.

I saw there were people on eBay who will solder on a new one, but I haven't shipped it off to get it fixed.
[Verizon Samsung Galaxy S 4] Cameron_S:
This does sound like the power button. Mine had the same symptoms. I ordered some of the buttons off ebay and replaced the old one. Not an easy job, unless you have experience with smt components and a hot air gun. Solved the problem though.
[Verizon Samsung Galaxy S 4] idrive67elky:
haha, yes... I do not have those fine soldering skills! Honestly I am afraid that if I ship it off to someone to fix, they may swap with another motherboard and then I would be stuck with something unrootable/unlockable.
[Verizon Samsung Galaxy S 4] mjdavis871:
So I installed CM12 to test out Google voice and it dials out fine without crashing or hanging up. Sounds like the dialer in this rom doesn't like Google voice