Allow Mock locations. And annoying "hold" on calls every time phone put up to my ear.
I have a galaxy s6.
SM-G920I to be exact
Running marshmellow
I have enabled developer options
I can not find the option allow mock locations at all.
It used to be there before the update.
I have tried resetting the device.
It seems the option has completely vanished.
Is there any way to bring the option back?
The only mock location option is the option to select a single app.
So have they done away with the option. And just included the option to select a single app?
Ps I'm sure the mock location option was there on my old s6.( Identical model and carrier also software version was also Marshmellow same build)
Also
Is there any way to reduce the touch sensitivity on this device. I know there is on the s5.
Every time I call and put the phone upto my ear it places the call on hold. Very embarrassing.
I'm deaf in my left ear so I need to use my right ear..
But every time I do. My ear touches the hold button.
I've tried searching for an app that replaces the in call screen. I've tried apps that "reduce sensitivity" there must be something I can do? Even move the hold button?
I don't want to root my phone as its only a month old.
I'd only root if I can guarantee the Knox counter won't trip.
I'm aware the hold issue is very common however have not been able to find a resolution.
Any help would be appreciated.
I have searched Google for answers but can't find anything.
Thanks
Proximity sensor isn't being triggered correctly, not an uncommon problem. Most blame it on how the phone is held.
As a workaround, hit the power button before putting the phone up to your ear, to lock the screen.
Sent from my SM-G920W8 using Tapatalk
Related
Hi
I hope someone can help point me in the right direction
I have been looking for a fake call app that when run fakes a call immediately
all of the apps seem to need some sort of user interaction to setup a call
i have a watch that when a button is pressed i can run an app on the phone
but even with tasker or locale i cant turn on the screen or input the security code so i need to fake a call so it will display when the phone is sleeping.
a fake call app will do this but i cant get one that i can run without having to select options first
the closest is the shake to fake but i really dont want to get my phone out and shake it when i can just press a discrete button.
i have seen apps with an immediate widget but i cant see how to get tasker to run a widget
does anyone know of one ?
Thanks
HTC Sensation: Possible solution of "phone doesn't sleep" and "power button" problem
Hi every body,
I was getting irritated and extremely fed up of basically two problems of my htc sensation:
1- The phone didn't automatically turn the screen off. The screen would remain ON and wouldn't automatically lock itself. For example, i use the phone and then i will place it at a side expecting that first screen will be dimmed and then phone will automatically lock itself. It wasn't happening since a very long time (I don't remember the beginning of problem), even when screen timeout setting was enabled. I also observed that if at one time i set the brightness level of display to be automatic, next time i check it and brightness level was always set to be at maximum level.
2- When i pressed the power button to lock the phone, the phone often doesn't go dark. It went dark for a second and then became ON again. I had to press it a number of times until it goes dark. Similarly when i wanted to unlock the phone, i had to press the power button multiple number of times, until it gets unlocked.
Basically i was trying to solve the 1st problem. I went into settings -> applications -> manage application. I checked for each installed application whether it has following in the permissions:
System tools: prevent phone from sleeping
Following applications had above mentioned permission, so i removed them:
xda
ebay
mobile voip
daily motion
sports tracker
Calorie Counter - MyFitnessPal
imdb
Photo Editor
speedtest.net
whatsapp
yahoo messenger
Surprisingly after removing those apps, both issues 1 & 2 were totally gone. The phone was automatically locking it self (it still is). So for me problem number 1 is totally gone now.
However, regarding second problem, i tested it like 100 times locking and unlocking the screen by pressing power button. The behavior was absolutely normal. Then i checked the brightness level of phone, it was set to maximum, i set it to automatic. As soon as i set the brightness level to be automatic, the 2nd problem somehow reappeared.
Now if i set the brightness level manually, the 2nd issue doesnt reappear, but when i set the brightness level to be automatic, power button issues reappears.
Sorry for such a long post but I hope may be this post helps someone, also i would like to ask the experts the justification of such behavior of phone.
I am using stock rom and android version 2.3.4, sense version 3.0 and software number 1.50.206.1
This definitely needs a bump!
I was thinking of possible solutions as well, but this one makes sense. Maybe it is a flaw in how that permission is handled? I don't know how to program, but if any of you clever rom hackers are around, maybe you can try tweaking this? I was thinking that it was maybe something to do with the hardware button itself, sending off multiple signals to the phone telling it to lock and unlock right after due to the shoddy power button design.
My main issue with the fix in the original post is that I use a lot of apps that require this permission, and apps are kinda what define how useful your phone is (aside from making phone calls, that is). If there was a way to fix this issue by either tweaking the "prevent phone from sleeping" permission, or maybe just trying to add an input delay that doesn't register any power button presses until half a second has passed or something.
Like I said, I don't know what is possible to tweak with android since I don't know how to program so I might just be talking out of my butt, however, I do like this phone, it just has this one major power button flaw that really annoys me!
#2 doesn't occur in ICS Roms. I'm always on auto brightness.
Some ROMS added some apps may let your phone awake automatically when you close the screen,so it is the right way to move some apps. Using ARHD ICS and Insection ICS ROMS ,#1#2problems never happend.
Basically i would like to stick to original stock rom. I know i can avoid these problems if i use custom roms.
@Tekuno
Let me tell you, i didn't delete all of those apps which were using that permission "prevent system from sleeping". I only deleted those which i mentioned in my 1st post. Among those, i installed "yahoo messenger" again and 1st problem started happening again. I removed that app, problem gone. For me it's the case of hit and trial. I can't definitely point out one specific app which cause the problems.
I think there is really a flaw in the way this permission is handled by operating system of the phone.
I would also like to keep with the stock rom if possible. I figured it would only be a few apps that would be causing the lock screen issues, I am currently too lazy to go through all of the apps and figure out which ones are causing it.
I'll wait patiently for the ICS and Sense 3.6 update and see if that helps.
i have both problems too. About no 2, i always tot it happens after using the stock camera app which forces the brightness to go maximum and sometimes after exiting, there is some bug that doesnt return setting to automatic. Just a hunch but not sure :s
Do you have "Extended quick settings" installed ? and on a custom ROM, if so then i guess you need to check the "Screen On" option in the extended quick settings dropdown window.
You must have accidentally pressed it and activated it instead.
I have a Samsung Galaxy S2. It recently was warrantied with an identical unit -- the previous one was rooted and ROMed; this one is stock ICS.
Like most android phones, when any form of screen lock is enabled, my phone presents an "Emergency Call" option there on the lock screen. I realize this is present by law, bla bla bla..... I also have read through around 2-dozen threads on the subject... This is apparently a hot topic, please excuse this addition to the discussion.
While I have never butt-dialed 911, I have a very tenacious toddler who had developed the super power of finding my hidden phone (regardless of where it is), who then proceeds to fiddle with it until 911 is called. This has now happened on several occasions. I am unable to find any way to disable the call 911 feature when the phone is locked. Reading today, it was suggested that ~20% of all 911 calls in US and Canada are accidentally dialed from the "Emergency Call" button from the locked screen.
It would seem my only options are to leave my phone unlocked, allowing my kids to screw everything up, or lock the phone, allowing my toddler to place emergency calls.
Today a third option occurred to me. If there was an app that provided a Second Lock Screen, I could leave my phone 'unlocked', never revealing the dreaded Emergency Call button. The phone could be configured to have NO LOCK, or just SWIPE, but then the second lock screen would pop up, offering the standard security options, but with no possibility of placing an emergency call. I would hope for an option that required either no extra actions/swipes, or only one to access the locked phone.
This would be different from the plethora of app locks that are readily available -- I do NOT want to have to unlock individual apps.
Is anyone familiar with an app that would provide this functionality, or of another work-around that would allow me to secure my phone without the 911 hassles? If I need to place an emergency call, I would simply dial it manually, and if there is no SIM card, the emergency call functions remain present, which sounds like a good idea to me.
As a final thought, I do not remember having this problem with my previously ROMed phone. I can't recollect if it had the same emergency call options from the locked screen.
Thank you!
-Steve
AT&T LG G3, love the phone. I'm down for the lollipop update, but I can't seem to remedy one new Lollipop problem.
At various times, i haven't figured out exactly what causes it, but when i drag down my notification bar, during just normal use of my phone, I can see various notifications from applications, but NO DETAILS, only a line saying "Unlock to see sensitive". Of course my phone is unlocked as I AM USING IT!! I tried going into settings/sound/notifications/turning SHOW ALL NOTIFICATIONS on, and then you can go into apps individually to set notification preferences, but nowhere does it say anything about setting sensitivity for individual apps. This seems to be a bug. I've dug through all the possible settings.
One example that has happened to me many times is i'll be on the phone talking, i hear a notification tone, put on speaker phone and drag down my notifications to see what it is, and i only see the app icon, with "Unlock to see sensitive". Then if i press the notification it brings up the application no problem, but that is a pain and i didnt want to open the app, just see the notification. This is sure frustrating.
Any help greatly appreciated.
???????
I am also having random occurrences where all of my drop-downs say unlock to see sensitive. Locking and then unlocking the phone fixes it I have no idea what causes it
I am having the same issue haven't figured out the cause or a fix
I just started having the same issue. I went to Display >>> Lock Screen and noticed that my setting had been set to Swipe to Unlock, even though I've always had it set to None. I switched it back to None and now I can see the notifications again.
This randomly happens to me too. Checking the power button automatically locks screen option is a bandaid solution for me
I'm noticing that during many of my calls, I apparently hit the HOLD button accidentally with my cheek. My proximity sensor seems to be working fine, and the screen does turn off appropriately when I hold the phone against my face. I'm assuming that at certain angles enough light gets through to the sensor to turn the screen on, and I accidentally hit the button in the corner. Anyone else have this issue? Is there any way to circumvent this? Thanks
Unfortunately i can't help but i am getting the same issue
Sent from my SM-G930F using Tapatalk
I tried applying different dialer apps and they only serve to change the dialer/contact screens, but the default calling screen containing the HOLD button remains unchanged. I found that using Skype as the default dialer fixes this issue since it uses its own dialing/calling screens, but obviously it's not practical to just rely on Skype. So the problem still remains unresolved.
As an update, someone on Reddit posted a download link to the Google dialer app here at: http://forum.xda-developers.com/galaxy-s6/themes-apps/app-google-dialer-t3323432
This installs a new dialer, which actually provides a new calling screen as well, fixing the main issue. The default dialer is better in my opinion since it opens up the dial pad immediately while this one doesn't, but this is a good option at this point
gomulkaaa said:
I'm noticing that during many of my calls, I apparently hit the HOLD button accidentally with my cheek. My proximity sensor seems to be working fine, and the screen does turn off appropriately when I hold the phone against my face. I'm assuming that at certain angles enough light gets through to the sensor to turn the screen on, and I accidentally hit the button in the corner. Anyone else have this issue? Is there any way to circumvent this? Thanks
Click to expand...
Click to collapse
even worst than calls is when you press it while watching youtube vids, i wish there was a lock of some sort cuz the music stops paying all the sudden
It's embarrassing when I put my clients on hold and don't realise until they don't respond to me. The cheek hold doesn't result in any audible sound so you can be talking for 20 seconds with the other end on hold. I love the S7 edge but I'm contemplating sending it back. I'll try the Google dialer mentioned above first though
Same issue here. I talk on the phone almost 2 hours a day and this is happening at least 1-2 times in every call! Checked my proximity sensor and it's working as it should.
Any workarounds? Maybe someone can edit the phone.apk and remove this stupid button or disable it? I am against rooting but I will definitely root my phone if there's a fix for this.
Damn, I suffer exactly the same issue! Found this googling for ideas...
Very old thread, but I just wanted to give a suggestion to others with the same issue. I really love the Google Phone dialer app, which actually replaces the calling screen during calls with this app's own screen, so you no longer have the Hold button at such an unfortunate location. If you do choose Google's app, I recommend this specific version: http://www.apkmirror.com/apk/google-inc/google-phone/google-phone-2-05-07_rc4-release/google-phone-2-05-07_rc4-android-apk-download/
The caller-ID function by Google actually works with this version, whereas the other .apk files floating around do not have this function working properly.
I'm having the same issue and I've installed the Google phone, however as soon as I place the call, the existing on-screen options pop up.
The option to disable the default phone app is greyed out in settings, so unsure on how to resolve.
robot1000 said:
I'm having the same issue and I've installed the Google phone, however as soon as I place the call, the existing on-screen options pop up.
The option to disable the default phone app is greyed out in settings, so unsure on how to resolve.
Click to expand...
Click to collapse
Finally searched for the answer to this today, after several accidental holds on work calls.
The solution above with Google Phone APK worked for me. I just went to SETTINGS - APPLICATIONS - DEFAULT APPLICATIONS and then under Calling App near the top, changed it from Contacts to Phone. . For some reason, I cannot open the phone app itself (gives an error message) but calls do use the phone app rather than Samsung stock dialer.
Turn off screen!! Most phones allow you to turn screen off without interrupting the call.
Same issue with a galaxy A5 2016
Can't understand why samsung doesn't fix it