60% of the time, my speakerphone turns itself on when I make a phone call. Is there some option for this?
I have noticed this happens to me sometimes, very rarely... would like to know why
Still no ideas?
3L3C7R0 said:
Still no ideas?
Click to expand...
Click to collapse
Only thing I could come up with is because it wants to . Not much help lol
Sent from my HTC6600LVW using XDA Premium 4 mobile app
I also have this problem and think it could be to do with the proximity sensor, the speaker button touches your face before the screen turns off. I have been careful to hover the phone next to my ear for a second or two before placing it on my ear to make sure the screen turns off and haven't had a problem since. Try that it may help
Sent from my HTC One max using XDA Premium 4 mobile app
samo_nz said:
I also have this problem and think it could be to do with the proximity sensor, the speaker button touches your face before the screen turns off. I have been careful to hover the phone next to my ear for a second or two before placing it on my ear to make sure the screen turns off and haven't had a problem since. Try that it may help
Sent from my HTC One max using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Mine comes on before putting the phone up to my ear.
Chrome is to blame!
It's observed that the latest Chrome caused this strange issue. As long as you disable Chrome (or uninstall the latest update) the problem seems gone. I do also noticed that during phone call with BT headset, if I open Chrome the phone will also enable Speaker phone immediately.
Please test if this is the case for you. Several people in a Taiwanese forum confirmed this issue.
lssong99 said:
It's observed that the latest Chrome caused this strange issue. As long as you disable Chrome (or uninstall the latest update) the problem seems gone. I do also noticed that during phone call with BT headset, if I open Chrome the phone will also enable Speaker phone immediately.
Please test if this is the case for you. Several people in a Taiwanese forum confirmed this issue.
Click to expand...
Click to collapse
Why is a browser able to control my phone?
3L3C7R0 said:
Why is a browser able to control my phone?
Click to expand...
Click to collapse
Don't ask me, ask Google! I merely tell what I observed.
lssong99 said:
Don't ask me, ask Google! I merely tell what I observed.
Click to expand...
Click to collapse
I can't turn off that ability either in the hidden App Ops.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3L3C7R0 said:
I can't turn off that ability either in the hidden App Ops.
Click to expand...
Click to collapse
I am not sure if it's permission related (it should be...) and App OPS is kind of weak in this. Thus I suggest just try to uninstall or disable Chrome then check if this still happens. (you can disable Chrome via Titanium backup if the "disable" function is disabled in Setup-->Application)
Related
So a few weeks ago, my phone decided to go for a swim.
I managed to dry it out, and it works as well as it ever has, but for one casualty.
My proximity sensor is shot. It reads 0 all the time, that mean when I'm in a call, it instantly turns off the screen, leaving me un able to use the keypad, or to even end the call.
I came across this in my searches,
http://forum.xda-developers.com/showthread.php?t=1626611
Saying that there is a line I can amend to the end of my build.prop that looks like such:
gsm.proximity.enable=false
Click to expand...
Click to collapse
Now the original thread was for The HTC Desire S for AT&T, and seeing how it references GSM, I assume it's not just a Ctrl-c, Ctrl-v kind of job.
So what would be the correct conjugation of this line for the photon?
I'm getting closer
http://forum.xda-developers.com/showthread.php?t=1784195
dedraks said:
You can edit the file /system/build.prop
Search the line: mot.proximity.delay= VALUE
Change the value to an higher value.
Click to expand...
Click to collapse
Edit:
Looks like I should've herped but instead I derped.
Since I'm running CM7, all I had to do is look here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now when it means longer than nomal then it will still time out right?
Surely there's a way to have it be set for an indefinate amount.
Even with the option checked to set the power button to end the call, I still can't end calls with the power button.
Any thoughts will be really helpful, kinda takes away from the whole phone thing, if it's a pain in the ass to make a call, I'm tied having to make a battery pull just to hang up.
So above has not helped.
I have heard about an app called screebl that is supposed to lock the screeen on on boot, but that hasn't helped either.
Still having trouble with this, which is annoying as hell since I have to often dial exertions for work, but I can't since I can't pull up the key pad after placing a call
This time I'm really not trying to bump the thread up, I promise.
So using elixir, I can show you that both the proximity sensor and light sensor are both completely unresponsive, I took this screen shot with a flashlight directly in the light/proximity sensor area.
With the proximity sensor constantly reading 3cm, my phone believes it is up to my face constantly.
I'm at my wits end, the option in accessibility to have the power button end the call isn't working either. So calls on my /phone/ are seven times the hassle than it needs to be.
Sent from my MB855 using xda app-developers app
The only way I have kept this from tearing my hair out is flashing Peetr's Hybrid v20, instead of Cybik's CM7.2
Now at least the power button actually ends the call again.
This isn't a fix though, it's a stop-gap. I'm trying to keep as detailed records as I can so if google throws some unfortunate soul here, there will be someone who at least tried to walk this path. Wish someone would say something, even if it was "Stop bumping this thread"
I FIXED IT.
In peetr's hybrids build.prop there's a line
ro.mot.proximity.touch=1
Click to expand...
Click to collapse
Setting that to 0 disabled the proximity sensor.
Hopefully no one else has to go through the headaches that I have done. But there it is.
Sent from my MB855 using xda app-developers app
Hi XDA PPL,
So my S3 I9300 has this notification LED issue,
it is a dull BLUE color
The notification LED stays ON forever,
I Data Reset it, no change,
Its never Rooted, Updated to latest firmware.
The weirdest thing is that it Stays ON even after the phones turned off,
Please check the Video for Reference.
I have even checked the Samsung Service MENU All Colors are working.
U can also check the pics for details.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I cant get it replaced in warranty so looking for other solutions.
Flash firmware with odin and see if that cleans up the problem mate.
I9100/I9300
Did you try to deactivate the LED? Good luck with it
Sent from my GT-I9300 using XDA Premium 4 mobile app
Nyrus said:
Did you try to deactivate the LED? Good luck with it
Sent from my GT-I9300 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
How do u do that??
If u r talking about Changing LED indicator Setting in DISPLAY SETTINGS,
i have done it
saz542 said:
How do u do that??
If u r talking about Changing LED indicator Setting in DISPLAY SETTINGS,
i have done it
Click to expand...
Click to collapse
Yes, I was thinking on it.. Do you have Yahoo Mail app installed? Or have you installed any apps to control your LED? Lightflow perhaps?
Nyrus said:
Yes, I was thinking on it.. Do you have Yahoo Mail app installed? Or have you installed any apps to control your LED? Lightflow perhaps?
Click to expand...
Click to collapse
I request You to please check the Video , I have mentioned everything in Detail.
P.S. Its not Rooted , So LightFlow wont Work.
And My phone is Factory Data Reset So no third Party Apps.
had given to Official Samsung Service Center ,
They changed the Hardware LED Sensor but no success.
the phone still had the issue.
They Updated to latest update.
Nothing Changed....
blue led
saz542 said:
had given to Official Samsung Service Center ,
They changed the Hardware LED Sensor but no success.
the phone still had the issue.
They Updated to latest update.
Nothing Changed....
Click to expand...
Click to collapse
the same issue, except that my blue led notification was off and act normal when phone on, but remain lite when phone off, just disappear by itself.
What i done with no success.
1. reset, erase, going back to stock, wipe completely etc, flash with odin, flash with kies, the issue remain
2.changed batt, changed charger, changed usb cable, issue remain.
3. goes to warranty, the same hardware changed, the issue remain.
4. "damaged" on purpose the efs folder, with imei 0049 the issue remain.
i just give up, and thinking seriously to disable the led with a hammer for good. The issue disappear.The only thing that updated in this period was something about Samsung account.
Hope that you will treat your phone with a hammer will resolve for you the blue led issue (just kidding)
I have heard that Nexus 9 comes with Always listening mode, but I can't seem to get it working.
siddardhab said:
I have heard that Nexus 9 comes with Always listening mode, but I can't seem to get it working.
Click to expand...
Click to collapse
Mine works... App Drawer / Google Settings (not settings) / Search & Now / Voice / "OK Google" Detection / check all 3 tabs.. How did u not find this?? haha
All three options are checked, but hotword detection only works when I press the power button, not when the screen is off.
siddardhab said:
I have heard that Nexus 9 comes with Always listening mode, but I can't seem to get it working.
Click to expand...
Click to collapse
Is your device rooted?
When I update and rooted my Nexus 9 for the first time, somehow, it kept the old kernel, not the "Q" one. And had some issues like lag, adaptive brightness and inability to use "listening mode".
I installed and rooted again and everything was solved, including the listening mode.
Drifus Dreskeke said:
Is your device rooted?
When I update and rooted my Nexus 9 for the first time, somehow, it kept the old kernel, not the "Q" one. And had some issues like lag, adaptive brightness and inability to use "listening mode".
I installed and rooted again and everything was solved, including the listening mode.
Click to expand...
Click to collapse
Nope, never rooted. I didn't even unlock the bootloader. Here is the about device screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Are you using English as primary language?
An app conflicting with Google voice?
Check everything again. Maybe you are missing something.
I'm running out of ideas. Sorry.
Drifus Dreskeke said:
Are you using English as primary language?
An app conflicting with Google voice?
Check everything again. Maybe you are missing something.
I'm running out of ideas. Sorry.
Click to expand...
Click to collapse
I tried a factory reset and it seems to be working now although it's a little inconsistent. It stops detecting when the tablet is not used for some time but a reboot fixes that.
Glad it worked.
Drifus Dreskeke said:
Glad it worked.
Click to expand...
Click to collapse
My first Nexus 9 didnt work, but my second one which immediately updated to the newest version did work.
Inconsisten behavior here too. Sometimes it works, sometimes it doesn't. After a reboot everything seems to work just fine, but then it starts to fail here and there. Not smooth, anyway.
Inconsistent behavior with screen off. I'm on the latest R release (fresh factory image install).
mine did today, in a carry bag, while is was using the n7 while driving. this is why I want a customizable hot word I can set per device. how hard can that be.
Sent from my Nexus 9 using Tapatalk
Any new suggestions on this?
I am on 5.0.1 and "OK Google" works from locked some time after a reboot, but then it stops working and is only working when on a home screen and screen on.
Does this work properly and consistantly all the time for anyone?
There are two main things that are killing me atm...
1. If I send an email to myself on the gmail app I'll get duplicates instead of one... WHY IS THAT!?! i tried everything I can think of to stop it...
2. My phone all of a sudden started doing a audible notification when I do or don't have a network signal and it's driving me nuts... I looked everywhere in setting. I seem to remember a settings where you can shut off the notification sound off. As of now I have "notification sounds" off.
For reference I'm on 5.1.1 thanks for your help in advanced.
vipfreak said:
There are two main things that are killing me atm...
1. If I send an email to myself on the gmail app I'll get duplicates instead of one... WHY IS THAT!?! i tried everything I can think of to stop it...
2. My phone all of a sudden started doing a audible notification when I do or don't have a network signal and it's driving me nuts... I looked everywhere in setting. I seem to remember a settings where you can shut off the notification sound off. As of now I have "notification sounds" off.
For reference I'm on 5.1.1 thanks for your help in advanced.
Click to expand...
Click to collapse
Can you provide screenshots it'd help me out.
Are you on stock?
Yes, stock. Not rooted.
I can take screen shots, but don't know how it will help. 2 has been sorta resolved since I left the sound off. I could've swarn i remember a setting before to toggle if you wanted an audible warning if you did or didn't have a mobile connection. The emails do it still but is more random than consistent. It will do it on wifi and mobile data. I think it has to do with sync though.
vipfreak said:
Yes, stock. Not rooted.
I can take screen shots, but don't know how it will help. 2 has been sorta resolved since I left the sound off. I could've swarn i remember a setting before to toggle if you wanted an audible warning if you did or didn't have a mobile connection. The emails do it still but is more random than consistent. It will do it on wifi and mobile data. I think it has to do with sync though.
Click to expand...
Click to collapse
Well see if its the syncing. With a screenshot I can pinpoint the issue out right away.
That notification sound is an OS issue, while the duplicate mail issue is a Gmail issue, so I would try to maybe:
1. Clear Gmail data from Settings-> Gmail -> Clear data
2. Force a re-sync from Settings-> Accounts -> Google
3. Send yourself an email on the desktop site and see if it still happens. If it does it's a google service issue and not an app issue.
I found a fix. I'm getting a LG V10. Lol... Thanks for the help though anyways.
vipfreak said:
I found a fix. I'm getting a LG V10. Lol... Thanks for the help though anyways.
Click to expand...
Click to collapse
Sure, why not!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi,
I got this watch used, arrived two days ago. I like it so far. Only tweaks done so far is unlock BL.
I want to preserve the battery life as much as possible though, while keeping it usable. So I think there is efficiency to be made by having the watch face stay as a silhouette instead of "waking up" whenever I look at it. To activate the watch, I have no problem with tapping it once or twice.
Does such a tweak exist? I could not find it in settings (only to turn screen off completely when inactive). Any prerequisites for such a tweak (e.g. root)?
Many thanks.
Are you on 5.1.1 (LCA43)? If yes, you can try disabling wrist gestures in watch settings. Of course, you won't be able to move trough cards as well if you disable it, but it will prevent the screen to leave dim mode when you move your wrist.
Sent from my LG-D410 using XDA Free mobile app
lfom said:
Are you on 5.1.1 (LCA43)? If yes, you can try disabling wrist gestures in watch settings. Of course, you won't be able to move trough cards as well if you disable it, but it will prevent the screen to leave dim mode when you move your wrist.
Sent from my LG-D410 using XDA Free mobile app
Click to expand...
Click to collapse
I tried that before (am on LCA43), but it seems to just disable the scroll. Just tried again, may have made a difference this time. Though it looks like the screen still activates 1 out of the 5 times I put the watch to my face. We shall see. Thanks!
You're correct, my bad! The setting you want is in the Android Wear app: Tilt to wake screen. You may want to keep wrist gestures on.
Sent from my LG-D410 using XDA Free mobile app
lfom said:
You're correct, my bad! The setting you want is in the Android Wear app: Tilt to wake screen. You may want to keep wrist gestures on.
Sent from my LG-D410 using XDA Free mobile app
Click to expand...
Click to collapse
Found it! The guide I found had the setting on the main page. I had to tap on the actual device listing to get to the sub page with all the goodies (Google probably did it that way so you can program different actions for different watches).
Thanks again!
By the way, one day later with no charge in between. I am proud of this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Set for two solid days of use. [emoji3]