Related
i have been searching for the iphone touch scroll and media player for the hermes 8525 phone. is there anyone working on this? also is there anyway to make the touch screen to a multi tocuh screen like the iphone.
The multi touch screen is totally different hardware, although it would be cool if there was a way...
delude said:
The multi touch screen is totally different hardware, although it would be cool if there was a way...
Click to expand...
Click to collapse
i thought so but i would think if you hack the dll file maybe there is a way to make it read multi times i dont know i am not an expert on hardware or software hacking.
I thought I heard somewhere that there might be someone working on doing something like that. given hardware constraints, it wouldn't be perfect. It would detect the space between the fingers as being pressed as well (I'm assuming), e.g. if you have fingers on the screen like this:
__........__
|__|.....|__|
it would see this:
_________
|_________|
So it would have to figure out by the shape of it where your fingers really are.
Still, I hope someone does. Multitouch would be very nice...
EDIT: due to the restrictiveness of this forum, just imagine that the periods in my ASCII art above dont exist.
That would be amazing, and something i would definately pay for. Looks like it would be like the drag box on a PC desktop. If you put two fingers on then it could drag things or select the space within.
jackbnymbl said:
I thought I heard somewhere that there might be someone working on doing something like that. given hardware constraints, it wouldn't be perfect. It would detect the space between the fingers as being pressed as well (I'm assuming), e.g. if you have fingers on the screen like this:
__........__
|__|.....|__|
it would see this:
_________
|_________|
So it would have to figure out by the shape of it where your fingers really are.
Still, I hope someone does. Multitouch would be very nice...
EDIT: due to the restrictiveness of this forum, just imagine that the periods in my ASCII art above dont exist.
Click to expand...
Click to collapse
Detecting the space between fingers would only be possible with double touch screens one on top of the other. To simulate it on the present hardware would require low-level programming to continuously scan the screen within milliseconds so that it could detect minute differences of whichever finger came in contact first. It will not detect it if both fingers pressed on the screen at exactly the same time. Theoretically it should be possible to do but that would really slow down the system just to do it that way.
for multi touch, i'm not sure how it would be useful but i was thinking, maybe it somehow "remembers" a first click, then that second click is processed. for example, the iphone zooming feature. a single click, then a second, separate clickanddrag to zoom in and out
Well, many of the features can actually be done without requiring multi touch. For example, as the screen of the phone small enough, you can actually assigning area in the viewing screen to be doing something specific. For example, on my notebook touch pad, I can assign part of the right portion to do a scroll function. Hence, it is possible to implement the dynamic zoom function on a WM (non-multi touch device) by assigning (say) right hand area to do a zooming. It wont be as cool though.
would it still be cooler than a generic scroll bar? i like to think so.
Hey all,
I'm hoping to get the Xperia in a few weeks, and hope to get some emulators installed on there. The two d-pads underneath the screen would be include for most controls, however I don't know if I will be able to use them.
Are they hardwired to perform certain functions (i.e. 'Home' and 'Back') or is it possible that they can be set up on a per-application based so I can use them in games as a controller?
Thanks.
I'm not sure as to which 2 d-pads you were reffering to, but it is surely has a 5 way d-pad and 2 multifunction buttons...about the other buttons (phone call, reject and panels button), I don't think you can re configure it .
Hmmm, on closer inspection (see here!), it would appear that what I thought was two d-pads is actually two sets of two buttons, accompanied by two fake buttons.
Bah.
Thanks for your reply anyway!
btw where did you get that pic?
is it an official pic?
Just Google'd 'xperia' and asked for extra large images. I would guess it's an early promotional image - not a photo.
Wow that is a kick ass picture.
Definetly old though, the X panels button is still with the windows logo.
Having written StylusLock I wanted an additional lock/unlock method. Although StylusLock works great, I wanted some extra features:
* to have it possible to lock and unlock "one handed". The StylusLock approach cannot be done "one handed", e.g. on a bike.
* Also some people do not like to operate with the StylusLock (always).
* The combination with this new CapacitiveFingerLock and existing StylusLock will suit more people.
* And sometimes people will use the Stylus, so they will get the right behaviour depended on the usage pattern
* Still the goal is to let it consume almost no CPU and battery and KISS to operate
I discovered with StylusLock that when the TouchPanel and Hardware keys are locked, still the Zoom function works in e.g. Opera.
You can try yourself, using StylusLock:
1. Start Opera
2. Lock the Touch Diamond or Touch Pro with StylusLock
3. TouchPanel and all hardware keys are locked
4. Try to Zoom in/Zoom out in Opera, this still works with the NavWheel
5. Also the Ok button seems to react
I figured out via Scott Seligman and Koushik Dutta how to programmatically access the Capacative Touchpads. You can read also more here: [REF]Capacitive touchpad apps
So this idea is implemented in CapacativeFingerLock. But I am not using the NavWheel idea, but just uses the Capacative hardware area for locking/unlocking. The idea is again simple and clever. When you softly touch the area where the hardware keys are located (so do not press the keys, just gently touch them), the up/down and position area can be detected. I programmed that when the same area is touched gently 3 times within a second (without touching another area), the lock status is toggled.
I made a proof of concept program (just copy the exe inside the zip file attachment to your phone and just execute it), which shows how it is going to work. Just play around with softly touching the hardware panel, to see what happens.
If am working on integrating CapacativeFingerLock with StylusLock, to have a working "real locking" application. The Proof of Concept program just shows that it is possible.
Reserved for future use
Another one for future use.
very nice concept....now i noticed you posted a link of this thread in the wheel to unlock thread...would there be a way to possibly implement a config tool that lets you choose say, touch 3 times softly, or run your finger around the circle?
Malik05 said:
very nice concept....now i noticed you posted a link of this thread in the wheel to unlock thread...would there be a way to possibly implement a config tool that lets you choose say, touch 3 times softly, or run your finger around the circle?
Click to expand...
Click to collapse
In principle this can be done. But because the NavWheel is also used for other purposes (Zoom In/Out), I have chosen not to use the NavWheel, but the 3 times gently touching. In this way there is no interference with other existing applications.
I'll try that, it seems like no one cares aboyt the capacitive touch pad, it seems like an amazing thing that we've got that is so neglected. I hope to give some positive feedback later, but first I have some rom flashing to play with!
Thanks for the work, there must be so many possible implementations for this, I hope this is just the beginning of something much bigger.
How about a simple tap to launch app?
i went ahead and installed it, and it works very well...Will there be a (pretty) GUI to show that it was unlocked?
Also the diamond does have multi touch on that pad area, which enables a "trace" of the movement of your touch
http://www.youtube.com/watch?v=f3Owgcos_KY
Since the nav sensor wont be so ideal, how about sliding your finger from the top of the pad to the bottom (lets say, place your finger on the back button, and gently moving it down to initiate unlock, with a GUI on the screen following your movement, as you go closer to the bottom, the color changes from lets say, red, to green...with incremental color changes in between)
Instead of 3 taps, why not a swipe between the home and back keys, which seems much more natural.
Surur
surur said:
Instead of 3 taps, why not a swipe between the home and back keys, which seems much more natural.
Surur
Click to expand...
Click to collapse
I imagine it is just harder to implement for a proof of concept.
Personally I think there are enough ways to lock the diamond, whether you swipe the screen or 1cm below it is not a revolution, but if swiping the capacitive touch pad could be made to launch desired apps from selected gestures, that would be a revolution, like dynamo3 or hibernate or even standby. I think a lot of people here would want that over another locking solution. Good will intended!
Just tried it.
This is very cool very very cool
Thanks for time invested in such a cool development.
surur said:
Instead of 3 taps, why not a swipe between the home and back keys, which seems much more natural.
Surur
Click to expand...
Click to collapse
Swiping is not so easy one handed. Touching gently 3 times is much easier one handed, holding your Touch Diamond or Touch Pro firmly and touching with your thumb.
However, I can imagine other sort of applications which can use the swiping for other sort of operations. Both are possible with the programming API I made.
uniqueboy said:
I imagine it is just harder to implement for a proof of concept.
Personally I think there are enough ways to lock the diamond, whether you swipe the screen or 1cm below it is not a revolution, but if swiping the capacitive touch pad could be made to launch desired apps from selected gestures, that would be a revolution, like dynamo3 or hibernate or even standby. I think a lot of people here would want that over another locking solution. Good will intended!
Click to expand...
Click to collapse
I am going to share the source code. I have written it in C#. And others can get ideas and take over some of the source code for their own application. At the end we profit all of it.
ZuinigeRijder said:
I am going to share the source code. I have written it in C#. And others can get ideas and take over some of the source code for their own application. At the end we profit all of it.
Click to expand...
Click to collapse
I like your style, that is the the kind of development attitude that keeps here!
ZuinigeRijder said:
Swiping is not so easy one handed. Touching gently 3 times is much easier one handed, holding your Touch Diamond or Touch Pro firmly and touching with your thumb.
However, I can imagine other sort of applications which can use the swiping for other sort of operations. Both are possible with the programming API I made.
Click to expand...
Click to collapse
If you are open to other ideas, I would love the area from the back to home key to be a scroll bar when the device is in landscape mode. Grabbing the narrow on-screen scroll bar can be tricky, and the Touch Pro lacks the scroll wheel of the HTC Kaiser.
Surur
Have been looking into this myself as well. The only code I found was managed C#. Do you think we can use this in our native C code? Looks promising though!
ZuinigeRijder said:
Having written StylusLock I wanted an additional lock/unlock method. Although StylusLock works great, I wanted some extra features:
* to have it possible to lock and unlock "one handed". The StylusLock approach cannot be done "one handed", e.g. on a bike.
* Also some people do not like to operate with the StylusLock (always).
* The combination with this new CapacitiveFingerLock and existing StylusLock will suit more people.
* And sometimes people will use the Stylus, so they will get the right behaviour depended on the usage pattern
* Still the goal is to let it consume almost no CPU and battery and KISS to operate
I discovered with StylusLock that when the TouchPanel and Hardware keys are locked, still the Zoom function works in e.g. Opera.
You can try yourself, using StylusLock:
1. Start Opera
2. Lock the Touch Diamond or Touch Pro with StylusLock
3. TouchPanel and all hardware keys are locked
4. Try to Zoom in/Zoom out in Opera, this still works with the NavWheel
5. Also the Ok button seems to react
I figured out via Scott Seligman and Koushik Dutta how to programmatically access the Capacative Touchpads. You can read also more here: [REF]Capacitive touchpad apps
So this idea is implemented in CapacativeFingerLock. But I am not using the NavWheel idea, but just uses the Capacative hardware area for locking/unlocking. The idea is again simple and clever. When you softly touch the area where the hardware keys are located (so do not press the keys, just gently touch them), the up/down and position area can be detected. I programmed that when the same area is touched gently 3 times within a second (without touching another area), the lock status is toggled.
I made a proof of concept program (just copy the exe inside the zip file attachment to your phone and just execute it), which shows how it is going to work. Just play around with softly touching the hardware panel, to see what happens.
If am working on integrating CapacativeFingerLock with StylusLock, to have a working "real locking" application. The Proof of Concept program just shows that it is possible.
Click to expand...
Click to collapse
A while ago I posted about the Windows Messages received by the form for capacitive touch events. Is that what you ended up using to figure out where on panel is being touched? Mind posting some code so I can add it to the Sensors assembly?
Great idea. Defienetly it will be my way of locking device. StylusLock works nice but can't be operated by one hand so its useless for me. SensorLock uses battery and i've drop my phone already unlocking it.
surur said:
If you are open to other ideas, I would love the area from the back to home key to be a scroll bar when the device is in landscape mode. Grabbing the narrow on-screen scroll bar can be tricky, and the Touch Pro lacks the scroll wheel of the HTC Kaiser.
Surur
Click to expand...
Click to collapse
This can be surely done, programmatically. But I do not know if you can control the scrolling of other applications. The latter seems to me difficult?
Anyway, when a lot of applications are going to use gestures using the capacative areas, there will be going conflicts (different programs reacting differently on different gestures).
For the locking application I want to made, I see also some different gestures possibilities:
- 3 taps for locking/unlocking
- swipe left to right for Power off
- swipe right to left for starting a configured application
And I am sure I can come up with other gestures and actions....
drvdijk said:
Have been looking into this myself as well. The only code I found was managed C#. Do you think we can use this in our native C code? Looks promising though!
Click to expand...
Click to collapse
Actually I started with C++ and had also a working Proof Of Concept. However, because I am new to Windows Mobile Programming, I also wanted to use C# as next project. I have developed programs in a lot of languages (also in C++ and C#), but I like C# more. And I wanted to do this now for Windows Mobile, to get experience with this. Note that the C# sample is using only .NET 2.0, so you do not need .NET 3.5.
You can find a C++ sensortest program, which was available on Scott's weblog:
http://scottandmichelle.net/scott/cestuff/sensortest.zip
ZuinigeRijder said:
This can be surely done, programmatically. But I do not know if you can control the scrolling of other applications. The latter seems to me difficult?
Click to expand...
Click to collapse
I dont know if you can manipulate the scroll bar of another application directly (though this would be ideal) but at the least maybe a page down keystroke could be sent to the active window.
Surur
It´s been a month since I "upgraded" from Diamond to the X1
Overall I am very pleased with the X1, BUT:
1.- I miss the smooth (flat) screen edges!! Corners are difficult to reach with my thumbs in the X1 because the screen is depressed from the chassis. The diamond's screen was flat with the chassis, thus making it very easy to press/touch icons in the corners
2.- The VOLUME keys should be located at the left, not the right (IMHO)
3.- I miss the circular touch control from the diamond: it let me zoom/pan very fast in excel and opera (circular finger movement around the central button). At least a "jog dial (p800-esque?) would have been nice...
4.- It's easy to press the "panel" button (wrongly) to answer a phone call !!
5.- Having a hardware "back" button was a plus in the diamond
6.- The "power" button is too hidden.
7.- The mini-USB connector is located at the natural left finger position. It should be ergonomically positioned down the phone ??
8.- Regarding the HW keyboard, I miss a couple of extra keys from the TyTN (dedicated CTRL key, windows context menu key, those two "softkeys" up there... etc) and I find the first row of keys too close to the phone body, making it difficult to type in the upper row
9.- Sony's standard panel is cool but dull, TouchFlo 3D was VERY USEFUL and practical... I got so used to doing everything with my THUMBS instead of the stylus...
Anybody else has noticed/missed these hardware/design issues ??
I know this is Sony's FIRST WM PDA phone
Hope any Sony engineer is reading this post
ad 1. We discussed this topic before. A few users are with you opinion and a few users (including me) like the recessed screen because it protects the screen from scratches and I haven't got any problems with pressing anything until now.
ad 2. I never had a phone with the volume keys on the left. I think they are okay where they are. Good to reach, either you hold the phone in the left or the right hand.
ad 3. I don't know the circular touch, but it sounds interesting.
ad 4. What thumbs do you have?
ad 5. The touch button is okay for me. If not, you have the two buttons below the screens to configurate.
ad 6. The power button is perfect, because it wakes up the phone and therefore it has to be hidden. It shall not be pressed unintentional while the phone is in my pocket.
ad 7. Then the phone could not be charged while it is in a carholder. Most carholders are closed on the bottom so I'm very happy with the layout while navigating with the X1.
ad 8. A bigger keyboard would make the writing easier but the phone bigger. It's a good compromise in my opinion. I got used to the keyboard and now writing's very fast.
ad 9. That's a matter of taste, really! Let me quote myself:
The panels are great. With the SE-Panel you have everything you need in one panel -calender, messaging, weather, shortcuts aso...
You don't need to change pages like with the touchflothing. TouchFlo is one of the reasons for me not to buy a HTC phone.
I now have the SE Desktop Panel with everything I need, additionally a fullscreen weather panel if I want to know more about forecast, windspeeds and whatelse, one panel for everything that's multimedia and one panel is for the navigation software TomTom which works great with with the internal GPS
Click to expand...
Click to collapse
Anybody else has noticed/missed these hardware/design issues ??
I know this is Sony's FIRST WM PDA phone
Hope any Sony engineer is reading this post
Click to expand...
Click to collapse
Sorry to say that, but I like these "issues" and, as you can see, I have my reasons. But each user has its own pros and cons so the "perfect" phone is not going to happen
I too moved from a diamond to an x1 nearly a month ago, overall I think i prefer the X1.
my previous windows mobiles all had some kind of hardware keyboard, be that a full qwerty or dialpad,
(SPV c500, C550, C600, HTC wizard, HTC TYTN)
I really struggled at first without the keyboard,
I then got really annoyed with how dirty the diamond touch screen got from typing,
it also got VERY scratched because of the flat touchscreen, which i never experienced with previous phones,
yes the X1 has its little quirks, but I got to say its either equal to or better than any HTC device i know of, even htc never get it 100% right...
cheers
Steve
gtrab said:
1.- I miss the smooth (flat) screen edges!! Corners are difficult to reach with my thumbs in the X1 because the screen is depressed from the chassis. The diamond's screen was flat with the chassis, thus making it very easy to press/touch icons in the corners
Click to expand...
Click to collapse
I've also got no problems with the recesed screen, actually I prefer it like that, gives a "little" more protection.
gtrab said:
2.- The VOLUME keys should be located at the left, not the right (IMHO)
Click to expand...
Click to collapse
That's a matter of taste, anyways, they must be where the camera is, as they allo to zoom (on lower mpix. resolutions)
gtrab said:
3.- I miss the circular touch control from the diamond: it let me zoom/pan very fast in excel and opera (circular finger movement around the central button). At least a "jog dial (p800-esque?) would have been nice...
Click to expand...
Click to collapse
Actually I don't like those "touch" controls that the newer htc's got...
gtrab said:
4.- It's easy to press the "panel" button (wrongly) to answer a phone call !!
Click to expand...
Click to collapse
I've never pressed the panel button when answering...
gtrab said:
5.- Having a hardware "back" button was a plus in the diamond
Click to expand...
Click to collapse
useless...
gtrab said:
6.- The "power" button is too hidden.
Click to expand...
Click to collapse
better... sucks turning on accidentally your phone...
gtrab said:
7.- The mini-USB connector is located at the natural left finger position. It should be ergonomically positioned down the phone ??
Click to expand...
Click to collapse
that's actually better for me...
gtrab said:
8.- Regarding the HW keyboard, I miss a couple of extra keys from the TyTN (dedicated CTRL key, windows context menu key, those two "softkeys" up there... etc) and I find the first row of keys too close to the phone body, making it difficult to type in the upper row
Click to expand...
Click to collapse
yup, ctrl key would be great, but the other ones I don't need them, actually the upper part is in a nice position so is easy to combine keyb+screen
gtrab said:
9.- Sony's standard panel is cool but dull, TouchFlo 3D was VERY USEFUL and practical... I got so used to doing everything with my THUMBS instead of the stylus...
Click to expand...
Click to collapse
Panels sux (actually) just like touchflo.
I've used touchflo in other devices and always end disabling it.
anyways, at least with panels we have a nice facebook one... let's hope more come soon.
10: I always cover the loudspeaker with my fingers while holding the X1. Would have been better position on the back- or downside of the device. But maybe i could just drill a hole....
Ah and
11: First touch resonse works on the Diamond, the X1 just brigthens the screenlight and you have to click again.
1. The screen design on the X1 is better, its too exposed on the Diamond.
2. Not true.
3. I like the joystic on the X1 better than the "wheel"
4. I have mapped my program launcher to the panel button + I dont have fat fingers
5. Not in my opinion, I found it rather useless. HW softkeys are much more usefull
6. No way, its better than in Diamond
7. USB connector is located in little bit weird place, but use your phone on landscape while connected, how does it sit now?
8. What you mean TyTN had CTRL, you mean you had Touch Pro not Diamond or TyTN? CTRL missing from the keyboard is disadvantage. Coming from TP I found the upper row to be close to screen at first, but now I do not experience this problem anymore, probably got used to it
9. I dont even have panels installed, or even TF3D
As you see most of these are just opinions...
One thing you did not mention is the magnetic stylus holder in the Diamond and Touch Pro... But you also did not write any of the pro's that X1 has over those devices...
I had Diamond and Touch Pro and I do prefer X1 over them... Only big thing we are missing is a stable and tweaked rom... Dutty's comingggggggggggggggggggg.....
What people seem to be forgetting is that you couldn't make a phone with a flush screen and a metal housing.
The Diamond / TP does a little vibrate when someone picks up your call, am i right? (I'm not a Diamond user)
That is a VERY handy feature in my opinion. Would've been great if that would be possible on the X1.
I have a Polaris/Touch Cruise/Orbit 02, and also got an X1 a couple of weeks ago. I really miss the scroll wheel from the Polaris as well as the Cube/touchflo. Navigation for me was much simpler. Maybe it's just the usual case of configuring Window Mobile to personal preferences. I've installed HTC Home flike I had on the Polaris and this has made things easier.
I Also find the non-flush keyboard a problem, especially when typing on the screen keyboard. On full qwerty keyboard I find it difficult hitting the keys on the left or right edge of the screen.
I remember when I got the Polaris (after having a Hermes) I had to change settings/software until I was happy with it's operation/navigation. Hopefully, it'll be the same with the X1.
SomeoneSimple said:
The Diamond / TP does a little vibrate when someone picks up your call, am i right? (I'm not a Diamond user)
That is a VERY handy feature in my opinion. Would've been great if that would be possible on the X1.
Click to expand...
Click to collapse
This is a software feature that I would imagine wouldnt be that hard to transfer to X1...
Yes, its a software feature with the Phone application. Should work on any custom ROM with the Blackstonephone - like on mine ...
nurps said:
10: I always cover the loudspeaker with my fingers while holding the X1. Would have been better position on the back- or downside of the device. But maybe i could just drill a hole....
Click to expand...
Click to collapse
UPS I forgot that one !!
That's so true: hold the phone with your left hand and sound mutes (because the speaker hole gets covered)
skycamefalling said:
...ad 9. That's a matter of taste, really! Let me quote myself: "additionally a fullscreen weather panel"...
Click to expand...
Click to collapse
A dedicated weather panel ?? Sounds great. I'm searching for it right now
And yes you're right: matter of taste (and use).
Don't get me wrong: I am writing my oppinions to make this phone EVEN better. As I stated before: I am overall please with the phone, I've have them all ("near" all ) and the Xperia is my best phone ever.
Matter of choices and tastes of course, but I wanted to know if somebody shared my thoughts about that minor "issues".
Regarding panels, I think it is a fresh new idea with great potential.
1.- A "camera" panel would be OK (how about a panel that turns your phone into a full Sony Cybershot digicam?? )
2.- A GPS panel would be OK too
3.- More customization options for the strandard Sony panels would be even better !!
I would have preferred the screen flat too, it doesn't need more protection as I keep it in a soft pouch. Besides I find overall its LESS protected as the dirt that gets stuck in the recessed screen is more likely to get wiped across the surface repeatedly before you actually get it removed. It also makes the grease buildup extremely hard to clean off.
My other gripe is the keyboard. I had wished the whole phone had been a little bit wider so that they keyboard was more like my Wizard. Sure you get used to the screen being so close to the top row but it does slow you down. When I go back to my Wizard I can ALWAYS type easier and quicker because the keyboard is more spaced out.
The rest listed are none issues for me. I may even like the panels in the end as I am going to play with the SDK.
haha the funny thing is that the x1 is made by HTC
What's so funny about that?
There has always been a difference between one HTC device and another. In all other respects the Wizard was rather underpowered compared to other HTC devices at the time and it was/is rather chunky. Also technically I own a T-Mobile MDA Vario, its just from visiting these forums I learnt about updating the ROM to WM6 and that its a HTC Wizard (WIZA200 actually) in a T-Mobile branded shell.
backslash225 said:
haha the funny thing is that the x1 is made by HTC
Click to expand...
Click to collapse
The X1 has been designed by sony ericsson, build in cooperation with htc and produce by htc.
so it's not a made by htc . Sony got an idea and ask one of the most experienced winmo company to make it. And they are not so pleased with htc they have stopped their partnership with them. Seems they reproach htc to have underpowered x1 software and got a lot of production problem with them.
I was using a HTC tornado, after long used hardware keys start giving problems. I thought a fully touch phone with no depending on hardkey is my future solution and Android is more or like iPhone or more better. So, I choose this Tattoo small and beauty Android phone.
But why it is so much depending on this 'back' and 'menu' hardkeys for its operation???? Why the android developing team did not include some other alternative?? like some gestures or small icons??
I hope they consider this case in future releases.
thacen said:
I was using a HTC tornado, after long used hardware keys start giving problems. I thought a fully touch phone with no depending on hardkey is my future solution and Android is more or like iPhone or more better. So, I choose this Tattoo small and beauty Android phone.
But why it is so much depending on this 'back' and 'menu' hardkeys for its operation???? Why the android developing team did not include some other alternative?? like some gestures or small icons??
I hope they consider this case in future releases.
Click to expand...
Click to collapse
Because, how would you press a home icon when the appilication has frozen, and also, why not have buttons to accept/reject calls instead of pressing buttons on the screen (like the iPhone)?
I'm sure you can figure it out...
Ill have to agree with thacen on this one. I hade an artemis which in the long run had hard buttons problems. Only thing that made it still useable was that winmo doesnt depend on hard buttons. I think the android people should think about that. Im not saying the buttons should be eliminated, as coburn said they are useful. But we should have an alternative with not using the hard buttons, even if this means soft reset the device when an app freeze if the home hard button does not work anymore.
Actually, I think Android has a feature like the iPhone built-in. If someone is calling you and you get "Incoming Call", try tapping the grey box that has the android in it. It may work.
Euh I have onscreen answer/reject buttons dont you? ... we were mostly refering to closing apps etc. There is basically no onscreen close buttons.