Database Info

icon for Gmail????

Ok i can't stop messing with my X. does anyone know what file the gmail icon is in.I am talking about the one that appears in the top left of the notification bar when you get new gmail. i tried changing the icon I found in the gmail app itself and had no luck when i got new mail.
No biggie if no one does just like to tinker.
Nycorduroy

nycorduroy said:
Ok i can't stop messing with my X. does anyone know what file the gmail icon is in.I am talking about the one that appears in the top left of the notification bar when you get new gmail. i tried changing the icon I found in the gmail app itself and had no luck when i got new mail.
No biggie if no one does just like to tinker.
Nycorduroy
Click to expand...
Click to collapse
I forget the name off the top of my head but if memory serves me it is in the framework-res.apk. So if you know what you have now decompile that and look in there to change it.

it used to be in the gmail apk, but since we got the update, search your data/app folder. you will find the update in there. For this one you must pull it from your phone, delete the old update (via market or app manager) change your image drop it into a good apk (one that wasnt decompiled) then re sign it. then install from sd or adb.

So in data/apps I see com.google.android.gm-1.apk. I checked and sure enough the icon is in there. So let me see if I got this right. Pull that file using adb to my computer. Then uninstall gmail app from phone. Download clean gmail app from market. Place icon I want in the apk using something like 7zip and then install gmail??? Am I understanding you correctly?
Thanks bad
Sent from my DROIDX using XDA App

pull the apk
uninstall gmail
modify the apk
sign the apk
install new apk

Ok hopefully last question. what is the best way to sign an application??
Edit: alright I figured it out. Thanks again bad4u

no prob, sorry i wasnt able to get back to ya on the last question.

Alright,
I have tried and tried but no luck. Here is what i have done so far:
pulled the update from phone. uninstalled gmail updates. Modified the icon image in the gmail update. Signed the modified new gmail update apk ( did it twice separately with 2 different methods found on these forums). Sent signed, modified new update for gmail back to data/app on phone. disconnected phone from pc. through root explorer clicked on the new update. It attempts to install and then comes back with application failed to install. Just to check if i click on the unmodified update.apk it installs just fine.
Any ideas?? So little of a mod, but it is driving me nuts!!!

nycorduroy said:
Alright,
I have tried and tried but no luck. Here is what i have done so far:
pulled the update from phone. uninstalled gmail updates. Modified the icon image in the gmail update. Signed the modified new gmail update apk ( did it twice separately with 2 different methods found on these forums). Sent signed, modified new update for gmail back to data/app on phone. disconnected phone from pc. through root explorer clicked on the new update. It attempts to install and then comes back with application failed to install. Just to check if i click on the unmodified update.apk it installs just fine.
Any ideas?? So little of a mod, but it is driving me nuts!!!
Click to expand...
Click to collapse
You placed in system/data then tried to install? if so just place on sd then try to install.
Are you decompiling then recompiling? if so, just take your edited images and drop them into the apk you didnt decompile, into their correct folders then resign.
do you have "unknown sources" checked in settings>app
try those, if you still cant get it, i might be able to look at them and check it out.

Finally got it!!! The only way I got it to work after trying every possible suggestion was to use Ninjamorph. No matter how many times i uninstalled, edited, signed, and attempted to install I kept getting application did not install. Don't know why but it would not accept my signed apk. I never even decompiled it. Weird but i am new at this stuff. ninjamorph took the least amount of work and effort and it worked 1st try.
Go figure.. thanks bad4u for all your help. i almost gave up but your suggestion kept me going.
Now, what can i mess with

I would like to see the image you used. Maybe I will do the same. Could you do a little step by step on your ninja morph process? Thanks.
Sent from my DROIDX using XDA App

Ok I attached icon I am using.
These were my steps. 1. Download and install Ninjamorph from market
2. Put the gmail icon on root of sdcard
3. start ninjamorp
4. click allow checks in ninjamorph
5. when done click start new project
6. click data folder
7. click app
8. scroll down to and click com.google.android.gm-1.apk
9. NM will extract files, just wait
10. when down click res
11. click drawable-hdpi
12. scroll down and click stat_notify_email.png
NM will bring you to the root of the sdcard
13. click on the new icon that you want to use
14. NM will replace it, once done, click on blue arrow in bottom right of NM
15. click finish project
16. You should see com.google.android.gm-1.apk. Click it.
17. hit ok at all warnings. One will mention zipalign or something like that I clicked no for that one.
18. Phone should reboot (if not do it yourself) and you should have the new icon appear in top left of notification bar when you get Gmail.
This is how I got it to work. Of course make a backup and don't blame me if anything screws up
Nycorduroy

Here it is in action

Man! That is the kind of write up I can appreciate.
+10
Do you have any other images you can share? i.e. tweetdeck, set cpu etc?
Also - I assume - just right click on the icon and "save as"? It is the proper size? I mean the gmail icon is the exact one you are using?
thanks a bunch.

glad you like the right up. This forum has taught me so much so I gotta give back what little I do know. Yeah just right click and save as. It is the right size and named correctly. As for other icons, don't have anything special really. All the ones I have, I've snagged from these forums and other droid spots.

where is this icon on gingerbread? Ur Guide doesnt works for me :-( ne new icon is inside the .apk file but still the old gmail icon appears and makes me crazy
im on gingerbread 2.3.3 with a ram build on HTC HD2
any help?

honki said:
where is this icon on gingerbread? Ur Guide doesnt works for me :-( ne new icon is inside the .apk file but still the old gmail icon appears and makes me crazy
im on gingerbread 2.3.3 with a ram build on HTC HD2
any help?
Click to expand...
Click to collapse
I'm having the same issue I've tried everything to change it.

The Cause Of Bootloops From Wiping Data on Themes

I have been trying endlessly to find the cause of the bootloops when you factory reset(wipe data/cache)> I believe I have narrowed it down to either in the framework-res.apk(however I do not believe it is the battery mod causing this). Its not the reboot recovery mod either because I made a version of my theme of the stock deodexed theme with no mods, and just modded services.jar to change some colors around and it still bootlooped.
But the normal unthemed stock deodex template you can wipe data(however I believe the android keyboard fc's everytime)
I need some advice/help from some of the experienced devs out here. At first I thought it was because of compressing the .jars when modding them(for example serives.jar) however I realized that if the stock deodexed template or ROM didnt bootloop on data wipe, it couldnt be that because when deodexing you have to compress the .jar's when adding the classes.dex using 7zip or somthing.
I also took a version of my theme that has the reboot recovery mod, and the 1% battery mod(both of which I confirmed not to be causing it by process of elimination) and unzipped the .jars I had modified, and zipped them up with no compression, and it still bootlooped.
It seems like its a combination of several things. If anyone out there experienced with theming and how the framework works that can help I'm all ears because I want my ROM to wipe data on the first release to give the best possible install without them having to go back to stock to wipe data. Hoewever at the moment it just bootloops if I wipe data.
I am at a complete loss lol! It's so frustrating and confusing!

Have you been unzipping and rezipping with the latest version of apktool (1.4.2, unofficially distributed by Brut.all)? And if so, then... I may be at a loss for words too. Then again I haven't wiped data in a while, but never had any issues either...
The very act of recompiling those files might result in smaller ones (blame apktool not me)... maybe that's the reason?
Going to check that out on my BL right now.

Extra thought: Where are you wiping data from? I remember on my old Optimus, if you wiped data from the regular phone, it would crash the phone into a bootloop too. But if you did it from recovery, everything was fine.

Recovery. I never wipe from phone menu. Its somewhere in the framework Res but I don't know what it is!
Sent from my MOTWX435KT using Tapatalk

How does your phone look with the stock framework-res applied?
Is there a bare minimum of a /data structure you can flash back onto your phone to get it to worK? If so, you could make a /data-flashing update.zip instead. A little hacked, but it would still work...

Tried that. Too many permission complications!!
Sent from my MOTWX435KT using Tapatalk

Is there a way to just delete stuff until you can't delete any more, and then make a nandroid backup of that specific image, and then make the image flashable?
Or just delete all your data or something, then Nandroid it... I dunno. Opening images for editing is too much of a pain.
Stupid permissions, why can't everything be more like Windows?

If you use the latest CWM(5.0.2.3) with the blue text it defaults to making .tar backups instead of .img nandroids. But if you wanna unpack a nandroid use a tool called unyaffs.exe compiled for windows.
The new CWM can be found in a flashable zip here:
http://forum.xda-developers.com/showthread.php?t=1282951
And I'll attach the unyaffs.exe program. You just use it through the command prompt and change directory to where you unyaffs.exe is located at and put you system.img or data.img in there with it and call unyaffs system.img or unyaffs data.img. It will extract everything to that folder. Pretty neat its how I made the stock ROM for this phone originally!

One of these days, you devs gotta tell me where you find these tools, after I googled and googled and only came up with a Python script! (Heck, even the name "unyaffs" sounds familiar.)
Is there an easy way to throw those files back together? I mean, the structure would probably be the worst part, but from what it sounds like you can just throw a bunch of files together by practically appending to them... (Edit: from the unyaffs source page. "Now it can only extract images created by mkyaffs2image" probably answers my question.)
again, not like I know what I'm doing. But ah well .w.
Edit 2: Herp derp, this would be a little easier from Linux... I think. But I really, really don't want to put Linux on my computer.
Edit 3: I suddenly don't feel totally stupid... http://forum.xda-developers.com/showpost.php?p=16084313&postcount=17

Try this; wipe data, flash, wipe cache, wipe dalvik, and fix permissions. I just did that testing my rom. It booted. I didn't flash back to stock. But, my dumb ass didn't include the set up wizards in my rom so I really couldn't do much. Had to restore. I always flashed with this procedure with my vibrant with no problems. Hoping it will work for y'all.
Sent from my MOTWX435KT using xda premium

Does your rom have a modded framework. Like reboot recovery, themes or 1% battery mod?
Sent from my MOTWX435KT using Tapatalk

b_randon14 said:
Does your rom have a modded framework. Like reboot recovery, themes or 1% battery mod?
Sent from my MOTWX435KT using Tapatalk
Click to expand...
Click to collapse
Reboot/recovery in power menu, and 100 charging/100 discharging battery mod. Tried it again, it booted, but had a slew of acore FCs. It boots though.

Dan_Brutal said:
Reboot/recovery in power menu, and 100 charging/100 discharging battery mod. Tried it again, it booted, but had a slew of acore FCs. It boots though.
Click to expand...
Click to collapse
As cool as that is, I don't think that counts... hmm. Is your framework-res.apk signed? I had bootloop issues with an unsigned framework-res.apk (just pushing it over, file-explorer style), and then force-close up the wazoo when I signed it.
Ironically, I solved the problem by putting the framework-res.apk into a flashable zip and, well, flashing it.
Feels weird man. This is like deja vu or something...

primetechv2 said:
As cool as that is, I don't think that counts... hmm. Is your framework-res.apk signed? I had bootloop issues with an unsigned framework-res.apk (just pushing it over, file-explorer style), and then force-close up the wazoo when I signed it.
Ironically, I solved the problem by putting the framework-res.apk into a flashable zip and, well, flashing it.
Feels weird man. This is like deja vu or something...
Click to expand...
Click to collapse
And why wouldn't it count? Signed with testkey x509.pem and testkey.pk8.

Dan_Brutal said:
And why wouldn't it count? Signed with testkey x509.pem and testkey.pk8.
Click to expand...
Click to collapse
Because ACore force-closes just don't make a working rom Although they're... marginally closer to it.

primetechv2 said:
Because ACore force-closes just don't make a working rom Although they're... marginally closer to it.
Click to expand...
Click to collapse
True, but I got the system to boot without a loop.
Sent from my Motorola Triumph using xda premium

Yeah I'm giving up lol. My rom will ist not wipe data and if you do wipe data then you will have to restore a stock backup for data!
Sent from my MOTWX435KT using Tapatalk

[Mod] Google Play Multi DPI fixed

I have tried multiple play store fixes from around the web and seemed to receive multiple force closes and various other issues when trying to launch Google play and Google apps. So, I decided to take the time to actually fix the files for the rom that I am currently using. Therefore, if you are someone who modified the DPI of your phone manually, happens to be running the Alpha for CM9 (or are willing to try with other roms) you can download the Vending.apk and GoogleServicesFramework.apk from this thread here and see if it helps you too. I should mention that you have to Clear data on the Google Play Store after replacing the files so it can again work properly.
I know many people are going to just say "why didn't you just download LCDModderPro, since it has the market fix?" Simple answer, because I wanted to do it myself. That is one of the great things about Android, it's open source and you can modify things to meet your needs. So why did I post this if I just wanted to do it myself? Well, once it was done I figured I might as well share... below are the links if anyone finds it to be useful.
Google Play 3.5.16:
My attempt at a CWM flashable zip: http://d-h.st/L5B
The files if you just want to copy them to /system/app yourself: http://d-h.st/AhT
The original files in case something goes wrong: http://d-h.st/5FS
Google Play 3.5.19
CWM Flashable Zip: http://d-h.st/d0t
The files if you just want to copy them to /system/app yourself: http://d-h.st/JGo
Google Play 3.7.13:
CWM flashable zip: http://d-h.st/fvz
The files if you just want to copy them to /system/app yourself: http://d-h.st/GfI
I am requesting that only people more experienced try this one ^^ out. I am trying something different this time around and I only actually edited a couple of lines, literally one in both the GoogleServicesFramework.apk and one in Phonesky.apk. It has been working for me for three days now, if you have an issue or it fails to work let me know.
Don't forget to clear data for the Google Play store after installing

Do what you do bro lol
Sent from my SGH-T989 using Tapatalk 2

Why didn't you just download LCD Modder Pr..... Oh..... Nevermind....

SolsticeZero said:
Why didn't you just download LCD Modder Pr..... Oh..... Nevermind....
Click to expand...
Click to collapse
Ha! I guess that little rant wasn't totally necessary...

Thank you for sharing! I personally used LCD Modder Pro, but it's good to know another way to get it done!! Thanks again!

Good work. there is option if we dont wanna use lcd modder pro....

Thanks, works great. I like the fact that I can get Google Play working without the use of an extra application. I'll hope you keep this updated.

PlagueBoy said:
Ha! I guess that little rant wasn't totally necessary...
Click to expand...
Click to collapse
Yeah, I was just messin with ya, dude. Great work, by the way. This is a lot more convenient.

Google Play Version 3.5.19
I downloaded and installed the newest Google Play store version (3.5.19) and it appears that google has changed the display metrics from DPI to Height/Width. I am waiting to see if the old problem of apps becoming unsupported reoccur with the new version. As of now, after clearing data and toying with the DPI some more, I still have access to all my downloaded apps and the error hasn't occurred. I will update if it proves necessary...

PlagueBoy said:
I downloaded and installed the newest Google Play store version (3.5.19) and it appears that google has changed the display metrics from DPI to Height/Width. I am waiting to see if the old problem of apps becoming unsupported reoccur with the new version. As of now, after clearing data and toying with the DPI some more, I still have access to all my downloaded apps and the error hasn't occurred. I will update if it proves necessary...
Click to expand...
Click to collapse
Oh nice, I hope the issues will be a thing of the past so we can run custom DPI with no hassle. Thanks for the fix, its appreciated.

PlagueBoy said:
I downloaded and installed the newest Google Play store version (3.5.19) and it appears that google has changed the display metrics from DPI to Height/Width. I am waiting to see if the old problem of apps becoming unsupported reoccur with the new version. As of now, after clearing data and toying with the DPI some more, I still have access to all my downloaded apps and the error hasn't occurred. I will update if it proves necessary...
Click to expand...
Click to collapse
I can confirm this. Just installed 3.5.19 running 200dpi. Cleared data and rebooted. New version shows all my apps where before "incompatible" apps would not appear. Finally done with this mod

elitrix said:
I can confirm this. Just installed 3.5.19 running 200dpi. Cleared data and rebooted. New version shows all my apps where before "incompatible" apps would not appear. Finally done with this mod
Click to expand...
Click to collapse
Yup. That is what I am seeing here as well. There should be a need to update the original post/files then. If people still want to use 3.5.16 until it is officially pushed to our phones then this will help, otherwise download 3.5.19 and you shouldn't have to worry about your DPI... as far as I can tell anyway.

I wish I would have found this before buying the LCD Density Modder Pro
Lol
Thanks for the hard work and the alternative approach to the app on the market! And thanks for the heads up about the new market
Sent from my SAMSUNG-SGH-I727 using XDA

PlagueBoy said:
I downloaded and installed the newest Google Play store version (3.5.19) and it appears that google has changed the display metrics from DPI to Height/Width. I am waiting to see if the old problem of apps becoming unsupported reoccur with the new version. As of now, after clearing data and toying with the DPI some more, I still have access to all my downloaded apps and the error hasn't occurred. I will update if it proves necessary...
Click to expand...
Click to collapse
After flashing and trying different roms for a bit, I realized that Market 3.5.19 ultimately ended up having the same issues. I went ahead and updated the APK and updated the OP with the new link for the download. It is a CWM zip, don't forget to clear data after the install.
I have only tested this on CM9 and AOKP roms, it should still work on others… but I thought I should put it out there that I have only personally tested it on those two roms.

PlagueBoy said:
After flashing and trying different roms for a bit, I realized that Market 3.5.19 ultimately ended up having the same issues. I went ahead and updated the APK and updated the OP with the new link for the download. It is a CWM zip, don't forget to clear data after the install.
I have only tested this on CM9 and AOKP roms, it should still work on others… but I thought I should put it out there that I have only personally tested it on those two roms.
Click to expand...
Click to collapse
Yeah i can confirm this. 3.5.19 seemed to work for one day or so. But what ended up happening was that the apps just wouldn't show up at all. I normally use dropbox to test it but that always worked on this new market. Dolphin browser, Draw something, app quarantine wouldn't show up in a search. My phone is running sky ics 4.0.3, dpi 180.
EDIT: omg thank you! You are awesome! Thank you for doing this! You are faster with updates then LCD Density Modder pro, they are lagging it with updates. He is still running 3.5.15, amazing! You rock!
---------- Post added at 09:05 PM ---------- Previous post was at 08:37 PM ----------
I just flashed the 3.5.19 CWM flashable zip you made and it worked great! As soon as i rebooted clear the data and amazing. I cant thank you enough! Thank you
If we wanted to do it our selfs, could we extract your zip and take the files? Just wandering for future references.

Just wondering what dpi are you guys using? I tried toying with dpi values on atrix, wanted to get a reference of what the range to look for the sweet spot on the skyrocket
Also i just tried flashing and could not even make it to the boot animation. I'm running the sky ice off the latest leak.
Admittedly i wasn't sure if i was to change the DPI first, reboot, and the flash, or flash clear data then change DPI. I'm back to a nandroid backup, if someone could shed light on this it would be of great help.
Thank you

s.sharm01 said:
Just wondering what dpi are you guys using? I tried toying with dpi values on atrix, wanted to get a reference of what the range to look for the sweet spot on the skyrocket
Also i just tried flashing and could not even make it to the boot animation. I'm running the sky ice off the latest leak.
Admittedly i wasn't sure if i was to change the DPI first, reboot, and the flash, or flash clear data then change DPI. I'm back to a nandroid backup, if someone could shed light on this it would be of great help.
Thank you
Click to expand...
Click to collapse
I think, at least I found, when doing the math that the native DPI of the phone should be 207.32 and CM9/AOKP tends not to like DPI being set on an odd number, so 208 is what I have settled on. Although, as Voiid mentions he is running 180 and elitrix mentions 200, just find something that works for you!
As for your issue, I haven't been able to replicate it on my phone. You didn't clear the cache/d-cache in CWM after install did you? I have heard there are times when ICS has issues after doing so... if you did that it could be your problem. As for the proper way to do things, well, I have flashed this at many different times with different roms. I recommend clearing data in apps manager after the flash though, that way it has to resend the DPI information mimicking a first boot or launch of the Google Play store. Try downloading the files them selves, extracting them and manually copying them into the /system/apps folder in something like root explorer. Don't forget to change permissions to rw-r-r.
Voiid - I have uploaded the files in non-cwm flashable format so you can just have the modded files and the link is in the OP. However, for future reference, yes you can just extract the files from the app folder in the CWM zip and use them moving forward as updates come along.

Thanks for the reply Plague. The problem i am having seems to be with dpi modder app. I tried changing the dpi to 200, 180 and 210 and all of them sent me into a bootloop (not actually sure if it was a bootloop because the phone never got passed the samsung logo, i'm assuming it was still on). Either way i resolved the issue by using rom toolbox and changing the dpi to 200. Then i flashed the modded play store and its working great. Thank fully i am crazy about having nandroid backups so i didn't loose anything.

PlagueBoy said:
I think, at least I found, when doing the math that the native DPI of the phone should be 207.32 and CM9/AOKP tends not to like DPI being set on an odd number, so 208 is what I have settled on. Although, as Voiid mentions he is running 180 and elitrix mentions 200, just find something that works for you!
As for your issue, I haven't been able to replicate it on my phone. You didn't clear the cache/d-cache in CWM after install did you? I have heard there are times when ICS has issues after doing so... if you did that it could be your problem. As for the proper way to do things, well, I have flashed this at many different times with different roms. I recommend clearing data in apps manager after the flash though, that way it has to resend the DPI information mimicking a first boot or launch of the Google Play store. Try downloading the files them selves, extracting them and manually copying them into the /system/apps folder in something like root explorer. Don't forget to change permissions to rw-r-r.
Voiid - I have uploaded the files in non-cwm flashable format so you can just have the modded files and the link is in the OP. However, for future reference, yes you can just extract the files from the app folder in the CWM zip and use them moving forward as updates come along.
Click to expand...
Click to collapse
Thank you PlagueBoy for the answer and the help!
s.sharm01 said:
Thanks for the reply Plague. The problem i am having seems to be with dpi modder app. I tried changing the dpi to 200, 180 and 210 and all of them sent me into a bootloop (not actually sure if it was a bootloop because the phone never got passed the samsung logo, i'm assuming it was still on). Either way i resolved the issue by using rom toolbox and changing the dpi to 200. Then i flashed the modded play store and its working great. Thank fully i am crazy about having nandroid backups so i didn't loose anything.
Click to expand...
Click to collapse
Yeah I had this issue too! Changing the dpi with LCD Modder Pro caused my phone to not boot too. I am not sure why though some apps that change dpi do that on this phone. On my old phone, the HTC aria, LCD modder worked. So idk. I just use root explorer and go to /system/ open build.prop as a text (make sure the folder is writeable) and change the dpi from within that my self. The line says
ro.sf.lcd_density=240
Its like in the center of the file.
You can change that number to whatever just make sure its a feasible number.
And then save it and reboot.
But you said rom tool box works so thanks for the heads up!
Sent from SAMSUNG-SGH-I727 using awesomesauce

Will this fix works on a galaxy s i9000
Sent from my GT-I9000 using Tapatalk 2

Verizon Galaxy S III (d2vzw): Persistent Google Wallet [ROOT]

__
__

ATT seems to work
Sweet idea! Just tried this on an ATT GS3 and it seems fine. I did not test other apps. I do get an unsupported device tag at the top in the app but I don't think that impedes the function. When I use the Nexus device device, name and model (maguro, yakju and Galaxy Nexus) I don't get the warning but probably more likely to end up with incompatible apps.
Do you reset Google Wallet prior to flashing a new rom or do you just have the build.prop update before you run wallet?

__

I'm confused. I have Wallet installed on my Verizon GS3 and I have no problems now. I am rooted and running Synergy ROM. When installed Wallet, I had to use a patched APK and edit my build.prop prior to installing Wallet to trick the phone similarly to what your script does (Galaxy Nexus, yakju, and maguro instead) After installing and setting up Wallet, I restored my original SCH-I535, d2vzw, d2vzw settings in build.prop and rebooted again. I am running Wallet no problems and it doesn't even tell me that I am using an unsupported device.
When I reboot my phone, it does not affect Wallet and my build.prop is not modified. I don't understand why someone would need your script to keep modifying the build.prop to say it is the pretend device? Please don't take my reply wrong, I'm simply trying to figure out what I am missing, not be a jerk.
I am always leary about leaving my build.prop modified because you trick other things into thinking your phone is something it is not. I feel this leaves you open to potential problems. I used Goo Manager the other day to see if there were any updates for my ROM and because of a modified build.prop it thought my phone was an AT&T GS3 and if I had downloaded and tried to flash an AT&T ROM I might have bricked it. I'm not sure, but I wouldn't want to take that chance. Also, isn't there a possibility of downloading an app from the Play Store that is only for the Sprint phone you're pretending to be and causing problems?
Jim

__

Hi Jeremiah,
Thanks for the info. Just so you know, I used that Google installer few weeks ago and it worked fine. I changed to a new ROM last week and forgot to reset wallet before switching which caused bunch of problems. I was able to fix them but the installer did not work for me anymore. I was however able to get wallet working by manually editing build.prop and installing a patched apk of wallet. After wallet was up and running, I reverted back to the d2vzw and SCH-I535 version of build.prop. So you know, I have my correct build prop AND a working Google wallet. I can send you the link but its the Verizon Google wallet thread in the mods and app forum under Verizon GS3. I understand if you switch ROMs it would need to be reset and build prop edited again, but I don't think the is a need to keep your build prop edited unless you are using the play version of wallet. Perhaps the link could get you the patched version and that might help.
Take care,
Jim

__

jeremiahmegel said:
As I recall, the patched APK isn't the newest version/update of Google Wallet, right? That's why I'm using the Play Store version: to receive updates to the app. If you don't care about updates, though, I suppose your way of doing things would be best. (I don't think it works throughout ROM updates, though. Let me know if I'm wrong about this.)
Click to expand...
Click to collapse
Oh OK... I'm not sure but that makes sense... You would know more than me! Thanks... Again I was just looking for clarification. Thanks for your work. Good luck.
Jim

jeremiahmegel said:
The "Unsupported device." error only shows up if you're running Google Wallet on a rooted device (unsurprisingly); you're right that it doesn't impede the function. And you don't need to do anything as the user before or after flashing a new ROM; once you update the ROM, your phone should reboot automatically within a minute or two of starting up to put the new build.prop into effect! Simply install this once and don't worry about it again! (Unless, of course, you uninstall Tasker or wipe your phone or something.)
Click to expand...
Click to collapse
So to clarify, when you say:
"And you don't need to do anything as the user before or after flashing a new ROM"
Do you really mean "you still have to reset Google Wallet before flashing a new ROM"?
Also, I'm wondering if it's possible that modifying build.prop might cause my Nfc.apk to stop functioning. I'm wondering this because it stopped functioning (after using 'Google Wallet Installer' - which does replace nfc.apk I believe, so that could be it, but not sure).
calaski8123 said:
Hi Jeremiah,
Thanks for the info. Just so you know, I used that Google installer few weeks ago and it worked fine. I changed to a new ROM last week and forgot to reset wallet before switching which caused bunch of problems. I was able to fix them but the installer did not work for me anymore. I was however able to get wallet working by manually editing build.prop and installing a patched apk of wallet. After wallet was up and running, I reverted back to the d2vzw and SCH-I535 version of build.prop. So you know, I have my correct build prop AND a working Google wallet. I can send you the link but its the Verizon Google wallet thread in the mods and app forum under Verizon GS3. I understand if you switch ROMs it would need to be reset and build prop edited again, but I don't think the is a need to keep your build prop edited unless you are using the play version of wallet. Perhaps the link could get you the patched version and that might help.
Take care,
Jim
Click to expand...
Click to collapse
Jim will you please tell me how you fixed it? I did not reset Wallet before installing a new ROM a couple months ago and unfortunately all my nandroids are bad due to a CWM bug involving partitions (I didn't do anything to my partition structure manually...).
Thanks a lot!

Hi,
I'll tell you what I did, but I was just trying anything so I'm not sure if I got lucky or if you have to do everything I say... First I went into application manager and I cleared all data and updates from wallet. Then I rebooted into recovery and did full wipe 3x. Then I went onto Google on my laptop and logged in. Go to wallet and then to your activated devices. Not sure what they are called but you will see all your devices that have wallet. Some might day deactivated. If there are any active then disable or remove them. I don't remember what the term is Google uses to Deactivate. Once you have no active wallet applications left on Google go back to your phone. Install the working ROM or good backup. I had a good backup with wallet working...i was able to restore that nandroid and reset wallet from within the app so that i could then install the new ROM. then After setup, reboot again and wipe dalvic cache in recovery. Then try to install wallet again. Thats pretty much how I got it fixed... The key was getting it deactivated online.
---------- Post added at 09:52 PM ---------- Previous post was at 09:28 PM ----------
Oh and I uninstalled wallet after clearing the cache and updates.. Forgot that part sorry.
Jim

I followed the instructions to the T and it worked perfectly. Thank you. But my question is, what happens to the Tasker Profile? After, I went back in to check out what you did. I am a relatively new Tasker user and was curious about what all was intailed. But when I went back the profile was gone and the only sign that I had imported the xml file was two variables. Is it supposed to disapear?

__

jeremiahmegel said:
As I recall, the patched APK isn't the newest version/update of Google Wallet, right? That's why I'm using the Play Store version: to receive updates to the app. If you don't care about updates, though, I suppose your way of doing things would be best. (I don't think it works throughout ROM updates, though. Let me know if I'm wrong about this.)
Click to expand...
Click to collapse
Correct, the patches lag behind the updates somewhat. You can only use Play Store Wallet if you build.prop matches Play Store Wallet accepted devices (d2spr being one of them). For this reason, I prefer to wait for the updated patched version - if you do that, you can keep d2vzw or whatever you want in your build.prop
As far as resetting when changing ROMs, back when everything was stored on the secure element resetting was a big pain in the ass. I don't even bother anymore - there's a separate "reset wallet" option in the menu of the actual app (different than clearing app data), but you don't need to use it. I just keep a version of Wallet Installer V3 in TiBu, and restore it after installing a new rom. After restoring Wallet Installer, just run it once and then reset build.prop - the installer downloads the latest patched Wallet.apk.

jeremiahmegel said:
No, it is not supposed to disappear. Since Tasker updated its UI, Step 4 ("Tap the green check-mark at the bottom-left of the screen to save the profile.") is no longer available. Instead, press the back button or home button on your phone (or just switch to another app) to save the profile, then continue to Step 5. Let me know if this works. Nice to know that I could help you get Google Wallet up and running!
Click to expand...
Click to collapse
I tried going through the steps again but I cant get Tasker to recognize the xml file when going through the import sequence. I downloaded and extracted (when extracrted its another file folder with the xml file in it), placed it on the root of my internal sd card. I go into tasker to import. It recognizes the file folder but when I select it, there isn't anything inside. Tasker wont recognize the basic xml file. I remeber when I first did this, the xml file was recognized without being in a folder. I can plainly see the xml file on the root of the sd card from Root Explorer in ROM toolbox. Would have it something to do with the permissions of the xml file? I show the permissions as rw-rw-r--.
I think I know why I am having to go this. I didn't follow the step to the T. I clicked "Run" before saving becasue I didn't see the green checkmark.

__

jeremiahmegel said:
What is the file name of your XML file?
Click to expand...
Click to collapse
I have the actually xml file on my sd card. It is named Replace_build.prop.prf.xml
When i go to the file through Root Browser in ROM Toolbox, its visible. I click it and it presents me with options to open it. I select Tasker and is says "Failed to move import to my sd directory"

08BajaBoy said:
I have the actually xml file on my sd card. It is named Replace_build.prop.prf.xml
When i go to the file through Root Browser in ROM Toolbox, its visible. I click it and it presents me with options to open it. I select Tasker and is says "Failed to move import to my sd directory"
Click to expand...
Click to collapse
I am not what was happening but I updated to CM10.1.0 RC2. I cleared anything I had tried previously with this tut. redownloaded the file and went though everthing again. It worked and the tasker profile stuck this time. Thanks for the help.

Great write up. Very simple to install. Google wallet was installed and running in less than 5 minutes. Thank you!
Galaxy S3 :good:
MOAR :BetteR:

Can anyone confirm this method works with 4.3? I made the jump to CM10.2 Nightly 8/27 (and tried 8/14, I think) and my phone goes into bootloop. It was working fine on CM10.1.2.

__

personalize not working (Stock, Sense, 4.0.4)

I went back to a stock rom and started manually debloating it but I deleted too much and now "Personalize" isn't working. I already put HomePersonalize.apk and HomePersonalize.odex back into system/app but I still don't have the app appearing in the drawer and it's not working via settings either.
Can someone tell me what other files are associated with Personalize? (the only two folders I was messing with was system/app and data/data)

curto said:
I went back to a stock rom and started manually debloating it but I deleted too much and now "Personalize" isn't working. I already put HomePersonalize.apk and HomePersonalize.odex back into system/app but I still don't have the app appearing in the drawer and it's not working via settings either.
Can someone tell me what other files are associated with Personalize? (the only two folders I was messing with was system/app and data/data)
Click to expand...
Click to collapse
Just reflash whatever rom you flashed. Also this should be in q and a.

filthyfnj24 said:
Just reflash whatever rom you flashed. Also this should be in q and a.
Click to expand...
Click to collapse
I see, sorry about the wrong place for this. I would prefer not to flash the whole rom.. it's gonna be a big pain the ass to redo everything I did. Considering I only started removing stuff from two locations I just figured someone would know what files the whole "Personalize" thing uses so I could undo what I did. Like maybe there's a com.android.XXX folder I need to put back perhaps?

curto said:
I see, sorry about the wrong place for this. I would prefer not to flash the whole rom.. it's gonna be a big pain the ass to redo everything I did. Considering I only started removing stuff from two locations I just figured someone would know what files the whole "Personalize" thing uses so I could undo what I did. Like maybe there's a com.android.XXX folder I need to put back perhaps?
Click to expand...
Click to collapse
If you don't wipe aka dirty flash you shouldn't have to redo much. All your settings will be saved and system apps will be reinstalled. Do you use titanium backup?
Edit: Also, not trying to be a **** about post location, you'd probably just get more help posting in q and a.