Related
Not sure if anyone found a fix, but someone on the Google Code forum has found a solution. I am NOT taking credit for his fix, simply getting it out there as it is a huge issue.
1) Open up the .zip for your custom or stock Rom and look in the /system folder for a file called "build.prob". Copy this to your Desktop as you will be editing the file and then replacing the original on the Rom.
2) Open Notepad++ or any text editor of your choice and open the file. You are going to want to search for a line that says:
# try to disable proximity sensor in call by default
gsm.proximity.enable=false
Uncomment that line and make it equal to false.
3) Next, copy it back onto the /system directory of the Rom and then flash it. If it doesn't work for you, I am sorry. This is what worked for me so I just wanted to get another solution out there.
Again, I did not make this solution! I found it on Google Code forums.
Enjoy!
What problem does this fix ?
After making a phone call, there should be a process called Dialer. It gradually increases over time to 99% and kills the battery
Sent from my HTC Wildfire S A510e using XDA App
Small correction
Hey, small correction to your above post, hopefully this helps somebody out there
The file is actually build.prop
And the original commented line looks like the below WITH the hash in front
# try to disable proximity sensor in call by default
#gsm.proximity.enable=false
Instead of reflashing the ROM I booted the phone into recovery, then did
adb shell
adb mount /system
exited the adb shell, then
adb pull /system/build.prop c:\temp
edit c:\temp\build.prop, removed the comment hash
adb push c:\temp\build.prop /system/build.prop
rebooted, made a call, watching the battery usage, and dialer isn't at 98% after 30 minutes, in fact, it hasn't even shown its ugly face!
Awesome, thanks for that find!
Ah. Been reading posts all over and they all say to remove the hash tag. I'll give this a try later. You can for sure tell its not showing up after a reboot, power off, etc.? This really is an frustrating bug we have on our hands and I for one hate having a phone that lasts ~5 on a ful charge.
Sent from my HTC Wildfire S A510e using XDA App
Quick question. Dialer is already in my processes running. Will it still work or do I need to clear it first, cause I have no idea how to do that lol.
Sent from my HTC Wildfire S A510e using XDA App
Need your help. I'm trying to run these commands, but they aren't working for me. When I go to type adb shell mount /system, it keeps saying adb: not found. Any help with this? I used to be able to do this, but it's not letting me do it
Please clarify one thing for me...
I don't know for sure but this seems to disable the phone's proximity sensor during calls, so the screen will be always on while calls are being made (until the screen timeout activates).
Am I right? If so this fixes one bug and creates another problem.
I would be glad if someone that already tried this can confirm what I'm thinking.
Thanks a lot in advance.
Confirmed,i used this long time ago and the display stayed on for whole time during call and also proximity was disabled for screen auto brightnes(probably more apps)
aigaming said:
Confirmed,i used this long time ago and the display stayed on for whole time during call and also proximity was disabled for screen auto brightnes(probably more apps)
Click to expand...
Click to collapse
But it seemed to work for me. I did it and rebooted my phone and the Dialer process was gone. I then made a test call and while the call was on, the Dialer process was not there. Then, I kept checking and it still did not appear. I also applied the best battey tip you'll ever need.
aigaming said:
Confirmed,i used this long time ago and the display stayed on for whole time during call and also proximity was disabled for screen auto brightnes(probably more apps)
Click to expand...
Click to collapse
aigaming, thanks a lot for confirming what I already suspected.
This is a "fix" that creates an even bigger problem.
Last week I had a phone call with an Engineer that lasted more than 80 minutes.
If the screen was on during this period then instead of the Dialer draining the battery I would have the LCD draining the battery.
I don't need the proximity sensor for auto-brightness for example (like to set it on my own) but it shouldn't be turned off because it's probably necessary for the camera application (for example).
This Dialer battery drain is just a cosmetic bug IMO.
If we want to know what really eats our batteries then we should use *#*#4636#*#*, usage statistics instead.
There is info in miliseconds of usage by each app.
And what about fix for S-ON phones?
shaarky said:
And what about fix for S-ON phones?
Click to expand...
Click to collapse
If you edit the file, replace it on the ROM and flash it, then this method works on s-on phones. Be warned that the screen will remain on during calls.
miguelca said:
I guess that's off-topic here. This thread is about another problem.
Click to expand...
Click to collapse
Well, I mean if there is some way to apply this on S-ON phone.I think it's not, so better to update name of the thread...
I also interested in fix for battery drain on s-on phones. Mine adb says permission denied.=(
shaarky said:
Well, I mean if there is some way to apply this on S-ON phone.I think it's not, so better to update name of the thread...
Click to expand...
Click to collapse
The method drzerog uses is for s-off phones. The method on the first post works with all, s-on included.
Sent from my HTC Wildfire S A510e using XDA App
shaarky said:
Well, I mean if there is some way to apply this on S-ON phone.I think it's not, so better to update name of the thread...
Click to expand...
Click to collapse
I updated my posts. Sorry for the mistakes but now info is correct. Please read again. Thanks.
Sent from my HTC Wildfire S A510e using XDA App
I can also confirm that, for me, during a call it does NOT leave the screen on. It turns it off on my device. Maybe it's different for each phone? But that can't be. Weird. Again, confirming it works on my device and my battery is now showing proper statistics, as well as Dialer process not appearing
Also wanted to make note that I have changed the topic title and noticed this thread is now in the rom/recovery/guides/kernal/root stickie!! VERY COOL!
Not work for my WS rom 2.3.5 stock/ S-OFF, the dialer process still keep 92%
Hey,
is there any way to calibrate the proximity sensor one the One X?
For some reason my proximity Sensor needs very high brightness values to activate the screen again, when calling. This happens on every ROM I use, even stock. Does anyone else have this issue and is there a solution? I've been looking for a while now but only found solutions for other devices. Help would be very appreciated
Are you taking about ambient light sensor?
Proximity sensor is sensor made for distance detection.
No I actually mean the proximity sensor. I know it shouldn't be depending on light but it does. I don't know why. First I thought the sensor is broken, but if there is enough light it reacts to movement. If not I'm not able to get the screen back on until the other person hangs up. Its really weird. Sometimes even the little red light stays on. In the DHD forum i saw a thread about someone who developed an app to recalibrate the proximity sensor, so i thought this could also be done for the HOX.
For your knowledge, the proximity sensor on One X is kind of binary type (return 0/1;object detected /none). There are some sensors test tool offers on play store, you may try them out..
Sent from my HTC One X using Tapatalk 2
Ok. I did that already. Same happens there. Thats why Im not sure if its malfunctioning or just needs to be calibrated.
Sent from my HTC One X using xda app-developers app
Well, this is enough. I have to assume that its a hardware defect and I wont send it in a 6th time.Getting rid of this contract next week.
Sent from my HTC One X using xda app-developers app
Marc199 said:
Well, this is enough. I have to assume that its a hardware defect and I wont send it in a 6th time.Getting rid of this contract next week.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
i had exactly the same problem. You can fix it with http://forum.xda-developers.com/showthread.php?t=1882725 this patch. All you need is a custom rom with init.d support. Cheers!
You can use this.
http://forum.xda-developers.com/showthread.php?t=1904974
frwida said:
You can use this.
http://forum.xda-developers.com/showthread.php?t=1904974
Click to expand...
Click to collapse
Thanks! That solved the problem for me. I had always found the proximity sensor a bit too unresponsive. I didn't know it could be callibrated.
Ok i found out that my proximity sensor is working but it needs a lot of light to see me i was wondering if there is a way to calibrate it manually and i can update to jellybean my phone is from mexico telcel and my CID BSTAR301 i tried some of the apps in the playstore but they dont work i using stock rom whit ICS can somebody help please
You'll need root access, read the sticky in android development forum
Sent from my EndeavorU using Tapatalk 2
All credits go to ginodp and the users he mentions for finding the solution for a similar problem on the Desire S. Here is the link to the original thread.
The problem: An awful lot of HTC Desire phones have a malfunctioning proximity sensor which constantly reads 0.00 cm i.e. complete obstruction. This causes the phone to blank out the screen during a phone call but never light it up again. Trackball wake and other methods generally don't work; inserting a headset sometimes works, but obviously it's not a workable solution.
The solution: The solution is disabling the proximity sensor. To do this you will need a rooted phone. Edit the file \system\build.prop with any editor that has been granted Superuser permissions by adding the line
Code:
gsm.proximity.enable=false
at the end of the file. Done! now the phone's proximity sensor is disabled and the screen will not blank out during a call, enabling you to end it at will.
I don't understand how to do that, could you give me a noob-proof rundown? Sure thing!
Code:
1. Have rooted phone.
2. Download BuildProp Editor from Google Play.
3. Press "get su prompt"
4. Gran Superuser permission.
5. Press menu, Add property.
6. In "Type in keyname" type gsm.proximity.enable
7. In "Type in value" type false
8. Press "Save value to file".
9. Reboot phone to let changes take effect. Done!
Any further questions or ideas on how to make this easier or better are much appreciated.
Again, all props to original finders!
malaspina_speaking said:
gms.proximity.enable=false
Click to expand...
Click to collapse
Typo... u mean gsm.proximity.enable=false
Sent from my HTC Desire using Tapatalk 2
Thanks!
Is proximity sensor not work on all Desire (Bravo) phones?
Oh great. So now you can hang up the call by accident with your ear.
Sorry, but disabling the proximity sensor is plain stupid?!
In my old winmo6 days u had to manually press the orf button to shut down the screen.
I guess with this u can do the same. Use off button instead of the sensor kicking in?
Sent from my HTC Desire using Tapatalk 2
Can i use this solution for my galaxy i9000 cause my sensor not working and service need 50 eu to change it.
Sent from my GT-S5670 using xda premium
vigan_ks said:
Can i use this solution for my galaxy i9000 cause my sensor not working and service need 50 eu to change it.
Sent from my GT-S5670 using xda premium
Click to expand...
Click to collapse
It should be universal fix.
Sent from my HTC Desire using Tapatalk 2
sudkcoce said:
Oh great. So now you can hang up the call by accident with your ear.
Sorry, but disabling the proximity sensor is plain stupid?!
Click to expand...
Click to collapse
Unlike some other run ins from the past, this I completely agree with.
Sent from my HTC Desire using Tapatalk 2
Unfortunately my proximity senor is brocken.... I have tried everithing to disable it but no success.
Now is in service center... waiting for repair... new sensor:crying:
Nikog
Yeah well why don't you try to enter a number after the screen goes dead for automated services that depends on it...
This is meant as a fix for ppl that have faulty proximity sensors. Not for fully functioning phones.
IF I had a faulty one this would be perfect.
Press off button after you have answered and your ear won't press a single thing. Press off again and screen goes on.
Sent from my HTC Desire using Tapatalk 2
I have Desire with broken proximity sensor
I tried this build.prop edition, but it doesnt helped
Is there any more methods?
Daredee said:
I have Desire with broken proximity sensor
I tried this build.prop edition, but it doesnt helped
Is there any more methods?
Click to expand...
Click to collapse
Installed MIUI ROM, it has disable prox sensor option in settings
sudkcoce said:
Oh great. So now you can hang up the call by accident with your ear.
Sorry, but disabling the proximity sensor is plain stupid?!
Click to expand...
Click to collapse
The alternative is not being able to end calls, which kinda sucks ass. I wrote that in the OP though, so what exactly is your objection?
My solution was...
I thought that I have the same problem but after all I found out what caused it - it was a low-quality faceplate as I changed it. After I put a new original one the problem was gone.
Big Thank you!
A big thank you!!! Just the buildeditor is huge, let alone the good data!
Thank you!
malaspina_speaking said:
All credits go to ginodp and the users he mentions for finding the solution for a similar problem on the Desire S. Here is the link to the original thread.
Again, all props to original finders![/B]
Click to expand...
Click to collapse
sudkcoce said:
Oh great. So now you can hang up the call by accident with your ear.
Sorry, but disabling the proximity sensor is plain stupid?!
Click to expand...
Click to collapse
Sometimes, signal stops, when covering proximity sensor!
recompiling kernel with modified drivers also helps
bokisis said:
Sometimes, signal stops, when covering proximity sensor!
Click to expand...
Click to collapse
I've tested several solutions found on the web, but none of them helped
(using Screebl, gsm.proximity.enable=false among them)
I ended up modifying kernel drivers (in case of my htc desire i was drivers/input/misc/capella_cm3602_htc.c)
I changed capella_cm3602_report routine to read:
Code:
static int capella_cm3602_report(struct capella_cm3602_data *data)
{
int val = 1;
D("proximity %s\n", val ? "FAR" : "NEAR");
/* 0 is close, 1 is far */
input_report_abs(data->input_dev, ABS_DISTANCE, val);
input_sync(data->input_dev);
wake_lock_timeout(&proximity_wake_lock, 2*HZ);
return val;
}
ie always return FAR instead of NEAR.
Then I recompiled the kernel, and reflashed zimage with fastboot.
Now it no longer locks the screen during voice calls.
Anyone here experiencing uncalibrated compass or rather if they have installed a compass app and shows different orientation?
Does anyone know how to calibrate well their compass?
Moving the phone in a figure of 8 horizontally doesn't work I've even tried vertically...
I'm using Tiny Compass and I've tried installing it on different android phones and tablets only the grand show a different orientation...
I use always a compass and gps apps due to nature of my work
Thanks in advance..
+1.
Think it is weak magnetic sensor.
Sent from my GT-I9082 using Tapatalk 2
polpan said:
Anyone here experiencing uncalibrated compass or rather if they have installed a compass app and shows different orientation?
Does anyone know how to calibrate well their compass?
Moving the phone in a figure of 8 horizontally doesn't work I've even tried vertically...
I'm using Tiny Compass and I've tried installing it on different android phones and tablets only the grand show a different orientation...
I use always a compass and gps apps due to nature of my work
Thanks in advance..
Click to expand...
Click to collapse
the thing about caliberation iis just go to settings->motion->senstivity settings->gyroscope caliberation ... then place your phone on a flat surface and tap caliberate....
this may solve ur problem probably..
otherwise just go to dialer and type *#0*# u will see a new window , select sensor from their and see if all of them are working properly...:good:
panku123 said:
the thing about caliberation iis just go to settings->motion->senstivity settings->gyroscope caliberation ... then place your phone on a flat surface and tap caliberate....
this may solve ur problem probably..
Click to expand...
Click to collapse
No.. I tried this thing many times... but no use...
[/QUOTE] otherwise just go to dialer and type *#0*# u will see a new window , select sensor from their and see if all of them are working properly...:good: [/QUOTE]
tried that >sensor>magnetic sensor>selftest = pass...
This means it is working... is there anything we need there to fix the issue...?
SRISRIANDROID said:
No.. I tried this thing many times... but no use...
Click to expand...
Click to collapse
otherwise just go to dialer and type *#0*# u will see a new window , select sensor from their and see if all of them are working properly...:good: [/QUOTE]
tried that >sensor>magnetic sensor>selftest = pass...
This means it is working... is there anything we need there to fix the issue...?[/QUOTE]
ur issue is related to magnetic sensor only??/ right... tell me if auto rotation is working properly???
[/QUOTE]
ur issue is related to magnetic sensor only??/ right... tell me if auto rotation is working properly???
[/QUOTE]
Auto rotation and everything works perfectly. Only thing is compass app(magnetic sensor).
By the way I always turn of auto rotation.
Sent from my GT-I9082 using Tapatalk 2
ur issue is related to magnetic sensor only??/ right... tell me if auto rotation is working properly???
[/QUOTE]
Auto rotation and everything works perfectly. Only thing is compass app(magnetic sensor).
By the way I always turn of auto rotation.
Sent from my GT-I9082 using Tapatalk 2[/QUOTE]
then there are two options bro... probably there may be some error (lyk some kind f file missing or things lyk dat) if u r on stock rom just take backup of everything and factory reset your phone... sometimes it happens..
still if u r facing same problems i must say contact samsung servICE center to get ur phones motherboard replaced...as it may also be a hardware bug...
ultimately if u r on custom rom.. ask its developer to help u out..
Anyway I will contact Samsung service center.
Sent from my GT-I9082 using Tapatalk 2
SRISRIANDROID said:
Anyway I will contact Samsung service center.
Sent from my GT-I9082 using Tapatalk 2
Click to expand...
Click to collapse
ok bro....:fingers-crossed:
I tried this trick which i read it somewhere...
rotating the phone 3 time on all its axis..(x,y.z), sideways, laying flat, and facing the screen.. something like that...(hoping i explained clearly )
I open my compass app then do the rotations and there i got the correct direction of north.... i havent tried yet if when i restart the fone if still have the correct orientation.
polpan said:
I tried this trick which i read it somewhere...
rotating the phone 3 time on all its axis..(x,y.z), sideways, laying flat, and facing the screen.. something like that...(hoping i explained clearly )
I open my compass app then do the rotations and there i got the correct direction of north.... i havent tried yet if when i restart the fone if still have the correct orientation.
Click to expand...
Click to collapse
Poplan...
Please explain clearly how to caliberate that.. And Please check the compass app showing exact north when you restart the phone.
SRISRIANDROID said:
Poplan...
Please explain clearly how to caliberate that.. And Please check the compass app showing exact north when you restart the phone.
Click to expand...
Click to collapse
I followed youtube video to calibrate. Now it seems working properly.
Sent from my GT-I9082 using Tapatalk 2
polpan said:
I tried this trick which i read it somewhere...
rotating the phone 3 time on all its axis..(x,y.z), sideways, laying flat, and facing the screen.. something like that...(hoping i explained clearly )
I open my compass app then do the rotations and there i got the correct direction of north.... i havent tried yet if when i restart the fone if still have the correct orientation.
Click to expand...
Click to collapse
Yup... Tried that trick. Works perfectly.
But after reboot.... Same thing happens... Have to calibrate again.:'(
Sent from my GT-I9082 using Tapatalk 2
by recalibrating the sensors it may work
Sarath280 said:
by recalibrating the sensors it may work
Click to expand...
Click to collapse
Do we need to calibrate at each boot?
Sent from my GT-I9082 using Tapatalk 2
SRISRIANDROID said:
Do we need to calibrate at each boot?
Sent from my GT-I9082 using Tapatalk 2
Click to expand...
Click to collapse
no we dont need to recalibrate sensors at each boot just recalibrate once.
Sarath280 said:
no we dont need to recalibrate sensors at each boot just recalibrate once.
Click to expand...
Click to collapse
But I have to recalibrate each reboot. Otherwise is showing wrong directions. Any fix?
Sent from my GT-I9082 using Tapatalk 2
I tried calibrated before, I just shake my phone like a "madman" in the sensor monitor section (*#0*#). Until you see the arrow pointer is blue and indicate 3. Then you have successfully calibrated it. Hope that helps
SRISRIANDROID said:
But I have to recalibrate each reboot. Otherwise is showing wrong directions. Any fix?
Sent from my GT-I9082 using Tapatalk 2
Click to expand...
Click to collapse
wait lemme check.
Some times the problem is with the application too..
I had the same problem..
But now im using" smart tools" appn.
It works fine..
Go try it buddy!
Sent from my GT-I9082 using xda app-developers app
My sensors are good, this must be software related since it happened at the first boot of a new ROM.
Problem is, even if I flash stock firmware I have no luck making auto rotation and other motion features such as quick glance to work.
Anybody got an idea?
Anyone?
Please this is exhausting
rotem07773 said:
Please this is exhausting
Click to expand...
Click to collapse
Are you Sure Your Sensors are Good.
Open The Phone & Apply Alcohol to the Sensor Connecting Strips ....
OR
Trying Using a Different Sensor Flex from Your Friends or someone else's Note 2 ...
mgvishal said:
Are you Sure Your Sensors are Good.
Open The Phone & Apply Alcohol to the Sensor Connecting Strips ....
OR
Trying Using a Different Sensor Flex from Your Friends or someone else's Note 2 ...
Click to expand...
Click to collapse
It must be software related.. When i flashed the leaked 4.3 it was fixed, but after a week stopped again
rotem07773 said:
It must be software related.. When i flashed the leaked 4.3 it was fixed, but after a week stopped again
Click to expand...
Click to collapse
What apps are you using to test the errors... If they aren't compatible with the leaked 4.3 then that might be the issue? Also kernal compatibility might be what's throwing it off
Sent from my SGH-T889 using xda app-developers app
PhxDroid86 said:
What apps are you using to test the errors... If they aren't compatible with the leaked 4.3 then that might be the issue? Also kernal compatibility might be what's throwing it off
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Well i try to rotate the screen for starter's.. Calibration don't even respond to movement as the ball stays in the center. Gyroscope demanding apps such as flight games dont work. Its not 4.3 as 4.1.1 and 4.1.2 don't fix it either
Same problem since 2 months
i too have the same problem...
i guess i can say that i'm not a noob... searched everything on the internet for this problem...
found no solution yet...
i too thought this was a kernel related problem ... tried many roms and kernels ... even i unrooted my phone and installed the stock ROM ... no help still..
i got the sensors working by accident sometimes ... but they again stopped working randomly...
i didn't open up my phone yet .. and didn't give it to the service center... thinking of doing that in some days
i guess the problem started when i dropped my phone and cracked the screen ... 4-5 months ago .. gave it to an unauthorized repair to replace the screen .. i guess he messed something up ..
but the problem started way after i replaced it ... started giving the problem since 2 months after the repairs...
any help before i spend more money to repairs/replace the sensors? .. \
attaching a screenshot from CPU-Z