EMERGENCY! My pixel 2 NFC is not working. Bought from Google play store.
Recently bought, or long ago? Has it never worked, or was it working and has now stopped? If it's just stopped, did anything change before that (updates for example). Does it simply not respond, or is there any error message? Is it not working at all, or just in one app (have you tried it in more than one app)? Have you ever modified the phone software? "It's not working" doesn't give anyone much to go on when trying to identify the problem.
I'll assume you've done obvious things like checking NFC is enabled or rebooting the phone.
Related
I've tried everything I can think of to resolve this, but I need some suggestions.
So - my husband finally got a smartphone, after getting by with a keyboard phone for years. I talked to him about different phones - iPhones even - and after looking at several, he took my advice and got a Droid Maxx. Of course I helped him set it up, etc. Everything went well for a day or two, but then he started getting all sorts of errors - Google sync problems, Google account sign-in problems, "Unfortunately Google play services has stopped" etc. I was able to solve most of the problems by uninstalling updates to Google Play, and a few other things. He was still having some issues, though. The phone occasionally shut itself off. So, I decided to do a factory reset.
Since then, everything is working much better. The phone hasn't shut down at all, etc. However, in the last day or two, he will get an error notification that's something like "Trouble signing in to Google Account". He has to tap the notification and enter his Google password. Then everything seems fine until it happens again sometime later. Now it's happening frequently
He has almost no apps installed. The two or three he has installed are the same ones that I have used forever on my android devices, including on my Droid Maxx and Moto X - so on the same or similar devices. I have checked every setting I can think of. He doesn't have 2-step authorization on his Google account and he never has problems with that account on his desktop, laptop, etc.
Any ideas what could be happening? He does drive through an area with no cell service every day, so that could have something to do with it, but I drive through the same no-service area, and I have never, ever had to sign in to my Google account after initial setup. Sometimes this issue crops up when he has perfectly good service.
jkmasi said:
He does drive through an area with no cell service every day, so that could have something to do with it, but I drive through the same no-service area, and I have never, ever had to sign in to my Google account after initial setup. Sometimes this issue crops up when he has perfectly good service.
Click to expand...
Click to collapse
i think that's the problem, i had issues the first time i passed by a no service area and the problem showed up ''we have trouble authenticating this account, tap here to solve'' and thats all. it solved with the tap in the notification, and never appeared again, i suspect your rom data its corrupted and i recommend reinstalling the phones firmware 4.2 or 4.4 whatever version is. that should solve the problems.
Jaocagomez;50875823 your rom data its corrupted and i recommend reinstalling the phones firmware 4.2 or 4.4 whatever version is. that should solve the problems.[/QUOTE said:
Thanks for your reply! Can you please explain what "your rom data its corrupted" means?
Also, how do I reinstall the firmware? This phone is not rooted and was updated to 4.4 KitKat OTA.
I'm hoping that it was just the magnet on his pouch case interfering with the radios. He realized that he's always noticed this problem after the phone has been in the case. This afternoon I asked him not to put it in the case as an experiment.
Click to expand...
Click to collapse
I was wondering if anyone knows if this feature will work on the HTC one M8? It hasent appeared yet but I know they are enabling it per account. Just wanted to see if it is going to work.
Here is how you can force it. Works perfectly. Also to add haven't seen it stated anywhere else yet but it will also work with the screen off WHILE charging.
https://plus.google.com/app/basic/stream/z12sczagllb1inism235gtbp1mb2j3qb204
sent from::§::
I updated Google Search from the Play store and in the settings is an option for "OK Google Detection" to choose "From any screen. Responds to your voice. Works when the screen is on or the device charging"
Since I value batter life over having to swipe up Google Now, I have not tried it.
dag079686 said:
I was wondering if anyone knows if this feature will work on the HTC one M8? It hasent appeared yet but I know they are enabling it per account. Just wanted to see if it is going to work.
Click to expand...
Click to collapse
I've read too that they are enabling it per account but I'm not so sure. A couple nights ago while I was on an AOKP rom I installed the new Google search. OK Google worked from any screen. The next morning restored a backup of my stock sense rom and installed it on there too. Strange thing is, it didn't work. I don't even have the option for OK Google from any screen in the settings. I did a search and found a couple things to try but neither worked. I flashed back to AOKP and it was still working. Don't ask me.
I did come across the article runandhide linked to but after doing a search on that, I see some end up in a boot loop after doing it. I decided to just let it be.
Anyway, if it's a per account thing, I would think it would work on any rom on a given account.
Just thought I'd throw this out there. It took me about 4 days to figure out and resolve this and couldn't figure it out. Here's what I'm running
Phone: Pixel 2
Build number: OPM1.171019.019
Magisk: v16.0
TWRP: 3.2.1-0
Android Auto: 3.0.5705
Whenever I would open AA, AA worked fine with exception to the 'Microphone' option. I validated all permissions were properly set and that I allowed AA to use voice as well as enabling 'Ok Google' but it still continued to crash with the message "Voice Commands Aren't Working Yet" . I happened to be looking for crash logs and looked at the 'tombstone' files in '/data/tombstones/' and found the following line:
Code:
/dev/ashmem/dalvik-classes.dex extracted in memory from /data/app/com.google.android.googlequicksearchbox-myLQ80LPFOqvrolYhMKlDA==/base.apk (deleted)
I wiped Dalvik/ART Cache although I didn't think this would fix it... I don't know if this had to do with that crash since there wasn't a timestamp or reference to AA but thought it was peculiar. It looks like the 'google quicksearch box' is part of the 'Google' app in Google Play. I uninstalled the 'Google' app, then re-installed (updated) it. Then opened it and went through the 3 quick steps to set it up. After doing so, I opened AA and the issue was fixed...
I hope this helps someone.
Did the issue stay fixed for you? I did the same thing (uninstalled, then reinstalled Google app updates) but the issue returned within 20 mins or so. What's extra weird is that two of my devices (Pixel XL and Nexus 6P) with the same Google account are having the same problem in the last few days, but a friend's device (Pixel XL) doesn't when used with the same radio.
Well I just checked after reading your response and something reverted/no longer working. I know it did work for a while because I played with it and used Google Assistant in AA but now it's crashing again like you've said... I guess it's not worth keeping with this process for it to only work for a few minutes... I'll have to continue looking...
I've had the versions (that I put in my first post) working together for a few weeks (with exception to AA 3.0.5705) now but I swear this issue of AA not properly working has only recently cropped up this week in the 3.0 version -- which I think has only been out for a week.
I tried rolling back to AA 2.9.XXXX and it's still not properly working so I don't have a plan at this point.
I may be speaking too early @MaSt3rGrIfF01 but it's been working 5 hours and has survived several test shutdown/reboots without AA flaking. Here's what I did on this round:
-Uninstalled Android Auto
-Removed all Magisk Modules (only left Tethering Enabler)
-Android O APT-X Libraries
-Busybox
-RAM Management
-Sysconfig Patcher
-Systemless TZData -Rebooted Phone
-Went to 'Google' app settings, performing 'Clear All Data' and 'Clear Cache'
-Uninstalled 'Google' app
-Re-installed 'Google' app
-Configured 'Google' app
-Updated 'Google' app
-Sideloaded 'Android Auto' APK version 2.9.5749
-Rebooted Phone
.... Since then, I haven't experienced a crash
...and by 7PM last night, while not touching the phone at all since my last update here, I picked it up to check and it was busted again... Back at square one.
That's been my same experience so far; Erasing all data in the Google app will immediately resolve the issue, only for it to return soon after without me changing anything. Another thing I've noticed is that once the issue rerurns, I will periodically notice alerts saying the Google app has become unresponsive or suddenly closed.
I also tried wiping my Pixel XL and used a different Google account on it. I was unable to get the issue to reproduce on the same device when using this second Google Account. At this point, it seems like there's an issue somewhere in my Google Account, rather than in the device itself. So far I'm stumped, to say the least.
That's strange that a Google account would be the result of that behavior. Nonetheless, I will give that a try. I have two Google accounts tied to my phone so I removed one and re-did my previous steps. I will give it a few hours (hopefully days) before I confirm if this might be the solve.
One thing I noticed is that immediately after wiping my phone and updating the Google app, if I look in the settings for Google Assistant I'll see that it's missing options for music (and a few other things that I don't remember right now). I cannot get the issue to reproduce in this state. If I either erase the data in the Google app or use the phone normally for a period of time (between 6 to 30 or so hours), the missing options will return. As soon as those options are back, the issue starts back up. After that, if I wipe the Google app again, it will work normally immediately but the issue will return within 20 mins or so. This issue just keeps getting stranger.
How's everything going for you so far with the other Google account?
Well I had a primary Google account that I've been using for like 8 years. Then I have another which I made this year. I had both tied to my phone. However, I removed the newer one from my phone -- all traces of it gone -- then repeated the steps from earlier.
AA worked for almost the whole day without that crashing issue. Then I started having it's normal trouble. I'm in the same place you are. We can't be the only other people experiencing this... It does make me feel slightly better that it's happening to you on a different model phone which tells me this isn't just a Pixel 2 issue.
.... but yea, still not solved on my end...
Agreed, it's really strange that I can't find anyone else online complaining about the same issues. I'll keep in touch in case I find out anything else useful.
---------- Post added at 06:11 PM ---------- Previous post was at 06:09 PM ----------
I did find this http://piunikaweb.com/2018/03/06/android-auto-voice-commands-arent-available/ and https://productforums.google.com/forum/#!msg/android-auto/GwDHrjlL3mk/Kylyw15MBgAJ
---------- Post added at 06:30 PM ---------- Previous post was at 06:11 PM ----------
After reading through that thread, it looks like the way to resolve the issue is by installing a new version of the Google App (7.22.24.21). I've never been prompted to update to it, but you can find the APK online https://www.apkmirror.com/apk/google-inc/google-search/google-search-7-22-24-release/. So far so good, I'll let you know if the issue returns.
Nice find! And agreed. I just updated Google app via the apk and the issue wasn't happening again. Didn't even have to uninstall/reinstall/clear cache
If you are having these issues (see title), what worked for me was to disable, uninstall or freeze (if rooted) the google app. This means you'll lose "ok google", google lens, etc. everything related with the assistant, but, for me is worth it because sending sms messages to have them show "sending..." eternally while knowing they were received drove me nuts.
Try uninstalling or disabling the google app if you are having issues like this.
Good Day.
nichobrooks said:
If you are having these issues (see title), what worked for me was to disable, uninstall or freeze (if rooted) the google app. This means you'll lose "ok google", google lens, etc. everything related with the assistant, but, for me is worth it because sending sms messages to have them show "sending..." eternally while knowing they were received drove me nuts.
Try uninstalling or disabling the google app if you are having issues like this.
Good Day.
Click to expand...
Click to collapse
This worked exactly once for me. Has it solved your problem indefinitely? If so, do you know why?
channeledbymodem said:
This worked exactly once for me. Has it solved your problem indefinitely? If so, do you know why?
Click to expand...
Click to collapse
As long as I had the Google app disabled everything worked flawlessly (I tested for months)
Recently I had to restore my phone to factory (locked bootloader, wipe, etc)
Now Google and my phone can work together again.
Not sure what changed, but so far so good.
This oddly worked for me
have been having this problem since June 2019with a Honor V10. I too found disabling the Google app was a work around. Strangely yesterday I managed to enable Google update all apps and the sms sent fine for about 10 hours now I'm back to the same problem again. I have also restored the phone and reinstalled all apps from scratch rather than use a back up. With the same issue occuring I presume there must be a software conflict somewhere with the apps I download.
Did anyone find a long term solution that enable the Google app to run?
Cheers n Gone Nick
Whoever stumbles here from google, I had same problem today and instead of disabling Google app, just killing it worked for me.
Sup folks,
so something very annoying is happening on my Pixel 7 Pro.
I first noticed it yesterday when i couldnt get any ,,Press Yes to Sign in,, Prompts on my Pixel 7 anymore.
I then reinstalled the whole phone and everything worked as before.
To explain ,,working as before,,:
- Google One Backup has its grpahical backup with the Loading bar etc
- I can get Sign In Prompts
So this worked up until about 4-2 Hours ago.
I reset cache and Data on Google, Playstore and Google Play Services with Airplane Mode and restarted my Device because i had them on the Zygisk List.
Now its the same as before. I cant get any SignIns and my Google One wont backup and or will just show its bareones UI when pressing backup and even refusing to backup at all.
Oh yeah and going into Settings and Google then pressing on Devices to get the Devicelist just unlimited Loads me.
Im also not able to link my Chromebook at all.
EDIT:
I wanna metion that it now after like waiting some time, did a full backup.
It also showed me the prompt of signin but said it was ,,smth smth expired,, and linked me to my Devices.
The phone shows up all fine in Find my Device too!
But still no Sign In Prompt and chromebook working.... NOR the device tab
Anyone else or just me?
Seems like the Module from @Displax caused this.
Once removed Chromebook worked like a charm.
But it takes some time to break, which is weird.