[size=+2]DONATIONS[/size]
This will help me keep my girlfriend happy
GSoudBox is an application for HTC Windows Mobile phones with G-Sensor. It plays a wide variety of sounds. The sounds are triggered by shaking the phone using a variety of gestures.
{
"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"
}
[size=+1]Changelog:[/size]
Version 1.0.0.3
Improved: Sound Player
Fixed: Volume keys now minimize the application
Changed: Some skin images
Version 1.0.0.2
Fixed: Location of buttons in WVGA screens
Version 1.0.0.1
New: Option to turn on touch vibrations and sound pulse vibrations
Improved: Open sounds touch scroll list
Improved: G-Sensor sensitivity
Replaced: All instruments sounds and images
Changed: Some skin images
Version 1.0
Initial version
[size=+1]Notes:[/size]
Can be installed in memory or storage card.
[size=+1]Warning![/size]
This program is provided as is. It should not harm you device, but I recommend you to create a backup, before you start.
Anyway, I'm not responsible for anything you do to you device.
[size=+2]DONATIONS[/size]
This will help me keep my girlfriend happy
Please visit the new site
www.loffactory.webs.com
[email protected]
Nice! Trying it out now.
Anyone tried it on Omnia?
Regards
nice app
great idea, shame it doesnt work on my tg01
nice app.Gracias
opal dont have g-sensor nooooooooo
Works a treat on HD2
good stuff..
Nice will try this out thanks
looking good ..smooth..
installed on storage, and working fine on hd with stock rom..6.1
thank you
Looks fantastic. Giving it a run on my HD2. Need feedback/suggestions?
Really nice! But I have many problems controlling it via the g-sensor. I think it would be much easier if it would be a little bit like "Motion Drum":
http://www.youtube.com/watch?v=8yydDd727eE
Just 8 effects in a circle (or square) and a dot in the middle, which shows the movement of the g-sensor.
I love it
nice application
request QVGA...!!!! Please.
Installed and played with it only for a few minutes, but it is a hell of a lot of fun. I installed it with no issues on my HTC HD2. The program and interface is nice and simple, good image quality and user interface. The Home, sound and settings buttons at the bottom are a bit misleading. They look like HTC sense buttons which makes you first think you can slide across it with your fingers. They are however individual buttons and take a second before you enter the menu. Whichever it works, the buttons are OK, no oldstyle windows mobile look there. The instrument menu is great and user and touch friendly, so no issues there. The settings tab is simpel and clean. Have not had the time to get a feeling for the sensitiviy of the X, Y and Z axis, but I guess it is a question of trial and error. I think a small table in the help menu would be helpful to get insight into the settings.
I found it quite frustrating to use the G-sensor. When you hold the htc horizontally the Z-axis, or vertical axis is the middle box and works ok. The problem starts with the horizontal x-axis (or left and right shake). One side is one instrument and the other another. in the y-axis (or forward/backward shake) you have another 2 insturments that also seem to battle amongst themselves. This makes it difficult to create a harmonic beat. Also the G-sensor seems to have a "contra-coup" effect, in which a sudden change in direction in one axis of the x- or y-axis seems to cause a repeat of the same instrument. This is counter intuitive. The reason for this is that the postive axis (can) code(s) a different instrument than the negative axis. This applies for both x- and y-axis. You expect from a movement from the positive to the negative (left to right or visa versa, to-and-through) or visa versa to change instrument. This is not always the case. This makes this method of use with the G-sensor an unpleasant experience.
On the other hand the individual instruments can be tapped which works much better and is much more fun! 2 issues I have found is there is a lag time of the instrument sound when pressing it multiple times. Perhaps this issue could be solved. A second issue is that, although the HD2 is multitouch enabled, it apparently is not enabled in this app. I can only press one instrument at a time. Perhaps this issue could also be solved.
All-in-all G-soundbox is a must have app for the HTC HD2! Before its availability, however, a few usability issues with the G-sensor and multitouch need to be solved.
Installed and played with it only for a few minutes, but it is a hell of a lot of fun. I installed it with no issues on my HTC HD2. The program and interface is nice and simple, good image quality and user interface. The Home, sound and settings buttons at the bottom are a bit misleading. They look like HTC sense buttons which makes you first think you can slide across it with your fingers. They are however individual buttons and take a second before you enter the menu. Whichever it works, the buttons are OK, no oldstyle windows mobile look there. The instrument menu is great and user and touch friendly, so no issues there. The settings tab is simpel and clean. Have not had the time to get a feeling for the sensitiviy of the X, Y and Z axis, but I guess it is a question of trial and error. I think a small table in the help menu would be helpful to get insight into the settings.
I found it quite frustrating to use the G-sensor. When you hold the htc horizontally the Z-axis, or vertical axis is the middle box and works ok. The problem starts with the horizontal x-axis (or left and right shake). One side is one instrument and the other another. in the y-axis (or forward/backward shake) you have another 2 insturments that also seem to battle amongst themselves. This makes it difficult to create a harmonic beat. Also the G-sensor seems to have a "contra-coup" effect, in which a sudden change in direction in one axis of the x- or y-axis seems to cause a repeat of the same instrument. This is counter intuitive. The reason for this is that the postive axis (can) code(s) a different instrument than the negative axis. This applies for both x- and y-axis. You expect from a movement from the positive to the negative (left to right or visa versa, to-and-through) or visa versa to change instrument. This is not always the case. This makes this method of use with the G-sensor an unpleasant experience.
On the other hand the individual instruments can be tapped which works much better and is much more fun! 2 issues I have found is there is a lag time of the instrument sound when pressing it multiple times. Perhaps this issue could be solved. A second issue is that, although the HD2 is multitouch enabled, it apparently is not enabled in this app. I can only press one instrument at a time. Perhaps this issue could also be solved.
All-in-all G-soundbox is a must have app for the HTC HD2! Before its availability, however, a few usability issues with the G-sensor and multitouch need to be solved.
wow! will give this a try on my touch pro.
spy1983 said:
Anyone tried it on Omnia?
Regards
Click to expand...
Click to collapse
It's copied from the Omnia so why not use the original?
http://innovator.samsungmobile.com/caxixi/
Problem with Touch Pro2
Gsensor seems not work on TP2..
EDIT: I'm sorry, i changed sensor sensivity
spy1983 said:
Anyone tried it on Omnia?
Regards
Click to expand...
Click to collapse
The Omnia has a WQVGA = Wide QVGA screen (240*400) This app is only for (W)VGA(800*600 - 480*640)
So no need to try to see it isn't working.
@Loffactory
Are you planning a WQVGA (Omnia i900) version?
@drdionysius
Thanks
@Loffactory. Forget my question
Related
Without buttons, it makes most of them a bit useless.
I have mobipocket reader installed at the moment, and this will handle html and plain txt files, which are what most of the books I have are in, but I am wondering if there's anything better.
On the iPhone there's a really nice one that slides the pages up and down by tapping the top or bottom of the page, but I forget what it was called. I remember it cost about £5 though, but it was worth it.
Ideally something that displays full screen, will handle plain text and html, as well as other formats, and will turn the page by touching the screen.
The issue I have with mobipocket is the file and folder navigation seems really messed up, and you can't expand the column sizes when you want to look at the files in the open file window. With long book names you have no idea what they are
Any suggestions?
TIA
TRy these
I use mobibook too but have also tried these:
uBook: not bad but menu's a bit small.
Allreader+: pretty good but hard to figure out options
Tiny reader: poor
AlanJC said:
Without buttons, it makes most of them a bit useless.
I have mobipocket reader installed at the moment, and this will handle html and plain txt files, which are what most of the books I have are in, but I am wondering if there's anything better.
On the iPhone there's a really nice one that slides the pages up and down by tapping the top or bottom of the page, but I forget what it was called. I remember it cost about £5 though, but it was worth it.
Ideally something that displays full screen, will handle plain text and html, as well as other formats, and will turn the page by touching the screen.
The issue I have with mobipocket is the file and folder navigation seems really messed up, and you can't expand the column sizes when you want to look at the files in the open file window. With long book names you have no idea what they are
Any suggestions?
TIA
Click to expand...
Click to collapse
It's probably a good idea to use this thread
http://forum.xda-developers.com/showthread.php?t=449778&highlight=ebook
or maybe this one
http://forum.xda-developers.com/showthread.php?t=466638&highlight=ebook
Mobipocket is great for the commercial books in PRC format. I can touch the screen on the bottom to turn a page.
I also have AEB+ to map the volume buttons to up/down and I use it to rotate the screen.
I have to say, I haven't kept up to date with the latest bells and whistles versions, but for years I've used, and am happy to entirely recommend iSilo.
It will read various text formats, but most conveniently comes with a converter for making your own custom ebooks - and helpfully, this can be fed a load of html files, so I often decompile ebooks distributed as chm files, and then convert them into isilo books that I can read on the road, which is excellent for massive reference works like Britanica etc. These are also highly compressed, and settings and last reading position is saved per book.
The version I'm using is probably old school, but as I said, it works perfectly and I've had no reason to upgrade. Helpfully on the Blackstone, it has user assignable buttons and screen regions, so eg clicking the top 25% of the screen will page up, or the middle 25% will auto scroll etc. This makes it ideal for the Blackstone with no usable buttons.
Black on white in portrait:
{
"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"
}
And landscape view:
V
I like mobipocket, I have used it for years, and even on my N95, but I find tapping the screen is very random, sometimes it works, sometimes it highlights some text, and sometimes I have to tap it several times to get it to change. If I use a styus, it's fine, if I use two hands, and ise my fingertip it's fine.
iSilo looks like it may do the trick though, although I didn't think it handled plain txt files?
Only problem I have with using the volume keys to change pages, is that they are not designed for repetitive use, I managed to break the switch on my N95 by using it for changing page.
I will have to investigate more I think, I just wish there was one as nice as the iPhone reader I had.
(I just wish to point I used it on an iPod touch, not an iPhone, because I hate them lol)
iSilo certainly supports plain text, a couple of other ebook styles, HTML I think, and it's own format.
I really like using it - it also has autoscroll if your hands are otherwise "occupied"!
V
Well I won't be reading *those* kinds of books
OK I have had a more in depth play with isilo, and it does the job in a buggy kind of way.
Takes a bit of messing around, and looks as though once you go into full screen you cant get out without making it look a bit messed up, so you have to restart the app, but it's certainly better for page turning than mobipocket!
Doesn't have the bells and whistles of others, but it's a free reader, and it does the job effectively.
Cheers V
Regarding the bug coming from fullscreen, I noticed that but thought it was just my old version.
The way to get around this, is instead of pressing the "ok" (back arrow) button to get out of fullscreen, press hang up instead. This will revert it to a normal size window, without the bug.
V
http://forum.xda-developers.com/showthread.php?t=449778
I have a ton of .lit so although i like Mobipocket it isnt of use. So I use TinyReader it's ok i suppose it definitely beats MS Lit reader. I wish someone would make a good reader for .lit files.
Ever dreamed of playing those good old SNES and Genesis games with your Touch HD ? Your dream comes true !
Let me present to you my new skin:
WVGA-MT-Dredd67 v0.3
{
"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"
}
What you need:
- Morphgear 2.4.0.9. you can get it from here : http://www.spicypixel.com/web/page/morphgear/Download.aspx
- Some Morphgear modules (each emulator has to be bought separately)
- Some Roms (google for them, no roms here).
- My skin
Installation:
1) Extract the files in the zip and copy them directly into:
Code:
\Program files\Games\Morphgear\Skin[B]s[/B]
2) In Morphgear's global settings be sure to have:
* uncheked "Disable Full Screen"
* checked "Use Virtual Pad"
3) In Morphgear's SNES (exemple) settings be sure to select:
*Skin: Name: WVGA MT Pad v0.2 by Dredd67
Troubleshooting:
-If the skin doesn't appear is the skin list, removed all others skins that could have been placed there.
-If you start a rom and the Pad doesn't show, be sure to go full screen by pressing the center of the screen.
-I won't do the support specific to Morphgear, I assume you know how to use it or you are able to read the guides on Morphgear's website.
Advises:
This skin provides fake multi-touch support (See the release notes for details). To got it to work you need to press simultaneously two virtual buttons. And you need to be quite precise even if I have tried my best to build this skin as finger-friendly as possible. So for best game experience here is what I suggest:
- Lay down your HD on flat surface (I put it on my pouch on my desktop), the device is easier to manipulate this way.
- Unprecise pressing is OK as long as you don't expect multi-touch.
- For multi-touch to work, you need to position your fingers properly, use your indexes or even better, the tip of your indexes.
- Some games use unusual combinations which are probably not mapped (see release notes). I can't map them because of the calculated multi-touch principle and the space I have to layout the buttons.
- This skin is mainly designed for SNES games. You will have to edit the .txt file to make it work properly with other modules.
- Don't press between the DPAD and the buttons, this is the place where the hidden buttons are. Expect some unexpected moves if pressing there
Release notes:
03.03.2009 : First version.
04.03.2009 : v0.2 : New layout for better multi-touch support.
Buttons that are mapped:
A, B, X, Y, N, S, E, W, NE, NW, SE, SW.
Combinations that are mapped:
A+N, A+E, A+S, A+W, B+N, B+E, B+S, B+W
Advised settings for Morphgear for best performance
Global Settings:
- Driver: Auto
- Frame Rate statistics: Unchecked
- Disable Full screen: Unchecked
- Orientation: North
- Enable Sound: Unchecked
- Use Virtual Pad: Checked
SNES9x Settings:
- Screen Size: Autoscale
- Image smoothing: Unchecked
-Sound: Everything Unchecked
-Frame Skip: 2 (or 3 if the game really needs it)
-Auto Sync: Uncheked
With these settings you should get roughly between 55-60/60 fps
Additional information
You may be interested in reading this thread:
http://forum.xda-developers.com/showthread.php?t=486268
This is where everything started, this skin is just a first result of our investigations. Now the principle should be generalized to any application if some devs want to give us a hand.
Just a mirror for those having trouble downloading:
http://rapidshare.com/files/211370608/Morphgear_Gamepad_fo_Touch_HD.zip
thank
thank its very amazing
unbeliveable this is fab!!
Thanks a lot for this, I tried it and it works fine!
Great job!
Will it be possible to use it when the phone is horizontal one day?
xr2i said:
Thanks a lot for this, I tried it and it works fine!
Great job!
Will it be possible to use it when the phone is horizontal one day?
Click to expand...
Click to collapse
We are working on it, but it will be different application, because Morphgear's limitation doesn't allow this.
Look at the link at the end of the 1st post, this is where we are actually.
At my knowledge, it's very hard to have a vpad in landscape mode with Morphgear, because its hardcoded to pop-up UNDER the game screen, which means a few line of pixels...
idea is simply wonderfull , but still need to be better performed
Ciao! Good Job !
Good job
Wow man! Excelent job!!
Sounds AMAZING! I will test it right away ... THX man
All is good,
just to correct the directory skin with skins to extract your skin files
thx
thanks for this!
tested on sonic 1 and 2 for mastersystem and super mario world for snes and works like a charm!
great work
Dredd67, your´re the one! Thanks for this. The best Skin and (even better) supports "multi-touch"
Hi
Why i only have a small control, how can i change it to bigger size?
thanks.
can you make a VGA version Multi-Touch for the diamond ??
davtheultimate said:
All is good,
just to correct the directory skin with skins to extract your skin files
thx
Click to expand...
Click to collapse
+1 true
mailmaarnaarluc said:
Hi
Why i only have a small control, how can i change it to bigger size?
thanks.
Click to expand...
Click to collapse
Ha ve you selected the right skin in your module's settings ?
Aqrab said:
can you make a VGA version Multi-Touch for the diamond ??
Click to expand...
Click to collapse
I could try, but I think it will be too small to be really usable.
Zepiii said:
+1 true
Click to expand...
Click to collapse
What's the problem with the directory, I'm not sure what you are referring to ?
will download and test it...thank you...
Nice work on the skin, thanks!
I only tested it on the SNES emulator, but I can't get the games to run properly on my HD. I tried changing all the video and audio settings, but it just runs very sluggish. Any ideas?
MrData said:
Nice work on the skin, thanks!
I only tested it on the SNES emulator, but I can't get the games to run properly on my HD. I tried changing all the video and audio settings, but it just runs very sluggish. Any ideas?
Click to expand...
Click to collapse
Try to disable sound, fps stats, and screen smoothing which is a incredible performance drainer.
Note that it will never be as fast as on other devices, due to the lack of proper graphics drivers.
Dredd67 said:
Try to disable sound, fps stats, and screen smoothing which is a incredible performance drainer.
Note that it will never be as fast as on other devices, due to the lack of proper graphics drivers.
Click to expand...
Click to collapse
Tried that already, I guess I can get an ok framerate with no sound, a tiny screensize and no smoothing, but where's the fun in that?
Besides, this guy:
http://www.youtube.com/watch?v=CL2mUeR2KOQ
is clearly running morphgear at perfect framerate?
{
"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"
}
Thanks to all betatesters for their help and I apologize for all bugs and inconveniences.
FAQ:
Q: When I start the app I got a error: "mToolbox.exe TypeLoadException". What can I do?
A: Try a softreset, it's known problem when your RAM is quite full.
mToolbox is a multifunctional sensor app. It's like a Swiss knife but without all the hardware functions. mToolbox is using the built-in sensors of your device. So in this version the light sensor and the G-sensor are supported. Maybe I add the support for the stylus sensor in a further release.
You'll have:
water level
light sensor
ruler
angle meter and
shock sensor
It's very important that you report me every error (maybe with screenshot). That's the only way to make the app bug-free. Report here or send me an email to: error ( a ) dev.etechniker.com
Overview - Features, ToDo and System requirements
Changelog
Screenshots
Download
Suggestion are welcome on every time.
If you like this app, I would be very happy if you donate me a coffee or two.
If you want you can "follow me" and the progress on twitter.
Looks awesome, I would like to see this toolbox available in all ROMS as a standard.
I already PM'ed you about beta testing it for you.
I have an Omnia (WQVGA). G-sensor apps work by having the htc gsensor api dlls.
How about adding a g-sensor pedometer function?
Also what happened to mFlash? It was a usefull tool (too bad the standby/hibernate function and the power button of the phone would turn off the flash led... it needed a button to turn of screen). I think it would be a nice addition to the toolbox.
Merlot check your mail, I've sent you the testing results.
frmariam said:
I have an Omnia (WQVGA). G-sensor apps work by having the htc gsensor api dlls.
How about adding a g-sensor pedometer function?
Also what happened to mFlash? It was a usefull tool (too bad the standby/hibernate function and the power button of the phone would turn off the flash led... it needed a button to turn of screen). I think it would be a nice addition to the toolbox.
Click to expand...
Click to collapse
Yes you're welcome to try the beta version. Look at the first post where I added the download link to the beta vesion.
What exactly do you mean with pedometer? Do you mean a step counter?
Sorry that I can't continue with mFlash but without a device with flashlight it's not possible.
Looks interesting... will stay in touch...
I'm going to download this and try it out. I have the HTC Fuze (aka Touch Pro)
The buttons are quite large for the VGA device right now and some of the buttons have a hard time actually working. Meaning it takes a while for me to actually get into the tool I want.
I know I was supposed to e-mail you, but thought this might be easier.
I am working on the screenshots.
I have a Blackstone, EVO IIIt cooked ROM (wm 6.1, Manila 2.0, NetCf 3.5, localized IT). I cannot even start the app:
Code:
mToolbox.exe
TypeLoadException
Same error with version 1.3
xtremekilla09 said:
The buttons are quite large for the VGA device right now and some of the buttons have a hard time actually working. Meaning it takes a while for me to actually get into the tool I want.
I know I was supposed to e-mail you, but thought this might be easier.
I am working on the screenshots.
Click to expand...
Click to collapse
Same Problem here (diamond VGA). Buttons must be pressed hard and often before i get any reaction. Also text, for example in thre ruler app, is cut off on the right side, or overlapping. Also the program is running VERY slow (don't know if that's because of my rom) Exit Button does not work for me, i think (killed the program by taskmanager after waiting 30 seconds).
I'd love to help you beta testing, but at the moment the app is not really usable on my device.
idea..
Flashlight app
nice app, works great here on HTC Touch HD.
Thanks for your hard work!
I get error when starting program
mToolbox.exe
TypeLoadException
Touch HD - stock rom
looks awesome
I've made some changes and uploaded version 0.2.1 beta. Please use the download link in the first post and try the new version.
*some changes in the resolution calculation
*fixed some bugs
nhvoltagenh said:
idea..
Flashlight app
Click to expand...
Click to collapse
Flashlight. I fully agree. Would be nice and sometimes useful.
Some things I have noticed,
In the shock section, it will freeze sometimes when logging is on (tested on AT&T Topaz rom, but on my custom rom it works ok so far.)
Also the info section, it would be better to color the x y z letters to show what they are on the graph. and maybe a set of guides as to what the graph should look like when the phone is laying flat up with no movement. That way you can get an idea of the angles as well. and a way to record and view a log (while in the app, i do see a record button, but no intuitive way to read such log)
Also the page animations are slow (switching between menu and the sections of the app.)
Other than that I love this application and plan on cooking it into my roms as soon as it is closer to being finished, if that is okay anyway.
Ok, so I finally got around to posting these screens.
Here is what I have:
My device:- HTC Touch PRO (VGA)
mToolbox version:- 0.2.1 BETA
So here are the screen shots:
- The splash screen has some overlapping.
- The red marking in the third screen, shows the areas that respond to touch. I can only touch that area of the button to activate that tool.
- I didn't include the screen for light sensor because my light sensor is off for now, and I reached the limit for attachments in a post (its 8 attachment per post).
View attachment 207593View attachment 207594View attachment 207595View attachment 207596View attachment 207597View attachment 207601
The water level, 'angle' and shock sensor all worked perfectly. Its just a matter of resizing them. As you can tell Water level is way off the target. The 'angle' needs a bit of tweaking and the shock sensor is ok.
The App is still a bit sluggish when I go to any tool.
Some cool things I did notice were that I can just slide from left to right to get back to the main menu and the arrow in between Back and Exit is really useful to gain more screen space.
Awesome tool, merlot. Hope we can get this working on VGA devices.
I too have Samsung Omnia SGH-i900 running a WM6.5 ROM (build 23007) by Sector. After installing the 0.2.1 beta .cab and tapping the icon in start menu I just can see the initial splash screen and then the app crashes without any explanation.. I have > 40 MB free RAM so that shouldn't be an issue. An suggestion ?
P.S: for those of you interested in mLight, I recommend moving to TorchButton, which currenly has lots more function (ideally to be integrated in mToolbox !)
the website seems to be down atm
edit: its working now
SciLor's GSensor Control Preview v2
{
"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"
}
SciLor's GSensor Control is a tool for converting your Gsensor in a Dpad .
Choose from to modes: Analog Emulation or Digital Pad.
Analog Emulation sends the more keystroke the more you tilt your device
Digital Pad just holds the button in the direction you tilt it. If you put your device flat again the button is release.
You will know to be able to press enter by pulling your device up.
Readme:
Code:
SciLor's GSensor Control Preview v2
i.
.7.
.. :v
c: .X
i.::
:
..i..
#MMMMM
QM AM
9M zM
6M AM
2M 2MX#[email protected]
OM tMMMMMMMMMM;
.X#MMMM ;MMMMMMMMMMMMv
[email protected]@
[email protected]
[email protected]@#$BWWB#@@#$WWWQQQWWWWB#@MM.
MM ;M.
$M EM
[email protected]@@@@@@@@@@@@@@@@@@@@@@@@@@@#OMM
#M cM
QM Another Cake by tM
MM SciLor CMO
.MMMM oMMMt
1MO 6MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM iMM
.M1 BM For all Portal Lovers! vM ,Mt
1M @M............................... WM M6
MM .A8OQWWWWWWWWWWWWWWWWWWWWWWWWWWWOAz2 #M
MM MM.
@MMY vMME
UMMMbi i8MMMt
[email protected];;i.......i;XQMMMMMMt
;[email protected];.
ReadMe
You will need .NET CF 3.5 (and a device with a g-sensor of course) - Link at the Bottom
This is a g-sensor d-pad emulator. Just tilt your device for sending up/down/left/right/return.
For sending the return button just pull your device upwards.
-Analog Emulation tries to send the more keystrokes the more you tilt your device
-Digital Pad sends just holds the "button" as long you tilt your device in that direction
You will always have to run the application to make it work. There is not background process (yet).
Beware, Alpha status!
ToDo:
Additional:
Known Bugs:
If you like my hard work PLEASE DONATE! :)
http://www.scilor.com/donate.html
ChangeLog:
Preview v2(2010-03-27)
-Enhancement: Pull your device upwards to press enter.
-Fix: Less CPU ussage to stop lagging.
-Internal: Recoded everything for future use of new features
-----------------------
Preview (2010-03-23)
-Initial Preview Release
---------------LINKS-------------------------
My Website: http://www.scilor.com
SciLor's WiMoBlue Website: http://www.scilor.com/gsensorcontrol.html
Donation: http://www.scilor.com/donate.html
-
DotNET CF 3.5: http://www.scilor.com/gsensorcontrol.html
Download/More Info: http://www.scilor.com/gsensorcontrol.html
WOW need to try this!
sounds verry intresting!
Totally off topic, and please forgive this post But what program is that your using to show open programs in tha top taskbar? i had tha App, SD card corrupted and have no clue...
Again i Apologize
Thanks for any help..
Oh and your app seems cool.. i Will test it
NICE! Congrats! Keep Going!
criminalogic said:
Totally off topic, and please forgive this post But what program is that your using to show open programs in tha top taskbar? i had tha App, SD card corrupted and have no clue...
Again i Apologize
Thanks for any help..
Oh and your app seems cool.. i Will test it
Click to expand...
Click to collapse
Search for WKTask
Wow, this is quite innovative. Gonna try definitely.
Nice but can I suggest something?
I completely agree, this is what button less devices need. I can't believe there are no proper working versions of tilt scrolling are available. G controller and D pad seem promising but are not really getting far.
As far as I can see you only need two things to get this working great.
1: Device centring so it can be calibrated to a normal holding position for neutral.
2: Maybe a map to a button to pause it - so, for instance, hold the volume button so stop it scrolling once you are where you need to be - or the other way round - press a button to un-pause it and allow scrolling.
If you could get it to emulate finger scrolling - like moving around a webpage or document - that would be awesome.
Good luck - someone's gotta get this working
Nice ideas, I will take them into account Feel free to post future suggestions in my Forums so I can better keep track of them!
tested
I tried this on my Imagio this morning (6.5). Didn't appear to work (I could have been doing something wrong but it seems like a pretty straight forward deal). I tested it on the Total Commander menu and the PHM Registry menu. It did not respond to either of the 2 options.
I tried installing on device memory and storage card. I did several soft resets. I reinstalled. I have zoombar plus installed. that turns your zoombar into a d pad by sending keystrokes- could that cause a conflict with this app?
**EDIT** So I uninstalled both. Reinstalled GSensor. Still not working for me. Looking forward to further development though.
To bad Do you have any GSensor build in? Does other software work that uses this sensor (HDWobble/HD2Wobble)?
GSensor
I do have a G Sensor built in. I have the game Teeter (labyrinth) . Works like a charm.
I will come back to you, if I continue working on it
Brilliant!
I've just installed it on my HD2 (using Duttys HG v0.9 WWE).
The only App I really want to use it in is MS Reader & I can confirm that it works there. However, there are a few enhancements needed before I'd add it to my permanently installed programmes ...
1.) Sensitivity setting ... it's far too sensitive (analogue or digital) ... I'd prefer it if a definite movement was needed, as it is, the slightest adjustment of angle (and none of us are rock steady! ) triggers the app.
2.) The ability to automatically enable or disable depending on which application had the focus (i.e. a whitelist & a blacklist) ... was a bit disconcerting when my home-page suddenly started switching tabs, etc!
3.) Calibration for centering (as suggested by Toggs) ... I definitely don't use my phone perfectly flat, but hold it tilted at all times ...
4.) ?? Mapping of the G-Sensor direction ?? i.e. I'm fine with left-tilt/right-tilt being page forward, page-back. But it would be nice if up-tilt/down-tilt were mappable to something else.
5.) This is 1. & 4. combined ... would it be possible to be selectively sensitive? i.e. set the up-tilt/down-tilt to a low (or zero) sensitivity & the left/right higher?
Thanks for a great addition to my HD2 experience. I'll definitely be donating once it's out of beta!
Thank you for your suggestions. I wil do my best to include that
SciLor
Does nothing here on my Touch HD
What should it do?!
Do I have to start that program to work or is it autostarted after a soft reset?
Should it "simulate" d-pad right button when i do this with my phone?
Doing nothing for me either. I am really looking to try this & spread word about it...Let me know if I can be of any help. I tried both ways but not working..actually nothing happens actually. Using TP2 unbranded with g-sensor enabled.
Nice, gonna try this.
btw. why are you giving me the finger in your readme
pmbellis said:
1.) Sensitivity setting ... it's far too sensitive (analogue or digital) ... I'd prefer it if a definite movement was needed, as it is, the slightest adjustment of angle (and none of us are rock steady! ) triggers the app.
Click to expand...
Click to collapse
Yes, that will be great. For now its to much.
Maybe its nice idea to measure the curent state (position) of the device and use that as 0 position (starting) for G-Sensor every time we starting this software
I will do my best to give you a nice experience. I am currently planning that you can set up a standard behavior and you may also set special behavior for applications. You may choose if the GSensor should be calibrated on the programs startup automaticly, you may pre calibrate it for the application only or use the standard you set.
Mhh I hope I find enough time to make that features soon
SciLor
PS:
What about running it as a process, seperated from the config tool so there is any need of an open window in the background.
0. I'm new user. I cannot make any links. remove replace ^ to .
1. Short english.
I'm not native English speaker. My grammar is bad.
2. Sweeter jellybean 4.3! Faster, Smoother, More Responsive.
: According to Android developer page, touch latency has been improved on Android 4.3.
3. TouchMarks - Test about <= 4.2.2 Devices.
: GSG4, HTC One, MotoX. they're all <= 4.2.2
4. So I built my own touchmark device.
Sensor/device :
{
"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"
}
CdS Sensor/ and resistor for voltage dividing.
Button / pull-up resistor.
I have only one phone/camera, so my whiteboard eraser will show how the experiment environment is set.
As you know, the plastic button cannot make a touch input, so I attached some conductive film which will make a touch input when the button contact on the screen surface. I taped screen around to minimize false inputs.
Android App, Arduino code :
github dot com /foriequal0/TouchTest
5. Experiment.
a button contact on the surface -> arduino will record the timestamp
-> touch event will arise -> screen will brighten
-> CdS sensor's resistance will change -> Arduino will record the timestamp, and send latency time to the computer.
Button's stroke is very short (<1mm) and I touched screen very fast so, time difference between button click and touch input can be neglected.
I've tested on these devices
GNex : JB4.3, Rooted, recent Fancy kernel, zRam enabled, Governor OndemandPlus(governor change won't made big difference)
SGS2 : JB4.1.2(Korean, SKT), My friends' own. no rooted, many apps installed.
SGS2 : Gingerbread(I forgot the build number. Korean. SKT), Factory resetted.
Optimus G Pro : JB 4.1.2(Korean, LG U+), My colleague's.
6. Result.
GNex
x axis : sorted sample.
y axis : response time(us)
left tail and right tail may be false input/lag caused by background apps.
uniform distribution between [75ms, 92ms]. note that interval of 1 frame on 60FPS is 16.6ms
SGS2(JB):
uniform between [115ms, 150ms]. I think there might be some synchronization failure. touch response distributed on 2 frames.
SGS2(Gingerbread):
uniform between [100ms, 120ms], but have smoother tails than SGS2's
OptimusG Pro:
Fairly better than samsung's. I don't know why.
Have anyone a question/improvement/objection?
Nexus 5 response time
Hi there, great experiment, seems like android response time isn't so bad after 4.2
Just wondering, would you be able to get your hands on a new Nexus 5 and do the same test? apparently it has good touch screen which should result in a low response time.
Or someone could also do a complete Touch+Audio latency test. This is the way I like to do it:
Install a musical app, either drumming or keyboard.
Install a sound recording app,
Start recording audio and give the screen a good tap in the musical app, this way both the "tap" and resulting drum or keyboard sound will get recorded.
Open that saved .wav up in audacity then zoom in and observe the visual audio waveforms then measure the distance between the TAP and the sound actually playing.
On my devices I was getting around 175ms if the particular music app used the "Sound Pool" class or 250+ if using "Audio Track" I'm running android 4.2.
I hope you or some lucky dude with a Nexus 5 can do this test, there are dozens of nexus 5 reviews popping up online but NONE provide this sort of information, and if anyone wants the Nexus 5 for real-time music creation we need to know this info, and we need to make it public
**I know the test isn't accurate down to the ms but it is accurate to around 5-10ms which should be good enough to gauge its approximate performance.
Hi! and thank you for your reply!
ianmere said:
Hi there, great experiment, seems like android response time isn't so bad after 4.2
Just wondering, would you be able to get your hands on a new Nexus 5 and do the same test? apparently it has good touch screen which should result in a low response time.
Or someone could also do a complete Touch+Audio latency test. This is the way I like to do it:
Install a musical app, either drumming or keyboard.
Install a sound recording app,
Start recording audio and give the screen a good tap in the musical app, this way both the "tap" and resulting drum or keyboard sound will get recorded.
Open that saved .wav up in audacity then zoom in and observe the visual audio waveforms then measure the distance between the TAP and the sound actually playing.
On my devices I was getting around 175ms if the particular music app used the "Sound Pool" class or 250+ if using "Audio Track" I'm running android 4.2.
I hope you or some lucky dude with a Nexus 5 can do this test, there are dozens of nexus 5 reviews popping up online but NONE provide this sort of information, and if anyone wants the Nexus 5 for real-time music creation we need to know this info, and we need to make it public
**I know the test isn't accurate down to the ms but it is accurate to around 5-10ms which should be good enough to gauge its approximate performance.
Click to expand...
Click to collapse
Hi! and thank you for your reply!
I checked this thread for a long time. sorry for the late.
I highly inspired by your audio latency experiment!
I lately bought a new nexus5 and now I'm full with willingness to build new experiment on it, but unluckily I'm very busy day and night. I have to be stucked in my office for a while
Whenever I get some new results, I'll promise not to hesitate to post it on this thread.
Thank you.
Trying to replicate your experiment
Hello foriequal0,
I have tried to replicate your experiment with little success.
Here are some pics of my setup (Arduino Uno)
Note the conducting film around the switch (not easy to see) to make contact with my finger
and some results...
Not sure what might be the conclusion (especially for trial 3 - D2-727 tablet).
I am concerned whit the high variability of my results ...
This is my first post on a forum so please indulge if it is not perfect!
2014 May 1st addition:
After many tests, I achieved more stability and here is the result for the D2-227 Android tablet: