Hey everyone,
some years ago I had the Nexus One and started digging into Android development, custom ROMs, CyanogenMOD and so on. But since the iPhone 5S I've always been an Apple user.
One of the reasons I still prefer iPhone over Android phones is the convenient usage of Siri with headphones. Sounds awkward? Let me explain:
I use my bike every day, and while I try to find my way through the cars of the early morning traffic in Munich (Germany), I'm able to control the music I'm listening to with Siri.
A long press on my headphone button gives me accesss to Siri:
"Play some funk music".
Or: "Call Veronica."
Or: "Send a message to Peter: I'll be late for the rehearsal, sorry."
Or: "Set my alarm to 3 pm."
Stupid question: Is this possible with Bixby? Or Google Assistant?
Long story short: I don't want to have to fiddle around with my phone on the bike, especially when wearing gloves or anything. I'd love to activate the assistant from my headphones without unlocking the phone or taking it out of my pocket.
This is actually the thing that has kept me away from Android for quite a long time.
Thanks,
Ben
Assistant does all of that, plus much more. I don't use bixby.
Bixby currently is useless wouldn't even recognise my voice to train it as its Korean or US english only.
Google Assistant however is great BUT they've only started allowing assistant to work when the phone is sleeping and locked in the Oreo beta. I can now use voice commands (no button presses) to do anything like listening to music sending texts or calling. Nougat only lets you use the assistant with the screen on (and phone locked/unlocked).
Karlinski said:
Assistant does all of that, plus much more. I don't use bixby.
Click to expand...
Click to collapse
While the screen is off? Oblox said it won't work..
You can do that with "Ok Google" and it should work.
If you are still pending and not sure about switching, then check how this works on an Android in a phone store or get one from a friend.
heisven said:
While the screen is off? Oblox said it won't work..
Click to expand...
Click to collapse
I have not gotten the phone to wake by saying "ok google". but "Hi bixby" does wake the phone from a lockscreen.
what I do is say, "Hi Bixby, open Assistant" - and then Google Assistant launches and is listening.
saying, "Hi Bixby, open GOOGLE Assistant" just launches Google, so be sure leave out the word "Google".
Bixby: your *****'s *****.
As i stated above Samsung only made assistant wake the device in the Oreo beta which should be out in January if all goes to plan.
Ok Google works fine on Oreo to wake the phone so you dont have to mess with Bixby at all.
On Nougat i had to press the power button first then could say OK Google.
Oblox said:
As i stated above Samsung only made assistant wake the device in the Oreo beta which should be out in January if all goes to plan.
Ok Google works fine on Oreo to wake the phone so you dont have to mess with Bixby at all.
On Nougat i had to press the power button first then could say OK Google.
Click to expand...
Click to collapse
right, I think the OP may not have known that the S8 is still on Nougat (7.0) - Oreo (8.0) has been released only in beta form to certain users for testing.
so in other words, if you buy the device now, you will NOT be able to launch Assistant directly from the lockscreen. this feature should become available with the next software update.
but you could, in essence, use the device as you would like, but just have to say "Hi bixby" instead. also, as another user noted, test it for yourself. I have, and it works as advertised, just not as polished as google or Siri (takes training/repetition before you get the full AI experience).
this lockscreen wake capability has been around on android for quite some time. I had it on my 2014 Motorola Droid Turbo - and worked perfectly every time.
jco23 said:
right, I think the OP may not have known that the S8 is still on Nougat (7.0) - Oreo (8.0) has been released only in beta form to certain users for testing.
so in other words, if you buy the device now, you will NOT be able to launch Assistant directly from the lockscreen. this feature should become available with the next software update.
but you could, in essence, use the device as you would like, but just have to say "Hi bixby" instead. also, as another user noted, test it for yourself. I have, and it works as advertised, just not as polished as google or Siri (takes training/repetition before you get the full AI experience).
this lockscreen wake capability has been around on android for quite some time. I had it on my 2014 Motorola Droid Turbo - and worked perfectly every time.
Click to expand...
Click to collapse
Yep although as he's from germany id imagine he might have more issues than me trying to get US bixby to recognise his voice. It wouldn't even complete the training for me an I have a pretty standard UK english accent with no regional accent.
Thanks me later
https://www.youtube.com/watch?v=67PsQAqwoyI
Related
These Smart Lock features are really interesting and I wanted to know if anyone with a second gen Moto G had received them yet
We got smart lock ages ago, but no trusted voice on my device yet
shxrm_ said:
These Smart Lock features are really interesting and I wanted to know if anyone with a second gen Moto G had received them yet
Click to expand...
Click to collapse
Hi, got trusted voice, I don't really like it, you're supposed to say "ok google" to unlock the phone but every time google now pops up and you have to close it then swipe up to unlock. I dislike the fact that it is not a "better way to unlock your phone" but rather "a better way to use google now from the lockscreen". In the end its cool, but I'm pretty sure it is easy to fool, although I haven't tried. It is a nice gimmicky feature but security-wise, it sounds pathetic.
I was not having trusted voice and on-body detection features...
But Three days ago when my device got soft-bricked, I flashed factory firmware 5.0.2 and after that i got all these features
Now i dnt knw how i didn't have this before and how i got this now...
But my experience, the on-body detection is a great thing that it does not lock ur phone untill its layed down on a surface but there is a silly thing in that was if you give the device to your friend obviously it couldn't detect that it's not you.
So to rectify this you can use both trusted face and on-body to make ur device safe.
Yes, I have trusted voice and on-body detection. Trusted voice seems to work, but I have not tried either in real use. I don't know when they showed up, I don't think infrastructure updates show in the play store.
ArtRahul said:
I was not having trusted voice and on-body detection features...
But Three days ago when my device got soft-bricked, I flashed factory firmware 5.0.2 and after that i got all these features
Now i dnt knw how i didn't have this before and how i got this now...
But my experience, the on-body detection is a great thing that it does not lock ur phone untill its layed down on a surface but there is a silly thing in that was if you give the device to your friend obviously it couldn't detect that it's not you.
So to rectify this you can use both trusted face and on-body to make ur device safe.
Click to expand...
Click to collapse
I got them, and I switched from trusted places to on body. I've never really used trusted face, and don't really plan on it.
hi to all how any one that has the same setup will help me understand i will try and keep it short first im using samsung note 4 running 6.0.1 now
ok so here goes i use my gear 2 together with my note 4 as a trusted device you know like every time the gear 2 is close the device must stay unlocked but it does not stay unlocked and there is no Bluetooth disconnecting anything like this i look at that so battery is full the gear 2 and phone stayed together and there was no setting like disable and enabling of Bluetooth at any stage but i connect it now and its fine but after a wile (don't know the exact time here ) but say after 3 hours of no use i press the power button and it asks for my pin or fingerprint as if the gear 2 is not near but it is still on and there was nothing like it disconnecting it is as if the phone on its own make sure that it asks the finger print every now and again say like i leave it overnight the next morning first fingerprint then you can use the phone i hate this it kind of bugs me if the steal the phone and the range is to big the device will lock any way why lock when the gear 2 it near the phone any help please
honestly, i stopped reading after few seconds.
have you ever heard about punctuation? - you know, the thing that looks like dots and commas, makes reading much easier.
244 characters in 1 sentence.
wow dude, looks like you dont wanna get helped.
biebie29 said:
...say after 3 hours of no use i press the power button and it asks for my pin or fingerprint as if the gear 2 is not near but it is still on...
Click to expand...
Click to collapse
From the Google Smart Lock support page (https://support.google.com/nexus/answer/6093922):
"Note: When you don't use your phone for 4 hours, and after you reboot your phone, you'll need to manually unlock it with your PIN, pattern or password"
It's a security feature.
EDIT: ...and, wow, yes, that was some run-on sentence!
Is there a root app to disable it or not
biebie29 said:
Hi to all. How any one that has the same setup will help me understand. I will try and keep it short. First, i'm using samsung note 4 running 6.0.1 now.
Ok, so here goes:
I use my gear 2 together with my note 4 as a trusted device. You know like every time the gear 2 is close, the device must stay unlocked. But it does not stay unlocked and there is no Bluetooth disconnecting, anything like this. I looked at that. Battery is full, the gear 2 and phone stayed together and there was no setting like disable and enabling of Bluetooth at any stage.
I connect it now and its fine, but after a while (don't know the exact time here ), say after 3 hours of no use, i press the power button and it asks for my pin or fingerprint as if the gear 2 is not near. The gear 2 is still on and there was nothing like disconnecting. As if the phone on its own make sure that it asks the finger print every now and again.
For example, i leave it overnight the next morning first fingerprint then you can use the phone.I hate this. It kind of bugs me if they steal the phone and the range is to big, the device will lock any way. Why lock when he gear 2 it near the phone? Any help please.
Click to expand...
Click to collapse
Fixed that for you
I really had to break that down to make it readable for me. But as others said, it's an Android feature. Afaik there is no way of disabling that all together. There might be some xposed module i haven't heard of, but with my moto360 i couldn't get it to work the way you'd want. Sorry mate
Kinsman-UK said:
It's a security feature
Click to expand...
Click to collapse
As the programmers use to says: Its a feature, not a bug
Some people are just plain jerks, and I wish XDA would take these "grammar police" trolls a bit more seriously and penalize them.
Perhaps OP is using a translator, or is from another country, or is young. That should not matter to any of us and we should offer our help regardless of whether he/she includes proper punctuation or not. I'm sure the effort he/she put into typing it was much greater than that of the ridiculous responses some of you gave.
thanks Crossvxm i appreciate that you came up for me its just i love the new 6.0.1 but there are a few new thing that google does not say and i thought it was a bug like my Bluetooth failing
biebie29 said:
thanks Crossvxm i appreciate that you came up for me its just i love the new 6.0.1 but there are a few new thing that google does not say and i thought it was a bug like my Bluetooth failing
Click to expand...
Click to collapse
The Note 4 is problematic all around, but 6.0.1 is a problem for every device that has it. It is the reason I left my Nexus 6P, and my Nexus 6. I have a Xiaomi Mi Max, also on 6.0.1 and it has the same major flaws I experienced on all devices running 6.0.1. The problems I speak of are the WiFi and Data stop working briefly while browsing the web, or downloading something. However, I believe this is an issue related to the security patches related to Qualcomm devices on 6.0.1. It seems like an overall radio problem.
In my research it looks like Samsung has disabled okay google trusted voice. In other words, when I say okay google with the screen off nothing happens even though I have trusted voice on. It works fine on my 6p.
My question is has anyone ever found a workaround for this.
It really annoys me they are trying to force me to use svoice to have this Android feature.
Yes, if you go to the Apps - settings - Language & Input - Look under virtual keyboard, there will be a little sprocket. You can click on that and tell it to allow 'ok google' only on the main screen, on any screen or anytime even when the phone is locked it will use your voice to unlock it. ,
I believe that if the screen is off, it must be charging so that is not wasting the battery listening for the command.
rbgCODE said:
Yes, if you go to the Apps - settings - Language & Input - Look under virtual keyboard, there will be a little sprocket. You can click on that and tell it to allow 'ok google' only on the main screen, on any screen or anytime even when the phone is locked it will use your voice to unlock it. ,
Click to expand...
Click to collapse
is there a way for nougat?
Outbreak444 said:
I believe that if the screen is off, it must be charging so that is not wasting the battery listening for the command.
Click to expand...
Click to collapse
It seems like that (may be?) true for the Exynos chip. The SnapDragon chip has the hardware built in (and activated) to 'always listen'. The SnapDragon 810 and later has this, and this phone should be able to do it.
This guy figured it out (somehow or other) - has to be the SnapDragon version, I believe, because it's on Sprint https://www.youtube.com/watch?v=zysh2GwYp9U
I have a european S7 (Exynos). I can wake the Phone with S-Voice by saying "Hello Galaxy" also when not charging.
A few weeks ago this also worked (only when charging) by saying "Ok Google", but this doesnt work anymore. I dont know whats the reason. I also dont have an option in the input settings where i can tell the phone when to listen to my voice. Does anyone know how to fix this with google?
I'm in the same boat as the previous comment. I was able to unlock the phone saying OK Google when the phone was plugged into Power. all settings are on for OK Google. Verizon Note 5 latest up-to-date firmware
The newer Google app updates have broken this feature. If you uninstall all updates of the Google app the original one works just fine with the screen off.
Hi all, hopefully this has not been discussed. I searched but from the xda app search isn't so great...
Anyway wondering if anyone is having issues with trusted voice. I noticed okay Google was only working when phone was authenticated. And not from secured lock screen. Figured trusted voice was disabled, so I checked and it's just not there. (See image). I'm on 4.5.8 stock not rooted. I have tried clearing data on Google app.
Any suggestions is appreciated.
Thanks!
I wanted to use Google Assistant so had to use the beta versions of Google app and services. My Smart Lock screen is showing Trusted Voice, Trusted Face, On body, Trusted places, Trusted devices. With that being stated Google Assistant has never worked from my the lock screen which requires Trusted Voice to be enabled. Of course it's enabled on my OP5 but still doesn't work, which is a real pain in the butt.
Current versions:
Google v7.9.18.21.amd64
Google Play Services v11.5.20
I running OOS v4.5.8 with an unlocked bootloader and rooted (SuperSU). Recently I changed from stock to the Franco Kernel but Trusted voice has been available on my OP5 since I first got this device. My replacement of the stock kernel made no difference in this case.
3DSammy said:
I wanted to use Google Assistant so had to use the beta versions of Google app and services. My Smart Lock screen is showing Trusted Voice, Trusted Face, On body, Trusted places, Trusted devices. With that being stated Google Assistant has never worked from my the lock screen which requires Trusted Voice to be enabled. Of course it's enabled on my OP5 but still doesn't work, which is a real pain in the butt.
Current versions:
Google v7.9.18.21.amd64
Google Play Services v11.5.20
I running OOS v4.5.8 with an unlocked bootloader and rooted (SuperSU). Recently I changed from stock to the Franco Kernel but Trusted voice has been available on my OP5 since I first got this device. My replacement of the stock kernel made no difference in this case.
Click to expand...
Click to collapse
That's dumb! Have you tried toggling Smart lock in the trust agents of the security menu?
Also I noticed you're in Canada (eh?), mind if I ask which language you run as primary on your device? English US, Canada?
I started on English US as google assistant wouldnt fire up with Canada, but since then, I'm back to English Canada. Assistant still works, but as mentioned only when phone is unlocked.
tsuttie99 said:
That's dumb! Have you tried toggling Smart lock in the trust agents of the security menu?
Also I noticed you're in Canada (eh?), mind if I ask which language you run as primary on your device? English US, Canada?
I started on English US as google assistant wouldnt fire up with Canada, but since then, I'm back to English Canada. Assistant still works, but as mentioned only when phone is unlocked.
Click to expand...
Click to collapse
I'd read that others (UK) switched back to their native language after getting Google Assistant working and all was well. I've left it as US as primary with Canada as a second as it simply doesn't effect me. I like spelling colour as "color" which always made more sense to me.
My real reason for not switching back is that I've done a lot of home automation scripting with Google Assistant/Tasker's Voice Assist/Termux to automate my audio/video equipment and associated lighting. As far as I'm concerned Google Assistant may be in beta for built in functionality but is alpha for any third party integration. Every Google app update seems to break something while fixing other functionality (e.g. macros).
I like the automation I've created enough that I have little interest in rocking the boat at the moment. I had previously retested Trusted voice and the lock screen after updates and will again until it works. Right now I'm using a work around with an app called Caffeine (disables the lock screen timeout when charging) and Screen off (only turns the screen off but does not trigger the lock screen).
Also I may have tried toggling Trusted agents as I did so many tests and retests while working on Google Assistant functionality, I just can't remember.
I think there is something very broken with Smart Lock on this phone's stock OS.... I set up my cars BT as trusted device.... still i need to Authenticate with finger/pattern. Coming from a 6P where this all worked seamlessly it's frustrating.
My assisstant works from lock screen with "OK Google".
Stock 4.5.8 with root.
I boot into TWRP instead of flashing the recovery. Still have stock recovery.
Use Magisk v13.3 with Magisk Manager 5.1.1.
Have English (US) as my primary language with English (Australia) as my 2nd.
ultramag69 said:
My assisstant works from lock screen with "OK Google".
Stock 4.5.8 with root.
I boot into TWRP instead of flashing the recovery. Still have stock recovery.
Use Magisk v13.3 with Magisk Manager 5.1.1.
Have English (US) as my primary language with English (Australia) as my 2nd.
Click to expand...
Click to collapse
By the way how do you pull off the trick of "boot into TWRP"? I've never read about how to do that. Also what does it buy you other than maybe the GA working on the lock screen?
3DSammy said:
By the way how do you pull off the trick of "boot into TWRP"? I've never read about how to do that. Also what does it buy you other than maybe the GA working on the lock screen?
Click to expand...
Click to collapse
Just get your phone plugged into your PC and from bootloader you type "fastboot boot recovery <twrp file name>.img
It will just boot from that image instead of writing it to flash
tsuttie99 said:
Just get your phone plugged into your PC and from bootloader you type "fastboot boot recovery <twrp file name>.img
It will just boot from that image instead of writing it to flash
Click to expand...
Click to collapse
Interesting trick, thanks for the info.
Unfortunately I could not use it as I had to borrow a relatives Win10 PC just to flash TWRP in the first place as I couldn't get around that fastboot file size error multiple people experienced no matter which USB ports (v2 or v3) or adb versions I tried. Going to another computer (same model of motherboard) and TWRP was flashed in a second.
3DSammy said:
Interesting trick, thanks for the info.
Unfortunately I could not use it as I had to borrow a relatives Win10 PC just to flash TWRP in the first place as I couldn't get around that fastboot file size error multiple people experienced no matter which USB ports (v2 or v3) or adb versions I tried. Going to another computer (same model of motherboard) and TWRP was flashed in a second.
Click to expand...
Click to collapse
No worries, I've never actually used that trick as I can always think of a good reason to just have TWRP installed. But times are weird right now, I'm still 100% stock on this phone aside from oem unlock toggle being set. This is the longest I've gone on a fully stock setup. Aside from this Smart Lock/Trusted Voice issue everything is perfect on the OS.
Okay so this is weird. I can't believe i didn't try this test. I can yell "okay google" until the cows come home while the screen is off. it wont light up or unlock. However if i wake the screen THEN say okay google, my phone unlocks and assistant begins working. Is this the same for others who claim "everything is working fine for me"?
tsuttie99 said:
No worries, I've never actually used that trick as I can always think of a good reason to just have TWRP installed. But times are weird right now, I'm still 100% stock on this phone aside from oem unlock toggle being set. This is the longest I've gone on a fully stock setup. Aside from this Smart Lock/Trusted Voice issue everything is perfect on the OS.
Click to expand...
Click to collapse
I'm on stock oos & I'm using Blu kernel & Blu twrp. Blu kernel was so good on the op3T that OnePlus sent him a free op5 last week. I really like the Blu kernel, so much I switched from RR to oos for the first time. OK Google is working to unlock my phone btw.
Rebel7022 said:
I'm on stock oos & I'm using Blu kernel & Blu twrp. Blu kernel was so good on the op3T that OnePlus sent him a free op5 last week. I really like the Blu kernel, so much I switched from RR to oos for the first time. OK Google is working to unlock my phone btw.
Click to expand...
Click to collapse
Thanks for the info. Can you share if you can unlock the phone with OK google with the screen off? Scenario: Your phone is on a nearby table and you are a few feet away from it, the screen is off, the phone is not charging. Can you OK google without touching the phone?
tsuttie99 said:
Thanks for the info. Can you share if you can unlock the phone with OK google with the screen off? Scenario: Your phone is on a nearby table and you are a few feet away from it, the screen is off, the phone is not charging. Can you OK google without touching the phone?
Click to expand...
Click to collapse
There's a xda article on OK Google that has a hack to do that. I tried it it works.. But that was 3 months ago
tsuttie99 said:
Okay so this is weird. I can't believe i didn't try this test. I can yell "okay google" until the cows come home while the screen is off. it wont light up or unlock. However if i wake the screen THEN say okay google, my phone unlocks and assistant begins working. Is this the same for others who claim "everything is working fine for me"?
Click to expand...
Click to collapse
Yep, works from lock screen, not screen off...
tsuttie99 said:
Okay so this is weird. I can't believe i didn't try this test. I can yell "okay google" until the cows come home while the screen is off. it wont light up or unlock. However if i wake the screen THEN say okay google, my phone unlocks and assistant begins working. Is this the same for others who claim "everything is working fine for me"?
Click to expand...
Click to collapse
Well fancy that. I just did your test, locked screen with power button, with screen off there's no reaction to "OK Google". I then double tap the screen and the lock screen displays. Now "OK Google" unlocks the phone and Google Assistant is fully functional.
Kind of feels like a sprinter that falls inches before the finish line. What the heck Google or OnePlus? I wonder if custom ROMs have the same issue?
Thanks for noticing this phenomena and posting about it.
At this point, I'm feeling a lot of love and hate for my PH-1, but I'm locked in. I'm on the Sprint lease plan and I'm passed the point of returning the thing. So here's the latest issues:
Voice-to-Text: Whether it's in Chrome, Brave, Messenger, Google Assistant or Keep, voice-to-text has the same problem. First of all, when the phone says it's listening, I have to wait a few seconds before saying anything. Otherwise, it'll miss the first few words of whatever I'm about to say. The other problem: If I'm trying to do voice-to-text, it'll take about 5 words and stop taking anymore even though the phone appears to still be actively listening. At that point, I can cancel and then tap the microphone button again. This will allow me to voice-to-text 5 more words. So voice to text is barely usable at this point.
I installed Google Voice, but it won't take over as the default voicemail app. I've dug around in Settings and such, but I can't seem to find where I can change this. Presumably, the install of Google Voice should have taken care of it, but that doesn't appear to have happened. It has all my old voicemail from my prior phone, but nothing since getting the PH-1.
Stays connected to my car and my LG headphones no problem, but has issues losing connection anytime my ASUS Zenwatch 2 runs out of battery. Three times so far, I've had to wipe the watch and reconnect to get the two devices talking to each other again.
Google Keyboard is interesting and all, but it seems to do a great job of registering the wrong keystrokes. Honestly, I'd gotten used to my Samsung keyboard anyways, so if there's an option to map the same second character layout, that'd be ideal. But I definitely need SOME keyboard app that presents large enough keys that my huge hands won't confuse the phone. G Board is as big as I can make it and it's just not enough.
BonkersTheClown said:
At this point, I'm feeling a lot of love and hate for my PH-1, but I'm locked in. I'm on the Sprint lease plan and I'm passed the point of returning the thing. So here's the latest issues:
Voice-to-Text: Whether it's in Chrome, Brave, Messenger, Google Assistant or Keep, voice-to-text has the same problem. First of all, when the phone says it's listening, I have to wait a few seconds before saying anything. Otherwise, it'll miss the first few words of whatever I'm about to say. The other problem: If I'm trying to do voice-to-text, it'll take about 5 words and stop taking anymore even though the phone appears to still be actively listening. At that point, I can cancel and then tap the microphone button again. This will allow me to voice-to-text 5 more words. So voice to text is barely usable at this point.
I installed Google Voice, but it won't take over as the default voicemail app. I've dug around in Settings and such, but I can't seem to find where I can change this. Presumably, the install of Google Voice should have taken care of it, but that doesn't appear to have happened. It has all my old voicemail from my prior phone, but nothing since getting the PH-1.
Stays connected to my car and my LG headphones no problem, but has issues losing connection anytime my ASUS Zenwatch 2 runs out of battery. Three times so far, I've had to wipe the watch and reconnect to get the two devices talking to each other again.
Google Keyboard is interesting and all, but it seems to do a great job of registering the wrong keystrokes. Honestly, I'd gotten used to my Samsung keyboard anyways, so if there's an option to map the same second character layout, that'd be ideal. But I definitely need SOME keyboard app that presents large enough keys that my huge hands won't confuse the phone. G Board is as big as I can make it and it's just not enough.
Click to expand...
Click to collapse
I have ZERO of these issues...
And Google voice hasn't put itself in the Google dialer since it was updated to material design like over a year ago...
Gboard is smart... And will get accustomed to your "large hands"
You do realize that this isn't the "***** at Essential" forum... Right?
Sent from my PH-1 using Tapatalk
rignfool said:
I have ZERO of these issues...
And Google voice hasn't put itself in the Google dialer since it was updated to material design like over a year ago...
Gboard is smart... And will get accustomed to your "large hands"
You do realize that this isn't the "***** at Essential" forum... Right?
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
I'm so happy for you! You have no problems in your life and nothing bad ever happens to you! Meanwhile, I see post after post after post on this forum where people are on their second or third PH-1 .... because their PH-1 had issues. Sprint's support for the Essential Phone is worse than nonexistent. Essential Phone's own support kinda sucks too. Honestly, this forum is the only resource for useful help I've been able to find period. Apparently, people posting who are frustrated with their new phone offends you. Meanwhile, I will continue to try to make my purchase of a PH-1 as livable as possible.
BonkersTheClown said:
I installed Google Voice, but it won't take over as the default voicemail app. I've dug around in Settings and such, but I can't seem to find where I can change this. Presumably, the install of Google Voice should have taken care of it, but that doesn't appear to have happened. It has all my old voicemail from my prior phone, but nothing since getting the PH-1.
Click to expand...
Click to collapse
Google broke the integration more than a year ago.
You will need to install an old version of the app manually.
The version you want is "com.google.android.apps.googlevoice_0.4.7.10.apk".
This is the last version that integrates with any dialer.
make sure you setup not to auto-update or the update will kill the integration.
BonkersTheClown said:
Stays connected to my car and my LG headphones no problem, but has issues losing connection anytime my ASUS Zenwatch 2 runs out of battery. Three times so far, I've had to wipe the watch and reconnect to get the two devices talking to each other again.
Click to expand...
Click to collapse
I didn't have that issue with my LG Urbane 2. Try uninstalling wear and reconnecting after resetting the watch.
BonkersTheClown said:
Google Keyboard is interesting and all, but it seems to do a great job of registering the wrong keystrokes. Honestly, I'd gotten used to my Samsung keyboard anyways, so if there's an option to map the same second character layout, that'd be ideal. But I definitely need SOME keyboard app that presents large enough keys that my huge hands won't confuse the phone. G Board is as big as I can make it and it's just not enough.
Click to expand...
Click to collapse
Maybe Swiftkey, but I used Gboard.
tech_head said:
Google broke the integration more than a year ago.
You will need to install an old version of the app manually.
The version you want is "com.google.android.apps.googlevoice_0.4.7.10.apk".
This is the last version that integrates with any dialer.
make sure you setup not to auto-update or the update will kill the integration.
Click to expand...
Click to collapse
Thanks, that explains a lot. Weird that they broke the integration. Can't think of a good reason for them to want to do that. Alternately, is there a different voicemail app that would work? Google Voice has it's good points, but if letting an update sneak through breaks it, I don't see the point in using Google Voice. Sometimes updates patch vulnerabilities after all.
Did Google replace Google Voice with something else perhaps?
I didn't have that issue with my LG Urbane 2. Try uninstalling wear and reconnecting after resetting the watch.
Click to expand...
Click to collapse
Did that so we'll wait and see. Hopefully it doesn't break again.
Maybe Swiftkey, but I used Gboard.
Click to expand...
Click to collapse
By rights, GBoard should be working great and isn't. Not really sure why. I've given myself time to get used to it but I fat finger crap way too much. I'll try Swiftkey and see if that works.
Thanks for the help!
Just an FYI, I have no issues with latest google voice, integrated with hangouts and used for my voicemail with Verizon after doing the standard *71(googlevoice#) *90(googlevoice#) an *92(googlevoice#). Maybe Sprint has a similar method of call forwarding you can use?
Also, maybe your phone has a hardware issue with a microphone. It wouldn't be the first case. Many of us really don't have an issue with voice to text, so that might be something to RMA about if you can test further.
manaox2 said:
Just an FYI, I have no issues with latest google voice, integrated with hangouts and used for my voicemail with Verizon after doing the standard *71(googlevoice#) *90(googlevoice#) an *92(googlevoice#). Maybe Sprint has a similar method of call forwarding you can use?
Also, maybe your phone has a hardware issue with a microphone. It wouldn't be the first case. Many of us really don't have an issue with voice to text, so that might be something to RMA about if you can test further.
Click to expand...
Click to collapse
The issue is not about being able to use it, dialer integration is broken.
Without integration you can't go to the dialer and listen to your VM.
tech_head said:
The issue is not about being able to use it, dialer integration is broken.
Without integration you can't go to the dialer and listen to your VM.
Click to expand...
Click to collapse
Try oreo beta... Or wait to oreo ota.. looks to be working or close to working in beta
Sent from my PH-1 using Tapatalk