yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] cpbartlett:
Still no GV

I've tried several modems and Google Voice is still not working for me. Anyone have any ideas?
[Verizon Samsung Galaxy S 4] grumpyj1:
mms

I have not been able to find a solution for my mms being soo blurry.

Pls help me i would really like to get full or at least good resolution in the pictures received.

I am able to send full resolution pics but i can not receive...

Any help would me appreciated thank youuu
[Verizon Samsung Galaxy S 4] sauravdn:
Cell standby using a lot of battery. from the latest update.
[Verizon Samsung Galaxy S 4] davidanthony921:
software not authorized

I'm on the MDK original bootloader. I installed this rom back in December and I love it. it's been running flawlessly through all the updates since. On the last update 1/5 I updated modem to NK1to fix some problems with call quality. when trying to install newest update aroma gives no problems but when system goes to reboot after installation in a Roma it goes to a screen that says software not authorized please see Verizon.I should also mention that before installing the upgrade I updated TWRP recovery to 2. 8.4. I'm still sort of new to all this but seems like a look problem but not if upgrading modem could relocation bootloader. BTW top of screen says secure fail:kernel
[Verizon Samsung Galaxy S 4] Kenpachi 91:
Well I'm on the Jan 5th build with the nk1 modem. No issues for me whatsoever. I'm not going to jump to the Jan 12th build any time soon since that was released once I flashed the Jan 5th build (just my luck). Perhaps a bad download? I always check the md5 for every download with rapidcrc.
[Verizon Samsung Galaxy S 4] grumpyj1:
mms

Mms is not working for me messages received are too blurry.

---------- Post added at 09:23 PM ---------- Previous post was at 09:16 PM ----------

I was having the same issue and getting the same message. I upgraded to the latest twrp using flashify and made sure it was jfltevzw recovery.

After that i flashed the rom and auto Loki worke. Only issue is mms when i receive the picture is really blurry.
[Verizon Samsung Galaxy S 4] xdatufoz:
Google Apps Device Policy Encryption

Hi,

Is it possible to have the encryption work on this rom: [ROM]【5.0.1】Google Play Edition 【JFLTE-GPE】 - 01-12-2015

I tried to encrypt using Google Apps Device Policy Encryption but it gets stuck at the spinning dots when booting. Anything I can do to have my device comply with Google Apps Device Policy Encryption?

Galaxy S4 Verizon with TWRP

Thanks,
[Verizon Samsung Galaxy S 4] CarvedArt:
FYSA... You might be able to encrypt it, but there are no custom recoveries that can read it yet.
[Verizon Samsung Galaxy S 4] xdatufoz:
If the custom recovery cannot read it, that means Android OS cannot boot?

I had a 4.4.X Eclipse Custom ROM before and Google Device Policy worked and allowed me to encrypt the phone. And of course I was able to use the ROM. Lollipop Custom ROMs in general does not allow encryption to work or is this specific to the Google Play Edition 5 Dandvh ROM?

Thanks!
[Verizon Samsung Galaxy S 4] CarvedArt:
Nope, simply means you can't use a custom recovery with an encrypted device.
[Verizon Samsung Galaxy S 4] xdatufoz:
But I had Eclipse 4.4.2 ROM + CWM and I was able to encrypt the phone and use my phone.
[Verizon Samsung Galaxy S 4] CarvedArt:
I'm not using Koush's recoveries on anything right now. I'll have to look into CWM handling encrypted devices.
[Verizon Samsung Galaxy S 4] flamadiddle:
I've been meaning to ask about this since I ran into the same issue. The TWRP changelog says 2.8.2.0 added support for lollipop encryption. I'm running 2.8.3.0, and it still couldn't mount my Android-encrypted partitions. What am I missing?
[Verizon Samsung Galaxy S 4] CarvedArt:
So it turns out I haven't been paying attention to this topic very well. Anyhow, I haven't tried it myself, but if you really want to give it a go... I have an idea:

1) Unroot

2) Encrypt

3) Root via OTG through recovery
[Verizon Samsung Galaxy S 4] Jrowe820:
Sm-n910p Lost - so many posts... Just looking for lollipop on sm-g900p?
[Verizon Samsung Galaxy S 4] davidanthony921:
software not authorized/yellow triangle

I had the same problem. I flashed twrp 2.8.4 with flashify without fixing the build.prop. Therefore i had the wrong variant of recovery. I flashed my backup. Then changed the build.prop back to jfltevzw and reflashed twrp with flashify. Then flashed the ota and all was well. I hope this helps anyone with the same problem.
[Verizon Samsung Galaxy S 4] gomangoman:
Flashify will download TWRP version for jgedlte with the default settings in build.prop. When i was on 1/12 I manually updated build.prop based on post 4422 and then flashify would download the proper version. But I am not sure if these build.prop changes will cause other problems.

The values I changed were:

ro.product.model

ro.product.device

ro.build.model

ro.product.name
[Verizon Samsung Galaxy S 4] Ermacaz:
Can I dirty flash newest update over the 1-12-15 release?
[Verizon Samsung Galaxy S 4] sauravdn:
audio stuttering fixed?
[Verizon Samsung Galaxy S 4] CarvedArt:
It's not recommended due to the network changes.
[Verizon Samsung Galaxy S 4] :
I had a quick question and couldn't find the specific answer on searching. I was on the 1224 build and attempted to update (clean flash) to the 1/28 build, but it gets stuck on the Samsung Custom screen on reboot. I flashed off the the verizon variant of TWRP and tried both 2.8.3.0 and 2.8.4.0 without success. I also manually flashed the Loki patch (lokipatch-danvdh-12242014). Any suggestions as to what I should do next or another thread that might have some guidance? Thanks for the help.
[Verizon Samsung Galaxy S 4] CarvedArt:
If you're sure your on a jfltevzw TWRP, check your md5. A re-download might be on order.
[Verizon Samsung Galaxy S 4] :
Thanks for the quick suggestion. Even after all these years, I still miss the silliest mistakes. The download was fine, but for whatever reason the md5 on the sdcard did not match.

As an aside, has anyone reported noticeable differences from the "hardware swap"?
[Verizon Samsung Galaxy S 4] mcsdoode:
Going from older version to new

Would flashing from an older version of this rom to the latest version without a full wipe cause issues? I'd like to avoid having to reconfigure/re-download all of my apps, but if will cause issues, I will of course bite the bullet (As this rom rocks!).

Thanks for any help/info you can provide :D
[Verizon Samsung Galaxy S 4] scrillakev:
Like going from Kitkat to Lollipop? Definitely a full wipe.
[Verizon Samsung Galaxy S 4] flamadiddle:
Even from the most recent previous build (01-23-2015), the dev has said you need to do a full wipe because of the new carrier changes. Also, reading through the thread before posting would have saved you some time as this question was answered not 5 posts before yours. Just a tip. ;)
[Verizon Samsung Galaxy S 4] mcsdoode:
Thanks for the advice, I'll be more vigilant with my searches. :good:
[Verizon Samsung Galaxy S 4] AndrewIsMyFav:
APN Settings

I am unable to change APN settings due to "access point name settings are not available for this user". Airplane mode trick did not work for me. I am unable to find any other work arounds?

http://xdaforums.com/showpost.php?p=58048162&postcount=4437
[Verizon Samsung Galaxy S 4] CarvedArt:
Try switching to anything other than LTE/CDMA/EvDo wait a sec then switch back.
[Verizon Samsung Galaxy S 4] ZanaX:
parse error - problem installing motocamera and motogallery help

I got it copied into the proper directories in system/priv-app and system/app but when I go to install the apk I get a parse error message: "There was a problem parsing the package"

Can someone help with a fix to this? Thank you,
[Verizon Samsung Galaxy S 4] CarvedArt:
What is it that you copied there?

To install something manually to a directory like you're describing you:

1) Copy the apk to the correct directory

2) Set the correct permissions (usually -rw-r-r- OR 644)

3) Reboot
[Verizon Samsung Galaxy S 4] ZanaX:
Thank you but can I have some more instructions on how to set the correct permissions? I have the apk copied to the correct directory already.
[Verizon Samsung Galaxy S 4] CarvedArt:
You didn't tell me what apk you have in which directory.
[Verizon Samsung Galaxy S 4] likehelly:
i have baseband I545VRUFNK1

can i install this? TWRPs website says that i can't put that recovery on, (even though modmanager does restart my phone into some sort of recovery (and i had chose twrp)) and this thing says i need TWRP to install it?
[Verizon Samsung Galaxy S 4] CarvedArt:
No, unfortunately you need I545...MDK. Look for Safestrap ROMs
[Verizon Samsung Galaxy S 4] na300zx:
Hey guys,

I have an old S4 (MDK) that I returned to stock MDK and then rooted and flashed TWRP all over again. I then installed this rom and absolutely love it. in fact, i can't believe I stayed on HyperDrive for so long!

However, I could not get MMS working with Google messenger, which the consensus seems to be that it will not work, so I even tried flashing some APN settings that I found with no luck. So, I switched to Textra messenger and all is well. My 4G speeds are rock solid along with everything else working great except for one simple thing. Can you recommend an app to force the home screen to rotate into landscape mode? Reason I ask, this will be a dedicated YaV1 (Radar detector) and Waze phone.
[Verizon Samsung Galaxy S 4] flamadiddle:
You could always just put the phone into landscape mode and turn off auto-rotate. If that doesn't work for you, Nova Launcher has options for orientation as well. https://play.google.com/store/apps/details?id=com.teslacoilsw.launcher
[Verizon Samsung Galaxy S 4] TheSt33v:
If anyone still wants to get Google Messenger working, there are two workarounds. The first is to clean flash the 1/23 build and dirty flash the latest build over it. The second is to go to settings-> cellular networks -> preferred network type and set to WCDMA only. After the APNs load, change that setting back to LTE/CDMA/EVDO. The setting switch fix must be repeated after every reboot.
[Verizon Samsung Galaxy S 4] TheSt33v:
I just found a bug. I'm on a Verizon S4. When I call my voicemail, it shows up as "voicemail" in the dailer. If I call it again, it shows up as "emergency number." Has anyone else experienced this?
[Verizon Samsung Galaxy S 4] TheSt33v:
I just found another issue. I'm not sure if it's a bug or something on my end, but whenever I plug in the phone when it is powered off, it boots. Any thoughts?
[Verizon Samsung Galaxy S 4] gomangoman:
Yes I have seen the same thing occasionally. Currently on the 2/10 build.
[Verizon Samsung Galaxy S 4] gomangoman:
Showed "emergency number" when I called voicemail today on 2/23 build. Not a problem just curious. Using stock kernel and "material dark" dialer if that helps isolate the issue.
[Verizon Samsung Galaxy S 4] TheSt33v:
I'm using the same kernel and dialer. It scared the hell out of me the first time it happened (thought I was dialing 911) but I'm used to it now. I'd prefer that it didn't happen though.
[Verizon Samsung Galaxy S 4] itsmejson:
Does anyone know if it is possible to get the s view function working?
[Verizon Samsung Galaxy S 4] efaden:
Anyone else have mms problems on Verizon? Tried hangout, messages, and textra. I get a lot of messages telling me I got an mms and that downloading failed and to click to download. Never works. Particularly group messages.
[Verizon Samsung Galaxy S 4] asl1:
Battery Drain

I'm having an issue with the latest build and battery drain., Using battery stats "tcpdump" is using between 10 and 20%. I've got googy's kernel and did a system/data wipe on install. Anyone else having issues with this?
[Verizon Samsung Galaxy S 4] thedoman:
Anyone know my custom ringtone won't stick with lollipop? All build I've tried so far it's the same. Set it and it reverts to default
[Verizon Samsung Galaxy S 4] flamadiddle:
I've had the same problem. If I set the ringtone or notification sound to something custom, on reboot, it'll revert back to default. As it is, I'm stuck on one of the built-in options for both. Makes me sad.
[Verizon Samsung Galaxy S 4] gomangoman:
I recall this problem reported earlier. I think the solution was to copy the sound files to the internal SD card folder.
[Verizon Samsung Galaxy S 4] RussTdesign:
Google Voice Doesn't work & Black screen on calls

Google Voice will not call out through the calling app or receive calls. When I make calls it also goes to a black sceen and I have to hit the home then power button to get back into the phone, click on the dialer, and select dialer then touch tone key pad to get back into the phone app so I can hang up or answer calls....

Upon closer examination, it looks like google voice is giving me the option to use it to make calls, but it blacks out quickly and makes the call through my phone provider.
[Verizon Samsung Galaxy S 4] RussTdesign:
SOLVED:

After a lot of research, it turns out this is a common problem in Lollipop if your phones proximity sensor is not working properly and always reading close. As of now if your proximity sensor is not working it is not a good idea to upgrade to a Lollipop based ROM. Some say they have found workarounds, but none of them worked for me. Maybe developers should give the option of using kitkats dialers?. Here is a link to a thread discussing the same exact issue on the Nexus5 https://productforums.google.com/forum/#!topic/nexus/9HZHQJMrxF8%5B151-175%5D
[Verizon Samsung Galaxy S 4] marioluigi64:
Android Auto interaction

So I have had the Pioneer AVH-4100NEX receiver for about a week and wanted to share some observations about how my phone interacts with Android Auto.

ROM: 20150315

Modem: NK1

Kernel: GoogyMax3

Dialer: Material Dark

1) When I try to make a call from Android Auto, the call is not actually made. Instead, after the voice command is given, the dialer app appears on my phone with the number of the contact I wanted to call having been entered. I have to press the "call" button from my phone to actually initiate the call. I can replicate this when my phone is not in Android Auto mode using "OK Google" voice commands, so the problem is not isolated to Android Auto.

2) After disconnecting my phone from the headunit, when I adjust the ringer volume, the volume control popup says "Muted by Android Auto". The ringer volume still adjusts like it should, this is just a visual hiccup.

3) When my phone is in Android Auto mode, I am still able to fully control the lockscreen. By that I mean from my phone I can still launch the dialer and make a call, launch the camera and take pictures, and launch any app that has a notification displaying on the lockscreen. Only if I bring up the launcher will the phone screen "lock" and display the Android Auto logo. I can repeat this once I turn the screen off and back on. Not sure if this is actually a bug or not, I guess I figured Google would lock the entire phone down when in Android Auto mode and not let you interact with it until disconnecting it.

Overall though, I'm loving this ROM. Danvdh, et al. Thanks for all your hard work!
[Verizon Samsung Galaxy S 4] TheSt33v:
Has anyone used Miracast with this ROM? I bought a cheap dongle that I can't connect to using this rom (I tried stock and Googymax kernels), but I know it works because when I install a stock TW ROM, it works. I also tried cyanogenmod 12 (which I might keep because it's pretty awesome), and that also works, so it's not a TW vs. AOSP related issue. Does anyone have any ideas?
[Verizon Samsung Galaxy S 4] KennyWongX:
I'm not sure if I'm in the right forum but is it possible to go from NK1 4.4.4 back to NC5 ??
[Verizon Samsung Galaxy S 4] TheSt33v:
One of the few recurring issues with this otherwise perfect rom (cheers, Dan!) is Google Messenger not playing well with MMS. After a brief stint with CM12 (broken Bluetooth is a deal breaker for me), I found a solution.

1. Go to Cellular Network Settings

2. Change the preferred network type to WCDMA only, wait about 10 seconds, then change it back to either LTE/CDMA/EvDo/GSM/WCDMA (if you want global support) or LTE/CDMA/EvDo (if you're staying in the states).

3. Go to Access Point Names

Now the above has been posted before, and I've tried the previously suggested solutions without success, but this is what did it for me:

4. Edit the Verizon Internet APN

5. Change MMSC to http://mms.vtext.com/servlets/mms

6. Set MMS port to 80

7. Change APN type to default,supl,mms

8. Back out using the back button to save changes (DON'T tap the settings dots on the upper right corner of the screen and tap Save. This sometimes will cause the APN to disappear.)

9. Make sure this APN is selected.

This worked for me and will survive a reboot.

P.S.: If someone wants to be really cool and figure out how to get Miracast working on this rom, that would be awesome.

---------- Post added at 09:31 AM ---------- Previous post was at 09:30 AM ----------

Yes, you are in the wrong forum. This is a forum dedicated to Q and A about a specific rom that you cannot use with either of those builds. But to answer your question, I'm pretty sure I read somewhere that that's fine. You just have to Odin back to it. You might want to check elsewhere though. Safestrap forums usually address questions like that.
[Verizon Samsung Galaxy S 4] Otakulad:
Issue with Netflix on Mobile Data

Hello,

Due to my post count, I was bounced here. I hope to get to the 10 post soon but it is hard since I don't have a lot of questions.

I have been running JFLTE-GPE 5.0.1 (multiple releases) for a while now and at one point I lost the ability to watch Netflix on mobile data. I went back to 4.4.2 Hyperdrive and Netflix started working again. Has this happened to anyone else? Thanks in advance.
[Verizon Samsung Galaxy S 4] gomangoman:
I can watch Netflix on mobile data on the latest GPE. I never do but just checked and it worked.
[Verizon Samsung Galaxy S 4] gomangoman:
Actually I should probably retract this claim. I tried again and it failed. If I start a show on Wi-Fi then disable Wi-Fi, I can continue watching on mobile data. But it seems I am unable to start a new show while on mobile data.
[Verizon Samsung Galaxy S 4] phonedawg:
I tried the below combination but android auto does not work - Does it still work for you?

I heard that the new google play services versions blacklist the GS4
[Verizon Samsung Galaxy S 4] marioluigi64:
Yep, still works for me, just used it yesterday. Here's what I'm currently running:

ROM: JFLTE-GPE 20150419

Kernel: 3.4.106-Hulk-Kernel_GE5_V1.1

Google Play Services: 7.3.29

Android Auto app: 1.1.069961

Pioneer NEX firmware: 1.03
[Verizon Samsung Galaxy S 4] phonedawg:
Just tried the above combination. Does not work
[Verizon Samsung Galaxy S 4] marioluigi64:
Hmm, has Android Auto worked for you in the past? If not, to setup the Pioneer headunit for Android Auto is somewhat convoluted (unnecessarily so, really). First, the USB cable has to be connected to the headunit's USB2 port, USB1 is reserved for the iPhone. Next, you need to go into the Smartphone Settings in the headunit and set it to Android mode, then select Android Auto connectivity. That should work for you...hopefully!
[Verizon Samsung Galaxy S 4] phonedawg:
yeah, I use usb2. I get a red screen saying this device is not supported with android auto. I think you are the only person who managed to get android auto working with a GS4. All the other posts on the internet say they are stuck where I am stuck
[Verizon Samsung Galaxy S 4] marioluigi64:
That's so strange because it has worked for me since the day the Android Auto app was released. I am grasping at straws at this point, but what is the listed Model Number of your phone in Settings -> About Phone? I've noticed over time as I flash from ROM to ROM that the model number can change. At one point it was "SCH-I545" (Verizon's GS4), now it is "GT-I9505G" (unlocked GPe). Perhaps Google has the SCH-I545 blacklisted, but not the GT-I9505G?
[Verizon Samsung Galaxy S 4] phonedawg:
The settings showed GT-I9505G when I was on this ROM but android auto gave the same error message saying this device was not supported
[Verizon Samsung Galaxy S 4] marioluigi64:
Well crap...sorry, but I don't really know what else to tell you at this point. I haven't done anything special to get Android Auto compatibility. To steal a phrase from Apple, it "just worked".

I doubt this will help, but I do have one more thing you may try. I last did a clean rom install when 5.0.1 was released, I believe that was the 20150303 release. The past couple of updates have been dirty-flashed. Perhaps you could try flashing back to that rom???
[Verizon Samsung Galaxy S 4] Rizon216:
Got the ROM installed and love it so far but had a quick question. I'm on the 5.0.1 build from 4/19.

I have a network extender and it displays "Empty" on the settings drop-down. This I am okay with, but it also shows me as "Roaming" and I have to turn on Data Roaming in order to use the Network Extender 3G data (which I'd rather leave off as I don't want to *actually* use data roaming). Is there a way to have it not think I am roaming? I've tried MK2 modems and also tried adding "ro.telephony.get_imsi_from_sim=true" that someone had suggested in the main ROM thread.
[Verizon Samsung Galaxy S 4] yilun:
How do I install the add ons I have downloaded from the ota updater? It has no option to install, and it doesnt install automaticly. Do I have to flash it manualy on twrp? Also after each update it all desapears and I have to flash again, its really annoying, plz help me??

(Im on 5.0.1)
[Verizon Samsung Galaxy S 4] croldan72:
I agree. From one update to the next things seem to change and it would be nice to be able to flash the items we want after each update.

For me it looks like the latest update removed Hulk Kernel and Installed Alucard's kernel. Now all of the tweaks I had in Hulk kernel are gone and I don't have a way to tweak Alucard kernel.
[Verizon Samsung Galaxy S 4] flamadiddle:
I just move the ROM and addon files to the SD card after download. By default, they're in:

/storage/emulated/0/OTAUpdates/

I move them to:

/storage/extSdCard/

Then in TWRP, I wipe everything on internal memory, and set all of them to install in succession (the ROM update first of course). Works beautifully.
[Verizon Samsung Galaxy S 4] Soniku:
GPS not fixing to as many satellites as it should be?

Hey Guys,

My phone is only locking on to about half the GPS satellites that are visible (approximately 10/19) and I'm running the latest version of this ROM.

My dad's phone is running rooted Jelly Bean stock and is locking on to more like 19/22 satellites.

This happens even when I have the phones directly next to each other.

Mine SEEMS to be functioning fine, although I've noticed a couple instances of warping around on the map.

I re-flashed, wiped everything, and used that script that removes any remaining old kernel data, but that didn't help at all.

I could try flashing back to stock to see if that changes anything, but I really don't want to.

Is this normal?

Thanks!

- Soniku
[Verizon Samsung Galaxy S 4] alaricljs:
The 5.0.1 thread punted me here... any chance there's a mirror? I'm getting this: Error establishing a database connection at the DL link.
[8525, TyTN, MDA Vario II, JasJam General] nzone:
Can I reset the total talking counter (total call in and call out time) for HTC Hermes :confused:
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
Well if you fancy a challenge see the POF solution:

http://xdaforums.com/showthread.php?t=280543&highlight=call+counter

Now I used an application to reset mine the other day - but I'll need to hunt around to find which application it was!! So if you don't fancy the above and I find what I'm looking for I'll post later.

Mike
[8525, TyTN, MDA Vario II, JasJam General] nzone:
I've tried POF solution but got error, error details in my other thread http://xdaforums.com/showthread.php?t=290464
[8525, TyTN, MDA Vario II, JasJam General] nzone:
Problem fixed, thanks mikechannon :)
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
Good news, pleased it worked.:)

Mike
[8525, TyTN, MDA Vario II, JasJam General] JuniorPhatFarm:
Did you find it Mike?