Database Users

[Q] Proximity Sensor

Hi,
I did the 2.2 update for the Epic through Samsung's website before it was it was warned not to download/update. Now that my phone has the update my proximity sensor is not working at all. When I put my phone up to my ear during a phone call, it does not shut the screen off, it keeps it on where I am able to press keys during calls. It really annoys me and want to know if there is a fix for this or if anyone else is having the same problem?
Thanks,
katie

should probably backup your things and reflash, preferable with odin i would think.

KateC1 said:
Hi,
I did the 2.2 update for the Epic through Samsung's website before it was it was warned not to download/update. Now that my phone has the update my proximity sensor is not working at all. When I put my phone up to my ear during a phone call, it does not shut the screen off, it keeps it on where I am able to press keys during calls. It really annoys me and want to know if there is a fix for this or if anyone else is having the same problem?
Thanks,
katie
Click to expand...
Click to collapse
You could take it in to the store and see what they can do...they will probably just do a hard reset....I think your best bet is to, like the other poster said, do a fresh install of EB13. Most of the problems with this update were with the update and not with the clean install...good luck!

I could probably assume you don't know what odin is and everything so.. maybe someone could post a link to odin and the eb13 tar??
From My Samsung Epic Using TapaTalk.

It's just your install, use the full 200MB samsung exe after backing up your data and you should be good to go. That's not a bug of EB13, just the way your phone patched to it.

So I reinstalled it using Odin and it started up fine, acts fine, but the proximity sensor still does not work. Any other ideas?

KateC1 said:
So I reinstalled it using Odin and it started up fine, acts fine, but the proximity sensor still does not work. Any other ideas?
Click to expand...
Click to collapse
Sorry you did all of that for nothing :-( Download Z-Device Test from the market. There is a test for the proximity sensor in there. If it is not working in the test, I would say you should go to Sprint and have them fix it...I searched for others with your problem and there were a few (not from updating, you might have had it stop working by coincidence). They all ended up going to sprint and having the screen replaced. Just make sure that if you have a screen protector you remove it so Sprint doesn't try to blame that.
Good luck Katie
P.S. If you are feeling adventurous, you could always Odin back to DI18 and see if the sensor works and the back to EB13 to see if it still works....you could also try installing a ROM on top of EB13 and see if that makes it work (though I don't see why it would) Good Luck
Patrick

Thanks Patrick. I have installed older ROM versions, custom ROMs, and the new update and nothing makes the proximity sensor work. I tried the app you suggested and it shows that the proximity sensor was a green check mark which must mean it works. I do not understand what is going on with it. I have done complete erase on the phone and installed several ROMs with only fail on the sensor. I guess I am going to have to go to Sprint, but I hope that if they have to replace something on the phone I do not have to pay for it.
Thanks again

KateC1 said:
Thanks Patrick. I have installed older ROM versions, custom ROMs, and the new update and nothing makes the proximity sensor work. I tried the app you suggested and it shows that the proximity sensor was a green check mark which must mean it works. I do not understand what is going on with it. I have done complete erase on the phone and installed several ROMs with only fail on the sensor. I guess I am going to have to go to Sprint, but I hope that if they have to replace something on the phone I do not have to pay for it.
Thanks again
Click to expand...
Click to collapse
No problem... just tell them it happened after the update and I don't see any reason that they should charge... they seem to be hit or miss about charging sometimes, try a different store if they want to charge... good luck Katie. Let me know how it turned out.
Sent from my SPH-D700 using XDA App

[Q] Proximity/light sensor turns of my screen

Hi!
Ive had a problem with the screen turning of, during calls only, for a couple of months. I think it happend somewhere in July/August.
Now, this question have been asked but there has been no answer that solves this.
There is a solution for Desire HD http://forum.xda-developers.com/showthread.php?t=951858.
I have tried the Proximity screen off http://forum.xda-developers.com/showthread.php?t=624206 for the HD2 but that does not deal with my problem, it did not work for me.
The problem only occurs during calls, the screen shuts of no matter if Iam close to it or not.
The screen does not shut off if I plug in the headset before/in the call and also if there is very very much light before I answer/make a call to the time where I hang up/the other person hangs up.
The screen does not wake up for along time after the call has been ended, unless I put it very very close to a light source ( LED does not work so good, light bulb would do the trick),or the usb charger. If I plug in the headset after the call has ended, the screen is till turned off.
I only have this problem when Iam in android. I have been using AmeriCanAndroid ever since I got the phone in May.
Regarding the Proximity sensor off, I made about 90 different setting combination, Screenoff triggered/not triggered with lockscreen delay immediately/several minutes (CM7 settings) with different values when the screen is covered/uncovered with Advanced task killer on/off.
No matter what I tried the result was either the same or worse.
The interesting thing I found out was the screen (at least for the first seconds) turned off each other time, i.e did not shut off for the first ~10 sec, the next call it shut off immediately.
Is there someone who could create an app/setting for the HD2 so that whatever reaction the phone gives when plugged to charger/headset, regarding the sensor(s), but without actually connecting it, would be a life saver.
This problem is very annoying when Iam in a call and want e.g use the dial/check messages/check the time.
Thank you

Go to your settings, and look for something dealing with your proximity sensor

GSM4ever said:
Go to your settings, and look for something dealing with your proximity sensor
Click to expand...
Click to collapse
Thanks for trying to help me, but I have checked everything on the phone.
Anyways, I think this problem is with the proximity sensor because the light sensor seems to work just fine (automatic brightness/backlight settings is responding to the amount of light)
Thanks!

Default settings on CM7 WITH TYPHOONS roms does not have this problem. Perhaps re-create system since it is same since may. Fresh install and all should be well.
Otherwise check for dirt or finger grease smudging over the proximity sensor.
Used to have this problem too on typhoon. Task29 and starting from scratch solved the problems.

Thanks for your reply!
But I dont know anything about TYPHOON roms, and I dont have a reason to change from americanandroid except for the proximity sensor problem.
Iam writing this in hope somebody can include an app or a setting for the HD2 so one can shut off the proximity sensor, I think that would be the best an easiest solution.

Still suggesting you might wipe everything. When I had issues appearing, I started fresh and it fixed it 99% of the time.
Backup your stuff first if needed, then install the newest American Droid and start from scratch.
You might do a nandroid backup before, then if a fresh install doesn't work, you can restore back right before you backed up.

I have the same problem & I couldn't fix it!
using all the sensor monitors in the Market I can't ge any readings from the light & proximity sensors!
in "Phone tester" the sensors read:
Proximity = Near
Light = 10.0 lx
This for covered & uncovered phone - near or far - dark or light!
I'm using: AmeriCanAndroid 110711(sd)
Radio: 2.15.50.14
I think the file /system/lib/hw/sensors.htcleo.so is the problem.

wh_hsn said:
I think the file /system/lib/hw/sensors.htcleo.so is the problem.
Click to expand...
Click to collapse
The reason why removing that file, fix the problem, is because you basically tell the system that there are no sensors at all.
Now that would be a good enough solution for me, only downside is that the sensor wich tells the phone to go in landscape mode also stop working.
I think if somebody could edit the script to tell the phone to stop using the proximity/lightsensor then the problem would be solved.
I saw a post where archagel got scripts from HyperDroid
Here
I checked the files, but the names did not match with my files, perhaps someone knows more about this?
archagel said:
I had the same problem, so I got libsensors source from HyperDroid, commented out lines that do proximity sensor initialization and got sensors.leo.so that shows to phone that there are no proximity sensor.
There are 3 identical files in the attachment - simply copy them over into /system/lib/hw on the device.
But, actually, repairing sensor would be better solution...
Click to expand...
Click to collapse

[Q] Knock on just stopped working?

I've had my G2 for almost a month now and the knock on/off always worked flawlessly. Then today it just stopped working, my knock off works but knock ON will not work, at ALL! I've restarted, turned the feature off/on, nothing is getting it to work again. Any ideas? What exactly triggers the knock on feature? Surely it can be the touch of the lcd if the screen is off...is it somehow the proximity sensor or gyro sensor? If I can figure out how it works maybe I can start there..Thanks for any help you can give me.

GHII said:
I've had my G2 for almost a month now and the knock on/off always worked flawlessly. Then today it just stopped working, my knock off works but knock ON will not work, at ALL! I've restarted, turned the feature off/on, nothing is getting it to work again. Any ideas? What exactly triggers the knock on feature? Surely it can be the touch of the lcd if the screen is off...is it somehow the proximity sensor or gyro sensor? If I can figure out how it works maybe I can start there..Thanks for any help you can give me.
Click to expand...
Click to collapse
Backup first...then Factory reset
Should fix whatever file or resource that got screwed up. Install your apps 1by1 until you find what app caused your issue & delete it

tiguy99 said:
Backup first...then Factory reset
Should fix whatever file or resource that got screwed up. Install your apps 1by1 until you find what app caused your issue & delete it
Click to expand...
Click to collapse
Well I havent installed anything new recently but maybe I'll take the opportunity to try one of the new CM/ASOP roms...Thanks for the reply

I'm having the same issue with knock on not working. i've wiped a few times and have flashed diferent roms but it wont turn the phone back on. i'm also having this strange issue where i cant pull the notification bar down.
EDIT: I figured it out. did you install TWRP Recovery? i did and mine was messed up. i flashed back to stock and re-rooted and everything works again. I'm not sure if TWRP is the reason since im on a t-mobile G2 but reflashing to stock definitely worked. also i think you have to do a reset after flashing rom because the changes wont take effect unless you do

GHII said:
Well I havent installed anything new recently but maybe I'll take the opportunity to try one of the new CM/ASOP roms...Thanks for the reply
Click to expand...
Click to collapse
Wow that's a relief, I'm having the same pull down issue too.. Even scrolling here is a dead spot on the screen if I'm scrolling a page or list as I get in that area it "slows". I thought my digitizer was going bad. I found my knock on works but I have to do it extremely slow... Tap... Pause 1-2...tap.
Edit yes to twrp.
Sent from my VS980 4G using xda app-developers app

well i re-rooted and it doesnt work anymore. i deleted stuff so i need to see if its something that is being removed that causes it to not work

I just flashed the stock rom back..shows unrooted again, and it is still doing the same thing. Im still under my 30 days, Im going to return it, hope for the Nexus 5 on verizon by the weekend and if not I guess buy a new G2.

mine still says rooted so i'm kinda screwed right now

Same issue
Same thing with my T Mo G2. Using Nova launcher. Knock on worked flawlessly since new, about 2 months,use Nova gesture for knock off. Suddenly knock on stopped working. Too bad, because I like the feature, got used to using it. Did a restore and wipe using TWRP, kept root access, but still no knock on. Next I'll try going back to stock ROM, but I'd rather go an easier route. Has anyone successfully restored knock on?

Hi i have a dead spot somewhere app in the screen and when i pull down the notification bar it doesnt goind down.Also i tryed to draw with quick memo and i can see that it is a dead spot somewhere near the top of the screen
Does anyone has the probleme and have you fixed it

The only solution is returning the phone

ankurcshah said:
The only solution is returning the phone
Click to expand...
Click to collapse
No...first try this.
Open phone app and go to dialer
Dial 3845#*XXX# where XXX is your phone model i.e. 800/1/2/3.. You will come accross a menu.
Select settings
Select touchscreen firmware update...
Wait for couple of minutes...screen will become unresponsive...
when it responds reboot....
Go to settings gestures...ensure knock on is selected.
It should work then,
Let me know...Best of Luck....
---prs thx if helped

rastigo said:
No...first try this.
Open phone app and go to dialer
Dial 3845#*XXX# where XXX is your phone model i.e. 800/1/2/3.. You will come accross a menu.
Select settings
Select touchscreen firmware update...
Wait for couple of minutes...screen will become unresponsive...
when it responds reboot....
Go to settings gestures...ensure knock on is selected.
It should work then,
Let me know...Best of Luck....
---prs thx if helped
Click to expand...
Click to collapse
It is a ls 980 model so the code is 5689#*980# and i did that and after doing that also its the same. no reponse ! So tired of this

ankurcshah said:
The only solution is returning the phone
Click to expand...
Click to collapse
ankurcshah said:
It is a ls 980 model so the code is 5689#*980# and i did that and after doing that also its the same. no reponse ! So tired of this
Click to expand...
Click to collapse
I read the following posts on some other forum...so essentially its a hardware issue....try stock jb rom kdz, then factory reset and reboot. If this helps solve the problem you are lucky. If not, try getting your phone replaced with 802 model. That is practically most stable with a lot of devlopment and tons of ROMS stable and working.
I will still keep looking for a solution and let you know consulting a few senior xda devs I know... sorry man, it hurts to see a fellow indian in distress.....:crying:
Tons of lg users are experiencing this issue. Its a design flaw with a hardware component that easily breaks. Wonderful build quality -_-...right. So only option is replacing the phone. But to how soon, until the other one breaks. So its kinda like. Well. This blows. I suppose Ill install a custom kernel and enable screen wake features that way.
Sent from my LG-LS980 using xda app-developers app
That's odd, I have not seen much on this... if running stock
Quote:
Originally Posted by Burkettacb View Post
Okay. So after hours of tapping. Which might i add. My fingers hurt, I am now able to activate the screen. Pausing after each tap, using my finger print area to tap "not to be confused with finger tip". The screen will activate. Also note, the standard two taps works sometimes, but with four presses, i seem to get the best results. Give it a try people. I have a theory the hardware has not failed. But yet, the activation area pixel size value changed. Either due to a conflicting app install. A intermittent system glitch etc
Sent from my LG-LS980 using xda app-developers app
Or againg, a ROM you may be using.
More detail would be helpful

ankurcshah said:
The only solution is returning the phone
Click to expand...
Click to collapse
Good luck with that if the phone is a D800. I took my G2 to the local AT&T store just a couple of hours ago with the same "no knock on" bug. But the sales person (who had bad breath) told me that because there was another way to get the phone to function (the back button), they won't even look at it. The fact that the knock off/on feature was a MAJOR selling point when the phone was released is apparently irrelevant.

He has a ls980 so it might not be the same for him. He can ask for a replacement
Sent from my LG-D802 using XDA Premium 4 mobile app

This happened to me this week as well, unfortunately in Canada none of the carriers will replace my device for me, LG says its user damage and are gonna charge me 125 dollars to fix it. I'm gonna see what the local repair shop says and hopefully theyll just fix it for me. It seems like this is an increasingly common issue, it's a shame that LG don't recognize that we didn't damage our phones, they sold us defective units. I'm very unhappy with LG's customer service, we should raise awareness of this and hopefully LG will come up with a solution for us

Andrew_han said:
This happened to me this week as well, unfortunately in Canada none of the carriers will replace my device for me, LG says its user damage and are gonna charge me 125 dollars to fix it. I'm gonna see what the local repair shop says and hopefully theyll just fix it for me. It seems like this is an increasingly common issue, it's a shame that LG don't recognize that we didn't damage our phones, they sold us defective units. I'm very unhappy with LG's customer service, we should raise awareness of this and hopefully LG will come up with a solution for us
Click to expand...
Click to collapse
Did you try the "Hidden Menu" "Touch firmware update" option? I had this issue and it got fixed with it.
try 3845#*modelnumber# eg: 3845#*800# change model number 800 with your phones model number, then tap on "Settings" and scroll down to "Update Touch Firmware"
I have a few more suggestions to make it work, let me know how it goes.

[SOLVED] No Knock-On/Knock Code

After toying with ROMs I've noticed that knock-on went missing on my G2 D802. Same for Knock Code on ROMs that claim to support it (and worked for me at some point earlier).
Some googling revealed that it could be related to bad touchscreen/proximity sensor error.
However, this is not the case: during call the screen turns off and on correcly, not getting stuck after call etc.
Touch works perfectly as well: dragging notification center at any point, could fill the screen in draw app with a single, long stroke.
Flashing to stock KK using this guide, then resetting to factory settings (which took reeeeally long, like 10-13 minutes. Also scared the cr*p out of me because I thought I bricked it ) didn't help as well.
Has anyone encountered such issue? If yes, how can I deal with it?
Maybe some way to enable sweep2wake instead? I'm really fine with ANY gesture to wake that works.

Siema89 said:
After toying with ROMs I've noticed that knock-on went missing on my G2 D802. Same for Knock Code on ROMs that claim to support it (and worked for me at some point earlier).
Some googling revealed that it could be related to bad touchscreen/proximity sensor error.
However, this is not the case: during call the screen turns off and on correcly, not getting stuck after call etc.
Touch works perfectly as well: dragging notification center at any point, could fill the screen in draw app with a single, long stroke.
Flashing to stock KK using this guide, then resetting to factory settings (which took reeeeally long, like 10-13 minutes. Also scared the cr*p out of me because I thought I bricked it ) didn't help as well.
Has anyone encountered such issue? If yes, how can I deal with it?
Maybe some way to enable sweep2wake instead? I'm really fine with ANY gesture to wake that works.
Click to expand...
Click to collapse
you can try the 1st post from here to see if that works, different problem but it can be the solution

XxZombiePikachu said:
you can try the 1st post from here to see if that works, different problem but it can be the solution
Click to expand...
Click to collapse
IT WORKED! 1000 thanks to you man!!!!
I already managed to flash full JB initial stock firmware with flashtool (with no avail) and this simple stuff did the trick
Thank you again!

Screen is always on - Help? [SOLVED?]

Hello!
I am unable to turn my screen off. When the phone tries to sleep and the screen turns off then it immediately turns back on in a loop forever. The same happens when I turn it off by pressing power button. I have done stock revert via odin and factory reset and the issue persists. I also have tried few other roms and wiped everything. what can I do? Please help me, thank you!
Phone model: Samsung galaxy J5 (00fn) 2015
Currently on stock 5.1
In the logcat screen goes off around 10:12:22.492 and then back on at 10:12:23.012

For others having the same issue; I found a 'better than nothing' solution. Google play - "screen filter" app. First set the icon in a place u remember at your home screen and then set 'screen filter' percentage to lowest and run the app. Voila! If you use a custom rom that supports it or have rooted your phone then you can assign a hardware button to launch that app on/off and if not then use "button mapper" from play store.

OK. I think I have solved this for good(?) On my phone. I have managed to get my screen working NORMAL without using screen filter about five times in a row now after installing new ROMs. If this method works for others I would be glad to hear. This might sound a bit odd but the method goes like this: first thing after installing a ROM I download the screen filter app. Then I press it on and off once. Then I assign the app to long press recents button and I disable all functions from home button except for 'double tap = home'. Then I long pressed the recents button couple times and after that let the screen dim and go off by itself and now my screen works!! I can remove the screen filter app and change the hardware buttons back and it works even after reboot! Unbelievable! Please share your thoughts if this worked for you also. BTW I'm now using resurrection remix official by SoUnd001 so at least for this ROM this trick works. (Customizable hardware buttons make this easy)

turkkilainenpippuri said:
Hello!
I am unable to turn my screen off. When the phone tries to sleep and the screen turns off then it immediately turns back on in a loop forever. The same happens when I turn it off by pressing power button. I have done stock revert via odin and factory reset and the issue persists. I also have tried few other roms and wiped everything. what can I do? Please help me, thank you!
Phone model: Samsung galaxy J5 (00fn) 2015
Currently on stock 5.1
In the logcat screen goes off around 10:12:22.492 and then back on at 10:12:23.012
Click to expand...
Click to collapse
Hello!
I've checked your logcat, but I don't know what's the issue due the lack of knowledge. There seems that these two lines appear right after lines related to the display:
Code:
E qdutils : int qdutils::getHDMINode(): Failed to open fb node
E qdutils : int qdutils::getHDMINode(): Failed to find HDMI node
There is also some errors regarding lights.
My questions are:
1) Did you modify that stock ROM in any way or you've been running stock ROM + stock kernel as it is? If you did modify it, what modifications did you make? If you used stock as it is, then the software shouldn't be the culprit for your issue.
2) You've been using screen filter apps before for long time? If yes, maybe this could be the problem. When I've checked the comments at a screen filter app in past, i did read that it harmed the phone of some people. However, might be fake comments as well. You can also search on Google something like: "android does screen filter harm?".

@#Henkate I also noticed those errors but couldn't find out the cause. Thanks for trying to solve!
Q1. Yes it was pure unmodified stock ROM flashed via odin. The issue was still there so I figured it must be hardware related BUT after flashing TWRP I noticed that the screen worked fine in the recovery ie dimmed and went off normal.
Q2. I hadn't heard of the 'screen filter' app before this issue. I think this app actually fixes my issue although the problem returns after installing new ROMs.
Thanks for support! :good:

turkkilainenpippuri said:
@#Henkate I also noticed those errors but couldn't find out the cause. Thanks for trying to solve!
Q1. Yes it was pure unmodified stock ROM flashed via odin. The issue was still there so I figured it must be hardware related BUT after flashing TWRP I noticed that the screen worked fine in the recovery ie dimmed and went off normal.
Q2. I hadn't heard of the 'screen filter' app before this issue. I think this app actually fixes my issue although the problem returns after installing new ROMs.
Thanks for support! :good:
Click to expand...
Click to collapse
This is kinda weird. Well, as long as that workaround works...
I also thank you for changing the thread name to "solved" and posting the solution/workaround! There aren't many users like you which does these two things, at least at J5 forum.
Have a nice day!