Android Pay on Rooted devices? - General Questions and Answers

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I saw an article on Reddit explaining how to enable Android pay on devices right now. Figured I'd give it a shot. So, following the steps on my rooted LG G4 from Verizon, I downloaded and updated to the most recent Google Play Services from http://apkmirror.com, created a shortcut with Nova Launcher (widgets>activities>Google Play Services> Android Pay) and opened it up. It took me to a menu from the Google Play Services settings app which isn't visible if you open the app directly. Runs you through a few prompts enabling it as the default payment app, and sends you back to the settings page. At the bottom you can add a card, which, if you used Google Wallet before, it will load all your cards from there. Enter the CVC of your card, agree to the terms and conditions, and it sits and loads. A few seconds later, the above error message shows up. Repeated this process a few times, and same result. So, I hopped on over to my non-rooted Galaxy S6 Edge from Sprint, and repeated the process. First time through, it activated with no error messages. So, this leads me to believe that Android pay does not work on a rooted device. Can anyone confirm/deny my suspicions?

I know it will not work. You can try apps that will hide your root. But sometimes it still won't work. It's because a rooted phone is less secure than a non rooted phone.
That's what the pay apps think anyways so it won't let you install.
Sent from my GT-I9505 using Tapatalk

th3av3ng3r said:
So I saw an article on Reddit explaining how to enable Android pay on devices right now. Figured I'd give it a shot. So, following the steps on my rooted LG G4 from Verizon, I downloaded and updated to the most recent Google Play Services from apkmirror.com, created a shortcut with Nova Launcher (widgets>activities>Google Play Services> Android Pay) and opened it up. It took me to a menu from the Google Play Services settings app which isn't visible if you open the app directly. Runs you through a few prompts enabling it as the default payment app, and sends you back to the settings page. At the bottom you can add a card, which, if you used Google Wallet before, it will load all your cards from there. Enter the CVC of your card, agree to the terms and conditions, and it sits and loads. A few seconds later, the above error message shows up. Repeated this process a few times, and same result. So, I hopped on over to my non-rooted Galaxy S6 Edge from Sprint, and repeated the process. First time through, it activated with no error messages. So, this leads me to believe that Android pay does not work on a rooted device. Can anyone confirm/deny my suspicions?
Click to expand...
Click to collapse
Use Rootcloak to hide root from google play services. I have the LG G4 on verizon as well, which version of the apk did you download? was it 248?

mfun89 said:
Use Rootcloak to hide root from google play services. I have the LG G4 on verizon as well, which version of the apk did you download? was it 248?
Click to expand...
Click to collapse
I tried Rootcloak, both the play store edition and the Xposed edition. Neither one worked, just resulted in Google Play Services crashing every time I tried to add a card. After doing a bit of seaching, I found another Reddit thread that said you can disable root in SuperSU, add your cards, and then enable root again. So far I haven't had any luck.
As to the apk version, it was 248.

Success!!
Update: It's been figured out. One, it checks for root. Easily fixable by going into SuperSU and disabling it. Two, it checks for stock DPI. So what I did, in order of operation, was I restored the unmodified build.prop for my phone, rebooted, went into SuperSU, disabled the app (not the options toward the bottom for switching root apps or unrooting, the one at the top of the settings page), and opened Android Pay. Seeing as we now have an apk for the full app, I opened that, but it works even if you haven't gotten it yet. Add your cards and such and you can enable root again. For some reason I restored my edited build.prop and it worked just fine, so it must be just an initial check when you add cards. Anyway, have fun and hit thanks if I helped at all!

th3av3ng3r said:
Update: It's been figured out. One, it checks for root. Easily fixable by going into SuperSU and disabling it. Two, it checks for stock DPI. So what I did, in order of operation, was I restored the unmodified build.prop for my phone, rebooted, went into SuperSU, disabled the app (not the options toward the bottom for switching root apps or unrooting, the one at the top of the settings page), and opened Android Pay. Seeing as we now have an apk for the full app, I opened that, but it works even if you haven't gotten it yet. Add your cards and such and you can enable root again. For some reason I restored my edited build.prop and it worked just fine, so it must be just an initial check when you add cards. Anyway, have fun and hit thanks if I helped at all!
Click to expand...
Click to collapse
Are you on stock firmware or are you running a custom ROM?

th3av3ng3r said:
Update: It's been figured out. One, it checks for root. Easily fixable by going into SuperSU and disabling it. Two, it checks for stock DPI. So what I did, in order of operation, was I restored the unmodified build.prop for my phone, rebooted, went into SuperSU, disabled the app (not the options toward the bottom for switching root apps or unrooting, the one at the top of the settings page), and opened Android Pay. Seeing as we now have an apk for the full app, I opened that, but it works even if you haven't gotten it yet. Add your cards and such and you can enable root again. For some reason I restored my edited build.prop and it worked just fine, so it must be just an initial check when you add cards. Anyway, have fun and hit thanks if I helped at all!
Click to expand...
Click to collapse
Awesome! This worked! Thank you!

Devo7v said:
Are you on stock firmware or are you running a custom ROM?
Click to expand...
Click to collapse
Stock firmware with Xposed.
Update: Not sure what it was, maybe because I added it as a new card, but my local bank debit card didn't work at McDonald's on my G4 today, yet the same card worked perfectly on my edge. Will do more testing, maybe it's just the way I added it because I'm pretty sure its not gonna be compatible unless it's "grandfathered" in from Google Wallet.

Is Xposed perhaps causing this issue? I'm having it too, on an AT&T S5 rooted stock with Xposed. Also what about KNOX? This is so @$% annoying
---------- Post added at 01:17 AM ---------- Previous post was at 01:14 AM ----------
Also is there a way to revert back to the functional google wallet app?
---------- Post added at 02:04 AM ---------- Previous post was at 01:17 AM ----------
Hey I figured it out, all you have to do is disable superuser like people have said, but before you do you need to uninstall xposed framework, then reboot, and bam worked for me. Goodluck

kchannel9 said:
Is Xposed perhaps causing this issue? I'm having it too, on an AT&T S5 rooted stock with Xposed. Also what about KNOX? This is so @$% annoying
---------- Post added at 01:17 AM ---------- Previous post was at 01:14 AM ----------
Also is there a way to revert back to the functional google wallet app?
---------- Post added at 02:04 AM ---------- Previous post was at 01:17 AM ----------
Hey I figured it out, all you have to do is disable superuser like people have said, but before you do you need to uninstall xposed framework, then reboot, and bam worked for me. Goodluck
Click to expand...
Click to collapse
I cannot say as to KNOX, but I have heard reports that it will not work if it has been tripped. Regarding Xposed, I still have it enabled with a few modules, mainly App Settings to change the DPI back to stock for Android Pay, Google Play Services, and Google Services Framework. Do all that, reboot, disable Superuser, and you should be good to go. I've found that RootCloak doesn't work, but it seems to be hit and miss among devices.
Reverting back to Google Wallet should be as simple as downgrading your Google Play Services to before Android Pay, uninstall Android Pay, and re-install the old Google Wallet from http://apkmirror.com. No promises as to how long it will work, but it should work for a few weeks, maybe even a month or two.

Well I got it working, but when I tried to use it at Whole Foods, it didn't work, it didn't even try. I had NFC on, and it did not try to do anything no matter what I did or what position the phone was. Seems beta right now......

On GPE marshmallow 2.62-3 systemless root and works great
~m8whl on the Always Solid ViperOneM8 Latest
Hypernova mako_hotplug kernel at 2.572 Max ¦ 300 Min ¦ 1.190 Sleep
interactive (Franco tweaked)*
row

Doesn't work on rooted Moto X with no xposed.
Tried disabling SuperSU as well as Rootcloak, including multiple reboots and wiping app data.
No go. F google. Then I won't use your payment system. Only wanted to get the BB $20 anyhow.

andTab said:
Doesn't work on rooted Moto X with no xposed.
Tried disabling SuperSU as well as Rootcloak, including multiple reboots and wiping app data.
No go. F google. Then I won't use your payment system. Only wanted to get the BB $20 anyhow.
Click to expand...
Click to collapse
Have you gotten around to trying a full wipe install, and latest experimental systemless SuperSU?
Sent from my SM-G900P using Tapatalk

Related

[ROM][KFHD7][7.4.8] ♦ Kinology 3.3 ♦ 2014/03/12 ♦ Final

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introducing Kinology - The Premier KFHD7 Custom ROM​
Standard Disclaimer: I cannot be held responsible for loss, damages, or any kind of issue whatsoever that could arise from installing this ROM. You install it at your own risk.
Kinology is the premier custom ROM for the Kindle Fire HD 7" tablet. It will not work on any other device. Kinology should be considered a "hybrid OS"; it contains Amazon's 7.4.8 ICS-based core along with Google's ICS Services Framework and application stack.
Feature list
Installation / Download
Advanced Configuration
Known Issues
History
Screenshots
3.3 will be the last version of Kinology. The 7.4.9 update does not leave enough room on the system partition for the Kinology base. Additionally, that version of the Amazon OS is using server side filtering that prevents many non-Amazon approved applications from working correctly. My investigations into the issue did not turn up an easy fix.
What's new?
3.3 - 2014/03/12
Update the base to 7.4.8 and updated included apps. See the History page linked above for further details.
3.2 - 2013/11/21
Kinology itself is unchanged for this release. Only apps have been updated. See the History page linked above for details.
3.1 - 2013/08/11
Updated the base OS to 7.4.6.
The restart/failure message when flashing the boot zip will only be shown if the recovery is actually changed.
Installers now apply ASLR correctly to all libraries.
Added Adobe Flash Player again, as it no longer causes browsers to crash.
Updated GmsCore, Hangouts, and Play Store in the Google package.
Updated Adobe Air in the Amazon Updates package.
Behind the scenes stuff:
* Added code to the make scripts to build all-in-one installation.
* Modified the make scripts so that .apks with identical code and resources always result in binary-identical files.
* Because of the previous modification, update zips can now be automatically generated.
* Many other changes to the make scripts so that they are more resilient.
3.0. - 2013/07/21
Updated the base OS to 7.4.5.
Fixed the disabled wallpaper issue in 7.4.1.
Removed text on battery icons (a percentage option was added by Amazon).
Updated Gmail, GmsCore, and the Play Store in the Google package, and added Hangouts instead of Talk.
Update SuperSU and included SuperSUNoNag.
Removed Adobe Flash Player as it is not compatible with 7.4.5.
Fixed the install process: the boot zip is now required, but it will only flash items that you do not already have installed.
Separated Amazon app updates from Kinology proper in the install process.
XDA:DevDB Information
Kinology [KFHD7/TATE], ROM for the Amazon 7" Kindle Fire HD
Contributors
JulianPaoloThiry
ROM OS Version: 4.0.x Ice Cream Sandwich
Based On: Amazon OS 7.4.8
Version Information
Status: Stable
Current Stable Version: 3.3
Stable Release Date: 2014-03-12
Created 2014-10-16
Last Updated 2014-10-16
I was just cleaning up my system (Had CM10.1 on it, but was facing issues with Video chat in GTalk) to go back to Kinology 2.0.1 and was facing some boot issues. When I went back to see the potential list of ROMs to try, I noticed this thread.
Edit: Flashed it and seems to be stable so far. Still checking stability of various apps.
Edit 2: Spoke too soon. Just got a random reboot. The screen was in landscape mode and was trying to get it to portrait, it just rebooted.I did a first reboot before setting up the device as mentioned in the installation procedure.
Sequence of events before I got the random reboot: I flashed the files as per the installation procedure (verbatim), did a reboot after the first boot, set up the system, added google accounts, installed nova launcher, set that as my primary launcher, tried hangout, it hung in the Video call, force stopped it, then was editing the message here in the forum, went back to Kindle, was rotating to portrait mode, kindle rebooted.
EDIT 3: I am still getting random reboots trying to play around hangout. I will find GTalk apk from somewhere and install. I will update the status after that.
No flash, no fun . That was one of the best features in android for me, besides the roms. If it's possible, i would love to see a fix for it.
Thanks,
Grwy
Sent from my KFTT using xda app-developers app
Request to package just Gtalk and allow option to users to upgrade to Hangouts
One humble request: If you could, please let the users decide if they want to upgrade to hangout. I am facing issues with that, and I was able to uninstall updates to go back to GTalk. But given that Hangouts was directly add to the ROM itself, I could not go back to GTalk by just uninstalling it in Playstore.
I will figure a way to get GTalk back. But it was easier to uninstall from play store
raj3366 said:
I will figure a way to get GTalk back.
Click to expand...
Click to collapse
I can make an updater zip that replaces Hangouts with Talk. Will probably post it tomorrow sometime.
GreyGeist said:
No flash, no fun . That was one of the best features in android for me, besides the roms. If it's possible, i would love to see a fix for it.
Click to expand...
Click to collapse
This bugs me a lot, too. I'm not sure if there will be a solution. Unfortunately, the crash is very low level (in the .so files), so it's very tough to even begin to know how to work around it. I certainly plan to continue working on it, though.
raj3366 said:
I am still getting random reboots trying to play around hangout.
Click to expand...
Click to collapse
I successfully made a video call using Hangouts to my phone for testing and didn't get any reboots. I know that's just one anecdote, but if I recall, GTalk's video/voice didn't work very well for some on Kinology 2 either.
JulianPaoloThiry said:
I can make an updater zip that replaces Hangouts with Talk. Will probably post it tomorrow sometime.
Click to expand...
Click to collapse
That would be awesome. I tried replacing the Hangouts.apk with Talk.apk in the google update zip. But the signature (SHA1-digest) had to be updated in META-INF/CERT.SF and META-INF/MANIFEST.MF files. So I could not get it working.
I had very good success rate using GTalk in Kinology 2.0. I guess my mileage varies. But having GTalk gives me the freedom to upgrade to Hangouts or stay with GTalk depending on whichever works. Again, that's just my personal opinion.
Thanks for looking into this Julian. I am sending this Kindle to my parents so that I could chat over Video call. I have to get it stabilized before that. They are not tech-savy.
So far I am not seeing any other issues. I will report back, if I run into any.
I can't thank you enough for doing this.:good:
JulianPaoloThiry said:
This bugs me a lot, too. I'm not sure if there will be a solution. Unfortunately, the crash is very low level (in the .so files), so it's very tough to even begin to know how to work around it. I certainly plan to continue working on it, though.
Click to expand...
Click to collapse
Alright, thanks. I've always really liked Kinology, but the gapps and lockscreen issues were its downfall for me. Are these fixed yet? In the previous build, gapps constantly crashes (especially chrome), and the lockscreen would randomly disappear.
There is now a download available to rollback from Google Hangouts to Google Talk. Be aware that your launcher's caching may cause the icon and/or name of Hangouts to remain unchanged. Be sure to actually launch the app and check it before claiming that the rollback did not work.
Edit: Hmmmm. Hold off downloading that. I can't seem to find the voice/video options at all now.
Edit: False alarm. Turns out that Google Talk cannot voice/video chat with Google Hangouts users. So if your friends upgrade and you do not, you're SOL. There's nothing wrong with the rollback package, so use it if you like.
GreyGeist said:
the gapps and lockscreen issues were its downfall for me. Are these fixed yet? In the previous build, gapps constantly crashes (especially chrome), and the lockscreen would randomly disappear.
Click to expand...
Click to collapse
... no one reported either of those issues previously...
I've used Kinology since it was released and have not seen them. I must admit, however, that I have the lock screen disabled (my Kindle never leaves the house and has a book-like cover), so I wouldn't have noticed that one.
I do use Chrome and most other Google apps, and can't recall them ever crashing. Capturing a logcat dump immediately after a crash and sending it to me is the best way to get that sort of thing identified. The only other workable alternative is to report reproducible steps that always result in a crash.
JulianPaoloThiry said:
There is now a download available to rollback from Google Hangouts to Google Talk. Be aware that your launcher's caching may cause the icon and/or name of Hangouts to remain unchanged. Be sure to actually launch the app and check it before claiming that the rollback did not work.
Click to expand...
Click to collapse
Thanks a lot. That solves my problem. I will try it tonight when I get back home and update you. As long as it works with other google talk users, I am good. Is there procedure to repackage it myself? (if you update the google zip, I would not want you to re-package it every time. I would be more than happy to do it myself and share it for those who need that.)
EDIT: I just saw the size of it. I guess no re-packaging necessary. I just need to flash it as the last zip. This even more awesome. Thanks!
Launcher
How do you start up in tablet mode, not Kindle carousel?
Do you need a launcher?
Wind Dancer said:
How do you start up in tablet mode, not Kindle carousel?
Do you need a launcher?
Click to expand...
Click to collapse
If you do not want to use the carousel as your default launcher then you will need to install an alternative launcher from the Play Store, such as GO or Nova. The next time you reboot (or press the home button, I think), your Kindle will ask you which launcher to use, at which time you can tell it to stop asking and just use the one you pick.
JulianPaoloThiry said:
If you do not want to use the carousel as your default launcher then you will need to install an alternative launcher from the Play Store, such as GO or Nova. The next time you reboot (or press the home button, I think), your Kindle will ask you which launcher to use, at which time you can tell it to stop asking and just use the one you pick.
Click to expand...
Click to collapse
okay, thanks for the confirmation
GreyGeist said:
Alright, thanks. I've always really liked Kinology, but the gapps and lockscreen issues were its downfall for me. Are these fixed yet? In the previous build, gapps constantly crashes (especially chrome), and the lockscreen would randomly disappear.
Click to expand...
Click to collapse
Odd, I never had a problems with Gaaps (Google Applications) although I have not liked chrome on any of my Android devices. . .Sorry, I can't compare with lockscreens -since I don't use one on my KFTT, but when I did it was never an issue. . . I hope this new version will be a stable, and dependable as Kinology2 -I am downloading now! (Thanks!) :victory:
Sorry to change topic but does anyone have the full build/version number for 7.4.5, it should be something like this: 7.4.5_D025_XXXXXXX
Thanks
Gilly10 said:
Sorry to change topic but does anyone have the full build/version number for 7.4.5, it should be something like this: 7.4.5_D025_XXXXXXX
Thanks
Click to expand...
Click to collapse
4513120
I cat find the update file anywhere the one i found will not manually update. Could you send me the stock update file for 7.4.5. I like to be up to date as much as i can but amazon is not posting this update on there web site and my auto update is not updating to 7.4.5
Sent from my KFTT using xda app-developers app
Hinzman420 said:
I cat find the update file anywhere the one i found will not manually update. Could you send me the stock update file for 7.4.5. I like to be up to date as much as i can but amazon is not posting this update on there web site and my auto update is not updating to 7.4.5
Click to expand...
Click to collapse
I downloaded this 7.4.5 file but since I'm not on stock Amazon OS I can't test it to see if it'll update properly, also supposedly Adobe Flash doesn't play nice with this build.
https://s3.amazonaws.com/kindle-fire-updates/update-kindle-7.4.5_D025_4513120.bin

stock google phone app

Like the title says, i want to use the google phone app. But play store says not compitable with your phone. Does anyone know why this is and maybe a solution? Thanks in advance.
You can always try to flash a gapps package.
---------- Post added at 06:04 PM ---------- Previous post was at 05:58 PM ----------
Try this link. Can confirm install works.
https://forum.xda-developers.com/an...292-bubble-t3708218/post74588791#post74588791
I too find the stock phone app leaving much to be desired. I really think OnePlus should leave the Phone, Contacts, Calendar and Messaging stock as they work GREAT. Unfortunately all but the Phone is easily fixed
mikex8593 said:
---------- Post added at 06:04 PM ---------- Previous post was at 05:58 PM ----------
Try this link. Can confirm install works.
https://forum.xda-developers.com/an...292-bubble-t3708218/post74588791#post74588791
Click to expand...
Click to collapse
This modified Google phone app on XDA won't allow you to answer the call when the screen is already on so find it to be a "no-go".
mikex8593 said:
You can always try to flash a gapps package.
---------- Post added at 06:04 PM ---------- Previous post was at 05:58 PM ----------
Try this link. Can confirm install works.
https://forum.xda-developers.com/an...292-bubble-t3708218/post74588791#post74588791
Click to expand...
Click to collapse
It's still not the same as the original. Its just weird that you can't install it from the play store like the other google apps.
I just wound up installing the "Google Framework" module from Magisk and then sideload the Google Phone apk from apkmirror. Works great for me.
Edit - I'm not even sure that installing the "Google Framework" module is necessary. Module descriptions says it's just so you can download Phone from the Play Store, which still doesn't work for me, but as I remember from dealing with my Nexus 6P, Google Framework Services was required to get the Google Phone app to work. Tbh I didn't pay attention and have no idea if Google Services Framework already existed or not.
There is a way. I had it working yesterday.
I bricked my phone by accident, well on purpose accident.....
I used the Chinese unbricking tool from this Forum, the only tool that worked for me after trying all others all day long. But it loads Helium not Oxygen, and you can load the play store from the "market" take almost all other apps out and the google phone for non pixel works just fine, also you still get Helium updates from oneplus. the only downside is there are some things in chinese that you cant change.
RickCain said:
I too find the stock phone app leaving much to be desired. I really think OnePlus should leave the Phone, Contacts, Calendar and Messaging stock as they work GREAT. Unfortunately all but the Phone is easily fixed
This modified Google phone app on XDA won't allow you to answer the call when the screen is already on so find it to be a "no-go".
Click to expand...
Click to collapse
Oh, okay. Didn't see that part.
Where did you get a version of magisk that works with the OnePlus 6?
Sicklyboy said:
I just wound up installing the "Google Framework" module from Magisk and then sideload the Google Phone apk from apkmirror. Works great for me.
Edit - I'm not even sure that installing the "Google Framework" module is necessary. Module descriptions says it's just so you can download Phone from the Play Store, which still doesn't work for me, but as I remember from dealing with my Nexus 6P, Google Framework Services was required to get the Google Phone app to work. Tbh I didn't pay attention and have no idea if Google Services Framework already existed or not.
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
RickCain said:
Where did you get a version of magisk that works with the OnePlus 6?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-magisk-root-oos-5-1-5-t3794440
Well I used the Magisk method with Google Framework and still can't answer a phone call if the screen is on...... GRRRRR
Top it off I tried to go back to stock and relock and now in a boot loop. Just sucks.
edit: went to fastboot and then recovery, it wiped and now back up and running. Not touching this thing again
RickCain said:
Well I used the Magisk method with Google Framework and still can't answer a phone call if the screen is on...... GRRRRR
Top it off I tried to go back to stock and relock and now in a boot loop. Just sucks.
edit: went to fastboot and then recovery, it wiped and now back up and running. Not touching this thing again
Click to expand...
Click to collapse
You have to install the magisk package and then manually go into the app settings and grant all the permissions and it should work. Works perfectly on my OP6.
Masterleon said:
You have to install the magisk package and then manually go into the app settings and grant all the permissions and it should work. Works perfectly on my OP6.
Click to expand...
Click to collapse
That is what I did, twice with the same result. Can you post a screen shot of your permissions for the phone app?
I'm going to keep the phone on ice for awhile to see if any custom ROMs come out for it before the Pixel 3 XL hits the street.
Sent from my Pixel 2 XL using Tapatalk
RickCain said:
That is what I did, twice with the same result. Can you post a screen shot of your permissions for the phone app?
I'm going to keep the phone on ice for awhile to see if any custom ROMs come out for it before the Pixel 3 XL hits the street.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yeah here's my permissions and proof it works. I'm using the "Google Dialer and Contacts for OP5/5T" package on magisk.
Maybe it's a T-Mobile thing, I could dial into Voicemail manually but did not have the voicemail icon on the phone page (where is shows favorites, recent, contacts, voicemail). That and couldn't get it to accept an incoming call if the screen was already on.
RickCain said:
Maybe it's a T-Mobile thing, I could dial into Voicemail manually but did not have the voicemail icon on the phone page (where is shows favorites, recent, contacts, voicemail). That and couldn't get it to accept an incoming call if the screen was already on.
Click to expand...
Click to collapse
I was having a similar issue over the past month or so with google dialer and T-mobile using my Nexus 6P. I think there is something going on there beyond our control. I did get it to work randomly for a few days, then back to having to dial voicemail.
Its a joke we can use Google Contacts on OnePlus but we cant use Google Phone, this is so weird!
I suspect they want its benefits to be exclusive to Nexus and Pixel devices. Just a guess. I like being able to type the names of local businesses to be able to dial them without knowing their numbers or looking them up elsewhere to begin with. Not having that is going to be an adjustment for me with this device.
Now that the Google Phone apk has been updated, to the new style and pastal colors, maybe the OP that [Patched] those google phone apks mentioned earlier in the thread, unless someone here figured out what is needed to get it done?
New Updated apk : https://www.apkmirror.com/apk/googl...-phone-23-0-208561757-3-android-apk-download/
Thanks in advance!
*edit*
OP in the [Patched] thread updated the google phone apk found HERE :
*edit* *edit*
Tried [Patched] Google Phone apk on Pie beta 1 and it would NOT install...I think it WILL install on OREO...
flast no limits 2.9.1, and select the google dialer in config file, it is working fine here.

[Help] GMS (sort) of working?

Hi everyone,
So although that I had made attempts to successfully install gms without any errors, I did not fully succeed in any of the guides. My firmware was 114 or 117 (don't remember now) and I tried several times with this firmware, as well as with 121 firmware (the only update I had).
So far, Google photos, Google maps, Google drive, YouTube, whatsapp, all work, however I am getting the notification "device is not play protect certified" when I open them (attached).
NEVERTHELESS, I do note foll:
- whatsapp backup successfully restored from Google drive, - Google photos sync and backup successfully between devices
- maps work (haven't actually navigated, but seems that everything is calculated properly).
-Contacts have synced with my Google contacts
-Gmail app works, but whenever I launch the app I get a banner saying "Google is having trouble with play services. Please try again", however I can see behind the banner that all new mails are there, but if i click the compose msg button, then I keep getting the error and cannot proceed.
-What I noticed though is that no any app currently installed on my p20 pro has been restored from play store on the p40 pro.
-i have NO notifications from Google apps
-Google search app works only for searching, I have no cards displayed on Google feed and it shows that I am not signed in, although all other Google apps have me properly signed in.
-Google Home does not work, since it does not allow me to sign in.
-Youtube works normally without any errors, actually I am also receiving notifications of newly uploaded videos :/
What the heck is going on? How come they partly work since my device is not certified and I am getting the notification page in all Google apps when they first launch?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my CLT-L29 using Tapatalk
IMO you should factory reset the phone and try another method for installing GMS until you find one that works for you. I tried a few and this way I was able to made it: https://forum.xda-developers.com/showpost.php?p=83303057&postcount=262
It seems it is not possible to have both notifications and play store working together, so you use Icebox to freeze Google Play after restoring your purchased in order to have notifications. Then use a replacement store like Aurora.
Good luck and don't give up ?
I have Google installed, with Google Play and notifications active (I don't know if that metod still works)
https://youtu.be/SrRW5ZcX1M0
A friend had installed Google on Mate30 pro yesterday and today from here:
https://youtu.be/VA-gyruGORo
https://youtu.be/J141DvUxIrU
I've tried both of these methods and both work on my P40 Pro with firmware .131. I've now updated to August security patch .154 and all Google services are still working fine.
https://www.youtube.com/watch?v=9fTIZFehwlw&feature=youtu.be
https://www.youtube.com/watch?v=VA-gyruGORo This is the one I am currently using for the last few weeks with no problems at all.
Good luck and don't give up
sko4a said:
IMO you should factory reset the phone and try another method for installing GMS until you find one that works for you. I tried a few and this way I was able to made it: https://forum.xda-developers.com/showpost.php?p=83303057&postcount=262
It seems it is not possible to have both notifications and play store working together, so you use Icebox to freeze Google Play after restoring your purchased in order to have notifications. Then use a replacement store like Aurora.
Good luck and don't give up [emoji846]
Click to expand...
Click to collapse
Thanks mate
I tried many methods so far, the one you used, one from a German guy, the other from the Portuguese guy (video in English) but all more or less resulted the same.
What I cannot understand is whether I do have play services working after all, or not, since as I said, my content syncs, although I am getting the non-certified error. Ok, and I do not have notifications from gapss.. [emoji23]
So I am really really confused.
Sent from my CLT-L29 using Tapatalk
Shymmy said:
I have Google installed, with Google Play and notifications active (I don't know if that metod still works)
https://youtu.be/SrRW5ZcX1M0
A friend had installed Google on Mate30 pro yesterday and today from here:
https://youtu.be/VA-gyruGORo
https://youtu.be/J141DvUxIrU
Click to expand...
Click to collapse
I will try the second one, first already tried, thanks! [emoji3]
Sent from my CLT-L29 using Tapatalk
potsykate said:
I've tried both of these methods and both work on my P40 Pro with firmware .131. I've now updated to August security patch .154 and all Google services are still working fine.
https://www.youtube.com/watch?v=9fTIZFehwlw&feature=youtu.be
https://www.youtube.com/watch?v=VA-gyruGORo This is the one I am currently using for the last few weeks with no problems at all.
Good luck and don't give up
Click to expand...
Click to collapse
Mine didn't work with that, or did it? I really don't know what to say. It's just weird, I have my content but I have this error and I don't have any notifications, yet everything syncs. Google photos sync automatically between my p20 pro and the p40 pro, etc
Sent from my CLT-L29 using Tapatalk
potsykate said:
I've tried both of these methods and both work on my P40 Pro with firmware .131. I've now updated to August security patch .154 and all Google services are still working fine.
&feature=youtu.be
This is the one I am currently using for the last few weeks with no problems at all.
Good luck and don't give up
Click to expand...
Click to collapse
How to downgrade? Some tutorial just downloading firmware with checking firmware approve or not approve. Is it safe to install with differen region firmware? Or all firmware just the same and can be installed to all devices?
dalfshiro said:
How to downgrade? Some tutorial just downloading firmware with checking firmware approve or not approve. Is it safe to install with differen region firmware? Or all firmware just the same and can be installed to all devices?
Click to expand...
Click to collapse
No, it is not save to install a firmware that does not suite to your device. In best case it just can't be installed, in worst case you'll brick your phone. This is at least what I think and what a heard from other user reports in this forum. Do you have difficulties to find the right firmware?
thanito said:
Hi everyone,
So although that I had made attempts to successfully install gms without any errors, I did not fully succeed in any of the guides. My firmware was 114 or 117 (don't remember now) and I tried several times with this firmware, as well as with 121 firmware (the only update I had).
So far, Google photos, Google maps, Google drive, YouTube, whatsapp, all work, however I am getting the notification "device is not play protect certified" when I open them (attached).
NEVERTHELESS, I do note foll:
- whatsapp backup successfully restored from Google drive, - Google photos sync and backup successfully between devices
- maps work (haven't actually navigated, but seems that everything is calculated properly).
-Contacts have synced with my Google contacts
-Gmail app works, but whenever I launch the app I get a banner saying "Google is having trouble with play services. Please try again", however I can see behind the banner that all new mails are there, but if i click the compose msg button, then I keep getting the error and cannot proceed.
-What I noticed though is that no any app currently installed on my p20 pro has been restored from play store on the p40 pro.
-i have NO notifications from Google apps
-Google search app works only for searching, I have no cards displayed on Google feed and it shows that I am not signed in, although all other Google apps have me properly signed in.
-Google Home does not work, since it does not allow me to sign in.
-Youtube works normally without any errors, actually I am also receiving notifications of newly uploaded videos :/
What the heck is going on? How come they partly work since my device is not certified and I am getting the notification page in all Google apps when they first launch?
View attachment 5091901
Sent from my CLT-L29 using Tapatalk
Click to expand...
Click to collapse
So what I can say from my side, Gmail app works for me. And Google Home allows me to sign in. Anyway I don´t use this app, so I cannot say more about it.
On the other side I had problems with syncing contacts and calendar.. but I found a solution.
Maybe the "functionality" refers to the firmware, maybe the GMS installation is just not "perfect".
Any other apps, that don´t work for you.? I can install them on my phone and try, if they are not country related, as "food delivery service" you´ve mentioned?
---------- Post added at 04:38 PM ---------- Previous post was at 04:27 PM ----------
thanito said:
First of all, thanks vm for your assistance
You can try to search for "efood delivery" , but even netflix does not let me sign in, although their behavior is different; when i click sign in to netflix, i get the pop up abt the device not being certified, then takes me back to initial netflix screen. In the efood app, I click to launch the app, i get the error and then the app closes again. The weird thing is that efood is also in appGallery (huawei native store), so supposedly it should work.
To be honest, I love huawei devices for their build quality, cameras, battery performance and I have been debating with myself on whether I should buy the p40 pro (i really need google apps for so many reasons- home automation by using google home, etc), but I guess I am screwed; unless I make things work properly i will have to keep using my p20 pro.
Click to expand...
Click to collapse
I just installed efood delivery, at least it lets me to sign in via facebook.
Concerning Netflix. It doesn´t work on some devices. I had problems with OnePlus and also with my Huawei P40 Pro at the beginning. Now it works (after installing through Aurora Store I think). I don´t think it is GSM related. For me it works. But there are some solutions in the app-section on XDA.
Flying Fox said:
So what I can say from my side, Gmail app works for me. And Google Home allows me to sign in. Anyway I don´t use this app, so I cannot say more about it.
On the other side I had problems with syncing contacts and calendar.. but I found a solution.
Maybe the "functionality" refers to the firmware, maybe the GMS installation is just not "perfect".
Any other apps, that don´t work for you.? I can install them on my phone and try, if they are not country related, as "food delivery service" you´ve mentioned?
Click to expand...
Click to collapse
The installation is far from perfect i tell you that
Let me ask you something, so if you have a successful gms installation, i take it that after that you have to freeze gsf in order to have push notifications of you have normal push notifications?I am somewhat confused on this. Do you have to freeze gsf to have push and then to unfreeze only when you want to use playstore?
thanito said:
The installation is far from perfect i tell you that
Let me ask you something, so if you have a successful gms installation, i take it that after that you have to freeze gsf in order to have push notifications of you have normal push notifications?I am somewhat confused on this. Do you have to freeze gsf to have push and then to unfreeze only when you want to use playstore?
Click to expand...
Click to collapse
No, I didn´t freeze anything. But as I remember it didn´t work from the beginning. I tried so many things and actually I don´t know why everything is working now. I should have written down all my steps . I think I also updated Google services. For syncing contacts I had to downgrade GoogleContactsSyncAdapter.
And I still didn´t recognize, if I get all the notifications that are possible. But I get them for my mails and all other messages (using signal for sms), whatsapp and I don´t miss anything.
If I understood correctly you imported your apps from your P20? Another idea, that there is a conflict with this method? I didn´t have this opportunity as I came from a non huawei device. I had to install all my apps from scratch using Aurora as well as Playstore especially for my paid apps.
Flying Fox said:
No, I didn´t freeze anything. But as I remember it didn´t work from the beginning. I tried so many things and actually I don´t know why everything is working now. I should have written down all my steps . I think I also updated Google services. For syncing contacts I had to downgrade GoogleContactsSyncAdapter.
And I still didn´t recognize, if I get all the notifications that are possible. But I get them for my mails and all other messages (using signal for sms), whatsapp and I don´t miss anything.
If I understood correctly you imported your apps from your P20? Another idea, that there is a conflict with this method? I didn´t have this opportunity as I came from a non huawei device. I had to install all my apps from scratch using Aurora as well as Playstore especially for my paid apps.
Click to expand...
Click to collapse
Since I had nothing to lose (phone not being properly setup with gms) I restored my p20 pro backup via hisuite. All my data, even home screen, were restored, minus 76 apps which failed for no apparent reason, I just saw a msg that 76 apps did not complete restoration (I have more than 250 apps installed normally)
Now I am pairing my Samsung watch active 2 to see if this works, but as I see it, I will have to try again from scratch.
Sent from my CLT-L29 using Tapatalk
thanito said:
Since I had nothing to lose (phone not being properly setup with gms) I restored my p20 pro backup via hisuite. All my data, even home screen, were restored, minus 76 apps which failed for no apparent reason, I just saw a msg that 76 apps did not complete restoration (I have more than 250 apps installed normally)
Now I am pairing my Samsung watch active 2 to see if this works, but as I see it, I will have to try again from scratch.
Sent from my CLT-L29 using Tapatalk
Click to expand...
Click to collapse
Of course I cannot know but HiSuite could be the problem, especially if you restore data from a different device. Did you just restore app data or also system data? I´m not firm with HiSuite, but also with former devices I sometimes had conflicts by using backup apps - one reason I miss root.... but I knew it before and still happy with Huawei and the given solutions here on XDA.
So yes, maybe give it a second try, but please don´t make me responsible if you brick your phone ... Good luck!
---------- Post added at 05:14 PM ---------- Previous post was at 05:09 PM ----------
Or you try to reset all your settings first through the phone´s menu. Maybe you have also restored settings from your older device which cause a conflict now.
Flying Fox said:
Of course I cannot know but HiSuite could be the problem, especially if you restore data from a different device. Did you just restore app data or also system data? I´m not firm with HiSuite, but also with former devices I sometimes had conflicts by using backup apps - one reason I miss root.... but I knew it before and still happy with Huawei and the given solutions here on XDA.
So yes, maybe give it a second try, but please don´t make me responsible if you brick your phone ... Good luck!
---------- Post added at 05:14 PM ---------- Previous post was at 05:09 PM ----------
Or you try to reset all your settings first through the phone´s menu. Maybe you have also restored settings from your older device which cause a conflict now.
Click to expand...
Click to collapse
I will try to start from scratch again today if I have some time to spare. Did you install MicroG as well?
thanito said:
I will try to start from scratch again today if I have some time to spare. Did you install MicroG as well?
Click to expand...
Click to collapse
No, both is not possible.
Flying Fox said:
No, both is not possible.
Click to expand...
Click to collapse
Meaning? Is there a way to install microG and have everything working without this trick?
thanito said:
Meaning? Is there a way to install microG and have everything working without this trick?
Click to expand...
Click to collapse
I don´t think so. Maybe you take a look into this thread:
https://forum.xda-developers.com/hu...-to-google-notifications-gms-sketchy-t4142659.
Especially the first post will answer your question, and also #13 of the OP:
https://forum.xda-developers.com/showpost.php?p=83212197&postcount=13
Flying Fox said:
I don´t think so. Maybe you take a look into this thread:
https://forum.xda-developers.com/hu...-to-google-notifications-gms-sketchy-t4142659.
Especially the first post will answer your question, and also #13 of the OP:
https://forum.xda-developers.com/showpost.php?p=83212197&postcount=13
Click to expand...
Click to collapse
Thanks mate, it starts getting a bit more clear now[emoji16]
Sent from my ELS-NX9 using Tapatalk
I also noted that in my setting menu when I select Google account it just keeps loading, is it the same in yours?
P.s: yesterday I inserted my sim cards and got a notification for 154 update, finally.. [emoji23] (although I won't be doing the update until I get this working)
FOR the time being, with my device as is, I would say that I could use it if I had Google home working (my local food app suddenly started to work), even though I am getting the error page when I open apps, since it seems that at the same time apps are working. Any solution on that?
Sent from my ELS-NX9 using Tapatalk

Google Search App keeps updating itself, any way to prevent this?

Hey guys,
I just discovered that the Google Search App (incl Assistant) keeps auto updating on all my devices, although Play Store is set to "manual".
This shouldn't happen at all, find this rather shady.
Has anyone any clue how to block this behavior? I'm rooted, just in case you might ask.
Thanks!
You might be able to at least block it from connecting to the web using netguard.
@shaftenberg
Simply disable automatic updates of apps:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jwoegerbauer said:
Simply disable automatic updates of apps:
Click to expand...
Click to collapse
Well, as stated in OP, automatic update is disabled in Play Store.
That's why I'm so annoyed because Google App (velvet.apk) doesn't respect the setting.
@SmawtPho20 I don't want to block the Play Store completely, that's not a workaround by itself
Has someone successfully signed velvet.apk so that it won't be recognized by Play Store but still working?
[edit]
I just have tried to sign velvet.apk with another key and installed it as system app, but it crashes then. This isn't a solution.
Magisk debloater module to debloat it.
Karma Firewall, uses almost no battery, freeware.
Or...
If you don't use wifi, set to update by wifi only
pl1992aw said:
Magisk debloater module to debloat it.
Click to expand...
Click to collapse
Well, I do not want to remove the Google App - I just do NOT want it to auto-update it by itself. I mean, come on, the user setting is "do not update" and Google App and Youtube keep updating nevertheless. Gladly I use Youtube Vanced, so because of the other signature, auto update doesn't work.
But Google App force closes when signing with another key.
I'm using the voice search feature alot, this is the only purpose for the app in my case. So I need velvet.apk / Google App.
OR: Has anyone an idea where to get voice search only? This is baked in unfortunately as far as I know.
Voice search? Bixby's big sister
Just more invasive Gookill data mining.
You're not the customer, you're the product.
You know like cattle...
shaftenberg said:
Has anyone an idea where to get voice search only?
Click to expand...
Click to collapse
Try Google Go ?
blackhawk said:
Voice search? Bixby's big sister
Just more invasive Gookill data mining.
You're not the customer, you're the product.
You know like cattle...
Click to expand...
Click to collapse
Your post is not useful at all, please stop trolling if you don't have any helpful things to say.
Stumbled upon many messages of you in the past few hours regarding Play Services and Battery drain and it seems, you simply hate Google but your "advices" do not help as they are out of logic in the corresponding threads.
@pl1992aw Google Go does not provide a system wide voice messaging unfortunately, but thanks for the hint!
shaftenberg said:
Your post is not useful at all, please stop trolling if you don't have any helpful things to say.
Stumbled upon many messages of you in the past few hours regarding Play Services and Battery drain and it seems, you simply hate Google but your "advices" do not help as they are out of logic in the corresponding threads.
@pl1992aw Google Go does not provide a system wide voice messaging unfortunately, but thanks for the hint!
Click to expand...
Click to collapse
shaftenberg said:
Hey guys,
I just discovered that the Google Search App (incl Assistant) keeps auto updating on all my devices, although Play Store is set to "manual".
This shouldn't happen at all, find this rather shady.
Has anyone any clue how to block this behavior? I'm rooted, just in case you might ask.
Thanks!
Click to expand...
Click to collapse
Simply my opinion. You called it "shady" yourself.
So stop stumbling like a smuck
shaftenberg said:
Hey guys,
I just discovered that the Google Search App (incl Assistant) keeps auto updating on all my devices, although Play Store is set to "manual".
This shouldn't happen at all, find this rather shady.
Has anyone any clue how to block this behavior? I'm rooted, just in case you might ask.
Thanks!
Click to expand...
Click to collapse
I'm struggling with the same issue. The voice-to-text was wrecked by the last update. Uninstall update and everything is good again. I have also disabled auto update on the Play Store and it keeps updating. All I can figure is that there is an update file saved on the phone that it is accessing. Does anyone know if it is possible to find/ delete the update file? FWIW, I am not rooted on this device (S20).
tacotory said:
I'm struggling with the same issue. The voice-to-text was wrecked by the last update. Uninstall update and everything is good again. I have also disabled auto update on the Play Store and it keeps updating. All I can figure is that there is an update file saved on the phone that it is accessing. Does anyone know if it is possible to find/ delete the update file? FWIW, I am not rooted on this device (S20).
Click to expand...
Click to collapse
Try clearing the system cache.
Hard reboot.
SDMaid might be able to find/delete the corpse file on a non-root phone. I use the old Samsung 360° powered Device Care* to clear system logs which works well.
*firewall blocked due to potential CCP spyware
blackhawk said:
Try clearing the system cache.
Hard reboot.
SDMaid might be able to find/delete the corpse file on a non-root phone. I use the old Samsung 360° powered Device Care* to clear system logs which works well.
*firewall blocked due to potential CCP spyware
Click to expand...
Click to collapse
Well, I cleared system cache and the app cache and it came back again this am.
Do you happen to know what directory the update file may be saved in and any clues on file name to look for?
Someone on another site recommended disabling Play Store and switching to a different apk app, which sounded promising. My main concern though is that I had already disabled "auto update" on the PS for the Google app and it keeps doing it- so either the file is already on my phone and the app is updating from there, or PS could be ignoring my selection...
tacotory said:
Well, I cleared system cache and the app cache and it came back again this am.
Do you happen to know what directory the update file may be saved in and any clues on file name to look for?
Someone on another site recommended disabling Play Store and switching to a different apk app, which sounded promising. My main concern though is that I had already disabled "auto update" on the PS for the Google app and it keeps doing it- so either the file is already on my phone and the app is updating from there, or PS could be ignoring my selection...
Click to expand...
Click to collapse
I keep Playwhore package disabled unless I need it. It will constantly run in the background, at start up etc. I don't use wifi, my wifi is always disabled so I set it to auto update by wifi only.
Nothing updates on my 10+ unless I authorize it to. Updates are way overrated and many times not in your best interests.
You can try locking it down with Karma Firewall. On Pie and below it's valuable logging feature is full functional. Thank Google for the limited app resources change starting with Q.
Karma uses almost no battery. A great app.
tacotory said:
I'm struggling with the same issue. The voice-to-text was wrecked by the last update. Uninstall update and everything is good again. I have also disabled auto update on the Play Store and it keeps updating. All I can figure is that there is an update file saved on the phone that it is accessing. Does anyone know if it is possible to find/ delete the update file? FWIW, I am not rooted on this device (S20).
Click to expand...
Click to collapse
Finally there is someone with the same problem Not that I like it, but now I don't feel that stupid anymore.
It seems, that Google pushes updates to Google App and Youtube regardless of the user settings in Play Store. But Youtube can't be updated automatically, because I'm using Youtube Vanced and the auto-update fails (haha).
So I suspected that a velvet.apk signed with another key would help, but this crashes immediately at start.
I haven't found a solution yet other than disabling Play Store, but this isn't a workaround for me. If you enable PS again, it will silently update Google App anyway in that short time frame.
I don't even know if Play Store is the culprit or the Google Play Services. If I had to guess, I'd tend more to the Play Services, but I really don't know.
What do you mean with "update file"? The apk to be installed will be downloaded either in a temp directory which isn't accessible without root, or it will be stored in the cache partition which you can safely clear in your recovery (Vol Up & Power). But I assume, deleting the apk wouldn't solve the problem as it has been installed already then.
Goggle Assistant and/or Quick Search maybe the culprit(s). I have both disabled along with Google Backup Transport and Framework.
I'm running on Pie as well as the factory load for most of the Google apps including Gmail and maps. I don't have this issue.
It may have something to do with Google account settings; there are many spread out in a big mess. Go through them all. I disabled most of them including Firebase and casting.
Gookill sucks.
Well, I am several days now without the app updating. Seems the solution was to disable the Google Play Services (not Play Store) app. Not sure if it is temporary or permanent of if it will cause long-term issues, but for now I have the voice-to-text interface that actually works good.
tacotory said:
Well, I am several days now without the app updating. Seems the solution was to disable the Google Play Services (not Play Store) app. Not sure if it is temporary or permanent of if it will cause long-term issues, but for now I have the voice-to-text interface that actually works good.
Click to expand...
Click to collapse
I'm just curious to see if this held or not. I've been dealing with the same thing with my SwiftKey keyboard. The Google app completely ruins speech to text on it. And the more you roll it back, the more frequently it wants to update. I've been fighting it for months and so far the only thing that I found are suggestions that require me to root which I kind of grew out of several years ago.
It is working. I had it backwards in my previous post though. You need to disable Play Store (not Play Services). Disabling Services kills a majority of apps.
I use Swiftkey also, but I don't think it has anything to do with Swiftkey. Swiftkey just uses the Google voice-to-text.
Once Play Store is disabled you have to go the the Google app and uninstall updates. The only negative I have experienced is that you have to enable PS again when you need to download a new app from the store (expected) which will mean uninstalling updates again.

Question Gboard's Assistant voice typing is jacked

Anyone have any suggestions on how to get the Assistant voice typing option working in Gboard? I'm at my wits end trying to figure this sh!t out and believe I have tried everything I can find on the Internet, as well as my own tinkering. Everything was working fine, but then all of a sudden this morning it stopped and the Assistant voice typing option is grayed out saying You can't currently use Assistant voice typing. The following are things I've tried
clearing data/cache for Gboard, as well as the Google app - still says You can't currently use Assistant voice typing
removed my Google non-gmail account
uninstalling Gboard (beta) and Google app (beta), which leaves you with the system default versions - same message
updated Google app (beta) from Play Store - Assistant voice typing needs an update. Connect to Wi-Fi to automatically download
leave Gboard settings, go back and message returns - You can't currently use Assistant voice typing
switched to non-beta of Google app via APKmirror - same result as the beta
updated to non-beta of Gboard - You can't currently use Assistant voice typing
what else haven't I tried??
Hi, it seems like you are as desperate as I was about that stupid greyed out option. I searched for days until I found a solution at least for my case. Perhaps it also works for you.
These are the instructions I followed:
1. Go into Assistant Settings and select Language (Account-Settings -> Google Assistant -> Sprachen (German for Languages))
2. Remove secondary Language by clicking on it and in Radial-Menu selecting keine (German for "None") right at the top.
3. Go into Gboard-Settings, into Voice typing. Now the option of Assistant Voice Typing should be available. Activate it!
4. Go back into Language-Settings for Assistant and add secondary Language again. After that just check it the Assistant Voice Typing is still activated in The GBoard settings.
You might have to give it some time to download the necessary files. I first thought it did not work, but when I checked again a bit later, it did!
Hope this helps.
vielfalter said:
Hi, it seems like you are as desperate as I was about that stupid greyed out option. I searched for days until I found a solution at least for my case. Perhaps it also works for you.
These are the instructions I followed:
1. Go into Assistant Settings and select Language (Account-Settings -> Google Assistant -> Sprachen (German for Languages))
2. Remove secondary Language by clicking on it and in Radial-Menu selecting keine (German for "None") right at the top.
3. Go into Gboard-Settings, into Voice typing. Now the option of Assistant Voice Typing should be available. Activate it!
4. Go back into Language-Settings for Assistant and add secondary Language again. After that just check it the Assistant Voice Typing is still activated in The GBoard settings.
You might have to give it some time to download the necessary files. I first thought it did not work, but when I checked again a bit later, it did!
Hope this helps.
Click to expand...
Click to collapse
I believe I may have come across your post in my searches and unfortunately I have checked there to see if there were any secondary languages that may have caused this and there are none =(
I ran into the same problem when I added Spanish to my languages for Gboard. Then after that, Google voice assisted typing worked intermittently. There were times that it didn't work, and then times that it did.
My remedy was sticking to just an English keyboard and flashing a whole new rom since I do it every month. I also wiped user data, because I thought whatever caused the problem was in user data.
Then it started working again. Whatever it is by Google, it's a nasty bug.
I've noticed in the settings, it says that I can't use it at times, but when I go to use it, it works perfectly fine.
Another thing is, if you're rooted, you can used rBoard to enable the flag NGA(New Google Assistant), but you will have to first do the fix for the flags by pasting the files they give into your /data/data/ folder to fix whatever Google did to the keyboard that breaks rBoard at the moment.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
rester555 said:
I ran into the same problem when I added Spanish to my languages for Gboard. Then after that, Google voice assisted typing worked intermittently. There were times that it didn't work, and then times that it did.
My remedy was sticking to just an English keyboard and flashing a whole new rom since I do it every month. I also wiped user data, because I thought whatever caused the problem was in user data.
Then it started working again. Whatever it is by Google, it's a nasty bug.
Click to expand...
Click to collapse
yes, I feel the same way in that it's a nasty bug that is somehow related to languages. tried too many things that I don't remember now, but I believe this started happening after I had added Japanese as a second language somewhere. removing any traces of it did not fix it and I fear unless it's fixed that the only way to fix now is to either wipe or find the cause and report it...
Curiousn00b said:
I've noticed in the settings, it says that I can't use it at times, but when I go to use it, it works perfectly fine.
Another thing is, if you're rooted, you can used rBoard to enable the flag NGA(New Google Assistant), but you will have to first do the fix for the flags by pasting the files they give into your /data/data/ folder to fix whatever Google did to the keyboard that breaks rBoard at the moment.View attachment 5765073
Click to expand...
Click to collapse
do you have a link to this rBoard app? searches turn up rBoard theme manager, but the screenshots of the app do not look anything like yours... are you saying that rBoard breaks or GBoard when it comes to fixing the files in /data/data? does this mean you run this fix from time to time to get NGA working?
dimm0k said:
do you have a link to this rBoard app? searches turn up rBoard theme manager, but the screenshots of the app do not look anything like yours... are you saying that rBoard breaks or GBoard when it comes to fixing the files in /data/data? does this mean you run this fix from time to time to get NGA working?
Click to expand...
Click to collapse
That's correct. It does a lot of things actually. You can even make your own custom themes for GBoard as well as enable different flags that aren't enabled by default.
Here's the XDA link for rBoard linking to the downloads.
[APP] Rboard Theme Manager
*require root* Rboard Theme Manager Manager app for Google Gboard keyboard app. Continuation of Magisk module "Rboard themes" with more customizations and themes. Rboard Themes are not overlays but just additional themes for Gboard app...
forum.xda-developers.com
There's been an uprise lately with XDA vs Telegram and whatnot, but based on what I read on the other thread, this doesn't violate the rules since you're not required to join the group to see this post, so...
Rboard Themes
New fix for flags until we figure it out why this happens: • Download • Extract it to /data/data/com.google.android.inputmethod.latin/shared_prefs • Force close Gboard flags should work now
t.me
This post here will tell you what to do do get rBoard working correctly. Root is required and you have to do this every time you update GBoard since it'll replace what you've done. You can turn off updating so you don't have to do it every time.
Feel free to PM me(or post here so others can see) and I'll happily guide you through whatever you need help with so that you get the hang of the app.
dimm0k said:
Anyone have any suggestions on how to get the Assistant voice typing option working in Gboard? I'm at my wits end trying to figure this sh!t out and believe I have tried everything I can find on the Internet, as well as my own tinkering. Everything was working fine, but then all of a sudden this morning it stopped and the Assistant voice typing option is grayed out saying You can't currently use Assistant voice typing. The following are things I've tried
clearing data/cache for Gboard, as well as the Google app - still says You can't currently use Assistant voice typing
removed my Google non-gmail account
uninstalling Gboard (beta) and Google app (beta), which leaves you with the system default versions - same message
updated Google app (beta) from Play Store - Assistant voice typing needs an update. Connect to Wi-Fi to automatically download
leave Gboard settings, go back and message returns - You can't currently use Assistant voice typing
switched to non-beta of Google app via APKmirror - same result as the beta
updated to non-beta of Gboard - You can't currently use Assistant voice typing
what else haven't I tried??
Click to expand...
Click to collapse
If you are rooted there are some Magisk mods that screw up ASI, which can impact voice input among other things. Pixilify screwed things up for me
K1nsey6 said:
If you are rooted there are some Magisk mods that screw up ASI, which can impact voice input among other things. Pixilify screwed things up for me
Click to expand...
Click to collapse
I was in fact rooted and using Pixelify... were you able to fix whatever issues you had with Pixelify? seems like disabling it as a test does not fix anything on my end regarding this issue...
Possibly trying to disable every accessibility will work. Tried it and after a day or so it worked(not grayed anymore)
dimm0k said:
I was in fact rooted and using Pixelify... were you able to fix whatever issues you had with Pixelify? seems like disabling it as a test does not fix anything on my end regarding this issue...
Click to expand...
Click to collapse
I had to factory reset it. I tried uninstalling ASI updates first with no luck. After a clean install everything works perfectly, without Pixelify. I lost voice text, live translate, Now Playing, and transcribe. I'm sure there were other features that it broke.
The only Pixelify mod I enabled was unlimited Photos storage.
TheShinyEnd said:
Possibly trying to disable every accessibility will work. Tried it and after a day or so it worked(not grayed anymore)
View attachment 5765557
Click to expand...
Click to collapse
I did try this... at least for the ones I actually touched/enabled, but that never helped =(
K1nsey6 said:
I had to factory reset it. I tried uninstalling ASI updates first with no luck. After a clean install everything works perfectly, without Pixelify. I lost voice text, live translate, Now Playing, and transcribe. I'm sure there were other features that it broke.
The only Pixelify mod I enabled was unlimited Photos storage.
Click to expand...
Click to collapse
yes, after your mention and my original suspicions I decided to look more closely into this Pixelify module. what I found and confirmed is that even if you only enable the unlimited Photos storage, there are other things that get installed/modified and one of them is ASI!! I've gone through the install script, as well as the files included in the module to comment out everything not dealing with the unlimited Photos mod. for extra measure I also removed the unneeded APKs and whatever else I could find from the module and repackaged it as a custom module for my own use. so far... it seems to be working!!
Just putting in my thoughts on the whole Pixelify thing, but I said I avoid using that module since it's used to enable Pixel features on non-Pixel devices. Since we already have a Pixel, it changes a lot of settings when everything already works fine.
Other have claimed the other Pixelify(app) doesn't work for them, but maybe you guys can try it as well. Don't know if you guys were apart of the other thread or not, but open it, select Pixel XL, click force stop(grant root), then open Google Photos and back up something. After that, check the description of it at the very very bottom for this tag in the screenshot below.
As for Assistant Voice Typing, you'll have to use rBoard to manually enable it. I've linked it in my other post above with the fix to get it working.
Curiousn00b said:
Just putting in my thoughts on the whole Pixelify thing, but I said I avoid using that module since it's used to enable Pixel features on non-Pixel devices. Since we already have a Pixel, it changes a lot of settings when everything already works fine.
Other have claimed the other Pixelify(app) doesn't work for them, but maybe you guys can try it as well. Don't know if you guys were apart of the other thread or not, but open it, select Pixel XL, click force stop(grant root), then open Google Photos and back up something. After that, check the description of it at the very very bottom for this tag in the screenshot below.
As for Assistant Voice Typing, you'll have to use rBoard to manually enable it. I've linked it in my other post above with the fix to get it working.
Click to expand...
Click to collapse
what is this other Pixelify app that you have in the screenshot?? didn't know there was a frontend for it...
dimm0k said:
what is this other Pixelify app that you have in the screenshot?? didn't know there was a frontend for it...
Click to expand...
Click to collapse
GitHub - Xposed-Modules-Repo/balti.xposed.pixelifygooglephotos: Pixelify GPhotos
Pixelify GPhotos. Contribute to Xposed-Modules-Repo/balti.xposed.pixelifygooglephotos development by creating an account on GitHub.
github.com
It requires LSPosed. Once enabled, just open the app, set it to Pixel XL and click force stop. After that, try backing something up and then check to see if you have what I had in the screenshot above.
dimm0k said:
yes, after your mention and my original suspicions I decided to look more closely into this Pixelify module. what I found and confirmed is that even if you only enable the unlimited Photos storage, there are other things that get installed/modified and one of them is ASI!! I've gone through the install script, as well as the files included in the module to comment out everything not dealing with the unlimited Photos mod. for extra measure I also removed the unneeded APKs and whatever else I could find from the module and repackaged it as a custom module for my own use. so far... it seems to be working!!
Click to expand...
Click to collapse
Does flashing your modified module fix the issue or do you have to factory reset to revert the changes made to the ASI? I have the same problem where my now playing isn't working properly. Voice text, live translate, and transcribe seems to work well. I'm hesitant to factory reset the phone just for the now playing feature.
chaos193 said:
Does flashing your modified module fix the issue or do you have to factory reset to revert the changes made to the ASI? I have the same problem where my now playing isn't working properly. Voice text, live translate, and transcribe seems to work well. I'm hesitant to factory reset the phone just for the now playing feature.
Click to expand...
Click to collapse
you can think of my module pretty much as a gutting of the original module so only the relevant bits pertaining to unlimited photos remain therefore it will not fix the issue without doing a factory reset unfortunately. you may be able to revert the changes by examining all the changes done and reversing them
Curiousn00b said:
GitHub - Xposed-Modules-Repo/balti.xposed.pixelifygooglephotos: Pixelify GPhotos
Pixelify GPhotos. Contribute to Xposed-Modules-Repo/balti.xposed.pixelifygooglephotos development by creating an account on GitHub.
github.com
It requires LSPosed. Once enabled, just open the app, set it to Pixel XL and click force stop. After that, try backing something up and then check to see if you have what I had in the screenshot above.
Click to expand...
Click to collapse
I am considering the LSPosed approach as it does seem cleaner... I know a lot has changed since the XPosed days, but does LSPosed all SafetyNet to pass enough for GPay to work?

Categories

Resources