First this is a guide from the Verizon Note 2 forums, for those who don't know about it.
All Credit to WarlockLord, ogdobber, and tpmwr, and everyone else involved in this.
Visit the original thread here
Follow these steps, I have done this 3 times already and every time it works, IF you follow these steps.
I HIGHLY suggest using root explorer for this
1. Download the attached zip file, you must extract it, and place everything in their respective folders, backup your current files, rename with .bak on the end, paste the files in their respective folders from the zip. Set the correct permissions as the other files in the folder. Under the "Read" check, owner, group, others. Under "Write", check owner, and press ok.
2. Next, navigate to your build.prop in your /system and edit it to mirror the Galaxy Nexus.
ro.product.model=Galaxy Nexus
ro.product.name=yakju
ro.product.device=maguro
3. Reboot
4. Open your app drawer, find the wallet app, from there, set it up, it will say Setting up this will take 5 minutes, you WILL get a force close.
5. From this point navigate to your /system/app and delete the wallet app.
6. Reboot.
7 Open the play store, download wallet, now set everything up, and add a card, once you have registered a card, it will say the app needs to reset. Reset it, and wait. Once you get back to the screen where you can select your account, close the app.
8. Navigate to your /data/app and delete the wallet.apk in there. DO NOT UN-INSTALL IT!!, This is crutial, ONLY DELETE IT
9. Now head back to your downloaded files from this post and paste the modaco R87 wallet apk back into your /system/app, and set the correct permissions, under the "Read" check, owner, group, others. Under "Write", check owner, and press ok.
10. Reboot.
11. Now open wallet again from the app drawer and set everything up. It should proceed with no errors if you did everything correct.
12. Once setup, reboot again and open the app again to make sure its still working, and your cards are still there.
13. If its still working, you can now change your build.prop back to
ro.product.model=SGH-I317 or SGH-I317M(which ever variant you have)
ro.product.name=t0lteatt
ro.product.device=t0lteatt
If you do not change your build.prop back to stock values, it wll probably break SNote
14. Save the build.prop and exit.
15. Profit.
Everything you need to know is in this post, if its not working, you didn't do something correctly, or you missed a step.
VIDEO HOW TO - THANKS TO YELLOWGTO
YellowGTO said:
Here you guys go
Click to expand...
Click to collapse
I did this thursday night, works perfect
Sent from my GT-N7105 using xda premium
I was one of those who tested this out for warlocklord. Weird thing is, I re-did everything last night again just to see(going back to stock) without all those steps. I used the flashable zip(r87), replaced the build prop warlocklord uploaded when he first started it(attached). I load up wallet without crashing, everything loads and then I place back the original build.prop.
cmjkxa said:
I was one of those who tested this out for warlocklord. Weird thing is, I re-did everything last night again just to see(going back to stock) without all those steps. I used the flashable zip(r87), replaced the build prop warlocklord uploaded when he first started it(attached). I load up wallet without crashing, everything loads and then I place back the original build.prop.
Click to expand...
Click to collapse
Yea I did the same, you already had the folder in your data with saved stuff is why it worked.
However that is the verizon build.prop - I dont suggest people using it. Won't hurt, but verizon likes to block app's from the makret.
This is my first chance to use google wallet, lol its awsome.gas stations, cvs, gas stations, toys r us, mcdonalds.love using it
Sent from my GT-N7105 using xda premium
This going to be a really stupid and probably self-explanatory question... but I don't want to take any chance: Do you have to be ROOTED to perform this complicated procedure or can you be fully stock??
Dr. Evo said:
This going to be a really stupid and probably self-explanatory question... but I don't want to take any chance: Do you have to be ROOTED to perform this complicated procedure or can you be fully stock??
Click to expand...
Click to collapse
Rooted of course you have to copy files to the system directory.
Sent from my SCH-I605 using Tapatalk 2
Was holding off, but now must root! Damn you,XDA!
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
srtpusher said:
Was holding off, but now must root! Damn you,XDA!
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
Root it. Its not "your" phone unless you root it.
Im on tmobile and still no luck it fails when it tries to finish the transaction
Sent from my SGH-T889 using xda app-developers app
Did this thursday night and it works flawlessly, glad to have Wallet back after I lost my Secure Element on my GS3
revemou ear
I am on step 7 now, and I think I am stuck. How long does the reset take? The progress bar is stuck on 98%, on "Removing payment cards," for about 15 minutes now.
Roundabouts said:
I am on step 7 now, and I think I am stuck. How long does the reset take? The progress bar is stuck on 98%, on "Removing payment cards," for about 15 minutes now.
Click to expand...
Click to collapse
That is very normal. Try to back out of the app.
malinois16 said:
That is very normal. Try to back out of the app.
Click to expand...
Click to collapse
Yeah, I finally gathered my courage and backed out. I finished everything and now my wallet seems to be working. Time to give it a go at a store!
Is this something that would be able to be cooked into a rom- a working version of Wallet, or would this procedure have to be done after every flash?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
I originally used the original link that you posted. Those directions were a bit lacking so I ended up using the GS3 thread in combination with the original GN2 thread. It said to remove the APK. I was like, what APK, I am starting new, i don't ahve anything installed. So I assumed this person started off using the GS3 thread. So I went to the GS3 thread and flash modaco patched r87 and the GS3 NFC fix (I know, that was mistake). I then removed the APK. Then changed my build.prop. I installed the legit APK from play store. Then I opened it and activated my cards. It claimed that the app would restart on it's own, but it never did. I then just deleted the APK and then moved the modaco patched r87 into the system/app directory. Everything appeared to go well. I tried to make a payment and got a declined message at a 7-11. I then tried it at a CVS and but this time the NFC didn't even register. I then realized, I had the wrong NFC fix. So I flashed the NOTE2 NFC fix and was able to make my first successful wallet payment. Well everything ended up well so I'm happy. It seems that your directions are a little bit clearer than he original. Good luck to everyone else. I feel a little uncomfortable because my method was little dirty cuz I flashed the GS3 NFC fix first by accident. Once the new Cleanrom comes out with the multiwindow, I will try this process again from scratch and hopefully get a cleaner install.
Why am I getting the message Android is Upgrading everytime I reboot my phone? Is there anyway to get rid of it?
homegeek said:
Why am I getting the message Android is Upgrading everytime I reboot my phone? Is there anyway to get rid of it?
Click to expand...
Click to collapse
I can't speak for sure, but I've only seen that after clearing out dalvik, when it starts having its odexing fun.
-----
I would love to help you, but help yourself first: ask a better question
http://www.catb.org/~esr/faqs/smart-questions.html
Except I did not clear out the Cache and it happens everytime I reboot the device.
mastermindx85 said:
Im on tmobile and still no luck it fails when it tries to finish the transaction
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Go back and repeat the process.
Related
Sending from my phone.
Problem #1: I'm running RandomRom EI22 and I've done every step to prevent the System Update message, however it's still popping up. Definitely made sure I erased the systemupdate apk and everything else. What other methods are there to make it stop being such a nuisance?
Problem #2: I uninstalled regular Swype and installed the beta, ever since the original kept asking for a system update. After installing the beta, it worked fine. Now everytime I try, it keeps saying "Try again".
Volknochi said:
Sending from my phone.
Problem #1: I'm running RandomRom EI22 and I've done every step to prevent the System Update message, however it's still popping up. Definitely made sure I erased the systemupdate apk and everything else. What other methods are there to make it stop being such a nuisance?
Problem #2: I uninstalled regular Swype and installed the beta, ever since the original kept asking for a system update. After installing the beta, it worked fine. Now everytime I try, it keeps saying "Try again".
Click to expand...
Click to collapse
Do a search here on "FOTAKill.apk" - that was the only thing that helped me on both my phone and my wife's - but we are on Froyo so this might not work for you.
With that being said, all of what you tried has been suggested for Froyo users also, but didn't work - so give it a try. Sometimes the search on XDA doesn't seem to work well for me - so what I do is use Google, and in the search terms I type "XDA FOTAKill.apk"
You have to edit your build.prop to say 2.3.6 and EL30 in all places where it says EI22 and 2.3.5. Then reboot.
Sent from my SPH-D700 using xda premium
kennyglass123 said:
You have to edit your build.prop to say 2.3.6 and EL30 in all places where it says EI22 and 2.3.5. Then reboot.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Okay.....so how do I go about doing that?
Volknochi said:
Okay.....so how do I go about doing that?
Click to expand...
Click to collapse
With Root Explorer. Edit build.prop in system directory.
Sent from my SPH-D700 using xda premium
EDIT: I did the trick of allowing it to do an update, then I let it reboot, it goes to the "Triangle !" mode, wiped Dalvik and rebooted, and so far, it hasn't popped up yet.
Now to fix Swype...
Volknochi said:
EDIT: I did the trick of allowing it to do an update, then I let it reboot, it goes to the "Triangle !" mode, wiped Dalvik and rebooted, and so far, it hasn't popped up yet.
Now to fix Swype...
Click to expand...
Click to collapse
It will be back within a week.
Sent from my SPH-D700 using xda premium
If it'll be back within a week, then does that mean that there's no way of getting rid of that update message?
Volknochi said:
If it'll be back within a week, then does that mean that there's no way of getting rid of that update message?
Click to expand...
Click to collapse
I mentioned what has to be done before. Build.prop has to be edited.
Sorry, thought I mentioned that I did. My fault.
Yes, I did edit the build.prop file through Root Explorer, per your advice. Even after I did the final editing (missed a couple), the message still popped up. But, that's when I did the cache clearing and it didn't pop up again upon reboot.
Volknochi said:
Sorry, thought I mentioned that I did. My fault.
Yes, I did edit the build.prop file through Root Explorer, per your advice. Even after I did the final editing (missed a couple), the message still popped up. But, that's when I did the cache clearing and it didn't pop up again upon reboot.
Click to expand...
Click to collapse
Ok, that makes sense because the message was still in your phone's queue.
Sent from my SPH-D700 using xda premium
If you are on a MTD rom, someone in another thread suggested going back to regular swype. You can get the appropo files from the Starsky ROM, this is one of the few MTD roms that uses swype still, and the only files that I found work.
http://forum.xda-developers.com/showthread.php?t=1242335
system/app/swype.apk
system/lib/swypecore.so
I pushed using Root Explorer and got mine working again
The 'Android Update to EL30' is not removed by uninstalling system updates.apk that apk is meant to provision your Epic to Sprint. The Update Notification is caused by the 'Google Framework' Service. There may be ways to fool it, such as the buildprop edit suggested.
Sent from my piece of **** SPH-M910 using xda premium while my CM9 Alpha 4 Epic is resting in my pocket. (Very Handy) it's like having a spare battery but better.
USE AT OWN RISK
Download S-Voice - not modded apk
download and install like you would any other app
Fix S-Voice Network Error
After installing the S Voice app, use a root explorer app to edit your build.prop
Change...
ro.product.model= ( your Phone )
To
ro.product.model=GT-I9300
and also change
ro.product.device=GT-I9300
HowTo Manually Edit your build.prop File.
Open Root Explorer
Scroll down to your /system directory and tap on it.
At the top of the screen tap the button that says 'Mount R/W' (it will change to 'Mount R/O')
Long press on your build.prop file and select 'Open In Text Editor'.
Your build.prop file is now fully editable, please pay attention to what you are changing!
Make Changes
Hit back twice, Root Explorer will ask you to save it. Tap 'yes'.
Reboot
Root Explorer (File Manager) - Android Apps on Google Play
It works but what about everything you want it to do locks up? Set alarm..lock up. Maps, lock up. Lol does anything work?
sent from Transformer Prime cranking it out with WSG customs.
Scuddster said:
It works but what about everything you want it to do locks up? Set alarm..lock up. Maps, lock up. Lol does anything work?
sent from Transformer Prime cranking it out with WSG customs.
Click to expand...
Click to collapse
From what JC tested on Venum Ice, that's kind of what it only does... Lol
Sent from my SPH-D710 using xda premium
i used the command navigate to (Location)
and it worked
i believe the alarm part does not work cause it depends on the clock from gs3
you should try the modded apk then cause not having any of those issues with that apk.
but u have to force install that apk file by coping it to system and changing permissions
that is to hard for some people
Es file explorer, super manager are easy to use not hard at all
if you want to post the file link to the other apk and detailed instructions i will add it to op
is the link in the OP the modded apk?
no
changed post to reflect not modded apk
htls said:
changed post to reflect not modded apk
Click to expand...
Click to collapse
thats what im saying.. when modded apk is posted id try that. i had it but uninstalled already and didnt back it up. but it is good to have two options.. if its too hard to set permissions they can take your route .. i personally only used it to check weather lol.. and i did ask this:
Sent from my SPH-D710 using XDA
Beware anyone changing their build.prop. Some apps wont run like mobile odin and some other apps may not install, just saying. AND WHATS UP Rob. I hope you and your family are well man!!!
Sent from my SPH-D710
Will this work on gb, blazer 4.1?
your stupid fix ****ed up my phone. i rebooted it and now it only goes past the "boot" screen and goes black and that's it. it wont boot at all... just great! :0/.
draconx said:
your stupid fix ****ed up my phone. i rebooted it and now it only goes past the "boot" screen and goes black and that's it. it wont boot at all... just great! :0/.
Click to expand...
Click to collapse
You do know every thing we do in here is at your own risk. You could of said hey I am running blah blah blah rom and did the fix but it wont let my phone boot up. So that others reading this would know that there are even more risks... Jus' Sayin'
Hope you get back up and running
wow .. it works ... thanks buddy .. last day i installed SVoice but frustrated bcz it didnt work .. now it works ..
playya said:
You do know every thing we do in here is at your own risk. You could of said hey I am running blah blah blah rom and did the fix but it wont let my phone boot up. So that others reading this would know that there are even more risks... Jus' Sayin'
Hope you get back up and running
Click to expand...
Click to collapse
your right, i apologize, I'm on CM9 alpha 4. epic 4g touch. and i did this "fix" and it wouldn't let me boot my phone so i had to re insatll the CM9 rom through odin to get it to boot again.
try it out if you guys want but make sure you have odin and whatever rom your currently on.
draconx said:
your stupid fix ****ed up my phone. i rebooted it and now it only goes past the "boot" screen and goes black and that's it. it wont boot at all... just great! :0/.
Click to expand...
Click to collapse
Hahaha couldn't help but laugh. Playya is right OPs are not responsible for what happens to your phone.
Should I revert back to the old build.prop before flashing a different rom?
Edit: So I did some reading and figured it out. Sometimes it's better to look for the answer on ur own. Ignorance is not bliss!
This brief guide is to help others get Google Wallet working on AOSP based ROMs. There are guides already by Dafoxs and Antiochasylum but they are apparently for Samsung based ROMs and the lib files, etc are incompatible with AOSP based ROMs. Personally, I tried several times and the NFC setting kept getting wiped out so I had to do restores. These instructions are what ManelScout4Life posted and the thread is at his request. All the credit goes to the DEVs that made this possible - I am NOT a developer - Seriously... Lastly, the typical disclaimer applies - I take no responsibility for bricking your phone, etc. I highly recommend making a nandroid backup before any mod like this. These instructions worked on JellyBAM 3.2 compiled by ManeelScout4Life - http://forum.xda-developers.com/showthread.php?t=2069164
1) The lib files should not be modified like the posts for the SamSung based ROMs. However, you will need the modified Google Wallet .apk that is included in the zip you can download from their threads. I used the attached file that I downloaded from this thread - http://forum.xda-developers.com/showthread.php?t=2037372&highlight=google+wallet
2) I already had NFC enabled so ensure it is on in settings if you haven't already.
3) You need to modify /system/build.prop. I used Root Explorer (remember to change to RW) and you have to modify three lines. I made a copy of the existing build.prop before editing because you will revert to the existing file once complete to match your actual device.
3a) ro.product.model=Galaxy Nexus
3b) ro.product.name=yakju
3c) ro.product.device=maguro
4) I then rebooted before installing Google Wallet from the Play store. I then opened the app and performed the setup. The other guides mention getting FCs on NFC and to continue on but I never had any and the setup completed. YMMV.
5) Once the setup is complete with the version of the app from the store, you need to replace the app with the modified version that you downloaded in step 1. I used TB to force stop the app before I deleted it from /data/app.
6) I then use Root Explorer again to place the attached apk in /system/app (remember RW). I checked permissions and removed the group write check but again am not certain if that was necessary.
7) I then changed the build.prop.bak file to build.prop so it is back to before you started.
8) Reboot and hopefully it will work.
Hopefully, this helps and is clear.
Note: I see a prompt in the app shown in the attached pic but it will still work. It is really just a warning about a rooted device.
I pretty much did this, and it didn't work until I fixed permissions on the modded file that I moved to system/apps at the last step, like I saw in the YouTube video
Sent from my SGH-I317 using xda premium
capite said:
I pretty much did this, and it didn't work until I fixed permissions on the modded file that I moved to system/apps at the last step, like I saw in the YouTube video
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
So, I assume you removed the group write permission like I mentioned in step 6 and that fixed it for you? I assume it is the same video referenced in the link I have in step 1. The person checked permissions and removed that one check but he didn't say you had to. I did it anyway and maybe that is why it worked for me the first time that I followed the instructions I listed - from ManelScout4Life.
Thanks for this!
Sent from my Samsung Galaxy Note II
Yes
Sent from my SGH-I317 using xda premium
So, I assume you removed the group write permission like I mentioned in step 6 and that fixed it for you? I assume it is the same video referenced in the link I have in step 1. The person checked permissions and removed that one check but he didn't say you had to. I did it anyway and maybe that is why it worked for me the first time that I followed the instructions I listed - from ManelScout4Life.
told me to reset the app...and its hanging at 98%...thoughts?
If you reboot and check the "about device", does it show Galaxy Nexus before you even download the app?
Have you double checked the spelling on the other two lines?
What ROM and version are you on?
Sent from my SAMSUNG-SGH-I317 using xda premium
All I did was change name, model and device in build prop let me download and install and runs flawless no need for modified app
Sent from my Galaxy Nexus using xda premium
crisis187 said:
All I did was change name, model and device in build prop let me download and install and runs flawless no need for modified app
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I assume the reason for the modified app is for it to continue working after you change the build.prop back to an unsupported device. I guess on AOSP ROMs where S-pen apps don't work, then the proper build.prop isn't as important. You will lose access to external sd card possibly and other issues possibly.
Sent from my SAMSUNG-SGH-I317 using xda premium
I switched back the info seems to work still haven't fully tested yet
**EDIT
After installing multi window support to jelly bear ROM wallet force closes when trying to add account
Sent from my SGH-I317 using xda premium
How about if you complete the instructions above - adding the modded app, changing permissions, deleting the downloaded app, etc?
Sent from my SAMSUNG-SGH-I317 using xda premium
RichMD said:
If you reboot and check the "about device", does it show Galaxy Nexus before you even download the app?
Have you double checked the spelling on the other two lines?
What ROM and version are you on?
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
sorry for the delay...yes everything was spelled correctly, said Galaxy Nexus etc etc...I'm running CM10 by madmack...with it hanging i forced out, deleted pushed modded apk fixed perm and rebooted...opened the app and it hung on "setting up google wallet" for a good 15min...so i forced out and left it at that.
MonsterBandit said:
sorry for the delay...yes everything was spelled correctly, said Galaxy Nexus etc etc...I'm running CM10 by madmack...with it hanging i forced out, deleted pushed modded apk fixed perm and rebooted...opened the app and it hung on "setting up google wallet" for a good 15min...so i forced out and left it at that.
Click to expand...
Click to collapse
With the Galaxy Nexus build.Prop and Google wallet downloaded from the store, the setup needs to complete before you move to the next steps of reverting the build.prop and pushing the modded app. Those steps are to keep the app working without having issues due to a Galaxy Nexus build.prop. I would delete the app, and start over. I assume you never got an email stating you activated wallet.
Sent from my SAMSUNG-SGH-I317 using xda premium
Also, did you ever use the steps/zip posted by dafoxs or the other thread (forgot the name)? If so, your NFC setting might be gone or you have incompatible lib files, etc. I would revert to the nandroid backup if you made one before following those procedures which are for Samsung based ROMs rather than AOSP/CM10
Sent from my SAMSUNG-SGH-I317 using xda premium
crisis187 said:
I switched back the info seems to work still haven't fully tested yet
**EDIT
After installing multi window support to jelly bear ROM wallet force closes when trying to add account
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
Wait. You installed multi window support on jelly beer!?
ManelScout4Life said:
Wait. You installed multi window support on jelly beer!?
Click to expand...
Click to collapse
LOL!
Modified build.prop and now my phone won't turn on. Any help?
---------- Post added at 02:37 PM ---------- Previous post was at 02:30 PM ----------
Took out battery, replaced it. Boot to recovery and restored Nandroid. Not sure what went wrong but I think I'll give up hopes of Google Wallet. Made me a little skiddish now.
This method of getting Google Wallet appears to break both Google Now and video output on cm10.1 variants that are running the open source audio hal.
Google Now goes into the 'Didn't catch that, retry?' Loop.
Steps to reproduce:
Install cm10.1 later than 01/26/2013
Allow it to boot and stabilize.
Setup Google Now.
Modify build.props to reflect Galaxy Nexus, yakju, maguro as dictated in OP.
Reboot.
Google Now will now have the 'Didn't catch that' error if you attempt voice recognition.
Sent from my "berry", spelling may vary.
bofhemeritus said:
This method of getting Google Wallet appears to break both Google Now and video output on cm10.1 variants that are running the open source audio hal.
Google Now goes into the 'Didn't catch that, retry?' Loop.
Steps to reproduce:
Install cm10.1 later than 01/26/2013
Allow it to boot and stabilize.
Setup Google Now.
Modify build.props to reflect Galaxy Nexus, yakju, maguro as dictated in OP.
Reboot.
Google Now will now have the 'Didn't catch that' error if you attempt voice recognition.
Sent from my "berry", spelling may vary.
Click to expand...
Click to collapse
Thanks,
I can't confirm this works on 10.1 (Android 4.2.x) - only confirmed on 4.1.x even though I expect Google Now, etc will be fine after reverting your build.prop. I'm "assuming" Google Wallet will work as indicated in these steps but Google Now, etc may have problems while the bulld.prop stilll indicates the wrong device - temporary until your wallet is working.
However, were you able to get Google Wallet to setup properly?
If you did get it working, did you try changing the build.prop back to original? I don't know if that would solve the Google Now but your steps listed don't indicate that you finished reverting the build.prop.
Please reply with your results for others.
Hello -
I did actually revert the build.props file to the original settings, and Google Now continued to give the same error. I'm about to test it without opening Google now until after the revert and reboot.
Thanks for your help!
If you like my work, donate to the Juvenile Diabetes Research Fund.
Question is, can someone modify the apk as below???
http://www.androidpolice.com/2013/0...-enable-voice-prompt-in-search-results-video/
Turns out, there's a secret flag within Search that lets you use the hotword, set by default to 'Google,' anywhere in search results instead of just the home Activity. By default, Search will let you say "Google" to activate voice input only in the main Search screen, after which you'd have to tap the Back button in order to use it again. It's nice, but it's not very fluid, as you have to keep touching your device.
The secret flag enables it in search results, so you can perform search after search after search without ever touching your phone or tablet.
As for the technical details, the flag is located in res/values/bools and is called hotword_from_results. To activate it, one would flip it from false to true, like so:
<bool name="hotword_from_results">true</bool>
Sent from my Nexus 4 using xda app-developers app
Wezi said:
Question is, can someone modify the apk as below???
http://www.androidpolice.com/2013/0...-enable-voice-prompt-in-search-results-video/
Turns out, there's a secret flag within Search that lets you use the hotword, set by default to 'Google,' anywhere in search results instead of just the home Activity. By default, Search will let you say "Google" to activate voice input only in the main Search screen, after which you'd have to tap the Back button in order to use it again. It's nice, but it's not very fluid, as you have to keep touching your device.
The secret flag enables it in search results, so you can perform search after search after search without ever touching your phone or tablet.
As for the technical details, the flag is located in res/values/bools and is called hotword_from_results. To activate it, one would flip it from false to true, like so:
<bool name="hotword_from_results">true</bool>
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I decompiled, made the above changes, recompiled with no errors, and got it to install but it force closes every time i try to open it. Maybe someone else can provide some insight. I used AutoAPKTool to make the edits
Cans someone resolve this? I'd do it myself but having tons of trouble getting my device to show on adb (after many tries, different methods)
I tried to make an Xposed module to patch it on the fly, but it is not working:
Code:
resparam.res.setReplacement("com.google.android.googlequicksearchbox", "boolean", "hotword_from_results", true);
upon starting the module, I get "Resource$NotFoundException", I tried other forms of the setReplacement method but none worked. I am still new to Xposed, so maybe I am doing this in a wrong way, attached are the sources of the Eclipse project in case someone can make it work.
If someone have the source of google now apk i can do something
I don't know if it's available, or also can be made from decompiling and recompile
firetrap said:
If someone have the source of google now apk i can do something
I don't know if it's available, or also can be made from decompiling and recompile
Click to expand...
Click to collapse
no you dont need source, just decompile. change the value, recompile. replace it
done.
Yes I know it's just iam working right now in my app and for me it's much easier to have the source I only had to import to eclipse than playing with apk tool etc in a few hours I will do that
Sent from my Nexus 4 using xda app-developers app
firetrap said:
Yes I know it's just iam working right now in my app and for me it's much easier to have the source I only had to import to eclipse than playing with apk tool etc in a few hours I will do that
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
you dont need to import to eclipse, all you do is just decompile it and change false to true.
you're making it so complicated on your part. i already did it, going to test it now it literally takes 30-45 seconds to do.
zephiK said:
you dont need to import to eclipse, all you do is just decompile it and change false to true.
you're making it so complicated on your part. i already did it, going to test it now it literally takes 30-45 seconds to do.
Click to expand...
Click to collapse
Yes but i was in the company desktop and here i don't have acess to apktool just because my company restricts the download site as dev host rapid share etc. now at home i had decompiled changed from false to true and recompiled and signed etc etc.. so i tested and the behaviour is the same are you guys sure that it's only change to do?! i think i had all perfect if you want i can upload the "modded apk"
EDIT: it doesn't work i don't know why here is the decompiled files and its true, i recompile sign and check manifest and all ok, but after install the behavior its the same
https://mega.co.nz/#!KZlVkIgS!FVLyrUXwtI4w5NHX22u7bWMcWZpEr5-7SydfU_fYX6M
Here the recompiled file i made you can test:
https://mega.co.nz/#!yJUjmYCC!fancLR6DwIlQHxYmX9JmNzCJEPBmpLgkIFsTFw4e_jw
Maybe the guy from the "30-45" seconds have more time to debugg this
I just modded this and got it running w/o issue.
I'm on CM 10.2 so I had to do some adjusting as there was an update installed to /data/app, with the original in /system/app.
I just uninstalled the update via the Play Store, and then moved the original (for CM it's QuickSearchBox.apk to QuickSearchBox.apk.bak), and adb pushed the newly modded apk (attached), to /system/app.
After doing all that, BOOM goes the dynamite.
Works for me, YMMV.
Hotword Quick Search
JsChiSurf said:
I just modded this and got it running w/o issue.
I'm on CM 10.2 so I had to do some adjusting as there was an update installed to /data/app, with the original in /system/app.
I just uninstalled the update via the Play Store, and then moved the original (for CM it's QuickSearchBox.apk to QuickSearchBox.apk.bak), and adb pushed the newly modded apk (attached), to /system/app.
After doing all that, BOOM goes the dynamite.
Works for me, YMMV.
Hotword Quick Search
Click to expand...
Click to collapse
Any way to do this without using ADB? (Having tons of trouble getting my SGS3 to be recognized). Tried installing the apk by itself but the installation fails.
trein91 said:
Any way to do this without using ADB? (Having tons of trouble getting my SGS3 to be recognized). Tried installing the apk by itself but the installation fails.
Click to expand...
Click to collapse
Are you rooted? I needed to make this a system app, as mentioned, to avoid signature conflicts, etc.
If so, I can make a zip to install to /system/app for you. I don't think it will work (as you have discovered), if you try and install as a standard app to /data/app, which is what clicking the download link and attempting to install is doing.
JsChiSurf said:
Are you rooted? I needed to make this a system app, as mentioned, to avoid signature conflicts, etc.
If so, I can make a zip to install to /system/app for you. I don't think it will work (as you have discovered), if you try and install as a standard app to /data/app, which is what clicking the download link and attempting to install is doing.
Click to expand...
Click to collapse
Please make a flashable zip, would love to try it
Sent from my Nexus 4 using xda app-developers app
OK. So I didn't have any files in data/app so I went ahead and just made quixksearchbox a .bak, and pushed new one after renaming it and setting permissions. Its working great.
I'm on PA
Sent from my Nexus 4 using Tapatalk 4
Here's a flashable zip. Though, because it has to place the APK in the /system/ folder (partition), the zip (out of the box), is only likely to work on the Nexus 4, since mount points are going to differ by phone. Any other phone you'll have to modify the script.
As mentioned previously, if you want to try and flash, FIRST, be sure to uninstall 'Google Search' from the play store.
Since I don't think there is a way to move a file in edify, and I'm too lazy to include a shell script to run a move command, I instead delete QuickSearchBox.apk if it is in your /system/app/ folder (instead of backing it up if you want to restore later), and then copy over qs.apk (the modded version).
I restored to original, ran the above process on CM 10.2, and got the results expected / desired (i.e. the attached zip is confirmed working in my setup).
It works on PA 3.99. However you'll need to set voice to US English or it won't work.
Sent from my Nexus 4 using Tapatalk 2
Anon87 said:
It works on PA 3.99. However you'll need to set voice to US English or it won't work.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Would be nice if this could be activated with any language.
Is it possible by changing any other flag?
JsChiSurf said:
Are you rooted? I needed to make this a system app, as mentioned, to avoid signature conflicts, etc.
If so, I can make a zip to install to /system/app for you. I don't think it will work (as you have discovered), if you try and install as a standard app to /data/app, which is what clicking the download link and attempting to install is doing.
Click to expand...
Click to collapse
Good Afternoon,
I am getting FCs after flashing the app. I am using a stock rooted ROM
I removed Google Search< restarted the phone<verify Googgle search was removed< flashed zip<rebooted phone<open app<set up account<FCs
anyone got a suggestion to get it working,
Lento10 said:
Good Afternoon,
I am getting FCs after flashing the app. I am using a stock rooted ROM
I removed Google Search< restarted the phone<verify Googgle search was removed< flashed zip<rebooted phone<open app<set up account<FCs
anyone got a suggestion to get it working,
Click to expand...
Click to collapse
Is the ROM odexed?
jarjar124 said:
Is the ROM odexed?
Click to expand...
Click to collapse
Deodex stock rom
Sent from my Nexus 4 using XDA Premium 4 mobile app
OK, so this may not even be the result of running a custom rom because it hasn't worked with any of them. When I click on Voicemail which isn't setup yet by the way, all it does is send me to my messaging app. It gives me no options to set it up, or check voicemail.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Running bonestock 1.0a
tygray6 said:
OK, so this may not even be the result of running a custom rom because it hasn't worked with any of them. When I click on Voicemail which isn't setup yet by the way, all it does is send me to my messaging app. It gives me no options to set it up, or check voicemail.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Running bonestock 1.0a
Click to expand...
Click to collapse
I removed the Visual Voicemail application. It can be added back.
The icon for Visual Voice mail is tied to the Messaging app.
I need to edit the messaging app to rid that icon. for now just use the feature to "hide" it in the app drawer.
of it you want the app, pull it outta the bloat.zip
Okay, thanks
Sent from my HTC6500LVW using XDA Premium 4 mobile app
OK, so I downloaded the bloat zip and extracted the vvm.apk it gives me the install option but says install failed every time. Any ideas?
Sent from my HTC6500LVW using XDA Premium 4 mobile app
tygray6 said:
OK, so I downloaded the bloat zip and extracted the vvm.apk it gives me the install option but says install failed every time. Any ideas?
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
are you using my empty flashable.zip..?
just pull vvm.apk and put in system/app
Once I get my phone back, and or you have S-OFF this won't be an issue.
Aroma will solve a lot of these types of issues as well.
Okay, I put it in place of the null file in the app folder in your flashable zip and after re zipping it it failed when flashing
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Don't unzip then rezip. Use a tool like 7zip and drop it into the zip. It failed because by unzipping, you broke the signature
Sent from my HTC6500LVW using Tapatalk 4
If I've helped, please hit the thanks button
tylerlawhon said:
Don't unzip then rezip. Use a tool like 7zip and drop it into the zip. It failed because by unzipping, you broke the signature
Click to expand...
Click to collapse
exactly what Ty said.
I am expecting my phone back today, and my first project is Aroma..
so bare with me.. (not you Ty)
I will be getting the ROM to where I am comfortable with calling it a full non beta release.
Only reason it's beta is because I don't have Aroma set up yet, once that is set up, it's game on.
you will be able to re-flash the ROM.zip pick "MOD only" and then select JUST the .apk you want (NO you can't remove apps, use root explorer for that, I think S-OFF takes away write protection but I have no idea yet, if not, then, well, we will need to get used to that .zip that deletes files (it's quite easy, once you try it out and everything)
andybones said:
exactly what Ty said.
I am expecting my phone back today, and my first project is Aroma..
so bare with me.. (not you Ty)
I will be getting the ROM to where I am comfortable with calling it a full non beta release.
Only reason it's beta is because I don't have Aroma set up yet, once that is set up, it's game on.
you will be able to re-flash the ROM.zip pick "MOD only" and then select JUST the .apk you want (NO you can't remove apps, use root explorer for that, I think S-OFF takes away write protection but I have no idea yet, if not, then, well, we will need to get used to that .zip that deletes files (it's quite easy, once you try it out and everything)
Click to expand...
Click to collapse
I forgot to come back and post a thank you, it worked great after I placed the apk into the zip and flashed. By the way, I've run every rom available now for the phone and keep coming back to yours, I appreciate your work.
Sent from my One using XDA Premium 4 mobile app
tygray6 said:
I forgot to come back and post a thank you, it worked great after I placed the apk into the zip and flashed. By the way, I've run every rom available now for the phone and keep coming back to yours, I appreciate your work.
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey man thank you very much, it really does mean a lot to me!
and you're very welcome
andybones said:
I removed the Visual Voicemail application. It can be added back.
The icon for Visual Voice mail is tied to the Messaging app.
I need to edit the messaging app to rid that icon. for now just use the feature to "hide" it in the app drawer.
of it you want the app, pull it outta the bloat.zip
Click to expand...
Click to collapse
Have you had any luck ridding the VVM icon and whatever else from the messaging app yet. I had a nasty issue related to the new VVM.
I will spell it out here in case anyone else has this issue.
So i like always update my phone when updates come out.
The new VVM has some addition network elements tied to it on the back-end.
Long story short this 443 update has created randomly dropping my mobile connection. I tried re flashing the radios, the stock rom, going back one radio version, etc. I mentioned this in a post in this thread:
http://forum.xda-developers.com/verizon-htc-one/help/wifi-bluetooth-mobile-data-wont-off-t2883253
I don't believe it is anything we have done in here, but the issue was with exclusively mobile data where it would disconnect but still show 4g, anyways back to the VVM
I had to revert to 442 stock rom as it didn't have the disconnecting issue
Since i already ran the newest 443 VVM app with those additional features, the 442 VVM fails with error code 2004 when on a 442 ROM
So i had to be coy when calling VZW to get them to reset this. Lucky they didn't ask SW/HW versions, so basically they had ' reset the network elements ' associated with the newest version. WORKED!
So if this happens to you , all i said was it came down as an update, i didn't like it, and reverted back and now it does not work, etc.... I tried to find the newest update again but cant find it.
I was wondering how the VVM icon still there after removing the APK, that answers that. I tried to load the newest VVM on 442, and epic fail lolz
Just providing some info for everyone
carm01 said:
Have you had any luck ridding the VVM icon and whatever else from the messaging app yet. I had a nasty issue related to the new VVM.
I will spell it out here in case anyone else has this issue.
So i like always update my phone when updates come out.
The new VVM has some addition network elements tied to it on the back-end.
Long story short this 443 update has created randomly dropping my mobile connection. I tried re flashing the radios, the stock rom, going back one radio version, etc. I mentioned this in a post in this thread:
http://forum.xda-developers.com/verizon-htc-one/help/wifi-bluetooth-mobile-data-wont-off-t2883253
I don't believe it is anything we have done in here, but the issue was with exclusively mobile data where it would disconnect but still show 4g, anyways back to the VVM
I had to revert to 442 stock rom as it didn't have the disconnecting issue
Since i already ran the newest 443 VVM app with those additional features, the 442 VVM fails with error code 2004 when on a 442 ROM
So i had to be coy when calling VZW to get them to reset this. Lucky they didn't ask SW/HW versions, so basically they had ' reset the network elements ' associated with the newest version. WORKED!
So if this happens to you , all i said was it came down as an update, i didn't like it, and reverted back and now it does not work, etc.... I tried to find the newest update again but cant find it.
I was wondering how the VVM icon still there after removing the APK, that answers that. I tried to load the newest VVM on 442, and epic fail lolz
Just providing some info for everyone
Click to expand...
Click to collapse
Foolish me, this is so very simple, I just forgot that you have to do it on a 100% clean flash, you can't use a flashable.zip as it is an .xml system edit.
system/customize/resource/allapplication.xml
basically you edit this .xml just search for "voicemail"
you will find this line of code
Code:
<item type="application" packageName="com.htc.sense.mms" className="com.htc.sense.mms.ui.VoiceMailTabActivity" display_order="200" display_hide="[B][COLOR="Red"]0[/COLOR][/B]" />
change it to
Code:
<item type="application" packageName="com.htc.sense.mms" className="com.htc.sense.mms.ui.VoiceMailTabActivity" display_order="200" display_hide="[B][COLOR="Red"]1[/COLOR][/B]" />
to be quite honest though to save yourself A LOT of time, just hit the menu button in app drawer click hide apps and hide it, that is what this MOD does anyway...
andybones said:
Foolish me, this is so very simple, I just forgot that you have to do it on a 100% clean flash, you can't use a flashable.zip as it is an .xml system edit.
system/customize/resource/allapplication.xml
basically you edit this .xml just search for "voicemail"
you will find this line of code
Code:
<item type="application" packageName="com.htc.sense.mms" className="com.htc.sense.mms.ui.VoiceMailTabActivity" display_order="200" display_hide="[B][COLOR="Red"]0[/COLOR][/B]" />
change it to
Code:
<item type="application" packageName="com.htc.sense.mms" className="com.htc.sense.mms.ui.VoiceMailTabActivity" display_order="200" display_hide="[B][COLOR="Red"]1[/COLOR][/B]" />
to be quite honest though to save yourself A LOT of time, just hit the menu button in app drawer click hide apps and hide it, that is what this MOD does anyway...
Click to expand...
Click to collapse
I will give this a try sometime; kudos