Does anybody know how to change the HW keyboard on a Fuze with an unlocked Touch Pro keyboard? Here is a website selling the HW Keyboard:
http://www.gsm4world.us/shop/touch-raphael-inner-keyboard-p-2161.html
i would imagine you would start at the screws under the door, look around in GOOGLE though, because im also interested in this
PROS--TAB, CTRL, etc buttons
CONS--no windows button, i like how the numbers are arranged on the fuze keypad.
things to think about here.
let us know about your findings, this will also void your warranty
Don't quote me on this but I'm *fairly* certain that there is *no* disassembly required to change the keyboard... If it's like my Tilt was (and I believe it is, from looking at the replacement picture) there is absolutely no need to remove anything... The replacement keyboard has a self-adhesive backing to it and is in several layers. You have to *carefully* peal away the old keyboard (don't worry if you lose a few buttons off the old one - you're pitching it anyhow) and make sure you get *all* layers (including the last black rubber layer that's sticky). You'll know you're all the way done when you're looking at bare circuit board with a bunch of little circle looking things. Peal off the backing on the new one, install, done. I'm pretty sure. But not certain.
mybikegoes200 said:
Don't quote me on this but I'm *fairly* certain that there is *no* disassembly required to change the keyboard... If it's like my Tilt was (and I believe it is, from looking at the replacement picture) there is absolutely no need to remove anything... The replacement keyboard has a self-adhesive backing to it and is in several layers. You have to *carefully* peal away the old keyboard (don't worry if you lose a few buttons off the old one - you're pitching it anyhow) and make sure you get *all* layers (including the last black rubber layer that's sticky). You'll know you're all the way done when you're looking at bare circuit board with a bunch of little circle looking things. Peal off the backing on the new one, install, done. I'm pretty sure. But not certain.
Click to expand...
Click to collapse
While that would work for an identical keyboard, we need to remove those sensor points you were trying to describe. Otherwise the keys will be different, but the actions will remain the same.
I'm sure the keys can be changed via a simple cab as they are not hard set.
D3TH METAL said:
I'm sure the keys can be changed via a simple cab as they are not hard set.
Click to expand...
Click to collapse
I am not just talking about software remapping...I am talking about Hardware remapping seeing as though the Fuze and Unlocked Touch Pro have 2 different keyboard layout.
I'm going to be as gentle as possible...
The circuit board beneath the keys is *IDENTICAL*. Additionally, the key location, size, and placement is *IDENTICAL*. That said, it should be a mere matter of replacing the keyPAD (that is the little plastic keys that are attached to several layers of rubber and self-adhesive) and using a different key mapping via Advanced Config or some similar tool.
gramsey1911 said:
I am not just talking about software remapping...I am talking about Hardware remapping seeing as though the Fuze and Unlocked Touch Pro have 2 different keyboard layout.
Click to expand...
Click to collapse
Yeah. That can be done via a registry change of 1 number It has the different layout because of that registry edit. It's no different hardware wise.
i mean its a really cool idea.. but compare the TP keyboard to the FUZE keyboard. i honestly think it is better. better shortcuts, they can be remapped using xcsdm's button mod.. and a start button to =] plus, just the basic FN>(shortcut) like what im saying is there are more symbols on he HW keyboard, you dont have to hit FN> Space to aquire some basic symbols that you have right there instead.
and btw i remapped my CAPS button on my fuze to become CTRL, seeing there is no use for CAPS (or TAB a that matter) since you can just hit shift twice and it does the same... kind of retarded on at&t's part in my opinion.. i dont think they added a ctrl button because theyre trying to dumb-down america. haha just my theory
EDIT
..then again, im just rambling.. because i still think it would be cool to have the stock keypad.. do IT gramsey!!! I WANNA SEE
I'm interested in this also. Can't stand not having a tab and control key.
If anybody makes this change, do post pics and install instructions.
I tried looking around for "peeling" off the keyboard but couldn't find any.
im pretty sure the buttons pop off, just like on a laptop
The link for the hardware Touch pro keyboard is in post 1. I stumbled upon it looking for extra parts for the fuze/touch pro.
@everyone
I ordered it and I should have it in a couple of days...I will post pics when I get it done
modem_man said:
I'm interested in this also. Can't stand not having a tab and control key.
If anybody makes this change, do post pics and install instructions.
I tried looking around for "peeling" off the keyboard but couldn't find any.
Click to expand...
Click to collapse
Alright..
well i got it.
its a little bit more technical than you might think. you need to void the warranty for this.
look
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
it looks to me like you need to take it apart and put it in holes in little nipples (hehe ) inside the phones housing
So is it possible to just peel of the fuze keyboard and replace it with the TP keybord without taking off the adhesive.
zachthemaster said:
Alright..
well i got it.
its a little bit more technical than you might think. you need to void the warranty for this.
look
it looks to me like you need to take it apart and put it in holes in little nipples (hehe ) inside the phones housing
Click to expand...
Click to collapse
no, i think the little holes insert into the housing and then they close into eachother
Zacht....thanks for the pics.
Guess I'll wait until the warranty ends on the phone before I attempt it.
If you decide to go ahead and change it out, do post your experience and the difficulty level for changing the keyboard.
Thanks.
i might be getting a touch pro soon so if i do ill do it =]
maybe someone else could give it a shot?
Any idea if this might work with the Verizon HTC Touch Pro? VZW, in their infinite wizdom, has put an arrow inbetween the N amd M keys.
I'm looking at a photo of the VZW phone, and it doesn't look like it has as many buttons. For example the top row is 1234567890. There's no - or =, as appear in the photo of the potential replacement.
Fingers crossed.
I could be wrong but the Verizon TP only has 48 keys, while ATT, Sprint, Alltel versions have 57 keys. That is another thing that those smartguys at Verizon screwed up with their version of the Touch Pro.
gramsey1911 said:
I could be wrong but the Verizon TP only has 48 keys, while ATT, Sprint, Alltel versions have 57 keys. That is another thing that those smartguys at Verizon screwed up with their version of the Touch Pro.
Click to expand...
Click to collapse
There's definitely fewer keys. The question is if under the keyboard if the electronics are the same. If they are, might a replacement keyboard work after doing registry edits to remap the keys?
I can't imagine this is the case, but I guy can hope...
If there are only 10 keys across the top, but the other carriers have 12, I'd think that the contact points on the electronics must be different, but who knows.
Related
[01/25/2009] PocketCM Contacts 0.29 - Finger Friendly Contact Application
Hi all,
I've release PocketCM Contacts 0.29, feel free to test, comment, etc...
I made a new thread, because the old one isn't really manageable anymore, and this version is a big rewrite of lot of stuff, so I expect a few regression issue.
Theme for 0.18 and before will not work correctly with this version, you need 0.29 theme
Support for SMS forwarding
Support for sending SMS to multiple contact at once
Better VGA support: more usable, react better to the finger, improved Black and Dream theme
Big speed improvment on animation (looks nice on VGA now)
Speed optimization for all text rendering (smoother than ever)
Various fix and improvements
Faster SMS loading
Improved theme developer mode: read here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As always, you can get it here: www.pocketcm.com.
Also, PocketCM Contact is available for free for personal use, in order to support me, you can make a donation. I thank everybody who already made a donation, and you can thank them too: PocketCM Contact is free.
Hi
Just loaded it up, changed it to the black skin, which i like best. Seems to run great, haven't run into any problems yet. Very nice work, mate.
One think i did notise is, that when I go into a contact, the "Back" is missing the right side of the "B". Just the vertical part. No biggie, but still guess it's not suppose to be like that.
Keep up the great work.
Flemming
this is truly the best tool ever for pdas. thanks a million times for your hard work.
Great update you're doing a great job.
Loading times is better than 0.15, which is a great improvement.
IMHO - the only thing missing is a keyboard easy to find a contact, and the best one I could find is the one found in FingerFriendlyFriends program. I truly love that keyboard. Implementing it in PocketCM would make it simply perfect.
Keep up the awesome work!!
CABless Installation
Guys, how do I do this ?
(Sorry found it on the website)
KamaL said:
Great update you're doing a great job.
Loading times is better than 0.15, which is a great improvement.
IMHO - the only thing missing is a keyboard easy to find a contact, and the best one I could find is the one found in FingerFriendlyFriends program. I truly love that keyboard. Implementing it in PocketCM would make it simply perfect.
Keep up the awesome work!!
Click to expand...
Click to collapse
Why do you need a keyboard when all you have to do is slide your finger down the side of the screen to get the alphabet bar, it doesn't get much easier than that!
Install from a zip: copy the files
Filtering with keyboard: click on phone (bottom right) and you can filter easily
great job.
Few messages are missing, for instance when you want to delete a contact.
Tene, I love the start-up time now, it has dramatically decreased. My only quirks: It seems like the scrolling feature has a delay, I will flick and it will stall a second and then it will scroll very fast. It doesnt seem as smooth as iContact. Also, when pushing the favorites tab I think the word favorites should change to All after it is pressed because pressing it again leads back to all the contacts. When you used to have buttons the filter used to change to the all contacts button after you press it, why does it not when its just words? overall great though, good work Tene
spencepu3 said:
Why do you need a keyboard when all you have to do is slide your finger down the side of the screen to get the alphabet bar, it doesn't get much easier than that!
Click to expand...
Click to collapse
Did u try it?? it 1000 times easier to use that keyboard than scrolling with your finger, at least that's my opinion.
And since there's already a keyboard why not use a better one
KamaL said:
Did u try it?? it 1000 times easier to use that keyboard than scrolling with your finger, at least that's my opinion.
And since there's already a keyboard why not use a better one
Click to expand...
Click to collapse
Yes I have tried it and I do like it as well. However it does take up a good amount of screen real estate and for this reason I would rather not see it implemented.
Thanks .... Very Good Job But Still have the bug when I press and hold phone .... its minimize by it self and i can not press close button... why !!! idon not know
do i need to uninstall 0.15 first?
much better than previous version on the athena. runs fast now and very good. only quirk is it seems the animation for the filter is slow though on vga and lags. seems like sms animation lags a bit too. but much better than previous versions
Ive only noticed one bug, when using the the side scroll to go to contacts by letter, if i try to scroll all the way down to the end of my contacts, it does the bounce animation and half the screen (left) shows the end of my contact list and the other half (right) shows the beginning of my contact list starting at "A"
I dont have any "X", "Y", or "Z" contacts in my phone either so i dont know if that helps
thanks for making such an amazing piece of software.
Can we use the themes we made for the previous version, or do we have to start from scratch?
Love the app by the way!!
Wow.. loading time is nice now. I like it a lot (black theme). Looks much cleaner and more crisp.
Nice improvement!
Same buggies as already said in the topic, when using side scroll (a/z) and I select the z the screen seems to break up a bit. Also don't have Z in my phonebook.
And yeah, the B of 'Back' is a bit too far to the left, but that seems more like a skinning thingy.
Other than that it's working great so far!
syrguy1969 said:
Can we use the themes we made for the previous version, or do we have to start from scratch?
Love the app by the way!!
Click to expand...
Click to collapse
If I understand correctly you have to start from scratch because a lot has changed for the skinning.
New skinning has much more options and can be much more customized as far as I know. Also has gradients done with color codes rather than images.
Haven't tried it out yet (the skinning) but this is what I've read here and there.
I thought I had seen that somewhere as well...that sucks, I just got to the point I made a couple skins I like (for me, that is quite the accomplishment LOL)!!!!
I have a suggestion to make it even faster for some cases.
It seems you do a lot more processing than necessary to activate the PocketCM window on launch if it's already open.
If PocketCM is already running, switching to PocketCM from a task manager is much quicker than launching the .exe again. So maybe you can optimize your launch code to look for an existing instance earlier in your code and active it if it's already running.
TalynOne said:
I have a suggestion to make it even faster for some cases.
It seems you do a lot more processing than necessary to activate the PocketCM window on launch if it's already open.
If PocketCM is already running, switching to PocketCM from a task manager is much quicker than launching the .exe again. So maybe you can optimize your launch code to look for an existing instance earlier in your code and active it if it's already running.
Click to expand...
Click to collapse
It's already working like that.
Hi all!
I am currently using the Touch Cruise, upgraded to it from an Artemis, and i love it. Now am planning to upgrade to the Touch HD. I really loved the device looks and screen size!
But my biggest doubt is - How exactly do we navigate around?
The iPhone is totally different and made in a way that u wouldnt need the dpad at all ever. But the Windows Mobile OS isnt like that.
For example - in the Dialer screen, how do i go down the call list, in the dialer mode itself (not in call history) and well, more small things like these which actually require a "d-pad" or atleast an optical dpad.
I was also considering the SonyEricssion Xperia X1, but dropped it due to the lovely screen of the Touch HD. But now i am thinking again.
Please help guys, please do give ur comments as to what is the technology behind the HD for better navigation - without a dpad.
Thanks.
Insane Devil said:
Hi all!
I am currently using the Touch Cruise, upgraded to it from an Artemis, and i love it. Now am planning to upgrade to the Touch HD. I really loved the device looks and screen size!
But my biggest doubt is - How exactly do we navigate around?
The iPhone is totally different and made in a way that u wouldnt need the dpad at all ever. But the Windows Mobile OS isnt like that.
For example - in the Dialer screen, how do i go down the call list, in the dialer mode itself (not in call history) and well, more small things like these which actually require a "d-pad" or atleast an optical dpad.
I was also considering the SonyEricssion Xperia X1, but dropped it due to the lovely screen of the Touch HD. But now i am thinking again.
Please help guys, please do give ur comments as to what is the technology behind the HD for better navigation - without a dpad.
Thanks.
Click to expand...
Click to collapse
yeh, i would really like to know too! For example, the moneycontrol.com app in JBed works only with the dpad, so this will pretty much be the deal maker/breaker for me...anyone?
For the most part, you'll be swiping the screen with with a stylus or any of your fingers.
In other parts, wherever you're able to pop up the onscreen keyboard, you can use the added directional keys on the onscreen keyboard.
I think as long as one is shielded by Touch controls from the underlying WinMobile controls the HD will shine. Without a Dpad one will have to use the stylus even more. That is one of WinMobile's weaknesses vs. OSX iPhone - it is not Touch from the ground up. But maybe a G1 ported Android for the HD will change this for us...
Hmm...
Thanks for ur comments guys, in that case, it looks that the SonyEricsson Xperia X1 is much better than this "usage" vise, and the Touch HD is more a cosmetic thing, wherein u get a bigger screen than the iPhone, but actually is slowing down ur working!
IF i am to take out stylus often, then its definately a bad phone! Thanks to the Dpad cum scroll wheel in the Touch Cruise, my phone usage is so much easier! i had problems slightly with the P3300 (Artemis) but this is like one step advanced to that.
Now the Xperia X1 is coming wtih a physical DPAD, AND also an Optical dpad/joystick! which i think is fantastic!
What do u guys think of it? Should i go for the Xperia X1 rather? or would the Touch HD be better than that?
Thanks.
:bump:
So how DID people adjust. I played around one briefly in the Orange shop yesterday, but I'm still not convinced.
I'm moving over from a Nike (touch dual) so use the D-Pad quiet a bit. Most when texting!
Thoughts please people!
i miss the dpad too on my htc thd..
speaking of popping the onscreen keyboard and using the direction buttons, is there a software which acts as an input method? just the arrow keys only to use as a dpad.. if not someone cud develop it.. i wud really do if i knew
mayb that wud make matters better for thd users.. wel hey, its better to hav just something rather than nothing at all
I'm still very new to my HD and pretty new to these fancy gadgets in general. From the little bit of research I've done so far though you can use 3rd party apps to remap the volume buttons to move up and down, and there's another app or 2 that is attempting to turn the g-sensor into a virtual d-pad as well.
I'm guessing it won't be long before these issues are perfected.
For the most part though, we're able to just swipe around the screen to scroll through the contact list, programs, etc.
Generally HTC has attempted to make it easier to use the device without the stylus, but Windows Mobile wasn't made that way, so you will almost certainly need to use the stylus.
Case in point - how did HTC/MS allow this to happen?
Start contacts, navigate down to the contact you want to call, but somehow, call the Work telephone number, NOT the default mobile number.
Normally you'd D-Pad down to choose the contact, d-pad left and right to choose the contact number (w for work, m for mobile etc), and dpad in to dial it. Try doing that with the blackstone.
Sigh. It's a lovely piece of hardware, but you miss the dpad when you don't have it.
But, at least HTC's modfications are a good start (elphantine start menu, menu for notification icons etc, menu for volume adjustment). I just can't stand them!
I've remapped a long press of the power button to bring up a virtual dpad instead. It makes life so much easier - makes me feel at home on the device, and the extra long screen resolution means it hardly interferes with normal usage when it's on screen.
V
vijay555 said:
Start contacts, navigate down to the contact you want to call, but somehow, call the Work telephone number, NOT the default mobile number.
Normally you'd D-Pad down to choose the contact, d-pad left and right to choose the contact number (w for work, m for mobile etc), and dpad in to dial it. Try doing that with the blackstone.
Click to expand...
Click to collapse
When you get to the contact swipe left or right to change the number/email or whatever before tapping the contact.
vijay555 said:
I've remapped a long press of the power button to bring up a virtual dpad instead. It makes life so much easier - makes me feel at home on the device, and the extra long screen resolution means it hardly interferes with normal usage when it's on screen.
V
Click to expand...
Click to collapse
Which virtual dpad are you using?
TIA
@fredskis - Swiping left and right is ok, but I find using the dialer and contacts somewhat hit and miss with the biotouch gestures. As I've said elsewhere, it just about works, but it's not perfect (I work in London, and accurate swiping on the Tube is a PITA). Again, I love the huge screen, but it's a shame the dpad had to go with it.
Segueing neatly on, @goody, I'm using a virtual dpad app that I wrote. It was just a quick idea I had, but I've found it extremely helpful. It's still a work in progress, as there are many more features I want to write in, but even now I find it indispensible.
V
vijay555 said:
Segueing neatly on, @goody, I'm using a virtual dpad app that I wrote. It was just a quick idea I had, but I've found it extremely helpful. It's still a work in progress, as there are many more features I want to write in, but even now I find it indispensible.
V
Click to expand...
Click to collapse
Hello Vijay, Where can I find your virtual dpad? I was not able to find it in your site. Would it be possible to share it with us, please? I'd be very keen in trying it out.
Thanks.
I have created one with Calligrapher.
vijay555 said:
I'm using a virtual dpad app that I wrote. It was just a quick idea I had, but I've found it extremely helpful. It's still a work in progress, as there are many more features I want to write in, but even now I find it indispensible.
V
Click to expand...
Click to collapse
That's fantastic V! Boy, can you share it yet? At least an alpha or something? C'mon man. share us your code!
I got my touch hd a week ago and there's a few essential programs that just are impossible to use......i also deem your d-pad indispensable
shameless bump. vijay555?
you can find my simple virtual dpad based on fingerkeyb here:
http://forum.xda-developers.com/showthread.php?t=483218
wow, I'll check it out!Thanks so much!!
Hi guys,
Sorry about shooting off of my handle, but VJVirtualMouseWinFX (code name, for now, certainly needs a better name) is not released yet.
I think there are many apps that can support a virtual dpad as that's not difficult to achieve, but I've re-written mine to support a virtual mouse (works like the Omnia's optical mouse pad, but hopefully better ) and dpad support amongst other features. I have to say, the Virtual Mouse thing was and is one of the hardest bits of code I've had to puzzle over .
I've just got a few more tweaks to make before it'll be ready for release, so not too long to go, I hope!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
V
Looks pretty excellent. Any chance you could pop along to this thread and share your expertise?
http://forum.xda-developers.com/showthread.php?t=486268
Thanks.
Take a look: http://www.fuzemobility.com/multitouch-exists-now-without-new-hardware-or-software/
On a Windows device pressing two points leads to a key press of a point in between those points. That means for games you can create a virtual key in between the two points that is mapped as pressing both buttons. It works right now on your device. Just press down with a sharp object (like two styluses) on two points and the point in the middle will be 'pressed'. It's not very easy to do consistently but it does work.
This means games can be created for multitouch as long as virtual keys are mapped for dual key presses.
You can see that here:
http://forum.xda-developers.com/showpost.php?p=2806409&postcount=126
When you drag our finger across the screen, theres a little yelow dot that follows your finger. But if you press two areas of the screen at the same time, it shows the dot on the middle, you can even drag your fingers, the dot always stays in the middle.
I just dont see anyway that this can be used properly. At least in flash... :/
If you check the video of the Nokia multitouch in action what you do with it is create virtual keys between the keys and then a game like Guitar Hero is possible...
Not dishing the results, but thats basically a (very small) hidden key in the middle of those two keys.
Its also very hard to use in a smaller scale and easy to miss...
you just need to offset the keys. Think of a 3 button version of guitar hero as a start - make the 3 keys into a triangle at the bottom so the virtual key presses would definitely be in dead space. That should work even on a smaller screen.
you can't count this as a multitouch feature, because it makes a line between the points you pressed, it doesnt just move your touch to the center because you're confusing your device, so using this method is tricky. check it out with omniano (piano app)
Check out these two links here in our forums for some indepth discussion on this:
http://forum.xda-developers.com/showthread.php?t=486268
and
http://forum.xda-developers.com/showthread.php?t=489147
Did a small test in flash to see my point:
Control:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just run the EXE in your PPC. Press ENTER to exit the application.
As you can see its not easy (at least on my qvga) to press both buttons at the same time, and its much easier to press the hidden button on the middle of the buttons.
sschrupp said:
Check out these two links here in our forums for some indepth discussion on this:
http://forum.xda-developers.com/showthread.php?t=486268
and
http://forum.xda-developers.com/showthread.php?t=489147
Click to expand...
Click to collapse
the first link is noted in the fuzemobility article. The second one I willt est out tonight on the HD. It sounds like it works. The downside is the lack of precision required. Simple games can easily have multitouch without a problem (less keys makes the process easier since there are less points of itnersection and therefore you get larger virtual keys). I like where these projects are headed...
twolf said:
Did a small test in flash to see my point:
Control:
Just run the EXE in your PPC. Press ENTER to exit the application.
As you can see its not easy (at least on my qvga) to press both the button at the same time, and its much easier to press the hidden button on the middle of the buttons.
Click to expand...
Click to collapse
The layout is a little off I think just because there are too many buttons in the same configuration so the points of intersection are too close. So left and C places you on top of A...
can you try to remove the dpad and just leave ABC in a triangle? The virtual presses would be in between again but the spacing of a triangle is a lot better. I can see that config worknig for guitar hero or a gsen game where you don't need a dpad (just buttons). The virtual buttons should be as big as the buttons themselves as long sa there's no overlap.
twolf said:
Did a small test in flash to see my point:
Control:
Just run the EXE in your PPC. Press ENTER to exit the application.
As you can see its not easy (at least on my qvga) to press both the button at the same time, and its much easier to press the hidden button on the middle of the buttons.
Click to expand...
Click to collapse
Yeah, the buttons need to be arranged in such a way as to allow the virtual buttons to have enough space between them. That's why in the Morphgear skin in the link above he has the buttons arranged the way they are. And of course the smaller the screen and/or resolution the harder it would be I imagine.
bugsykoosh said:
the first link is noted in the fuzemobility article. The second one I willt est out tonight on the HD. It sounds like it works. The downside is the lack of precision required. Simple games can easily have multitouch without a problem (less keys makes the process easier since there are less points of itnersection and therefore you get larger virtual keys). I like where these projects are headed...
Click to expand...
Click to collapse
The Morphgear skin works great for many games, at least on a WVGA device like the Touch HD. It's still not perfect, but at least the concept-of-proof shows that it can be done.
Like you said, where these projects are headed is where the excitement comes in. Eventually it's conceivable that we'll have an application that'll allow us to use the g-sensor and the multi-touch virtual buttons seamlessly to do so much more!
I just did it for a test, didnt even created commands for the dpad+button actions.
Its in flash, so, unless the game you want is in flash too, theres no way of using this...
I can post the source-code anyway...
twolf said:
I just did it for a test, didnt even created commands for the dpad+button actions.
Its in flash, so, unless the game you want is in flash too, theres no way of using this...
I can post the source-code anyway...
Click to expand...
Click to collapse
I think the proof of concept is great so people can develop off of it. Would you mind sharing the flash itself (I couldn't develop a thing ) But I think if it is proven that this works then games can be created using this method. so some games could just use this (Tetris with a left/right and rotate button for example) or guitar hero (three buttons for now) and other games that use the gsen if needed for a dpad...
Sure, here it is... I converted it to Flash CS3.
twolf said:
Sure, here it is... I converted it to Flash CS3.
Click to expand...
Click to collapse
sorry - it's too advanc for me Would you mind taking the first flash you did with the dpad and just removing the dpad and making the virtual keys between the ABC larger so that it is more likely to get a hit?
Guys, not to belittle the work going on here, but we've had "calculated multitouch" working for a while. That video is hardly the best example of what's been achieved so far.
If you want to make any comments or contribution, drop a line here:
http://forum.xda-developers.com/showthread.php?t=486268
V
Sure, the FLA is the source-code.
Made it portrait also.
---edit---
vijay555, I saw those (great) examples, I was just saying that its not very easy to use, and nothing compares to the real multitouch feel.
And again, great work on your excellent apps.
It's not exactly multitouch, it happens with every touch surface I own (mousepads and touch screens). It's more like a side effect of the surface getting confused by having more than one touch at a time. It's been an annoyence to me for years. hehe
But I'm glad that people want to make it useful. Take a "bug" of sorts and turn it into a feature... Only at XDA. I can't wait for a new app or new touch.dll that will extend features somehow based on this.
vijay555 said:
Guys, not to belittle the work going on here, but we've had "calculated multitouch" working for a while. That video is hardly the best example of what's been achieved so far.
If you want to make any comments or contribution, drop a line here:
http://forum.xda-developers.com/showthread.php?t=486268
V
Click to expand...
Click to collapse
Screen size is a big difference here - on the HD it is a lot easier than on a Fuze...there's also more flex to the HD's screen. I think that your keyboard is great and revolutionary by all means but on a Touch Pro it could never happen because the level of precision simply doesn't exist (the virtual keys are too close). Simple apps can be made using multitouch and no one has developed them yet so hopefully the guitar hero type games will be made...
I posted a comment on FuzeMobility and I'll copy it here.
Vijay, that's impressive looking, but is along the same lines as I mention in my comment, correct? Or, are you truly using the dual touch capability of the capacitive touch panel?
I see this as an interupt of the traditional cooridinate recognition system, not true multitouch. Yes, you touch two points simultaneously and get feedback, however, you’re simply providing a simulated, broader surface that the touch interpreter is seeing as a giant sylus or finger.
In order for multitouch to work on a resistive screen you need to be able to select a point on either side of the screen and manipulate the coordinates directly related to that area. Selecting the center of a double press like is shown in the video is simply the phone interpretting the input as one big thumb.
Until two completely unrelated sets of X,Y input can be pulled from the touch panel, you’re not really getting multitouch. This can be used just like the game video shown if you place the ‘dots’ smartly on the screen, but this method won’t yield any thing resembling the multitouch on an iPhone
Click to expand...
Click to collapse
Some people might remember me from the Wizard forums...
it has been a long time since I made a public contribution on this forum, but the time has come that I will be making another one soon. it is not a full rom as of yet, but it is somthing that might be just as good.
If you look in my signature I have been working and testing a theory that graphics processing is a major contributer to laggy interface. one of the problems is the keyboard that we have come to depend on (the on screen keyboard made by HTC)
this keyboard has about 100 image files that the cpu has to process some from the PNG files and most in the SIPBITMAPS.DLL . well, I went through all of them 88 in the dll + the png files. got rid of the dithering, made uniform color schemes and overall optimised the gfx to be as light weight as possible. so light in fact that the package weighs nearly 25% less than the original one made by HTC.
I need some testers. ones who type really fast with the EZ INPUT KEYBOARD. once it is tested and proven that it is in fact faster, I will release it to the public. those interested in testing, PM me so that I can send you the CAB and directions (testting conditions)
If you have bench marking programs that would help too.
thanks for testing.
P.S. the point of this exersise is to give me a reason to "fix" the lag in the 10mb of ram eating phone skin which take a full 2 seconds to load. I figur if the keyboard is improved the most vital part of our phones should be fixed. it just takes a lot more work for those files... and it better be worth spending more than tree days of my time fixing it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Testing Conditions:
S.V.I said:
thrashingdeth said:
what are the directions for your testing on the keyboard? i want to try it out cause i use the virtual keyboard very often. thanks for your time.
Click to expand...
Click to collapse
the best way to test it is to do a soft reset; put on an mp3 file (once the phone boots and loads everything, so let the manila start up and load every tab. turn on the mp3; go into the notepad app and start typing while the music is playing. about half way through the song rotate the device (if you use the gyro rotation) and test how long it takes to catch up. (the rotation causes lag)
do the same thing with the modded gfx cab that I provided on the first post.
You can also do the test without the music playing, but the results will not be as apparent.
Click to expand...
Click to collapse
[EDIT 2/18/10] For those who do not have the same version of 2.1 keyboard and may have a different layout, I attached the XML files out of my package. I don't know if it will work to fix your layout, but it might. let me know if it works
[EDIT 2/22/2010] I added My PSD files for those who wish to change the skin in any way. I also added a comment for the .zip file.
For those who wish to change the background to a SOLID grey, you just need to change the black background to a grey of your choice. for those who wish to have the old dithered background with a lot of colors, then just make the black layer invisible (although the keyboard will run slower)
HINT: when it comes to PNG's, black is least in bytes as opposed to GIF's where it is oposite. With bitmaps it does not matter, what matters ultimately is the complexity of the pixel mosaic.
Have fun
A great idea! That must've taken quite a while to figure out
But I'm not really a fast typer when it comes to the on-screen keyboard, so I'll wait for the (possibly) public release.
does not seem like there is much interest.
either due to the holiday, or what?
I tested it last night while playing music and there is no lag. there is a bit of a lag when rotating to landscape, but only lasts about two seconds and the lag is gone. (while playing music) maybe I should post some screens or have the mods move ot to the dev/hack section. some people rely on the screen keyboard only.
I would like to test this out.
I think I can type pretty fast on the on-screen keyboard, well, if it allowed me to. Primarily I find myself having to slow down when I hit space. Sometimes I'll go so fast the space input doesn't register, effectively merging the words together.
S.V.I said:
does not seem like there is much interest.
either due to the holiday, or what?
I tested it last night while playing music and there is no lag. there is a bit of a lag when rotating to landscape, but only lasts about two seconds and the lag is gone. (while playing music) maybe I should post some screens or have the mods move ot to the dev/hack section. some people rely on the screen keyboard only.
Click to expand...
Click to collapse
Hey man, I'll give it a test drive for you...just know that I'm on the stock T-mobile US 6.1 ROM. I'm sure I'll be texting as much this afternoon as ever, so I'll give it a try and see how it feels.
ADDED THE CAB ON THE FIRST POST sorry for the caps.
try it and let me know how it works for you. seems a lot faster than the original.
I also just installed the russian cab, and it is slow as hell in comparison. so I know it works.
enjoy.
I think that if I make a new phone skin, I will have to do it on the basis of donations recieved for the keyboard. just too much work.
S.V.I said:
ADDED THE CAB ON THE FIRST POST sorry for the caps.
try it and let me know how it works for you. seems a lot faster than the original.
I also just installed the russian cab, and it is slow as hell in comparison. so I know it works.
enjoy.
I think that if I make a new phone skin, I will have to do it on the basis of donations recieved for the keyboard. just too much work.
Click to expand...
Click to collapse
Just saw your update, and grabbed the .cab, will start using it first thing in the AM, and have impressions by end of the day.
Thanks a lot for the effort either way...I'm trying every improvement to the on-screen kb that I can find, to make me less jittery about moving to the HD2 in a month or two
I tested your cab, and it does seem to respond better, and the letter's pop up faster. I'm probably not the fastest phone typer, but the original files would not keep up with me. With your fixed files, it seems to do a much better job, although still not as fast as I type. I'm running IME 1922/2011, so I'm not 100% sure how much of a difference it makes, but if you want I can run a spb benchmark with 1920 before and after installing your speedy files.
Glad to see you in the WVGA stuff, I used some of your stuff when I had an omnia.
I installed it a few mins ago and I can already notice quite a difference. Before, like ^^ he said, the buttons would not keep up with me typing, but now that lag is completely gone. I would say it is a very noticeable difference if you use the soft keyboard much. Thank you very much. (BTW, I am on the 2/14 SSS R8.5 ROM with Manila 2012)
I think the trick to doing a comparison is do a soft reset; turn on some long mp3 and type. first with the original keyboard, then with mine (black background and dithering removed).
I'm glad that it is working better for you... hopefully this will be a good performance upgrade for all of us.
The damn phone skin has such complicated gfx that I will have to make a different dialer button (the red and green one) it won't look as nice, but the interface should behave a little faster... especially when cooked in.
tested on my topaz with last duttys ROM 6.5.3 and its better ty
Not working correctly on Sprint Version
Everything seems a bit faster, but the symbol on the space bar is mess up.
Instead of the regular symbol there's just a line in down the middle of the space bar. Function wise, works perfect. Mike
Sprint TP2 Stock 6.1
HUGE difference!
Ok, so I've been trying this out all morning, and I have to say it's a dramatic improvement of the response speed of the on-screen keyboard
My error rate has also dropped significantly since using it...I thought I was usually just fat-fingering a lot of keys, but now that they respond much faster I'm making 10% of the typos I did before.
I've also noticed that part of what makes it faster is how its quicker to pull up the symbol (punctuation, etc) on a long-press, that was one of the first things I noticed when trying it.
It looks good too, I think, save for that split-spacebar mentioned above. Oh, and one minor detail...the graphic for the XT9 switch doesn't change when you toggle it. I almost never use that, so not a big deal to me, just an fyi.
So....great job S.V.I, thanks!! If I can get the on-screen KB on the HD2 (once I get it) to be this smooth, I won't feel nearly as bad about it not having a physical KB
pimpol10 said:
Everything seems a bit faster, but the symbol on the space bar is mess up.
Instead of the regular symbol there's just a line in down the middle of the space bar. Function wise, works perfect. Mike
Sprint TP2 Stock 6.1
Click to expand...
Click to collapse
which version are you using???
IME_EzInput_Western_2_1_19202429_00 is the one in my rom stock tmo 6.5
I do not have the issue with the space bar not showing up right.
also, just to make sure that I uploaded the right cab, is the space bar in a grey box or a black box (meaning the background) are you using a different language?? can you post a screenshot?
Will this work on any TP2, GSM and CDMA?
S.V.I said:
which version are you using???
IME_EzInput_Western_2_1_19202429_00 is the one in my rom stock tmo 6.5
I do not have the issue with the space bar not showing up right.
also, just to make sure that I uploaded the right cab, is the space bar in a grey box or a black box (meaning the background) are you using a different language?? can you post a screenshot?
Click to expand...
Click to collapse
Here's what the split spacebar looks like...works fine though. Again, this is on Tmob US 6.1 stock ROM.
sirphunkee said:
Here's what the split spacebar looks like...works fine though. Again, this is on Tmob US 6.1 stock ROM.
Click to expand...
Click to collapse
That explains it. the EZINPUT in the 6.1 rom is 2.0 while in the 6.5 rom it is 2.1
the SIPBitmaps dll is different. that would explain why you do not have the xt9 button showing up either. it is a different version of the keyboard.
S.V.I said:
That explains it. the EZINPUT in the 6.1 rom is 2.0 while in the 6.5 rom it is 2.1
the SIPBitmaps dll is different. that would explain why you do not have the xt9 button showing up either. it is a different version of the keyboard.
Click to expand...
Click to collapse
Understood, that makes sense. It really doesn't seem to have any impact on the overall effectiveness of your changes, so those two minor things don't bother me at all.
I've been using it all day now, and it looks like this will finally let me give the slider on my HW keyboard a much-needed break!
Fantastic idea, great work! I'll test it out now...
only 34 downloads...
where should I post this so that it gets the best exposure???
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ok everyone, here's the newest NFL skinning project I've been working on for my pro2. I liked the way the Eagles one I made for myself came out so much I went ahead and made one for every NFL team so that you guys could enjoy as well. I'd like to present you with my NFL DINIK Keyboard skins. I used DINIK's-Anastasia-Keyboard v2.0 as a base when making them. He also has a newer v3.0 keyboard skin i could use to make a newer set. Let me know what you guys think. Enjoy..
Huge THANKS goes to DINIK for creating all of his amazing skins.. These are HIS Rules and they must be followed here as well! Here they are:
!!! ATTENTION !!!
This are my Rules, simple and fair. If you break them. I gonna contact the Admins.
You are free to use my works Ifor private use.
You are free to modify my works, but only for private use. (No Share or Posting here or on other Sites)
You are not allowed to modify my works and post it here or on other sites. (Without my Permission)
You are not allowed to include my works in your Roms. (Without my Permission)
I welcome modifications and fixes from other users but please contact me first via private message before posting you modifications in the thread.
More info can be found on DINIK's Original Keyboard Thread HERE.
You're always rocking it aren't ya?
I'm having a hell of a time getting a screen shot for you. I've tried resco screen capture and shake and save and even tho i have the keyboard up, it only captures the page behind the keyboard. I also tried with my camera, but i couldn't get a clear pic. any ideas?
The landscape lines up pretty well but it seems like the bottom of the helmet (AZ Cardinals at my nephew's insistence) is cut off at the space bar, but otherwise looks great.
for the portrait it looks like there is a double space bar and a double shift key and the bottom arrow keys are cut off by the bottom menu bar.
If you have any better ideas for a screen shot, let me know and i'll try it.
ezzie said:
I'm having a hell of a time getting a screen shot for you. I've tried resco screen capture and shake and save and even tho i have the keyboard up, it only captures the page behind the keyboard. I also tried with my camera, but i couldn't get a clear pic. any ideas?
The landscape lines up pretty well but it seems like the bottom of the helmet (AZ Cardinals at my nephew's insistence) is cut off at the space bar, but otherwise looks great.
for the portrait it looks like there is a double space bar and a double shift key and the bottom arrow keys are cut off by the bottom menu bar.
If you have any better ideas for a screen shot, let me know and i'll try it.
Click to expand...
Click to collapse
Try an app called capsure(just tried it and keyboard came up in pic). Get it HERE.
I did have to resize diniks keyboard skin to fit my tp2. Give me a min and I'll edit and attach a few files for you to try n see if it fixes the problem
EDIT: Here are the resized portrait images. Leave the Cardinals(tp2)cab installed and then copy and paste these into your windows folder overwriting the tp2 files then soft-reset. let me know how it works out.
The files you posted brought me back to normal and thanks for the CapSure link, worked like a charm!
ezzie said:
The files you posted brought me back to normal and thanks for the CapSure link, worked like a charm!
Click to expand...
Click to collapse
Your welcome!! When you say they brought you back to normal you don't mean they are as in the attached pics right? are those from the cab only? Cause those don't look good at all. If they do are aligned correctly with the files I attached, I'll remake them for all teams so that hd2 users can enjoy as well.
Here's the skin I pm'd you about. let me know what you think..
Differnt ROM
if im not running Diniks ROM, can i still use these tweeks? thanks
unique1331 said:
if im not running Diniks ROM, can i still use these tweeks? thanks
Click to expand...
Click to collapse
Yea they should work just fine.(i'm running stock sprint 6.5) They're uninstallable so go ahead and try it out. Let me know then if everything is aligned correctly.
Thanks for these. They look great!
Hey, how about doing a christmas keyboard that you can add to the CHT Christmas Theme string? I don't know if those guys are aware that your skins can be adjusted to work with HD2. An xmas dialpad would be cool too........aren't I just full of good ideas for things for you to do. If you want to send me a "skinning keyboards/dialers" for dummies I can work on doing it myself too.
ezzie said:
Hey, how about doing a christmas keyboard that you can add to the CHT Christmas Theme string? I don't know if those guys are aware that your skins can be adjusted to work with HD2. An xmas dialpad would be cool too........aren't I just full of good ideas for things for you to do. If you want to send me a "skinning keyboards/dialers" for dummies I can work on doing it myself too.
Click to expand...
Click to collapse
Oh wow..I'm sorry ezzie!! For the amount of time I spend on these forums, I can't believe I totally missed this post. That would of been a great idea. I'm alil disappointed I didn't see it in time. I'll def keep the idea in the back of my mind for next christmas
I'd be happy to help you make a few of your own skins! Pm me and let me know how i can help.
Here's a preview of a wp7 skin I'm working on for swype keyboard. I have all portrait images finished and will share it once I have landscape completed. What do you guys think of it?
sweet! are the swype ones hard to do? There are very few of them out there and for some reason none of them are working with my NRGZ ROM.
btw my nephew is really jealous of my AZ Cardinal's phone pad, cursor and keyboard which of course I switched to just for that very reason!
Once again I am in awe of your graphic abilities!
ezzie said:
sweet! are the swype ones hard to do? There are very few of them out there and for some reason none of them are working with my NRGZ ROM.
btw my nephew is really jealous of my AZ Cardinal's phone pad, cursor and keyboard which of course I switched to just for that very reason!
Once again I am in awe of your graphic abilities!
Click to expand...
Click to collapse
Thanks for the kind words ezzie. Yea i've also noticed there aren't too too many swype skins availabe. Na they actually aren't that bad, they're not any harder than making skins for htc keyboard. If anything it's a little easier because there are no images involved within the .dll file like there is for htc kb. When you say they're not working, do you men the skins or swype itself. If its the skins I'll help see if we can't figure it out
uh huh cause of your nephew lol.. i think it's because your turning into a sports fan before our very eyes!
HA!
It's just the skins that aren't working, swype is fine. (except for when i accidentally delete the files trying to get the skins to work!) I'm not sure when they stopped working either because they used to work just fine with his ROMs and for awhile I wasn't using swype a whole lot. I'll attach the files in a couple of days when I get home from vacation. I'd do it now but my laptop was commandeered the minute I got to my brother's and I'll be lucky to get it back before I leave!
Here are my wp7 skins for swype keyboard I'd like to share with everyone. I've never made a skin for swype and you can see how many different things I've skined. With all the new wp7 phones coming out, I thought a wp7 themed keyboard skin would be a great starting place. I posted a few preview shots a few days ago and just finished them yesterday. I played with them all day and have found no problems(tp2). Please post if you have any problems! Let me know what you think of them. Enjoy..
They work in both portrait and landscape and are available with either a white or black background.
Instructions..
-Make sure you have swype previously installed.
-Install cab to the same directory you installed swype. example if swype is installed to storage card, install the skin to storage card.
-or copy contents of zip to swype directory (program files/swype)
-Soft-reset and your done
White Background Screenshot..
Black Background Screenshot..