Related
I race a Grand Prix 250cc motorcycle and his it has a very trick race ignition which has the capability of downloading setup data etc..
Heres the problem...It has software which is only designed to run on Windows 95 and 98 upto and including SE....
My point is I have a laptop but its bulky and there are leads everywhere and as I have a XDA 2 I wondered if someone out there could adapt the software to run on Windows CE that the XDA 2 runs on....I already use the excel on the PDA to great effect....
Can anyone help....this is a vital piece of kit on my bike and I will supply tickets to any or all of the final 4 meetings of the year in the UK that I am racing at....
Heres the link if anyone wishes to try..
http://www.bpsracing.com/bps/product/rs250download.htm
Many thanks Lee
Wow, a GP 250 bike. You have brass ones, my friend, I stand in awe.
Can't help you with the ignition module question, but I'd happily trade my left nut for a few laps on that bike.
take a look my friend
If you like race bikes have a look at my website..
www.leefinneyracing.com
Regards Lee
in the mean time can anyone help?
Is this for static programming or does it adjust your timing/ignition on the move while detecting other changes in engine system?
The main purpose is to download the data picked up from the wheel speed
sensors and the detonation reading on each cylinder. ( there are 2 ) also there are 2 tempreture sensors....
This is done static.....but once I have the information I need to ie humidity density air presure etc and take the cylinder heads of then I can take a reading from the piston crowns and jet the bike to suit......
Once this is done I can modify the ignition maps and upload the new or modified maps to the ECU and away we go!
In the Practice or race I have a switch on the left hand bar to switch between 4 different ignition maps depending on circumstances or weather.
Hope this helps.
Hello all..
i was wondering if anyone has been successful in extracting the HTC Digital Compass from the HTC Trinity ROM incl of GPS ?
i believe it require hardware
there are no software i can think off
which can tell which way north is without
hardware
otherwise pc's would have had it years agoe
Rudegar said:
i believe it require hardware
there are no software i can think off
which can tell which way north is without
hardware
otherwise pc's would have had it years agoe
Click to expand...
Click to collapse
Check this out: http://www.mobilosiranytu.fw.hu/
I think you're looking for something similar.
I try to translate to English the description:
"This program is not an original compass. This program has the ability to calculate the angle between the northern direction and the direction of the sun (or the moon) by the knowledge of the actual place and time. This angle showed on the display by an orange (the Sun) and a blue (the Moon) arrow. You have to rotate one of the arrows towards the right direction (the orange towards the Sun or the blue towards the Moon), and the compass will show the right directions...."
well my phone has GPS... isnt there any software which i can use as a compass ?
There's so much gps software now,tomtom has a wee compass in it but I think you don't want that, maybe there is something here:http://www.freewarepocketpc.net/ppc-tag-gps.html
does the compass in nokia n97 is hardware compass
wait maybe i am wrong...but when we go north i'm sure the lattitude numbers goes up or down??
i know by standing we won't get it...atleast by walking couple of metres it should pick up the lattitude numbers....and see if we're going north....??
maybe i am wrong...but with gps turned on..and we go north i'm sure the lattitude numbers goes up or down??
i know by standing we won't get it...atleast by walking couple of metres it should pick up the lattitude numbers....and see if we're going north....??
GPS-based compasses compare two positions to know your direction, while a real compass is a magnet that interacts with the earth's magnetic field to know where you are looking (without moving)
I'm looking for app that uses hardware compass. GPS compass is no use if you are indoors. Anyone?
ridz said:
I'm looking for app that uses hardware compass. GPS compass is no use if you are indoors. Anyone?
Click to expand...
Click to collapse
Why would you want that if you don't have a hardware compass built in phone?
Solution: Buy a compass and sticky-tape it to your phone
mengsuan said:
Solution: Buy a compass and sticky-tape it to your phone
Click to expand...
Click to collapse
+1
http://www.sciencestuff.com/prod/P-g/0404-S
If you have a Diamond, Touch Pro, or any other device with a magnetic stylus, simply attach your stylus to a piece of cork, and float it in the nearest body of water. Voila! Compass.
ktemkin said:
If you have a Diamond, Touch Pro, or any other device with a magnetic stylus, simply attach your stylus to a piece of cork, and float it in the nearest body of water. Voila! Compass.
Click to expand...
Click to collapse
really??! going to test it soon.. thanks for sharing !
ktemkin said:
If you have a Diamond, Touch Pro, or any other device with a magnetic stylus, simply attach your stylus to a piece of cork, and float it in the nearest body of water. Voila! Compass.
Click to expand...
Click to collapse
The magnet is in the device, not the stylus
GPSSpot is the app your're looking for.
It is a digital compass which uses your phones built-in GPS receiver.
I use it, it works really well, and it also allows you to save waypoints.
http://www.cradle-software.de/en/software/gpsspot
GldRush98 said:
The magnet is in the device, not the stylus
Click to expand...
Click to collapse
My Touch HD has magnetic stylus as I can stick it to my PC case, fridge and so on
have you guys tried the new google maps app for windows mobile?
somehow when i start my gps it points to my true direction when using the new google maps app.
spikegotti: I think google maps points to the north when started and when you move, it calculates your direction from your previous position
what is so special about iphone4 "gyroscope" compared to the ordinary motion sensors found in phones today?
I assume it can detect more axis than the current accelerometer.
like, current sensors only detect X and Y axis (like if u tilt your phone left or right), but the gyroscope can detect if you tilt it forwards or backwards, plus maybe more than that. so all this means an uber gaming machine..
correct me if i'm wrong xD
But i think, unless you want to use your phone as a hardcore portable game device, it wont really matter. I see its main use in gaming only, but who knows, might have some interesting apps out there. If i want to experience good games, i would use my computer or a console, gaming on my mobile is only for time wasting, like puzzle games or 2D platformers... quick 2 minute games =)
please use the search
http://forum.xda-developers.com/showthread.php?t=714459&highlight=gyroscope
there was already a looooooooong post about this topic
Any one here has a problem with the touch screen when playing some fps games of Gameloft like Sandstorm, Nova, Bia2 ... ?
Sent from my MotoA953 using XDA Premium App
No such problems
Sent from my Desire HD using XDA App
Im having some multitouch issues @gunbros havent tried any other multitouch games.
Sent from my MotoA953 using XDA App
I think there is problem with Milestone 2's multitouch. I'm not sure this is a hardwares or softwares issue.
Hi. Are you playing with the charger connected? Capacitive screens are very sensible to leakage currents. If there is some ghost touch happening, it's the charger's fault. The original charger doesn't have this problem, but if you are using a generic charger or usb cable connected to your pc/laptop, there might be some leakage current.
Maybe your issue is connected with limitation of Milestone 2. It supports only 2 fingers tracking. Maybe your are using more of them during play and some of them are not tracked correctly.
AragornPE said:
Hi. Are you playing with the charger connected? Capacitive screens are very sensible to leakage currents. If there is some ghost touch happening, it's the charger's fault. The original charger doesn't have this problem, but if you are using a generic charger or usb cable connected to your pc/laptop, there might be some leakage current.
Click to expand...
Click to collapse
I experienced the ghost touch with my original charger as well...
Sent from my MotoA953 using XDA App
Sorry if it's a little bit side-tracking.
Do you guys experience lags when sliding through the menu (notification bar, contacts, etc.)? I mean the sliding is smooth but it is not synchronizing with my finger. It lags for like 0.5 sec until it scrolls to the place it's supposed to be.
If you own a DEFY and do a direct comparison you'll know what I mean.
I have the exact same problem with my Milestone 2 and it's bloody annoying.
I wish that Gameloft added the ability to assign hard keys; using the keyboard for directions and the camera button to fire would not only eliminate the problem but make the game much easier to play.
havent really had any problems with game loft. but i experienced tonnes of touch screen issues after installing the game 'Words'. as soon as i removed it, ive not had any touchscreen issues, including ghost touch.
I haven't got any issues with the touch up to now. Even playing with a connected (original) charger doesn't cause any problems.
That's annoying TBH. At least if everyone was having these problems there is a chance that Motorola would acknowledge and address the problem, but as it seems like an unlucky handful of people having this issue, I doubt it would be rectified. I'm reluctant to send my phone in for repair as I've got a feeling I'll just get it back with the same fault.
the games need multitouch wouldn't run well . i assuming that one finger can obstruct another
I've fixed it! At least, it seems to be fixed
I read a few times of people disconnecting their batteries (!) and that seemed to fix the issue. I tried it myself, leaving the battery out for an hour or so, and it didn't rectify it. So in desperation I tried leaving the battery out overnight. I played NOVA this morning and it seems just fine. Still gets a little confused but nowhere near as frustrating to play as it was before.
I hope this trick works for you guys.
Oh, by the way, before I did this I downloaded Simply Draw to check if the digitiser was faulty and it worked perfectly, so I knew that wasn't the problem. Anyone who has seen the Youtube video about the dodgy Milestone 2 touchscreen will know what I'm on about.
I also experimenting problems on games, but on simply draw it was ok to me.
where is this video you are talking about?
hugs
I use the App "Screen Test Toolkit" from the market. When my Phone is connected to the original charger, I experience massive touchscreen problems in the upper and lower left corner.
Oh, connected to the charger a lot of people experience severe problems with the touchscreen. Mine is absolutely not usable to surf through the web while the phone is plugged in...
Guys, if you have such a problem, try the USB extension cable. I am using this 1,2m long cable and I have no problem with touch screen when phone's charging And Idon't know why...
I have problems playing games on the M2. It seems that is the "intended" behaviour on the multitouch. For example, try PES11. Sometimes it seems that the touch screen gets "confused" and messes with the touch points. Also, check this:
supportforums.motorola.com/message/372437
Hi,
I'm a proud S2 owner but I'm note sure for how long. It seems the gyro in my device is very unstable. For example, if I use Google Maps and I turn on the sensor, the map will rotate if I only the tilt the device upwards (and this shouldn't cause a map rotation).
I've also tested some other apps using the gyro (STLView by ModuleWorks https://market.android.com/details?id=moduleWorks.STLView or some artificial horizon apps) and they all share this instability.
I have an EEE-Pad as well, and there those apps are really great.
So the question really is, is it just my device or can anyone else reproduce these issues?
Thanks,
Mark
I have the same issue.
pub00515 said:
Hi,
I'm a proud S2 owner but I'm note sure for how long. It seems the gyro in my device is very unstable. For example, if I use Google Maps and I turn on the sensor, the map will rotate if I only the tilt the device upwards (and this shouldn't cause a map rotation).
I've also tested some other apps using the gyro (STLView by ModuleWorks https://market.android.com/details?id=moduleWorks.STLView or some artificial horizon apps) and they all share this instability.
I have an EEE-Pad as well, and there those apps are really great.
So the question really is, is it just my device or can anyone else reproduce these issues?
Thanks,
Mark
Click to expand...
Click to collapse
I tested it on my sgs2 with maps and I don't seem to have the issues that you are experiencing. I even downloaded STLView and did not have this "instability" problem. Perhaps your handset is faulty?
Another possible reason is that you might have been trying to use your sgs2 in the bermuda triangle. It has been documented that the bermuda triangle wrecks havoc on electronics.
Are you sure maps use gyro ? I guess they use primarily compass and G-sensor, while of course, gyros can help too.
Did you try to calibrate the gyro sensor?
Yupp, tried calibration, didn't help.
@info5i2002
Pretty far from bermuda
In STLView, did you enable the gyro button (the button on the left side)? What happens if you tilt the phone by 90° (hold it over your head facing towards you) - does the heading swing around?
When I hold the phone level (in landscape orientation), and I tilt the phone up and down, I can clearly see the axis swing from left to right.
pub00515 said:
Yupp, tried calibration, didn't help.
@info5i2002
Pretty far from bermuda
In STLView, did you enable the gyro button (the button on the left side)? What happens if you tilt the phone by 90° (hold it over your head facing towards you) - does the heading swing around?
When I hold the phone level (in landscape orientation), and I tilt the phone up and down, I can clearly see the axis swing from left to right.
Click to expand...
Click to collapse
Yeap, tried it in landscape and tilted it up and down and it seems to move only up and down only.
If the device is in a case/cover which has Magnetic Lock then the issue is normal.
issue is NOT gyro related, what's described here is unstable accelerometer and/or compass readout. i guess it's mainly due to missing magnetic calibration (try to do the "8" pattern with the phone, AND turn the phone twice around each axis). if the problem persists, than it's maybe within technological limits (and everyone faces it, although the people here are more upset about it). also possible is magnetic interference due to huge amounts metal etc...
Yes .. people often confuse accelerometer (G-sensor), electronic gyroscopes, and compass. All do different things, but all can be used in applications like maps.
I also noticed that the magnetometer of my s2 is kind of imprecise.
I have continuously swinging head indication, of about +/- 15 degrees. Moreover, the correspondance from phone orientation and indication is not linear. I get higher sensitivity towards one direction and lower towards the opposite direction...
However what I did notice, is that the magnetometer, responsible for the compass, is very sensitive not only to nearby magnets, but even to metal objects at considerable distance. So perhaps it is all just this sensor beind a tad too sensitive.
Sent from my GT-I9100 using XDA App
Hi,
I've done a few more tests - I placed a strong magnet next to my Eee-pad and I had no deflection when I moved the magnet. So in this case, the app is correctly using the device's gyro and accelerometer. I then performed te same test with my S2 and bingo, I had a strong deflection as I moved the magnet. This is plain silly, as the sensor I'm using in my own app doesn't rely on the compass, instead it relies on the rotation vector sensor as provided by the SDK. Now the question is, who was sloppy? Does Gingerbread perhaps not support the gyro fully or did Samsung not implement the sensor correctly? As I wrote, the same code works perfectly on my Honeycomb tablet so it's not a programming error per se.
Regards
Mark
Yes, there definitely must be something wrong with the gyro and/or the magnetometer.
Some time ago I opened a specific thread on this subject in this forum, got many "reads" but no replies whatsoever...
So strange nobody did actually notice it so far.
pub00515 said:
Hi,
I've done a few more tests - I placed a strong magnet next to my Eee-pad and I had no deflection when I moved the magnet. So in this case, the app is correctly using the device's gyro and accelerometer. I then performed te same test with my S2 and bingo, I had a strong deflection as I moved the magnet. This is plain silly, as the sensor I'm using in my own app doesn't rely on the compass, instead it relies on the rotation vector sensor as provided by the SDK. Now the question is, who was sloppy? Does Gingerbread perhaps not support the gyro fully or did Samsung not implement the sensor correctly? As I wrote, the same code works perfectly on my Honeycomb tablet so it's not a programming error per se.
Regards
Mark
Click to expand...
Click to collapse
Now that's interesting. Could be !
My compass works a bit weird. I put it on table, let it show the north. Then I rotate the device 180 degrees .. and the north shifts like 5 degrees. It can be worse, but calibrating (waving the 8 pattern) helps .. but I can't get the error under 5 degrees no matter what.
Btw. it's common that that electronic compasses are much more sensitive to metal objects, that's not Samsung's mistake. But the sensors should not be linked.
Edit: I downloaded some sensors monitoring application. And gyroscopic sensor itself for sure is not sensitive to magnetic fields and works as it should, same for accelerometer. But then there are some IMHO virtual sensors: linear acceleration and rotation. They seem to be synthesized from more sensors, and the rotation does react on magnet.
So perhaps if someone has a different phone running Gingerbread with a gyro on board, we can see if the issue exists there as well (best would be to try it with STLView, as I know what API calls are made)
Thanks,
Mark
Dr.Sid said:
My compass works a bit weird. I put it on table, let it show the north. Then I rotate the device 180 degrees .. and the north shifts like 5 degrees. It can be worse, but calibrating (waving the 8 pattern) helps .. but I can't get the error under 5 degrees no matter what.
Click to expand...
Click to collapse
Mine does the same. Actually I can get even 15 degrees deviation. I noticed that it seems to depend on the location I am, despite apparently there should be no magnetic objects nearby. I am pretty sure that if if you try rotaring your phone at constant angular speed in the horizontal plane (with it horizontal on a table for instance) with a "compass" app running you will notice that the indicaton on the screen speeds up considerably when the phone is pointing to the north, and slows down when is pointing to the south.
Which Gingerbread version are you guys running?
I'm still waiting for the 2.3.4 update.
It would be interesting if someone could try this with 2.3.4, perhaps it works with the update?
Thanks...
Mark
pub00515 said:
So perhaps if someone has a different phone running Gingerbread with a gyro on board, we can see if the issue exists there as well (best would be to try it with STLView, as I know what API calls are made)
Thanks,
Mark
Click to expand...
Click to collapse
hi mark,
again, what you (we) experience here has nothing, i repeat nothing, to do with the GYRO. what you mean is the accelero- and magnetometer! a gyro knows nothing about it's current position (it only detects deviations, read about a coriolis vibratory gyro for more details about the mems gyro the sgs2 is using)
most programs i know are not using the gyro for positional information, for example google maps, google sky... they are all using the magnetometer in combination with the accelerometer ONLY!
regards,
markus
Hi Markus,
thanks for the heads-up, but I think I have a pretty good idea of what's going on:
Why?
Well, for starters, I'm a software developer in a technical field and I'm also the author of STLView mentioned above. Secondly, the same app running under Honeycomb with an Asus EeePad is working perfectly, and it is using the gyro there. Yes gyro and no, not magnetometer.
The problem with the S2 as I see it, is:
either Gingerbread or Samsung have failed to implement the rotation_vector sensor, as provided by the official API, correctly. On the S2, it is using the acceleration sensor combined with the magnetometer, which is just plain silly, as the magnetometer is too unstable for correct rotation rate measurement. On the EeePad, the same virtual sensor is using the accelerometer and the gyro in combination (gyro for rotation rate and the accelerometer to eliminate gyro drift). What you get is a very accurate sensor reading, which is just not possible on the S2 as of now.
Hopefully, either Samsung or Google are going to fix this flaw, but I think the problem is more on Samsung's side as they are the ones who actually know what physical sensors are available. That's also why it would be interesting to find out if other devices running Gingerbread that have a gyro on board are also experiencing the same problems.
By the way, I'm also a pilot so I think I have a pretty good understanding of what a gyro is and what it measures, thank you very much. Next time, remember: "Halbwissen ist gefährlich"
Regards
Mark
pub00515 said:
Hi Markus,
thanks for the heads-up, but I think I have a pretty good idea of what's going on:
Why?
Well, for starters, I'm a software developer in a technical field and I'm also the author of STLView mentioned above. Secondly, the same app running under Honeycomb with an Asus EeePad is working perfectly, and it is using the gyro there. Yes gyro and no, not magnetometer.
The problem with the S2 as I see it, is:
either Gingerbread or Samsung have failed to implement the rotation_vector sensor, as provided by the official API, correctly. On the S2, it is using the acceleration sensor combined with the magnetometer, which is just plain silly, as the magnetometer is too unstable for correct rotation rate measurement. On the EeePad, the same virtual sensor is using the accelerometer and the gyro in combination (gyro for rotation rate and the accelerometer to eliminate gyro drift). What you get is a very accurate sensor reading, which is just not possible on the S2 as of now.
Hopefully, either Samsung or Google are going to fix this flaw, but I think the problem is more on Samsung's side as they are the ones who actually know what physical sensors are available. That's also why it would be interesting to find out if other devices running Gingerbread that have a gyro on board are also experiencing the same problems.
By the way, I'm also a pilot so I think I have a pretty good understanding of what a gyro is and what it measures, thank you very much. Next time, remember: "Halbwissen ist gefährlich"
Regards
Mark
Click to expand...
Click to collapse
hi mark,
sorry - i didn't meant to be rude...
nor did i know your background; the thing nowadays is, a hell lot of people are talking technical nonsense all the time, which is quite frustrating...
i have to admit as i'm no software developer i didn't know the thing with the rotation_vector, what's sure for me was that the actual situation is caused from the accel/mag sensor, simply because of its behavior. that it would be way better to use the gyro as well for all this applications is absolutely true.
so let's hope either samsung or google will provide a fix, as you said!
glück ab, gut land!
markus