yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note I717] jimmbomb:
Here's something I've learned since....

Bring up the photo, screenshot, whatever...

Then pull out your S-pen and press the button and hold it on the screen....

That takes a screenshot AND if you wait a few seconds.....

You then can edit it with the old photo edit features... No sketch artist or re-installing the apk...

Its all ready there.. You just can't access it without a S-pen screenshot.

Good luck
[Verizon HTC Droid Incredible 4G LTE] vazersecurity:
I know that there are ROMs for this phone that have the feature. But why doesn't the official CM have it? I know it is disabled on some ROMs when the software keys are disabled, but when you enable them, the settings for PIE controls should appear. But in the official ROM, they don't when you enable them by adding "qemu.hw.mainkeys" with the value of zero (0). The Avatar ROM does, but why not official CM? anyone willing to do the mod?
[Verizon HTC Droid Incredible 4G LTE] taj80:
You can try this, it works on a lot of devices.

http://xdaforums.com/showthread.php?t=1330150

[APP] LMT Launcher v1.99 for GNex/Nexus4/Nexus7/GSIII/HD2 and more... (ROOT)
[Verizon HTC Droid Incredible 4G LTE] SynisterWolf:
this will work on any CM10.1 rom or based rom for the Inc 4g LTE

ok so here's why pie isnt showing up on our phones. we have captive buttons so they turned the pic control off by default. to get it back you'll need to do some things:

first

you will need to edit your build.prop and add this line

qemu.hw.mainkeys=0

second

you will need to turn on "expanded desktop" you can do this by going to settings > system > expanded desktop

once you have that reboot the phone.

then go back into settings > system and at the bottom you will see pie options and nav bar options.

let me know if you need any more help
[Verizon HTC Droid Incredible 4G LTE] mdmower:
Since the PIE controls currently duplicate our always available capacitive keys, I'm not sure I see the use. Perhaps if more options than home, back, recent/menu become available it will be worth enabling.
[Verizon HTC Droid Incredible 4G LTE] SynisterWolf:
its good to use if the captive buttons don't work anymore. during the rezound days mine stopped responding and i had to use the pie controls. later found out that was the start to the end of my touch screen but it was great when you have no other options.
[Verizon HTC Droid Incredible 4G LTE] vazersecurity:
On the Official nightly, i cant seem to get it to come up. And, yeah, my home button currently doesn't work. That is why I ask. I have to use the back button.

--

Edit: here is what we have on OFFICIAL CM. Do I have to switch to something like Avatar? I know it has it when you enable the NavBar. It doesn't show anything about PIE controls. Only about the NavBar and quick shortcuts that go with the NavBar.
[Verizon HTC Droid Incredible 4G LTE] vazersecurity:
I have tried it. It works, but I would like to get the official ones working.
[Verizon HTC Droid Incredible 4G LTE] SynisterWolf:
Ah, the official build doesn't have it. It wasn't made till later. Try one of the RC builds. They have it.
[Verizon HTC Droid Incredible 4G LTE] vazersecurity:
There's my problem. Thanks.
[AT&T, Rogers HTC One X, Telstra One XL] filthyfnj24:
If you haven't already, you should check out Kii. I'm always in search of the best keyboard and I think I may have found it. Swiftkey has been my old faithful awhile now but I think its finally met it's match/replacement. It's essentially Swiftkey 4 with more customization. The trade off is the predictions aren't quite as "magical" as Swiftkey's. I'm a decent typist so it's a fare trade off for me. Being free in the play store it's definitely worth a look.
[AT&T, Rogers HTC One X, Telstra One XL] Z1cK:
nevermind
[AT&T, Rogers HTC One X, Telstra One XL] pside15:
Seriously? His post says it's free in the play store, why would you need a link? It literally just took me like 5 seconds to find it in the Play Store.

@OP

Thanks for the suggestion. Gonna try it out and see how it compares to Swiftkey.
[Samsung Galaxy Nexus] prophetwithadd:
So after a multitude of time spent searching on how and countless downloading of programs copious amounts of command line entry , Found a much easier way I believe , Install FX file explorer add root access add-on ,start a LAN server with your computer and just copy and paste mmcblk0p12 (user data block) from /dev/block then open with WinHex and Recover the files you wish. if this has already been discovered my apologies
[Samsung Galaxy Nexus] prophetwithadd:
almost forgot to mention this does take a good deal longer than Warticklers method as the transfer rate is much slower , but just start it before you go to bed or if you prefer pop a couple adderall and sit there :P
[Verizon Samsung Galaxy S 4] open1your1eyes0:
Patched Google Wallet for Galaxy S4

(Version 1.x - Old Version)

​

Description

: This method (nearly identical to my previous thread for the Verizon Galaxy S III) will help you get Google Wallet working on your Verizon Galaxy S4, regardless if you have a TouchWiz-based ROM or AOSP-based and whether it's Odexed or Deodexed.

This should also work on AT&T/Sprint/T-Mobile Galaxy S4 as well.

Please Note

: In order to use this method you need to be rooted and have a custom recovery (1, 2, or 3).

Video Demos of the Full Process

(Courtesy of 17akota and DroidModd3rX)

Downloads

(Version R96 v16)

How to Apply Mod

When Changing Roms

Updating to New Version Anytime

Credits

Credit goes to PaulOBrien for providing the patched Google Wallet apk (Original Post)

Credit goes to tonu42 for creating the original thread for the mod (Original Post)

Credit goes to rovo89 for creating the Xposed Mod (Original Post)

Credit goes to joemagistro for creating the deodexed-only version of this mod in the T-Mobile Galaxy S4 section (Original Post)
[Verizon Samsung Galaxy S 4] skiddingus:
Everything seems to be working. I will have to head to McDonald's tomorrow and give it a try. Thanks!
[Verizon Samsung Galaxy S 4] coolsilver:
Well I got this working from the other thread but looks to be same methods which is fine.

Now poking around... I noticed I have a devices section on the Wallet website and see I can reset it remotely if anything happens (though I wouldn't test that for ROM issues). Nice to know... is this more a secure element self destruct?

Also I notice a section asking to "Verify Identify" which if required... I will. But I am already reading where people have entire Play Store/Checkout locked out over this permanently over this. I just hope I don't get my account screwed one day because Google hates the grocery which I shop at or some lame thing where GPS is off by 500ft and claims I'm not there.... I know farfetched and over the top but just concerned or if anyone had issues with this.
[Verizon Samsung Galaxy S 4] iTechWNC:
Ok it works for me untill I change my build.prop back. What am I doing wrong
[Verizon Samsung Galaxy S 4] open1your1eyes0:
I wouldn't worry too much about those, I think the remote reset from the website just wipes the app by itself, the secure element stays working so it can be passed on. Highly unlikely and unnecessary that Google will want to brick a secure element for security purposes.

Which method did you use? What happens when you restore the build.prop? I personally have this running back on the stock build.prop using method A, so I know no issues on that one.
[Verizon Samsung Galaxy S 4] djdef80:
Will this work for the at&t phone of the same model sgh-i337? Stock rom rooted.
[Verizon Samsung Galaxy S 4] trogdor3222:
I'm currently stuck in "identity verification hell" and can't use Wallet even on my 100% stock Nexus 7. not happy. I sent them my license and a utility bill already and they still want more (SS card) which seems ridiculous. Amazon Payments was required to collect SSNs not too long ago...but they didn't require a freakin scan of the original document.

ugh.

anyway: Method A works great for me (still on TouchWiz for now sadly).

anyone else notice that when you change the build.prop product name, if you long-press the home button you see three icons along the bottom of the screen instead of "Task manager", "Google", and "Close All"? I believe that's what AT&T/T-Mo users see by default. wasn't enough to get rid of that stupid WiFi notification though ;)

Sent from my SCH-I545
[Verizon Samsung Galaxy S 4] open1your1eyes0:
The way I designed it I'm pretty sure it should. Give it a try and let us know. :)

Wow sorry to hear about all that difficulty. Hope you get it resolved with Google promptly! Glad to hear the method worked for you though (as expected). ;)

On an unrelated note take a read at this thread here regarding the icons instead of words and also the Wifi notification fixes: http://xdaforums.com/showthread.php?t=2295622
[Verizon Samsung Galaxy S 4] Parafly:
!!!! Gonna try this today
[Verizon Samsung Galaxy S 4] dseda86:
Awesome! Going to switch to odex rom and try later. Hopefully this works!
[Verizon Samsung Galaxy S 4] trogdor3222:
brilliant! thanks for sharing :)

Sent from my SCH-I545
[Verizon Samsung Galaxy S 4] Parafly:
Method A , Step 7. Reboot into your recovery and flash the Google Wallet mod

The file downloads as JFLTEVZW-Wallet-TW-JB-1.6-R96-v16.zip.zip

It's a nested zip file. does it need to be unzipped one level first or is that just the name of it ?
[Verizon Samsung Galaxy S 4] EVOme:
Mine has been at 'setting up this could take 5 minutes' for 10 minutes. I used Method A.
[Verizon Samsung Galaxy S 4] Parafly:
Nice, just finished Method A.

ZIP file was fine as is.

Everything appears to be working. Will confirm after i get to make a purchase at some point. Thanks!!!!

Edit; I had previously used Google Wallet on my Galaxy Nexus so everthing came back, cards, etc. easy peasy.
[Verizon Samsung Galaxy S 4] just4747:
What happens if we follow all steps properly and get Wallet working, but then flash the 3Minit framework after in order to use the UI tweaks that the 3Minit app offers? Does that mess anything up for Wallet or is that Xposed framework needed permanently?
[Verizon Samsung Galaxy S 4] open1your1eyes0:
My mistake, it's not actually a nested file if you look inside, I just forgot to rename it. I'll reupload with proper name to avoid confusion.

This one did take some time for me as well, usually just let it be there for about 5-15 minutes. It checks a lot of stuff in the background at this point.
[Verizon Samsung Galaxy S 4] EVOme:
Wow!! That took like 23 minutes to configure, but it's working!!!!!!!!! Solid work on this. This was the only thing my S4 was missing.

THANKS!!!!!!!!!!!!!!!!!!!!!!!!!
[Verizon Samsung Galaxy S 4] open1your1eyes0:
The Xposed framework is needed to stay there for Google Wallet to patch properly but if I understand that 3Minit mod correctly I think it just added an additional patch to the Xposed framework to enable and doesn't need to replace it? Could be wrong but I think it should be fine.
[Verizon Samsung Galaxy S 4] ticrandall:
I already have xposed framework installed. Do I have to UN install it before doing this? I'll lose all my mods.. and have to set it all up again, grr.
[Verizon Samsung Galaxy S 4] open1your1eyes0:
In that case not required. All you have to do is update the new one that this mod flashes, the rest should remain the same however.
[Verizon Samsung Galaxy S 4] p-slim:
You are stuck in the old ways. Secure element is no longer a problem everything has moved to the cloud. There is no need to waste your time clearing the app. Flash on as many devices as you want without wiping
[Verizon Samsung Galaxy S 4] brizey:
I had to clear the app on my N7 to get it to work on my S4.
[Verizon Samsung Galaxy S 4] p-slim:
I also have an n7 and I used my s3 (from fear of breaking my new s4 drunk) when I went to Vegas last weekend. All three of my devices have google wallet and haven't been reset once
[Verizon Samsung Galaxy S 4] brizey:
Wonder what the deal was for me. It was a one, two, three thing. When i was first opening wallet on the s4 it gave me an error. I exited wallet on the s4. Then I reset wallet on the N7. Then I tried again on the S4 and it worked. No reboots, nothing. It seemed pretty causal, but maybe not. I guess it could have been something else.

Hmmm. Wonder what we can get away with with changing ROMS. Maybe restore a titu backup then do the xposed hack? Think that would work?
[Verizon Samsung Galaxy S 4] NickSaul:
I just installed this successfully on Hyperdrive 3.1 via Method A.

Just an FYI fore Hyperdrive users: If you go into the Hyperdrive settings, you can update the Xposed Framework there, which means you don't need to use the xposed installer app the gets installed after flashing the mod.

Thank you very much for this!
[Verizon Samsung Galaxy S 4] odinfire:
Tried this on my ATT phone. It would hang at set up. Also, after every reboot the "Android is Updating" box would show briefly. I'm restoring a nandroid backup now.
[Verizon Samsung Galaxy S 4] crobs808:
Does not persist through CyanogenMod 10.1 OTA updates. Have to reinstall every time. Also not the latest version of Wallet anymore. Always wants to update and I have to decline as updating via Play will break app.
[Verizon Samsung Galaxy S 4] p-slim:
Your doing it wrong. The directions allow you to update the app in the market. Also it will never persist through any rom update because every update will change the framework. If you update every day be prepared to add this to your crack flashing
[Verizon Samsung Galaxy S 4] BlastTyrantKM:
I got this running on my AT&T S4 using Method A. Worked perfectly first time...
[Verizon Samsung Galaxy S 4] gcarterny:
No problem on synergy option A. THANKS op for posting.
[Verizon Samsung Galaxy S 4] Bizack:
Nice process.

Hooked it up and got it working, now I need to go and spend some dough!

Thank you for your work and the collaborative effort on this...!

Nice work guys. :highfive:

Working on Beans 0.2.

~B
[Verizon Samsung Galaxy S 4] mcleaver84:
i got everything in and installed fine but for whatever reason when I try to add a card it tells me to check my cc info and try again. It does this with two different cards I've tried. Any thoughts, help??
[Verizon Samsung Galaxy S 4] lilphil240:
Thanks for this!!
[Verizon Samsung Galaxy S 4] peteskey:
I have the same problem but I cannot use Wallet. Got all the way through the instructions. Every time modify the build.prop with Root Explorer or with the app "BuildProp Editor" I can edit the file and save it, but when I check to make sure it saved properly, It has reverted back to the original. I am running on the stock Rom and I know I have root permissions. Tried fixing permissions in TWRP. Tried uninstalling and deleting data for Root Explorer. Any suggestions?. I am on an AT&T S4.
[Verizon Samsung Galaxy S 4] brizey:
Use the built in text editor from root explorer. It will even automatically save a back up copy that you can use to revert at the end of the process.
[Verizon Samsung Galaxy S 4] peteskey:
That's how I edit it...still won't save

---------- Post added at 05:27 PM ---------- Previous post was at 05:12 PM ----------

The permissions are rw-r--r--. I have root access so I don't understand why i cannot edi tit. I have also tried to change ther permissions but it is not sucessful. "Some file systems do not allow permissions changes"
[Verizon Samsung Galaxy S 4] Tada10:
Try FX File manager and FX file manager root addon. Works great. Has built in editor as well.

Sent from my Samsung Galaxy S4
[Verizon Samsung Galaxy S 4] EvanVanVan:
Hey, stupid question but is flashing GW safe? Was about to install it on my mom's S4, and had bad memories about the first GW flashing method on the Galaxy Nexus and people bricking their secure elements at some later date.
[Verizon Samsung Galaxy S 4] dts242:
I have been using this for several weeks. I was so excited to be able to use it again. Hadn't used it since last August on my Nexus. The reactions never get old haha
[Verizon Samsung Galaxy S 4] SimonTuffGuy:
Followed method A and it loaded and runs fine. We'll see if it works later today. Thanks for the effort all. :)
[Verizon Samsung Galaxy S 4] mharrall:
Ok I followed method a on Verizon s4 and I am gett8ng the message that it can fully initialize till it has access to the network but both my wifi and 4g are working I am running clean rom 1.3.any thoughts.:)
[Verizon Samsung Galaxy S 4] Joe T:
I had the same thing happen the first time I installed wallet. I removed everything and was successful the 2nd time around. Used method A both times. I'm stock and rooted. Good luck.
[Verizon Samsung Galaxy S 4] mharrall:
Ok dumb questiondid you just use the standard uninstall for gw or did you remove it another way
[Verizon Samsung Galaxy S 4] Joe T:
I had to uninstall with titanium backup. Also, I had to turn nfc on prior to opening wallet the first time.
[Verizon Samsung Galaxy S 4] mharrall:
Profit it was a problem with the build.prop corrected that it took 2 more reboots then it worked
[Verizon Samsung Galaxy S 4] SimonTuffGuy:
Used today at the local grocery store and worked flawlessly. I had done the Note 2 Wallet fix, but the payments never actually went through. Thanks again!
[Verizon Samsung Galaxy S 4] LuCaniTy:
pre-mod rom

Is there any rom that already premod with the google wallet outthere?

Thanks
[Verizon Samsung Galaxy S 4] brizey:
I don't think you can...you have to change the build.prop, set it up and change it back.
[Verizon Samsung Galaxy S 4] arcanexvi:
This. There was an app for the s3 that did the work for you. Eventually I'm sure one will pop up for the s4
[Verizon Samsung Galaxy S 4] notstevek:
Ran the script via gscript

Rebooted to recovery installed patch

Ran xposed installer did install/update

Rebooted

Went into xposed and enabled the module

Rebooted and opened up Google wallet

It just stays here at this screen..

I opened build.prop with root explorer to make sure it flashed the script properly and it did..

Any suggestions?

EDIT: NEVERMIND, literally took 10minutes for it to set up.
[Verizon Samsung Galaxy S 4] LuCaniTy:
, used that app with the s3, can't wait for the developer to bring it to the s4, I just hate how the carrier dictate what feature we can and can not use
[Verizon Samsung Galaxy S 4] Kaczman:
I've followed instructions to a T, and now when I try to launch it says "Device Not Ready"

Any ideas?
[Verizon Samsung Galaxy S 4] Simplexletalis:
Try disabling NFC adn re-enabling NFC in settings.
[Verizon Samsung Galaxy S 4] Kaczman:
Thanks for the suggestion. I tried it, reset it, tried it again, and still the same exact error message.
[Verizon Samsung Galaxy S 4] lazard:
question: after applying this mod, if you open NFC in the settings, under NFC payment is it supposed to say No payment method?
[Verizon Samsung Galaxy S 4] gravedigger76:
Yes that part shiuld be turned off. Wallet uses its own framework to charge and just thr hardware nfc chip.
[Verizon Samsung Galaxy S 4] Kaczman:
bump
[Verizon Samsung Galaxy S 4] Kaczman:
uninstalled everything, followed instructions again from step 1, including how to remove all data - still same error. Device not ready. Unable to proceed.
[Verizon Samsung Galaxy S 4] Himmad:
I am running Clean Rom 1.5 TW Odexed and have followed all the steps but keep getting the error saying Device Not Ready Wallet is unable to proceed until this device is fully initialized. Make sure the device has network access and try rebooting if the problem persists.

Any fix for this?
[Verizon Samsung Galaxy S 4] Solange82200:
Getting Device not ready as well. Tried turning nfc on and off but still getting same error

---------- Post added at 06:28 AM ---------- Previous post was at 05:33 AM ----------

fixed it, turns out root explorer wasn't saving my changes to the build. Prop file, I used another app to do it which did save the changes, retried everything and now working like a charm. Do that if you are getting "Device Not Ready" error...
[Verizon Samsung Galaxy S 4] Kaczman:
so can we assume this mod is no longer working and close the thread?
[Verizon Samsung Galaxy S 4] open1your1eyes0:
This mod has not changed since it was last reported working not long ago and OTA updates haven't affected it either. As always depending on your device and ROM, YMMV.
[Verizon Samsung Galaxy S 4] Kaczman:
no response since the 25th, and now the last 3 people to install and try it are getting the same exact message. am I missing something here? i am on stock MDL rom with stock MDL baseband, rooted.
[Verizon Samsung Galaxy S 4] Spunjah413:
The mod still works just fine. Make sure you willow directions to a T. Also verify your build . prop is actually saving when you edit it. I use ESFile Explorer.

The way I fixed device not ready is to open GW with my unedited stock build. prop til I got the build of incompatible device, then proceed to follow the steps as written

I am also not sure if your build.prop has to reflect your ROM, as ATT users who use I9505 ROM don't use the same build.prop as stock. Easiest way is to make a copy of the file and copy it over when finished.
[Verizon Samsung Galaxy S 4] gravedigger76:
did you hit r/w button at the top of the screen of root explorer before opening the file for edit?
[Verizon Samsung Galaxy S 4] Kaczman:
I've followed the instructions to a T. Twice. And I know build.prop is getting saved, because when I reboot and view the file, I see all the changes saved. T-Mobile Build.prop is located in /system, correct?
[Verizon Samsung Galaxy S 4] ervman1:
Just did this on my sprint S4...wallet is not giving me any errors and it seems to be setup. I just haven't been able to test if purchases go through because both Walgreens I went to didnt have their NFC set up. Will update

Edit: Confirmed working at McDonalds!! Giggity...thanks op :)
[Verizon Samsung Galaxy S 4] brizey:
This is primarily a Verizon thread and it works for us just fine. We have not had an OTA yet. And even if we did, most of us here will never take an OTA and risk losing the Loki exploit. And even if a new update made the particulars not work for ROMs based on the update, this thread would stay open as people worked out how to make it work with the new update.
[Verizon Samsung Galaxy S 4] :
Just restored from TWRP backup and of course, Wallet had to be reset. Couldn't get it set up at all - finally looked at build.prop after applying script and the ro.product.model=Galaxy Nexus was not being changed - other two lines were, but not this line (by script). Modified it manually, rebooted and continued process and was successful.

Just in case this helps others -
[Verizon Samsung Galaxy S 4] becca0327:
Wont reboot after build.prop final step

I'm tried this on my rooted SGS4 on AT&T carrier, running CM 10.1 nightly on 6-30-13 release. I accidentally updated CM to the 7-1-13 nightly and couldn't get it to work again. I went back to TW. Tried it again and I still can't get it to work. I can get through the entire set up until I change the build.prop file back to the original and reboot. Once I try to reboot the Samsung splash screen comes up but then I just get a black screen with the blue LED light pulsing. The battery gets VERY hot as well. The only way I can get out of this is by trying over and over again to boot into recovery mode. Once I'm there all I can do is restore back to my TW backup. Is anyone else having or had this problem. And is there a fix for it? In the instructions I noticed that it shows to reset the build.prop ro.product.name to jflteatt, but my original shows jflteuc. Should I change it to what the instructions show or just use a copy of my build.prop file? Thanks guys any info would be much appreciated!
[Verizon Samsung Galaxy S 4] p-slim:
This mod works just fine still.

you have a sprint s4, you don't need this mod, the sprint S4 along with every other sprint device is allowed to download wallet from the market and it will just work, that's if sprint doesn't even have it on the phone already
[Verizon Samsung Galaxy S 4] aikeru:
Thank you for this! This worked great on my stock/rooted Verizon S4.
[Verizon Samsung Galaxy S 4] dscott973:
Confirmed Testing

Just to confirm as I hadn't read the full post so forgive me if I repeat known info, but I have confirmed working on AT&T variant of Note II all while using the Straight Talk network !