Related
I'm on ConROM v4 (Senseless), and I just got Google Now partially working on my Rezound. The search works by typing but trying to use voice keeps crashing.
No guarantees, but here's what I did:
1. Downloaded the apk here
2. Used Titanium Backup to uninstall Google Search.
3. Removed the Search Bar widget from my homescreen.
4. Install the apk. Reboot
5. Add the search widget back.
6. It's ask to Authorize to your account twice. Agree to both.
7. Use the text search widget. Trying the microphone crashes the app.
Curious if the geniuses here can get voice working.
More Information here and here
khart1978 said:
I'm on ConROM v4 (Senseless), and I just got Google Now partially working on my Rezound. The search works by typing but trying to use voice keeps crashing.
No guarantees, but here's what I did:
1. Downloaded the apk here
2. Used Titanium Backup to uninstall Google Search.
3. Removed the Search Bar widget from my homescreen.
4. Install the apk. Reboot
5. Add the search widget back.
6. It's ask to Authorize to your account twice. Agree to both.
7. Use the text search widget. Trying the microphone crashes the app.
Curious if the geniuses here can get voice working.
More Information here and here
Click to expand...
Click to collapse
I can confirm that it works on SlimROM 1.6
Be interesting to see if we can get voice working. With dev's dropping left and right, I can only hope.
There's a few threads elsewhere on XDA about it, one way involves doing build.prop edits, voice is still screwed across the board though.
Sent from my Galaxy Nexus using Tapatalk 2
My guess is the voice component requires the newer API, but it could also just be Sense screwing things up...
a.mcdear said:
My guess is the voice component requires the newer API, but it could also just be Sense screwing things up...
Click to expand...
Click to collapse
That's not the problem. There are build.prop editing threads that change the devices api version, but voice is still shot.
AshtonTS said:
That's not the problem. There are build.prop editing threads that change the devices api version, but voice is still shot.
Click to expand...
Click to collapse
That's because you're not really changing the API at all, just what version it reports. Making it show a higher number does not actually mean your device supports the higher API version!
You can change the version string to make Gingerbread report as Android 4.1 - again, this will not actually bring any Android 4.1 features to gingerbread.
For those that have not seen this, the newly released Wallet will work on our phone with no hacking necessary:
http://www.androidcentral.com/updated-google-wallet-app-coming-all-us-based-android-phones
I haven't made a purchase yet but it seems to be running fine on rooted ME7. Watch out. I have noticed that the pin expiration default timeout is set to 1 day. It used to be 5 minutes!
skiddingus said:
For those that have not seen this, the newly released Wallet will work on our phone with no hacking necessary:
http://www.androidcentral.com/updated-google-wallet-app-coming-all-us-based-android-phones
I haven't made a purchase yet but it seems to be running fine on rooted ME7. Watch out. I have noticed that the pin expiration default timeout is set to 1 day. It used to be 5 minutes!
Click to expand...
Click to collapse
Nope! The app will install on almost anything now. The problem is Tap to Pay won't. Go into settings and click about and it says Tap to Pay and underneath it will say unavailable or not supported or something like that. I already uninstalled it. Waiting for a work around
I been trying to update the app the proper way as I'm still on MDK by changing the build.prop but for some unknown reason after I change the build.prop and reboot I get the samsung custom unlocked screen then the dreaded black screen. Can't figure out why this is happening. Permissions are set to rw - r- - r- -. If anyone can help me with this it would be greatly appreciated! I don't want to update directly and lose my NFC pay abilities. Thanks!
Sent from my SCH-i545 using RedBull & Viagra.
I took the update on my Galaxy Note II (Sprint), and my Wallet has gone from unsupported, but functional, to "Unrecoverable error -- Falied to upgrade your device PIN to the new PIN system. Please reset Wallet." Of course resetting Wallet, or even reinstalling keeps on coming up with the same error.
I just learned that the "tap to pay" reads "not available" in the settings->about menu. (thanks jimmypop13) It appears that we have received a neutered version of Wallet. What a bunch of crap. Maybe the hacked version is still the only way to make a purchase. I wonder what would have happened if I would have modified my build prop to a Nexus, install Wallet, and then change the build prop back. Maybe the new Wallet doesn't check after the install and it would work.
skiddingus said:
I just learned that the "tap to pay" reads "not available" in the settings->about menu. (thanks jimmypop13) It appears that we have received a neutered version of Wallet. What a bunch of crap. Maybe the hacked version is still the only way to make a purchase. I wonder what would have happened if I would have modified my build prop to a Nexus, install Wallet, and then change the build prop back. Maybe the new Wallet doesn't check after the install and it would work.
Click to expand...
Click to collapse
If you try that let me know if it works. I was gonna try that but my phone wouldn't boot after changing build.prop for some reason.
Sent from my SCH-i545 using RedBull & Viagra.
iwearthebelt said:
If you try that let me know if it works. I was gonna try that but my phone wouldn't boot after changing build.prop for some reason.
Sent from my SCH-i545 using RedBull & Viagra.
Click to expand...
Click to collapse
Changing the build prop doesn't work, unfortunately if you want to use tap to pay well have to wait for a fix. I Uninstalled the update and reverted to the hacked version where tap to pay works.
dseda86 said:
Changing the build prop doesn't work, unfortunately if you want to use tap to pay well have to wait for a fix. I Uninstalled the update and reverted to the hacked version where tap to pay works.
Click to expand...
Click to collapse
+1
Hey everyone this is how you can get the latest wallet working. Hit the thanks button for this guy! Success! http://forum.xda-developers.com/showthread.php?p=45690695
I have an unroofed s4 wallet working great just installed apk voila
Sent from my SCH-I545 using XDA Premium 4 mobile app
I remember from my Gnex days that you had to be sure to reset the Google wallet app before updating/resetting/flashing a new ROM. If you failed to do so, it broke the secure element and you were pretty much screwed... Hopefully that's not the case for any of you having trouble.
I can tell you that I have it updated and working just fine on my VZW S4. Rooted and running the Google Edition ROM 5.9 (port from i9505) from the development thread. Status says tap to pay is active. Took it down to the gas station, bought a 6 pack and used my phone to pay.
Hey I FINALLY got tap to pay working with the new wallet on cm10.2. I had to install the new modified apk from http://forum.xda-developers.com/showpost.php?p=45699789&postcount=3244. You just need the modified wallet apk, cm already had the correct nfc libs. ALSO, I had to edit my build.prop to the galaxy nexus one where product.model is galaxy nexus, Product name is yakju, and product.device is maguro. Then I rebooted and wiped wallet and when I opened, i clicked settings, change account and it wiped the app, then picked my email again and finally tap to pay showed up AND finished setting up . Without changing my build.prop the tap to pay setup always failed. I just changed my build.prop back after setting it all up and it still seems to be working
jimmypop13 said:
Hey I FINALLY got tap to pay working with the new wallet on cm10.2. I had to install the new modified apk from http://forum.xda-developers.com/showpost.php?p=45699789&postcount=3244. You just need the modified wallet apk, cm already had the correct nfc libs. ALSO, I had to edit my build.prop to the galaxy nexus one where product.model is galaxy nexus, Product name is yakju, and product.device is maguro. Then I rebooted and wiped wallet and when I opened, i clicked settings, change account and it wiped the app, then picked my email again and finally tap to pay showed up AND finished setting up . Without changing my build.prop the tap to pay setup always failed. I just changed my build.prop back after setting it all up and it still seems to be working
Click to expand...
Click to collapse
I couldn't get the APK to install the normal way ("App not installed" errors), so I manually pushed it to /system/app and it claims Tap to Pay is ready. Gonna try it out tonight.
Thanks for pointing this out...all set now on a rooted, stock VZW S4.
Sent from my SCH-I545 using xda app-developers app
if you have concern about the tap to pay function go to settings/about and look at tap to pay and see what it says. i had to use the install app for me7 rooted then update and all works good i just left my build prop the way it is and didnt change it back to stock after the mod
Sent from my Galaxy Nexus using Tapatalk 4
ogrekane313 said:
if you have concern about the tap to pay function go to settings/about and look at tap to pay and see what it says. i had to use the install app for me7 rooted then update and all works good i just left my build prop the way it is and didnt change it back to stock after the mod
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
If I'm not mistaken if you leave your build prop with another phone in there the play store will not show apps available for your phone but the one listed in your build prop. That may not matter to you but I thought I'd get that out to you in case you didn't know.
Sent from my SCH-I545 using xda app-developers app
I'm trying to install Kik Messenger twice. I have two accounts and don't like to log out because I lose all of my conversation history. I'm currently using Titanium backup's profile feature, which is a very nice fix, but it's still a pain having to switch back and forth between profiles. I might be looking for "perfect" when perfect doesn't exist. I am completely new to modding apks and Android in general, all of my work on this so far has been "trial and error". Anyways, here's what I have:
I have the Google Play version of Kik installed on my phone. I have taken that app and modified the package name successfully using apktool. However, when I try to install, I get an error saying something about duplicate provider authority. So I did some research and learned that I'm supposed to edit this part of the AndroidManifest. So I have played around with that a little bit and after I change the authorities, I am able to install the modded app. However, it crashes immediately.
Does anyone know how to fix this problem with the provider/authorities? I have attached the Kik apk, which has the modded package name and has been signed. The provider/authorities have not been touched by me in this attachment.
EDIT: I just realized this got posted in the wrong section. Sorry. Could a mod move this to a more appropriate section please?
Has anyone installed and tried Google Dialer on this phone yet? If so which apk did you use? Any problems?
What google dialer are you talking about? It already has the stock dialer from aosp on the phone.
termleech said:
What google dialer are you talking about? It already has the stock dialer from aosp on the phone.
Click to expand...
Click to collapse
Has built in caller id and you can type in names of nearby places to call stores and such.
I have and works perfectly.
http://www.apkmirror.com/apk/google-inc/google-dialer/google-dialer-1-1-apk/
Junior Passos said:
I have and works perfectly.
http://www.apkmirror.com/apk/google-inc/google-dialer/google-dialer-1-1-apk/
Click to expand...
Click to collapse
Is there anything special needed? Root? Disabling the stock dialer?
No, I have it installed but I have 2 phone apps in app drawer, you can't disable the phone app that comes with the phone.
Just tried it. Moto assist does not work using the Google dialer. So when I'm home, the phone no longer let's me answer the phone with voice activation. I use that more than I'd use the Google dialer features, thanks for posting the apk though.
Junior Passos said:
I have and works perfectly.
http://www.apkmirror.com/apk/google-inc/google-dialer/google-dialer-1-1-apk/
Click to expand...
Click to collapse
Thanks for the link and info!
Any time I do the location search at the top of the dialer in the APK I get a force close of the dialer. For instance I can type "Home Depot", as soon as I press on the result to select it I get a FC.
RyanTX said:
Any time I do the location search at the top of the dialer in the APK I get a force close of the dialer. For instance I can type "Home Depot", as soon as I press on the result to select it I get a FC.
Click to expand...
Click to collapse
I'm pretty sure you need more than just the dialer apk to get that functionality.
I was looking for a way to have that functionality as well, and after a little research I found out that the location search on the dialer is an exclusive feature for Nexus and Google Play devices :crying: . I had that on my Galaxy S4 GPE and I liked that feature too. Found a post on Android Police explaining on how to make it work on other devices, but a lot of bugs can happen.
seco2004 said:
I was looking for a way to have that functionality as well, and after a little research I found out that the location search on the dialer is an exclusive feature for Nexus and Google Play devices :crying: . I had that on my Galaxy S4 GPE and I liked that feature too. Found a post on Android Police explaining on how to make it work on other devices, but a lot of bugs can happen.
Click to expand...
Click to collapse
I've updated to Android 5.0 out of the box when I got my phone few days ago. - This morning I've installed the 1.1 Dialer APK linked in this thread, however, something did not work, when I pull up the app info on the only icon in the drawer it tells me version 5.0-10.
However, if I go into Settings > Apps > (Downloaded Tab) I see Dialer 1.1 is installed, under (All) I still see Dialer, and version lists 5.0-10 - The 5.0-10 is the stock moto one for Android 5.0, and this one does not have the caller ID, reverse look-up.
I might try disabling the 5.0-10, but from what I understand, that messes with the phone in a big way?
Shemploo said:
I've updated to Android 5.0 out of the box when I got my phone few days ago. - This morning I've installed the 1.1 Dialer APK linked in this thread, however, something did not work, when I pull up the app info on the only icon in the drawer it tells me version 5.0-10.
However, if I go into Settings > Apps > (Downloaded Tab) I see Dialer 1.1 is installed, under (All) I still see Dialer, and version lists 5.0-10 - The 5.0-10 is the stock moto one for Android 5.0, and this one does not have the caller ID, reverse look-up.
I might try disabling the 5.0-10, but from what I understand, that messes with the phone in a big way?
Click to expand...
Click to collapse
I'm not sure what can happen if you disable the stock dialer app, maybe prevent you from making/receiving phone calls if you don't have another dialer app installed? That's just my guess though, never actually did it to check. Were you able to make the location feature work?
Sent from my XT1097 using Tapatalk
seco2004 said:
I'm not sure what can happen if you disable the stock dialer app, maybe prevent you from making/receiving phone calls if you don't have another dialer app installed? That's just my guess though, never actually did it to check. Were you able to make the location feature work?
Sent from my XT1097 using Tapatalk
Click to expand...
Click to collapse
I was unable to get the Caller ID to work, the phone shows me that they are both installed ( Settings > Apps ) - however, the one that came with the stock/factory ROM is preventing the 1.1 version for loading/showing at all in the apps list, so short of disabling the stock one (which I understand is not something one should be doing), I can't even open/access the offloaded one (Dialer 1.1)
I might get brave and disable the stock dialer, see if the Dialer 1.1 surfaces in the apps list.
Shemploo said:
I was unable to get the Caller ID to work, the phone shows me that they are both installed ( Settings > Apps ) - however, the one that came with the stock/factory ROM is preventing the 1.1 version for loading/showing at all in the apps list, so short of disabling the stock one (which I understand is not something one should be doing), I can't even open/access the offloaded one (Dialer 1.1)
I might get brave and disable the stock dialer, see if the Dialer 1.1 surfaces in the apps list.
Click to expand...
Click to collapse
I think that no major issues should arise as long as you just freeze the app and not uninstall it with titanium backup, but again, that's just my wild guess haha. Anyway, leave us posted about your findings.
Sent from my XT1097 using Tapatalk
OK - Got it Working!!! - Not Really, it crashes.
Step #1 - Download/Install the APK from this post
(will need a file manager to browse the phone to where the APK was downloaded to)
Step #2 - Create shortcut for Google Dialer 1.1 that you just installed using QuickShortcutMaker
Detailed instructions are HERE - Start at Step #3 on that page.
(Stock Dialer should be the only one showing in app drawer, you need to make a shortcut for the Google Dialer 1.1)
Step #3 - Win!!!
Some Pictures as Proof in Puddin
Stock Moto X Lollipop 5.0 Dialer / Settings
Nexus Android 5.x Dialer (Dialer 1.1) / Settings / Results
Google Dialer 1.1 shortcut above Stock Dialer shortcut.
Since trying this app initially, I've rooted my phone, and I've tried to follow steps outlined in (http://htc-one.wonderhowto.com/how-to/install-new-kitkat-4-4-3-dialer-your-htc-one-0155515/), specifically Step 2 - Where the app is installed in /system/priv-app/ folders - I am sad to report this does not work still on MotoX
As previous users suggested, there are probably those other services the Dialer depends on that need to be installed.
I'll update if I find a solution.
I don't know if it matters but I had a Nexus 6 before getting my Moto X. The Google Dialer was version 2.0. I didn't grab the APK before returning it but I'm sure it could be pulled from the factory image.
I was unable to make this work, root/non-root.
Got it working, here -http://forum.xda-developers.com/moto-x-2014/themes-apps/mod-google-dialer-messenger-pure-edition-t2982408
I can't make or receive calls on any N ROMs, everything else works perfectly, any idea why?
Hello . I had this problem on my wife's opx very annoying the issue is with the roms in most cases but, it's normally because they add pixel stuff bundled with the rom... Because everyone loves pixel? Anyway. If you go into build prompt with an app you can download it on Google play.
Check to see if your ro.product.name says oneplus X and nothing else. This was my issue. Weird... I no. But anyway.
If it's not see if anyone can call you. Assuming you have full signal.
Try another phone or contacts app from Google play? The above worked for me but it might be different for you. Try switching brand name to pixel? There is a guide somewhere what to change in build prompt.
In the menus, there is a place to set the default ssm app, phone app...
Just re set it to make the Phone.apk be the phone app.
I've seen it on some users and it worked.
Simple fix happened to me once when I installed google phone. As Keno40 stated you need to set default phone app