Run this app in the background to use the G-Sensor as a DPad. Seems to work with cursor (in word etc) and, start menu, list boxes etc.
Comments/feedback appreciated (but please remember it is a work in progress!)
Version History
Added sample full config with descriptions
Added <VK_DPAD> option in config xml to increase compatibility.
Version 0.9:-
Bug fix to tilt logic
Added more override options for individual applications (e.g. MaxX/Y, DeadZoneX/Y)
Uploaded XSD for config file (contains some documentation)
Version 0.8:-
Added hardware key toggle to config file
Version 0.7:-
Moved all settings into config file
Improved UI
New "Switch" mode added
New "KeySend" methods added (SendMessage & KeybdEvent)
Version 0.6:-
Minor bug fix
Version 0.5:-
New config file format, to support...
Acceleration mode!
Version 0.4:-
Better matching of exe names (oops!)
Version 0.3:-
Allowed list now works from exe name (rather than window title)
Version 0.2:-
Config file
Proportional directions
Non-flat center/neutral point (config - CenterX/CenterY)
"Dead Zone" (config - Threshold)
Restriction by program (config - Application)
Have a play and let me know your thoughts.
I'll give her a look see --- not happy with the virtual SIP solution I've been trying to code. I was wondering if I could detect a hardware key (like the back arrow) and then use the g_sensor for scrolling if and only if that button was being held. That way apps aready using the g-sensor could continue to use it and users could have greater control over what was scrolled and when. Since you already have taken this this far I throw the idea your way to run with it if you want to... if not that is fine too.
Blessings my friend in the new year!
PS-If you want to collaborate in coding send me a PM
Seems to work as intended... The single-hardware button "hold to enable - release to disable" would make this a real solution... Are use using Dutta's Unified Sensor API "My Brain Hurts website"?
Good work so far
how do you install this??
Excellent !!
exactly what I was looking for, great job!
I'll test it in some games unusable without d-pad and report.
thanks !
patterns said:
how do you install this??
Click to expand...
Click to collapse
I copied the files to my SD card and ran the exe... switching to another application then uses g-sensor as directional arrows... stopping EXE kills behavior... at least that's what worked for me
I tried it out and this seems promising. Below are some things I would like to see added to make this truly useful.
1. You do not want to have it active all the time so you need an easy ability to activate/deactivate it as already stated above. Either by pressing and holding a hardware button or by pressing and holding a certain area/corner of the screen.
2. When I hold the phone in my hand the neutral position is almost never the completely flat position. I think the position of the phone when you activate it according to 1. above should be taken as the neutral position. Any relative movements from that position should then be interpreted as left,right,up and down.
3. Make the speed of the scrolling configarable.
4. Make the speed of the scrolling proportional to the movement from the neutral position. If I move only slightly from the neutral position it should scroll slowly and if I move it a lot it should scroll faster.
5. A per application filter would also be really useful. For each application you should be able to specify ig G-Pad is active always, never or when activated according to 1. above. The default for unlisted applications should be to activate it according to 1. above.
Don't hesitate to ask if you have any questions regarding my suggestions. I don't think any of them should be really hard to implement.
Keep up the good work. I look forward to the next version of this.
Wow, so many responses! Like I said initially, its a work in progress. On the "ToDo" list is :-
1. Config File!
* Threshold setting (how much to tilt before registering
* Center (i.e. what angle is neutral instead of flat)
* Application list
2. Proportional control
I'll add the other suggestions to my list.
Cheers
Great work! The most wanted for me is the possibility to map it to a button, so by pressing the button your program is enabled, by pressing it once again, it is disabled again.
Another idea would be that it is just enabled while you are pressing the button, whereas it is disabled when you are not pressing the specified button.
But its up to you .
johnpatcher said:
Another idea would be that it is just enabled while you are pressing the button, whereas it is disabled when you are not pressing the specified button.
Click to expand...
Click to collapse
This makes the most sense to me, browsing lists for instance would be so much more practical.
Keep up the excellent efforts!
1.)How is this virtual d-pad different of GController ?
2.) Can you move the map in Age of Empires 1,25 with this ?
excellent idea and a very promising start. thank you and Happy New Year!
this thread belongs to the "themes, applications and software". i'll try to persuade one of the mods.
Wolfenzi said:
1.)How is this virtual d-pad different of GController ?
Click to expand...
Click to collapse
Thats written for the Diamond (not 100% on HD) and development has stopped
Wolfenzi said:
2.) Can you move the map in Age of Empires 1,25 with this ?
Click to expand...
Click to collapse
No idea! I dont have AoE so once its up and running properly (its still in very early alpha!) I'll ask people to post compatible & incompatible apps.
Looks really promising! Seems to work pretty nicely. I think the two main things I would like would be similiar to what people already asked:
- An easy way to toggle it on\off rather than running the application and killing it.
- A way to calibrate the sensitivity threshold. It reacts rather quickly now.
Good job!
Ideas
I've been thinking about this more... if you allowed a program button like the BACK ARROW to temporarily activate when pressed, read current orientation and then applied scrolled based on the orientation delta from the initial orientation and then disabled scrooling once the BACK ARROW was released. This would solve the "Gee its not flat" problem and the enable/disable issue. Other configurable options might include as noted above -- changing g-sensor sensitivity; limiting scroll direction (N-S or E-W)
Can't wait to see your next version... I've suspended work on my v-DPad because i think yours will be the better solution
Has anyone tried this on a Touch Pro, i might do it right now and get back to you guys
EDIT: Well I just tried this on my Touch Pro and it works prefect, but it would be awesome if there was a way to disable it when using TF3D because you have to have the phone perfectly flat or it will move around on the tabs, or maybe make settings for it to disable in some programs
Very nice app, I will keep my eye on this one, Thanks!
Very nice!
I think this is the perfect solution as it allows to control everything with the GSensor. Too bad GController development has beed stopped, I hope this will be the perfect successor.
Great job!
This is really great work and has a lot of potential.
Let's wait for a more "finished" version.
thanks
It's so amazing good job
Work in PocketGBA (GBA emulator)?
Does this app work in PocketGBA?
Can't play GBA games on my mobile now since i upgrade my phone to HD as PocketGBA require hardware buttons for directions control.
GBA on Morphgear is just too slow with the sound on
Hi folks,
I need a few testers with LG devices to try something for me. This app is a test app to see if it might be possible to write a registry browser using no homebrew native DLLs (and therefore it would work on Mango).
The test app does not require Mango, but will run on Mango if your device is unlocked for Mango homebrew ("full unlock", not just "dev unlock"). Don't remove ID_CAP_INTEROPSERVICES; the app almost certainly work without it.
Please run the three tests and report the results. You can then uninstall the app. It will make no changes to your phone. Whether successful or unsuccessful, I have more tests that I'll want to run later. Thanks for helping out; I don't have an LG device so you're really just helping yourselves!
Note: I'm aware that Heathclif74 is bringing his Root Tools app to LG and to Mango, so in the long run this won't be needed. However, it may still be useful - as an interim solution or as an easy way to get interesting results.
EDIT 1: Thanks folks! Due to the third testing returning wayyyyy too many results, I suggest you don't run this anymore - I've got the data I need to create another version. I'll post test 2 later (and I'll have a better way to handle anything expected to return lots of data).
Ok, I will testing after ~5 hours.
I was thinking of the same thing although i tried to copy the repsonse xml files on samsungs to query, but unfortunately they were empty and querying did not work for me. I remember that LG indeed has a query api (it will probably only work on the registry and not on the file system itself).
Good luck with it, if you need help let me know
LG Optimus 7, V7392
Test 1= 1
Test 2= Sub.key contained 1 values: Version
Test 3= a whole bunch of results, maybe 150 !!!!!
If i have more time would report it all.
Thanks
LG Quantum: 7720.68
Test 1:
Success
the value was 1
Test 2:
Sub-key contained 1 values:
Version
Test 3:
attached 1st page as image.
all following pages as jpeg package (images 1168 through 1187)
it should be straight forward to OCR these if necessary.... (btw. it's not possible to create txt file and email this within your app? )
btw. Marvin_S and GoodDayToDie, some of this looks like a set of the config.xml that I can call up with the MFG tool on the phone.
the entire config.xml is here:
http://daytonacs.org/files/wp7/
image IMG_1160 (600x800).jpg through IMG_1167 (600x800).jpg
You say we need to full unlock our LG devices if we are on Mango. How can we do this if we can only unlock HTC devices? Did I miss something here?
airwa1kin7 said:
You say we need to full unlock our LG devices if we are on Mango. How can we do this if we can only unlock HTC devices? Did I miss something here?
Click to expand...
Click to collapse
I think dev unlock here is meant to be a legit developer unlocked device via an AppHub account etc.
Not the way LG users use the MFG tool to unlock their phones. I consider this as fully unlocked because I can sideload ID_CAP_INTEROPSERVICES xaps perfectly fine, whereas a user with a legit dev unlocked device cannot. They just get the dreaded E: 0x81030120 error.
Here is what the expert says.
The current status with LG devices on Mango is that registry changes are possible via DiagProvXML (MFG tool aside) but file ops are restricted.
1 and 2 tests - same.
What you need from 3th test? I don't understand.
minep said:
1 and 2 tests - same.
What you need from 3th test? I don't understand.
Click to expand...
Click to collapse
he needs the entire query result for research into LG on-device file operations and registry changes. Since it's many pages of code and no way to export to txt the best way is to take pics of your device for each page you can scroll through (see my post above).
That need change to TextBox.
Whoa, thanks guys!!
Not sure what test 3 is doing - it should be only retrieving results one level deep (recursive=false). This will need to be explored more.
However, the actual result is fantastic! Please stop running the app for now until I come up witha new version that doesn't throw pages and pages of results at you.
@derausgewanderte: I opened up Visual Studio to start that app less than 30 minutes before posting it. Total hack, no frills. I was only expecting maybe 20 results max for the third test, and not recursive ones either!
GoodDayToDie said:
Whoa, thanks guys!!
Not sure what test 3 is doing - it should be only retrieving results one level deep (recursive=false). This will need to be explored more.
However, the actual result is fantastic! Please stop running the app for now until I come up witha new version that doesn't throw pages and pages of results at you.
@derausgewanderte: I opened up Visual Studio to start that app less than 30 minutes before posting it. Total hack, no frills. I was only expecting maybe 20 results max for the third test, and not recursive ones either!
Click to expand...
Click to collapse
either way, there seems to be tons of interesting information in there
Dear XDA friends :laugh:today I make available an guide to align/calibrate the touch screen with more than just 4 points.
The benefit of aligning the screen with more than just more than 4 points is that the touch screen will be more acurate
when there is an touch input.
After much frustration of my 22" touch panel not registering my touch inputs the way it should I've spend weeks to search the internet
for an solution to this problem.
And the problem lies in the fact that microsofts calibration tool offers too few calibration points (4 or a few more for pen input).
This guide also applies to pen inputs but when using a pen you should keep in mind that the first point you touch while calibrating has to be with the pen.
Before starting off you should make an windows restore point. okay lets get it started.
1) Go to the control panel and open tablet pc settings.
2) Hit reset.
3) Open command prompt CMD as administrator.
4) Choose one of the following options: 4a,4b or 4c:
4a) As mine touchscreen is 22" 1680x1050 I calculated the folowing line to get 150 calibration touch points:
tabcal lincal novalidate XGridPts=5,117,229,341,453,565,667,789,901,1013,1125,1237,1349,1461,1537,1675 YGridPts=5,109,213,317,421,525,629,733,837,941,1045
Copy and paste this line above into the command prompt and hit enter than proceed to step 5.
4b) If your screen resolution is 1280x800 and you want 36 calibration see the following line:
tabcal lincal novalidate XGridPts=5,259,513,767,1021,1275 YGridPts=5,163,321,479,637,795
Copy and paste this line above into the command prompt and hit enter than proceed to step 5.
4c) If you have a different screen resolution than the ones above than calculate the best entries for your screen:
lets say you want 36 calibration points for your 1280x720 screen reslotution.
than do the folowing for the XGridPts: 1280-10= 1270
Now we make sure that we start of at XGridPts=5 and the last XGridPts=1275
that leaves us with 1270 Pts lets divide it by 5 > 1270/5= 254
So the steps will be 254Pts
As our first XGridPts=5 we keep adding 254Pts until we get around 1275Pts
So 5Pts+254Pts=259Pts and that will be our second Pts
The result will be: XGridPts=5,259,513,767,1021,1275
Next will be our YGrid:
720-10=710
Now we make sure that we start of at YGridPts=5 and the last YGridPts=715
that leaves us with 710 Pts lets divide it by 5 > 710/5= 142
So the steps will be 142Pts
As our first YGridPts=5 we keep adding 142Pts until we get around 715Pts
So 5Pts+142Pts=147Pts and that will be our second Pts
The result will be: YGridPts=5,147,289,431,573,715
So now we have succesfuly calculated the x and y grid:
XGridPts=5,259,513,767,1021,1275 YGridPts=5,147,289,431,573,715
Copy and paste this line above into the command prompt and hit enter than proceed to step 5.
5) If al goes wel you should now be presented with an calibration window with more than 4 points hit all the points and your touchscreen should be
beter to use in older applications.
if you get any syntax error make sure there are no spaces in the numbers while copy and pasting.
6) If you get an pop up message when using 4a 4b or 4c saying that there already are calibrations settings entered and that you should go
to the tablet pc settings and hit reset you should do the following:
*Go to Control Panel>Device manager
*In Device Manager, locate the device you want to remove/reset, and then double-click the device name.
*Click the Driver tab, and then click uninstall and disconnect the device from computer and restart.
Now when you reconnect the device after the restart it should reinstall the default driver settings.
Of course you should use these settings at your own risk but it shouldnt be a problem if you made an restore point.
As an result my touchscreen works 100% in every part of the screen.
If you have used this guide please let me know your results and dont forget my thanks meter .
Sources used:
http://forum.tabletpcreview.com/ep121-slate/43622-pen-calibration-trick.html
http://answers.microsoft.com/en-us/windows/forum/windows_vista-hardware/tablet-calibration/f11fcc78-2926-4463-8445-ec6e7de2603d
No offense, but I don't think anyone is going to try this. Seems far too complicated.
Well I'm not so sure about that.. Beacause the moment your touch input is way of from the point that you touched you will be frustrated with a useless screen. thats when this thread will be a handy guide.
And also I do believe people are appriciating this thread because my thanks meter is climbing slowly .
Frustrating... WACOM...
So I've tried this on my series 7 slate but am having no joy...
I've tried this with default windows drivers as well as the wacom drivers and each case the results are still inconsistent.
Also settings defined in portrait adversely affect settings defined in landsacpe and vice versa...
It's quite frustrating as I need this thing for note taking...
I am actively looking into this and will share any findings with the you all.
young blade said:
Dear XDA friends :laugh:today I make available an guide to align/calibrate the touch screen with more than just 4 points.
The benefit of aligning the screen with more than just more than 4 points is that the touch screen will be more acurate
when there is an touch input.
After much frustration of my 22" touch panel not registering my touch inputs the way it should I've spend weeks to search the internet
for an solution to this problem.
And the problem lies in the fact that microsofts calibration tool offers too few calibration points (4 or a few more for pen input).
This guide also applies to pen inputs but when using a pen you should keep in mind that the first point you touch while calibrating has to be with the pen.
Before starting off you should make an windows restore point. okay lets get it started.
1) Go to the control panel and open tablet pc settings.
2) Hit reset.
3) Open command prompt CMD as administrator.
4) Choose one of the following options: 4a,4b or 4c:
4a) As mine touchscreen is 22" 1680x1050 I calculated the folowing line to get 150 calibration touch points:
tabcal lincal novalidate XGridPts=5,117,229,341,453,565,667,789,901,1013,1125,1237,1349,1461,1537,1675 YGridPts=5,109,213,317,421,525,629,733,837,941,1045
Copy and paste this line above into the command prompt and hit enter than proceed to step 5.
4b) If your screen resolution is 1280x800 and you want 36 calibration see the following line:
tabcal lincal novalidate XGridPts=5,259,513,767,1021,1275 YGridPts=5,163,321,479,637,795
Copy and paste this line above into the command prompt and hit enter than proceed to step 5.
4c) If you have a different screen resolution than the ones above than calculate the best entries for your screen:
lets say you want 36 calibration points for your 1280x720 screen reslotution.
than do the folowing for the XGridPts: 1280-10= 1270
Now we make sure that we start of at XGridPts=5 and the last XGridPts=1275
that leaves us with 1270 Pts lets divide it by 5 > 1270/5= 254
So the steps will be 254Pts
As our first XGridPts=5 we keep adding 254Pts until we get around 1275Pts
So 5Pts+254Pts=259Pts and that will be our second Pts
The result will be: XGridPts=5,259,513,767,1021,1275
Next will be our YGrid:
720-10=710
Now we make sure that we start of at YGridPts=5 and the last YGridPts=715
that leaves us with 710 Pts lets divide it by 5 > 710/5= 142
So the steps will be 142Pts
As our first YGridPts=5 we keep adding 142Pts until we get around 715Pts
So 5Pts+142Pts=147Pts and that will be our second Pts
The result will be: YGridPts=5,147,289,431,573,715
So now we have succesfuly calculated the x and y grid:
XGridPts=5,259,513,767,1021,1275 YGridPts=5,147,289,431,573,715
Copy and paste this line above into the command prompt and hit enter than proceed to step 5.
5) If al goes wel you should now be presented with an calibration window with more than 4 points hit all the points and your touchscreen should be
beter to use in older applications.
if you get any syntax error make sure there are no spaces in the numbers while copy and pasting.
6) If you get an pop up message when using 4a 4b or 4c saying that there already are calibrations settings entered and that you should go
to the tablet pc settings and hit reset you should do the following:
*Go to Control Panel>Device manager
*In Device Manager, locate the device you want to remove/reset, and then double-click the device name.
*Click the Driver tab, and then click uninstall and disconnect the device from computer and restart.
Now when you reconnect the device after the restart it should reinstall the default driver settings.
Of course you should use these settings at your own risk but it shouldnt be a problem if you made an restore point.
As an result my touchscreen works 100% in every part of the screen.
If you have used this guide please let me know your results and dont forget my thanks meter .
Sources used:
http://forum.tabletpcreview.com/ep121-slate/43622-pen-calibration-trick.html
http://answers.microsoft.com/en-us/windows/forum/windows_vista-hardware/tablet-calibration/f11fcc78-2926-4463-8445-ec6e7de2603d
Click to expand...
Click to collapse
Maybe you should try to calculate more than 36 touch points..
Also check and see what happen if you delete all drivers and use the windows default drivers.
Please let us know your findings.
Front Paged :good:
This is far too complicated...... how do you set it up for 1920x1680 ??
thekiller99 said:
This is far too complicated...... how do you set it up for 1920x1680 ??
Click to expand...
Click to collapse
1920 gives you: starting point 5 and ending point 1915.
Than you do 1915 - 10 = 1910
divide 1910 by 5 -> 1910/5= 382
so your starting Xgrid point is 5.
second = 5+382=387
next 387+382=769
next 769+382=1151
next = 1151+382=1533
next = 1533+382=1915
Yeah all went well so or Xgrid will be:
XGridPts=5,387,769,1151,1533,1915
Now you do the same for the Ygrid.
start off by doing 1680-10=1670
than divide 1670 by 5= 1670/5=334
Good luck..!!:good:
Hey! This is absolutely great!
I came here looking for a method to increase calibration for my HP 2740p Tablet PC! I have successfully used your calibration data and so far it seems a lot more consistent! It used to 'drift' a lot in the middle of the screen, with the edges being alright.. Will this need to be calibrated if I rotate the screen? I'll have to reverse the X and Y values first though, but is it necessary?
Thanks for this awesome tutorial,
Regards Giles
GilesTheAlmighty said:
Hey! This is absolutely great!
I came here looking for a method to increase calibration for my HP 2740p Tablet PC! I have successfully used your calibration data and so far it seems a lot more consistent! It used to 'drift' a lot in the middle of the screen, with the edges being alright.. Will this need to be calibrated if I rotate the screen? I'll have to reverse the X and Y values first though, but is it necessary?
Thanks for this awesome tutorial,
Regards Giles
Click to expand...
Click to collapse
I'm pleased that it helped you out.. i would say just experiment with it.. and dont forget my thanks meter..
There's no necessity for calculating the grid points, any grid point you give to the device, it brings it up for you in the calibration process.
Anyway, this is a great tweak, but it does not work on my ThinkPad Tablet 2. Not even with admin permission. It brings up the calculation routine with added grid points ( I tried with even 120 points ), but in the end, nothing happens, no change in accuracy at all.
What i would suggest to make this even user friendly is do the lines for the common screen resolutions like 1366x768 , 1920x1080 etc. We all know the majority of people are lazy so if you can make it copy and paste etc it'll be even more popular.
Very Useful
I found this immensely helpful. Thanks very much. I used the utility to solve the calibration on a Dell Latitude 10 - which has a wonky native screen resolution of 1366 x768. I created a batchfile and set it with admin priv and it's great. In the process of evaluating 8.1 preview the touch screen calibration got way off. It was always a little exciting because where you touched it and what happened next were not really related.
Thanks again.
young blade said:
Dear XDA friends :laugh:today I make available an guide to align/calibrate the touch screen with more than just 4 points. ...
Click to expand...
Click to collapse
spiperman said:
I found this immensely helpful. Thanks very much. I used the utility to solve the calibration on a Dell Latitude 10 - which has a wonky native screen resolution of 1366 x768. I created a batchfile and set it with admin priv and it's great. In the process of evaluating 8.1 preview the touch screen calibration got way off. It was always a little exciting because where you touched it and what happened next were not really related.
Thanks again.
Click to expand...
Click to collapse
Do you still have that batch file around? I could use it
spiperman said:
I found this immensely helpful. Thanks very much. I used the utility to solve the calibration on a Dell Latitude 10 - which has a wonky native screen resolution of 1366 x768. I created a batchfile and set it with admin priv and it's great. In the process of evaluating 8.1 preview the touch screen calibration got way off. It was always a little exciting because where you touched it and what happened next were not really related.
Thanks again.
Click to expand...
Click to collapse
I actually have the same resolution. Would you happen to still have that batch file?
Was this not done a while back, people saying its complicated, really, the other thread had people doing it over 273 (iirc) touch points and that thread was huge and the thanks were coming in left and right..