Develop Bugs

[Q] 2 problems: System Update and Swype

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.

Making VVM work with ports AOSP and Sense

Ok guys here is the steps to get VVM to work:
Download https://www.box.com/shared/p24yjznt25ls8tucc0n7
vvm apk do not install yet
Open root explorer
Go to system / build prop
Open with text editor ( make system r/w)
Find line that says (ro.Horizontalvvm = true
Change "true" to false
Save edits
Reboot
Once rebooted install VVM. Have wifi off when installing.
Under VVM settings set storage to external.
I got a few fc's when the first down load came through then it stated working great.
Sent from my ADR6350 using xda premium

The steps are appreciated, but it installs and works for me without doing this, for some reason. I have to use my PC to download the APK, but after that it's fine.
Sent from my Incredible 2 using Tapatalk

Thanks for this information. I've always known about editing both true/false values in the build.prop for Verizon Backup Assistant and Visual Voicemail, but I have never had much luck getting the various .apks I found to install. This .apk actually installs fine, which is nice and greatly appreciated; however, I wish it was at least the same version as the VVM that comes stock on the Incredible 2. This version is pretty basic, which still makes me lean towards using Google Voice as an alternative when running ROMs that don't include VVM.
Thanks again zax10!

ScallywagginIT said:
Thanks for this information. I've always known about editing both true/false values in the build.prop for Verizon Backup Assistant and Visual Voicemail, but I have never had much luck getting the various .apks I found to install. This .apk actually installs fine, which is nice and greatly appreciated; however, I wish it was at least the same version as the VVM that comes stock on the Incredible 2. This version is pretty basic, which still makes me lean towards using Google Voice as an alternative when running ROMs that don't include VVM.
Thanks again zax10!
Click to expand...
Click to collapse
You are welcome. I agree about the simplicity of the VVM apk. It is from a MOTO device. I have tried the original from my inc2 but it messes up everytime.
To the OP who stated he installed and ran with out editing build.prop. what Rom are you running?
Sent from my ADR6350 using xda premium

zax10 said:
You are welcome. I agree about the simplicity of the VVM apk. It is from a MOTO device. I have tried the original from my inc2 but it messes up everytime.
To the OP who stated he installed and ran with out editing build.prop. what Rom are you running?
Sent from my ADR6350 using xda premium
Click to expand...
Click to collapse
It was working in Condemned CM7. I'm trying out Virtuous Affinity now, and it doesn't work without this trick. Condemned must have a build.prop modification built in.
EDIT: For those who like to switch ROMs, here's another trick. Once you have VVM working in one ROM, make a backup with TiBU. When you wipe user data or switch ROMs, you can restore the app with data, without changing build.prop. VVM "remembers" checking build.prop before the backup, and will not check again.
2nd EDIT: Doesn't work every time.

What if those lines are in the build prop? should i add the lines myself???

TweakedSystems said:
What if those lines are in the build prop? should i add the lines myself???
Click to expand...
Click to collapse
Won't hurt. Certainly worth the trying IMO.

[GUIDE] How to get a working Google Wallet

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.

[Q] Synergy rom T-999

Need help! caller ID voice mail not working.. +1added to all numbers.

1totalpro1 said:
Need help! caller ID voice mail not working.. +1added to all numbers.
Click to expand...
Click to collapse
maybe thats something that you should post in the ROM's thread or search

He has less than 10 posts...
Need more info Op. When did it start? Flash any mods or themes? Make any changes? Install any apps recently?
And I do recommend searching the thread, even if you can't post there. Could be a known issue that's been solved already.
Sent from my SGH-T999 using xda premium

Synergy rom SGH -T999
DocHoliday77 said:
He has less than 10 posts...
Need more info Op. When did it start? Flash any mods or themes? Make any changes? Install any apps recently?
And I do recommend searching the thread, even if you can't post there. Could be a known issue that's been solved already.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Thanks! yes to all
Previous rom Universe s4. The mane thing I was trying to do was to Get the Mod DriveLink up and running.
I switched back to synergy because I couldn't get it to work on the s4 rom. I Had Drivelink working on Synergy
but Flashed to s4 because of caller ID and voice mail issues. now tmserver not working and drive link not working
on synergy rom along with caller Id & voice mail.

Ok, synergy if I'm not mistaken is kind of a FrankenDroid build. It has parts taken from the S3, Note2, and S4 I think. This is likely the cause. Your data wouldn't work with some of the apps on the other rom causing confilcts and bugs. Then when you flashed back, you now had data that has been manipulated by two different roms built from different sources.
Unfortunately I believe the best way to fix this is a factory reset. Or if you have a nandroid of your system and data from before you flashed you can just restore that.
Otherwise, boot into twrp or cwm and choose factory reset. This will wipe all apps and app data setting you back to a fresh rom install. If you have backups from Titanium backup or similar app, you can try to restore your data that way.
If you factory reset from stock recovery it will also wipe your internal sdcard.
Another option would be to find each offending app in App Management and clear data, then reboot. Youll only lose those apps data, but if you miss any it could cause future problems.
Of course, you are more than welcome to get a second opinion, but I'm pretty sure this is what's going to have to happen.
But again, if you have a nandroid, restore it and all should be good again.
Sent from my SGH-T999 using xda premium

Synergy rom SGH -T999
DocHoliday77 said:
Ok, synergy if I'm not mistaken is kind of a FrankenDroid build. It has parts taken from the S3, Note2, and S4 I think. This is likely the cause. Your data wouldn't work with some of the apps on the other rom causing confilcts and bugs. Then when you flashed back, you now had data that has been manipulated by two different roms built from different sources.
Unfortunately I believe the best way to fix this is a factory reset. Or if you have a nandroid of your system and data from before you flashed you can just restore that.
Otherwise, boot into twrp or cwm and choose factory reset. This will wipe all apps and app data setting you back to a fresh rom install. If you have backups from Titanium backup or similar app, you can try to restore your data that way.
If you factory reset from stock recovery it will also wipe your internal sdcard.
Another option would be to find each offending app in App Management and clear data, then reboot. Youll only lose those apps data, but if you miss any it could cause future problems.
Of course, you are more than welcome to get a second opinion, but I'm pretty sure this is what's going to have to happen.
But again, if you have a nandroid, restore it and all should be good again.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Thanks Doc! I started over with super wipe through Synergy flash everything works including drivelink-r3,except for caller ID invalid mms code.
Tmobile SGH-T999
4.1.2
Base Band. T999UVDMD5
Kernel. stalk
SynergyROM(r484)

1totalpro1 said:
Thanks Doc! I started over with super wipe through Synergy flash everything works including drivelink-r3,except for caller ID invalid mms code.
Tmobile SGH-T999
4.1.2
Base Band. T999UVDMD5
Kernel. stalk
SynergyROM(r484)
Click to expand...
Click to collapse
Ok, so Voice Mail is working now and its not adding +1 to the numbers anymore? And you said caller ID invalid mms code is the problem. What exactly is it doing? Is "invalid mms code" an error message or somthing like that? Did you mean "invalid mmi code"?
Try this,
Go into Application Management and find and select T-Mobile Name ID, then press Disable. See if that helps. If not try it after a reboot and let me know.

Synergy rom SGH -T999
DocHoliday77 said:
Ok, so Voice Mail is working now and its not adding +1 to the numbers anymore? And you said caller ID invalid mms code is the problem. What exactly is it doing? Is "invalid mms code" an error message or somthing like that? Did you mean "invalid mmi code"?
Try this,
Go into Application Management and find and select T-Mobile Name ID, then press Disable. See if that helps. If not try it after a reboot and let me know.
Click to expand...
Click to collapse
Thanks Doc!
Application manager /all . T -Molbile Account. Is that what your referring too? I'm not finding the tmo name ID.
Also I need to clarify. I can work around and call vioce mail with #123# code or just call my self. On the phone home screen when I push the voice mail icon it diles +1then I get recording check the number massage CA84o51. When I recieve calls caller ID shows &%7768%&%&^ it differs depending on who calls.everything els works clear calls, apps, blue-tooth, WiFi .

From the dialer press menu, Call Settings, then scroll down and see if you can access Voicemail settings. You may be able to change the number there. Otherwise it may be a csc file providing that info.
For caller Id, it dounds like the same thing a number of people reported in the rom thread. The solution was to disable a caller id app if om remembering right. I don't think the tmobile account app would do it but you can try. Look through the listed apps to see if you find something like that though.
Sent from my SGH-T999 using xda premium

Synergy rom SGH -T999
DocHoliday77 said:
From the dialer press menu, Call Settings, then scroll down and see if you can access Voicemail settings. You may be able to change the number there. Otherwise it may be a csc file providing that info.
For caller Id, it dounds like the same thing a number of people reported in the rom thread. The solution was to disable a caller id app if om remembering right. I don't think the tmobile account app would do it but you can try. Look through the listed apps to see if you find something like that though.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Thanks Doc! It was Google voice or skype going to try it hope it works.

[Request] Secret Flag Modified Google Search Apk

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