Necessary components for Shift/Function Keys? - Mogul, XV6800 General

I just did a fresh FLASH on a replacement device - probably should have checked all the keyboard functions first, but oh well...
... are there any things I should be looking for on this giant list of components that would either conflict in such a way that the Function and Shift keys don't function OR the absence of which will prevent them from working?
anyone experiencing this type of issue?
Nicholas
Go Sprint - Go Pre!

Related

UBQ 501 - ROM cooking, WM5 and WM6 mix.

Dear all,
I read the forum since some months now, and I thank you all for the awesome things I learned there, now I would like to know whether something I have in mind is achievable or not.
I own an Ubiquio 501, a very thin qwerty PDA (with touchscreen, wifi and all) which works very well. However:
-With the AKU 3.3 ROM (released around february) it suffered from very bad graphic/video performance, but everything else was working pretty well.
-With the last WM6 upgrade (released in august) the maker fixed the graphic issue, but for me the keyboard behavior is nothing but unacceptable. It seems like I am the only one having problems with the keyboard, however a downgrade (to AKU 3.3) fix the keyboard bit, so I guess the problem is not in the hardware.
What I would like to achieve is to put the keyboard drivers in the WM6 ROM, what do you think, is this feasible? I was able to unpack the ROMs with the kitchen tools, but am not sure of which module the actual keyboard driver is, the relevant files and dirs (find dump/ -iname "*key*") in the
AKU3.3 ROM :
Code:
./KeyBDState_service.dll
./KeyBDState_service.dll/KeyBDState_service.dll
./KeyIcon.dll
./KeyIcon.dll/KeyIcon.dll
./keypad.dll
./keypad.dll/keypad.dll
./keysifter.dll
./keysifter.dll/keysifter.dll
./devauthkey.dat
and in the WM6 ROM:
Code:
./KeyBDState_service.dll
./KeyBDState_service.dll/KeyBDState_service.dll
---> same file as in WM5 (md5sum match)
./KeyIcon.dll
./KeyIcon.dll/KeyIcon.dll
--> different
./keypad.dll
./keypad.dll/keypad.dll
-->different
./keysifter.dll
./keysifter.dll/keysifter.dll
--> different
./devauthkey.dat
-->same file as in WM5 (but I guess it doesn't have anything to do with the keyboard!
Should I look for other files? (I think so
Thank you all in advance!
Regards,
DAniele
I have had the 503g for a few weeks now and love it. If there is anything I can help you with please let me know.
Hi maevro, thanks for joining
I just found (using a task manager) that stopping the "key sifter" service yields to a complete stop of the hardware keyboard (only things that keep working are the keyboard backlight and some "special" buttons: the comm-manager activator, the mode switcher (alpha, num), the shift key).
However, overwriting the keysifter.dll file with the wm5 version I was only able to reach a non-working state (the service does not start automatically and will refuse to start manually).
So, keysifter.dll is definitely (one) culprit, but additional testing may be needed to see its dependencies (I guess) in order to replace it with a (better) working version.
Regards,
DAniele
--
gdaniele said:
Hi maevro, thanks for joining
I just found (using a task manager) that stopping the "key sifter" service yields to a complete stop of the hardware keyboard (only things that keep working are the keyboard backlight and some "special" buttons: the comm-manager activator, the mode switcher (alpha, num), the shift key).
However, overwriting the keysifter.dll file with the wm5 version I was only able to reach a non-working state (the service does not start automatically and will refuse to start manually).
So, keysifter.dll is definitely (one) culprit, but additional testing may be needed to see its dependencies (I guess) in order to replace it with a (better) working version.
Regards,
DAniele
--
Click to expand...
Click to collapse
Is the graphicproblem totally gone, so you can play games and watch movies without any problems?
Also, do you have any problems with network on this device?
Keep us updated if you find any solution to the keyboard-delay problem!
Thanks
Well, I kind of sorted it out. The solution ain't optimal, but at last I can write my sms & mails as I was used to.
After many tries and file swap between wm5 and wm6 rom dump, I stopped the keyBDState service and... kaboom, everything worked as expected Yes, it was _that_ simple
Please note that there are still some issues (shift + arrow keys does not highlight) but I made this mod a few days ago and have noted no instability whatsoever.
The only thing that ceased to work after the mod is that I can no longer compose phone numbers from today screen (but in the phone app everything works, so I am not that disappointed).
If you want to try it by yourself, I can only advice for a prior full backup, and can take no responsibility for whatever damage may occur to your data, phone, sim card... blah blah blah ...
So long for my first post, although I really would like to investigate the thing a little bit further (and get highlighting back as it was in wm5).
To answer uggugg, I only tried a (mandatory ) Zoolander sample and it worked well (re-encoded to fit screen size, 20 fps, don't remember the bitrate, should check) as for the games... I really ain't into gaming (not on my phone, at least) so I'm sorry I couldn't tell you anything.
Regards,
DAniele
--

problem hooking physical keys on HTC HD

Hi all,
im trying to hook the volume up and down keys using the SetWindowsHook API.
im having some problems with getting the vk codes of the keys, on a couple of different states on the machine:
1. when I try to get the code when the camera window is up - i get a same code for volume up and down.
2. when i try to do the same with camera windows is not up - i get a different code for each button and different then the event i got in section 1.
does anybody has a solution for me?
thanks.
IIRC I think that the keyboard driver has special case handling for the volume keys - I remember dissecting the driver with IDA some time back.
Try having a pick through the disassembly to see if you can find the codes and handling directly in there.
It was possible to hook right into the driver, but it's messy.
V

Service bypass

I don't know how much you are aware here about our Samsung application autoclosing bug/feature/whatever. This appears to be connected to taskmon.dll service since when I disable it, it stops. Thing is that this dll is also appears to be controlling another dll service motionagent.dll that controls things like slider response in the system.
So my question is: is there a way to either "emulate" taskmon or get info from/to motionagent based solely on data from these 2 files?
are you talking about Omnia II? I can never run more than 3-4 apps at the same time and always the "oldest" one is being closed. Veeeeeeeery annoying!
Both Omnia II and B7610 have the same problem, but for you it's easier and since you don't have slider you shouldn't have problem i have. Try this and let me know how it works for you.
great! It seems to be working!
What is this slider thing you are talking about?
Well slider is hardware keyboard that b7610 has.
maybe it's working to hook into the DLL and disable calls to function "SuspendThread"?
You may want to refer to the kingmobi article that provides more insight into the matter:
http://translate.google.com.hk/tran...ww.kingmobile.net/bbs/archiver/tid-98483.html
now it's finally done properly:
http://forum.xda-developers.com/showthread.php?t=637771

[Q] Snap + onscreen keyboard problem (only works after restart)

My probleem is that snap and the big onscreen keyboard only function after a restart of the system but not at cold boot..
My screen is 22" 1680x1050.
Please help..
Clean install, OEM install, or upgrade? What hardware (I'm guessing something with a touchscreen if you care about the SIP).
GoodDayToDie said:
Clean install, OEM install, or upgrade? What hardware (I'm guessing something with a touchscreen if you care about the SIP).
Click to expand...
Click to collapse
Goodmorning..
Clean install on a Dell d820 with An 6 point infrared touchscreen.
Wat do you mean by SIP..?
SIP = Software Input Panel. The catch-all term for the variety of virtual keyboards, handwriting recognition, etc.
It sounds hardware related (the OS shouldn't even know if it was started from cold boot or not) but I can't point to anything specific and say "there's your problem". However, you should definitely check for any BIOS (or EFI/UEFI) updates. A buggy BIOS could produce this behavior.

Using the create pad with Wacom/Bamboo pad compatible apps

Hi All,
I am wondering if anybody here had any success with getting their Yoga Book to work nicely with the GIMP photo editor at all? I can use it to draw, but as a mouse with no pressure. I went through a few tutorials online on how to get the GIMP to work with Bamboo/Wacom tablets, but it doesn't seem to work with the Yoga Book, as the drivers aren't being seen by GIMP or DirectInput for whatever reason.
I am more of a casual artist, and so I don't feel like I want to fork out money for say Photoshop, when the GIMP can for the most part do what I'd like. Plus, I am mostly an open source guy, using Linux as my main daily driver on my home PC, that I am fairly used to the GIMP already.
Thanks!
kveroneau said:
Hi All,
I am wondering if anybody here had any success with getting their Yoga Book to work nicely with the GIMP photo editor at all? I can use it to draw, but as a mouse with no pressure. I went through a few tutorials online on how to get the GIMP to work with Bamboo/Wacom tablets, but it doesn't seem to work with the Yoga Book, as the drivers aren't being seen by GIMP or DirectInput for whatever reason.
I am more of a casual artist, and so I don't feel like I want to fork out money for say Photoshop, when the GIMP can for the most part do what I'd like. Plus, I am mostly an open source guy, using Linux as my main daily driver on my home PC, that I am fairly used to the GIMP already.
Thanks!
Click to expand...
Click to collapse
Hey,
I indeed had the same issues with GIMP (also with Krita and MyPaint - I am open source guy as well ) a while ago. The trick is to install specific drives from Wacom. Here is the link (or at least I hope it is, I tried this few months ago ): http://us.wacom.com/en/feeldriver/ EDIT: Please note that this driver might change the way stylus behaves and might not work correctly.
Just little bit of advice/side note; I tried all thinkable painting/photoshop software on my yoga - both open source and piad one (trial versions) - and thou I use open source software daily in my work (GIMP and Inkscape) it is not the same on yoga. Small screen and Atom processor is not very optimal - it works, no doubt about it, but it just isn't same as on the desktop. I hate to admit it, but after a while I ended with older version of Sketchbook Pro - it runs very well and has nice easy UI and reasonably powerful tools, which is perfect for light sketching.
Thanks. So, I tried installing the driver, and it did install successfully. However, GIMP is still unable to work with pressure sensitivity. On the bright side, the Halo keyboard, and touchscreen are unaffected and still work as expected. The only issue from installing the driver is that now when I use the pen on the create, I still a full white windows cursor on the screen which is very very annoying.... I very much preferred the unobtrusive translucent circle. I went into the settings to attempt to return said circle, but it resulted in total failure as the annoying white Windows cursor remained. This now renders any drawing or writing activity now annoying as the windows cursor is an eye sore and just gets in the way and blocks whatever is behind it.
I am writing this on the Yoga book, and I'm just noticing something with the keyboard. I am a very fast typer, and I am feeling the hepatic feedback from each key press, but the click sound is only heard after I stop typing quickly. Not sure if this is related to the driver or if it was like this prior.
I am now considering removing said driver, however, I am unsure if it completely replaced the Lenovo one, and if I remove it, will it just turn this machine into a brick, and needing a full factory reset to get everything back to normal.
For anyone else reading about this driver, I highly recommend to avoid installing it until these specific quirks can be figured out, and if uninstalling it after will result in a non-functional wacom touch screen and create pad. I am really hoping that the keyboard part of the create pad is part of a completely separate driver, and the pen button/light is just a toggle between two completely separate hardware modes. I'll see if I can use a restore point perhaps to return back the previous functionality. I am hoping that Lenovo themselves issues an update for this rather great piece of technology so that we don't need to download wacom or third party non-Lenvovo tested drivers. This device is fairly unique and it's hard to see a generic driver keeping all the customization from Lenovo working 100%.
UPDATE: Okay, so I was unable to remove the driver using the standard add/remove program thing in Windows, which seemed to have restored the original functionality. My cursor is back to a nice small circle when I hover or use the create pad with the pen, which is much more favorable. I can live without pressure sensitivity in GIMP, as long as the sketching apps have pressure and show me a non-obtrusive circle, I can easily export said sketches into PNG format and import that into the GIMP to further edit using more advanced tools.
kveroneau said:
Thanks. So, I tried installing the driver, and it did install successfully. However, GIMP is still unable to work with pressure sensitivity. On the bright side, the Halo keyboard, and touchscreen are unaffected and still work as expected. The only issue from installing the driver is that now when I use the pen on the create, I still a full white windows cursor on the screen which is very very annoying.... I very much preferred the unobtrusive translucent circle. I went into the settings to attempt to return said circle, but it resulted in total failure as the annoying white Windows cursor remained. This now renders any drawing or writing activity now annoying as the windows cursor is an eye sore and just gets in the way and blocks whatever is behind it.
I am writing this on the Yoga book, and I'm just noticing something with the keyboard. I am a very fast typer, and I am feeling the hepatic feedback from each key press, but the click sound is only heard after I stop typing quickly. Not sure if this is related to the driver or if it was like this prior.
I am now considering removing said driver, however, I am unsure if it completely replaced the Lenovo one, and if I remove it, will it just turn this machine into a brick, and needing a full factory reset to get everything back to normal.
For anyone else reading about this driver, I highly recommend to avoid installing it until these specific quirks can be figured out, and if uninstalling it after will result in a non-functional wacom touch screen and create pad. I am really hoping that the keyboard part of the create pad is part of a completely separate driver, and the pen button/light is just a toggle between two completely separate hardware modes. I'll see if I can use a restore point perhaps to return back the previous functionality. I am hoping that Lenovo themselves issues an update for this rather great piece of technology so that we don't need to download wacom or third party non-Lenvovo tested drivers. This device is fairly unique and it's hard to see a generic driver keeping all the customization from Lenovo working 100%.
UPDATE: Okay, so I was unable to remove the driver using the standard add/remove program thing in Windows, which seemed to have restored the original functionality. My cursor is back to a nice small circle when I hover or use the create pad with the pen, which is much more favorable. I can live without pressure sensitivity in GIMP, as long as the sketching apps have pressure and show me a non-obtrusive circle, I can easily export said sketches into PNG format and import that into the GIMP to further edit using more advanced tools.
Click to expand...
Click to collapse
Hey, sorry to hear that you had issues, I did not noticed any when I tried the driver and pressure in GIMP/Krita/MyPaint was working - if I remember correctly, there was new wacom icon under Control Panel, did you tried adjust this? Also in GIMP you need to enable, and correctly set, "Dynamic" setting under brush tool for pressure sensitivity to work.
Anyway, I edited my previous post with warning about drivers so that anyone would know immediately. Again sorry for the issues, but from my point of view it worked.
Talsi said:
Hey, sorry to hear that you had issues, I did not noticed any when I tried the driver and pressure in GIMP/Krita/MyPaint was working - if I remember correctly, there was new wacom icon under Control Panel, did you tried adjust this? Also in GIMP you need to enable, and correctly set, "Dynamic" setting under brush tool for pressure sensitivity to work.
Anyway, I edited my previous post with warning about drivers so that anyone would know immediately. Again sorry for the issues, but from my point of view it worked.
Click to expand...
Click to collapse
I did notice the new settings under control panel, but there was nothing there but pen button related options, of which the Lenovo pen has no buttons. I tried a few options in GIMP, and the Wacom tablet did display itself as an Input device. I figure I could have gotten it working, but having a full Windows cursor when using the create pad was just a bit distracting in my eyes. This cursor persisted in programs which it is normally absent such as the Windows built-in Sketchpad which is one of the easiest and quickest programs to launch for quick jotting of notes and sketches. I tried changing a few options in both Settings and Control panel, but the Windows cursor remained.
Thank for your help anyways, I'm sure this driver will be useful to other people.

Categories

Resources