Hi,
I have an S9+ with Rogers in Canada, which was recently upgraded to Android pie. Ever Since I have not been able to use Google assistant when the phone is in sleep mode. Prior to the update, I was able to say "OK Google: set the timer for xxx minutes", when the phone was in sleep mode. But now it doesn't work anymore, other than vibrating. It still works on other screens, just not when the phone is asleep.
I called Samsung but they were useless telling me that I need to press the home button and that it has always been so and that nothing changed with Android Pie but that is BS.
Can other Pie users please verify, that OK Google works on your phone when it is in sleep mode and if anyone else has the same issue as I and if you have a solution.
Thanks,
Roli
Sleep mode? as in while screen is off? or another mode?
skygear said:
Sleep mode? as in while screen is off? or another mode?
Click to expand...
Click to collapse
Yes. When the screen is locked.
My phone was like that at one point, I am on Pie now and I had to go into the settings and make sure it was set to work even when the screen was off. Took a minute to find, have you checked there?
Settings/Google/Search, Assistant and Voice/Voice/Voice Match
I have. The phone vibrates when the screen is off and I say "OK Google" but is the screen remains black until I press the home button.
I'm thinking now that perhaps it has something to do with security and not with Google Assistant. I'm going to check my security settings. Maybe there's something there.
Come to think of it, I've had that happen before, not now but some time ago. I never sound effects, never really tried, somehow it just seemed to resolve itself after a while I guess. Good luck and keep us posted, you might be right in that it has to do with some security setting or something.
This? Access with voice match?
There is also that one underneath that says 'unlock with voice match', for use if you have a screen lock set up I guess. Did you try that one as well?
YrrchSebor said:
There is also that one underneath that says 'unlock with voice match', for use if you have a screen lock set up I guess. Did you try that one as well?
Click to expand...
Click to collapse
I’m sure that’s the option the OP needs to use.
I think it's a common problem with Google assistant and potentially the same as the 'voice unlock paused' issue, I've seen people complaining about both on pixel forums as well as on here (if Google can't get it right with their own phone what hope do we have!!). There were a few steps around deleting the voice model and resetting the smart lock agent (see screenshot). I did this and retrained the voice model in absolute silence which seemed to work for a bit but has since stopped. Annoyingly it doesn't seem to take into account when I'm at home and the phone is unlocked with smart lock!
xc rider said:
I’m sure that’s the option the OP needs to use.
Click to expand...
Click to collapse
OK. Here is my screenshot of the settings that I have on my phone. Access and Unlock with Voice Match are turned on.
Let me reiterate. The phone is reacting to "OK Google" on every screen so the voice match is working.
The problem is that when when I am on the lock screen and I say "OK Google" the phone vibrates, acknowledging that it heard the prompt but it does nothing until I press the home button or power button.
Have a look at this video. (I distorted for privacy reasons the audio because my phone and tablet were reacting when I was playing back the video):
https://youtu.be/fO3nsJ215eo
I have the S9+ on Rogers and thankfully, this feature continues to work flawlessly after the upgrade as I use it often in my daily work..It actually seems to be more responsive after the update.
It can be very frustrating when the feature randomly stops working but it is usually due to an update on Google's end that causes it as I can usually fix it by going through the voice setup steps after an update..
In extreme situations you may want to uninstall and then reinstall the Google app..
Had the same problem myself and fixed it, just go to app info for Google and clear the cache and clear data, worked a treat for me
Roli001 said:
Hi,
I have an S9+ with Rogers in Canada, which was recently upgraded to Android pie. Ever Since I have not been able to use Google assistant when the phone is in sleep mode. Prior to the update, I was able to say "OK Google: set the timer for xxx minutes", when the phone was in sleep mode. But now it doesn't work anymore, other than vibrating. It still works on other screens, just not when the phone is asleep.
I called Samsung but they were useless telling me that I need to press the home button and that it has always been so and that nothing changed with Android Pie but that is BS.
Can other Pie users please verify, that OK Google works on your phone when it is in sleep mode and if anyone else has the same issue as I and if you have a solution.
Thanks,
Roli
Click to expand...
Click to collapse
I'm on an S9+ with Bell in Canada and I can still unlock my device with voice when it's sleeping even though it gave me a notice that I would no longer be able to.
For some reason I've lost the ability to voice control any of my smart devices through Google Home. Seems like a related but different problem.
That, the lack of pro video mode and the brutal battery life have really turned Pie into a nightmare for me..
Hope they release fixes for these issues or I'll have to look at flashing..
I was JUST trying to manually flash android 9 to my AT&T s9+. I bought it used, so I do not have access to the original Samsung USB (figured that was worth mentioning upfront).
After doing some research online, I found a site called firmware.science that offered the manual update files I was looking for... or so I thought. I followed the directions and flashed this firmware (G965USQU3ZRJ9), which DID give me Android 9, but it gave me a few problems...
The phone vibrates once right after screen off - I cannot find a way to turn this off.
I cannot turn the screen immediately back on after turning the screen off - For some reason, the power button stops responding after screen off for about 5 seconds. Then, I can turn the screen on again.
The phone vibrates 3 times about 3 or 4 seconds after screen off - Oddly, it is after these vibrations that the power button starts working again and I can turn the screen back on.
The phone ignores the S-View Cover - The phone just goes right to the lock screen instead of the always on display when the S-View Cover is closed.
Whenever I factory reset it, I constantly (every few seconds) get nagged by the "reminder" app crashing. This happens until I disable it.
I constantly get security alerts about com.samsung.lool and com.google.android.gms.unstable (I can't remember exactly what the packages were): "Security Notice - This Pop-up is only for Develop Phase (noship). Please do the following to fix permission denial. (QA) please attach Log(*#9900#) and screenshot(Module Info) (PL) Please assign PLM to module TG.
I cannot update the Google app from the playstore
I would like to get from this to a stable android 9 firmware. Even if that involves going back to android 8.
simmonsdeux said:
I was JUST trying to manually flash android 9 to my AT&T s9+. I bought it used, so I do not have access to the original Samsung USB (figured that was worth mentioning upfront).
After doing some research online, I found a site called firmware.science that offered the manual update files I was looking for... or so I thought. I followed the directions and flashed this firmware (G965USQU3ZRJ9), which DID give me Android 9, but it gave me a few problems...
The phone vibrates once right after screen off - I cannot find a way to turn this off.
I cannot turn the screen immediately back on after turning the screen off - For some reason, the power button stops responding after screen off for about 5 seconds. Then, I can turn the screen on again.
The phone vibrates 3 times about 3 or 4 seconds after screen off - Oddly, it is after these vibrations that the power button starts working again and I can turn the screen back on.
The phone ignores the S-View Cover - The phone just goes right to the lock screen instead of the always on display when the S-View Cover is closed.
Whenever I factory reset it, I constantly (every few seconds) get nagged by the "reminder" app crashing. This happens until I disable it.
I constantly get security alerts about com.samsung.lool and com.google.android.gms.unstable (I can't remember exactly what the packages were): "Security Notice - This Pop-up is only for Develop Phase (noship). Please do the following to fix permission denial. (QA) please attach Log(*#9900#) and screenshot(Module Info) (PL) Please assign PLM to module TG.
I cannot update the Google app from the playstore
I would like to get from this to a stable android 9 firmware. Even if that involves going back to android 8.
Click to expand...
Click to collapse
According to ATT's website, the Android Pie update for their S9+ was G965USQU3CSAB. The firmware number you downloaded does not match the Pie firmwares that ATT has on their website.
Click on the past versions to see their firmware history.
https://www.att.com/devicehowto/tutorial.html#!/stepbystep/id/stepbystep_KM1253489?make=Samsung&model=SamsungG965U&gsi=5avrp3
Wazzup.
Over at the Pixel 6 Pro fair, we have quite the number of people having problems with random reboots. We are trying to narrow it in - Android12? Pixel 6? Software? Hardware?
So - anyone here with the same set of problems? Or does the Pixel 6 not have that kind of issue?
For reference: https://forum.xda-developers.com/t/random-reboots.4353231/
I have gotten several random reboots as well. 256gb seafoam pixel 6. In particular, I was using "Frep" automation app (unrooted, used pc to start server) to do repetitive image searches in a game. Also the phone was sitting on a wireless charger while doing this. I noticed my phone felt pretty warm, wonder if it could be overheating?
Could be a naughty 3rd party app. Have you tried safe mode?
I posted this here:
P6 Bluetooth Problems
My p6 will see most some of my Bluetooth devices (laptop, tablet, TV, earbuds) . It pairs with the earbuds, but everything else it will try and pair, usually does not. If and when hen it does pair, that pairing is dropped dropped within 5 secs...
forum.xda-developers.com
My random reboots (or crashes that forced me to reboot) almost entirely stem from the wifi+bluetooth implementation. I found a sure-fire way to crash it during setup. Without word vomiting here, connecting the P6 with and to other devices has proved more difficult than any previous Pixel (for me).
mruno said:
Could be a naughty 3rd party app. Have you tried safe mode?
Click to expand...
Click to collapse
Not yet. It's also hard to "force" it (the reboots, I am not able to replicate it manually). Yesterday it just randomly happened whilst the phone laid idle next to me, thrice at the morning, about one time through late afternoon, then one time evening. I just notice the screen lighting up, then the Google logo comes, meaning the phone restarted.
I'm also pretty sure that Bluetooth/Wifi settings differed when the reboots happened, ergo at some times bluetooth was on, then when it rebooted, bluetooth was off. At no time when the reboots happened had I a bluetooth device connected. WiFi was online though, all the time.
What all the reboots have in commong though (at least the ones where I am concerned), is that the phone is just laying next to me, or somewhere, being in idle - doing as far as I know, nothing. It never happened when I used the phone or put it under load, so my P6 never "crapped" out under me. That's why I am not that concerned about this as of now, but it's certainly a nuisance to unlock the phone every time with my darn pin.
(Concerning 3rd party app) - I'd say that's unlikely. I copied my files over from my Pixel 4 XL and have not yet added one singular other app to my P6 Pro, so it should have gone naughty before my transfer over.
Hi! I experienced a big crash on the pixel 6. When I was configuring telegram, the app crashed and then the screen got black. After a minute it rebooted to the Google logo with a loading bar underneath. It was blocked in that state, but I could reboot it with volume up + power button.
I was pretty scared as the usual button down + power button didn't do anything lol
12 (SD1A.210817.036) on my pixel 6, occurred randomly when opening camera app. Happend 7-10 times.
dirtyissa62 said:
12 (SD1A.210817.036) on my pixel 6, occurred randomly when opening camera app. Happend 7-10 times.
Click to expand...
Click to collapse
Odd. I never had a problem whilst using the phone, my phone only rebooted when laying idle (even though today I had no reboots at all, alas I didn't use the phone much, maybe 2h SoT without any heavy lifting).
Something in android 12 is bugging around, maybe we have to open support tickets.
dirtyissa62 said:
Something in android 12 is bugging around, maybe we have to open support tickets.
Click to expand...
Click to collapse
I just talked for a while with a Google rep and he said that they are not aware of any reboot problems, no people over at Google Forums have reported such a thing. "We do not monitor Reddit or XDA" - so he said he opened a support ticket to the responsible team and they would look into it, he also asked that I / we report/feedback this under -> Settings -> Tips & Support -> Feedback.
We also talked about a lens flare problem, that at least the Pixel 6 Pro has. If you shot some photos where the sun is directly shining into the camera, you might want to re-check them. Most of mine have either some sort of big circular green dot in them, or a big beam of light like in a phone with a very bad HDR processing. It seems to be some sort of software glitch, he also reported that.
So hopefully those things can get fixed.
This was the follow-up email:
Thank you for contacting Google support.
This email is regarding the chat conversation we had earlier today, I'm sorry we weren't able to complete it. Hence I wanted to follow up via email to ensure all your queries have been answered.
Please re-launch the camera app and check if the issue is fixed.
Please be assured our developer team is working on this to fix it as soon as possible. We would really appreciate your kind understanding as we work on this to fix it for you.
If there is anything apart from this that needs clarification, please feel free to reply back to this email. I'll be more than happy to assist you.
Thanks!
Nova
The Google Support Team
I'm having similar restarts while phone is sitting on a table doing nothing. Tried a factory reset and was fine until overnight on charge and it happened again.
Also have had a few times where wifi has stopped working for some reason. Not sure if related.
Not had any reboots but quiet a few app crashes in especially FB will be scrolling away and bang just closes also Amazon app ,
Well that was interesting.. When it rebooted that time, it gave me an error screen saying it could not load and may be corrupt. I had two options, try again and factory reset. Try again got me back running, but I'm wondering do I got as defective device now.. or if it's software related.
So after a lot of messing around, I think I have narrowed down what may be causing my reboots. It only seems to happen when I am using "Frep" to play macros on a game while charging my phone.. the phone gets pretty hot, and reboots when I tap the screen or try to swipe home or recent apps. Maybe its overheating, or maybe its "Frep" playing naughty.. but Frep did work perfectly fine on my old $200 used Nord N10 5g. Will update if it reboots while not doing this.
no reboots or crashes so far, not doing any gaming - but using phone for email, surfing, whatsapp etc and also a work profile for MS outlook and teams.
I have/had similar issues with my Pixel 6 (128GB - europe unlocked).
I was transferring old data via cable from my old (Xiaomi Mi A1) to the Pixel 6. This resulted in sluggish performance, crashes every 15 minutes. The crashes would randomly occur and behave mostly like this:
Try to unlock phone with fingerprint sensor
Fingerprint sensor lights up, nothing happens, no haptic response
Swiping up to the PIN entry. Enter PIN and hit enter. Nothing happens. Now freeze.
Screen turns black and it takes phone to reboot on average ~7minutes
Factory Reset; Installed apps manually (standard messaging apps, no games etc), better performance, problem persists
Factory reset; boot into safemode. It now took way longer to provoke the issue. But it still happened.
After this I contacted the customer service and they will provide me with a replacement. But now after a night of idle, the phone was working for 3-4 hours without any issue at all with most of my apps installed. It just now went into a random reboot (could only notice because it asked for PIN because of the reboot). But not the 8 minute blank black screen type of reboot.
I am really unsure what is the issue at hand here. But have to say that experience is less than ideal.
Mine just happened last night, not charging or running anything 3rd party apps (all from App Store). I tried to use the camera after eating dinner and noticed that double clicking power button doesn't open the camera anymore. After unlocking the phone it appears that the phone has restarted.
Is anyone running Private DNS on their system like Adguard DNS or NextDNS? I did some searching and people reported some private DNS were causing Android to crash. It was suppose to be fixed in previous Android versions but it could be back again.
I haven't noticed any random reboots (and the lock screen will require a pin to be entered after reboot and says this on the screen, so you should know the phone rebooted). I've had the P6 since the official release date. In fact, I haven't restarted the phone in days.
I run a wide variety of apps. Some from the Play store and some sideloaded. I think that any reboot issues are probably app related. Remember that A12 is very new and the are surely still some compatibility issues that app developers haven't found/fixed yet.
I have a Nokia 7.2 ... It was running on Android 10 and I upgraded to 11 ....
I use the Google dialer app and I don't wanna use any 3rd-party apps...
My problem is before upgrading to Android 11 I had faced a bug which is when some one calls me my phone rings normally and vibrates but there's no notification popping up so I can answer or cancel even if my screen is off it turns on but a blank screen like there's no name or no swipe button to cancel or pickup ...
So I have cleared the storage for the app and uninstalled updates, I have restartey phone , ihave made a factory reset many times and etc. But the bug was still there.
Even after I upgraded to Android 11 it was there to idk why !!...
I also downgraded to Android 10 and then upgraded again to 11 but nothing happens it's still there... And I don't know what to do!
One more thing I have noticed that this thing happens when my mobile data is turned on, so when I turn it off the notification pops up normally and I can answer or cancel but otherwise it's not popping up or turns on the screen it's just showing a blank one as I said ...
Unfortunately I'm now using Truecaller but I wanna go back to the stock phone app so please help to solve this
Good evening everybody,
my Oppo Reno 4 5G is behaving strangely / not at all since yesterday. Over night I forgot to recharge it and the battery drained flat. Next morning I recharged the phone (luckily waking up by my inner clock) and found the phone unresponsive after boot. On the Screen, only a closed lock icon is visible. When I tried to use the touchscreen, the screen flickered randomly. I attached a Video file where you can see it yourself. Other than that it will respond to no input. I even tried to attach a USB Mouse/Keyboard, but it was still unresponsive to any input. When I hold press the power button, only an empty grey box appeared. Removing the SIM card made no difference. Strangely my alarm clock was working fine when it rung.
I managed to get it into the recovery-mode. When I try to do an online or local update it asks for the lockscreen password. But I use fingerprint + pattern to unlock my phone, I don't remember setting any password. I tried already a dozen passwords i used in the past and translated the pattern into numbers but no chance. I also don't have a Google Account connected to my phone, if that's relevant. The only thing I can do in recovery is to format the phone, but I see it as a last resort. My last Backup is 3 weeks old so it wouldn't hurt that much but I actually want to keep the pictures because I was on holiday for the first time since covid in the meantime.
Has anyone ideas how to troubleshoot the problem further? It seems to boot fine, only the lockscreen seems to be broken.
Phone: Oppo Reno 4 5G (european version)
Modelnr: CPH2091
OS: Android 11 / stock ColorOS
I'm thankful to any ideas!