Related
I'm currently running a rooted version of the OxygenOS Open Beta 9. I tried to enable the Google Assistant, it does work, but I can't enable "Trusted Voice" or "Say Ok Google any time". In other words, I need to be in the app for it to detect my voice. It says that "This feature is currently unavailable for this language." even though I'm running English (US), and updated it with the latest update(s). I've seen people mentioning Xposed Framework, however that would be for Android 6 (Marshmallow), there is no Xposed for Android 7 (Nougat) yet as far as I know. Perhaps someone has had the same issue as I have, or has Google Assistant working properly.
Also, another thing I've noticed on many phones is that you need to activate the screen in order for the device to start detecting your voice. Is there any way that this can be "fixed" so you can do it while screen is off?
EDIT:
Now it seems like the only problem is that the voice model isn't saving. Because when I say "Ok Google", it'll react, but it'll ask me to teach it how to recognize my voice. This happens over and over.
EDIT2:
It's partly working. I was reading the thread about enabling it on any Android device. (http://forum.xda-developers.com/showpost.php?p=70146853&postcount=2047), ChopAssistant is a partly fix. It'll not work in Pixel Launcher at least (I have that installed on my OP3), I've not had any success elsewhere. It won't let you enable the "Say "Ok Google" anywhere", it'll either be grayed out or automatically turn itself off. As far as I understand, this is a known issue, and no known full solution for Android 7 on OP3 yet, well, not for the OOS Beta 9 at least.
If you happen to have a solution, I'd love it if you shared it with me!
I have assistant enabler xposed module and it works with the screen off and everywhere else.
Edit: accidentally quoted op lol
MrWilsonxD said:
I have assistant enabler xposed module and it works with the screen off and everywhere else.
Edit: accidentally quoted op lol
Click to expand...
Click to collapse
The problem with Xposed is that it doesn't yet support Android 7. Otherwise I'd do that too.
Nozemi said:
The problem with Xposed is that it doesn't yet support Android 7. Otherwise I'd do that too.
Click to expand...
Click to collapse
Oh : didn't know you were on n.. Not sure then.. Sorry man.
MrWilsonxD said:
Oh : didn't know you were on n.. Not sure then.. Sorry man.
Click to expand...
Click to collapse
No problem, hopefully someone has a solution, or finds a solution. Unfortunately I'm not very experienced with such things, I know how to search and find guides, but that's about it hehe.
have you tried to flash nano gapps over the rom? doing that usually solves my problems with the google app.
---------- Post added at 06:12 PM ---------- Previous post was at 06:07 PM ----------
and after you do that, here's a guide how to enable the assistant just like on the pixel
http://forum.xda-developers.com/android/software/guide-how-to-enable-google-assistant-t3477879
bombaglad said:
have you tried to flash nano gapps over the rom? doing that usually solves my problems with the google app.
---------- Post added at 06:12 PM ---------- Previous post was at 06:07 PM ----------
and after you do that, here's a guide how to enable the assistant just like on the pixel
http://forum.xda-developers.com/android/software/guide-how-to-enable-google-assistant-t3477879
Click to expand...
Click to collapse
Assistant is enabled and installed, just not detecting "Ok Google" command. Never heard of nano gapps. Mind linking me? Or confirm that this; http://opengapps.org/ is the same thing as what you were talking about. And thanks for your reply! Much appreciated!
EDIT:
Tried to flash the nano package I found there, it got me further. Now I can at least enable it, but it'll instantly disable it again. However, earlier it was grayed out with the message specified in my OP.
Nozemi said:
Assistant is enabled and installed, just not detecting "Ok Google" command. Never heard of nano gapps. Mind linking me? Or confirm that this; http://opengapps.org/ is the same thing as what you were talking about. And thanks for your reply! Much appreciated!
Click to expand...
Click to collapse
well, if you're on beta9 i guess you have a working twrp-recovery. what you need to do is, download the nano gapps package (be careful to pick the 7.0 version for arm64!) from opengapps.org, and flash the zip via recovery, then clear cache and dalvik. this should do a clean install of the google app on your rom and solve it's problems.
however, before you do that, make sure you have set assistant up properly, enabled voice detection on any screen in the google app under settings, and take a look into battery optimization settings, and disable the optimization of the google app. try that first, if it doesn't help, continue flashing
hope you get it working, "ok google" is an awesome feature
bombaglad said:
well, if you're on beta9 i guess you have a working twrp-recovery. what you need to do is, download the nano gapps package (be careful to pick the 7.0 version for arm64!) from opengapps.org, and flash the zip via recovery, then clear cache and dalvik. this should do a clean install of the google app on your rom and solve it's problems.
however, before you do that, make sure you have set assistant up properly, enabled voice detection on any screen in the google app under settings, and take a look into battery optimization settings, and disable the optimization of the google app. try that first, if it doesn't help, continue flashing
hope you get it working, "ok google" is an awesome feature
Click to expand...
Click to collapse
I can't enable it under voice settings. It doesn't allow me, it keeps automatically disabling itself. Earlier it was grayed out. (as I mentioned in my previous reply) And I can't find anything to disable in battery optimization. I have aggressive doze and high power usage apps disabled. This is getting really frustrating! Why couldn't Google just release this for everyone!? xD Got any more ideas as to why the on/off switch keeps turning back to off automatically?
Nozemi said:
I can't enable it under voice settings. It doesn't allow me, it keeps automatically disabling itself. Earlier it was grayed out. (as I mentioned in my previous reply) And I can't find anything to disable in battery optimization. I have aggressive doze and high power usage apps disabled. This is getting really frustrating! Why couldn't Google just release this for everyone!? xD Got any more ideas as to why the on/off switch keeps turning back to off automatically?
Click to expand...
Click to collapse
you say your phone's language is english us, but what about the google voice language? try to go to this settings, and long-press english to set it as default
bombaglad said:
you say your phone's language is english us, but what about the google voice language? try to go to this settings, and long-press english to set it as default
Click to expand...
Click to collapse
That is indeed English (US) right now, I could try to change it to something else and back again, just to see what happens.
if that doesn't do anything, you'll have to go the flashing way
it surely has nothing to do with your location, as i'm in slovakia (central europe), it's not available in slovak but i can use "ok google" just fine in english, although on resurrection remix...
bombaglad said:
if that doesn't do anything, you'll have to go the flashing way
Click to expand...
Click to collapse
I did that as well, it seems that it doesn't save my voice training. Because it does react to me saying "Ok Google" now, but it wants me to teach it how to recognize my voice.
Nozemi said:
I did that as well, it seems that it doesn't save my voice training. Because it does react to me saying "Ok Google" now, but it wants me to teach it how to recognize my voice.
Click to expand...
Click to collapse
then it must be a bug with the beta, sorry.. i suggest you check out resurrection remix, it is really fast and stable, and full of customizations
bombaglad said:
then it must be a bug with the beta, sorry.. i suggest you check out resurrection remix, it is really fast and stable, and full of customizations
Click to expand...
Click to collapse
Perhaps, but I'll stick with this, and will be waiting for Xposed to support Android N. Thanks for your help anyway, much appreciated!
Nozemi said:
I did that as well, it seems that it doesn't save my voice training. Because it does react to me saying "Ok Google" now, but it wants me to teach it how to recognize my voice.
Click to expand...
Click to collapse
I have the same issue as you... how did you get it to react to saying "Ok Google"... I've flashed pixelfy, when that didn't work, I ran the GetAssistant app... I installed GApps... It still will not react to Ok Google from any screen other than the Assistant screen.
dpicts said:
I have the same issue as you... how did you get it to react to saying "Ok Google"... I've flashed pixelfy, when that didn't work, I ran the GetAssistant app... I installed GApps... It still will not react to Ok Google from any screen other than the Assistant screen.
Click to expand...
Click to collapse
Still haven't found a good solution. I believe it works in the OTA version of OOS (running Android 6) with Xposed Framework and Assistant Enabler. I'm actually trying that right now. As for enabling it on Android 7 (N), it's a known issue for now, as far as I read at least. So I guess we'll just have to wait for a complete solution. Otherwise, you can read my OP for a incomplete fix. Under the "Edit 2" part I wrote something about this.
It was suggested I come over here and see what's going on. I've got a 5t with Oxygen.
I've never been able to get Android Auto to load, once. It always says "Something went wrong - Google Play services doesn't' seem to be working right now."
I can't Force Stop the Google Play services, or deactivate it. I've cleared my cache. I don't have a Android Device Management App installed either.
I enrolled and updated to the Google Play services Beta, but haven't still can't force stop it either.
Where do I go from here?
I don't know about this issue.
But I can say I use Android auto daily in my car and have no issues.
I have a Volkswagen caddy 2017 and use ob3
I sideloaded the app because it is not officially released in my country. I use version 3.0.
@dashbarron,
I have the exact same problem . I've also gone the play services beta route with no joy. I've tried literally every possible solution I've come across on the web, still no joy. I can't get past this.
Did you ever get AA to work? How?
Thanks!
-Warren
dashbarron said:
It was suggested I come over here and see what's going on. I've got a 5t with Oxygen.
I've never been able to get Android Auto to load, once. It always says "Something went wrong - Google Play services doesn't' seem to be working right now."
I can't Force Stop the Google Play services, or deactivate it. I've cleared my cache. I don't have a Android Device Management App installed either.
I enrolled and updated to the Google Play services Beta, but haven't still can't force stop it either.
Where do I go from here?
Click to expand...
Click to collapse
I don't know if you have used Android auto before, so maybe you really like it and my advise maybe of no use to you. But while it is good to use, I soon reverted back to using split screen, top half for nav and bottom half to easily switch between music or radio or whatever else you want, even set up a YouTube video before you get going if it's something that doesn't require your focus on it, with gestures it's safer than messing around with the complicated controls in my car! And I have the plug in version of Android auto built into the car, I literally only plug it in when I have my daughter's on board so they can call out ok Google for whatever tune they want on. Anyway that's how I roll when driving and I'm driving all day everyday, hope maybe I saved u some time getting it working
Anyone having this problem where call doesn't connect with error of 'Call not sent'? This is doesn't happen when connected to Wi-Fi but happens most of the time otherwise and I have to re-try 2 times (sometimes 10 times) to get the call connected. I have tried clearing data for phone app but it didn't help. I am not seeing any reports on it in any beta discussion so I am guessing its not a beta problem? It never happened before the beta update and I installed the beta update from total reset instead of just updating.
Yes. Only happens when I am on Bluetooth connected to my car. I gave to call from the phone app instead of my driver control.
"Call not sent" error on Samsung Note10
I'm having a similar issue with my Note10, just shows "Call not sent.", whether connected or not to Android Auto or any other dock/bluetooth, it doesn't seem to fix the problem.
I have tried several active sim cards from different carriers which work fine in other phones, but in the Note10 I can only access the web and text. When trying to make a call with full signal bars and LTE next to it, it just shows "Call not sent". I've done all the usual restart, full factory reset from the recovery menu, even reflashed it via Odin with the latest firmware (N970U1_UES2BTA1) three times, then factory reset again, but it's doing the same. It seems to be a hardware problem, not a software glitch.
By the way, my phone is unlocked and I have checked the IMEI to make sure it's not blacklisted. I have also examined the charging port for any liquid damage, but it's completely clean and shiny. When I dial the test code *#0011# to compare the network status screen against a Samsung S9's, I've noticed that the "MIPI TEST SUCCESS" and "ASDiv: PASS THROUGH" at the bottom of the screen are MISSING on the Note10, which might have something to do with the failed calls.
Also, out of curiosity I have installed a couple of different phone dialers (Google Phone and Simpler Dialer), but the outcome is the same "Call not sent.".
Evidently there's a hardware problem with the Note10 series (some or all), because Samsung's own forum full of similar complaints.:=(
Same problem. Getting call not sent
Was not issue in Android 9. Only Android 10.
Galaxy note 10+ unlocked version on tmobile.
I've also had other random Bluetooth issues.
this issue got so bad, i am not able to make calls, unless i make multiple attempts.
so i just upgraded to the S20 Ultra. Same issue!!
Here are other factors and connected devices.
Connected to a Ford vehicle (Sync; 2017 Explorer)
Connected to Samsung Active2 smartwatch (but issues remained even when watch disconnected).
I've also tried to unpair / re-pair. To no avail...
Help!
Also here:
https://us.community.samsung.com/t5...-Android-Auto-after-upgrading-to/td-p/1077007
I am really glad I blocked updates, I am still running on Pie
billa said:
I've noticed that the "MIPI TEST SUCCESS" and "ASDiv: PASS THROUGH" at the bottom of the screen are MISSING on the Note10, which might have something to do with the failed calls.
(
Click to expand...
Click to collapse
I have an Exynos Note 10+ I don't seem to have this problem and when I did the test you did I got "MIPI TEST SUCCESS" but nothing about ASDiv.
Could this be a problem with the Snapdragon chipset?
ultramag69 said:
I have an Exynos Note 10+ I don't seem to have this problem and when I did the test you did I got "MIPI TEST SUCCESS" but nothing about ASDiv.
Could this be a problem with the Snapdragon chipset?
Click to expand...
Click to collapse
It certainly could be, on all other phones I always see the "MIPI TEST SUCCESS" in test mode, but not on the N970U.
It might be fixed with a new update, unfortunately there's still nothing newer available than UES2BTA1 as of right now.
I have the feeling it's a hardware issue rather than software, in which case it's not going to be fixable, short of replacing the main board.
No idea, why this started happening mostly after the last update.
billa said:
It certainly could be, on all other phones I always see the "MIPI TEST SUCCESS" in test mode, but not on the N970U.
It might be fixed with a new update, unfortunately there's still nothing newer available than UES2BTA1 as of right now.
I have the feeling it's a hardware issue rather than software, in which case it's not going to be fixable, short of replacing the main board.
No idea, why this started happening mostly after the last update.
Click to expand...
Click to collapse
Are you able to rollback?
As long as the bootloader is the same you might be able to go back to an update prior to the problem.
Not 100% sure but I believe the 5th number from the right in the build number is the bootloader version. Just need to make sure it is the same and you might be able to fix...
Sorry if I'm rambling, working on 3 hours sleep...
ultramag69 said:
Are you able to rollback?
As long as the bootloader is the same you might be able to go back to an update prior to the problem.
Not 100% sure but I believe the 5th number from the right in the build number is the bootloader version. Just need to make sure it is the same and you might be able to fix...
Sorry if I'm rambling, working on 3 hours sleep...
Click to expand...
Click to collapse
Right, but usually same bootloader version updates are just maintenance or critical security updates only.
Looks like some major changes have happened in the latest update, which could be causing the no call issue.
Just checked, and it's still the same version available.
Version: N970U1UES2BTA1/N970U1OYM2BTA1/N970U1UES2BTA1/N970U1UES2BTA1
OS: Q(Android 10)
I found a solution!
Google Voice app was the culprit. I uninstalled and so far it has been working for 2 days without issues. Tried this on both my new S20 and the Note 10+.
kingsfan33 said:
I found a solution!
Google Voice app was the culprit. I uninstalled and so far it has been working for 2 days without issues. Tried this on both my new S20 and the Note 10+.
Click to expand...
Click to collapse
But it's happening for others with or without the Google Voice app installed.
You may have had a different issue.
Chiming in late to the game with a Samsung Galaxy S20. I never had this issue with the new OS on my S10 but it started happening with the S20. It's also intermittent. Sometimes it works. I have tried unpairing and repairing. I have tried deleting the bluetooth device and reconnecting it. All to no avail. At least other folks recognize this issue and hopefully Samsung issue an update soon.
i have regerts (spelled wrong to be funny)
winol said:
I am really glad I blocked updates, I am still running on Pie
Click to expand...
Click to collapse
As nice as this phone is--I am annoyed with myself that I upgraded to Android 10--everything worked so great with 9!!! I wish there was a way to go backwards. I might investigate that, actually. I have a little downtime as of late.
I finally updated to android 10, ui 2.0, and, luckly, all is working fine, only thing I notice is that battery seems to last a little bit less…
i have Android 10 ui 2.1 with infinity rom 6.0 rom N975FD and everything works perfect including goodlock 2020
winol said:
I finally updated to android 10, ui 2.0, and, luckly, all is working fine, only thing I notice is that battery seems to last a little bit less…
Click to expand...
Click to collapse
For me, Android 10, whether UI 2.0 or 2.1
battery.... standby, is exceptional good .!
I am a power user, eg theming etc
so i don't worry or have time to worry,
about SOT ETC....
For me what matters is when , my device is sleeping.....!
/ if anything
is draining my device battery etc.
( Ihave about 200./300 apps.)
Suggestion... factory reset or did you already done that.?
See examples of device overnight
standby etc.
kingsfan33 said:
I found a solution!
Google Voice app was the culprit. I uninstalled and so far it has been working for 2 days without issues. Tried this on both my new S20 and the Note 10+.
Click to expand...
Click to collapse
THIS WAS THE FIX FOR ME! I'll have to research why Android 10 isn't playing nicely with Google Voice, but I'm glad I can hit call and it goes though, instead of hitting "send" over and over and over again!!!
S10+ Exynos, running Android 10 stock - same problem. Annoying as hell!
I can't uninstall GV because I use it for international calls.
Edit: BTW - it definitely seems to be affected by connected BT headset. As soon as I turn the BT headset off I am able to make the call (using MPOW headset, don't remember the exact model).
billa said:
But it's happening for others with or without the Google Voice app installed.
You may have had a different issue.
Click to expand...
Click to collapse
I have had this issue so many times on my S20+ unlocked. Swipe and touch to call just doesn't work. I saw this thread today when I had multiple call not sent instances. I force stopped Google voice and the problem disappeared. If I have to make an international call, I just to start Google Voice.
dhebi111 said:
I have had this issue so many times on my S20+ unlocked. Swipe and touch to call just doesn't work. I saw this thread today when I had multiple call not sent instances. I force stopped Google voice and the problem disappeared. If I have to make an international call, I just to start Google Voice.
Click to expand...
Click to collapse
Are you (were you at the time) connected to a BT headseat? It happens to me only when my headset is connected, and not just one - two different types of headseats and also happened once or twice when the phone was BT connected to my car. As soon as I disconnect the BT, all calls can be completed without a problem.
Anyone else having problems with AA? When I unplug from either of my head units, the phone AA app fires up and music keeps playing on the phone. Sometimes it's just the music that keeps playing in the background, so I have to start the app on the phone to stop it.
Oh, and then in AA Waze will show my car traveling sideways on the screen instead of actually orienting the road top to bottom.
It's working fine for me on the N9860. I have next to the system app version of AA also AA for phone screens installed so I can set preferences for AA on my phone. No display issues at all. I do experience sound routing problems in combination with some sound assistant settings. Multi Sound and Separate App Sound conflict with AA audio routing. You need to keep rhse settings off in Sound Assistant.
Sent from my SM-N9860 using Tapatalk
Works Fine for me on My AT&T Note20 Ultra 5G 512GB Snapdragon
Running On SM-N986U Galaxy Note20 Ultra 5G 512GB
https://youtu.be/SXmO8l6iyJs
Damn, I was really hoping it was a known issue.
I have not had the audio issue however I do see that my car is not oriented properly on the map.
Make sure location setting is set for greatest accuracy.
Try clearing the System cache on the boot menu.
Try clearing cache and data if necessary on associated apks .
Is the GPS sensor working properly... check it with maps make sure it's not intermittent.
Yea, if I hop over to maps, it's running correctly. I've uninstalled and reinstalled waze. It also only does it with AA. If I unplug the phone, waze runs fine.
Waze is pretty worthless; it's dependent on Goggle maps running in the background to operate.
Just pretty face with no brains.
Try it in Safe Mode. If it runs correctly, it's a 3rd party apk.
blackhawk said:
Waze is pretty worthless; it's dependent on Goggle maps running in the background to operate.
Just pretty face with no brains.
Try it in Safe Mode. If it runs correctly, it's a 3rd party apk.
Click to expand...
Click to collapse
Uhh, what?! They use totally different mapping services.. They're based off open street maps. It will run just fine with maps uninstalled.
Also, android auto doesn't work in safe mode.
barry99705 said:
Uhh, what?! They use totally different mapping services.. They're based off open street maps. It will run just fine with maps uninstalled.
Also, android auto doesn't work in safe mode.
Click to expand...
Click to collapse
You can't uninstall gmaps normally... it's running in the background when waze is being used.
When I package blocked gmaps, waze went doa; it needed it.
Works just fine on my phone with maps disabled. Waze doesn't use any code, or services from maps. They're still a separate entity, just owned by google.
barry99705 said:
Uhh, what?! They use totally different mapping services.. They're based off open street maps. It will run just fine with maps uninstalled.
Also, android auto doesn't work in safe mode.
Click to expand...
Click to collapse
barry99705 said:
Works just fine on my phone with maps disabled. Waze doesn't use any code, or services from maps. They're still a separate entity, just owned by google.
Click to expand...
Click to collapse
Haven't used it in 2 years. I saw this behavior though.
Blocked or disabled? I blocked it so gmaps couldn't run in the background which it loves to do.
Just an update, Waze told me to just lock north up, which kinda sucks as a fix. September update didn't fix the issue.
I have this persistent music issue junt one time, but I just can´t get the notifications in the right language. Don't matter if I set the car and everything on my phone to my native language, it always read the notifications in english
rafafischer said:
I have this persistent music issue junt one time, but I just can´t get the notifications in the right language. Don't matter if I set the car and everything on my phone to my native language, it always read the notifications in english
Click to expand...
Click to collapse
This is a know issue with AA and Android 10 that is not affecting only Brazil. Google acknowledged it AFAIK but a fix was never delivered. Not sure if someone with Android 11 that used to have this problem can report if it still happens.
I read somewhere (sorry, can't recall where) that if you change the assistant language to English somehow it will read your messages in the right language in AA. Or maybe it was about changing the phone language to English and keeping the assistant in your language.
May have ended up causing more confusion than helping.
antinun said:
This is a know issue with AA and Android 10 that is not affecting only Brazil. Google acknowledged it AFAIK but a fix was never delivered. Not sure if someone with Android 11 that used to have this problem can report if it still happens.
I read somewhere (sorry, can't recall where) that if you change the assistant language to English somehow it will read your messages in the right language in AA. Or maybe it was about changing the phone language to English and keeping the assistant in your language.
May have ended up causing more confusion than helping.
Click to expand...
Click to collapse
I've tried this process of change the Assistant language, but not solved the issue... Maybe Android 11 came to save us :laugh:
I'm hoping someone can help me with this issue. I have an x80 Pro the CN version. I unlocked the bootloader and rooted it with Magisk. After a few days my Google Play Services stopped working. I reset my phone and again it works a few days then stops. I finally found a video where it shows how to setup everything on Magisk so that your SafetyNet doesn't detect the unlocked bootloader. I did all that, passed all the tests, it worked a few days then the same thing. When I run a SafetyNet checker it just says can't access Google Play Services. Anything that uses Google Play Services doesn't work or is delayed. Here's the weird part.. If I connect my phone through USB to my car or my computer, the play services work well but the minute I unplug it, back to not working again. So something is making this happen and I am not sure what.. If anyone has any experience with this and could help, it would be greatly appreciated.
Go to settings/Account and sync.
Open Google Service and deactivate this. Wait a Moment and activate. Working.
morpheus620 said:
Go to settings/Account and sync.
Open Google Service and deactivate this. Wait a Moment and activate. Working.
Click to expand...
Click to collapse
I just tried. Same thing unfortunately. I have no idea why it's doing this.
Music&Art said:
I'm hoping someone can help me with this issue. I have an x80 Pro the CN version. I unlocked the bootloader and rooted it with Magisk. After a few days my Google Play Services stopped working. I reset my phone and again it works a few days then stops. I finally found a video where it shows how to setup everything on Magisk so that your SafetyNet doesn't detect the unlocked bootloader. I did all that, passed all the tests, it worked a few days then the same thing. When I run a SafetyNet checker it just says can't access Google Play Services. Anything that uses Google Play Services doesn't work or is delayed. Here's the weird part.. If I connect my phone through USB to my car or my computer, the play services work well but the minute I unplug it, back to not working again. So something is making this happen and I am not sure what.. If anyone has any experience with this and could help, it would be greatly appreciated.
Click to expand...
Click to collapse
Have you turned on "Google Basic Services" in settings? Most resellers turn this on for you and install the Google Play store before shipping the device, but it is turned off by default. If you have done a factory reset then it would be off. Turning it on is essential to maintaining permanent Google Play services.
frcraig said:
Have you turned on "Google Basic Services" in settings? Most resellers turn this on for you and install the Google Play store before shipping the device, but it is turned off by default. If you have done a factory reset then it would be off. Turning it on is essential to maintaining permanent Google Play services.
Click to expand...
Click to collapse
Yeah. I turned it off then back on to make sure. But same thing would happen. What I did now is I downgraded it to a previous firmware version and then did the whole safety net process again. It seems to be okay now. Honestly I think it started happening after I would go into the clear cache mode where it wipes the phone cache but not the data on your phone. I haven't done that since I did this and it seems to be okay now. I don't know why clearing the cache would cause this to happen since I like doing that every once in a while. It was very weird because I would connect my phone to USB and the services would come back. Unplug it, they would be gone. Something was triggering it to do that and I have no idea what.
If you have removed com.vivo.pem every firmware update is a problem with google authentication.
Restore com.vivo.pem and you get rid of the issue.
maxant69 said:
If you have removed com.vivo.pem every firmware update is a problem with google authentication.
Restore com.vivo.pem and you get rid of the issue.
Click to expand...
Click to collapse
Well, not only after the update the Google services turn off. In my case every third day they just turn off. There exist more frustration issues, because they can be turned on again easily. But still... It's annoying.