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
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
Nothing I can do will make screen rotation work correctly. Have tried all the usual fixes:
1. Turned on in settings.
2. Done GPS Status calibration.
3. Done figure of eight calibration.
4. Tried various kernels.
5. Tried various ROMs.
6. Done *#0*# and the graph shows everything moving correctly on all three axes.
However, when I do "gyro self test" I sometime get big red FAIL.
Here are two results:
Normal 0 0 -1
SelfTest -437 435 -460
PASS
Normal 0 0 -1
SelfTest -437 434 -460
FAIL
Anything left for me to try?
Looked up some more possible solutions including this one: http://www.techbeats.co.in/2012/12/samsung-galaxy-screen-rotation-problem.html
No dice.
Sometimes the screen does rotate but it is about 30 seconds too late and then doesn't' return back to portrait. Sometimes it gets stuck upside down. Anyone have any clue about this issue?
How can I fix this?
I'm working on an app to turn on the screen when my tablet is rotated from horizontal to vertical. It works as
desired when it runs at the same time as the Shake app.
When the Shake app is not running, it can take 10 to 20 seconds to much longer to never for the screen to come on after I've rotated the tablet.
What does Shake do that lets my app work as desired? What can I change in my app so the screen comes on very soon after the tablet is rotated.
The code that turns on the screen:
Code:
// Turn on the screen
PowerManager pm = (PowerManager)getSystemService(Context.POWER_SERVICE);
PowerManager.WakeLock wl = pm.newWakeLock(PowerManager.SCREEN_BRIGHT_WAKE_LOCK
| PowerManager.ACQUIRE_CAUSES_WAKEUP, "tag");
wl.acquire();
System.out.println("ScrnOnOffSrvc Turned on screen at "+ sdfTime.format(new java.util.Date()));
try{Thread.sleep(100);}catch(Exception x){} // wait some ???
wl.release(); // get rid of it and hope screen stays on a while???
Hi all,
I've got a strange problem with my Gear Fit. It stopped counting steps and waking up on hand guest. Now I've done a check of sensor using a test mode, instructions found here:
http://forum.xda-developers.com/showthread.php?t=2739949
Gyroscope and Accelerometer is showing different real values while Gear Fit is moving. However the Fit is not waking up on guest and not counting steps.
Now reboot by holding for 7 sec the power button was done.
Erasing the data and pairing again the Fit was done.
I'm out of ideas now....
Anyone had such issue?
Regards,
P
Fixed it Just figure out what was wrong. The accelerometer was showing a strange high value on the y axis. Now restarts did not solve it. I've remembered that I've hit a wall with the watch yesterday.... Not big hit but apparently was enough to hung the accelerometer in the watch. Now with running test menu -> sensors and graph I've hit it again (not very hard) from the top and it started to work again ....
Just pasting this if someone will look for a answer.