yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] marioluigi64:
Hi everyone, hoping you all can help me with a problem I'm having with my phone. First, some specs:

ROM: Danvdh GPE 9/30

I am one of those lucky MDK users, I got the phone in May 2013 and rooted early :)

I had been running the NC5 modem for a while now with no issue. The problem started after I flashed the NG6 modem (from Surge1223's thread) in TWRP. Just fyi, here are the steps I took to flash the modem. Within TWRP, I flashed the zip file, cleared Dalvik/cache, then rebooted.

Almost immediately I started getting random reboots. It rebooted twice, then seemed to settle down, so I decided to wait a day or so to see what my phone would do. Sadly enough, it started rebooting again, so I gave up last night and reflashed the NC5 modem in TWRP using the same method as before. The phone was fine after that, until this afternoon. About an hour ago, my phone froze, and rebooted, but the screen cut off at the Samsung custom padlock boot screen. It seems to be off at this point, but I can't power on the phone without pulling the battery. After pulling and replacing the battery, the phone powers on by itself, but again cuts off at the Samsung boot screen, about 3-4 seconds into the boot process. I've tried booting into TWRP and download mode, with the screen turning off and the device seemingly freezing after 3-4 seconds. I'm at a loss as to what to do at this point.

I'm at work right now, but when I get home, I will see if Odin3 can make some sort of contact with the phone. Any help in the meantime would be greatly appreciated!
[Verizon Samsung Galaxy S 4] Alxoom33:
Sounds like you may have a bad dl. Re download. Turn phone off. Then boot into TWRP and reflash the modem zip. Not the non-halos.zip.
[Verizon Samsung Galaxy S 4] marioluigi64:
I would love to, but I can't. :(

I put a video up on Youtube showing what the phone is doing right now. I don't have 10 posts yet, so I can't post links, but if you go to youtube.com then add "/watch?v=3ey5xD9LodY" at the end of the URL, you can see what the phone is doing.

It is the only thing the phone will do. I've tried doing a hard reset by holding the power button, but nothing happens. All I can do is pull the battery and start this process again. If I hold the correct button combos, I can begin to boot into TWRP or download mode, but the phone cuts off/freezes like clockwork after 3 seconds.

I tried to get Odin3 to recognize the phone, but my desktop doesn't recognize that anything is plugged in when I connect my phone to it, so Odin3 by extension doesn't see anything.
[Verizon Samsung Galaxy S 4] Alxoom33:
Did you install the Samsung apps on your computer? You need them for the computer to recognize your phone.

To hard boot into recovery you need to hold power button and volume up at the same time, then let go of power button once blue writing appears on upper corner of phone.
[Verizon Samsung Galaxy S 4] marioluigi64:
I'm sure I have. I've been able to send adb commands to the phone in the past. Now however, my PC doesn't even see that a device has been connected to it (nothing shows up in the device manager, not even an unrecognized device).

The phone will no longer charge when I plug it into an AC adapter either (or at least the LED no longer lights up indicating it's charging).

I have tried booting into recovery several times. Each time, it will begin to boot into TWRP, the blue text, "RECOVERY BOOTING...", will display, then immediately afterwards, the screen will cut off and the phone will freeze, just like in the Youtube video I posted.

I'm afraid the thing is bricked...
[Verizon Samsung Galaxy S 4] marioluigi64:
So, I was talking to a friend about what's been going on with my phone. During the conversation, I started goofing around and smacking the back of the phone like 4-year-old me would an NES to try and make it work (ah, good times...). Believe it or not (and I did not touch the power button while doing this), the phone powered up and successfully booted!!!

It showed only 2% battery life, so I connected it to the AC adapter, but then a few seconds later the phone died again.

This occurrence leads me to believe there is something wrong with the battery, and leads me to another question. Can the S4 (or any other smartphone) run solely on USB power?

My roommate has a Galaxy SIII, I read the SIII battery can be used in the S4, so I will test the phone out with his battery when he gets back tomorrow, and update you then.
[Verizon Samsung Galaxy S 4] CarvedArt:
Have you tried a different USB cable/transformer? It sounds like you might just have a charging issue. Not enough juice to get it started.

Allowing a battery to cool down will give it more usable power, which as it heats back up will deplete again. This sounds like your situation... Power off for a few, restart it has enough to begin booting, then depleted again.

The phone cannot run on USB alone it needs the battery to sustain it's operation.
[Verizon Samsung Galaxy S 4] marioluigi64:
I have tried 3 USB cables, 2 AC adapters, and 2 PCs.

When this started on Friday, my phone was hooked up to my PC at work and showing about 50% battery, but it's possible something went wrong with the battery and it's stopped delivering any significant amount of power or accepting a charge.
[Verizon Samsung Galaxy S 4] marioluigi64:
So it turns out it wasn't the rom or new modem that was the problem, my battery has decided to kick the bucket. I tried my roommate's battery in my phone and it booted right up as if nothing was ever wrong! Strange that an OEM battery would just die like that, but I suppose that does happen from time to time. Thanks for the help!
[Verizon Samsung Galaxy S 4] TheSt33v:
I use it, and I've never had any issues with it. I would recommend reinstalling, but you've probably tried that already. Are you using the latest version of the app?
[Verizon Samsung Galaxy S 4] matycakes:
Yeah, I have tried reinstalling it, and I am using the latest version of the app. The fact that you haven't had any issues is encouraging. I'll continue to troubleshoot and see what I can find.
[Verizon Samsung Galaxy S 4] jake.levinez:
I keep getting this (in CWM touch)

Flashing Google Play Edition

Android 4.4.4

Enjoy!

format() expects 5 args, got 4

E: Error in /storage/sdcard1/danvdh-GE-4.4.4-09-30-2014-VZW.zip

(status 7)

installation aborted

Is it just a bad DL?

EDIT: Tried a new DL, same issue. I want to get this fixed asap
[Verizon Samsung Galaxy S 4] brd912:
Is cm11 theme manager included in this rom?
[Verizon Samsung Galaxy S 4] cambunch:
It is not.
[Verizon Samsung Galaxy S 4] swieder711:
Can the CM11 dialer be used with this ROM? I recall the CM11 doing a nice job of automatically switching from BT to my wired headset when it's plugged in

With the GPE dialer I have to manually select the wired headset for every call.
[Verizon Samsung Galaxy S 4] CarvedArt:
Try this: http://xdaforums.com/showthread.php?t=2522762

You could install the latest TWRP or maybe even just updating CWM, but definitely by following the steps in the post above.
[Verizon Samsung Galaxy S 4] JCTechie:
Flashed Dan's 5.0 GPE from ATT forum post

So I was able to flash 5.0 on my VZW S4, I am using Philz Touch recovery v6 . I am on MDK baseband and was running Dan's GPE v4.4.4 prior. I followed instructions wiped all data/factory reset and flashed Danvdh-GPE-5-12172014 from the ATT forum followed by the ktoonz patch of dan kernel.zip as mentioned by macravin in the prior post. Rebooted and rom boots up, strange thing is I can't make phone calls or text but data is working which is strange. I tried to go in to manually specify the APN and it can't seem to connect to Verizons network for phone calls and texts, any thoughts?

Thanks again Dan and Kryten for all your amazing work!

---------- Post added at 10:48 PM ---------- Previous post was at 10:38 PM ----------

I have no problem with the phone recognizing charging, the LED lights up and the phone shows that is plugged in and charging. Also regarding the APN not being included, is this something that can be flashed separately?

Thanks!
[Verizon Samsung Galaxy S 4] swieder711:
Anyone try the latest NK1 modem?
[Verizon Samsung Galaxy S 4] sauravdn:
My sim card is not being detected.
[Verizon Samsung Galaxy S 4] ajgonzales:
Is your phone still working with the new battery? I am having the same issue shown in your video, but I am not sure whether my issue is with the power button or the battery. I'm hesitant to take it into the store because I'm still on MDK.
[Verizon Samsung Galaxy S 4] sauravdn:
Step by step instructions please.

I am currently running CM 11 M12 Snapshot with I545OYUAMDK baseband. I tried flashing the rom but had an issue where it wasnt detecting my sim so i had to restore my Modem and radio and go back to cm 11. So how do i properly flash this rom with CWM v6.0.5.1 recovery on I545OYUAMDK baseband.
[Verizon Samsung Galaxy S 4] marioluigi64:
Nope. I bought an Anker battery for it, and my phone ran for about a month and an half before the same thing started happening again. I tried my roommate's Galaxy S3 battery again and no luck this time, my phone just powers up for a couple seconds then dies. As this was my daily driver phone, I've become fed up with it and it is now in storage. I'm using an HTC One Max until my contract runs out in May.

I guess I could drag the phone back out and start tinkering with it. The problem definitely seems hardware-related. My first guess is that either the USB charging board has died or something has gone wrong at the battery terminal. The easy fix would be the charging board, but that brings up a question. Would a faulty charging board cause the phone to suddenly lose power like that? I would imagine the phone could still run until the battery dies (and the battery was full when this problem started), but I could be way off base...

P.S. Mods, yes, I originally thought my phone's issue was ROM-related, but that turned out not to be the case, and this is now going way off base from a ROM Q&A. Feel free to move this discussion if you want. :)
[Verizon Samsung Galaxy S 4] elprofet:
GPE 5.0 screen turns on when charging

So far I'm really enjoying lollipop. I just have one nagging issue.

I use a qi charging pad at night. Whenever my device is fully charged it automatically stops charging. After a little while it drains enough that it starts charging again. This is normal behavior for qi charging.

The problem is that every time the device starts charging, the screen turns on, illuminating the entire room. At night, this drives my wife crazy.

Is there any way to disable that?
[Verizon Samsung Galaxy S 4] Kenpachi 91:
I've been using nk1 for the past few days actually. I came from mdk and the difference is quite noticeable.

Sent from my Verizon Galaxy S4 (running Danvdh's 5.0 GPE ROM)
[Verizon Samsung Galaxy S 4] clarinetboy:
GPE lollipop won't boot up

HI, so I was running the 4.4.4 GPE rom, and tonight I upgraded to the lollipop version, except now the phone won't boot. I followed the instructions, installed the rom, then loki doki'd, but now the phone boots to a screen that says "samsung [lock] custom"

I've tried reinstalling 4.4.4, installing 5.0 again, and messing with the radios, but it won't boot to rom, only back to recovery. Any help would be much appreciated!

Thanks!
[Verizon Samsung Galaxy S 4] elprofet:
Bluetooth Skipping

Anyone else getting bluetooth "skipping" every 30 seconds or so with this ROM?

I'm getting some bluetooth interruptions or skipping every 30-45 seconds in my car while playing music.
[Verizon Samsung Galaxy S 4] rcorchado:
NC5 baseband and build number w/ safestrap

I'm currently running Eclipse 4.4 TW on my Verizon Galaxy S4 with baseband and build number NC5. I also have safestrap installed. Is this ROM compatible with the aforementioned criteria?
[Verizon Samsung Galaxy S 4] elprofet:
This is not a safestrap compativle rom. You need an unlocked bootloader.
[Verizon Samsung Galaxy S 4] Kenpachi 91:
Is it me or does anyone else think that vibration is a bit weak?

Sent from my Verizon Galaxy S4 (running Danvdh's 5.0 GPE ROM)
[Verizon Samsung Galaxy S 4] scrillakev:
Running the latest TWRP by any chance?
[Verizon Samsung Galaxy S 4] CarvedArt:
Loki Doki is auto patching now. So it sounds like you may have added some steps. Couple other things to consider:

This is not a Safestrap ROM (MDK only)

Your Recovery needs to be lollipop ready

Check your MD5

Did you try entering Download Mode then continuing to boot into the ROM?

If you're MDK and MD5 is good I'd guess you undid the Loki with the extra flash.
[Verizon Samsung Galaxy S 4] sauravdn:
[ROM]【5.0】Google Play Edition 【JFLTE-GPE】 - 01-01-2015

New update feels sluggish for some reason. Is it just me? Is it because i used CWM v6.0.5.1 recovery instead?
[Verizon Samsung Galaxy S 4] clarinetboy:
I updated my TWRP to 2.7ish and the ROM worked. Thanks!
[Verizon Samsung Galaxy S 4] davidanthony921:
AWESOME

fairly new to modding and have only tried a few different customs but this is by far the best. so clean so smooth and fast. great work man. only one question. i know its vanilla android but do you think youll be adding split window mod to this?

btw donation coming.. just gottta get that first paycheck after the holiday. lol.
[Verizon Samsung Galaxy S 4] flamadiddle:
Really love this ROM! Thanks so much.

Any chance we could get Reboot options back on the power menu? I really liked being able to reboot directly to recovery. Even just a regular reboot button (no options) would be nice.
[Verizon Samsung Galaxy S 4] CarvedArt:
That would be ideal... in the meantime, you might try "Reboot Menu" from the Play Store.
[Verizon Samsung Galaxy S 4] flamadiddle:
Thanks for the tip. That widget works pretty well.
[Verizon Samsung Galaxy S 4] vladness:
Severe Lag Placing/Receiving Phonecalls

Happy New Year everyone!

Thanks Dan for the hard work you've put into this release!

I've been trying to get the Verizon 5.0 up and running since the Christmas eve release...

My daily driver is CM 11, KitKat 4.4.4. I have absolutely no issues making or receiving phone calls on this ROM.

Yet, the same issue I had with the first release of 5 continues to even the 1/5 release of 5.0.1 which finally has led me here asking for help in solving my frustration. What happens is that there is significant delay and lock up during phone calls. If I try to place a call, the dialer opens, but upon entering a number, absolutely nothing happens for at least 10 seconds until the trying to call screen appears. It tries to make the call but nothing goes through and my phone completely locks up when trying to end a call. There is also an issue with incoming calls. The phone doesn't ring when I try to call it and goes to voicemail after a bunch of rings. Only after it gets to voicemail does the prompt appear on my phone that a call is coming through which locks up the phone completely if i try to answer.

At wit's end trying to figure out WTF could possibly be wrong with this damn dialer software!! Today I even took apart my phone and cleaned off the proximity sensor as has been suggested to no avail. I have tried to use third party dialer software but they didn't do anything more then act as a skin to the problem dialer. Trying to understand why on a fresh install where everything else runs like silk, this is getting caught up.

Please let me know if I can provide any other information or clarification on this issue.

Thanks all in advance!
[Verizon Samsung Galaxy S 4] CarvedArt:
Have you updated your modern?
[Verizon Samsung Galaxy S 4] vladness:
Yes I have, I've tried from MDK to the new one NK1, both Retail and non-HLOS without any effect. I have LTE data working perfectly for any of the modems I try to flash.

NK1 is what is currently flashed but I can certainly try other ones if that is recommended. Would dev edition of the modem help in any way?

Thanks!!!
[Verizon Samsung Galaxy S 4] CarvedArt:
Have you tried a Dev modern? Is this the behavior immediately following a ROM flash? Have you tried booting into safe mode and trying a call? Do you have a logcat?
[Verizon Samsung Galaxy S 4] TheSt33v:
Older Versions

Does anyone have a link to older (4.4.4 safestrap compatible) versions of this rom? I dropped and broke my beloved MDK phone, and I imagine that the replacement coming in the mail will be locked up. I need something to hold me over until May when I will be buying a Nexus 6, provided Verizon didn't convince Google to let them lock that up too.
[Verizon Samsung Galaxy S 4] vladness:
I just tried flashing dev modem I545OYUFNC5 with same results. I have historically used CM on this phone, ranging from 10.1 to 11. I have never had an issue with any dialer under CM. This is the first time i'm ever seeing such behavior in the life of the phone.

Booting into safe mode did not help. Same issue... freezing and lag while trying to make the call. I don't have logcat but the android logger that the 5.0.1 rom comes with is enabled. Would it be helpful for me to get logcat and post output here?
[Verizon Samsung Galaxy S 4] CarvedArt:
I could take a look at a logcat if you could get one to see if there's a clue.
[Verizon Samsung Galaxy S 4] vladness:
Much appreciated! Please see attached, hopefully I did it right. I included log of what happens during receipt of call and trying to call.
[Verizon Samsung Galaxy S 4] krypto1300:
This is so strange. I have two MDK's and haven't had any problems besides Google Play Movies not streaming on any build so far.

The one thing that I always do is wipe/factory reset then wipe internal storage prior to flash. Could this possibly be why I haven't had any problems? Have you tried wiping internal storage?

I've also used TWRP 2.7.0.1 and 2.8.3.0 without problems.
[Verizon Samsung Galaxy S 4] vladness:
Hi Kripto1300,

Thanks for looking into this as well. Here is something stranger... For ****s and giggles I installed lollerpop which is based off cm12. Phone works without issue on this build. Same performance as on cm11. The reason I wanted gpe was for stability and native drivers. I want to move away from the nightly model and to something more grounded. It doesn't make sense why its not working even on a brand new install. Is there any way to see why its working here and not there? Would a trace log from this ROM be of any use? I also want to see if installing a completely barebones version using the installer could lead to some answers.

---------- Post added at 01:18 AM ---------- Previous post was at 01:11 AM ----------

One more thing... You mentioned wiping internal memory.

I use latest twrp and always wipe everything besides SD card and internal data. The actual data folder does get wiped. Is there anything in my storage location that might for whatever reason conflict with the dialer even though the files are not in the actual system or root data folder. Does that make sense?
[Verizon Samsung Galaxy S 4] JCBiznatch:
Download link isn't working! Let me know when it's fixed would love to download it. Tried on multiple browsers!
[Verizon Samsung Galaxy S 4] krypto1300:
Hi,

Not sure if there is anything in internal SD that could affect this, but I've always wiped it anyway.
[Verizon Samsung Galaxy S 4] CarvedArt:
Looks like whatever recovery you're using isn't taking care of cleaning all of the CM stuff. I'd try to Odin back to a stock TW then flash this ROM.
[Verizon Samsung Galaxy S 4] vladness:
I am using TWRP 2.8.3.0 as recovery. I do the following when I install the ROM:

Wipe

Advanced Wipe

Check Off Dalvik, System, Data, and Cache

Install ROM

What could possibly be interfering with those directories wiped? Is there a super cleanup mode that I am not familiar with?

Also, Sorry for the lazy request, but I haven't used Odin since the first few weeks of the S4 coming out... Can I get a nudge in the right direction, or a link or two?:confused:

Thanks so much for the info and time thus far!
[Verizon Samsung Galaxy S 4] mcsdoode:
Question about installation from a 4.3 based rom

First and foremost, I'd like to apologize for asking such a noob-level question...

I haven't flashed a new ROM in a while and am currently running a Hyperdrive 4.3-based ROM. Is there anything I should update, recovery-wise and whatnot, before I attempt to flash this? I'm currently running a variant of TWRP.

Thank you in advance for any answer you can provide!
[Verizon Samsung Galaxy S 4] CarvedArt:
Are you on MDK? If so then just update TWRP to the latest. It needs to be a jfltevzw variant to auto patch Loki Doki.

---------- Post added at 01:21 PM ---------- Previous post was at 12:54 PM ----------

Looks like you're process is good but something's not getting wiped.

Get the MDK from here: http://xdaforums.com/showthread.php?t=2289325

★ Get into Download mode (Volume Down + Home Buttons)

★ Launch Odin

★ Only check "Auto Reboot" and "F. Reset Time"

[DO NOT "Re-Partition" DO NOT]

[DO NOT "Nand Erase All" DO NOT]

★ Open MDK in PDA (or AP in newer Odin)

★ Start
[Verizon Samsung Galaxy S 4] flamadiddle:
Download working for me. If you still can't get it, try the torrent. I'm still seeding along with 46 others.
[Verizon Samsung Galaxy S 4] vladness:
So I gave in and did a full wipe of even my internal data directory without avail... Going to try restoring the stock MDK...
[Verizon Samsung Galaxy S 4] davidanthony921:
gear 2 neo?

Can any of the wearable samsung products be connected to my gs4 while running this rom? Or could anyone suggest a smartwatch that will. Or some type of apk or file too install samsung apps? Any help would be appreciated. I might just have to wait for alcatel watch
[Verizon Samsung Galaxy S 4] vladness:
Well that worked... way more painful then I would have liked, but it's all good now... Didn't realize that restoring to stock meant going through the rooting process all over again which was quite the pain...

But yeah, I flashed in stock which made calls perfectly. Then flashed in 5.0.1 GPE which works exactly the way it should now! Wish there was a way to pinpoint what exactly the issue was as to perhaps bring it up to devs? It had to have been something either in the actual phone root that wasn't getting over-written or one of the folders that twrp doesn't give you access for wiping.

Since I don't have 10 posts yet, would anyone be interested in referencing this discussion in the actual thread for this ROM? In case someone wanted to look further into the logs I posted.

Thanks for the troubleshooting tips on this!!

PS. Yay for Lollipop!!
[Verizon Samsung Galaxy S 4] krypto1300:
This is so strange. I have 2 MDK's and have only flashed TouchWiz or Dan's ROMs on these devices. Maybe its CM that's leaving traces. I've been using TWRP exclusively for at least the last 2 years as well.
[Verizon Samsung Galaxy S 4] mcsdoode:
Thanks for the help! Flashed and running like a best.
[Verizon Samsung Galaxy S 4] grumpyj1:
mms

Is anyone having issues with mms being Compressed to less than 30kb?

I've installed all the builds, 12/24 to 1/5/15 and i have the same issue on all of them.

Am i missing something or doing something wrong?

I am running latest modem and latest twrp any help would be appreciated. Thank you!
[Verizon Samsung Galaxy S 4] AndrewIsMyFav:
Authenticator on gpe 5.0.1

I am using [ROM]【5.0.1】Google Play Edition 【JFLTE-GPE】 - 01-05-2015 on my phone.

Problem is unfortunately authenticator has stopped. After pressing begin setup.

I installed this rom after restoring from my first backup after installing TWRP/supersu

I resolved my issue by restoring the data only from authenticator from my backup prior to installing this rom.
[Verizon Samsung Galaxy S 4] CarvedArt:
This what you're looking for? http://content.samsung.com/mobile/us/contents/aboutn/appsMobileIntro.do

Or this? https://play.google.com/store/apps/details?id=com.google.android.wearable.app&hl=en
[Verizon Samsung Galaxy S 4] sauravdn:
auto loki doesn't work for me.
[Verizon Samsung Galaxy S 4] CarvedArt:
You must use a jfltevzw recovery for it to work
[Verizon Samsung Galaxy S 4] Kenpachi 91:
Does anyone know a good way to determine how long the phone has been on off a charge? I'm basing it off cell standby since that's what has the most time