Database Info

Raphael Issues List:

Right, I can't see an Issues list for this device yet so I'll start one:
1. A couple of times now, I've left my phone to charge overnight and woke up to an unresponsive device. Power button does nothing, screen is off and only way to get it device back up and running is to poke the soft-reset button OR remove and reinsert the battery.
2. Unresponsive buttons: every now and then the "right" button of the D-Pad does nothing, then suddenly it will start working again, same with the "Back" button though much more infrequent/noticable than the D-Pad issue I've experienced.

I did not expierence the first problem with the charging issue.
To close and app you can use the (arrow pointing left) key but sometimes i have to push it like 3 or 4 times before it respond.
Same with the touchscreen but i fixed that by increasing the touchpad sensitivity with a regedit.

My device has reset a few times while I been reading email or texts.
John

Guys. The whole phone besides the keyboard is touch sensitive. So the whole front keys and touchscreen. Increase sensitivity and it should work fine.

Kraize92 said:
Guys. The whole phone besides the keyboard is touch sensitive. So the whole front keys and touchscreen. Increase sensitivity and it should work fine.
Click to expand...
Click to collapse
Erm, I'm sorry but that's not right is it. The D-Pad, Send, End, Home and Back buttons are actual buttons as opposed to touch sensitive.
The zoom wheel is obviously a "touch" area too. The issue I am descriping seems to suggest that the switches might be a bit flakey rather than anything else.

no he is right all the buttons are PRESSURE (he said touch) sensitive..when they unvieled the diamond the ceo of htc demonstrated that the keys are pressure sensitie and even the cameria button can SENSE when your finger is approaching to ready the zoom ..here is the youtube vid
http://www.youtube.com/watch?v=YTd3SUPSJsMit

pazookie said:
no he is right all the buttons are PRESSURE (he said touch) sensitive..when they unvieled the diamond the ceo of htc demonstrated that the keys are pressure sensitie and even the cameria button can SENSE when your finger is approaching to ready the zoom ..here is the youtube vid
http://www.youtube.com/watch?v=YTd3SUPSJsMit
Click to expand...
Click to collapse
Sorry my bad. WM phones used to be called touch sensitve but in reality they're pressure sensitive. The only touch sensitive phones out currently are the iPhones and the Omni I would say.
Syphon Filter said:
Erm, I'm sorry but that's not right is it. The D-Pad, Send, End, Home and Back buttons are actual buttons as opposed to touch sensitive.
The zoom wheel is obviously a "touch" area too. The issue I am descriping seems to suggest that the switches might be a bit flakey rather than anything else.
Click to expand...
Click to collapse
If the were actual buttons they would be capable of being pushed in which it's not possible to do

Issues:
HTC task man doesnt work properly.
Poor reception
Too many startup apps/services put on by htc to provide touch interface (which i hate)
why on eart you use operaloder on phones stratup just to get 2-3 more seconds fast load time for opera.
i think htc just over done this touch crap.
could anoyone access setupfiles on rom so i can use plain wm6.1

Kraize92 said:
If the were actual buttons they would be capable of being pushed in which it's not possible to do
Click to expand...
Click to collapse
Hang on, you clearly don't own either Touch Pro or a Diamond, the D-Pad, Call, End, Home and Back buttons CAN BE PUSHED IN. They are actual buttons.

Syphon Filter said:
Hang on, you clearly don't own either Touch Pro or a Diamond, the D-Pad, Call, End, Home and Back buttons CAN BE PUSHED IN. They are actual buttons.
Click to expand...
Click to collapse
No. I'm sure of it. I have demoed both a touch pro and a diamond. I meant that they CANNOT be pushed in as you can on the kaiser. I know this for a fact and on every video you will see that it is mentioned as a pressure sensitive all around except for the keyboard. I'm sure of that. They are not real buttons. I guess you could push it in if it's just a piece of glass and paper underneath the actual pressure sensitive touchpad, but it wouldn't make it real buttons. I know what I'm talking about Unless HTC suddenly decided to make them real buttons which would kill their profits so I'm assuming that they wouldn't do that either. I demoed it about 2-3 weeks ago.

Syphon Filter said:
Right, I can't see an Issues list for this device yet so I'll start one:
1. A couple of times now, I've left my phone to charge overnight and woke up to an unresponsive device. Power button does nothing, screen is off and only way to get it device back up and running is to poke the soft-reset button OR remove and reinsert the battery.
2. Unresponsive buttons: every now and then the "right" button of the D-Pad does nothing, then suddenly it will start working again, same with the "Back" button though much more infrequent/noticable than the D-Pad issue I've experienced.
Click to expand...
Click to collapse
1 - Not had that problem - hopefully that'll go after your next hard reset or ROM update - these damn things always have, and always will behave differently for different people, it seems!
2 - My Back button missed my press once or twice, but I think it's more of a hardware issue than a software issue though (or possibly user error!). I'll tell you now though, hitting the "Right" button on my Diamond was next to impossible. It was extremely stiff, and would eventually register as a press on the "Hang Up" button. Drove me absolutely mental! But I think I was the only Diamond user who had that problem, and my Raphael is fine.

having got one in my hand - they are tactile push bottons - i.e you push them until it clicks before an action happens.

ardsar said:
having got one in my hand - they are tactile push bottons - i.e you push them until it clicks before an action happens.
Click to expand...
Click to collapse
Then I must be crazy. Since all I have to do is touch the button and a action happens. But my pressure threshold is very high.

Kraize92 said:
No. I'm sure of it. I have demoed both a touch pro and a diamond. I meant that they CANNOT be pushed in as you can on the kaiser. I know this for a fact and on every video you will see that it is mentioned as a pressure sensitive all around except for the keyboard. I'm sure of that. They are not real buttons. I guess you could push it in if it's just a piece of glass and paper underneath the actual pressure sensitive touchpad, but it wouldn't make it real buttons. I know what I'm talking about Unless HTC suddenly decided to make them real buttons which would kill their profits so I'm assuming that they wouldn't do that either. I demoed it about 2-3 weeks ago.
Click to expand...
Click to collapse
I'm not going to get into an argument over this but the 9 buttons (Home, Back, Call, End, Up, Down, Left, Right and the centre of the D-Pad) on the face of the Diamond and the Touch Pro are buttons which have a tactile feedback, a press will not register until you "feel" the button pressed. The only thing in that area that is a "touch sensitive" thing is the zoom wheel.
Just because the area looks flush does not mean they are not buttons. There's a single piece of material that covers that area but I can assure you there are individual switches under there that provide a tactile feedback. You HAVE to feel that feedback for the button to do anything, simply touching it will have no effect unless you are using the zoom wheel functionality.
If you believe anything else you are wrong.

Kraize92 said:
Then I must be crazy. Since all I have to do is touch the button and a action happens. But my pressure threshold is very high.
Click to expand...
Click to collapse
1. What do you mean "my pressure threshold is very high"? Are you talking about the registry settings?
2. I thought you didnt have a Touch Pro or Diamond?

I said I didn't own one. Doesn't mean I don't have one in hand right now I have family members and friends that work for HTC america and AT&T.
Yeah. Registry settings/Advance Config for diamond

Kraize92 said:
I said I didn't own one. Doesn't mean I don't have one in hand right now I have family members and friends that work for HTC america and AT&T.
Yeah. Registry settings/Advance Config for diamond
Click to expand...
Click to collapse
Yes. Ok.
Anyway, so you're saying that device you have in your hand right now has no tactile feedback on the front face buttons?
If have insiders at HTC why did you ask for donations so you could get a Touch Pro in the other thread?

Syphon Filter said:
Yes. Ok.
Anyway, so you're saying that device you have in your hand right now has no tactile feedback on the front face buttons?
Click to expand...
Click to collapse
EDIT: Okay. Maybe I'm mistaken. It's only the d-pad that's pressure sensitive. The buttons are tactile even though they feel as if they are pressure sensitive because I don't push into it like I did with the front face buttons on my kaiser.

ah, you've seen the light. The button DOES push in but the panel is one solid "sheet" that covers all the buttons.
The "wheel" is the only touch sensitive bit. The 5 navigation functions of the d-pad (up down left right select) are all tactile buttons that work off little switches.

Syphon Filter said:
ah, you've seen the light. The button DOES push in but the panel is one solid "sheet" that covers all the buttons.
Click to expand...
Click to collapse
Actually. I should show you the light I'm right.
[Link]
Click number 3 and read this caption: "Swipe your finger across the screen to scroll through contracts, zoom, and pan web pages, browse your music library, and more, or press the touch-sensitive buttons to navigate and control your phone."
So concluding to that original fact that I was indeed right

The touchpro "D-Pad"

Apologies if this has been thoroughly covered, I went back 4-5 pages in each forum but didn't see anything.
From what I can gather from reviews and youtube videos the D-pad on the Touch pro works like a standard D-pad, and when in opera can be used to zoom in by circling it with a finger like a click wheel on an Ipod. Is it possible to modify it to work as a scroll wheel instead of a "zoom wheel". I know this isn't an option out of the box, but is it something that's possible, or being worked on?
I'm considering from the tilt, and while I've convinced myself that I don't need the hard left and right buttons, or the email & browser buttons, I'm not sure I'll be able to get used to working without any kind of jog dial/scroll wheel.

I think it's been asked and the answer is not yet.
The D-pad is one of the things I really don't like about the phone though, the buttons are all on the same plane, not separated in any way, and that makes it very difficult to differentiate the d-pad from the home/back/send/end buttons. I didn't find it was a problem until playing games, when I kept minimizing the window by hitting the Back button.

oh... the touch pro has a d-pad??? omg ive had the phone for almost a month and i only just discovered it. i thought it was just a scroll thing. its really hard to press though..

Black93300ZX said:
I think it's been asked and the answer is not yet.
The D-pad is one of the things I really don't like about the phone though, the buttons are all on the same plane, not separated in any way, and that makes it very difficult to differentiate the d-pad from the home/back/send/end buttons. I didn't find it was a problem until playing games, when I kept minimizing the window by hitting the Back button.
Click to expand...
Click to collapse
Well I don't really play a whole lot of games on my phone, but I do read a lot of really long email threads, and more importantly, when I'm bored I read sites like overheardinnewyork.com which is basically a lot of text to scroll through.
I'm getting the feeling that I'm going to have to find a way to "play" with a TP and see if I love it or not. I went 8125, x01ht, tilt, and now I'm looking to upgrade. but if this phone isn't going to rock me, I'll hold out (for what I don't know).
As much as I like flashing new roms to my tilt, it seems all anyone does is try to rip the best features from other phones...so at some point I might as well just get the other phone.

Diamond Tweak 0.5.3 allows you to enable d-pad scrolling for some applications.
http://forum.xda-developers.com/showthread.php?t=409540
(you need to soft-reset after you have changed options)

dougalls said:
Diamond Tweak 0.5.3 allows you to enable d-pad scrolling for some applications.
http://forum.xda-developers.com/showthread.php?t=409540
(you need to soft-reset after you have changed options)
Click to expand...
Click to collapse
Hmmm, looks promising. Have you tried it? I just can't imagine I'd ever use the zoom feature, although up to now I've used opera mini, so perhaps after switching to opera mobile I'd change my mind. But I'm still pretty sure I'd prefer to double tap the screen to zoom, and have another means of scrolling.

I have tried it and it works well for contacts (useful), programs etc but does not work with my Yahoo inbox (possibly due to the ROM I am using - ROmeOS v1.22) and it does not replace the zoom in opera. You can set up custom applications in DiamondTweak so it may be possible to overcome any differences between ROM's by setting up a custom application. I do use the zoom in opera so wouldn't want to replace it.
You can still double tap to zoom in/out on opera, as well as the wheel - the wheel lets you zoom in/out in small increments, double tapping toggles between full page and zoomed in.

DesCo said:
Hmmm, looks promising. Have you tried it? I just can't imagine I'd ever use the zoom feature, although up to now I've used opera mini, so perhaps after switching to opera mobile I'd change my mind. But I'm still pretty sure I'd prefer to double tap the screen to zoom, and have another means of scrolling.
Click to expand...
Click to collapse
Think about this, with Opera Mobile you'll only have 2 levels of zoom ("in" or "out") unless you use the wheel to zoom. I liked being able to use it to fine tune and get things to look just right, but that's me. Try it out and see what you think.

With newer versions of Opera Mobile, there is now an on-screen zoom slider that adds a "tap and slide" button for incremental zooming. Now I find myself wanting an alternative to scrolling, since my finger otherwise covers up part of the screen and might accidentally click a link. Unfortunately the arrows and dpad don't scroll the page but instead jump from link to link.
This has been one detail (although a minor detail) that has made be begin to consider replacing my TP with the X1, since the X1's optical sensor dpad apparently provides scrolling functionality.

DesCo said:
Hmmm, looks promising. Have you tried it? I just can't imagine I'd ever use the zoom feature, although up to now I've used opera mini, so perhaps after switching to opera mobile I'd change my mind. But I'm still pretty sure I'd prefer to double tap the screen to zoom, and have another means of scrolling.
Click to expand...
Click to collapse
use advance config 3.3 ........search for the link
go to options, click smart touch and it allows you to add any application, where in touch wheel (above D Pad) can be used for scrolling......i use it for contacts, file manager, program, call history, phone window, mails, messages and its really usefull and very cool........i dont use it for opera and internet explorer and use it for zooming as put in default
~
Kingjack

Thanks for the info. As I said, I haven't picked up the TP yet, I'm holding out for the Fuze (or a reasonably priced GSM model).
To change gears a bit, I'm curious, what kind of difference do people see in using cooked Roms on this device. I only ask because as a Kaiser user I'm used to using Roms because they incorporate features from the latest equipment. But as this is among the newest models out, and a "flagship" phone so to speak...is there much of an advantage over say a stock ATT rom minus the bloat? I enjoy high level of customization, and being able to pick my features, but as this is a relatively new device, I don't want to go through the trouble of unlocking and flashing if there isn't going to be a real gain in performance/features, or if it's going to impact performance (like trying to run Manilla 2d on a Kaiser, and pretending that a 5 second screen rotate time is ok)
PS: just for the record, despite my incredibly low post count, I've been lurking on the board for ~2 years...I'm not some (I hate this word) newb asking "what rom is best" or "can someone explain to me how to XXX reading the Wiki is too much work"...just wanted to throw that out there.

Volume buttons for scroll
Review on wmexperts of Sprint Touch Pro has the information below in the comments area. Looks like the reviewer followed up with the statement that he used AE Buttons to remap the volume buttons on the side, where the scroll wheel is on 8525/Tilt to scroll up and down with each click. I don't have Fuze, but it seems like this would work on it as well, I don't think it's a free softare though.
http://www.wmexperts.com/reviews/smartphones/review_24_hours_with_the_sprin.html
Buttons: I have successfully used AE Buttons to successfully remap the volume up and down buttons. I have the volume down button set at one click to scroll down and a log click for OK/Enter. The volume up button is set at one to scroll up and the log click Alt/Tab Wisbar's switch utility. I have also remapped the Back button to OK/Enter. The Home button now brings down the Start Menu on a single click and Email when I hold it down. This has made life a lot easier and has in virtually increased my available hardware buttons to a more comfortable level of usable buttons.

cparkhorn said:
Review on wmexperts of Sprint Touch Pro has the information below in the comments area. Looks like the reviewer followed up with the statement that he used AE Buttons to remap the volume buttons on the side, where the scroll wheel is on 8525/Tilt to scroll up and down with each click. I don't have Fuze, but it seems like this would work on it as well, I don't think it's a free softare though.
http://www.wmexperts.com/reviews/smartphones/review_24_hours_with_the_sprin.html
Buttons: I have successfully used AE Buttons to successfully remap the volume up and down buttons. I have the volume down button set at one click to scroll down and a log click for OK/Enter. The volume up button is set at one to scroll up and the log click Alt/Tab Wisbar's switch utility. I have also remapped the Back button to OK/Enter. The Home button now brings down the Start Menu on a single click and Email when I hold it down. This has made life a lot easier and has in virtually increased my available hardware buttons to a more comfortable level of usable buttons.
Click to expand...
Click to collapse
How have you managed to get AEButton working on your home button?
I found that the home and back buttons seem to be "hard coded" to do their tasks, and AEbutton only assigns an *additional* task to each button. In other words, when I press Home for start menu, it first goes home, and then opens start. If I map the back button to Camera, it first goes back an application screen, then launches camera. Very annoying. The only buttons I found AEButton works with is the vol up and down. Is there a trick I'm missing?

Android 3-DOF Controller App

Hello guys. I've just released my app's source code as well as a short video at:
http://androidcontroller.googlecode.com/
--necessary improvements list--
on the Android side:
* service discovery so that the client and the server can find each other on the local network (it's very annoying having to manualy enter an IP address in a textfield that's why I change the source code every time and compile with the new ip )
* kalman (or some other kind of) filtering to smooth the sensor output
* improve menus/configuration/interface
* look for a marker and calibrate automaticaly
on the windows side:
* switch model you're rotating somehow (ability to load models via xaml files?)
* interact with the object (I'm already transmitting the touch screen's x/y event)
* smooth the sensor data on the windows side to take the load off the android app
* sounds
* transmit images to display on android or sounds?
I would appreciate VERY much ANY help that anybody could provide. If you are interested in contributing code please contact me and I will add you to the project members list.

Well Done !
congrats

HES A JUBEH IMPOSTER
Just kidding, awesome app btw

wow...this is pretty cool. I would love to help but due to my lack of knowledge in this. Keep up the good work!!

Great work, I'd love to see how this develops.
Starred in google code.

Everybody thanks for the encouraging remarks

re
Génial___$$$$$$$$

Draw custom buttons to the touch screen which send keyboard commands to windows, and implement gamepad support for the sensors? Then this could be used as an input device for a computer.

bjehsus said:
Draw custom buttons to the touch screen which send keyboard commands to windows, and implement gamepad support for the sensors? Then this could be used as an input device for a computer.
Click to expand...
Click to collapse
But if I do that then the touch screen becomes just another gamepad, and a bad one for that matter since touch screens have no tactile feedback (i.e. the finger is not aware of wether it has pushed the button or not). Tactile feedback could be implemented via vibration or perhaps even audio feedback with sound for button press but both those scenarios are impractical for a gaming situation where buttons are being pressed at a frantic pace.
Besides I wanna do more than just pushing buttons. Something with touching/swiping gestures etc. Transmitting data from the pc to the mobile device, or sounds? ooor.. dunno^^
I need some good ideas on what more one could do with this ^_^

I'd be more than happy to help, unfortunately the most I can do for you is clean up images and menu buttons. If you need any of that done feel free to hit me up.

woah
This is really cool. Are there any real apps available yet?

henrynhl said:
This is really cool. Are there any real apps available yet?
Click to expand...
Click to collapse
Plx define 'real' apps.

Actually this is a great idea, I'm surprised no one had thought of it yet.
Blender (open source 3d suite) supports NDOF devices nowadays - I'll see about giving this a try when I get a chance, and perhaps contribute some code (and we'd need a linux server as well, which shouldn't be too big of a deal)

Jubei said:
But if I do that then the touch screen becomes just another gamepad, and a bad one for that matter since touch screens have no tactile feedback (i.e. the finger is not aware of wether it has pushed the button or not). Tactile feedback could be implemented via vibration or perhaps even audio feedback with sound for button press but both those scenarios are impractical for a gaming situation where buttons are being pressed at a frantic pace.
Besides I wanna do more than just pushing buttons. Something with touching/swiping gestures etc. Transmitting data from the pc to the mobile device, or sounds? ooor.. dunno^^
I need some good ideas on what more one could do with this ^_^
Click to expand...
Click to collapse
I have an idea, heh...use it to control the mouse on a PC.
There are remotes that work using accelerometers and such...by tilting the remote up, it moves the mouse arrow on the screen up, left goes left, etc. Then simply have the screen react to a short tap(which would be a single click), double tap (which would be a double click), and a long press (for right click).
That is certainly something that I would use on a daily basis.

jmhecker said:
I have an idea, heh...use it to control the mouse on a PC.
Click to expand...
Click to collapse
Thanks for your feedback jmhecker! Do you mean like a wiimote? If so then unfortunately that's not possible with the HTC Dream unless the user performs some kind of calibration process first (because the device has no way of knowing where the monitor is). So first some sort of calibration would be necessary, which could be done by placing a marker/qr code on the monitor then pointing the camera OR just pointing the device to the middle of the screen and pressing a button (which is what i"m doing now to calibrate).
Jubei

Jubei said:
Thanks for your feedback jmhecker! Do you mean like a wiimote? If so then unfortunately that's not possible with the HTC Dream unless the user performs some kind of calibration process first (because the device has no way of knowing where the monitor is). So first some sort of calibration would be necessary, which could be done by placing a marker/qr code on the monitor then pointing the camera OR just pointing the device to the middle of the screen and pressing a button (which is what i"m doing now to calibrate).
Jubei
Click to expand...
Click to collapse
Kind of like that, yes. But, not exactly.
Basically, the phone knows when it is in 'zero' position. IE: lying flat on its back.
Now, I tilt the phone (rotate) to the left a smidge, so it look like / (when looking at it if it were in front of you...what oyu see is the bottom (where the plug is) of the phone. Now, when you tilt it like that, the mouse cursor moves left. Then when you turn it like \, it moves right...tilt the phone forward, it moves down, and tilt it backwards, and it moves up.
Kind of what you have being done already with the video and the plane in it...but, rather than move the plane, move the mouse cursor.
Does that make sense?

This with remote droid...
jmhecker said:
Kind of like that, yes. But, not exactly.
Basically, the phone knows when it is in 'zero' position. IE: lying flat on its back.
Now, I tilt the phone (rotate) to the left a smidge, so it look like / (when looking at it if it were in front of you...what oyu see is the bottom (where the plug is) of the phone. Now, when you tilt it like that, the mouse cursor moves left. Then when you turn it like \, it moves right...tilt the phone forward, it moves down, and tilt it backwards, and it moves up.
Kind of what you have being done already with the video and the plane in it...but, rather than move the plane, move the mouse cursor.
Does that make sense?
Click to expand...
Click to collapse
I could see this working with RemoteDroid, or something of that nature. Make the tilt like a joystick, and the screen with a touch pad and buttons. That would make a killer game controller

jmhecker said:
Kind of what you have being done already with the video and the plane in it...but, rather than move the plane, move the mouse cursor.
Does that make sense?
Click to expand...
Click to collapse
It does yes. But i think it would require a lot of work to be usable because isometric or isotonic (speed of cursor relative to tilt angle) devices are not nearly as usable as mice. So in the end you'd spend so much hours coding just to have another mouse, whereas I think this device can be more.
it has a speaker, a display, vibration, buttons, keyboard, a trackball, sound. It has a lot of potential to be used just as a simple mouse.

[Q] WP7 Phone App Registry Location

Hello everyone,
I have an unlocked Nokia Lumia 710 running a custom ROM and all in all the phone is good. However, the proximity sensor doesn't seem to work properly (I don't know if the problem is from the custom ROM or from the phone itself but it doesn't really matter) - when I'm in a call I keep pressing the Hold and Mute buttons (no matter how I hold the phone) which makes me really irritated. So I was wondering, there should be registries I guess that make the buttons active when pressed during a phone call. Can someone point me to the correct registries that control if the buttons are active or not when pressed so that I will hopefully be able to completely disable these two buttons (so that when pressed nothing happens)? I don't use them anyways, so completely disabling them would certainly fix my problems. I'm posting in the general WP7 section because I guess the location of these registries would most probably be the same for all phones...
Thanks a lot in advance!

There's a registry value that is updated automatically by the proximity sensor and indicates its current status system-wide, but I doubt you'd want to use it. For one thing, it would almost certainly get immediately reset by the sensor, faulty or otherwise. For another, the Phone app isn't the only thing that uses the proximity sensor; you would end up locking out the touchscreen in some other apps too. Finally, this would also prevent you from pressing the End Call button!
I don't know of a registry value that's specific to the Phone app's use of the proximity sensor. However, even if there is, the first and third reasons above still apply.
I instead recommend that you simply tap the power button when putting the phone up to your ear to talk. This will turn off the touchscreen (and incidentally save power) and you can tap the Power button again to access the Phone app or any other app on the phone when you need them, without interfering with the call.
There may also be a tool in some built-in Manufacturer or Diagnostics app that would let you test and adjust the sensitivity of the proximity sensor. This would perhaps be the best option, but I don't know where or if it exists on a Lumia.

What I want to do is not to play with the proximity sensor itself but rather with the buttons on the screen during a call. I guess I didn't make myself clear enough, sorry about that. The idea is that when I'm in a call, the proximity sensor does not work properly and I always press either the Mute or the Hold buttons. So, these buttons can still appear during a call but when you press them, I don't want anything happening. I mean, the idea is even when the phone is not next to your ear and the screen is active during a call, pressing the buttons to do nothing. I'm just following some simple logic, which might of course be incorrect (or too simple), but I'm thinking that there is most probably a separate registry for each button that controls whether this button does some action when pressed or not. I'm also hoping that they'll be separate registries for each button so that I can, for example, disable the actions for the Hold and Mute buttons, but leave the End Call button active. The problem is that I have no idea where to look for this registry since I'm still new to WP OS.
Heck, it would even be OK for me to completely remove the buttons from the screen during a call (or substitute the current buttons with some 1x1 px transparent images), if that's possible, so if someone knows how to do even that, tell me.
I was also considering using the power button when in call but I first want to see if there is any other way to do what I want. And since I'm not using the Mute and Hold functions at all, I just thought about disabling them.

No, I understood you. I was suggesting the "fix your proximity sensor" option because normally, the problem you're experiencing just doesn't happen; that's what the prox sensor is for. Sometimes it's miscalibrated, though, or something is covering it up (some poorly-cut or installed screen protectors do this, for example).
The "Phone" app isn't a Silverlight app like third-party ones; it's a native EXE that we pretty much can't modify without using a custom ROM. That's going to make changing it the ways you suggest (disabling or resizing certain buttons, etc) quite difficult.
I'm pretty sure you don't want to disable all the buttons always, even if that were possible. For one thing, that would prevent you from hanging up, as I mentioned before. It would also prevent you from dialing any numbers, which would make the use of touch-tone automated services impossible.
The Power button option really seems like the best fit for you. It's easy, doesn't require any hacks, doesn't break any other functionality, and should be the next-best solution beyond actually solving the problem.

I see now, makes sense. In my head it sounded simpler than what it really is. I was considering resizing the buttons because I'm also using iOS and I quite enjoy digging in the OS and changing some elements, so it's possible there to, for example, substitute some buttons with transparent 1x1 px images, etc. But that's irrelevant. Looks like WP is different and I still need some time to get in to it. Anyways, thanks for your help.
P.S. The screen protector was the first thing I "accused" but unfortunately it wasn't causing the problem.

On a custom ROM, you could definitely tweak the Phone app if you wanted to. However, the way WinCE (the kernel behind WP7) works, OS files are almost always marked as "in ROM" which means that the filesystem driver will refuse to modify them while the OS is booted. This makes tempering with the stock OS difficult; we have to find ways to modify the behavior of apps and system features without modifying the apps or features themselves.

[Q] Can the middle button behave like a capacitive button?

Is there any way to set the fingerprint button to behave like a capacitive button? I really just want to dab my finger on it and not have to depress, like the other two keys. I know the scanner registers contact but that click press it's really annoying when I just want the "desktop" etc. I think it would do wonders for the buttons longevity too... This may seem like a minor thing but it would really make the make the whole user interaction thing more standard. Having to big press one of three buttons is odd..

You can get a lot of apps that add "soft buttons" to your screen for things like Home. One that jumps to mind is called Button Savior.
That was my way of saying that, no, I don't think you can use that button without actually "clicking" it.

You could try the app called swype home button, just swype up from the screen just above it and itll take you home.

I completely agree with your desire here OP. Coming from an LG optimus G, I find myself gently tapping the button hoping for home.
As an alternative, I'd recommend the pie launcher app in the play store. No root required unless you want menu button functionality. Makes for a nice, easy to reach one handed set of on screen buttons that are only there when you need them, and you can use it as an app launcher too.

pisanty said:
Is there any way to set the fingerprint button to behave like a capacitive button? I really just want to dab my finger on it and not have to depress, like the other two keys. I know the scanner registers contact but that click press it's really annoying when I just want the "desktop" etc. I think it would do wonders for the buttons longevity too... This may seem like a minor thing but it would really make the make the whole user interaction thing more standard. Having to big press one of three buttons is odd..
Click to expand...
Click to collapse
There has to be a way to do it because of the fingerprint sensor. I'm sure custom kernels soon will have this feature.

Bump any new ideas here?