yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] heath2805:
Latest build is running great! I have the note 3 but I really miss how my S4 has recovery and so many more options. Plus I paid 800 bucks when it was released so its kinda hard to ignore lol
[Verizon Samsung Galaxy S 4] NikolaeVarius:
Anyone else have this issue where when recieving a phone call, the screen takes FOREVER to show up? Like literally takes 10+ seconds for the screen to come on. I have to try and frantically press buttons to wake the screen but that just seems to make it worse.
[Verizon Samsung Galaxy S 4] swieder711:
I did a clean install to the 6/21/2015 release, coming from the 3/15/2015 release. The new release seems to lag, especially when responding to screen touches.

Are there any performance tweaks that I can try to improve the response times that I am experiencing?

I am using the default kernel that comes with the ROM file. Might another kernel work better?

EDIT: MY Quadrant score is 10.4K which looks pretty good.

thanks,

Scott
[Verizon Samsung Galaxy S 4] cognitivedissonance:
The dialer in general seems to take a really long time to start a call, answer a call, etc. That and the Google search app takes a while to open and get going. I'm on 3/15 build so hopefully the newest build and the different kernel will help...
[Verizon Samsung Galaxy S 4] bswides412:
I use to run into this issue as well. I tried an app called "S4 sensors [Requires Root!]" from the Play Store. It was recommended by another poster I think in this thread and somehow it fixed the lag of the screen while on a call.
[Verizon Samsung Galaxy S 4] gts24:
Hello,

I am attempting to install this ROM on my MDK Verizon S4.

I always wipe dalvik/cache prior to installing any ROM.

I first tried the 3/15 release: ( http://ultimarom.com/jflte-gpe-03-03-2015/ ). Wiped dalvik/cache before trying ALL 3 kernels. The phone completes installation does a reboot and all looks well, then suddenly it reboots again and goes back to TWRP.

I then tried the 6/21 release ( https://romhut.com/roms/danvdh-googleedition ) . With the exact same results as above.

Thankfully I had a nandroid and was able to restore to my HD ROM installation.

any thoughts here?
[Verizon Samsung Galaxy S 4] swieder711:
Did you wipe internal memory too? Recommended when switching ROMs.
[Verizon Samsung Galaxy S 4] flamadiddle:
Actually, recommended always, as noted in the OP Installation Instructions.
[Verizon Samsung Galaxy S 4] zeb carter:
Problem downloading JFLTE-GPE-20150702

Whenever I try and download today's update and check the MD5, it fails. Anyone else having a problem?
[Verizon Samsung Galaxy S 4] flamadiddle:
Same here. Looks like a bad file or bad checksum.
[Verizon Samsung Galaxy S 4] gpz1100:
Download checks out just fine for the 7/2/2015 update. MD5 matches and no errors when doing a zip test. Use a different browser to dl.
[Verizon Samsung Galaxy S 4] jackdubl:
Update your twrp to 2.8.4.
[Verizon Samsung Galaxy S 4] zeb carter:
Used the OTA app - still fails the MD5 check..
[Verizon Samsung Galaxy S 4] flamadiddle:
We're using the OTA Updates app to download and check. I'll try downloading from my laptop.

---------- Post added at 11:11 PM ---------- Previous post was at 11:02 PM ----------

Confirmed: Downloading from here on my laptop gave me a file matching the MD5sum. Something must be wrong with the OTA Updates app.

Coincidentally, I just bought the Pro/Donate version of OTA Updates. :p
[Verizon Samsung Galaxy S 4] Aminoacow:
Downloading 20150702 update using OTA updates fails all the time. I can't find the downloaded file in any folder within my internal/external storage, including /emulated/0/OTAUpdates folder which is specified as storage location in OTA updates setting. Downloading the file using my browser now.
[Verizon Samsung Galaxy S 4] swieder711:
Downloaded the 7/2 release directly to my phone. It was stored in the Downloads folder. Checked the MD5. Installed over the top of the 6/21 release.

Running fine.
[Verizon Samsung Galaxy S 4] ktraub:
OTA app fails download

I had exactly the same issue with the OTA app. Attempted D/L multiple times and watched it D/L, but couldn't find the downloaded file anywhere. Had to download manually from Romhut with Chrome browser. This happened with a previous version of the OTA app, but they fixed it. I guess it's broken again.
[Verizon Samsung Galaxy S 4] jackdubl:
FYI, I found the file OTA downloaded. It was stored on some emulated storage that wasn't visible the normal way. So yours may still be on your phone somewhere taking up 400mb.
[Verizon Samsung Galaxy S 4] anothersmith:
mine were under the downloads ap..they said they were still downloading..I deleted them from the download app and downloaded via romhut using chrome...no problems

https://romhut.com/versions/jflte-gpe-20150702
[Verizon Samsung Galaxy S 4] jackdubl:
Yeah, that must have been it.
[Verizon Samsung Galaxy S 4] zilla.:
Anyone having issues after installing the ROM? I can't get past recovery after rebooting.

I do a full wipe and then install. The system reboots, gets to the Samsung screen with the unlocked padlock, and then immediately boots in to recovery again. If I select reboot again, it goes back into recovery after a little bit.
[Verizon Samsung Galaxy S 4] bswides412:
I installed the latest update (7-2-15) without problem. Did you try cleaning cache? I did a full wipe (internal storage included) when I upgraded the ROM.

On a side note, I am getting insane standby battery usesage (under 2%/hr.) Idk if it is the updated ROM, googly kernal, updated rogue apps or what, but life is good for right now!
[Verizon Samsung Galaxy S 4] zilla.:
Yes I did a factory reset and also wiped the dalvik cache and cache.

The ROM seems to flash fine but it just boot loops back to TWRP recovery.

I've tried installed the stock kernel also and it doesn't do anything. Is there some kind of prerequisite to install?
[Verizon Samsung Galaxy S 4] hakkalugi:
I think someone already asked this, but what version of TWRP are you running?

It could easily be that you just need to update TWRP.
[Verizon Samsung Galaxy S 4] zilla.:
Yeah you were right. I had an older version of TWRP. I updated it and it finally worked. Thanks for the suggestion!

To recap (if anyone is looking for a solution to my problem):

1. Flashed the ROM.

2. Rebooted. The samsung screen with the unlocked custom padlock shows but then the phone doesn't actually boot up. It goes straight back into the TWRP menu.

SOLUTION = I was running an old version of TWRP (2.2?). Restored my backup, then installed the latest version of TWRP using TWRP manager. I noticed someone else say in this thread to use no version higher than 2.8.4. Reflashed and the phone boots up without any issues.
[Verizon Samsung Galaxy S 4] hakkalugi:
Success. Glad to hear you had an easy answer.
[Verizon Samsung Galaxy S 4] gts24:
Still isn't working for me , see my next post.

---------- Post added at 11:06 AM ---------- Previous post was at 11:04 AM ----------

I'm on the latest edition of this ROM. (JFLTE-GPE-20150702)

Your issue is identical to what is happening to me, I have updated my TWRP to the recommended level, wiped EVERYTHING on my phone. I am absolutely 100% unable to dial out using my google voice # using this ROM

I ONLY give out my Google Voice # to my clients, and have my phone prompt me everytime "use google voice to make this call or carrier, and I select with EVERY call." The dialer simply dials before the prompt even gets a chance to ask me, and uses my carrier phone #.

Basically this issue is an absolute 100% showstopper for me and I will have to restore my ancient HDROM

Many others have reported this issue since very far back in the existence of this ROM.

http://xdaforums.com/showpost.php?p=58523687&postcount=4869

http://xdaforums.com/showpost.php?p=58523999&postcount=4870

http://xdaforums.com/showpost.php?p=58521482&postcount=4865

http://xdaforums.com/showpost.php?p=59791890&postcount=5257

If the devs need anything from me as far as bug reporting or testing, please do let me know. I simply can't use this phone without being able to use google voice via the dialer.

---------- Post added at 11:10 AM ---------- Previous post was at 11:06 AM ----------

Until the dialer + google voice selection issue is fixed, is there a dialer we can install/use to overcome this issue?
[Verizon Samsung Galaxy S 4] Oishikatta:
Of course!

You have a few options.

One is to simply install the Google Hangouts app and the Google Hangouts dialer app. Dial outgoing calls with the Hangouts dialer. This does not require you switching to hangouts for your messages, I still use the classic google voice app for everything except making calls. Hangouts dialer uses data rather than minutes (VOIP) - so it's not an exact replacement at all, calls may be significantly lower quality depending on your service.

The other is to use voice.google.com in the browser on your phone, which works just as it would from a computer - you enter the number, google calls you, google calls the target number from your google voice number after you pick up.

You can even create an icon for that directly on your home screen if you prefer it to the hangouts dialer.

I haven't seen Google Voice work properly with any 5.0+ rom on my S4 unfortunately. It's still plenty usable though.
[Verizon Samsung Galaxy S 4] gts24:
Thank you, I really appreciate the reply. I use google voice to dial out through the native dialer so many times a day I'm not sure it's worth not rolling back or....... as this individual points out, CM12 dialer seems to be fine:

Is there any chance we could just rip the CM12 dialer out, install it in this ROM?
[Verizon Samsung Galaxy S 4] needslipo:
Is it just my phone or have the last few updates been extremely laggy? The phone freezes and lags unbearably and changing the cpu governor/io scheduler does little to fix it. Meanwhile my sister's phone running the 20150102 build is still snappy..
[Verizon Samsung Galaxy S 4] jackdubl:
All builds have been about exactly the same for me. Latest release feels the same. If anything, I'd say it was a little snappier before I said it was laggier.
[Verizon Samsung Galaxy S 4] needslipo:
Thanks for confirming. I decided to go nuclear and wiped system, data, dalvik-cache, cache and internal sdcard, then flashed the 20150702 build. The phone is snappy again :)
[Verizon Samsung Galaxy S 4] NikolaeVarius:
Maybe one of these days 5.1.1 will come out...
[Verizon Samsung Galaxy S 4] itsmejson:
Is it possible to get call recording with this ROM?
[Verizon Samsung Galaxy S 4] jackdubl:
I have always and will always use this over a rom's built-in recording: https://play.google.com/store/apps/details?id=com.skvalex.callrecorder&hl=en

It's worth the money.
[Verizon Samsung Galaxy S 4] aleggsue:
I wish there was an NC5 bootloader unlock. This ROM is gold, and it's the only ROM I'd leave Eclipse for.

Sent from my Eclipse'd S4.
[Verizon Samsung Galaxy S 4] gpz1100:
Any updates on the googletalk app issue with this rom?
[Verizon Samsung Galaxy S 4] jesand83:
Anyone have any issues with syncing a fitbit to this ROM? I had the fitbit one before and now have the flex. I can't get either one to sync consistently. I'm on the 6-21 version of the ROM but this has been going on for months really. It's funny, I just got the Xiaomi Mi Band to play with and it syncs way better. The fitbit will sync maybe one time in ten and never really background syncs. Anyone seen anything like this?
[Verizon Samsung Galaxy S 4] bswides412:
My fitbit on occasion will not sync. Sometimes I will have to unpair and then repair. I don't get great background sync, however I am often connecting to other Bluetooth devices throughout the day. Bottom line, it works, but not all that great.
[Verizon Samsung Galaxy S 4] Lanky09:
when i plug in my s4 to laptop it stays in usb debug mod efor 10-20 seconds then automatically switches to media storage..

i have tried different cable, usb port and even different laptop

how can i make it stayin debug mode?
[Verizon Samsung Galaxy S 4] Ermacaz:
Is it possible to silence emergency alerts on this rom?
[Verizon Samsung Galaxy S 4] Oishikatta:
I'm not using the S4 any more myself, but I believe you can use TItanium Backup to freeze the app that is responsible for emergency alerts (named something like "Emergency Alerts").
[Verizon Samsung Galaxy S 4] anothersmith:
In settings Wireless & Networks select "more" under Data Usage. At the bottom is Emergency broadcasts, Can you turn your emergency alerts off there?
[Verizon Samsung Galaxy S 4] Aminoacow:
I have been using this ROM for awhile now. I feel this ROM is quite fast and reasonably smooth and I like it. However, there are several issues still need to be addressed:

1. Battery drain. I don't know what is going on but my battery normally goes empty after 3-4 hours use (on 4G, normal use of some social apps, little web searching, 1-2 calls, ZRam turned off, logger turned off, google now voice activation turned off, location turned off). With official Rom and the same use, my battery can usually last a day before it goes completely dead.

2. Sometimes the lower half of the wall paper and lock screen will turn black. This is likely to happen when the screen is rotated horizontally and rotated back. - Don't know if it is exactly the cause of this problem.

3. As soon as I pick up a call, the screen went black. Also, during a call, the screen won't automatically light up when I move the phone away from my ear. This makes it very difficult to put the call on speaker or use the dial pad or hang up the call before it goes to voice mail.

I don't know whether or not I'm alone on these issues. I haven't seen this ROM been updated for some time. Hope these problems can be fixed in the next patch which will come soon. :D
[Verizon Samsung Galaxy S 4] Nick_73:
Just got the S4 on OC1, rooted with SuperSU, and I am new to this FlashFire stuff and not having a recovery. Will this work on OC1 Lollipop?? Thx
[Verizon Samsung Galaxy S 4] TheBadBen:
Nope.
[Verizon Samsung Galaxy S 4] soad1789:
Has anyone had issues with xposed on 5.0.1 of this ROM? I know in the OP it says Xposed is unsupported but I really want to be able to use it to use GravityBox for one feature; long-pressing the Back soft-touch button to immediately switch to the last active app a la alt-tab on desktop. Really appreciate any input on this, thanks.
[Verizon Samsung Galaxy S 4] cognitivedissonance:
I'm on the 03/15 build. Xposed works as does Gravity Box.
[Verizon Samsung Galaxy S 4] jackdubl:
So, I guess Sammy won't be updating this phone anymore? All those false rumors of 5.1.1 had my hopes going for so long. Still the best phone I have ever had, thanks to Dan the Man.
[Verizon Samsung Galaxy S 4] gpz1100:
Got an update from the official google play services about a 5.1 update. Pretty sure this will not work and likely cause issues. Tried hunting for the file but it's nowhere to be found.

Where is google play services hiding this and what needs to be frozen so it's disabled in the future?

---------------------

Edit

Found it in the /cache folder, called update.zip

It does indeed contain some nasty stuff including aboot and tz. Partitions not meant to be flashed on this device (and still have it working).

version_info file

Current Firmware :I9505GUEUDNL3/I9505GXARDNL3_2809293_REV06_user_low_shipFOTA.tar/I9505GUEUDNL3
Update Firmware :I9505GUEUDOH2/I9505GXARDOH2_2834474_REV06_user_low_shipFOTA.tar/I9505GUEUDOH2

Also has a baseband patch.
[Verizon Samsung Galaxy S 4] needslipo:
Anybody get this notification? Is it safe to apply this update or should we skip it?
[Verizon Samsung Galaxy S 4] Ermacaz:
Got it too. No clue if safe to install.
[Verizon Samsung Galaxy S 4] sob372:
Anyone else getting a not enough storage notification? I've got over 7gb out of 9 free can't fix it.

Running 702 build
[Verizon Samsung Galaxy S 4] vladness:
So it seems to me that this is great news that we finally get the fabled official rollout of 5.1 for GPE!

Perhaps Dan, if he so very graciously chooses, can use this update to make an official GPE 5.1?

I am running on the 7/2 build and figure that if this triggers an official google update alert, the update should be for the most part fully compatible with the code already put out by Dan. Of course I can be completely wrong but this was an exciting development last night.
[Verizon Samsung Galaxy S 4] swieder711:
I would like to see one more update for my aging S4.

I just ordered a Moto Pure X with 64 GB of memory. Seems to be easy to unlock the bootloader. Hopefully there will be lots of Dev Support.
[Verizon Samsung Galaxy S 4] azjaffo:
Yeah, i got this today, too. haven't tried it. Waiting to hear if it is going to mess anything up.
[Verizon Samsung Galaxy S 4] vladness:
It did nothing for me when I tried to apply it. It restarted, gave me a notification that recovery was loading, then touchwiz came up and that's it. After rebooting, the notice to update does not appear again unless the update.zip is deleted from Cache folder.

I have not tried manually flashing the file from the cache folder, just know that automatic update does nothing.
[Verizon Samsung Galaxy S 4] Flypanam:
It just aborts using CW Recovery, both with the system update and a side loaded .zip.
[Verizon Samsung Galaxy S 4] djdmbrwsk:
+1
[Verizon Samsung Galaxy S 4] azjaffo:
So I allowed it to "install" which just booted up recovery mode (I use TWRP.) Nothing happened in recovery. Rebooted - but I got the update notification again. How do we disable these notifications?
[Verizon Samsung Galaxy S 4] bswides412:
Quick Google search shows that there is a 5.1 update! Yippie!

http://www.androidpolice.com/2015/0...update-to-android-5-1-heres-the-ota-zip-file/
[Verizon Samsung Galaxy S 4] Oishikatta:
Just long press on the notification, click the i icon, and select block notifications.
[Verizon Samsung Galaxy S 4] flamadiddle:
Add me to the chorus of users who would love one last update for this phone. Thanks for all the work you have already done on this great ROM [MENTION=4830253]Danvdh[/MENTION], [MENTION=1897326]googy_anas[/MENTION], [MENTION=4325945]ktoonsez[/MENTION], [MENTION=4600715]sbreen94[/MENTION], [MENTION=3443334]MattBooth[/MENTION].

http://androidandme.com/2015/09/new...y-edition-finally-getting-android-5-1-update/
[Verizon Samsung Galaxy S 4] jackdubl:
I am ready for one last donation, Dan.

And to everyone else: check out the i9505 threads for progress. Dan is already working on this but there are problems.
[Verizon Samsung Galaxy S 4] itsmejson:
I'm in for another donation as well!
[Verizon Samsung Galaxy S 4] bswides412:
Yes, it seems like everything is ready to go except the camera! Fingers crossed!

+1. I've donated before and I will be donating again. This will allow me to extend the life of my phone even farther than it has already!
[Verizon Samsung Galaxy S 4] bswides412:
Just a matter of time now!

http://xdaforums.com/showthread.php?p=62805660
[Verizon Samsung Galaxy S 4] Danvdh:
UPDATE IN THE OP

Android Lollipop 5.1

Download the Stock Edition here

CLEAN FLASHES ONLY
[Verizon Samsung Galaxy S 4] bswides412:
THANK YOU! Still in the process of downloading (stupid Romhut...)

Either way, I can't thank you enough. With a newborn at home (1 week today!), we are trying to conserve money where we can. Your update will allow me to squeeze even more life out of my S4! For that, enjoy a few beers on me!

Confirmation number: 55D95038KP0289124 :)
[Verizon Samsung Galaxy S 4] gpz1100:
Has the update been loki patched? Getting the unauthorized screen when booting the new update.

Looks like this

Secure fail: Kernel

The old loki patch zip doesn't seem to work on this.

Thanks!

Installing '/external_sd/loki-doki.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
about to run program [/tmp/loki-doki.sh] with 1 args
4096+0 records in
4096+0 records out
2097152 bytes (2.0MB) copied, 0.053406 seconds, 37.4MB/s
20480+0 records in
20480+0 records out
10485760 bytes (10.0MB) copied, 0.264648 seconds, 37.8MB/s
error: only position independent executables (PIE) are supported.
error: only position independent executables (PIE) are supported.
rm: can't remove 'out.lok': No such file or directory
run_program: child exited with status 1
script result was [/system]
I:Legacy property environment disabled.
Updating partition details...
I:Data backup size is 1220MB, free: 5691MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
I:Set page: 'flash_done'
I:operation_end - status=0
~ # ←[6n

---------- Post added at 09:18 AM ---------- Previous post was at 08:49 AM ----------

Edit: Flashed the googley kernel from here: http://xdaforums.com/showpost.php?p=62814742&postcount=21521

direct link: GoogyMax3_GE5.1-Kernel.zip - https://www.androidfilehost.com/?fid=24052804347815277

This gets the phone to boot, still upgrading apps.

Yes, I did a dirty flash :D, will test it out, if fails then will start from scratch.

---------- Post added at 09:48 AM ---------- Previous post was at 09:18 AM ----------

Ok, phone boots fine after dirty flash but xposed is disabled (to be expected).

Flash updated xposed framework from here: http://xdaforums.com/showthread.php?t=3034811 Phone will go through the optimizing apps again
[Verizon Samsung Galaxy S 4] gpz1100:
Edit 3: Mostly everything appears to be working - gps, cell connection, data (did have to edit build.prop as i'm using the s4 on a mvno in 3g mode only).

So far the only app that appears to be broken is google voice. Hopefully others can report in if this is due to dirty flashing or some other incompatibility.
[Verizon Samsung Galaxy S 4] gpz1100:
Edit 4:

Found out the external sd card is not visible. Going to try some other kernels when I get a chance. I'm hopeful ktoonsez has something for 5.1 - his/her kernel worked great on 4.4.x and also fixed the compass in that version of android.

Edit 5: Not too many options for GE roms and 5.1 kernels. Tried a few cm12.1 based i9505 kernels but just bootlooped.

@Dan, when you get a chance, if you could implement the loki kernel patching with the stock kernel. Maybe that will be the best way to go.
[Verizon Samsung Galaxy S 4] Trygon:
Same problem as gpz, but flashing the googymax kernel just gave me bootloops instead of a verizon error.

Edit: Hah, decided to try rewiping and it took. Phone is booted now.

Edit2: Interface options are gone, can't seem to find a way to enable nav bar in the menu. Suppose I'll do it manually for now, might be related to the replacement kernel?
[Verizon Samsung Galaxy S 4] gpz1100:
If you were using xposed, you'll have to reflash the xposed framework - that did not carry through on a dirty flash. I haven't tried a clean flash yet until the kernel issue is resolved.

IIRC, by default, the navigation bar (home, back, recent) was not present in this rom to begin with.
[Verizon Samsung Galaxy S 4] flamadiddle:
Could somebody who followed the OP's directions (full wipe, no xposed) please post their results?
[Verizon Samsung Galaxy S 4] Danvdh:
there was some jeebo recovery i believe that will loki the stock kernel for you, I suggest you try to get that one working guys as stock is an actual 5.1 kernel, Googy is not
[Verizon Samsung Galaxy S 4] gpz1100:
I tried a lokipatch I have in my collection. It's worked on previous builds but failed on this one. See the code I pasted on the previous page. That's from the recovery.log file. Maybe 5.x gets patched differently?
[Verizon Samsung Galaxy S 4] marioluigi64:
I did a clean flash along with Googy kernel, and have no cell signal whatsoever. The phone will periodically show that it is has a cell connection (along with displaying "VERIZON" as the carrier text), but I cannot send an SMS message or make a call. I have no data signal, no indication of one either.

Tried setting the bool.prop value ro.telephony.default_network to 8 and 10 with no luck.

Anything else I could try? :confused:

FWIW, I'm on Verizon prepaid.