GNex JB4.3 touch response time experiment : 85ms - Samsung Galaxy Nexus

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:

Related

[VOTE THE BEST]SciLor's Fuel Blaster vs. LulzSoft's Gasmate

SciLor's Fuel Blaster vs. LulzSoft's Gasmate​
Gasmate:
http://www.lulzsoft.com/
SciLor's Fuel Blaster:
http://scilor.ac-host.net/fuelblaster.html
Hello, I would like to now if it is worth to continue developing my Fuel Blaster due to a similar program by dlichterman (Gasmate)
I'll try to show all features of each program and you can decide what program you like more.
BEFORE VOTING TAKE A LOOK!, WOULD BE NICE TO GIVE SOME FEEDBACK!
First of all Screenshots:
(Showing all available Screens/Pages)
{
"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"
}
Then a table comparing features
Feel free to vote for the best, not just to me for writing this. (I tried to show the best of both tools!)
Reserved for later use
vote no.4
Reminded me on Brewster's Milions "Vote for None of The Above" campaign
j/k
in my opinion, both apps are good, I just would like them to have some of the eyecandy
I disagree with Gasmate 'Stylus is a Must' statement.
I have been using Gasmate for about 2 months and find that I have YET to need my stylus to use it.
Only thing missing from Gasmate currently is multiple vehicles, but author is polishing the program for single vehicle currently and then promises to support multi vehicles when fully released.
Thank you for your response, but in my opinion on my QVGA device I is really difficult to press the tabs without hitting the exit/about button and this is very anoying
I agree that it would be nicer if the tabs were more finger friendly but it can be done without a stylus.
scilor said:
Thank you for your response, but in my opinion on my QVGA device I is really difficult to press the tabs without hitting the exit/about button and this is very anoying
Click to expand...
Click to collapse
Looks like an excuse to buy a new phone
600€ for a kaiser...
So I want to use it for some time
nice you found the thread dlichterman
scilor said:
600€ for a kaiser...
So I want to use it for some time
nice you found the thread dlichterman
Click to expand...
Click to collapse
Holy crap thats expensive. I only paid 240 for my touch pro(with 2yr contract)
I without a contract
And the bloddy s**t is that the value of a used kaiser fell to 300€...
I like your Fuel Blaster better.
The following are some of my impressions of Fuel Blaster vs Gasmate. No offense to either creators, these are just my opinions. I'm providing my feedback so maybe each creator can improve their programs. You're both awesome for making programs to help us all.
Pros
- Fuel Blaster's interface feels & looks better, Gasmate seems too "basic"
- Fuel Blaster's summary page is more in depth
- Fuel Blaster has Graphs
- Fuel Blaster has Customizable Units
- Fuel Blaster utilizes WVGA, Gasmate is only VGA (doesn't utilize the full screen for WVGA screens)
Cons
- Gasmate has different fuel types & grades
- Gasmate has Maintenance Records
- Gasmate has changeable date for Record Entry, Fuel Blaster is set to the time you enter the Record (what if you forgot & enter it the next week?)
- (Minor) Gasmate uses a decimal point "." instead of a comma "," (I know some places uses a comma for a decimal point but I don't like it)
Suggestions
- I would like to see Fuel Blaster with selectable different profiles for different vehicles. That way if I have multiple vehicles, I can keep track of them all. (I have a car & a motorcycle).
Thank you for your feedback
I will take a look at your suggestions in the next release
Add FuelLog to this comparision. I use it third year (maybe longer...?) and it works ok (but could be better). What I miss in FuelLog is multicar functionality, and multifuel (I have gas+LPG). Also very usefull would be possibility to synchronize with websites, which tracks fuel consumption (export/import) like www.motostat.pl
I would love to see a simpler "just fuel log" finger friendly "pretty" interface.
I boot up and it has a date field but its already filled in (I can change if need to)
tap miles I enter my miles traveled (my odo is 1.05 off so odo readings are worthless I use trip meter readings because I have larger tires)
it should guess by prefilling with the last miles I used.
tap fuel and plop in gallons used (it should guess by putting in the last amount I used and use 2 decimal places)
being able to "slide" the values would be nice. IE say I went 442 miles but last time I went 402 and it fills with 402. I just "slide" my finger over the 0 4 times to make it a 4 hit done.
this would make entry super slick super fast.
THEN the final punch. some way of "integrating" with sites like "ecomodder" to "sync" my log with the site automatically right over the air.
that would rock
Data Entry Is Problem for Both
Both programs require multiple taps to enter each digit. This is time consuming. Another program, MPG Tracker, displays a numeric key pad when you tap into each of the fields - miles, gallons, price. So data entry is faster and easier.
The biggest problem I have with Fuel Blaster is that I entered the data, and tapped on the Save button but nothing happened. When I moved to another screen, my entries had not been saved. I had to do this three times before I finally got a message asking if I wanted to create another data set. I tapped Yes, and my data was saved. I have no problems with my screen responding to taps in other programs. I can't understand why the large Save button does not easily save my data - and I don't need a confirmation screen; just save the data.
Gas Mate has not been updated since 2009 and the design reflects the old stylus entry screens.
All three programs need better Exit methods that actually shut down the program and remove it from memory. Many programs do thnis, so it can be done.
I will test all three for a while, but right now, MPG Tracker appears to be better for recording fuel consumption. It allows for different fuel grades and multiple vehicles. If I used my vehicle for business, I would probably get one of the better, paid programs that does more.

[APP] GSoundBox v1.0.0.3 (VGA, WVGA) (G-Sensor)

[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

[2010-03-27]SciLor's GSensor Control Preview v2

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.

Guitar Hero

Is there any (good) Guitar Hero (or sort of) for X1?
I don't think, that any guitar hero style game would work properly on the X1, because X1 doen't support multi touch. I tried a sort of guitar hero game and it was hardly playable.
nos2k5 said:
I don't think, that any guitar hero style game would work properly on the X1, because X1 doen't support multi touch. I tried a sort of guitar hero game and it was hardly playable.
Click to expand...
Click to collapse
Ok, thanks for the reply. I keep looking for it
Touch The Music
Beta, but interesting and worth supporting
Arlanthir said:
This is the official development thread for Touch The Music.
All information is going to be posted here.
The project consists of a music game, similar to Guitar Hero and Tap Tap Revenge, for Windows Mobile 6 onwards.
Development Team
Programming
Arlanthir
Graphics
Previously: Jakob Dam (jakobdam)
{
"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"
}
​
Announcements
- Version 0.31 out
- The OPTIONS Menu doesn't work yet.
Latest Version (0.31)
Download
QVGA
VGA
WQVGA
WVGA
Squared QVGA (discontinued)
Squared VGA (discontinued)
How to play
You can tap the fret buttons on the lower part of the screen or you can use LEFT UP RIGHT hardware keys to play.
If you want to quit the level, just press the RED (end call) key. Alternatively, you can click the top right corner (where the framerate counter is located).
Please note that with the hardware buttons you won't be able to net those multitouch points. A singletouch easier mode is planned for future versions.
Changelog
Version 0.31
Debug information added.
DirectShow error checking added.
Version 0.3
Major graphic overhaul
Pause
New scoring method
Vibration Feedback
FIX: Experimental bugfix for when receiving messages and calls, etc. The program should now behave fine when losing focus.
Version 0.2
Multitouch working.
New menu system, with placeholder graphics.
New level (incomplete).
New resolutions.
Version 0.1
The first playable level is released on a simplistic game engine.
The Options Menu doesn't work yet.
Planned features for next version
...
Planned features for FUTURE versions
There is going to be a music editor for PC (at least) so you can create levels. The process won't be automatic, though, because we cannot make a program that guesses where the guitar is in the music by itself. So you are going to place the notes where you feel is right.
Note animations when you tap them.
Options menu.
...
Known Issues
I can't access the Options menu!
It's not working yet!
If the application below the game updates the screen, Touch The Music no longer recognizes touches or keystrokes
To be honest, I don't know why this happens but it will have to be fixed. Starting the game from the programs menu or the manilla programs tab minimizes this, as long as the messaging tab is not visible. (experimental fix in version 0.3)
The game does nothing!
This is a problem with some hidden GAPI calls I may be using... Try this fix: http://forum.xda-developers.com/showthread.php?t=532200
I have no Sound
If possible, change your ROM. If not, try the latest version and tell me all the eventual error messages.
Multitouch isn't working, my device has got no multitouch support!
Multitouch for Touch the Music is entirely software-based. It should work on any phone without hardware multitouch (yeah I know, mixed roles here).
If it doesn't on yours, try the latest version out and send me your log.txt
How can I make my own track levels?
I recommend using a program like audacity to open the mp3 file. Then, check the timing of the notes and write them in a text file as such:
<note type> <time>
Time can be absolute (i.e. 3000 = 3 seconds since beginning of the song) or relative (i.e. +1000 = 1 second since PREVIOUS NOTE). Please put in an absolute note for reference once in a while.
Note types can be:
L - left
M - middle
R - right
< - L + M
> - M + R
v - L + R
So for example, a simple music could be:
# This is a comment
# Intro of simple music
L 2000
R +200
M +300
R +200
< 5000
> +500
# Chorus. Note the absolute timing for reference
R 7000
L +200
R +200
M +300
etc......
Always remember, higher pitch (acute) notes should be on the right. I can't tell you enough to look at the track1.txt in the tracks folder of the game, to understand what I just said.
When you want to test it, convert your mp3 to aac and save it in the tracks folder as well as the txt with the notes script. Rename them both to track1.aac and track1.txt.
Thank you all for your time and especially the users who are contributing with testing, ideas or just kind words, you are all that makes this project possible.
Click to expand...
Click to collapse
Thanks! I'ma try it out.
http://www.microsoft.com/windowsmobile/en-us/totalaccess/software/games/guitarhero3.mspx
Sera_6969 said:
Touch The Music
Beta, but interesting and worth supporting
Multitouch for Touch the Music is entirely software-based. It should work on any phone without hardware multitouch (yeah I know, mixed roles here).
Click to expand...
Click to collapse
The version i tried had no multi touch support on my X1.
orelsi, I'ma try your link right now .

[APP] Altimeter - BETA v0.4 (Feb 7th)

Thought I'd let people know about a new app coming out in the next few days (workload dependent). As we know, the Galaxy Nexus has a barometer inside, but it's essentially isolated from the rest of the system.
This app uses the barometer to simulate an altimeter - a surprisingly sensitive one at that.
{
"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"
}
Features:
* Hardware accelerated via OpenGL - no lag whatsoever with smooth analogue and digital updates
* Automatic pressure setting download
* Multiple themes
* Light CPU and memory footprint
* Metric and imperial units - metres / feet, and hPa / inHg.
Coming soon:
* Better landscape support
Compatibility:
Anything with ICS and a barometer. It'll probably (definitely) crash if you try it on something without.
Feature suggestions welcome!
[v0.4 Beta Released]
Attached is a preview release of the app. Please bear in mind that it's a very, VERY early alpha of what the final thing is going to be like for anyone interested in testing it.
What works:
* Correct indications (both digital and analogue)
* Correct vertical speed calculations
* QNH adjustment
* QNH download
* Preferences (with the exception of theming)
Known bugs:
* Incorrect analogue needle movement if QNH rapidly increased - might be fixed.
How to use - READ ME:
Any barometric altimeter can only give correct indications when referenced to the correct pressure setting, which in Europe is measured in hectopascals and in the Americas, inches of mercury (inHg).
To locate the correct pressure setting, you can look it up at a nearby airport. Go to this link and put in a four letter ICAO identifier (for example, EGCC is Manchester, England) and look for the part QXXXX, which is the current pressure setting to use.
Alternatively, you can have the app download it automatically by inserting the ICAO identifier in the preferences. You'll know it's got a valid pressure setting by the "AUTO" indication in the bottom right corner.
The app is now compatible with American (ie, inHg) units. However, you might notice a slight glitch when using it where changing the QNH manually alters it by +/- 0.02 inHg. This is basically a rounding error: the app is only accurate to the nearest 10 ft, and .01 inHg is about 9.5 feet, hence the issue. Which isn't really an issue.
Please let me know if you get either an incorrect reading; a force close; or something else funky. It should remember QNH settings on pause / exit / rotation but if you've got it on auto-update, it'll invalidate the old measurements after 20 minutes.
Changelog
v0.4
* Themes added (six to choose from)
* Much time wasted trying to add digits to the analogue display. Given up.
* Analogue dial size increased
* About dialog fixed
* Bug fixes.
v0.2
* Automatic QNH download
* Preferences fixed
* Units selectable
* VSI (units/minute) - though not actually tested yet.
* Bug fixes
* Tweaks
v0.11
* Fixed force-close on non-English devices.
* Correct xhdpi action bar icons.
Do I need to get the pressure from ATIS/AWOS to calibrate this?
Looks cool!
LionAR10 said:
Do I need to get the pressure from ATIS/AWOS to calibrate this?
Looks cool!
Click to expand...
Click to collapse
Yep. Though unless a storm's coming through you can just wind the QNH up or down to show a known elevation. That'll give a fairly accurate pressure setting for the region.
Kewl, wanna try it!
It amazes me how many sensors there are in the Gnex compared to my old N1 ...
After taking it to work today I can confirm it reads accurately up to 8000ft (+/- 10ft) compared to the altimeter in the aircraft.
David Horn said:
After taking it to work today I can confirm it reads accurately up to 8000ft (+/- 10ft) compared to the altimeter in the aircraft.
Click to expand...
Click to collapse
Can't wait to try it out.
You should probably be able to filter out devices without barometer by simply requiring android.hardware.sensor.barometer to be true in your manifest. That way you avoid people incorrectly giving you bad reviews just because most phones don't have that sensor. Judging by the comments you see in Android Market, most people can't or don't read simple instructions or important information in the description so be prepared for a lot of 1-star reviews if you don't filter it those devices out. That's the sad truth.
David Horn said:
After taking it to work today I can confirm it reads accurately up to 8000ft (+/- 10ft) compared to the altimeter in the aircraft.
Click to expand...
Click to collapse
Are there going to be 'Donate Only' features as well or will only one version be released?
blunden said:
Can't wait to try it out.
You should probably be able to filter out devices without barometer by simply requiring android.hardware.sensor.barometer to be true in your manifest. That way you avoid people incorrectly giving you bad reviews just because most phones don't have that sensor. Judging by the comments you see in Android Market, most people can't or don't read simple instructions or important information in the description so be prepared for a lot of 1-star reviews if you don't filter it those devices out. That's the sad truth.
Click to expand...
Click to collapse
Me cannot wait to try it out as well!! A nice 'backup device' while I am flying my little C172.
And as a 'sad' truth, most people don't know how a barometric altimeter works. I guess sooner or later some people will complain that the altimeter reading is way off their assumed altitude, since they don't know an altimeter need to be calibrated/adjust to the current air pressure in their local area.
Also, people will try it in a pressurized plane and wonder why it display 8000 ft (or 6000 ft depending on plane model) while cruising at 32000 ft!
And Thanks the app author for the work!!
Update: Been busy with work but getting there. Analogue dial now works correctly with smooth graphics, improvements to other parts of the app. Just adding a vertical speed indication (text only at the moment) and polishing a few bits off.
At the moment the preferences screen doesn't work (it's all hard-coded). Would anyone be interested in trying a very early alpha on condition they don't complain if it doesn't work properly?
I'd try this for sure
David Horn said:
Update: Been busy with work but getting there. Analogue dial now works correctly with smoothing graphics, improvements to other parts of the app. Just adding a vertical speed indication (text only at the moment) and polishing a few bits off.
At the moment the preferences screen doesn't work (it's all hard-coded). Would anyone be interested in trying a very early alpha on condition they don't complain if it doesn't work properly?
Click to expand...
Click to collapse
me too
Sent from my Galaxy Nexus using Tapatalk
David Horn said:
Update: Been busy with work but getting there. Analogue dial now works correctly with smoothing graphics, improvements to other parts of the app. Just adding a vertical speed indication (text only at the moment) and polishing a few bits off.
At the moment the preferences screen doesn't work (it's all hard-coded). Would anyone be interested in trying a very early alpha on condition they don't complain if it doesn't work properly?
Click to expand...
Click to collapse
I would like to test it as well.
Sent from my Galaxy Nexus using Tapatalk
David Horn said:
Update: Been busy with work but getting there. Analogue dial now works correctly with smoothing graphics, improvements to other parts of the app. Just adding a vertical speed indication (text only at the moment) and polishing a few bits off.
At the moment the preferences screen doesn't work (it's all hard-coded). Would anyone be interested in trying a very early alpha on condition they don't complain if it doesn't work properly?
Click to expand...
Click to collapse
Yes, I'd be happy to try it out. Anything specific you need tested or logged?
Great, will upload it on Saturday (away from home tonight + tomorrow). Basically, I'd just like you to see if it works and report any crashes or force-closes, glitches with the read-outs, or bad calculations.
There's a lot of maths going on behind the scenes and it's quite likely there are a few mistakes. I've tried to keep it as efficient as possible so most of it is fixed-point, which is almost certainly going to need tweaking to sort out problems related to loss of precision.
It will always over-read slightly in a light aircraft due to the lower pressure inside the cabin - the same problem you encounter if you select the alternate static source.
can't wait to test
is the app going to have a widget?
@fridykker - it's on the list.
Still away from home but have taken a picture or two to show it in action. First two pictures are of the ECAM pressurisation page, which shows cabin altitude referenced to 1013 hPa. The last picture is the reading from the app.
Sorry about the blurry photos; it's been really choppy over Europe today.
Will you be able to add numerals, etc to the display to give it more of a steam gauge look? It's clean and sparse now, but the numeral hinting means less interpretation time for a glance at it.
Yep, it's in the works.
Alpha v0.1 now available - see first post.
David Horn said:
Alpha v0.1 now available - see first post.
Click to expand...
Click to collapse
If you have another language than English it immediately fc.
Thank you for this innovative app.
Sent from my Galaxy Nexus using Tapatalk

Categories

Resources