Works sometimes, but often I have to reboot to get it to work again. Anybody else experiencing this? Have checked that settings are correct.
Mine has never worked, screen off or screen on from the lockscreen. I've rebooted multiple times. Between this and the creaky back panel that flexs, & the garbage battery life, I'm beginning to regret this purchase.
You've set language to English US?
Ya it's set to english(United States). Doesn't work from the lockscreen or with screen off. Does it work on yours?
---------- Post added at 12:50 PM ---------- Previous post was at 12:42 PM ----------
I just restarted it and now it works. For the first time ever. Even though I have restarted this thing many times before. Let's hope it keeps working. Definitely buggy.
Mine doesn't work either. Language set to EN-US, and retrained the voice model 4 times already. Works when I'm in the launcher, but anywhere else and it doesn't work. Seems to be a Nexus 9 problem as my HTC One M7 works perfectly even in lock screen.
Works every time after reboot for me, but stops after using just a couple of other apps.
UAL4588 said:
Mine doesn't work either. Language set to EN-US, and retrained the voice model 4 times already. Works when I'm in the launcher, but anywhere else and it doesn't work. Seems to be a Nexus 9 problem as my HTC One M7 works perfectly even in lock screen.
Click to expand...
Click to collapse
EXACTLY the same problem here (works fine on my Oneplus One, but only in the launcher on the Nexus). This thing is really buggy...
Related
I have this issue: I'm running on CM10, build 2012-08-18 and I would to like to upgrade to latest build. When I install CM10 nightly (or anything build) over the original build and then I make a call I don't hear anything :crying:
OK, then I make full wipe and voila, it works! OK, I wait when applications restore from google account but they don;t restore all settings (for example Touchdown), so I restore Apps/Data/Both via MyBackup Restore and... no sound when make call :crying::crying:
Long story short: on CM10 I cannot restore anything else I lost sound when callind (no ringtone but don't hear second side).
This is unpleasant because restoring system get a lot of time.
Any ideas?
P.S. More into about my phone: flashed original ROM via ODIN, then root and recovery, then CM10. No Jelly Bean leaked ROMs were installed after flashing original ROM (ICS).
Same here!
Do you found a fix?
Yeah. M also facing same
pradeepb said:
Yeah. M also facing same
Click to expand...
Click to collapse
Try flashing modems. If it dont work, send to technical assistence.
Enable lockscreen sounds....known cm10 problem
any resolution? i have sound working until i make first call in ANY app (viber,skype,csipsimple,caller).
doggydog2 said:
any resolution? i have sound working until i make first call in ANY app (viber,skype,csipsimple,caller).
Click to expand...
Click to collapse
read above
I don't even have lockcreen enabled and I don't see any sound settings there.
I got the same problem on cm10.1 2012-01-03 nightly, this is a serious problem that they need to solve..
---------- Post added at 12:51 PM ---------- Previous post was at 12:48 PM ----------
OK I just solved this problem by enabling lock screen sounds, at first it did not work but then I restarted and it works, credits to whoever figured this out
shaneel1491 said:
I got the same problem on cm10.1 2012-01-03 nightly, this is a serious problem that they need to solve..
---------- Post added at 12:51 PM ---------- Previous post was at 12:48 PM ----------
OK I just solved this problem by enabling lock screen sounds, at first it did not work but then I restarted and it works, credits to whoever figured this out
Click to expand...
Click to collapse
Did you mean 2013-01-03? Me too but for me helped enabling repro during the call and then disabling it and then all works well
It is a really really annoying bug. A system sound has to be made first - the lock screen does that IF you have sound on. If you make a call before doing this, forget about any sound.
I agree it is a pain in the arse and if I knew how to fix it I would. You can use Tasker to reset the volume, play a sound, then reset volume, but it is annoying. Only thing stopping me switching over.
SOLVED
Hi guys.
Don't know if this helps someone now, but i had this problem recently on two different phones. Two weeks ago with my HTC One M7 and today with my girlfriends SGS3 i9305. with HTC i didn't figured out back then what was the problem, but i fixed it somehow after re-flashing/re-installing .. but now i think i know what was the problem. With both phones in-call sound/mic disappeared for no reason. what i noticed in both cases problem was restoring my setting from Google account. with HTC i did not give attention to that, i was happy that it worked after some 5h of trying different things. But now with SGS3 after many attempts i tried without Google restore and voila ... works just fine. After this i connected phone to Google account, but did not restored settings.
I rad many forums and saw that in case of SGS3 it can be hardware problem..but in my case I've tried VIBER and everything was working good. so it was not mic/earpiece problem for sure.
Hope someone finds this useful.
Happy Holidays to everyone!
Hi guys,
I hope that this is the proper forum, if not please direct me to the correct one.
I am currently using a Sprint Samsung Galaxy S6, non-rooted.
My problem started about 48 hours ago while I was voice dictating a test message.
I was doing my regular texting with the SwiftKey keyboard microphone (problem also replicates with the Samsung Keyboard as well) and the box at the bottom of the screen would not go away. I tried to X it out, hit the back button and the home button but nothing gets rid of it other than restarting the phone.
This all seemed to start happening after the Google App update.
I rolled back to the old version and it seemed to work fine. Last night, it updated itself again and problem was back.
I have included an image of what I am talking about.
If anyone has any suggestions, I would be very appreciative!
Thanks
Mikeinstlouis
I have to same issue that just happened and same as the screenshot.
Same issue...
This is so freaking ridiculous! A Google update that does this crap?!
I too own a S6 Edge Verizon 128GB and I noticed a couple of things.
If you bring up text to speak and then power off your phone.. Once you come back... you have locked it (Until restart)
I tried the following...
1) Reset the Dalvik Cache .. No luck.
2) tried force closing TTS and samsung text to speech.. no go.
3) Uninstalling latest update to the high quality voice. .. No Go.
4) Tried holding both buttons at the Same Time... No go..
5) For quibs and giggles.. Held down the close "X" for 5 whole minutes.
********************************************
What I think is going on is a time out error in the code.
So how i am able to get around it RARELY is..
Bring it up with the microphone button
Say what I need to say then hit the X to close it as FAST AS I CAN!!
I know that with all of our phone hackers, crackers and experts that we can ALL reach a Fix on this.
Damn Google...
mikeinstlouis said:
Hi guys,
I hope that this is the proper forum, if not please direct me to the correct one.
I am currently using a Sprint Samsung Galaxy S6, non-rooted.
My problem started about 48 hours ago while I was voice dictating a test message.
I was doing my regular texting with the SwiftKey keyboard microphone (problem also replicates with the Samsung Keyboard as well) and the box at the bottom of the screen would not go away. I tried to X it out, hit the back button and the home button but nothing gets rid of it other than restarting the phone.
This all seemed to start happening after the Google App update.
I rolled back to the old version and it seemed to work fine. Last night, it updated itself again and problem was back.
I have included an image of what I am talking about.
If anyone has any suggestions, I would be very appreciative!
Thanks
Mikeinstlouis
Click to expand...
Click to collapse
Latest update have little bugs
Sent from my Nexus 5 using Tapatalk
I am also having this issue on my Galaxy S4.
---------- Post added at 02:56 PM ---------- Previous post was at 02:46 PM ----------
mrneoz81 said:
This is so freaking ridiculous! A Google update that does this crap?!
I too own a S6 Edge Verizon 128GB and I noticed a couple of things.
If you bring up text to speak and then power off your phone.. Once you come back... you have locked it (Until restart)
I tried the following...
1) Reset the Dalvik Cache .. No luck.
2) tried force closing TTS and samsung text to speech.. no go.
3) Uninstalling latest update to the high quality voice. .. No Go.
4) Tried holding both buttons at the Same Time... No go..
5) For quibs and giggles.. Held down the close "X" for 5 whole minutes.
********************************************
What I think is going on is a time out error in the code.
So how i am able to get around it RARELY is..
Bring it up with the microphone button
Say what I need to say then hit the X to close it as FAST AS I CAN!!
I know that with all of our phone hackers, crackers and experts that we can ALL reach a Fix on this.
Damn Google...
Click to expand...
Click to collapse
One way I found that I can close it is by opening the menu that has active apps, then going to RAM, next turn the phone on its side (<--- yes do that), then hit clear memory a few times. And done its gone.
Thanks! That worked on my Sprint S4! (restarting phone has also worked for me, but this is easier.)
After holding down Home button to open the menu that has active apps, the options were still covered by the text to speak box. So I had to FIRST turn phone on its side to make visible the pie chart icon on bottom left, THEN then going to RAM tab and hiting clear memory a few times. When I turned it back to portait orientation, the text to speak box was gone. Thanks!
This has been happening to me all day long. so frustrating. I am also not the tech savy one in the house and hubby is not around. So thanks for the quick answer to get rid of it until he can uninstall the new update. Thanks
What is the pie chart menu option? What is the RAM tab? And will just be a little easier for Google to fix this? Lol
same problem here
Galaxy S6, same problem, started last night (September 24, 2015) . I do know that some updates were performed last night, not sure what. How do I uninstall the update? Which one is it? Help! I use voice typing constantly, and my phone is a brick when this thing locks up. It covers all my buttons. "Restart" doesn't clear it, I have to totally power off and back on. Right now, I have disable my voice key on my keyboard so that I don't accidentally touch it while waiting for solution.
Me too - just started today after some updates yesterday.
Same here....has anyone responded with a fix yet??
THANKS!
Glad it's not just me and my Note 3, but where does google get off sending out this kind of crap? It's enough to drive me to a windows phone.
Having the same issue only way I can get ride of it is to turn off my phone
same issue on moto droid mini; have to turn off phone too! poor QA google!!!!!
Me too. Galaxy S4. Have to shut the phone down and restart it to resolve the issue.
Piece of crap
Note 4 same problem started on the 24th
Same issue, Note 4
Same issue, Samsung Note 4.
Yep me too Verizon Galaxy s6
Sent from my SM-G920V using Tapatalk
So i just updated to MM. Now, my fingerprint sensor/scanner(whatever you wanna call it) is acting up. There are times when it won't read my finger at all. Other times, i would have to try three or more times to get a good scan in. This usually happens when the phone has been on standby for at least 10mins. Unlocking the phone with the fingerprint sensor when you just(say 2-5mins) locked it is ok. It works as it should. Could it be a doze related bug? Is there anyone else experiencing this problem?
update: it does happen even if i just locked it. though not as often as when it had been on standby for a longer period. "/
My response got better with MM. Try a factory reset? How did you install MM?
eumanoid said:
So i just updated to MM. Now, my fingerprint sensor/scanner(whatever you wanna call it) is acting up. There are times when it won't read my finger at all. Other times, i would have to try three or more times to get a good scan in. This usually happens when the phone has been on standby for at least 10mins. Unlocking the phone with the fingerprint sensor when you just(say 2-5mins) locked it is ok. It works as it should. Could it be a doze related bug? Is there anyone else experiencing this problem?
update: it does happen even if i just locked it. though not as often as when it had been on standby for a longer period. "/
Click to expand...
Click to collapse
After scaning my fingerprint, sometimes I need to enter my password, it's not like this before I upgrade the device.
Yakkosmurf said:
My response got better with MM. Try a factory reset? How did you install MM?
Click to expand...
Click to collapse
dirty install with pcc. i'm reluctant to reset since i have 12gb worth of installation files. will it be ok if i backup-reset-restore?
iMaeGoo said:
After scaning my fingerprint, sometimes I need to enter my password, it's not like this before I upgrade the device.
Click to expand...
Click to collapse
right. at first i thought it wasn't reading my finger. but now that you mention it, it may have read my finger but asked for my key after since it didn't show an error. if it didn't read/recognize my finger, it should show an error saying so right? but it just vibrates and asks for my key. will clearing fingerprint data and re-adding them help? sure hope so.
eumanoid said:
right. at first i thought it wasn't reading my finger. but now that you mention it, it may have read my finger but asked for my key after since it didn't show an error. if it didn't read/recognize my finger, it should show an error saying so right? but it just vibrates and asks for my key. will clearing fingerprint data and re-adding them help? sure hope so.
Click to expand...
Click to collapse
If it vibrates and asks for a key, then you are probably using an app to lock the screen. On marshmallow, you have to lock the phone with the power button for the fingerprint sensor to work
eumanoid said:
right. at first i thought it wasn't reading my finger. but now that you mention it, it may have read my finger but asked for my key after since it didn't show an error. if it didn't read/recognize my finger, it should show an error saying so right? but it just vibrates and asks for my key. will clearing fingerprint data and re-adding them help? sure hope so.
Click to expand...
Click to collapse
I heard that Nexus based on MM has this problem, too.
Screen Lock Pro(Prahallad) on Play store may be useful.
---------- Post added at 10:12 AM ---------- Previous post was at 10:07 AM ----------
Sadman Khan said:
If it vibrates and asks for a key, then you are probably using an app to lock the screen. On marshmallow, you have to lock the phone with the power button for the fingerprint sensor to work
Click to expand...
Click to collapse
Thanks, when I use one-key lock, it'll always ask me for passwords.
iMaeGoo said:
I heard that Nexus based on MM has this problem, too.
Screen Lock Pro(Prahallad) on Play store may be useful.
---------- Post added at 10:12 AM ---------- Previous post was at 10:07 AM ----------
Thanks, when I use one-key lock, it'll always ask me for passwords.
Click to expand...
Click to collapse
Yep. I used to use the app "Soft Lock Screen" but now I can't anymore as I have to input pin if I use that to lock the phone hahaha
Sadman Khan said:
If it vibrates and asks for a key, then you are probably using an app to lock the screen. On marshmallow, you have to lock the phone with the power button for the fingerprint sensor to work
Click to expand...
Click to collapse
yes. i am using knock-off(double tap to turn off display) from smart launcher to lock my phone. i'll try disabling this and report back. thanks a bunch Khan.
Update: evrything is working fine now. Looks like it was a marshmallow issue as khan said. Too bad i can't use double tap to lock anymore.
My Device İs LGH850TR ( From Turkey)
*Sorry my bad english
İ found any bugs. ( *report turkey services )
1. Screen rotation sometimes not working * fix rotating open close
2. When used with Quick Cover Dial Ending Button Not Working.
3. Phone it is opened not working fingerprint sensor (and sometimes not working)
4. Phone is off plug charger cable not charging info screen. and push any button ( volme up-down, open button. ) nothing is happening screen.
5. Lg Smart World app very very very slowly. our country used 4.5 G LTE download 450mb/s but i smartworld app start theme download 1,5mb 3-4 minutes.
What do you think about this situation?
It sounds like your device is defective. I would swap it out under warranty.
I agree. That's unusual.
There's an annoying bug where the sound when you click "volume up" is coming from the speaker while headphones are connected.
Smartworld is slow!
The other things are weird...
Sent from my LG-H850 using XDA-Developers mobile app
---------- Post added at 05:48 PM ---------- Previous post was at 05:47 PM ----------
Oh screen orientation is also a known bug...
Sent from my LG-H850 using XDA-Developers mobile app
I got the same thing with the fingerprint scanner should i get a replacement? Im using h850
Get it replaced... And forget about speed in LG World. Whatever or whoever the problem is, bandwith is extremely limited to, seems like, anyone....
I'm having the strangest problem, and I've experienced this on multiple Android 10 only roms for Platina, it is relating to audio problems. It is the only thing I have trouble with on this ROM and wonder if anyone you had the same thing? I believe they are all related in some way!
Problem 1: When I use the regular dialer, and dial out, the dialing tone after calling a number comes through the speaker output and switches to normal ear piece sound the moment the call is answered
Problem 2: Using apps like WhatsApp, WeChat, LINE, and Kakaotalk, if making AUDIO only calls, I cannot hear the other person through the normal ear piece but if I switch to speaker, it works fine. The other person has no problem hearing me at all. Using Video chat works just fine and in normal fashion.
Problem 3: Whenever I am on speaker in any application, Increasing or decreasing the volume doesnt do anything
Could you tell me the location of the Audio file maybe I can look through in my file explorer and compare it to what a normal audio file should look like?
I've checked Volume, permissions, etc.. and cant figure this out. I've searched forums and everything and most people have a problem with the mic, not the speaker on their end.
Thanks for any help
Again, no problems if I use a Android 9 (custom or official), and it's just the earpiece speaker in apps other than the normal dialer. (normal dialer works like it should)
Flash this zip that I made and tell me https://mega.nz/file/xBoEAIxY#02Pp2SEnmnrS9f0kr8tJp_SNQfLMR7WEIYhIAO9pPq8
what rom Q u using?
---------- Post added at 12:07 AM ---------- Previous post was at 12:06 AM ----------
coz that old issue
soyimparable said:
Flash this zip that I made and tell me https://mega.nz/file/xBoEAIxY#02Pp2SEnmnrS9f0kr8tJp_SNQfLMR7WEIYhIAO9pPq8
Click to expand...
Click to collapse
First of all, thank you for trying to help me. Lately I've seen some questions go unnoticed. As I only have access to my dad's phone at the moment and he only has whatsapp and viber, i tried those too. Whatsapp still suffers from the same problem I noted. I never tested it on Viber prior so I can't comment, but when I created a voice to voice call, I hear it finally on my phone but it comes through the speaker but it isnt on speaker mode. If I turn on speaker mode on my phone, the volume is just much louder.
Regarding the normal dialer and dialing, I actually switched to Bliss Rom 12.7 after writing the original question and that part seemed to be already solved when I tested it.
Not sure which question of mine you sought to try to help me with?
ndrabodo said:
what rom Q u using?
---------- Post added at 12:07 AM ---------- Previous post was at 12:06 AM ----------
coz that old issue
Click to expand...
Click to collapse
Back in April when I was mainly trying to switch to Android 10, I tried almost all of them that were up in the ROMS section. I haven't tried the xiaomi official one yet but I did try xiaomi eu miui 12 with android 10 and that also has this problem.
Currently running Blissrom 12.7 that was released just a few days ago
It just doesnt make sense how I see no one else having this problem, yet my ear piece is working fine for normal operation and/or when I am running Android 9 on the phone.
I've tried playing around with OK GOOGLE, GOOGLE ASSISTANT, I dont use either now those so they were already off or didnt exist in my settings, but since installed and tried all kinds of variations.