Develop Bugs

[req] Disable Proximity Sensor

I've been trying to pour through the API and find a way I can access and disable the proximity sensor with some code, but have been unsuccessful.
Does anyone know of a way, rooted or unrooted, that I can disable the proximity sensor completely?
I searched the forums and the only ways I found seem applicable to WinMo based phones.
Heck, I'll pay for a way to do it, I hate the proximity sensor that much.
Even if someone knows of a way I could disconnect it by opening my phone, I might even spring for that - but obviously a software approach would be much more appreciated...
Thanks!

redball said:
Heck, I'll pay for a way to do it, I hate the proximity sensor that much.
Click to expand...
Click to collapse
Why do you hate it, if I may ask?

larsrya8 said:
Why do you hate it, if I may ask?
Click to expand...
Click to collapse
It is unreliable, and I know it isn't just my phone because a number of people I know also have an HTC Incredible and it seems to behave just as erratically on theirs.
Based on the code I read through for Phone.apk or whatever, it seems like it is supposed to disable the proximity sensor when you're using bluetooth, just like when using the speakerphone - but it doesn't. I can't figure out why, and I noticed another thread floating around with users having the same issue.
I want to be able to use my phone while on a call and not have to worry about a shift in overhead light or something passing over the sensor and flipping the screen off while I'm trying to use it.
I would much prefer the ability to disable it entirely, and have full control of the screen off/on using the power button.
There was one app on the app store recommended in my searches that let's you lock the screen on and only go off based on orientation or something, but it doesn't seem to work for the HTC Incredible

Try screebl? Should keep your phone on based on orientation, I think even during a call? Not sure though.
Sent from my ADR6300 using XDA App

drawde said:
Try screebl? Should keep your phone on based on orientation, I think even during a call? Not sure though.
Click to expand...
Click to collapse
I tried Screebl, too...but unless I'm configuring it wrong - it doesn't seem to work while in phone calls.

I hate it too. Makes my screen turn on and off when I use my bluetooth.
Sent from my HTC Incredible

I'm right there with you on this. I really hate being on a call and having the screen turn off and have to shake the phone around to be able to end the call.

JTCGiants56 said:
I'm right there with you on this. I really hate being on a call and having the screen turn off and have to shake the phone around to be able to end the call.
Click to expand...
Click to collapse
That's the worst! It's like it gets doubly worse just when I want to be able to hang up.
If it helps anyone...I found these links. (If you google for "mProximityWakeLock", and follow the first Stack Overflow link, it also has two links in it to PhoneApp.java and InCallScreen.java)
I tried making an app that just kept calling release(), but it ended up just creating force closes.

you guys should email HTC so t hey fix it in the next OTA.

I know this is not really about droid, but what proximity sensor also does is scale down CPU speed (even despite using setcpu) making Skype completely useless without a headset.
When you initialize a call - everything is cool.
If you hold your phone on your hand and use loudspeeker - it's cool.
As soon as you put it to close to your face/ear - not cool anymore. To the point where it's absolutely impossible...
Cheers!

It does check for a headset plugged in, bluetooth audio or the speakerphone enabled. For bluetooth, it gets a code from a getState method. It only prevents the screen from turning off if it equals a specific state. All you have to do is force it to always be true.
You can also put this in the build.prop to completely disable it.
Code:
gsm.proximity.enable=false

How i do this?
ihtfp69 said:
It does check for a headset plugged in, bluetooth audio or the speakerphone enabled. For bluetooth, it gets a code from a getState method. It only prevents the screen from turning off if it equals a specific state. All you have to do is force it to always be true.
You can also put this in the build.prop to completely disable it.
Code:
gsm.proximity.enable=false
Click to expand...
Click to collapse
I m a nerd....how i do this ? where i write this code in my htc desire?
Thanks

1. you need to be rooted (if your on this forum and running miui you already are rooted) and have ES File Explorer downloaded from market.
2. open es file explorer and press menu then settings scroll all the way to the bottom and go to root options & turn on root explorer & mount file system
3. go back to the view of your sd card now on the top left there is a image of sd card click that. look for a folder named system and click there
4. in system scroll to bottom and look for a file called build.prop long press on this file and click copy now click the house at top left and paste the build.prop to your sd card
5. now go back to the system folder click on build.prop and you will get a selection of apps to pick from depending on what you have installed. pick es note editor
6. now that you in your build.prop scroll down and WHERE i put "gsm.proximity.enable=false" ? i write this code where? in the end? Where?
Thanks

I need Help please
i need help in
http://forum.xda-developers.com/showthread.php?p=15689458#post15689458

Quick fix
I had a similar problem with my phone (Samsung Galaxy S2) when I put it in a waterproof box. The display went black when someone was calling, and it didn't reappear unless I opened the box and thereby deactivated the proximity sensor reading.
My quick fix is to put a piece of black electrical insulating tape over the sensor. Since the sensor basically is a light sensitive receiver looking for tiny reflections from a coded light source, total blackness will be read as "no near object".
But of course, a nice API call would be more elegant

For the love of god, bump!

Bump....seriously.....I've been looking everywhere for a way to disable proximity sensor. I wish Tasker had a simple Disable/Enable toggle on this sensor

Follow the post at the top of this page.
Make a backup of your rom just in case.
In summary, if you have root explorer then here's how I'd do it.
1. Navigate to /system.
2. Click the button at the top that says Mount R/W.
3. Open the file called build.prop.
4. At the bottom of the file add a line that says:
gsm.proximity.enable=false.
5. Hit menu, save and exit, reboot
It should work. If it doesn't you still should be ok. If unsure go ahead and restore your backup.

have the same problem but with incredible s. the screen goes down until on other end some body will not put the phone down! iv trued the false method. it did nothing.

Disabling Proximity Sensor works!
ihtfp69 said:
It does check for a headset plugged in, bluetooth audio or the speakerphone enabled. For bluetooth, it gets a code from a getState method. It only prevents the screen from turning off if it equals a specific state. All you have to do is force it to always be true.
You can also put this in the build.prop to completely disable it.
Code:
gsm.proximity.enable=false
Click to expand...
Click to collapse
For all those who are looking for a solution to a faulty proximity sensor and nothing else works, I can tell you that modifying the build.prop as described does work!
I simply can now press the button to turn the screen on or off while on call instead of relying on faulty sensor. Very pleased.
This was done using HTC WILDFIRE S a510a running HTC Sense GingerBread 2.3.3 which has been rooted with CWM root through CWM custom recovery installed after unlocking the bootloader at the HTCDEV site. The program used was called Rom Toolbox Lite and I used the "build.prop Editor" feature to safely make the modification to the file.

Anyone experiencing this?

Just wanting to see if anyone is experiencing...
1. If you go to the dialer (from the home screen) - my previously called contacts do not populate. Meaning when I go to use the "smart dial" (# pad to find contacts) nothing comes up. This is how I usually call people.. so its quite annoying.
Side note - I can get them to show up, if I tap a single number then hit the back button (not the back capacitive touch button) - the one thats in the dialer.
2.When using the power bar widget (the one that comes with it) every time I click to turn on the GPS I am prompted with a message telling me:
"Be selecting Standalone GPS services, you are enabling access.."
I was certainly not prompted every time with my original incredible. Furthermore, this prompt seems to disrupt the power widget causing the bar underneath to not light up (signifying its on), even though it is.
I have since switched to Power control Plus which fixed the bar not lighting up issue - but am still prompted every-time.

Are you using LauncherPro? I was experiencing the same issue when using the LauncherPro default Phone dock shortcut with the previous call history not showing. I just "re-routed" the phone shortcut to the phone app and all is well.
Hope that helps.

fsiddique said:
Are you using LauncherPro? I was experiencing the same issue when using the LauncherPro default Phone dock shortcut with the previous call history not showing. I just "re-routed" the phone shortcut to the phone app and all is well.
Hope that helps.
Click to expand...
Click to collapse
+1 ... I had the same issue and that trick fixed it.

fsiddique said:
Are you using LauncherPro? I was experiencing the same issue when using the LauncherPro default Phone dock shortcut with the previous call history not showing. I just "re-routed" the phone shortcut to the phone app and all is well.
Hope that helps.
Click to expand...
Click to collapse
Thank you much!!!!!!!!!!! OMGOMOMG

orangedude654 said:
2.When using the power bar widget (the one that comes with it) every time I click to turn on the GPS I am prompted with a message telling me:
"Be selecting Standalone GPS services, you are enabling access.."
I was certainly not prompted every time with my original incredible. Furthermore, this prompt seems to disrupt the power widget causing the bar underneath to not light up (signifying its on), even though it is.
I have since switched to Power control Plus which fixed the bar not lighting up issue - but am still prompted every-time.
Click to expand...
Click to collapse
Any fix for this? Is it present in custom ROMs?

Some CM7 and GO DEV TEAM issues

Have been doing a bit more customising and almost set up properly but still a few hanging issues:
cormie said:
Sometimes when I unlock the phone, the brightness is set differently even though the ambience of where I am is the same, sometimes it could be dim and others bright and it doesn't really change.
Not fixed - CM7 issue
The Email app doesn't appear to be the best. It's very dark, is there any brighter theme available or maybe suggestion of another app for pop3 mail?
Not really an issue - APP Issue
I'm using GO SMS and unfortunately I'm still having an issue sending group messages, I've the option to seperate each message to each person into its own thread, sent a small group text, only to maybe 10 people yesterday and it split it into 4 separate threads, only 4 separate contacts who I sent it to as opposed to the 10, so where did the other 6 go? I couldn't check delivery status or anything.
Not Fixed -Possible App Issue, possible CM7 issue
Also with GO Dialer EX, I assume it's because I've over 1,900 contacts, but it freezes quite a lot if I'm going through my contacts/groups/adding new etc. Also you can't see the individual times of consecutive missed calls from one contact and if you have a missed call notification in the notification bar, clicking the notification used to clear the notification and bring you to the missed call screen, now it just brings you to the missed call screen but you have to go back to the notification menu to "clear" the notification, again, this didn't happen in sense and clicking to see the missed calls also cleared the notification. I also miss being able to just open up the dialer, press call on a blank field and it would call the last dialled, also with the way the call log is, I don't like that it groups the contacts together, I much prefer being able to see a log based on time only. Also by grouping the contacts together, you can't just click on a recent called contact and it will go to phone them immediately as you could with sense.
Not Fixed: App Issue, plus now discovered, if you have 2 missed calls, clear the notification and get 1 more missed call, the notification will come up again but say 3 missed calls
I miss the fact with Sense, you just clicked the clock and you got to your stopwatch/countdown timer/alarm straight away. Is there any way to get this back? Clicking the clock now brings me to a screen that isn't much use.
Fixed: App Issue - Got a separate stopwatch/countdown timer app and use stock alarm and using Go Weather widget
The included Calendar app widget has a few annoyances, you can't click a number to go straight to dialpad with from within an event, only 1 event is displayed in the widget and to go into details of that event you've to click into open the calendar first and then into the event. Again, the sense calendar app was better and you could also scroll through the events from the widget itself.
Fixed - Assigned swipe up and swipe down action to open calendar from home screen, this makes it just as quick as before to open the calendar app and gets right into the app, also I can now just click numbers and it opens the dialer, not sure what the issue was before but it's working grand now
Twitter widget is also worse than it was in sense, it only shows one tweet at a time as opposed to sense which you could again scroll down which is much handier if you're looking for say updates from AA Road Watch while stuck in traffic and you can just keep your eyes open for the AA logo on a scroll rather than clicking and clicking and clicking to see if they have any updates.
Not really an issue, I don't even use twitter that much
Calculator is too basic compared to sense one too
Fixed - Real calc
Another thing is I used to like to have "camcorder" shortcut instead of "camera" (I just feel it's better to have instant access to record something rather than photo it). You could easily then switch to camera if you want to photo something, there was no camcorder shortcut so I downloaded one, but it opens only the camcorder alone, as opposed to the same thing that you got when clicking the camera, in which you could easy switch between camera and camcorder. Any way to start that same thing, but just in camcorder mode by a shortcut?
Not really an issue, added camera and camcorder shortcut to home screens
Can someone also tell me if the CM7 "File manager" does the same as Astro? I installed Astro before realising there was a file manager there, guess there's no need for both so can I uninstall astro again? I'm only a very basic user that would be copying/pasting and installing apps via astro, so if this can all be done via file manager, I'll just get rid of Astro
Not really an issue, seems astro is better though, you can select multi select files in a folder to edit.move etc and just looks to be more options in general.
Click to expand...
Click to collapse
A few more issues then using Go Dev Team apps:
on froyo, I had handscent and loved the way if I got a text, the led would be a permanent blue until I read it. I checked this option in go sms too but it doesn't seem to be working at all. I tried flash on at 300ms and then off at 0, I also tried at 300/300 and it didn't seem to flash at all.
Have also noticed a bug in go sms where a different contact name could appear in someone elses text, which happened before with Handscent on froyo, was hoping it would have been fixed. I wonder is it go, or a bug with android itself that's causing this.
Hoping I can sort the above not fixed issues so any advice would be appreciated, the LED notification thing is a strange one, just doesn't seem to work at all for go sms but it may be something conflicting with the CM7 settings or stock settings? Any feedback appreciated!

cormie said:
Have been doing a bit more customising and almost set up properly but still a few hanging issues:
A few more issues then using Go Dev Team apps:
on froyo, I had handscent and loved the way if I got a text, the led would be a permanent blue until I read it. I checked this option in go sms too but it doesn't seem to be working at all. I tried flash on at 300ms and then off at 0, I also tried at 300/300 and it didn't seem to flash at all.
Have also noticed a bug in go sms where a different contact name could appear in someone elses text, which happened before with Handscent on froyo, was hoping it would have been fixed. I wonder is it go, or a bug with android itself that's causing this.
Hoping I can sort the above not fixed issues so any advice would be appreciated, the LED notification thing is a strange one, just doesn't seem to work at all for go sms but it may be something conflicting with the CM7 settings or stock settings? Any feedback appreciated!
Click to expand...
Click to collapse
Note & Thanks

Not sure what your reply means, are you on the dev team for go/cm7 or something? If so, have plenty of suggestions and bugs to report

[Q] Navigation doesn't do text to speech anymore

I have a rooted and stock rom Galaxy nexus running the latest Android Version 4.2.2 the phone when ever I turn on the navigation the device no longer tells me to turn onto whatever the street name it just tells me "turn right, turn left etc" How do I get this issue resolved?
Thanks

Tap the button that mutes/un-mutes voice navigation, make sure its un-muted and turn up your MEDIA volume (not your ringer volume).

jsgraphicart said:
Tap the button that mutes/un-mutes voice navigation, make sure its un-muted and turn up your MEDIA volume (not your ringer volume).
Click to expand...
Click to collapse
Yea its not that it doesnt make any noise it does it speaks but instead of doing text to speech it just gives me basic navigation like turn right or turn left not a complete tts I've read somewhere that I need to re-install the language pack but im not sure how to do that

urmab501 said:
Yea its not that it doesnt make any noise it does it speaks but instead of doing text to speech it just gives me basic navigation like turn right or turn left not a complete tts I've read somewhere that I need to re-install the language pack but im not sure how to do that
Click to expand...
Click to collapse
bump, none else have this issue ?

urmab501 said:
bump, none else have this issue ?
Click to expand...
Click to collapse
when I've had Nav just say take a right instead of the actual street/route name, I found if you go and delete the data associated with Google Maps in Settings/Apps it will correct the problem. right after I flashed to CM 10.1 from CM 10.0, mine did have this problem and I cleared data on the maps and then made sure to have the most recent maps from Play and all was well.

Can't see full screen in Google Maps

Is anyone else having the issue of their on screen nav buttons cutting off part of the google maps screen? When I'm navigating I can't see the ETA section or hit the 'X' to close navigation. Really annoying. I'm wondering if it's a maps app issue or possibly the ROM I'm using somehow. I'm on the latest ICE custom ROM. Also, it might be related, but when the pop up asking which app i want to use for various options pops up (ie when I click a number to call it asks if I want to use phone or skype) I can't click on the 'Just Once' or 'Always' option because it makes me hit the nav keys (even though I am hitting the 'Always' selection). Thanks for any help.