I understand many people avoid Bixby like the plague. Nevertheless I've noticed the wake command Hi Bixby doesn't work on Oreo. It stopped working on my S9+ almost out of the box. If I reboot the phone it works for five minutes or so. Then it stops working. You can see a little icon blip in the status bar as you say Hi Bixby but that's it nothing happens otherwise.
Just upgraded my S8+ to Oreo and it's now broken as well... Malfunctioning just like the S9+.
The S9+ was setup as a new device didn't use the S8+ as a restore source.
Just curious if I'm the only one who noticed what would seem to be a glaring problem.
Thanks for any feedback!
Sent from my SM-G965U using Tapatalk
I've experienced this too.....intermittently, it does come back without a reboot.....intermittently......
Any resolution to this issue? I have the same problem with my S9+.
Have you guys been to Samsung apps as there's been a few Bixby updates through there over the past few days
I'm yet to try Bixby I need to look into what Bixby does first.
I have noticed if you clear cache and data and setup bixby it works till the phone is locked. I have reported this to Sammy but am yet to get a positive response. Once I do I'll update here.
I have also picked up that the wake up command stops working after x amount of time. The clear cache route sorts it out, but then after x amount of time it stops working again. Pressing the button still works, just not the voice part. Very frustrating
Related
No idea why this has happened but want to see whether anyone else experienced issues after updating firmware to OD1 and if there is a fix.
Seems the norification panel flashes when scrolling through and scrolling up and down through text is no longer smooth.
ixnayondahombre said:
No idea why this has happened but want to see whether anyone else experienced issues after updating firmware to OD1 and if there is a fix.
Seems the norification panel flashes when scrolling through and scrolling up and down through text is no longer smooth.
Click to expand...
Click to collapse
yeah my VZW S6 edge 128GB just started doing the exact same thing over the weekend. It's so frustrating! I would say it first started when all of "my" media sounds (for texts, email, ringtones, etc.) all of sudden stopped working and could not be detected by apps & the OS. Then, out of nowhere, the notification pane would flash when pulled down AND I was unable to use the power button to reset the device (when holding down the button, the power menu would appear & quickly disappear without giving me a chance to make a selection).
I took it back to the Verizon store and of course, all they want to do is a full factory reset. I haven't done it yet but when the guy force-restarted it (holding Vol Down, Home, & Power), the problem seemed to go away. I rooted the phone the next day, de-bloated more than a few apps & froze TouchWiz w/ TB but the notification pane flashing glitch & just overall sluggish system performance has since returned. Since no one anywhere seems to be reporting any such performance, I suspect a hardware issue so I will be making an exchange before my 14-day return period expires.
What have you done to fix your issue?
Possible Fix?
stumbled across a few threads in regards to various graphics issues: try rolling back your Android System WebView update in the Application Manager and then reboot your phone, it seems to have cleared up some of the performance problems for me...but only time will tell if this "fix" holds for the long-run
justian007 said:
yeah my VZW S6 edge 128GB just started doing the exact same thing over the weekend. It's so frustrating! I would say it first started when all of "my" media sounds (for texts, email, ringtones, etc.) all of sudden stopped working and could not be detected by apps & the OS. Then, out of nowhere, the notification pane would flash when pulled down AND I was unable to use the power button to reset the device (when holding down the button, the power menu would appear & quickly disappear without giving me a chance to make a selection).
I took it back to the Verizon store and of course, all they want to do is a full factory reset. I haven't done it yet but when the guy force-restarted it (holding Vol Down, Home, & Power), the problem seemed to go away. I rooted the phone the next day, de-bloated more than a few apps & froze TouchWiz w/ TB but the notification pane flashing glitch & just overall sluggish system performance has since returned. Since no one anywhere seems to be reporting any such performance, I suspect a hardware issue so I will be making an exchange before my 14-day return period expires.
What have you done to fix your issue?
Click to expand...
Click to collapse
Yeah I couldn't fix it...I ended rolling back my firmware to the OC1 and starting again. But now my Music apps don't recognise music in the storage file (Walkman app). This phone seems to have the strangest glitches!
s6 glitching as well after recent update
After recent update my s6 *international version randomly starts scrolling through the open apps.
I have a video of it on youtube if anyone is interested. s6 glitch. I may decide to root it and see if it goes away with CWM.
Recent apps button thinks I'm pressing it after recent update- Galaxy S6 & Galaxy S5
I have a Galaxy S5 that's getting pretty old. About a week ago, immediately after a system update, my phone started acting strange. It was as if I was pressing and sometimes holding the recent apps button. Constantly. I could sit the phone down and watch it go to town showing the recent apps, then closing it, then showing them again. It made it almost impossible to use the phone. I'd try to type a text message or URL and I'd get one or two letters typed before it would do it again. It was maddening.
After a lot of research and seeing that other people had similar problems, I was able to find an app called "All in One Gestures" and set the recent apps button to not react when it's long pressed. That seemed to work, although it's a bit of a temporary solution as the problem continues when I turn my phone on before the app loads.
Anyway, I chalked this up to having an old phone and was looking forward to getting an S8 soon anyway.
But here's the odd thing.. last night, my mother called me about her Galaxy S6. She had downloaded a system update. Her phone says "Software updated to G920VVRS4DQD1" Android 7.0 Nougat. Anyway, immediately after the update she said her phone started acting strange. She said the power button was controlling the volume and the volume button was controlling the power, and that she couldn't type anything because menus kept popping up. So sure enough, I came to her house today and realized the exact same problem is happening to her phone as was mine. I wasn't able to duplicate the power/volume button problem she mentioned, but I realized the recent apps button is continually thinking it's being pressed. So after starting in safe mode and making sure she hadn't downloaded any new apps recently, I installed the All in One Gestures and it fixed the problem, mostly, (for now) on her phone.
My questions are... is this a known problem with this update? And does anyone know how to permanently fix it?
We have different phones, different carriers (Sprint for me, Verizon for her) and don't live in the same home. It seems too coincidental for it to happen to both of our phones so close together. When I googled "G920VVRS4DQD1" it appears that's a firmware update exclusive to Verizon.
Short of rooting or flashing the phones (my fiance could probably do that for us), does anyone know how to permanently fix this?
We could try a factory reset, but I'm worried it would force me to download the update again and we'd be back at square one.
Sorry for the long post, just wanted to be thorough. Any insight would be appreciated.
I bought an S9+ on launch day long story short it lasted 2 weeks before it would just shut down itself anytime you put it to sleep (screen off). I figured out after doing some tests and research that it would only do it when the fingerprint scanner was turned on. I sent it to Samsung which if anyone has had the pleasure of dealing with their customer service knows it's a nightmare to say the least. At least 2 week turnaround time but in the end they did come through and send me a brand new in box s9+.
Fast forward about a month later the new one is doing the EXACT same thing. If I turn the fingerprint scanner off and just use facial unlock it works fine. I really don't want to go through their customer service again and be without a phone for 2 weeks. I think this very well could be a software issue though factory reset does not solve the issue neither does erasing fingerprint and re entering them.
Has anyone else experienced this? I saw searching google that it is actually an issue others have had and like me, their replacements have all done the same thing. I am yet to find a thread with a solution though. What do you guys think? I'm actually wondering if perhaps rooting it and putting a custom rom on it would help.
Honestly, I have not heard of this before. After you try with fingerprint can you turn the device on at all?
Do you have any apps that may in the background that captures button inputs or fingerprint apps that capture slide movements or anything?
Scott said:
Honestly, I have not heard of this before. After you try with fingerprint can you turn the device on at all?
Do you have any apps that may in the background that captures button inputs or fingerprint apps that capture slide movements or anything?
Click to expand...
Click to collapse
Nope it seems to go off within seconds with the fingerprint scanner enabled. Even if I try to wake it up with the power button it seems to be dead. I've had the phone for about a month now and haven't recently added any new apps. I don't believe I have any apps that would be capturing anything. Is there any app I could use to check and see if perhaps I have something app related thats causing this?
I do believe it's gotta be software related.
You can type *#0*# in the dialer, then go to sensor and scroll down to find fingerprint test
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..
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.