Hello guys,
I am having this issue with my device - sometimes when I press the home button the Voice talk / command powered by Vlingo starts. I always press the button just once (I understand that it should happen when one double-presses the home button) and it is very annoying :-(
Note, that I have Settings/Motion/Double tap turned off as well. Is there any way to fix this or do you have any idea what may be wrong??
Thanks in advance!
Sent from my GT-I9100 using XDA App
while in the motion settings, you can see the tutorial clip and that double tap has nothing to do with the home button, but with double tapping the top side of the device to start voice control instead of saying "hi galaxy". so even with that switched off, your device will react to hitting the home button twice and does not really help diagnose the initial problem.
either you have a slight hardware defect in the home button, a software issue (or maybe user error). since hardware would be more severe, let's see the software side first. what exact rom do you have? device rooted or not? anything that could mess with voice input (connected bluetooth hands free, market vlingo or other tts or stt software installed...)?
also, just to exclude user error, let another person try.
P.S. are there special circumstances when this happens? like only from deep sleep, only when charging, with a connected headset, running certain apps or whatever?
Chef_Tony said:
while in the motion settings, you can see the tutorial clip and that double tap has nothing to do with the home button, but with double tapping the top side of the device to start voice control instead of saying "hi galaxy". so even with that switched off, your device will react to hitting the home button twice and does not really help diagnose the initial problem.
either you have a slight hardware defect in the home button, a software issue (or maybe user error). since hardware would be more severe, let's see the software side first. what exact rom do you have? device rooted or not? anything that could mess with voice input (connected bluetooth hands free, market vlingo or other tts or stt software installed...)?
also, just to exclude user error, let another person try.
P.S. are there special circumstances when this happens? like only from deep sleep, only when charging, with a connected headset, running certain apps or whatever?
Click to expand...
Click to collapse
Hello, thanks for your reply. I am running the device with an unmodified SW i.e. stock rom (having a branded phone from orange slovakia), no rooted just some apps installed from the android market. It is XXKE4/XWKE7, running android 2.3.3. I dont use bluetooth or handset nor dock or anything like that.
The issue seems to be completely random to me, while I usually notice it during browsing web with opera, but it happens with more apps. I don't know what is tts or stt sw, nor market vlingo. If you would like to know some more details please let me know what would be relevant for you.
I already thought about the hw issue, but I am not sure if they would accept the warranty claim as it is quite random. I thought there would be some way to completely disable voice talk as I dont expect to use it anytime in the future anyway...
As of the user error, it happens both to me as well as to my gf while using the phone for common internet use.
Sent from my GT-I9100 using XDA App
ok, that gave us something to work with. for future reference, when asking a question like this, it might speed up the process by giving as much information in the initial post as possible and let me explain why:
the fact that you use your unrooted stock rom tells me, that it is not a common and maybe reported bug that comes with a custom rom, and with an unrooted device, it is rather unlikely, that you screwed up a system component like this.
bluetooth, docks and handfrees could influence the voice input and its triggering by having their own triggers, but that is not the case.
if it happens to other people with your phone as well, it excludes your personal behaviour, tremors or whatever (no offense, you never know, just to cover everything, some people are shaky).
if it happened only in a special state, like only while sleeping for a minute or while charging, it would ensure, that it has something to do with deep sleep.
about the other things: with tts i was referring to text to speech, the engine that reads out display content, like incoming calls, text messages or navigation instructions, stt refers to speech to text, like voice input, saying hi galaxy, telling where to navigate or dictating notes...
vlingo is the engine that is used for voice talk and voice command and there is also a 3rd version, that can be downloaded on the android market, coming with yet other features and having them all present and maybe screwed up settings might have influenced anything there, however, this doesn't seem to be the case either.
so this leaves few options for how to proceed. in your place i would start off with reading this thread: http://forum.xda-developers.com/showthread.php?t=1097153
it deals with home button issues and a theory on how the home button sometimes might react as much as 15-30 minutes later than initially pressed, which might coincide with an actual press and being registered as a double press (although that's a stretch at best).
and when it comes to a next step, if you made sure, that does not apply to you, i would be uncertain, which way to go. a factory reset might help, but if, after hours of setting the device up again, you realize there has not been any change, it was nothing but work. then there are 2 things left:
either flash a newer rom using odin and any rom from here: http://forum.xda-developers.com/showthread.php?t=1075278 (full guide and download links included)
OR decide to send it in for warranty first and see what's what.
flashing a rom might solve your problems but influence your warranty state, if not done correctly and cautiously, which would make sending it in risky.
sending it in first and not getting that bug recognized or repaired for free would mean you might end up with weeks without your phone and/or a huge bill and the same issue as before.
i guess i would get a usb jig, read up on flashing, try several stock roms, not root the device and see if the bug is gone, if not, flash back to stock, make sure the flashing is not traceable and then try a local store or your carrier for a hardware replacement or repair.
Related
I need a way to be able to voice dial at any time even with the phone locked or with some other app the Voice Talk open via Bluetooth, I know this is possible on Android since my old Motorola Milestone could do it and would be legal under the new laws.
My province is now getting distracted driving laws which will make using my phone illegal with how many steps it takes currently.
I refuse to give up locking my phone since I have private info on it but I need to be able to make calls by pressing the button on my Bluetooth even with the phone locked since it could even be in my jeans pocket with no way to get at it when sitting.
Currently on my GS2 I have to unlock the phone then double click the home button to bring up voice dialing or even open the voice talk app if I am in a different app.
Compared to my Milestone where I never touched it and at any time even pattern locked or in a different app I could just press the button on my Bluetooth and say "call jane" or something and it always worked.
How can I get this back? Considering the laws are coming into effect next month for me.
I would like to keep the stock Samsung voice for most time but would be willing to have a second one that works even if the phone is locked.
I also have people that want this phone but willn't buy it until I get this fixed.
Use Tasker to disable the lock pattern when connected to a bluetooth device - therefore when you disconnect from your car bluetooth, your lock pattern will re-activate.
Problem solved!
OK I have that and think I am close to setting it up but can't totally figure it out how to disable the lock screen.
All I have figured out is a profile that runs if a mic headset is connected but when I try to figure out the task it does I get stuck.
I have never used Tasker before.
This is suddenly going to be to expensive since I found out the SGS2 requires extra work to disable the pattern lock which is a extra $10 plugin and I am not even sure if I want to pay for Tasker itself after the 7 day trial.
I might try and find out how it was done on my old phone when locked.
For others that may want to kn ow here is the thread for this on a GS2
http://forum.xda-developers.com/showthread.php?t=1110307
Nope, you don't need the plugin - there's a keyguard action that you would disable, which also disables the lockscreen.
I'm trying to set this up myself, but for some stupid reason, it's not responding when I press my bluetooth button at all...
Fricken Vlingo - you suck!
k1sr said:
Nope, you don't need the plugin - there's a keyguard action that you would disable, which also disables the lockscreen.
I'm trying to set this up myself, but for some stupid reason, it's not responding when I press my bluetooth button at all...
Fricken Vlingo - you suck!
Click to expand...
Click to collapse
Are you sure that would work on our Samsung phones since they modified the locking system to use the /efs partition?
If you do get it working make sure to tell me how.
Ok so I want to convey all the relevant information without this being a mile long.
I have a o2 UK SGS2 running on a 3 sim. I have flashed on Lite'ing 6.1 with ninphetmaine 2.0.5. Up until the following, everything has been 100%.
This morning I downloaded Destinia and played it for a while. Before quitting I took a quick look at in app purchases to see if they charge ridiculous prices (they do). I'm not interested so I quickly spam back to close everything. This is when **** ****s up. OS becomes unresponsive immediately and I have no choice but to pull the battery. (power menu disappears instantly, no registered actions from soft keys or menu button in OS). No change on reboot.
I try reflashing Lite'ning. Mostly no change but I got the chance to get into task manager and uninstall Destinia/Launcher Pro.
I reinstall launcher pro, and now it works most of the time except:
1. Quite frequently the voice action app will load itself, and the unlock notification will pop up.
2. MTP notification will appear occasionally and phone will act like it's plugged in
3. Random Launcher/OS crashes. Sometimes screen on but no response from apps or OS. Sometimes screen won't turn on at all, just softkeys and darkness.
4. at first unlock after boot, camera makes standard focusing sound.
5. on boot, little popup dialog will read "in app purchases not supported in this version of android".
Really I doubt there's going to be any solution other than "wipe and reflash" but I'm really interested if anyone knows what would cause all these problems.
Cheers
. I'm not interested so I quickly spam back to close everything
Whatever that means looks to be the source of your problem..
jje
JJEgan said:
. I'm not interested so I quickly spam back to close everything
Whatever that means looks to be the source of your problem..
jje
Click to expand...
Click to collapse
what this means is that pressed back from the game's in app purchases screen, back to the main menu and then back to the Launcher, I'm sure everyone has done basically this countless times.
Fine but my dictionary defines spam as a different meaning .
But as posted that's where it all went wrong for whatever reason .
jje
Right I wipe-flashed stock 2.3.5 and it's STILL doing this. Voice actions popping up at random, all sorts of apps crashing and hanging all the time.
This has to be a hardware problem now, right?
just a stab in the dark but run a virus check.
I've never had a virus in my life, but I checked anyway and nothing.
Right so I've been watching my phone today. It's still doing random voice action popups. If I leave the phone on standard standby it will be fine for a while. It will then randomly turn on the screen by itself. The screen will stay on, if i leave it long enough the whole thing become totally unresponsive. If I press power the phone will wait a few seconds, then restart. If I don't touch it, it will just restart on its own eventually.
Can anyone recommend at least, some logging software that will let me look at the underlying OS and see what's happening when this is going on.
Is there any possibility your phone also goes to car-mode by itself?
spare parts app??
Your phone is more or less doing the same thing as mine is. It's a hardware issue from the seems of it. The voice command thing is from a dirty pin in the USB connector part which apparently isn't that hard to clean, for users in the thread below it actually helped to solve the issue. But my persisting issue is the unresponsive screen and power button causing an active screen to dim out and making the screen unresponsive..
http://forum.xda-developers.com/showthread.php?t=1174291
Im getting random voice talk and mtp etc. phone is all ovr the place. flashed litening and nimphet last week and seemed fine. used mhl hdmi cable and problems seemed to start from there.
millia90 said:
Your phone is more or less doing the same thing as mine is. It's a hardware issue from the seems of it. The voice command thing is from a dirty pin in the USB connector part which apparently isn't that hard to clean, for users in the thread below it actually helped to solve the issue. But my persisting issue is the unresponsive screen and power button causing an active screen to dim out and making the screen unresponsive..
http://forum.xda-developers.com/showthread.php?t=1174291
Click to expand...
Click to collapse
Read your thread http://forum.xda-developers.com/showthread.php?t=1278790 and your problems are down to the letter the same. I've resigned myself to it being a hardware fault and put in a service request with samsung. Wish I had better news.
Yea me too. My issue is that my SGSII was manufactured in UK so I'm at odds seeing as how I'm in America. The people at the Samsung call center referred me to the UK number so I guess I will have to bits the bullet.
Howdy! I peruse the forums quite a bit to figure out little fixes for my phone, but there are a couple problems that I haven't quite been able to find proper solutions for.
The first problem deals with the phone randomly shutting down (usually only when it's in my pocket). I've seen other posts regarding the topic, but the OPs usually stated that simply holding the power button would effectively turn the phone back on, or that the phone doesn't shutdown but rather reboots. My phone completely shuts down and requires that I take the battery out, wait 10-15 seconds, put it back in, and then hold the power button for an extended period of time in order for the phone to start up. The battery doesn't get extremely hot. It's usually around ~33-35C when it does this, but when I look at some of the other posts with similar problems, their batteries are ranging withing ~38-42C. I have seen that it may be a faulty battery, as shown in the other posts, but as I mentioned my problem is slightly different.
The second problem deals with streaming videos on browsers. Before the ICS update, I was able to stream videos on any browser, but after that OTA update I cannot. I have tried multiple browsers, including Dolphin, Firefox (my main browser), and Opera. I heard it may have to do with flash not supporting android anymore (after 4.0.x, whereas I'm only running 4.0.3), but I have checked my phone and I have Flash 11.1 already installed. The settings on my browsers are to enable plug-ins on tap (means that I would tap a video to start it, right?).
Lastly, as of now, I'm having a WiFi issue. It's not so much of an issue as a hindrance, though. Basically, I'm pretty much always in a WiFi zone, either being at home or on campus. When I get home from uni, WiFi automatically connects, no problem. When I'm at the uni, it will connect as soon as I get on campus, but when I walk from building to building, it loses connection and makes me reconnect. I go to hit reconnect, and it demands some credential password which I have never set. If I hit forget so that I can forget and reconnect to the network, it wants me to put in my screen unlock pattern. I draw the pattern to unlock it, but then it sort of refreshes and my pattern is gone and it doesn't let me continue with the process, so I have to go back to the home screen, back into settings, and clear credentials. Some posts said to continue to input incorrect passwords to allow a credential storage password reset, but that did not work. Some posts said to clear credentials, so I do that, but then I have to continuously type my login information whenever I move from class to class, which gets pretty irritating. The only way to connect to the WiFi is by disabling and reenabling the WiFi. Like I said, it's not a huge issue, rather a hindrance.
As for my phone specs, I'm not really a super tech so I haven't messed with anything. The phone is not rooted and is running Android 4.0.3. It is, however, unlocked, and I'm running it on ATT's network if that makes a difference.
Let me know if I've posted in the wrong section or anything, and if I have, I apologize. I'm not one for posting on forums, rather one to creep around and hopefully find solutions.
Thanks for your time.
Hi there.
I also want to join this topic:
1. my HTC amaze also shuts down randomly.
2. but the main thing is: can anybody help me with this WiFi issue? I can connect and use WiFi in the street, at McDonald's, at different places with public WiFi, but when it comes to connect to WiFi at my home or at other places where the WiFi is PASSWORD PROTECTED, my phone jams the network and i have to turn off WiFi on the phone and restart the WiFi router to have everything working again.
Somebody, please help
thanks in advance.
Don't know if I'm allowed to do this, but bump!
Powstriker said:
Don't know if I'm allowed to do this, but bump!
Click to expand...
Click to collapse
this is out of question phone is good. there must be way to solve this WiFi issue
418 Replies but not a single instance of input? There has to be someone that knows something about this!
Powstriker said:
The first problem deals with the phone randomly shutting down (usually only when it's in my pocket). I've seen other posts regarding the topic, but the OPs usually stated that simply holding the power button would effectively turn the phone back on, or that the phone doesn't shutdown but rather reboots. My phone completely shuts down and requires that I take the battery out, wait 10-15 seconds, put it back in, and then hold the power button for an extended period of time in order for the phone to start up. The battery doesn't get extremely hot. It's usually around ~33-35C when it does this, but when I look at some of the other posts with similar problems, their batteries are ranging withing ~38-42C. I have seen that it may be a faulty battery, as shown in the other posts, but as I mentioned my problem is slightly different.
Click to expand...
Click to collapse
Since you are stock, the only thing being that your phone is unlocked, I would say this is either a config issue or a HW issue. The simplest thing to do is to clean the battery contacts, as there is a small chance that something got on them and is causing the battery to drop out. You can also look at the battery meter in the settings menu and see if you have a sudden drop in battery power or if it entirely cuts out. May give some clues to what's going on. Finally the only other thing I can think of is to uninstall any apps that save power or mess with the power settings on the phone.
Powstriker said:
The second problem deals with streaming videos on browsers. Before the ICS update, I was able to stream videos on any browser, but after that OTA update I cannot. I have tried multiple browsers, including Dolphin, Firefox (my main browser), and Opera. I heard it may have to do with flash not supporting android anymore (after 4.0.x, whereas I'm only running 4.0.3), but I have checked my phone and I have Flash 11.1 already installed. The settings on my browsers are to enable plug-ins on tap (means that I would tap a video to start it, right?).
Click to expand...
Click to collapse
Streaming video doesn't work for me, it will for a couple seconds and then die. So now I just open all links in the youtube app, which isn't perfect but it's good enough.
Powstriker said:
Lastly, as of now, I'm having a WiFi issue. It's not so much of an issue as a hindrance, though. Basically, I'm pretty much always in a WiFi zone, either being at home or on campus. When I get home from uni, WiFi automatically connects, no problem. When I'm at the uni, it will connect as soon as I get on campus, but when I walk from building to building, it loses connection and makes me reconnect. I go to hit reconnect, and it demands some credential password which I have never set. If I hit forget so that I can forget and reconnect to the network, it wants me to put in my screen unlock pattern. I draw the pattern to unlock it, but then it sort of refreshes and my pattern is gone and it doesn't let me continue with the process, so I have to go back to the home screen, back into settings, and clear credentials. Some posts said to continue to input incorrect passwords to allow a credential storage password reset, but that did not work. Some posts said to clear credentials, so I do that, but then I have to continuously type my login information whenever I move from class to class, which gets pretty irritating. The only way to connect to the WiFi is by disabling and reenabling the WiFi. Like I said, it's not a huge issue, rather a hindrance.
Click to expand...
Click to collapse
This has got to be either a config issue or a bug in how your phone handles your uni's wifi. Your uni will have multiple wifi APs with the same SSID (but on different channels) so that you can walk around and still remain connected. My guess is that there is a bug in the wifi drivers that don't like what your uni is doing, but it's really hard to say since that stuff is generally pretty complicated...
If you can't get your power issue fixed easily I would recommend you factory reset your phone. Don't install any apps for a couple days and see if your problems persist. If the power one does then take your phone in for warranty repair. The wifi one could be a bug, which would mean a warranty repair isn't going to do anything for that so you may be screwed on that one. Unless you want to hack your phone and load a new ROM; there is a slim chance that an updated ROM will not have the same bug.
gripen40k said:
Since you are stock, the only thing being that your phone is unlocked, I would say this is either a config issue or a HW issue. The simplest thing to do is to clean the battery contacts, as there is a small chance that something got on them and is causing the battery to drop out. You can also look at the battery meter in the settings menu and see if you have a sudden drop in battery power or if it entirely cuts out. May give some clues to what's going on. Finally the only other thing I can think of is to uninstall any apps that save power or mess with the power settings on the phone.
Streaming video doesn't work for me, it will for a couple seconds and then die. So now I just open all links in the youtube app, which isn't perfect but it's good enough.
This has got to be either a config issue or a bug in how your phone handles your uni's wifi. Your uni will have multiple wifi APs with the same SSID (but on different channels) so that you can walk around and still remain connected. My guess is that there is a bug in the wifi drivers that don't like what your uni is doing, but it's really hard to say since that stuff is generally pretty complicated...
If you can't get your power issue fixed easily I would recommend you factory reset your phone. Don't install any apps for a couple days and see if your problems persist. If the power one does then take your phone in for warranty repair. The wifi one could be a bug, which would mean a warranty repair isn't going to do anything for that so you may be screwed on that one. Unless you want to hack your phone and load a new ROM; there is a slim chance that an updated ROM will not have the same bug.
Click to expand...
Click to collapse
Thank you very much for the in depth reply. I'll take a look at the battery connections some time tomorrow as it's pretty late today. Do you have any recommendations as what to clean them with? I heard erasers are pretty good cause they have the "stickiness" to pick up grime, but wouldn't the rubber inhibit connectability?
The video thing isn't too big of an issue, but eh, a fix would be nice. If there's nothing that's known of atm, that is fine as well.
As for the WiFi, I didn't know if it was a bug or something I could fix internally. It's good to know, though, that it's not something I seem to have messed up myself haha.
Once again, I greatly appreciate the response!
Powstriker said:
Do you have any recommendations as what to clean them with? I heard erasers are pretty good cause they have the "stickiness" to pick up grime, but wouldn't the rubber inhibit connectability?
Click to expand...
Click to collapse
The contacts won't be corroded because they are gold, however it could be either they aren't springy (ie they got bent) or that something is stuck on them. Just take a look, make sure they look fine and that they are making a good connection. It's most likely not the issue but you just want to rule that out, as it would obviously cause problems if your battery was being disconnected
So, as an update, I managed to fix the battery issue by actually turning my phone around in my pocket (Strangely enough, I found that if I keep the screen away from the leg and the power button facing up, rather than the screen towards my leg, the phone does not turn off.). All that's left is to find a fix for the video and WiFi. The WiFi problem has actually started to become more significant, as WiFi is no longer automatically connecting to my home internet anymore. Sometimes at uni, as well, the phone requires a complete reboot before it will reconnect rather than a WiFi off -> WiFi on reset. Any more input would be greatly appreciated ^.^
I had same restart Issue
I don't know why or how it works.
Just put a piece of paper below the battery and the restart problem is solved
Flash a kernel and see maybe the modules are messed up
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
Battery
I don't know why changing how the phone is situated in your pocket would solve the issue unless you were somehow unknowingly keeping the power button pressed down for long periods of time.
I will say I had the same issue and my suspicions lead me to the battery. Indeed, I bought a new battery and the issue has been resolved. There must have been some sort of short or default in the battery I was using that would cause my phone to randomly shut down or reboot..
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..
Currently on stock, non-rooted rom. Just restored from my smart switch backup but something was changing my ringer mode (from sound to vibrate) at random times. So, I downloaded NiceCatch in order to identify what process is doing it. When it occured, I checked NiceCatch and it says it was the AS.AudioService.onSetStreamVolume process that set ringer mode to vibrate then back to sound. Sometimes it sticks to vibrate only and I often miss calls. Any ideas how to stop this? I've already checked Bixby Routines, DND, Easy Mute, and SmartThings. They're all turned off and their not scheduled to turn on. This was not happening before the smart switch backup (I've reset the phone because I was having touch issues, turns out it was just the screen protector.)
Try clearing the system cache.
SmartSwitch can transfer the problems along to the new load. Don't use it if you can't ID the issue.
Never trust SmartSwitch as a stand alone backup for critical data as it can fail you miserably.
Done clearing the cache partition in recovery. I've also disabled all DND permissions from all apps in the settings. Let's see if it still happens. I'll post the screenshot here again from nicecatch if it still happens. If this still keeps happening, I guess I have no choice but to start from scratch. What a pain.
Yeah, I've learned not to trust smart switch ever again. Quite sad, in my opinion, it was actually better than google's backup and restore. Can you recommend some backup and restore apps? Best one I've used is Nandroid backup from TWRP. But it is only for phones with custom recovery though.
blackhawk said:
Try clearing the system cache.
SmartSwitch can transfer the problems along to the new load. Don't use it if you can't ID the issue.
Never trust SmartSwitch as a stand alone backup for critical data as it can fail you miserably.
Click to expand...
Click to collapse
Helium but it's sort of a pain. Never did a restore with it.
I just make redundant backups and load 'em the hard way. I used SmartSwitch to transfer homepage settings on my N10+'s although I accidentally included apps. I'm using Android 9 on one and the newest is running on 10.
SmartSwitch worked well... who knows?
Regardless I know not to trust SmartSwitch
As the name suggests, this is part of the Android Audio Service and it is a perfectly legitimate part of the OS. Unfortunately, the cause is going to be nigh on impossible to find out without a stack trace as the service is being called by something else and NiceCatch won't tell you that. onSetStreamVolume is a function that is called when something is adjusting the volume, be it an app or some hardware interaction. An audio/video app or another part of the OS can make this call. Hardware could be the volume buttons, inserting or removing headphones (or a faulty headphone socket thats mimicking insertion or removal) or a third party device connected to the phone such as Bluetooth headphones or a smart watch. Try disconnecting any Bluetooth headphones and smart watches and see if it happens without them connected. Disable any related apps for those devices too and see if it still occurs (update them if available). Since you have NiceCatch you must have Good Lock and that offers you SoundAssistant. If that's installed, try disabling and updating it and seeing what happens. Disable/update any audio/video apps and see if it occurs. My best guess is that because used Smart Switch, you may have restored an app thats no longer compatible thats making erroneous calls to the function. Thats all I can think of right now. It seems you have a lot of trial and error to do!
richhaynes said:
As the name suggests, this is part of the Android Audio Service and it is a perfectly legitimate part of the OS. Unfortunately, the cause is going to be nigh on impossible to find out without a stack trace as the service is being called by something else and NiceCatch won't tell you that. onSetStreamVolume is a function that is called when something is adjusting the volume, be it an app or some hardware interaction. An audio/video app or another part of the OS can make this call. Hardware could be the volume buttons, inserting or removing headphones (or a faulty headphone socket thats mimicking insertion or removal) or a third party device connected to the phone such as Bluetooth headphones or a smart watch. Try disconnecting any Bluetooth headphones and smart watches and see if it happens without them connected. Disable any related apps for those devices too and see if it still occurs (update them if available). Since you have NiceCatch you must have Good Lock and that offers you SoundAssistant. If that's installed, try disabling and updating it and seeing what happens. Disable/update any audio/video apps and see if it occurs. My best guess is that because used Smart Switch, you may have restored an app thats no longer compatible thats making erroneous calls to the function. Thats all I can think of right now. It seems you have a lot of trial and error to do!
Click to expand...
Click to collapse
Spot on.
Little doubt SmartSwitch is capable of doing this. Most times it just won't reload the app. Or it may have transfer another hidden setting?
3rd party apps can alter hidden user settings on stock phones that do not revert back even if you uninstall the app. This is rare but it happens. Saw a Google book reader app do this. Had to reinstall it, change the display setting, then finally uninstall it for good. With some patience and persistence many times you can track a hidden settings issue down and avoid a reload.
I prefer a doing clean load especially if malware caused the need for a reset. A Android load can lasts for years if you load it right and leave it be.
It's worth doing it right the first time...
blackhawk said:
Spot on.
Little doubt SmartSwitch is capable of doing this. Most times it just won't reload the app. Or it may have transfer another hidden setting?
3rd party apps can alter hidden user settings on stock phones that do not revert back even if you uninstall the app. This is rare but it happens. Saw a Google book reader app do this. Had to reinstall it, change the display setting, then finally uninstall it for good. With some patience and persistence many times you can track a hidden settings issue down and avoid a reload.
I prefer a doing clean load especially if malware caused the need for a reset. A Android load can lasts for years if you load it right and leave it be.
It's worth doing it right the first time...
Click to expand...
Click to collapse
Smart Switch isn't as smart as its title suggests. For about 80% of the apps I have installed, it only backs up the APK for the app but not the app data itself. Yes it will install all my apps on mass but I still have to set each app up individually afterwards. That makes it a useless solution. I might as well install them all fresh from the Play Store so that they are up to date too. There are some third party apps that get data backed up along with all the Samsung apps but I find virtually all games reset unless the game itself saves a cloud backup. I've never had any apps be faulty after a restore but I've only done it twice personally and I've heard plenty of horror stories from others to know its bad.
As for OP, it could be a strange setting on a smartwatch that triggers it. I can silent my phone from my watch and if it developed a bug then it could cause a situation like OPs. I'm still betting on it being a dodgy Smart Switch restore but it will take days for OP to pinpoint what actually caused it.
richhaynes said:
As the name suggests, this is part of the Android Audio Service and it is a perfectly legitimate part of the OS. Unfortunately, the cause is going to be nigh on impossible to find out without a stack trace as the service is being called by something else and NiceCatch won't tell you that. onSetStreamVolume is a function that is called when something is adjusting the volume, be it an app or some hardware interaction.
Click to expand...
Click to collapse
Ahh okay. This will be tough to trace then. I wonder if this can be traced via system tracing in developer's option. It did include system tracing for audio. I don't know what program does it need though in order to read the logs.
richhaynes said:
An audio/video app or another part of the OS can make this call. Hardware could be the volume buttons, inserting or removing headphones (or a faulty headphone socket thats mimicking insertion or removal) or a third party device connected to the phone such as Bluetooth headphones or a smart watch. Try disconnecting any Bluetooth headphones and smart watches and see if it happens without them connected.
Click to expand...
Click to collapse
Also, I did have my screen replaced recently. I did it myself, it was a reglassed screen from China (Screen with frame). Works perfectly fine though. I tested all the functions on Samsung's testing menu thing (*#0#*). All functions seem to be working fine. Except for the Grip Sensor. It doesn't seem to work correctly. It used to say "Release" when the phone was not being held and "Working" when the phone was held. Not really sure what this Grip sensor does. While being inside the phone, I also replaced the thermal pad with Thermal Grizzly's Kryonaut (Non conductive thermal paste). Though I doubt this would cause this to happen. It improved thermals indeed compared to stock.
Anyways, after the screen replacement (before the backup and restore in smart switch), I had no issues with the ringer mode. It only started occuring after the restore on smart switch.
As for the bluetooth, I use the Xiaomi Mi Band 6. Including its Mi Fit app. I tried uninstalling the app to see if the issue still occurs. It still does. So I guess it wasn't due to this app.
richhaynes said:
Disable any related apps for those devices too and see if it still occurs (update them if available). Since you have NiceCatch you must have Good Lock and that offers you SoundAssistant. If that's installed, try disabling and updating it and seeing what happens.
Click to expand...
Click to collapse
Yes, I have disabled several apps to test if the issue was gone. I also tried updating them to their newest version. Unfortunately, it still occurs from time to time. I also have SoundAssistant installed. But even though I cleared its data and cache, the problems still continues. I guess it wasn't due to this either.
richhaynes said:
Disable/update any audio/video apps and see if it occurs. My best guess is that because used Smart Switch, you may have restored an app thats no longer compatible thats making erroneous calls to the function. Thats all I can think of right now. It seems you have a lot of trial and error to do!
Click to expand...
Click to collapse
Oh okay. But upon backup and restore, I never updated the phone though (November 2021 Security Patch). So I doubt there is some compatibility problems. Maybe smart switch is just buggy. I also did some research about this issue and it turns out, it also occurs to other samsung models (S21). This seems to be a bug from smart switch that samsung hasn't fixed yet. I guess if all else fails, I have no choice but to completely start from scratch. It'll surely be a pain though because I use a lot of apps.
Thanks for the tips though. I really appreciate your reply.
I've used system tracing but not for the audio component so I'm not exactly sure what its output would be. The system traces can be viewed through Android Studio and can be very technical. If your used to debugging kernel logs you will be at home as they can be just as cryptic!
One wild thing that I'm thinking now is that the headphone socket got damaged when you replaced your screen and its triggering as if you plugged in your headphones. I'm not sure how that would result in your phone going in to vibrate but it would certainly trigger activity within the Audio Service as it contains code to check the volume limiter which is specifically for headphones. Its a possibility to consider but a wild one at that.
The grip sensor is a sensor that notifies anything that needs to know when your holding your phone. Its one of the things Samsung Health uses to guess when your asleep or not. I dont know how Sammy actually do it but I'm guessing its going to be from slight current changes on the edge of the digitizer as you grip your phone but thats a wild guess too! As for the test, the release message is a message to tell you that you need to release it not to say your currently holding it. Its a bit strange to us because you think it would say gripped or ungripped or something but its messages for a human or robotic tester, not for us.
I've not heard about Smart Switch being an issue on the S21 but I didn't get that model so I've not really read much on the issues it suffers from. Unfortunately Smart Switch is just not reliable as a backup solution. Use it to backup you content and settings but don't rely on it for backing up your apps. You need root otherwise its a manual job I'm afraid.
richhaynes said:
I've used system tracing but not for the audio component so I'm not exactly sure what its output would be. The system traces can be viewed through Android Studio and can be very technical. If your used to debugging kernel logs you will be at home as they can be just as cryptic!
Click to expand...
Click to collapse
Ahh alright. My understanding of Android software isn't really that great. I'm only self learning. I guess its better to start clean.
richhaynes said:
One wild thing that I'm thinking now is that the headphone socket got damaged when you replaced your screen and its triggering as if you plugged in your headphones. I'm not sure how that would result in your phone going in to vibrate but it would certainly trigger activity within the Audio Service as it contains code to check the volume limiter which is specifically for headphones. Its a possibility to consider but a wild one at that.
Click to expand...
Click to collapse
Headphones are completely working though. Both left and right, including the volume up, down, play/pause controls on the earphones. Headphone detection is working fine. If there was a problem with the headphone jack, there would be no sound coming out from my phone speakers or atleast it would be intermittent. But thats not what really happens on my phone.
richhaynes said:
The grip sensor is a sensor that notifies anything that needs to know when your holding your phone. Its one of the things Samsung Health uses to guess when your asleep or not. I dont know how Sammy actually do it but I'm guessing its going to be from slight current changes on the edge of the digitizer as you grip your phone but thats a wild guess too! As for the test, the release message is a message to tell you that you need to release it not to say your currently holding it. Its a bit strange to us because you think it would say gripped or ungripped or something but its messages for a human or robotic tester, not for us.
Click to expand...
Click to collapse
The grip sensor is located on the frame of the phone. It has a touch sensor chip located on the charging board module. It makes contact with contacts on the frame. I first thought it was for the wifi/cellular antennas, but then I noticed that antenna cable traces on the charging board PCB led to a signal amplifier chip which then leads to contact pins connecting to the speaker/wireless charging coil plastic piece (which probably serves as the antenna). My grip sensor is probably not working because the pin was not making contact with the frame part. Probably 'cause of corossion or some dirt. Maybe I need to scratch up the part where the pin connector touches the frame. I'll try to get this fixed soon if I ever need to open up the phone again. I kinda already sealed it up with a new water resistant seal. Its gonna be a pain to remove and replace again just for the grip sensor.
richhaynes said:
I've not heard about Smart Switch being an issue on the S21 but I didn't get that model so I've not really read much on the issues it suffers from. Unfortunately Smart Switch is just not reliable as a backup solution. Use it to backup you content and settings but don't rely on it for backing up your apps. You need root otherwise its a manual job I'm afraid.
Click to expand...
Click to collapse
Yeah. I decided I'm gonna start again from scratch. Instead of doing all the trouble finding out whats causing this problem. It went bonkers again last night and early morning. I give up. I decided to reset the phone and reinstall all of the apps. Its going to take a while for sure. I would still back up my current data using smart switch though. Just in case it still occurs even after a full factory reset.
Be aware the issue may return if you don't find the root cause. It's likely a 3rd party app or a settings issue. It's always better to find the root cause. Malware is also a possibility in which case a reload will kill it.
You can use ApkExport to make installable app copies in the future, no need for Playstore then on reloads. Available on Playstore.
blackhawk said:
Be aware the issue may return if you don't find the root cause. It's likely a 3rd party app or a settings issue. It's always better to find the root cause. Malware is also a possibility in which case a reload will kill it.
You can use ApkExport to make installable app copies in the future, no need for Playstore then on reloads. Available on Playstore.
Click to expand...
Click to collapse
Already done factory resetting the phone. And freshly installed all the same apps from the play store (also individually set them up). I also only used smart switch to restore my contacts and messages. Did not use it to restore settings and apps. All good so far. No more annoying ringer mode switching. So that confirms it then, it was indeed a bug in smart switch.
Aries2376 said:
Already done factory resetting the phone. And freshly installed all the same apps from the play store (also individually set them up). I also only used smart switch to restore my contacts and messages. Did not use it to restore settings and apps. All good so far. No more annoying ringer mode switching. So that confirms it then, it was indeed a bug in smart switch.
Click to expand...
Click to collapse
Lol, SmartSwitch is a Pandora's box of trouble.
I would also use the backup feature in Contacts to create an export backup file. This is important to have.
Its back again. Huhu.
Seems to occur less frequently now though. Tried doing setting up some automation on sound assistant to see if it was the one thats changing the ringer mode. But its process can clearly be seen by Nicecatch. This is really starting to bug me. I've already done a factory reset and reinstalled all my apps fresh from the play store.
I've tried plugging a headset with volume control and tried changing the ringer volume over there. It still says audioservice but the process is different. Its the checkforRingerModeChange process. Not the onSetStreamVolume.
Update: I've decided to open the phone again and fix the grip sensor. Grip sensor probe is marked Red. It connects to the lower portion of the aluminum frame. Those "antenna bands" on the aluminum frame are not actually antenna bands. They are plastic molded spacers to separate a piece of aluminum (sky blue) from the side aluminum frame. The lower piece of aluminum is then connected to the probes of the grip sensor IC (located on charging board and as well as on the top of the motherboard). There are also two grip sensors. One at the top and one at the bottom. But on the test menu, only the test for the bottom one is present. (Newer models have test for top and bottom grip sensors). When I touch the bottom probe, grip sensor test becomes "working". Therefore there is no problem on grip sensor circuits. Problem is on brand new frame I installed, I had to scratch the part where the probe makes contact on the frame and viola, grip sensor works now (I also scratched the top grip sensor probe contact). Yellow marked ones are wifi/cellular/gps antennas. They're present as well at the top.
I wonder if the grip sensor was the one triggering AudioService.onSetStreamVolume. I'll just wait and see if it still occurs after this.
2nd update: Its still here.
3rd update: Updated to March 2022 update. Issue completely gone.
Glad for you but I've never used smart switch and my m30 already saw the endo of the updatos, amigo!