Wizard Keyboard Lighting - 8125, K-JAM, P4300, MDA Vario General

is there a way to have the Keyboard Light come on when the device is opened?
I find it aggrevating that I must press a key first!

I second that

I third it.

I fourth it....

yeah thats pretty god damn true actualyl when your in cinema and trying to txt when u open it you have to press two buttons, (a letter to lite it up) then another to delete that letter before u can start to reply, gay !

who is the one!
does anyone have ideas heres a thought
it should be triggered with the screen rotation

Haha, this is one of the most annoying things about the wizard.
I hate that "feature" and I also hate that the backlight goes out after a second or two on the keyboard if you don't push a key.

Lol, I second that one too!

I'm sure it would be possible to make an application that simulated keypresses on the slide out keyboard, but only whilst it was open (could be detected by looking is the screen was in landscape mode or portrait mode)
Should be simple enough to make, but i've not learnt enough at university yet to tackle such a problem, maybe next summer

it should not be triggered by app simulating keypress with screen rotation or upon opening it should be executed in same manner as screen rotation.

brins0: have you tried simulating a keypress by using the onscreen keyboard? Doesn't work.
The keyboard backlight is not stimulated by non hardware keypresses (at least on the Hermes)
V

jeffbar1 said:
it should not be triggered by app simulating keypress with screen rotation or upon opening it should be executed in same manner as screen rotation.
Click to expand...
Click to collapse
Actually, looking into it further, there arn't actually any keys you could "press" that wouldn't result in an action on-screen. You may be able to trick the hardware into thinking you pressed a key (by possibly creating a virtual hardware key (if that is even possible)), which would make the keys light up.
Are the keyboard lights controlled by the hardware itself, or does Windows have some mention in the lighting status?

The keyboard backlight timer is all hardware controlled.
This means there is no way to change it's crappy 5 second time out, and no way to control it from within software.
Yes, it sucks. That is one of my few complaints about this device. The backlight on the keyboard DEFINATELY needs to be configurable.

vijay555 said:
brins0: have you tried simulating a keypress by using the onscreen keyboard? Doesn't work.
The keyboard backlight is not stimulated by non hardware keypresses (at least on the Hermes)
V
Click to expand...
Click to collapse
I understand what you mean, but I think you mis-understand what i'm suggesting. The drivers for the keyboard should have something similar to a key status. If you make the status for a peticular key "pressed" or whatever, it's effectively fooling the driver into thinking the key has been pressed, hence the keys would illuminate. (I don't fully understand how the hardware works, not being an expert in this feild, and considering each new model differs (sometimes quite heavilly))

GldRush98 said:
The keyboard backlight timer is all hardware controlled.
This means there is no way to change it's crappy 5 second time out, and no way to control it from within software.
Yes, it sucks. That is one of my few complaints about this device. The backlight on the keyboard DEFINATELY needs to be configurable.
Click to expand...
Click to collapse
Yeah, I gathered this was the case...
I wonder if a physical modification of the hardware would allow it to be changed... Any volunteers
Elsewise, it is impossible...

brins0 said:
Yeah, I gathered this was the case...
I wonder if a physical modification of the hardware would allow it to be changed... Any volunteers
Elsewise, it is impossible...
Click to expand...
Click to collapse
Any electrical diagrams of the keyboards interface? lol

Why not just have it trigger upon landscape activation?

I too would like to see the keyboard light come on when landscape is activated, and stay on until landscape is de-activated

h00ligan said:
Why not just have it trigger upon landscape activation?
Click to expand...
Click to collapse
This is what we are suggesting, but this is not possible as the keyboard lights are controlled by the hardware, not by windows, so we can't really trigger them in such a way.
Unless you are willing to physically modify your hardware, it is NOT possible to make the keyboard lights activate upon sliding the keyboard open, and most likely never will be with this device, and most likely others too...

Hmm.
I know it's a stretch, but hit the delete key?
Or hit a menu key twice.

Related

X1 Manual now online!

X1 manual is now online.
At first I was alarmed - no button for switching UI orientation between portrait and landscape! But then I looked a little more and I see you can assign a button to perform that function.
Otherwise reasonably obvious WinMo stuff...
The attached zip needs the file extension to .rar in order to extract it - its the manual for your viewing pleasure.
But then I looked a little more and I see you can assign a button to perform that function.
Click to expand...
Click to collapse
can u tell me where did you find that in the manual?
*edit*
I've found it.
NZtechfreak said:
At first I was alarmed - no button for switching UI orientation between portrait and landscape! But then I looked a little more and I see you can assign a button to perform that function.
Click to expand...
Click to collapse
Oh hooray... You can do the same thing on a Tilt. That's quite disappointing, that a phone of this caliber can't even set something up where you can rotate the screen out of the box, you need to remap one of the buttons to do it.
Black93300ZX said:
Oh hooray... You can do the same thing on a Tilt. That's quite disappointing, that a phone of this caliber can't even set something up where you can rotate the screen out of the box, you need to remap one of the buttons to do it.
Click to expand...
Click to collapse
That is called customization. lol...
samy.3660 said:
That is called customization. lol...
Click to expand...
Click to collapse
Exactly, so screen rotation isn't standard, it needs to be customized on a phone that's almost into the triple digits of cost (USD). That's not called customization, that's called pathetic.
yep, pathetic
nap007 said:
yep, pathetic
Click to expand...
Click to collapse
Why is this pathetic? They have given you a way to customise a button for this purpose. If you want it, its there, if you don't need it, it doesn't get in your way.
I think you just want to have that dedicated button to justify your purpose. Now THAT is pathetic.
^ so you joined here
now ask yourself, why did Samsung, HTC Apple and even Nokia give accelerometers to their device (which some people even found they're annoying)? why not just a customizable button like you said?
now ask yourself is there any reasonable reason why SE put away the button that was supposed to be screen orientation button?
and the damn on screen keyboard, gosh, I'm speechless...
What is the light sensor for?? Maybe it can act as a function to rotate the screen(like what it did for n82).... but this is not seen in the video demostration.
@nap007, I've been lurking here for some time already, but joined in just to reply to your comment.
Adding a feature as a marketing gimmick is one thing. The accelerometer is not really that useful in its current implementation. I do applaud SE's decision to make the screen rotation customisable to any softkey, as opposed to having a dedicated button of limited use.
nap007 said:
^ so you joined here
now ask yourself, why did Samsung, HTC Apple and even Nokia give accelerometers to their device (which some people even found they're annoying)? why not just a customizable button like you said?
now ask yourself is there any reasonable reason why SE put away the button that was supposed to be screen orientation button?
and the damn on screen keyboard, gosh, I'm speechless...
Click to expand...
Click to collapse
You ALSO been here ONLY for a couple of weeks. People here are inerested in the Xperia, and looking for info or help.
If you think is pathetic, what is your decision? Are you getting something else? I don't understand why you hang around here, instead to welcome new people and contribute, you discharge your personal frustrations.
.
gvino said:
What is the light sensor for?? Maybe it can act as a function to rotate the screen(like what it did for n82).... but this is not seen in the video demostration.
Click to expand...
Click to collapse
Welcome gvino you are in right place.
Xperia has 4 lcd lights one in every corner. You can set each one to alert you for up to 12 different event.
That's cool. Very nice touch from SE.
Pinguino1 said:
You ALSO been here ONLY for a couple of weeks. People here are inerested in the Xperia, and looking for info or help.
If you think is pathetic, what is your decision? Are you getting something else? I don't understand why you hang around here, instead to welcome new people and contribute, you discharge your personal frustrations.
.
Click to expand...
Click to collapse
funny how you didn't say anything to BLACK93300ZX, as I was only agreed with him
I didnt know it had a built in stylus...Excellent!
The problem as I see it is that the actual button is gone; which button are we supposed to assign our custom request to? Panels? Call end? There are no frigging buttons to assign anything to!
bloob said:
@nap007, I've been lurking here for some time already, but joined in just to reply to your comment.
Adding a feature as a marketing gimmick is one thing. The accelerometer is not really that useful in its current implementation. I do applaud SE's decision to make the screen rotation customisable to any softkey, as opposed to having a dedicated button of limited use.
Click to expand...
Click to collapse
mkent_barbados said:
The problem as I see it is that the actual button is gone; which button are we supposed to assign our custom request to? Panels? Call end? There are no frigging buttons to assign anything to!
Click to expand...
Click to collapse
Exactly! There should be a specific key that one could program for this. Customization is good, but a specific button should be there.
In the latest prototype models there was usually a Funciton Key mentioned on the left side of the device. Maybe this manual does not mention that 'cos it was written before that decision or something? It does say "This is a DRAFT publication". Let's hope that this is the case.
As shown in the manual, there are 2 softkeys, labelled as Selection Keys, immediately below the screen, one on the left and other on the right. As far as I can see, these softkeys are not specifically assigned to any particular functions.
One could say that these softkeys could correspond to options show on screen immediately above, but you could just press the options on the screen anyway, so quite redundant in this premise.
Thus, these 2 softkeys can be permanently assigned to function as the screen rotation button, if you so desire. SE may well even default one of these softkeys to be the screen rotation button for production units.
The manual we have now is not yet complete, and we'll have to see the production one to see for sure.
I really don't see what's the problem and fuss here.
nap007 said:
funny how you didn't say anything to BLACK93300ZX, as I was only agreed with him
Click to expand...
Click to collapse
Ok nap007, is your opinion and you have the right to it. But don't tell me to go after everyone on this site. Friends?
I got news about the FCC TEST REPORT.
the USA version was approved and the 3G bands is 1900.
AT&T people should be happy.
https://fjallfoss.fcc.gov/prod/oet/forms/blobs/retrieve.cgi?attachment_id=1011331&native_or_pdf=pdf
bloob said:
As shown in the manual, there are 2 softkeys, labelled as Selection Keys, immediately below the screen, one on the left and other on the right. As far as I can see, these softkeys are not specifically assigned to any particular functions.
One could say that these softkeys could correspond to options show on screen immediately above, but you could just press the options on the screen anyway, so quite redundant in this premise.
Thus, these 2 softkeys can be permanently assigned to function as the screen rotation button, if you so desire. SE may well even default one of these softkeys to be the screen rotation button for production units.
The manual we have now is not yet complete, and we'll have to see the production one to see for sure.
I really don't see what's the problem and fuss here.
Click to expand...
Click to collapse
YEAH, I am sure I saw a youtube video where the person very clearly puts the finger at the bottom to rotate the screen. At the time I thought if was a touch on the screen, now I believe it was the left soft key.
Yes, that video is of Magnus himself doing a demo for journalists. He did press the left-side softkey to rotate the screen, because someone asked him whether you could rotate the screen without opening the keyboard. Well, there you have it.

[APP][Updated 16-10-2008]CapacitiveFingerLock (Proof of Concept with sources)

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

Multi-touch Keyboard

We all know that multitouch is capable on the popular G1 and myTouch. Now I was wondering if adding such a feature onto the virtual keyboard is a can-do. All for the sake of exponentially increasing text insertion speed.
I don't see a reason to use multitouch for text input. What should happen if you enter 2 keys at the same time?
MarcLandis said:
I don't see a reason to use multitouch for text input. What should happen if you enter 2 keys at the same time?
Click to expand...
Click to collapse
the point of multi-touch on the vk is to increase the speed of texting meaning u can press a key directly after another without fear of the keys not registering. it really helps when holding the phone sideways because when text i start texting too fast and keys dont register correctly. thats y im still partial to the hard keyboard.
MarcLandis said:
I don't see a reason to use multitouch for text input. What should happen if you enter 2 keys at the same time?
Click to expand...
Click to collapse
The reason for multi-touch is simple... take a look at the iPhone, if you hit one key and then before releasing it hit another it registers both hits. So that way you can type much quicker! Try this on the android/htc/better keyboards and you'll see that if you hit two keys at the same time, it will register a key that is almost always half-way in between the two.
However, I think Google is having a hard-time coding for not simultaneous taps but for timing. Meaning that if you hit both the 'K' and the 'N' keys at the same time while trying to type the word 'KNOW', the software not only has to recognize that 2 keys were hit; but has to resolve which one was hit first or was likely meant to be hit first. So that way, it can say
"hey, he hit the 'K' and the 'N' at virtually the same time; BUT, because he hit the 'K' .00002 seconds before the 'N' I'll put register and display the 'K' before the 'N'"
Multi-touch in the browser is probably not easy to code for but it certainly is much easier than the keyboard because pinching only requires the software to recognize that two fingers are on the screen, not that one was there before the other.
But, I think Google needs to work on the usability of the keyboard first. The screen-size on the magic and keyboard might restrict them somewhat but damn the virtual keyboard layout is verry bad... I always hit the "M" key when trying to hit the "DELETE" key.. And why not auto-popup the keyboard when you enter messaging? and why is there the "smiley" key in messaging? WASTE OF SPACE?!?
I thought the HTC keyboard sorta-of had multi-touch support, no?
How does one "sorta" have multi-touch support?
I would love to see this. My biggest problem is not registering a space in between words because I hit it too quickly and then the autocorrect can't fix the issue. Maybe a 3rd party keyboard developer would be interested in incorporating this into their app?
I believe better keyboard has multi touch.
exile20 said:
I believe better keyboard has multi touch.
Click to expand...
Click to collapse
It does not, unfortunately.
TonyDeez said:
How does one "sorta" have multi-touch support?
Click to expand...
Click to collapse
I think I only got it working with the bottom row of keys.
I can't fathom how one would get the Dream/Magic (G1/myTouch3G) to have a fully functional multitouch keyboard. The multitouch capacity of these devices is hackish to say the least; if the horizontal or vertical coordinates of the touched points coincide to within a rather wide range (comparatively speaking) then the device is incapable of registering more than one touch -- and it wouldn't necessarily be /either/ of the points originally touched.
That would seem to me to be a game-breaker.
Unless I misunderstand? Perhaps the Droid or Cliq are different.
IConrad01 said:
The multitouch capacity of these devices is hackish to say the least; if the horizontal or vertical coordinates of the touched points coincide to within a rather wide range (comparatively speaking) then the device is incapable of registering more than one touch -- and it wouldn't necessarily be /either/ of the points originally touched.
Click to expand...
Click to collapse
Reading this got me curious so I went back to Luke Hutchison's blog posts on the matter and played around with his multitouch demo apps here and it looks like there are indeed problems. I then found this post which explains his observations on the matter.
Even with these limitations, though, it's hard to say if there would be much of an issue. I think this "rather wide range" you speak of is small enough. The QWERTY keyboard layout was designed to spread out keys to minimize "jams" of neighboring keys. This works in our favor, making the distance between possible close-to-simultaneous keypresses rather large on average. If I play with the virtual keyboard a little bit, I notice that if my fingers are hitting neighboring keys I don't have problems with simultaneous presses because I have to move my first finger out of the way to make room for the second. I do have unusually large fingers, but give it a try yourself.
Who knows though...it may indeed be too inaccurate.
Also, it looks like there's a similar thread to this one over here.
The trouble, as I understand it, is that you could not touch two points on the same horizontal "read" line of the device, at the same time. You could probably do top row and bottom row as multitouch, but not middle row and anything else. (Assuming three rows total.)
It's not just about touching two keys simultaneously but that if the same capacitors are triggered horizontally, then the device will read this as one -- confused -- input. And if the same capacitors are triggered horizontally, the same will occur.
It is my understanding that the Motorola Milestone's Eclair keyboard is multi-touch. Can anyone confirm that?
i can conform that there is a multi-touch keyboard. Ive actually tested it out. They rebuild the keyboard and made capable of it. I think its called HTC VK keyboard. And yes i can press 2 keys at the same time too.
I have a t mobile Touch pro 2, love the keyboard but i would rather go back to android. Its almost new if anyone is interested let me know in a pm. thanks.
If I'm not mistaken, the HTC Keyboard on the hero has multitouch.
ajones7279 said:
If I'm not mistaken, the HTC Keyboard on the hero has multitouch.
Click to expand...
Click to collapse
sorry but you are mistaken. the hero does not even have real multitouch in the driver. one finger gives a small dot, while a second finger would increase the dot size that is reported from the driver, the bigger the distance between fingers the bigger the dot size. this way the pinch-to-zoom works, but it does not actually detect a second touch.
you can see this with various application that show the touch graphically, for example cracked screen or steamy window.
Then I stand corrected. Just relaying something I heard. But doesn't mulititouch have to be written into the program? Like how Picsay had multitouch on the Droid whereas other apps didn't? Just throwing things out there.
kendong2 said:
sorry but you are mistaken. the hero does not even have real multitouch in the driver. one finger gives a small dot, while a second finger would increase the dot size that is reported from the driver, the bigger the distance between fingers the bigger the dot size. this way the pinch-to-zoom works, but it does not actually detect a second touch.
you can see this with various application that show the touch graphically, for example cracked screen or steamy window.
Click to expand...
Click to collapse
Dunno about the Hero, but the Eris definitely does have it.
Also- multitouch DOES have to be coded into the application. The driver isn't important at all if the application itself only supports one input.
Interesting new tweet by cyanogen:
@paracycle multitouch is built into keyboardview on eclair. i've backported this for the next CM-4.2 release.
Click to expand...
Click to collapse

change Button LEDs

Hi there,
can anyone explain me how to get access to the control of the "Button LEDs"?
I know there must be a way because in Android those LEDs are glowing for example when you touch a button. At WM they only glow if you PRESS a button or touch the scroll wheel.
Thank you in advance
+1 here, that would be a nice option too
OK, what exactly do you all want? Buttons that light up on touch? is that all?
I'm brainstorming on ideas for my next version of X-Sense, so.... be creative!
Cheers
shirreer said:
OK, what exactly do you all want? Buttons that light up on touch? is that all?
I'm brainstorming on ideas for my next version of X-Sense, so.... be creative!
Cheers
Click to expand...
Click to collapse
That would be a first step. The default settings (light up all LEDs on button press or on scroll wheel touch) is just stupid.
The next step could be something like use the sensors on the buttons as extra buttons or use the LEDs as indicatiors for diffrent stuff. The scroll wheel for example seems to have 3 or more diffrent LEDs as Backlight. This could be used to indicate the battery status.
shirreer said:
OK, what exactly do you all want? Buttons that light up on touch? is that all?
I'm brainstorming on ideas for my next version of X-Sense, so.... be creative!
Cheers
Click to expand...
Click to collapse
Customizable options for the so the lights can follow your touch when scrolling ?
Not practical but it would look good
But how could we interact with the sensors?
I dont think they land somewhere in the message queue of windows mobil. I think we have to rewrite the driver which is responsible for them. But maybe I'm wrong, because I don't have a lot of experience with the windows Mobil API. I prefer managed code like C#.
As far as I understand, the center of the dpad is the only part of the hardware that has the capability of sensing when you touch it. The only way you are gonna get the other buttons to respond is with a button press unless you modify the hardware.
try the latest version of xdandroid. if u thouch for example the back key, it glows.
so, no. every button has a sensor on it
Just so we're all on the same page, the entire area below the screen is a touchpad, it is sensitive to touch & motion - there is an app that implements this very nicely as both a touchpad and touch launcher/Task Mgr. My xsense app already interacts with button lights to show several events (i.e. stylus out, volume profiles).
freaksey said:
try the latest version of xdandroid. if u thouch for example the back key, it glows.
so, no. every button has a sensor on it
Click to expand...
Click to collapse
shirreer said:
Just so we're all on the same page, the entire area below the screen is a touchpad, it is sensitive to touch & motion - there is an app that implements this very nicely as both a touchpad and touch launcher/Task Mgr. My xsense app already interacts with button lights to show several events (i.e. stylus out, volume profiles).
Click to expand...
Click to collapse
OK Sorry! I have the cdma diamond on sprint so I didn't know the other versions(gsm) had touch sensative buttons! My d-pad is that way but the others are not. Forgive my ignorance.
Y'all should check this app out; I'm not in league with the developer, but I recognize his talent on this one. Its an amazing app that does all of the above and more - and there's a trial version:
http://mobilesrc.com/gscroll2.aspx
this app looks nice.
Is anyone out their who can explain me how to catch the events of button-touch area?
freaksey said:
this app looks nice.
Is anyone out their who can explain me how to catch the events of button-touch area?
Click to expand...
Click to collapse
Google for Koushik's sensors.dll library; it comes with sample apps etc...
in his libary is only a event for the rotation of the scroll wheel...
touch lock pro
As I know, app called "Touch lock pro" can do some settings with the ring LED's, so this can be the way

How could I disable hardware keyboard while it's open and use software keyboard?

I know some of you might think this is a stupid question. I would like to use any on screen keyboard while the hardware keyboard is open and disable hw kb until I want to use it. Let me see if I can explain this to you why.
I am starting to like typing in landscape mode with on screen keyboard. I am getting pretty good at it and definitely think my speed is faster that way than a hardware keyboard. Have any of you tried typing in landscape for any extended length of time? I don't know about you but my fingers really start cramping and hurting because I have to hold the phone with the rest of my hands and fingers while typing with my thumbs. When the hw kb is open, this could give me more area to hold the phone a little more comfortably while using a fast software keyboard. My thumbs wouldn't be at funky downward angles to hit the keys, they would be extended straighter and upwards and might be less prone to getting crampt up and carpel tunnel.
Am I crazy to think this might be useful? Has anyone heard of it being done or an app or hack that could achieve what I'm trying to do?
I do understand where you are coming from, having big hands and fingers can suck sometimes, but I don't think its possible. I've tried to see if I could pull up the virtual landscape keyboard with the hw one open but no luck.
Sent from my PG06100 using XDA App
Why'd you get the Shift and not the Evo if you would prefer an on-screen keyboard?
cosine83 said:
Why'd you get the Shift and not the Evo if you would prefer an on-screen keyboard?
Click to expand...
Click to collapse
I'm not complaining or whining, I'm just asking for help with something that I might like to do.
to answer your question, yes, it is possible.
i just tested this on skyfire, ebuddy, and gmail. if you simply leave the keyboard in, aka don't slide the screen, and rotate the device, the screen will turn and whatever app you are using will also turn (if it supports it). then just click in the text box you want to type in again, and the onscreen keyboard will come up. I'm using better keyboard atm, so didn't test it with the HTC or any others. but i'm fairly positive that if it works with that one, it'll throw up whichever keyboard you are currently using in the same situation.
viperv303 said:
to answer your question, yes, it is possible.
i just tested this on skyfire, ebuddy, and gmail. if you simply leave the keyboard in, aka don't slide the screen, and rotate the device, the screen will turn and whatever app you are using will also turn (if it supports it). then just click in the text box you want to type in again, and the onscreen keyboard will come up. I'm using better keyboard atm, so didn't test it with the HTC or any others. but i'm fairly positive that if it works with that one, it'll throw up whichever keyboard you are currently using in the same situation.
Click to expand...
Click to collapse
I think you missed what he was trying to say. he was asking if it's possible to use the on-screen keyboard with the physical keyboard open.
OP, here's an android tip (it works with any android phone): if you hold down the menu button with your cursor in a text field, it forces the on-screen keyboard to come up. You could try selecting a text field, then holding down the menu button.
viperv303 said:
to answer your question, yes, it is possible.
i just tested this on skyfire, ebuddy, and gmail. if you simply leave the keyboard in, aka don't slide the screen, and rotate the device, the screen will turn and whatever app you are using will also turn (if it supports it). then just click in the text box you want to type in again, and the onscreen keyboard will come up. I'm using better keyboard atm, so didn't test it with the HTC or any others. but i'm fairly positive that if it works with that one, it'll throw up whichever keyboard you are currently using in the same situation.
Click to expand...
Click to collapse
I know about what you are explaining, that's normal usage. What I'm interested in is using the open physical keyboard as additional area to hold the phone with while in landscape and using the on screen keyboard. I'm thinking there needs to be something to trick the phone into thinking the keyboard drawer is closed when it's actually open.
It seems, as usual, that I am coming up with lame brain ideas and haven't a clue as how to making them happen. I emailed one keyboard dev a few days ago and haven't heard anything back yet. I guess I could shoot out emails to all the devs of the keyboards I have bought and see if I get a response.
SirRipo said:
I think you missed what he was trying to say. he was asking if it's possible to use the on-screen keyboard with the physical keyboard open.
OP, here's an android tip (it works with any android phone): if you hold down the menu button with your cursor in a text field, it forces the on-screen keyboard to come up. You could try selecting a text field, then holding down the menu button.
Click to expand...
Click to collapse
I just tried that with the drawer open and it is not working. I tried switching to the stock keyboard too and still nothing. Thanks for the suggestion.
herbthehammer said:
I just tried that with the drawer open and it is not working. I tried switching to the stock keyboard too and still nothing. Thanks for the suggestion.
Click to expand...
Click to collapse
Same issue here, The flex or ribbon cable from heyboard to PCB is broken, so my device is perm on landscape and I can't use any onscreen keyboards.
wickedpenguin said:
Same issue here, The flex or ribbon cable from heyboard to PCB is broken, so my device is perm on landscape and I can't use any onscreen keyboards.
Click to expand...
Click to collapse
Damn dude! That really sucks. You have insurance? Can you take it to a repair center?
wickedpenguin said:
Same issue here, The flex or ribbon cable from heyboard to PCB is broken, so my device is perm on landscape and I can't use any onscreen keyboards.
Click to expand...
Click to collapse
correct me if I'm wrong, but isn't there a 1-year warranty on manufacturing defects, regardless of insurance standing or the 30-day return policy? Certainly sounds like a manufacturing defect to me, unless it's broken from misuse
this isnt the place for talking about warantee issues. start a different thread. this is about answering the question in this thread.
have you tried any other keyboards from the market or like the swype beta or anything? idk if it would make a difference. i doubt you can disable it while its open. if you want to use the soft keyboard close the phone? Its probably best practice to keep the phone closed when you arent using the hardware keyboard anyways?
t0esh0es said:
this isnt the place for talking about warantee issues. start a different thread. this is about answering the question in this thread.
Click to expand...
Click to collapse
and I was pointing out a potential fix for someone with an issue in this thread, try to keep up.
Looks like smart keyboard pro has that feature. Its buried in the advanced menu.
Yes sir it is I just downloaded the trial to give it a shot one thing I notice is when you open the keyboard on the home screen they keyboard pops up over all your icons I'm gonna play with the settings somemore and see what I can do about it
*EDIT* if you are on a text box and hit home the keyboard don't open over home screen but if you just open the phone to put it into landscape on the homescreen they beyboard will pop up just hit the search button then back and you have your whole home screen
herbthehammer said:
Looks like smart keyboard pro has that feature. Its buried in the advanced menu.
Click to expand...
Click to collapse
Sent from my PG06100 using XDA Premium App

Categories

Resources