I'm trying to tackle my problem from another angle. So, does anyone know how to disable the touch screen on a Galaxy S2?
I'm trying to have the screen off while an app runs (and thinks the screen is on). I can turn the screen off by this command:
echo 1 > /sys/devices/platform/samsung-pd.2/s3cfb.0/graphics/fb0/blank
Screen will be off, but it still responds to touch. I figure there's probably a similar command to disable the touchscreen. I found a thread that describes how to do it for the nook; however it won't work on this phone (obviously because the hardware's different).
I've seen apps that may disable the touchscreen...however I won't have access to the notification bar while in the app I want to run (frustrating). I plan on creating a script that'll sleep for 2-3 minutes, giving me enough time to get to the app and set it up just the way I want, then the screen will go out. To get the screen back on, I'll either wait until I can ssh in and undo what I did (in the example above, just substitute echo 0 instead of echo 1) or do a hard reboot.
Edit: This may be OS dependent...I'm running ICS 4.0.3 at the moment.
Use below:
# To Disable touchscreen
service call window 18 i32 0
# To Enable touchscreen
service call window 18 i32 1
I use this in my Gesture script thanks to Tungstwenty.
Sent from my GT-I9100 using Tapatalk 2
acekay said:
# To Disable touchscreen
service call window 18 i32 0
# To Enable touchscreen
service call window 18 i32 1
Click to expand...
Click to collapse
Looks like it'll be good enough for my purposes.
I've now realized it might be ever so slightly helpful if I could disable the home and power buttons as well (but not all the buttons, might need volume). I think if I keep it in a pocket or make a little space for it where it won't get disturbed too much, it'll be ok.
Just a note, this doesn't completely turn off the touchscreen. The phone still reacts to touching the screen (specifically, the menu and back buttons light up). And touching the menu or back button will also cause them to light up and make the phone vibrate, though the button is ignored otherwise (i.e. you're in the app, press the back button...it lights up and vibrates the phone, but it does NOT exit the app).
I'll test it in a couple weeks (once the headset and amplifier come in), but I think it'll fit the bill.
Thanks!
Hi,
It did not work in my case (android 6).
Any other way ?
Ranchu
Related
Phone works and everything but the touch screen is not responsive.
Does anyone know how to call up the "Start" menu just using the keyboard?
or
How to press "Send" using just the keyboard for SMS msg?
Thanks in advance!
I'm not sure that it is possible. this has happened twice to me* (see below) and those were the only 2 things that I could not do. you can go to the program tab to the far right and start any programs you may still be able to use...
*I've had this happen to 2 of my touch pros...What I was told by a rep was there is a small plastic tab on the back of your screen. If you look on your phone where the volume buttons are...opposite side. That small plastic tab should be removed because this rubs against some connector inside the phone that causes the touch screen to die. soooo long story short you'll need to take it in and get it replaced
Sort of the same issue:
I've got a stock ROM, PhoneAlarm (latest beta) and a few other applications installed on this device, only recently has it caused me as much of a hassle as it has. I get a phone call and no matter if I press the softkey "Answer" button or the answer button on the bottom left below the jogdial, NOTHING picks up a call. Sometimes if I stab at it wildly enough it answers and immediately places a call within a call which means I can't get back to the original one i answered. It's frustrating and really annoying.
@sanjsrik - I'm having the same issue.
Using a Sprint issued TouchPro. Along with the 'Answer' issues, I'm also having problems with the screen jogging around. When I go into applications or the phone keypad, the screen is skewed, however if I touch the screen (in the correct spot), the correct command happens. For example, if my keypad screen is skewed (which only happens sporadically), it shows the '7' where the '9' should be and if I touch the screen there, the '9' correctly apprears. I plan to take the phone to Sprint either tomorrow or next and hopefully will have a clearer verdict.
Stock ROM
Apps:
Adv Config Tool
Google Maps
Facebook
Skype
TinyTwitter
I am a new android owner. When I make a phone call the proximity sensor turns the screen off... great, no accidental screen pressing. However, when I finish the phone call or take the phone away from my ear... I get the lock screen. Why? Why doesn't the screen just go back on to whatever screen was on before the phone call... like the dial pad.
I find this annoying. To hang up a phone call, I have to unlock the screen first.
What phone are you using? Software version etc and are you rooted? This doesn't happen to me so it's not a general android issue.
Sent from my Galaxy Nexus
I have the Moto Droid X. Running CyanogenMod 7.1. Also using exDialer as a dialer replacement.
Does it happen with the stock dialer? If not that's your answer
Sent from my Galaxy Nexus
RTContent said:
Does it happen with the stock dialer? If not that's your answer
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Yep it happened with the stock dialer on ICS and it is happening with JB as well. I am really surprised it doesn't bother more people. What is most annoying is that, I initiated a new call and put my phone to my ear to only that the call did not even establish (e.g., due to network iss ue) and when I want to place the call again, it is already locked. It is definitely due to the proximity sensor, as the same thing doesn't happen if i never put the phone to my ear and just keep watching the screen to confirm that the call did get established (and started ringing).
njmsmith said:
I am a new android owner. When I make a phone call the proximity sensor turns the screen off... great, no accidental screen pressing. However, when I finish the phone call or take the phone away from my ear... I get the lock screen. Why? Why doesn't the screen just go back on to whatever screen was on before the phone call... like the dial pad.
I find this annoying. To hang up a phone call, I have to unlock the screen first.
Click to expand...
Click to collapse
If you are rooted, disable your Proximity Sensor in a call. To do so, add following line to /system/build.prop file:
Code:
gsm.proximity.enable=false
.
Plus, make sure to make screen timeout period long. You can use Widgetsoid app (or, other toggle apps) to make it infinite.
SachinShekhar said:
If you are rooted, disable your Proximity Sensor in a call. To do so, add following line to /system/build.prop file:
Code:
gsm.proximity.enable=false
.
Plus, make sure to make screen timeout period long. You can use Widgetsoid app (or, other toggle apps) to make it infinite.
Click to expand...
Click to collapse
I have display timeout set to 2 minutes, so that can't be the problem, as the whole experience when the call is not connected only takes 10 or 15 seconds to complete. However I have security setting to lock the screen in 5 seconds after the display goes to sleep. Perhaps that is somehow related, so I just increased it to 30 seconds, I will see if the problem goes away.
This phone has never been modified, no custom ROMS, never rooted, using the latest OS from AT&T ...
And today, for whatever reason, when making originating a phone call, and once I've hit "dial" ... the phone screen goes completely black except for the status bar at the top (the one you can swipe down). I'm saying that whereas usually, after hitting "dial" and as the phone dials, you can actually see a screen full of information (hang up botton, number/name of who your dialing, etc.) ... in this case and now, there is just a black screen.
Though there is a black screen (other than the status bar at top), I can still hear the phone ring and even have a conversation should somebody answer. But when the call is over (the person on the other end has to end the connection because I have no screen interface to do such), the screen remains blank (other than the status bar at top) and none of the bottom, permanent keys are operative either ("home" / "back" / settings / etc.). To get back to the home screen, I have to pop the battery and re insert it and re start the phone. But even then, it's acting weird: when booting, at the "Reimagine Possilbe" screen (I think that's what it says) it hangs there for about 45 seconds (usually only about 5 when functioning correctly) and will eventually end up at the home screen.
But if I originate a call, the cycle repeats.
I've completely reset the phone to factory defaults at least three times, formatted the USB storage and the whole nine yards but it remains glitched as described above.
...
So... has anyone seen/heard of this?
I'm thinking of just warrantying the phone as it's only about 5 months and I figure AT&T should have no issue as it's such a replicable problem and it certainly doesn't seem to be software related as it's completely stock and multiple factory resets have not worked but wanted to put a line out here first to see if anyone else has experienced this.
Thanks in advance for any information.
Best,
Joel.
I think the network is fugazi right now, as I had issues with the phone, and read about another user having same troubles. I'd give it a little time.
rangercaptain said:
I think the network is fugazi right now, as I had issues with the phone, and read about another user having same troubles. I'd give it a little time.
Click to expand...
Click to collapse
I sure hope so. Even though I've reset the phone (which sucks) ... I'd prefer that over having to go to the store and all...
Odd that a network problem could cause such, though ....
Thanks for the word ...
Best.
.joel
Just a llittle update ...
I changed the "Proximity Sensor" to OFF and now the normal iin-call screen appears but it never goes away, which can be problematic.
In general, I've always had the proximity sensor set to ON as this allows the in-call screen to blank after a few seconds (complete blank with no status bar at top) and then reappear when I remove the phone from my ear.
But when I re enable the proximity sensor, now ... the screen blanks immediately (excepting the status bar at the top) and never comes back ... even after my call recipient ends the call ...
I'm just gonna warranty at at the local service center; at this point (two days now with all my friends AT&T phones working fine) I'm pretty sure something is glitched with the internal sensor that manages the proximity settings ...
Thank God for warranty.
Hey. Thanks for reading!
I got an s4 recently and have not had any problems with it till now. I had to call a company today, and I thought the problem I had would not reappear. I'm posting here so...
On two calls lately I'v needed to input numbers during the call to give information. When I try to enter the numbers the screen turns off until I move it a little, then it turns on... until it detects my finger about to touch it, then it turns off again. The call continues through all of this. I could barely input the ten or so digit number I needed to provide. This only occurs during calls. Even when dialing my Voicemail I have a struggle to put in the 4 digit pin because the screen acts like a grinch, turning off when I try to press numbers. I turned off all the s4's "eye-monitoring" features and it still does this. Any ideas?
Thanks!
open your dialer
press the menu button
select call settings
uncheck "Autoscreen off during calls"
voila
seagypsy59 said:
open your dialer
press the menu button
select call settings
uncheck "Autoscreen off during calls"
voila
Click to expand...
Click to collapse
This will work.. but then it'll produce another problem when your cheek starts to press buttons.. ending in a txt msg to your mom whereas the msg was created with speech to text... while you were talking to your g/f.
Found the option. I may just have to turn it on and off as needed.
Now to find the on screen keyboard sensitivity! Thanks!
I have s similar issue where my screen turns off when I start a call and doesn't come back on wheni pull they phone away from my face. It only comes back on wheni puts power button or home button, but then the screen doesn't turn back off when I put it close to my face again. Turning off auto off feature does what is supposed to but then what's the point of the auto off anyway. Still searching for answers for the last 2 weeks.
There should really be a way of adjusting the sensitivity of this. My wife's S4 just recently started doing this, and my guess is that it's picking up the palm of her hand as her cheek and preventing her from being able to actually press any buttons on the numpad while on a call.
nightspeed98 said:
I have s similar issue where my screen turns off when I start a call and doesn't come back on wheni pull they phone away from my face. It only comes back on wheni puts power button or home button, but then the screen doesn't turn back off when I put it close to my face again. Turning off auto off feature does what is supposed to but then what's the point of the auto off anyway. Still searching for answers for the last 2 weeks.
Click to expand...
Click to collapse
This is exactly what is happening to my two week old gs4. I make a call put it up to my face and the screen turns off correctly. Then when I pull it away from my cheek it stays off. The only way to turn it back on it to hit the power button or home button. It's like the sensitivity of the proximity sensor is off.
I just disabled the thing. Really sucks for my conference calls that I mute and unmute and also use have to key into the calls.
Sent from my SCH-I545 using xda app-developers app
.
does anyone have an actual solution for this? i've tried like 5 different custom roms trying to fix it without any luck it's so bad now that i can't even hang up anymore.
nlm842 said:
does anyone have an actual solution for this? i've tried like 5 different custom roms trying to fix it without any luck it's so bad now that i can't even hang up anymore.
Click to expand...
Click to collapse
You guys try using a can of air to blow into the ear piece? Dust gets in there and screws with the proximity sensor. People have fixed it that way. Also if you have a case on try making a call with the case off and see if that happens. Sometimes Even though you wouldn't think it...its too close to the sensor and messes it up. Had that happen to me
Sent from my SCH-I545 using XDA Premium 4 mobile app
Mistertac said:
You guys try using a can of air to blow into the ear piece? Dust gets in there and screws with the proximity sensor. People have fixed it that way. Also if you have a case on try making a call with the case off and see if that happens. Sometimes Even though you wouldn't think it...its too close to the sensor and messes it up. Had that happen to me
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'll try it later today and get back to you on how it worked
Let us know if that works. I've been having this problem as well. However, I feel like it started happening after the last update to VRUEMK2. After that is when I noticed it, although that may just be a coincidence.
Basically no matter if I call someone or answer a call, the second I put it to my face and the screen shuts off(or if I hit the power button) it stays that way forever until the other person hangs up on their end. The screen won't turn back on until they hang up.
Sent from my SCH-I545 using xda app-developers app
My girls sprint s4 was the one doing this and like I said the compressed air thing worked. Poor design if dust can get into the ear piece and mess with a sensor that's not even right next to it. Oh well. Let me know how you guys make out
Sent from my SCH-I545 using XDA Premium 4 mobile app
compressed air works
Just tried the compressed air. It works. I agree that this is stupid.
Huge thank you to whoever mentioned compressed air in this thread. This was driving me nuts at work trying to manage through phone trees or switch calls without being able to get the screen back on. Compressed air was the fix.
THANKS!!!!!
Method 1.
As it happens due to dust so blow Air from ear speaker that will clear the dust from your sensor and solve your prob hopefully.
Method 2 (Root Needed).
go to samsung code *#0*#. then SENSORS and Read your Proximity sensor values.
Calibration is not needed if
your phone doesnt vibrate in normal but does so when u physically put your finger on the Sensor.
Calibration needed if
your phone is vibrating in this menu no matter what, you put your finger on the sensor or not
Follow these steps
1. download Android Terminal from store
2. type these commands to calibrate automatically
$ su
# echo 0 > /sys/devices/virtual/sensors/proximity_sensor/prox_cal
# echo 1 > /sys/devices/virtual/sensors/proximity_sensor/prox_cal
Reboot and see if it works.go to *#0*# and check if it continuously vibrating or only does so when you put your finger on the SENSOR.
I still continuously vibrating even after putting the upper comments use this manual maethod which always works
you need to manually put values in ur /efs/prox_cal.it Reads Hexadecimal value. so you have to convert your decimal values into HEX (which can be done by any online decimal to Hexadecimal converter).
FIND YOUR Decimal Values and pushing them into /efs/prox_cal
Method : finding two values for calibration . offset + normal value.
FINDING OFFSET
cat /sys/devices/virtual/sensors/proximity_sensor/prox_cal
note down the values it returns.. mine is 5,64,100.. you only need the 1st value which is 5.
FINDING NORMAL STATE
cat /sys/devices/virtual/sensors/proximity_sensor/state
note down the value if returns. mine is 64
now ADD OFFSET value + Normal Value
5 + 64 = 69
Convert in Hexadecimal which is 45.
Pushing the value in /efs/prox_cal
# echo -en $'\x45' > /efs/prox_cal (if not working try giving "space" after $ i.e. $ '\x45)
then
# chown system:system /efs/prox_cal
# chmod 644 /efs/prox_cal
# sync
# Reboot
All done. after that go to *#0*# then SENSORS and move your finger on the sensor, yout phone will Vibrate only when you put your finger on the sensors.
Source: click here
As of Android 13 (both on my Zenfone 8 and now my Zenfone 9), if I make a call, and then click the "Recents" softkey (that shows all the active apps) and tap the "Home" softkey (or just tap the "Home" softkey), do something, and then want to get back to my active call... I used to click on the phone app launcher and it would always go back to the current call.
Now, though, this doesn't ALWAYS take me to the current active call like it used to; sometimes, instead, it takes me to a new dialer.
If I try to pull down from the top of the phone to go to the active call, the proximity sensor almost always turns off the screen, so that doesn't work very well (a very fast gesture SOMETIMES can get past the proximity sensor, but not usually).
is there a NEW way for Android 13 that I'm supposed to get back to the current active call in a reliable way?
tbessie said:
As of Android 13 (both on my Zenfone 8 and now my Zenfone 9), if I make a call, and then click the "Recents" softkey (that shows all the active apps) and tap the "Home" softkey (or just tap the "Home" softkey), do something, and then want to get back to my active call... I used to click on the phone app launcher and it would always go back to the current call.
Now, though, this doesn't ALWAYS take me to the current active call like it used to; sometimes, instead, it takes me to a new dialer.
If I try to pull down from the top of the phone to go to the active call, the proximity sensor almost always turns off the screen, so that doesn't work very well (a very fast gesture SOMETIMES can get past the proximity sensor, but not usually).
is there a NEW way for Android 13 that I'm supposed to get back to the current active call in a reliable way?
Click to expand...
Click to collapse
The prox sensor is tripping whenever and wherever you try to swipe or touch the status bar? That strikes me as a bug and not intended feature.
Veiranx said:
The prox sensor is tripping whenever and wherever you try to swipe or touch the status bar? That strikes me as a bug and not intended feature.
Click to expand...
Click to collapse
Yeah, it's very annoying. I guess I should report it to Asus. It only happens during an active call.