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
Related
Don't you all agree?
not really. what bugs are you talking about?
I have had a G1, Mytouch, and now the Nexus - I see and have no bug issues with my Unit...
If you could explain what bugs (or problems) you are having ... Is this your first Andriod ???
zachthemaster said:
Don't you all agree?
Click to expand...
Click to collapse
100% disagree.
My phone is amazing. What bugs are you experiencing?
Be more specific? before or after the ota? Mine is still kicking a## after the ota!
I Agree......
Even after the OTA update, the touch screen issue still exists.
the phone gets all buggy with registering touch (touching middle of screen activates haptic soft keys, at the bottom of screen), getting tired of constently rebooting...........
ratsoda said:
I Agree......
Even after the OTA update, the touch screen issue still exists.
the phone gets all buggy with registering touch (touching middle of screen activates haptic soft keys, at the bottom of screen), getting tired of constently rebooting...........
Click to expand...
Click to collapse
You don't have to reboot.
Just turn the screen off for 3 seconds and back on...
lol
Not everyone has this "touch screen accuracy" issue...
I haven't noticed any bugs that jump out at me. I would like them to improve the speech to text, and would love them to get the kernel with full RAM support out ASAP. I was sad this update did not have that. But, in a month when we get the next one I am confident and optimistic it will make it into it!
New RAM kernel.
Trackball/LED notification fix.
If its software the bottom row of buttons being difficult to register.
Those are all legit HW/SW issues that are unique to the N1 and need to be resolved.
New RAM kernel - not a bug
Trackball/LED notification fix - what's the issue?
If its software the bottom row of buttons being difficult to register. - Not a bug. As I posted in the tips and tricks thread, aim for the top edge, where the screen meets the black border and you'll hit it every single time. Not many people know about this and that's why they always complain. This is just user error
Paul22000 said:
New RAM kernel - not a bug
Trackball/LED notification fix - what's the issue?
If its software the bottom row of buttons being difficult to register. - Not a bug. As I posted in the tips and tricks thread, aim for the top edge, where the screen meets the black border and you'll hit it every single time. Not many people know about this and that's why they always complain. This is just user error
Click to expand...
Click to collapse
Whether you label it as a "bug" or not its still an issue.
Half the available RAM not being used.
The ability for Devs/Apps to customize the LED/Trackball is a feature removed.
And considering the Droid has the same panel and not the issues it is in fact a problem that the keys and "touch" area are not aligned. Thats a design flaw and nothing to do with user error.Its like asking the user to tap the Q to get a W.
Those are 2 out of the box gimpings of available hardware.
And one either HW problem or design flaw. In which case can be chalked up to "it is what it is".
xManMythLegend said:
Whether you label it as a "bug" or not its still an issue.
Click to expand...
Click to collapse
Well, the OP is asking for a bug fix update. A bug is something that is not working as intended.
For Example,
Half the available RAM not being used.
Click to expand...
Click to collapse
If the Android developers intended for there to be half, then it's not a bug. Having all of the available ram is more of a new feature.
The ability for Devs/Apps to customize the LED/Trackball is a feature removed.
Click to expand...
Click to collapse
I don't remember this ever being possible? When did they remove it?
And considering the Droid has the same panel and not the issues it is in fact a problem that the keys and "touch" area are not aligned. Thats a design flaw and nothing to do with user error.Its like asking the user to tap the Q to get a W.
Click to expand...
Click to collapse
It's hard to say without having a Droid and Nexus One together side by side. If they are exactly the same touch pads, and you can clearly prove that the same exact precision keypress on the Droid works 100% of the time on the Droid and not on the Nexus One, then I can agree it's a bug.
If they intended it to be so that you have to use your whole thumb (or aim for the top), then no bug. I find that if I use my entire thumb, it will always land 100% of the time no matter where I aim, so that's why I say it's hard to say it's a bug or not.
But again, this is the only one that I might agree is a bug. The other two are definitely feature requests
Paul22000 said:
Well, the OP is asking for a bug fix update. A bug is something that is not working as intended.
For Example,
If the Android developers intended for there to be half, then it's not a bug. Having all of the available ram is more of a new feature.
I don't remember this ever being possible? When did they remove it?
It's hard to say without having a Droid and Nexus One together side by side. If they are exactly the same touch pads, and you can clearly prove that the same exact precision keypress on the Droid works 100% of the time on the Droid and not on the Nexus One, then I can agree it's a bug.
If they intended it to be so that you have to use your whole thumb (or aim for the top), then no bug. I find that if I use my entire thumb, it will always land 100% of the time no matter where I aim, so that's why I say it's hard to say it's a bug or not.
But again, this is the only one that I might agree is a bug. The other two are definitely feature requests
Click to expand...
Click to collapse
How about the dots which indicate the screen you are on being off.
You seem a little blinded by your love of Android. I like it too, but it is not without it's problems, just like any other software. You've convinced yourself that the the misaligned buttons are that way on purpose...really?
The wifi is very buggy, bluetooth as well. There are also notification protocols that seems a bit buggy, sometimes they pop up, sometimes they don't, sometimes they vibrate, sometimes not. E-mail client inbox refresh doesn't reconcile with server with read/unread messages, even though data packets are received. To name a couple...
gibosn6594 said:
How about the dots which indicate the screen you are on being off.
Click to expand...
Click to collapse
This is a bug yes. Introduced with this week's OTA.
You seem a little blinded by your love of Android. I like it too, but it is not without it's problems, just like any other software. You've convinced yourself that the the misaligned buttons are that way on purpose...really?
Click to expand...
Click to collapse
Blinded? No. But if something is 95% good, and 5% bad, I'm going to focus on the 95%, not the 5%
And the buttons might be that way on purpose, yes.
Even if not, I've found a way to use them so they always work for me (aiming for the top) so it doesn't bother me. If I had not figured that out, then I could see how it could be frustrating.
The wifi is very buggy, bluetooth as well.
There are also notification protocols that seems a bit buggy, sometimes they pop up, sometimes they don't, sometimes they vibrate, sometimes not.
Click to expand...
Click to collapse
Can you give specific instances of issues with these?
E-mail client inbox refresh doesn't reconcile with server with read/unread messages, even though data packets are received. To name a couple...
Click to expand...
Click to collapse
I haven't had issues with the email refreshing at all. In fact, when I'm sitting at my PC, my phone vibrates and makes a sound for new emails. I switch tabs in Firefox to Gmail and the email hasn't even shown up yet; I have to click inbox to refresh Gmail to make the email show up. My phone's email is faster than my PC's; that's how fast it is for me
Paul22000 said:
This is a bug yes. Introduced with this week's OTA.
Blinded? No. But if something is 95% good, and 5% bad, I'm going to focus on the 95%, not the 5%
And the buttons might be that way on purpose, yes.
Even if not, I've found a way to use them so they always work for me (aiming for the top) so it doesn't bother me. If I had not figured that out, then I could see how it could be frustrating.
Can you give specific instances of issues with these?
I haven't had issues with the email refreshing at all. In fact, when I'm sitting at my PC, my phone vibrates and makes a sound for new emails. I switch tabs in Firefox to Gmail and the email hasn't even shown up yet; I have to click inbox to refresh Gmail to make the email show up. My phone's email is faster than my PC's; that's how fast it is for me
Click to expand...
Click to collapse
As far as BT and wifi, it poorly handles the switchover. When disconnected, the attempt to reconnect does not always work, to put is simply.
The e-mail client issue is not with gmail, it is with the exchange integration on corporate accounts.
gibosn6594 said:
As far as BT and wifi, it poorly handles the switchover. When disconnected, the attempt to reconnect does not always work, to put is simply.
The e-mail client issue is not with gmail, it is with the exchange integration on corporate accounts.
Click to expand...
Click to collapse
Ah yes, I have noticed that turning on wifi sometimes it just sits there and doesn't connect until I open up wifi settings. Definite bug.
Oh, exchange. Yeah, I have heard exchange is pretty bad on the N1 (or non-existant without the file from the dev forum?). I don't use it so I can't comment. But supposedly, there will be a Nexus One Enterprise edition with full Exchange support, and a physical keyboard So maybe this one is not aimed at people who rely on it.
Cool thing about Android and this phone: all of the above mini-bugs can and IMO will be fixed. Something which you cannot say for most phones out there. That's why I love it - devs can do almost anything they want with it. Makes me go back to the list of smartphones behind this: If you had a problem you had to get used to it - so I think we all should give the guys working on the N1 a break - I mean we got an OTA upgrade LESS than a month after the phone went on the market which gave us multi-touch. So most of the bugs do exist but they are minor when compared to most of the mobile market and IMO Google is committed to fix them.
Paul22000 said:
Well, the OP is asking for a bug fix update. A bug is something that is not working as intended.
For Example,
If the Android developers intended for there to be half, then it's not a bug. Having all of the available ram is more of a new feature.
I don't remember this ever being possible? When did they remove it?
It's hard to say without having a Droid and Nexus One together side by side. If they are exactly the same touch pads, and you can clearly prove that the same exact precision keypress on the Droid works 100% of the time on the Droid and not on the Nexus One, then I can agree it's a bug.
If they intended it to be so that you have to use your whole thumb (or aim for the top), then no bug. I find that if I use my entire thumb, it will always land 100% of the time no matter where I aim, so that's why I say it's hard to say it's a bug or not.
But again, this is the only one that I might agree is a bug. The other two are definitely feature requests
Click to expand...
Click to collapse
Ive had the Droid and N1 side by side which is when I realized its a design flaw or OS issue.
Both the RGB trackball and 512mb ram were both advertised as such. Including in the initial press conference. Those arent feature requests those are hardware limitations that have yet to be addressed.
The ram limitation has at least been acknowledged.
As for the LED/trackball. Its been a feature since the G1. Theres bunches of apps including the most popular messaging app that allow you to designate different colors and flash rates for LEDs for notifications.
N1 is great but before we can move forward I would like for Google to address these pretty significant things.
MT was a major feature add. But the 3g fix is still plaguing many users.
All in all N1/Android 2.1 are fantastic. Googles lack of communication frustrates too many people.
Maybe Im too used to games but good Devs are constantly in touch with users concerning bugs and issues and are pretty consistent with "update/bug fix" information and ETAs.
The fact that google is just getting phone support hiring going is pretty silly.
Im an early adaptor so I know the risks. But this really is a barely past Beta piece of hardware. I dont see the harm in other early adapters acknowledging that.
Frankly if it wasnt for users ((and haters)) *****ing and moaning non stop I dont think MT would have been put out and a 3g fix would have been put off.
The way Googles worked recently whining gets more results then sitting and waiting.
dbaboci said:
Cool thing about Android and this phone: all of the above mini-bugs can and IMO will be fixed. Something which you cannot say for most phones out there. That's why I love it - devs can do almost anything they want with it. Makes me go back to the list of smartphones behind this: If you had a problem you had to get used to it - so I think we all should give the guys working on the N1 a break - I mean we got an OTA upgrade LESS than a month after the phone went on the market which gave us multi-touch. So most of the bugs do exist but they are minor when compared to most of the mobile market and IMO Google is committed to fix them.
Click to expand...
Click to collapse
I agree.
Heres my primary issue.
The guys at google seem like a bunch of brilliant engineers but rely rounds of feedback to get things right.
There creative and quality control people are suspect IMO.
Engineers tend to be a snobbish anti-social bunch. You dont want that leaking into consumer products. The communication pitfalls of this month highly reflect that mentality. They need another layer. They seem to desire it though so thats good.
ratsoda said:
I Agree......
Even after the OTA update, the touch screen issue still exists.
the phone gets all buggy with registering touch (touching middle of screen activates haptic soft keys, at the bottom of screen), getting tired of constently rebooting...........
Click to expand...
Click to collapse
Same here,,,,,I encountered this problem once, after I had updated (never tired before update)..
Since the update to GB... my voice-to-text has not been working properly in the car. I first thought it might be background noise like the A/C or something but it appears to only happen when the car is moving.
Isn't this the whole point of voice-to-text? To keep you safe while driving so it doesn't require typing. Am I the only one with this problem? Is there any kind of workaround? I depend heavily on this feature. This is a big negative for me.
Same issue here. Voice to text has been broken for me since the first GB update on a stock unrooted EVO.
busted here too.
sucks.
Yes this happens to me too.
Just quit using your phone in the car so i can quit flipping you people off!
Have y'all tried updating voice search from the market? I noticed there was a recent update for it mentioning bug fixes.
Tried updating everything. Full factory restore on Unrooted GB 2.3.3 both the first release and with the maintenance fix. Changed Voice Input and Output settings. Changed the Google account dashboard and personalization. Everything and even rolling back to 2.2 which doesn't work because of the new Hboot.
It is completely broken. You get going 20-25mph+ and the mic does not respond.
Hope that it is address in a future release update (not likely), but will have to root and roll back.
Can any one that is rooted and on the stock 2.3 or different rom confirm if voice search is working for them?
AudioJerm said:
Have y'all tried updating voice search from the market? I noticed there was a recent update for it mentioning bug fixes.
Click to expand...
Click to collapse
Yeah... I updated Voice Search and I will find out later if it works when I get in my car.
Well, I did the Voice Search update and still can't do voice to text in the car while it's moving. This is ridiculous! I love using HeyTell especially when driving and now it has become useless.
A guy at work asked me today if i knew anything about this problem. He has had this problem since the GB update and his EVO is stock and not rooted. I told him I would look into it. Looks like I found the answer.
Sent from my HTC EVO 4G with Tapatalk
I did; however, find out that the voice search does work in the texting mode once you've hit the car in front of you wondering why it wasn't working during the driving process. Once stopped, it is amazing!
EDIT: OK..couldn't resist, but reminds me of the little "Don't use this while your driving" disclaimer in the gps units turning them on.
I've had issues with it when not moving.
I'm not sure where this connection to driving comes into play?
dpilcher said:
I did; however, find out that the voice search does work in the texting mode once you've hit the car in front of you wondering why it wasn't working during the driving process. Once stopped, it is amazing!
EDIT: OK..couldn't resist, but reminds me of the little "Don't use this while your driving" disclaimer in the gps units turning them on.
Click to expand...
Click to collapse
The whole advantage of voice-to-text is so you don't text while driving. My phone sits in a dock in the car. If someone texts me, I can verbally respond without taking my hands off the wheel. You know... kinda like talking on the phone hands-free. That's why voice-to-text is so valuable to me.
Earlier tonight I discovered the problem is worse. I was outside taking a walk and decided to use voice-to-text and nothing. Would not recognize. But once I stopped walking and used it... it was fine. So it's not just limited to driving. They need to fix this problem!
I did some looking around on Google and this issue has been reported on multiple different sites. However, it seems that it's more related to background noise rather than being in a moving vehicle. If there is any amount of background noise, voice to text seems to not work properly. It seems that it works fine if you are in a completely silent environment.
Sent from my HTC EVO 4G with Tapatalk
kd0axs said:
I did some looking around on Google and this issue has been reported on multiple different sites. However, it seems that it's more related to background noise rather than being in a moving vehicle. If there is any amount of background noise, voice to text seems to not work properly. It seems that it works fine if you are in a completely silent environment.
Sent from my HTC EVO 4G with Tapatalk
Click to expand...
Click to collapse
Yeah... I read the same thing but my tests did not ring true. When I was stopped at a light, I put the AC on at full blast and the voice-to-text worked flawlessly. But as soon as I moved and even with the AC off... nothing. For me, there didn't seem to be any connection with background noise... only movement.
My only other suggestion is to try an app called Vlingo for the mean time. The In Car mode is amazing. Just say "hey vlingo" and it starts listening to commands. It really is completely hands free. You never have to touch your phone to send texts and it even reads your message back to you to confirm before sending. I've never had problems with it although the in car mode is still in beta. Good luck!
I just spoke this entire post while driving 45 miles an hour down the road using Google voice search.
I had same issue on stock Rom. I believe if u look at main settings, voice input and output, text to speach settings, and in there it should say something about downloading something. If it needs updating u can press it and market will open with what u need
Sent from my PC36100 using XDA App
So I tried going through the text-to-speech settings but no luck. The issue doesn't seem to be with text-to-speech but with voice-to-text. It's like the microphone stops picking up audio when in motion.
Nevertheless... got this today from HTC...
Dear Jack Storm,
We are sorry to hear that you are experiencing issues with your Voice to Text after the recent update.
We are aware of the issues surrounding the update to your Evo and are currently working on addressing these issues. We do not currently have an exact timeframe as to when all of these issues will be resolved. Please check our official media outlets and/or your device for any change to the update status.
We do apologize for any inconveniences that this may have caused, Jack.
To send a reply to this message or let me know I have successfully answered your question log in to our ContactUs site using your email address and your ticket number 11USCW26ENA0065.
Sincerely,
Reisa
HTC
Works fine on CM7
Sent from my PC36100 using XDA Premium App
I'm absolutly loving Assist, specifically while driving. However, the volume is really LOUD. It's much louder than the standard notification volume.
Yes, I'm sure it's designed to be loud, but to prevent scaring my family every time it's activated, is there any way to turn the volme on Assist down? I haven't actually tried the volume rockers when Assist is active, since I'm busy driving!
oturn said:
I'm absolutly loving Assist, specifically while driving. However, the volume is really LOUD. It's much louder than the standard notification volume.
Yes, I'm sure it's designed to be loud, but to prevent scaring my family every time it's activated, is there any way to turn the volme on Assist down? I haven't actually tried the volume rockers when Assist is active, since I'm busy driving!
Click to expand...
Click to collapse
Wouldn't that be controlled by the volume slider "Music, Video games & Other media" in sound options? I'm not sure I'm just taking a shot in the dark here.
I really love assist too. However, I only use it to silence my phone at night time before bed and wake in the morning. An option so simple, yet many phones lack it.
Xaroc8 said:
Wouldn't that be controlled by the volume slider "Music, Video games & Other media" in sound options? I'm not sure I'm just taking a shot in the dark here.
I really love assist too. However, I only use it to silence my phone at night time before bed and wake in the morning. An option so simple, yet many phones lack it.
Click to expand...
Click to collapse
You would think so, but I have that slider set to about 60%, and it definitely doesn't appear to change the Assist volume.
oturn said:
You would think so, but I have that slider set to about 60%, and it definitely doesn't appear to change the Assist volume.
Click to expand...
Click to collapse
Assist obeys that volume on my phone. If I set it to around 10%, it's very quiet indeed.
I feel like I'm the only person that can't get assist to actually work. Doesn't tell me who the message is from or say the actual message.
Sent from my XT1058 using xda app-developers app
Mine does not work at all either... no driving, meeting nor sleeping assist work. I tried to clear data and cache but no luck.
Sent from my Nexus 7 using xda app-developers app
terasia said:
Mine does not work at all either... no driving, meeting nor sleeping assist work. I tried to clear data and cache but no luck.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Okay, I did factory reset last night, and all Assist features are working now. Obviously, there was a problem before but I am happy now.
terasia said:
Okay, I did factory reset last night, and all Assist features are working now. Obviously, there was a problem before but I am happy now.
Click to expand...
Click to collapse
Yeah I've done a factory reset, cleared cache in recovery. Everything I can think of. The assist activates when driving, the alert starts, but as soon as it needs to do text to speech with the actual name and message it just stops.
I feel like there is a conflict somewhere but I tried it with a clean install and nothing downloaded. Now that i've got TIBU maybe I should do a clean reinstall of the factory software and re-root and test that. may not be a bad idea.
Mine was doing the opposite so i had to disable it...mine would work fine when driving but would de-activate...so when I got home/to work/wherever and assist 'stopped' it would continue reading out who the message was from and asking me if i wanted it read to me. Which is really annoying because like others, the volume seemed incredibly loud and turning it down didn't help.
Anyone else have this issue? I've had to disable assist because of this, don't want to be sitting in a meeting and get a text and have it start screaming at me.
tjohnstone3 said:
Mine was doing the opposite so i had to disable it...mine would work fine when driving but would de-activate...so when I got home/to work/wherever and assist 'stopped' it would continue reading out who the message was from and asking me if i wanted it read to me. Which is really annoying because like others, the volume seemed incredibly loud and turning it down didn't help.
Anyone else have this issue? I've had to disable assist because of this, don't want to be sitting in a meeting and get a text and have it start screaming at me.
Click to expand...
Click to collapse
I'm having the exact same problem. It ALWAYS announces them to me, whether it's in driving mode or not. Even when my phone is on vibrate... I tried turning the Assist feature completely off, and it still announced them to me, very frustrating
same
jrkeyboard said:
I'm having the exact same problem. It ALWAYS announces them to me, whether it's in driving mode or not. Even when my phone is on vibrate... I tried turning the Assist feature completely off, and it still announced them to me, very frustrating
Click to expand...
Click to collapse
I have this issue as well. I love that it does talk to me when I'm driving (when it should) but to do it for every text message no matter what is crazy. Device should know the difference between when I'm driving and when i'm at home....on my own wifi....with screen on....using my device. Even when actually using the messaging app having a conversation with someone is very annoying, just show it to me in the app don't take me out of the app and make me talk/swipe notification away to look at what I was already looking at. I tried several things to fix it until I gave up and installed a 3rd party sms app from play store. Even tweeted Motorola Mobility about issue and they only linked me to the Touchless Control FAQ, useless.
I guess I could try clearing Assist's data, I'm not willing to do a factory reset or anything over the issue though.
I am on pwnmymoto on vzw motox. had previous 2 releases of moto root as well. not sure if any of these root options may be to blame in the matter.
monkespit said:
I have this issue as well. I love that it does talk to me when I'm driving (when it should) but to do it for every text message no matter what is crazy. Device should know the difference between when I'm driving and when i'm at home....on my own wifi....with screen on....using my device. Even when actually using the messaging app having a conversation with someone is very annoying, just show it to me in the app don't take me out of the app and make me talk/swipe notification away to look at what I was already looking at. I tried several things to fix it until I gave up and installed a 3rd party sms app from play store. Even tweeted Motorola Mobility about issue and they only linked me to the Touchless Control FAQ, useless.
I guess I could try clearing Assist's data, I'm not willing to do a factory reset or anything over the issue though.
I am on pwnmymoto on vzw motox. had previous 2 releases of moto root as well. not sure if any of these root options may be to blame in the matter.
Click to expand...
Click to collapse
I contacted Motorola support, got transferred to level 2, and then level 3... they finally acknowledged that they found a bug they are working on and will hopefully issue an update for it soon. In the meantime, he showed me how to disable it. If you're interested, go into Settings > Apps > All... scroll down to "Motorola Assist Talk to Me", select it, and then click Disable. This will disable the spoken alerts totally until an update can be pushed out. Once the update is pushed out, you will need to go back in here and re-enable it.
Not the ideal solution, but at least we know an update will be coming to fix it
jrkeyboard said:
I contacted Motorola support, got transferred to level 2, and then level 3... they finally acknowledged that they found a bug they are working on and will hopefully issue an update for it soon. In the meantime, he showed me how to disable it. If you're interested, go into Settings > Apps > All... scroll down to "Motorola Assist Talk to Me", select it, and then click Disable. This will disable the spoken alerts totally until an update can be pushed out. Once the update is pushed out, you will need to go back in here and re-enable it.
Not the ideal solution, but at least we know an update will be coming to fix it
Click to expand...
Click to collapse
What's the common denominator here though? What do those who have this bug have in common? Verizon? Pwnmymoto? Excessive luck?
Sent from my XT1060 using Tapatalk 4
monkespit said:
What's the common denominator here though? What do those who have this bug have in common? Verizon? Pwnmymoto? Excessive luck?
Sent from my XT1060 using Tapatalk 4
Click to expand...
Click to collapse
Has nothing to do w/ Pwnmymoto. I was having this issue from day 1 and well before using Pwnmymoto. So it is either Verizon or just Motorola Assist in general.
The speaking of texts while driving was pretty much the main feature i liked w/ Moto Assist (along w/ silencing phone at night) so I'm just going to leave it disabled until an update is out to fix it.
tjohnstone3 said:
Has nothing to do w/ Pwnmymoto. I was having this issue from day 1 and well before using Pwnmymoto. So it is either Verizon or just Motorola Assist in general.
The speaking of texts while driving was pretty much the main feature i liked w/ Moto Assist (along w/ silencing phone at night) so I'm just going to leave it disabled until an update is out to fix it.
Click to expand...
Click to collapse
So it is just the Verizon ones?
Sent from my XT1060 using Tapatalk 4
monkespit said:
So it is just the Verizon ones?
Sent from my XT1060 using Tapatalk 4
Click to expand...
Click to collapse
No clue, haven't paid close enough attention to the people reporting the issue. I'm assuming it isn't specific to Verizon but as I said, nothing to back that up.
tjohnstone3 said:
No clue, haven't paid close enough attention to the people reporting the issue. I'm assuming it isn't specific to Verizon but as I said, nothing to back that up.
Click to expand...
Click to collapse
Was just curious since it seems like some don't have this issue.
I'm happier replacing the stock messaging app than killing all the spoken alerts since that's the only time it gets annoying. Hopefully they will get to it sooner than later since it's just an app update. Thanks for the info.
Sent from my XT1060 using Tapatalk 4
When I say OK Google it opens up the voice command screen and prompts me to say OK Google to activate the mic. This makes it so I have to say OK Google twice to do a voice search or command. The crazy thing is that it is inconsistent so sometimes it does this and sometimes it works as intended. What is going on and how the heck do I fix this?
You can try clearing the data in the app and resetting your launch phrase. What build is your phone? Rooted? Does it happen when you're on mobile network rather than WiFi? Poor signal/data connection?
kboya said:
You can try clearing the data in the app and resetting your launch phrase. What build is your phone? Rooted? Does it happen when you're on mobile network rather than WiFi? Poor signal/data connection?
Click to expand...
Click to collapse
Im on the latest pure Nexus rom but it happened on stock as well. Seems to just happen whenever it feels like. I'll pay more attention from now on and see if I can answer your other questions.
Thanks
Hello, solved?
Exostenza said:
Im on the latest pure Nexus rom but it happened on stock as well. Seems to just happen whenever it feels like. I'll pay more attention from now on and see if I can answer your other questions.
Thanks
Click to expand...
Click to collapse
i get the same problem , G is just an unfinished POS just like android itself
no surprises here it never works right
and it stopped working altogether 3 times last month after "update" to the google app broke it completely
toxic company with a toxic culture make worthless unreliable products , shocker
Bought this brand new sealed and opened it up and updated to current.
Problem,
Microphone works great on the phone but won’t work anywhere else.
Ok google won’t voice match to open, voice memos, gboard, video call apps, etc.
Anyone else had this issue and fixed it?
First thing I'd do is check the app's permissions that they are allowed to use the mic
I did that
swedyk said:
I did that
Click to expand...
Click to collapse
did it work before you updated it?
Does it work with headset etc?
I'd try going to reset all apps, as a first try.
Last resort, reflash.
IronRoo said:
did it work before you updated it?
Does it work with headset etc?
I'd try going to reset all apps, as a first try.
Last resort, reflash.
Click to expand...
Click to collapse
When you plug in a headset with a mic it works fine.
Don’t know about working first because updates were right away as I knew the phone at start was not a good experience until all the updates made it great.
swedyk said:
Bought this brand new sealed and opened it up and updated to current.
Problem,
Microphone works great on the phone but won’t work anywhere else.
Ok google won’t voice match to open, voice memos, gboard, video call apps, etc.
Anyone else had this issue and fixed it?
Click to expand...
Click to collapse
I think you/we are suffering from an software issue. The PH-1 and other devices like the OP6 have the problem that thirdparty apps are using the wrong microphone, even the camera app. For me this is causing very low volume in recorded videos and anreliable "OK google" trickering the assistant. I don't use whatsapp or snapchat, so can't say anything about it.
https://www.androidpolice.com/2019/...-mic-in-some-apps-like-snapchat-and-whatsapp/
Hopefully it will be fixed later once. Fingers crossed :silly:
swedyk said:
When you plug in a headset with a mic it works fine.
Don’t know about working first because updates were right away as I knew the phone at start was not a good experience until all the updates made it great.
Click to expand...
Click to collapse
LOL, yes suppose most of us would immediately update phone is s oon as we got it also
yes, I'd think it's software issue, I've also heard of similar problems on other phones & oK goggle also causing mic issue, that's very I suggested using the reset all app option. Maybe also try boot into safe mode to see if it's a 3rd party app causing this.