Hi All I have just purchased a new nexus 5 (gear live pre-ordered) in a curious attempt to have a go at android from my Iphone 5c.
I am tweaking the handset at the moment to give me some lost functionality from IOS. I have stumbled across a really painful problem that i can not find a solution to. I use a pair of bose wired earphones to listen to music and use as hands free in the car. On my iphone, I am used to to pushing the mic button and activating the voice dial from the locked screen, all good.
When i try doing this on my nexus, i get the "can not use OK Google until the phone is unlocked" message in my ear.
I have to have a passlock on the handset due to work security restrictions.
Does anyone have a work around for this? I am hoping my new gear live will keep the pass lock when in close proximity (A major flaw otherwise - unlocking your phone before you can see anything on your smartwatch!) in the interim though, putting a pass key in the phone every time i want to make a call whilst riving is pretty poor!
currently on stock 4.4.4. not rooted yet -
Thanks all
randomtechgeek said:
Hi All I have just purchased a new nexus 5 (gear live pre-ordered) in a curious attempt to have a go at android from my Iphone 5c.
I am tweaking the handset at the moment to give me some lost functionality from IOS. I have stumbled across a really painful problem that i can not find a solution to. I use a pair of bose wired earphones to listen to music and use as hands free in the car. On my iphone, I am used to to pushing the mic button and activating the voice dial from the locked screen, all good.
When i try doing this on my nexus, i get the "can not use OK Google until the phone is unlocked" message in my ear.
I have to have a passlock on the handset due to work security restrictions.
Does anyone have a work around for this? I am hoping my new gear live will keep the pass lock when in close proximity (A major flaw otherwise - unlocking your phone before you can see anything on your smartwatch!) in the interim though, putting a pass key in the phone every time i want to make a call whilst riving is pretty poor!
currently on stock 4.4.4. not rooted yet -
Thanks all
Click to expand...
Click to collapse
I'll be honest and say that being able to make a call with the phone being pin locked would be a security risk. Now as for a workaround I can only think of one thing that would work but it requires some time to configure things correctly.
You could us ethe app tasker to automate this. You can set a profile for when you are in your car. When you are driving in the car (e.g. moving over 10 MPH) you can have tasker turn off your PIN Lock. Then when you get out of your car (eg not moving) it would reenable your PIN lock.
If that's too hard to configure (I can show you if you are interested in the above method) You can just set up a much simpler profile in tasker that whenever your BT headset is connected disable your PIN lock. THough this is less secure.
Those are the only options I can think of and honestly I would be surprised if anyone came up with a true solution to this
I have posted a similar post in the CRV Owners forum, but I thought this forum would make more sense since it's filled with a bunch of hardware-hacking programmers!
The interface between my car and my phone (LG G2 Lollipop stock) is abysmal. I have seen a number of posts on the web about this issue with modern cars, but no real solutions. The following is a list of what I would like the interface to be between the phone and car. Then at the end of the email I'll flame a little about the "why"s.
GIve me a button to allow me to talk to my phone directly without the HondaLink getting in the way. There was a similar issue with a Volkswagon and a solution using Tasker to intercept the call. That solution doesn't work with my Honda and is a kludge.
Always have the phone interrupt the radio (whether it's a call or audio, e.g. Google maps navigation). For me, the information coming from the phone will always be more important than the music or talk show on the radio.
Mirror the phone screen onto the car screen when I'm driving (so I can see my map when I need to)
When I receive a call, let the phone do the talking (the phone can speak the caller's name to me and can send the caller's name over the bluetooth connection) and let me hit a button to answer it.
Has anyone successfully hacked into the firmware/software in the CV-R to fix these issues? Is it possible? At this point, based on my research, I see no other option. If there is another option that doesn't involve replacing the system or "just dealing with it," I'd love to hear it.
The "why"s:
My phone is custimizable, has all of my contacts, recognizes my voice, has GPS, accurate and up-to-date maps, and does everything that I need a phone and navigation system to do. The Honda solution tries to duplicate all of that functionality and does it very poorly. As one user wrote last year, my $50 bluetooth headset can listen to my phone and pipe in navigation directions and let me know when I get a call. It is a joke that an expensive car can't even get that part right. The fact that I can't put my phone screen on the car screen while I'm driving is idiotic. Now I've got to find some way to hold my phone up for navigation. I don't want this post to degenerate into a series of posts and counter-posts on whether drivers can handle the increased cognitive demand. I've been driving long enough to see that the majority of drivers are not paying any attention at all to the road anyway and no one seems to care.
The hardware in the CR-V seems to be capable of doing the things that I have listed above. So, if the Honda programmers can't get it the way I want it, the only solution is to take the programming away from them and do it ourselves. Has anyone done this yet?
Thank you in advance for your help.
Here, check this out.
Me:
When two BT devices capable of telephony functions are connected, the second one connects as "Connected (no phone)", and its telephony function cannot be used.
Example (picture attached). If Huawei Watch is already connected, when Jabra Talk attempts to connect, it will connect as described above, and one cannot make or receive phone calls on Jabra Talk (but still can on the watch.)
Oneplus support:
Thank you for taking the time to send us this email as well as the screenshot that you provided. I understand that you want to use both of the Bluetooth devices for easy access and getting in touch with loved ones for helping us keep on track with our daily activities.
I would like to inform you that the OnePlus 6 can actually connect to two Bluetooth devices. However, by default, you can only choose one for making and receiving calls. Just choose which you preferred to use by toggling the "Phone calls" under each setting of the Bluetooth devices.
This bug was not present in 5.1.5. They introduced it in 5.1.6/7.
This bug is present in all Pixel phones because it's a buggy Google code that Google simply does not care to fix.
Samsung fixed this in their phones.
So, I am guessing OP had this fixed in 5.1.5, but then they just lazily copied and pasted that Google garbage code.
And they don't know how to fix it now. So now it's a freaking feature.
UNBELIEVABLE!
I have the same problem with my Huawei Watch and my cars hands free system
I tried to disconnect the watch with Tasker as soon as my hands free system connects, but it never worked reliable (because the watch connects again immediately and takes over the call functionality)
I guess we need to wait until we get Android Pie because as far as I know this problem is solved with Android Pie
MJFox78 said:
I have the same problem with my Huawei Watch and my cars hands free system
I tried to disconnect the watch with Tasker as soon as my hands free system connects, but it never worked reliable (because the watch connects again immediately and takes over the call functionality)
I guess we need to wait until we get Android Pie because as far as I know this problem is solved with Android Pie
Click to expand...
Click to collapse
I hope so. But I'm not that hopeful - I think it's a Google bug, and they simply don't care to fix it.
Meanwhile, I have to disable the phone functionality on the Watch so I can use my hands free car kit.
It's so disappointing, especially since this stuff always worked with Samsung phones, OOS 5.1.5 (the bug was introduced in 5.1.6/7) and even the early Pixel, pre Android 7.0.2.
nabbed said:
Here, check this out.
Me:
When two BT devices capable of telephony functions are connected, the second one connects as "Connected (no phone)", and its telephony function cannot be used.
Example (picture attached). If Huawei Watch is already connected, when Jabra Talk attempts to connect, it will connect as described above, and one cannot make or receive phone calls on Jabra Talk (but still can on the watch.)
Oneplus support:
Thank you for taking the time to send us this email as well as the screenshot that you provided. I understand that you want to use both of the Bluetooth devices for easy access and getting in touch with loved ones for helping us keep on track with our daily activities.
I would like to inform you that the OnePlus 6 can actually connect to two Bluetooth devices. However, by default, you can only choose one for making and receiving calls. Just choose which you preferred to use by toggling the "Phone calls" under each setting of the Bluetooth devices.
This bug was not present in 5.1.5. They introduced it in 5.1.6/7.
This bug is present in all Pixel phones because it's a buggy Google code that Google simply does not care to fix.
Samsung fixed this in their phones.
So, I am guessing OP had this fixed in 5.1.5, but then they just lazily copied and pasted that Google garbage code.
And they don't know how to fix it now. So now it's a freaking feature.
UNBELIEVABLE!
Click to expand...
Click to collapse
if Google's code is garbage, I suggest you stop using android and start making your own good code!
nabbed said:
I hope so. But I'm not that hopeful - I think it's a Google bug, and they simply don't care to fix it.
Meanwhile, I have to disable the phone functionality on the Watch so I can use my hands free car kit.
It's so disappointing, especially since this stuff always worked with Samsung phones, OOS 5.1.5 (the bug was introduced in 5.1.6/7) and even the early Pixel, pre Android 7.0.2.
Click to expand...
Click to collapse
I disabled the phone functionality too
I had a Samsung phone before as well (Note 8) and with that I had no problems with my hands free kit but instead the smartwatch lost the phone functionality after a few hours so I always had to reconnect it (basically the same problem but the other way round)... it's very frustrating that such a pretty basic thing doesn't work properly
I also tried this app: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect
but it didn't seem to make any difference, it didn't seem to make anything at all
I read that Android Pie is able to connect to more than one Bluetooth headset at a time so this should fix the issue after all
kewlest22 said:
if Google's code is garbage, I suggest you stop using android and start making your own good code!
Click to expand...
Click to collapse
I had a Pixel XL for over a year. Only kept it for Project FI. Bug ridden POS.
Sold it for half going price just so I could feel clean again.
Even if Samsung *used* to have sluggish Touchwiz in the past, at least it didn't have deal breaking bugs.
Don't even have to make my own code - some XDA roms had fixed this bug, as opposed to Google.
MJFox78 said:
I disabled the phone functionality too
I had a Samsung phone before as well (Note 8) and with that I had no problems with my hands free kit but instead the smartwatch lost the phone functionality after a few hours so I always had to reconnect it (basically the same problem but the other way round)... it's very frustrating that such a pretty basic thing doesn't work properly
I also tried this app: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect
but it didn't seem to make any difference, it didn't seem to make anything at all
I read that Android Pie is able to connect to more than one Bluetooth headset at a time so this should fix the issue after all
Click to expand...
Click to collapse
I am almost positive that if you had a somewhat similar problem on a Note 8, it's probably Google's fault.
I don't really use the 2 BT phone functionality for more than 30 min on average, but I've never had any problems on Note 7, GS6 or GS9, or even on a Pixel pre 7.0.2 android, when this bug was first introduced.
After 7.0.2, bluetooth stuff just broke everywhere. This bug, constant disconnects and reconnects, for some people music skips, for some doesn't even work, BT UI in Settings just crashing etc.
It's like Google replaced their BT programmer with a monkey at that point, or even a monkey's nephew.
So just because you cannot use 2 Bluetooth devices simultaneously to make phone calls, it's a deal breaker??? Lmao please please please go back to Samsung so we don't have to hear the whining anymore. Good luck with those bootloaders
I'm an experienced programmer, but a complete novice when it comes to android development. I also hope I'm posting this in the right place...
I have recently bought a OnePlus Nord (AC2003) which I'm *fairly* happy with, and a Samsung Galaxy Watch3. I'm having an issue with it in that the watch and phone will fairly randomly disconnect from each other, even when they're in close proximity to each other. I have read extensively about the possible issue*, and reset both the watch and the phone, and cleared the bluetooth cache, which appears to have made a difference, at least in the long term. The disconnection now only happens about once a day, rather than the every half an hour that was happening originally.
* One school of thought is that the watch is absolutely at fault, as the users have no problems with other bluetooth devices. Another school say it's definitely the phone, as they have no issues when they use the watch with a different handset. Go figure.
My programmer's hunch (which I've learned to trust over the years) is that a service or app in the phone is stopping and starting, and I'd like to get a log of when the phone is stopping and starting apps and services. I've enabled developer mode, and I can see the option for 'Basic Log' and 'Power Consumption Exception' log in the OnePlus logKit.
My question is - Has anyone looked at the logs for this sort of data before, and is there anything in particular I should be looking out for, with particular attention to when the battery management on the phone decides that a process can be stopped or hibernated.
(Obviously, if anyone has anything to share about any Eureka moments regarding smart watch disconnects with this phone, I'd love to hear those too )
I recently upgraded from my trusty Note 8 and am finding the new Android version to be completely underwhelming (a common theme, I'm finding). I can't really think of any actual improvements to my daily user experience and two things have gotten worse enough that I have been researching solutions to them to no avail. The first is the main topic of this thread. My older Bluetooth car stereo (not Android auto, but apparently that is equally as broken) sends an "autoplay on connect" request. No individual app autoplay setting seems to matter, it is a system problem. On the Note 8 this was also the case, however it would only actually play if the app was open (present in the task switch windows). This was occasionally annoying but now it is much much worse. What happens now on the S22U is that apps I have long since closed will just appear to open zombielike and autoplay. Even when I am in the middle of opening a music app, e.g. a podcast that I was listening to yesterday will just start playing because it was the last used app.
I can't believe that it's 2022 and Android doesn't just have this fixed yet it has been underdeveloped for YEARS now. Why can't it just be a system wide setting? And why on earth does it insist on playing audio even if it was PAUSED before Bluetooth is disconnected? I have a feeling there is nothing I can do about this, but I wanted to vent.
I mentioned there was a second most annoying issue with the new version of Android. This is that the "double tap to switch" to previous app window is inexplicably slower than it used to be, to the point you might as well not use it. I used to do that constantly and it was very effective. Why on earth they removed this feature is beyond me.
If anyone has a current solution to either of these problems please lmk.
I've also have this issue... Both with the Pixel 6 Pro and same thing when I switched to the S22 Ultra. I'm inclined to think it's an issue specific with Android 12. On my Pixel 5 (using Android 11), autoplay when connecting to bluetooth worked every time. Even with having setup a Bixby routine to autoplay upon connecting to a specific bluetooth device, it does not always work... It's frustrating.