Hello,
I saw that there is no OBD software in the marketplace, so I assume there's no API for the OBD in windows phone 7??
If anyone has informations, I could develop a new obd tool... but I can't find informations about OBD..
If you mean by OBD the On-Board Diagnostics, all handsets already has one (provided by manufacturers). And it's nothing what you can do (if you'll not start manufactoring your own WP7 ) - all native code should be signed.
No, sorry, I meant the automotive diagnostic tool eheh!
It's probably because niether the USB or the BT connection allow to connect OBD interfaces. USB lacks host support and BT lacks virtual com ports support, so you have no way to connect the OBD interface whether it being KKL / ELM or whatever with the phone.
figured it was something like that.. any luck we will have support about this in the future?
There is a device for the iPhone that plugs into the OBD and creates a wifi network. After that it is just sockets. I'm sure you could make a windows phone version of the tool.
Found it: http://www.obdkey.com/wifi/index.asp
my buddy has one for android it communicates via bluetooth and cost like $20. He ran the codes on my caddy, very useful
Hello i am the developer for OBDMobile for windows mobile:
http://www.rklenka.com/software/winmobile/obdmobile/
and Windows:
http://www.rklenka.com/software/obdmobile/
and as soon as its possible there will be a version for Windows Phone 7, but for right now it cant be done. In fact I am trying to work with some OBD Connector manufacturers in order to find a way to get it to work.
Right now there is no Bluetooth API and no Ad-Hoc support which is what OBDKey and KIWI Wifi supports. All the back end code has all ready be done so as soon as there is a way it will be up.
RKlenka said:
Hello i am the developer for OBDMobile for windows mobile:
http://www.rklenka.com/software/winmobile/obdmobile/
and Windows:
http://www.rklenka.com/software/obdmobile/
and as soon as its possible there will be a version for Windows Phone 7, but for right now it cant be done. In fact I am trying to work with some OBD Connector manufacturers in order to find a way to get it to work.
Right now there is no Bluetooth API and no Ad-Hoc support which is what OBDKey and KIWI Wifi supports. All the back end code has all ready be done so as soon as there is a way it will be up.
Click to expand...
Click to collapse
This would be amazing if you could get it to work matey
I use Torque on my Android Tablet and Digimoto on my laptop and connect to my Bluetooth OBD-II Reader, if i was able to use my Windows Phone this would be a GREAT help!
ODB aplication for WP7 would be very good.
I was looking around the internet about 2 months ago and ran across hardware and apps that do this for android,ios,wm, and I think even blackberry...
I remember thinking that would be sweet on my windows phone. Way to show up my boss... Lol
I showed him the website and I think he's gonna look into it when the software on the current scan tool gets outdated since he has an iphone4, I got the hd7, and another kid has an android phone.. Would be sweet to just carry around the little piece that plugs into the port and broadcast the signal to the phones.
Do you think there's gonna be live data support or just a basic tool to pull engine codes. Possible abs, srs scan too?
Sent from my HD7 T9292 using XDA Windows Phone 7 App
Didn't know the USB adapters could be gotten for under $20 never mind software for the PC for fairly cheap. I always thought these adapters could only be gotten for around $300+.
I dont work on cars for a living but, if this could be all gotten and working on my WP7 device for under $30, I'd be all over it. It's always usefull to have one of these type of things around when a code comes up on one of our cars and not have to run to a store that will not reset codes, etc.
I might even grab it for a old WM 6.5 device I keep around for a spare....
any app for OBDII gauges in WP7.5 ????
Bump, it's been a while, anyone find anything for WP7 or 7.5 to do this ?
It's been a while for this thread - any updates on Windows Phone and OBD-II? Wondering because I want to expand into Windows development too, rather than just Android.
There's already a great thread where people are reporting what USB/Bluetooth items will and won't work on the Surface RT.
According to Pluggable, a manufacturer of USB peripherals, the problem lies much deeper: Windows RT doesn't support any USB device requiring a driver, and support may never come. It says:
"Windows RT does not have a Device Driver Development Kit and does not support or allow the installation of drivers. There is currently no Windows Update for Windows RT from which to match and download newly approved drivers for new device types from 3rd parties."
In short, the only devices which will work are devices which have traditionally had in-box support in Windows and never require a 3rd party driver to be installed: USB hubs, USB Mass Storage (USB hard drives and flash drives), USB Audio (headsets and mics), some USB printers, most USB video (webcams), USB HID (keyboards and mice), and a few other special cases.
I knew RT drivers would be a problem; this article implies that the drivers may never be coming at all.
AndyRathbone said:
There's already a great thread where people are reporting what USB/Bluetooth items will and won't work on the Surface RT.
According to Pluggable, a manufacturer of USB peripherals, the problem lies much deeper: Windows RT doesn't support any USB device requiring a driver, and support may never come. It says:
"Windows RT does not have a Device Driver Development Kit and does not support or allow the installation of drivers. There is currently no Windows Update for Windows RT from which to match and download newly approved drivers for new device types from 3rd parties."
In short, the only devices which will work are devices which have traditionally had in-box support in Windows and never require a 3rd party driver to be installed: USB hubs, USB Mass Storage (USB hard drives and flash drives), USB Audio (headsets and mics), some USB printers, most USB video (webcams), USB HID (keyboards and mice), and a few other special cases.
I knew RT drivers would be a problem; this article implies that the drivers may never be coming at all.
Click to expand...
Click to collapse
i think they just have to submit drivers to microsoft to have them work, my canon 5d mk 3 worked out of the box and i've had to install drivers for all my dslr's in windows before
When you plug in an unsupported device, does it at least attempt to search windows update for a driver? Or are all supported drivers included in the device?
Sent from my Galaxy Nexus using Tapatalk 2
Skitals said:
When you plug in an unsupported device, does it at least attempt to search windows update for a driver? Or are all supported drivers included in the device?
Click to expand...
Click to collapse
That's a good question. To control things, I turned on Airplane Mode. Then I plugged in an Easy Transfer Cable.
Surface RT recognized the cable, and USB Transfer Device appeared in Device Manager, but with the yellow exclamation point.
I turned off Airplane Mode, opened the Device Manager's Properties window for the USB Transfer Device, and told it to search automatically for updated driver software.
After visiting Windows Update, it gave me this message: "Windows was unable to find driver software for your device. If you know the manufacturer of your device, you can visit its website and check the support section for driver software."
I'm thinking Windows RT only accepts USB items that the OS natively recognizes: cameras, external storage devices, mice/keyboards, and a few other things. It won't accept anything requiring a third-party driver because Microsoft doesn't want to introduce that as a possible security hole.
I would be surprised if MS would not provide a driver development kit.
WinRT is basically a recompiled version of Win8 for the ARM. So in theory I would be able to take my C/C++ coded driver and run it through an ARM compiler to produce the correct dll.
Just made a quick look around, and I see the essential dll's required to implement a proper windows system driver. So it should work...
draftQ said:
I would be surprised if MS would not provide a driver development kit.
WinRT is basically a recompiled version of Win8 for the ARM. So in theory I would be able to take my C/C++ coded driver and run it through an ARM compiler to produce the correct dll.
Just made a quick look around, and I see the essential dll's required to implement a proper windows system driver. So it should work...
Click to expand...
Click to collapse
Just like you should be able to take your C/C++ desktop app and run it through the ARM compiler and it should work (like Office RT), but it doesn't. MS has it locked down tight. They are going the completely closed ecosystem route... like Apple (iOS).
Its a shame, because it otherwise has the potential of full blown windows 8. No reason we shouldn't have recompiled ARM versions of VLC and other open source desktop apps, but MS is keeping developers in the metro sandbox.
Sent from my Galaxy Nexus using Tapatalk 2
This was incorrect
AndyRathbone said:
There's already a great thread where people are reporting what USB/Bluetooth items will and won't work on the Surface RT.
According to Pluggable, a manufacturer of USB peripherals, the problem lies much deeper: Windows RT doesn't support any USB device requiring a driver, and support may never come. It says:
"Windows RT does not have a Device Driver Development Kit and does not support or allow the installation of drivers. There is currently no Windows Update for Windows RT from which to match and download newly approved drivers for new device types from 3rd parties."
In short, the only devices which will work are devices which have traditionally had in-box support in Windows and never require a 3rd party driver to be installed: USB hubs, USB Mass Storage (USB hard drives and flash drives), USB Audio (headsets and mics), some USB printers, most USB video (webcams), USB HID (keyboards and mice), and a few other special cases.
I knew RT drivers would be a problem; this article implies that the drivers may never be coming at all.
Click to expand...
Click to collapse
Hi gang-
I work for Plugable, not trying to advertise, but just want to share some news.
Then information we're quoted in above turned out to be wrong.
We've updated the post referenced above,
[Update: 11/16/2012] We had previously incorrectly written that device drivers aren’t installable on Windows RT. That’s not right.
Click to expand...
Click to collapse
We've also added a follow up where we explain how to install a driver on a Windows RT device. Here's the new post.
We're very sorry about providing the misleading information, but we'll be working hard towards being open about news and developments.
I'm game to explain how we arrived at the bad findings if anyone's interested: essentially just that Windows Update hadn't found any drivers, and we'd not been able to find any drivers posted at http://catalog.update.microsoft.com, nor other important resources for development and distribution.
dharmapunk said:
Hi gang-
I work for Plugable, not trying to advertise, but just want to share some news.
Then information we're quoted in above turned out to be wrong.
We've updated the post referenced above,
We've also added a follow up where we explain how to install a driver on a Windows RT device. Here's the new post.
We're very sorry about providing the misleading information, but we'll be working hard towards being open about news and developments.
I'm game to explain how we arrived at the bad findings if anyone's interested: essentially just that Windows Update hadn't found any drivers, and we'd not been able to find any drivers posted at http://catalog.update.microsoft.com, nor other important resources for development and distribution.
Click to expand...
Click to collapse
Any ETA (possibility?) of RT drivers for your USB video adapters? Oh, and just bought that Ethernet adapter, thanks for letting us know!
Actually, it does work. You just have to sign the apps with the Microsoft code integrity key. This may give the impression that you can't do it at all, but that's not actually true.
Obviously, this isn't possible for a third-party developer to apply such a signature directly, and MS is generally not fond of signing third-party code. It happens on occasion, though. Consider the Flash Player in IE10 for RT; that's Adobe code, but it's signed with the MS key. Downloading suitably signed EXEs and running them works just fine; for example, the remote debugging server for Windows RT is distributed by MS exactly like any other downloadable EXE, and it works.
In fact, if you somehow manage to put your device in Testsigning mode (which exists in RT and also in x86 versions of Windows, and allows using any trusted signature instead of only the MS signature), you can install your own signing certificate and then run your own compiled and signed desktop apps. Unfortunately, testsigning mode is a bootloader option, and the bootloader for all currently released Windows RT devices prohibits its use (although development devices were found to support it).
@dharmapunk: Any chance this driver is going to show up in Windows Update soon? Since you've obviously already gotten the MS signature, hopefully it will be literally plug-and-play soon...
GoodDayToDie said:
@dharmapunk: Any chance this driver is going to show up in Windows Update soon? Since you've obviously already gotten the MS signature, hopefully it will be literally plug-and-play soon...
Click to expand...
Click to collapse
@GoodDayToDie Sorry, I'm not entirely sure on this- since it's an ASIX developed driver the info I have here is second hand. We anticipated this would be baked into RT's RTM, however for some unknown reason it wasn't.
Sorry I can't be more help here, I'm still looking for ANY WinRT drivers over on catalog.update.microsoft.com.
---------- Post added at 06:05 AM ---------- Previous post was at 06:00 AM ----------
addictivepixels said:
Any ETA (possibility?) of RT drivers for your USB video adapters? Oh, and just bought that Ethernet adapter, thanks for letting us know!
Click to expand...
Click to collapse
Sorry @addictivepixels, I've not heard any news that DisplayLink is close to releasing, or even working on, a WinRT usb graphics driver. I anticipate that will stay only x86/x64 for quite some time. Wish I had better news...
The saga continues...
Hi again-
The saga continues. We’ve been asked to take down the WinRT driver for our ASIX-based USB Ethernet adapter. Seems like it wasn’t supposed to have been released after all, so we’re taking the driver off our website soon- before month's end.
We’ll still be selling the adapter. We’ll still be supporting customers. We’re even keeping the installation instructions that we wrote up on our website.
I hope that this issue can be resolved soon. I want more devices to plug into Surface too!
Since I'm a noob I can't post a link to our new post, however the one the OP listed now has an update notice with a link to further details.
dharmapunk said:
Hi again-
The saga continues. We’ve been asked to take down the WinRT driver for our ASIX-based USB Ethernet adapter. Seems like it wasn’t supposed to have been released after all, so we’re taking the driver off our website soon- before month's end.
We’ll still be selling the adapter. We’ll still be supporting customers. We’re even keeping the installation instructions that we wrote up on our website.
I hope that this issue can be resolved soon. I want more devices to plug into Surface too!
Since I'm a noob I can't post a link to our new post, however the one the OP listed now has an update notice with a link to further details.
Click to expand...
Click to collapse
Is there any chance that we could get the source to said driver? I'd like to poke around it to see if it has any vulnerabilities that'd allow a kernel-mode exploit.
I understand if you can't/don't want to post it.
netham45 said:
Is there any chance that we could get the source to said driver? I'd like to poke around it to see if it has any vulnerabilities that'd allow a kernel-mode exploit.
I understand if you can't/don't want to post it.
Click to expand...
Click to collapse
@netham Other than the driver package in the link in the original post, we haven nothing else to offer. Since I knew our blog post with the driver download was quoted in the original post in this thread, we wanted to warn any customers who might have purchased our USB2-E100 that the driver will be going away soon due to a takedown request.
To be clear, our concern is making certain any customers who purchased the USB2-E100 for use on Windows RT have a chance to download the driver before we take it down.
I'd post the link to our new blog post with details if I could, trying again: http://plugable.com/2012/12/11/windows-rt-surface-usb-ethernet-takedown
The RT driver situation has been odd to say the least - still trying to figure it all out. I've been able to yank some drivers out of my Windows 8 Pro box and manually install them onto the Surface. Outcomes:
I was able to get my Smart Card Reader half functional this way, although there is no current affordance for installing the necessary minidriver that allows the .NET card to fully interoperate with the Surface.
I had the same minidriver issue with my DisplayLink UV+.
I was also able to get my Lumia 900 to mount , but can't get the file system to read past the top level.
More research required...
That is... *very* interesting. Those must be .NET user-mode drivers, because the Surface RT uses the ARM instruction set and is completely incapable of running the typical written-in-C/C++-and-compiled-for-x86/x64 drivers used on "normal" Windows.
Alternatively, the driver may contain a firmware blob that is loaded into the microcontroller of the hardware even though the actual Windows driver code (which would be x86) wouldn't work. The firmware blob won't be x86, it'll be whatever instruction set the device's microcontroller executes.
Don't ever buy Windows RT again, it's a dead end operating system.
well, at a very low price,it's a good device. Kids like them for games and music. Youtube etc . play well on it . Not totally useless but I would of never paid the full price for it.
Hey guys. This is an important question for the Retro Gaming Community. Most of you guys aren't familiar with me but let me let you guys know how I do my threads. First I start a topic trying to figure out a problem. We have discussion and after the solution is reached I edit the title to "Solved" and I edit this first post with the solution for the sake of simplicity for when other people are researching the problem also (Whether on XDA or on their favorite search engine, ex. Google). So with that out of the way let me tell you what I'm trying to accomplish, why I feel this is Important to the Retro Gaming Community, and what ive tried to do to find my answer. This is what I'm trying to do...
Im a Retro Gamer (Someone who likes to play old video games, some argue how old but I believe for it to be Retro it has to be almost 15 years or older. ex. Sony Playstation, Nintendo 64, Sega Dreamcast or older).
I recently bought myself a Generic USB Super Nintendo Entertainment System (SNES ) Controller which advertised as Windows and MAC compatible for my PC. Now I also have a USB OTG (On-The-Go) adapter to plug in my USB Type-A (Regular USB) plug to my tablets USB Type-B Micro (Phone and Tablet USB, the small one). Of course you know what I tried to do next . Yes I did I downloaded my favorite SNES Emulator, plugged in my USB SNES Controller via the USB OTG Adapter and tested that bad boy out just to see what happens. And guess what happened next?
Absolutely nothing.....
I didn't receive a notification from my android tablet that I plugged in a peripheral like I did when I plugged in my USB flash drive via USB OTG and my emulator did not detect it so next I went scouring the internet to find an answer. One answer that kept coming up was to install an app called "USB/BT Joy Center" which didn't work for me and isn't even available in the Google Play Store for the USA, and the other thing that's scary about that app is that android gave my a warning saying it asks to detect keyboard input and it also needs access to the internet for some reason. , it also said that app can detect my inputs like passwords and credit card numbers so I uninstalled it.
There has to be a way to make this work. I know almost all Generic controllers work for Linux and Android is a derivative of Linux, also Ive read on many threads that other peoples phones and tablets work with Generic USB Controllers via the OTG adapter. I feel if we find a straight solution to this not only this would be the only forum to have a straight solution to this but for the Retro Gaming community and gaming in general this would be a huge step forward in emulation and gaming in portability.
So this is what Im working with.
I have an Azpen A1023 tablet with Android Jelly Bean, a Generic USB SNES controller with an USB OTG adapter, and Im using the Android SNES emulator "Snes9x EX+ 1.5.28" which allows you to configure a controller and has auto-detect with isnt working with my tablet.
And help, comments or feedback is welcome. Like I said when I solution is found I will edit the title of the thread and the first post for the sake of simplicity. If anyone feels I should edit the title of this thread to something else please feel free to offer any suggestions. Again I look forward to working with you guys to find an answer.
Im sure with over 400 views someone has something to say. Don't keep all that knowledge to yourself, any input would help ☺