Hey. Just got the Fossil Gen 5, amazing watch, well after two days when the battery actually lasted more than a few hours anyway. Basically, and I know I am playing a little loose with the rules against general questions here, but it is definitely wear OS related.
When making calls on the watch, which works surprisingly well, it always wakes the phone up and displays the normal call screen and as the proximity sensor doesn't even kick in, it stays on through the whole call unless I manually switch off the screen. Which means it is essentially useless as the only way I can make a call on the watch, without the risk of pocket presses, is to either have the phone in my hand, or on my desk or something, which completely defeats the object of using the watch.
Does anyone know a way to prevent this? There are no related settings in the watch or phone. Also, I know Wear OS connects as a headset, but I have never even used a BT headset of any kind before, so is this a watch thing, or does the same happen with any BT headset?
Related
Hi,
Is there anything that can be done to improve the mic volume when on speaker phone - I have had complaints when more than a foot or so away that people can't hear me.
I have the phone open on my desk most of the time and am just trying to work out the best way to deal with calls as they come in. At the moment unplugging the USB and then flipping the screen and then trying to answer the call seems a bit ham fisted and I keep on loosing calls
I personally never use my MDA Pro as a conventional phone. I find it too bulky. My own method is to always use a bluetooth headset.
If I was in your situation, I would have the Universal open on my desk, with the bluetooth headset lying beside it. When the phone rings, simply put on the bluetooth headset,press the call receive button on it, and away you go.
You don't really need to flip the screen, just close it and then use the green button to answer the call. Will work fine with the USB connected if you don't mind people looking at you strangely.
Hi Guys,
Thanks for the responses.
I don't have a headset so haven't gone down that route yet. Will they work with Skype and VOIP software etc on the phone?
As for closing and then picking up, I'm wondering if the phone has a problem because I have tried this a couple of times and have lost the calls although I am generally unplugging the USB, closing the phone and then answering - have only had the phone a couple of days so still getting the hang of it.
Hmmm....can it be used when in pda mode to answer and make calls... I have tried this, but I think either my machine's mic & speakers dont work on the inside (screen side) of the clamshell, the other person on the line can't hear, and I hear their voice (distantly), which means it is coming out of the back of the screen, not the front. Its either that or the device just isnt designed to work in this orientation.
Has anyone else tried recieving or making calls with the screen facing out in portrait mode?
Re the Bluetooth headset answering method, great idea, I do this, but I have found that sometimes my o2 blue headset loses the pairing when I press the answer call button, so I lose the call anyway.
Can anyone tell us how it should work, will the recent rom upgrade fix this, is there even a mic and speaker on the inside lid?
Can anyone tell us how it should work, will the recent rom upgrade fix this, is there even a mic and speaker on the inside lid?
Click to expand...
Click to collapse
The Mic is right next to the power button, so it is as close to your mouth when in PDA mode or closed. Also There are two speakers on the hinged lid, in PDA mode it's the slightly recessed oval shape 10mm from the top dead centre.
I've never discovered a software method of disabling this speaker. Possibly a hardware fault? Might be worth discussing with your handset provider
I am looking for a tweak or registry fix/setting to help me with the following problem:
On my parrot bluetooth car kit in headset mode after a call is finished the phone stays on. This is not a problem if you finish a normal call without handsfree because you switch it off manually but when you are driving with the phone in your pocket, the phone is liable to screen presses. I have been inadvertently creating/editing contacts and making notes with the phone in my pocket after use in the car.
The screen autopower off does work if the screen is not activated for a few minutes but the inadvertent screen presses occur within this timeframe.
Any help is appreciated - thanks!
I have a similar problem when using my bluetooth headset (Samsung WEP200)…
When I make a call using the headset the screen stays active, and if I turn it off during a call it turns it self on again after the call has ended. Not fun if it’s in my pocket and it decides to call someone back without me knowing.
Is there a general setting or fix that disables the screen when you answer or make a call with the headset active?
Have you found any solution to this?
aneben said:
Have you found any solution to this?
Click to expand...
Click to collapse
Nope, not yet…
I can’t believe that there aren’t a lot more people with this problem!? It’s a REALLY STUPID problem to have on such an advanced phone like the Blacksone when nearly EVERY basic mobile phone has this feature since the dawn of BT headsets.
This might leave me no other choice than to retire my beloved Blackstone and dig up my old Samsung phone so that I can drive my car safely with my phone in my pocket…
There is an app called Touch InCall Screen Tweak. With that you can configure so that screen will go off quickly when answering and ending calls and bluetooth headset is used. It works great for me!
aneben said:
There is an app called Touch InCall Screen Tweak. With that you can configure so that screen will go off quickly when answering and ending calls and bluetooth headset is used. It works great for me!
Click to expand...
Click to collapse
I actually tried that app yesterday but didn’t get it working as I wanted. How did you configure it?
I guess I can try it again – would be great if it works!
Well, now I can make a call without worrying about it to end (with the InCall Touch app), but when the call is ended we're back making random calls without knowing to whom.
This amazes me, how this feature can be missing. It’s not something I admit to my iPhone friends who still tries to find something that Blackstone can’t do – cuz this even works on the iPhone!
I'll try tweaking till I or someone else can find a solution to this rather embarrassing problem.
Hi,
I realize this will sound like a strange issue, but I can reproduce it so it certainly exists.
I have an LG G3 running Android 4.4.2 on Verizon. I just bought it back in Jan '15, and the phone has been working great with no issues. I use my car's built in bluetooth connectivity to place and receive calls while driving and have had no issues doing so.
A few days ago (week of 3/9/15), I acquired a used LG G watch from a friend at work. It's in good shape; he only had it a few months, and it's working well. It connects to my phone, and I can use it to txt, place calls, etc. It's running software version 5.0.2.
I am experiencing an issue for which I cannot find the root cause. My issue is that, when I'm in my car, and both the car and the watch are connected to the phone via blue tooth, and I place or receive a call, folks on the other end cannot hear me speak. I tried it with my wife's cell phone, and can reproduce it every call. My voice is barely audible, yet bluetooth is connected to the car and I can hear the other person's voice just fine over my car speakers. As this is happening, if I pick up my phone and switch the call to the handset from bluetooth, the problem goes away and I can take the call on the handset. But as soon as I put it back to bluetooth, the problem returns. Once this happens, if I hang up and try to call the person back using either bluetooth OR the handset, the voice problem returns and I cannot be heard speaking. I tried putting my mouth up to the watch and the phone thinking maybe it was trying to use another microphone, but I still sounded muffled and far away while I was testing this with my wife's phone.
I have checked all my settings in Android Wear, my phone settings for volume as well as call settings...I cannot find anything obvious. I've googled the issue, but there is little to no information regarding this problem.
Can anyone suggest something to help fix this? I really like the G watch, and I would like to get it to work so I can enjoy it. You would think that the G3 and G watch would play nice since they are both LG!
Thanks for any help,
Nick
Having the same issue....sort of...
First, allow me to apologize for any improper formatting or if I've tendered my reply in the wrong way.
I've literally never replied on a message board in my life. Ugh, I know. How, right? Moving on...
I have an issue very similar to the one you're having, only in place of the car, put a Plantronics WalMart headset and change the G3 for it's predecessor. I notice that people call me when my watch is connected to my phone. When I answer, they claim to not be able to hear or understand what I am saying. The problem persists even if I disconnect my headset and use the G2 in either handset or speakerphone mode. The only fix I've found is to restart the phone and return the call. Even then, if the watch is still connected, only the first call can be completed with no "interference".
I've attempted to update the software and firmware to my G2, with no success. I have no idea why this issue occurs.
Also, is probably noteworthy that regardless of whatever Bluetooth device I am connected, very very often during a call, my caller's voice will shift into "speakerphone" mode without being instructed to do so. I have to open the call screen, turn off the BT, then select it again to turn it back on. The call returns to the headset, but doesn't stay there in most cases. Sometimes I have to do this 5 - 7 times a call. Other times, it remains connected as it's supposed to. Again, I can find no reason why this happens, but it's been an issue for MONTHS with my G2. And it doesn't matter what headset I am using, it just "drops" the sound to my speaker phone, but still says that it remains connected to the headset.
It's a Sprint LG G2, if that matters at all.
PrivateBytes said:
Hi,
I realize this will sound like a strange issue, but I can reproduce it so it certainly exists.
I have an LG G3 running Android 4.4.2 on Verizon. I just bought it back in Jan '15, and the phone has been working great with no issues. I use my car's built in bluetooth connectivity to place and receive calls while driving and have had no issues doing so.
A few days ago (week of 3/9/15), I acquired a used LG G watch from a friend at work. It's in good shape; he only had it a few months, and it's working well. It connects to my phone, and I can use it to txt, place calls, etc. It's running software version 5.0.2.
I am experiencing an issue for which I cannot find the root cause. My issue is that, when I'm in my car, and both the car and the watch are connected to the phone via blue tooth, and I place or receive a call, folks on the other end cannot hear me speak. I tried it with my wife's cell phone, and can reproduce it every call. My voice is barely audible, yet bluetooth is connected to the car and I can hear the other person's voice just fine over my car speakers. As this is happening, if I pick up my phone and switch the call to the handset from bluetooth, the problem goes away and I can take the call on the handset. But as soon as I put it back to bluetooth, the problem returns. Once this happens, if I hang up and try to call the person back using either bluetooth OR the handset, the voice problem returns and I cannot be heard speaking. I tried putting my mouth up to the watch and the phone thinking maybe it was trying to use another microphone, but I still sounded muffled and far away while I was testing this with my wife's phone.
I have checked all my settings in Android Wear, my phone settings for volume as well as call settings...I cannot find anything obvious. I've googled the issue, but there is little to no information regarding this problem.
Can anyone suggest something to help fix this? I really like the G watch, and I would like to get it to work so I can enjoy it. You would think that the G3 and G watch would play nice since they are both LG!
Thanks for any help,
Nick
Click to expand...
Click to collapse
Have you tried going into android settings for voice input and allowing recording using Bluetooth mic?
Hey guys,
I am a proud S7 Edge owner since two weeks ago. I love it. The overall performance is astonishing y it's design ir ergonomic and beautiful.
But, nothing is perfect, and I found a little problem that is getting me crazy.
I live in Barcelona, and a use a lot the motorbike to move through the city. I have a Bluetooth headset installed in my helmet and i heavily use my LG G WATCH while riding.
I start calls using the watch, you know: "Ok Google, call to......."
The problem is that, while the device is in my pocket and if it is connected to the helmet's Bluetooth headset, the screen remains turned on, PROXIMITY SENSOR DOESN'T WORK while Bluetooth is working. Humidity in Barcelona is very high in summer, and I accidentally end a lot of calls, or while speaking I touch number buttons continuously, with is very disgusting for the person on the other side of the phone.
The user experience is absolutely frustrating.
Does anybody know how to fix this problem?
I came from a HTC M8, M9 and OnePlus X and didn't have this problem with them.
Thank you all.
There should be an option under Screen to keep the screen off while the phone is in a pocket.
I will answer to myself.
I found the solution here:
http://forum.xda-developers.com/z3/help/screen-bluetooth-connection-starts-t2925836
Bluetooth headset's setting should be like in the attached image.
I hope it will help someone.
EDIT: Doesn't work for calls.
Hi all,
So my issue was that I want to be able to receive phone call notifications and the ability to accept or reject those calls on my no.1 s9, but i don't want to use the watch as hands free. I've googled it for some time but i haven't found nothing to solve this.
It may sound silly but I believe that this should be implemented through options on smartwatch or even better, if you accept the call in the watch it redirects the sound, if you answer through your phone it shouldn't redirect).
I believe that with some other smartwatches this is the behavior but not with no.1 s9 and, maybe, with some other phones. The reason is simple: you have your phone on your backpack or in your coat, you can check who is calling and then you decide if it's worth to pick up your phone or not.
So, i have created a simple flow with Automagic to handle things just how I believe they should be. Well, not quite because with this flow you can not use your smartwatch as hands free. But if you want to do so, you just have to switch off the flow.
You can find the flow in the attached image.
The idea is simple, the flow is activated by InCallActivity, first thing is to ensure that you can choose what action to take on your watch so while it stills ringing nothing is done (maybe there is some other way of doing this... i don't know how so there is a condition that basically does nothing while true). when you choose what to do the flow moves on to the next step (well... if you reject the call in your watch nothing is done and the flow ends here). If you answer the call, it checks if the watch is connected and if so, disconnects the watch and sets Bluetooth off to prevent that your watch connects again and the sound is, once again, redirected. Here you find another condition that basically holds everything until your call finishes. After all of this, Bluetooth is turned on so that your watch connects again.
It's my first flow with Automagic and this means that maybe I have take some paths that are not the most correct ones but it works.
I'm still testing but tests made so far are giving the exact result that I was looking for.
If you have the same problem that i was facing please share your thoughts and what are the ways you're handling this.
PS: It works for outgoing calls also.
PS2: English is not my native language... sorry if there are some mistakes
Hi,
Nice idea!
Any progress so far?
Nenad