Hi,
i have an HP Mouse and would like to use it with my Windows RT. Normaly i would say connect the Mouse to the RT, driver will be installed automatically. But my mouse is working with the intern Wi-Fi of the deivce. So first i need to install the Software/driver before i can connect the mouse. Can someone tell me how i can do this? The mouse drivers are availabel for x86 and x64 Device.
Thank you
2 things.
First of all I have never heard of a mouse that connects via internal wifi. Only bluetooth, USB connector (which may have its own wifi or bluetooth device internally for a wireless mouse but does not need a special driver as it still appears as a normal USB mouse) or PS/2.
Secondly. You cannot install x86 drivers on windows RT.
1. You can complain about this directly by HP, but it's fact that this mouse connect directly by intern Wi-Fi. That's because there is no USB connector and the notebook has no bluetooth
2. if this is as easy as downloading a app from market i needn't to ask here? I found severel Threads saying they get Desktop Apps x86 runnying on the RT. So i thought maybe it is possible to get this driver/software running on the RT, too.
x86 drivers cannot be installed, it even says that in the thread.
I'm very crurious about this mouse; I've never heard of a WiFi mouse (the wireless ones that don't use BlueTooth use proprietary protocols of their own) and historically WiFi has been considered unsuitable for the purpose. I'd heard there was a project to try and produce a WiFi profile suitable for peripherals but hadn't heard of anything using it.
Could you please share the model name/number/whatever of your mouse?
As for using it on Windows RT, you'll probably have to wait for HP to release a Metro app that supports the mouse (if this is even possible). x86 and x64 drivers aren't supported, even to the extremely limited extent that x86 *anything* is supported, on RT. Offically, nothing is supported; the hack that we have uses a very clever emulation engine but only works on user-mode code (never kernel drivers, and probably never user-mode drivers unless the developer gets really ambitious). Open-source drivers *might* be recompilable - we've managed to get unsigned kernel-mode code execution - but even that is iffy. Closed-source ones, no chance.
http://google.com/search?q=hp+wifi+mouse
As the CNet review indicates, it only works with Win7 (and possibly Win8). I really doubt HP will actually provide driver for a 2-yr-old periph, especially since it has dumped on RT and is going with Android.
Essentially, you have an oddball periph that's limited to a particular OS. Rather than spending more time getting it to work, the simple fix is to spend the $10 and get yourself another wireless mouse.
Thank you for all your response.
here you go this is my mouse:
http://www8.hp.com/de/de/products/oas/product-detail.html?oid=5095508
Works fine with my Windows 8 Professional Notebook.
normaly i don't need the software. It's only for connecting. An other Mouse, which is older than my one, using an USB connector works with out problems with the RT. Only the USB connector into the USB hub, drivers are installed by Windows, and you can use the Mouse. I don't know maybe there are some ways to connect to the mouse. When looking for Wlan networks i found P2PHP-WIN-8. That's the Mouse-PC network connection. i tryed to login there with the RT, but it asks for a network key. And i don't have one for the mouse.
Someone an idea? I tryed the mouse ID and serial number. But doesn't worked
the mouse will use a proprietary protocol because frankly wifi mouses are so obscure that this is the first time I've ever heard of such a thing. That software likely includes the relevant drivers needed, not just initiate the connection. It just isnt going to work on RT until HP and microsoft work together to support it on RT which they likely wont.
Just go buy a normal mouse.
Wow... somebody actually used WiFi Direct for a mouse! Interesting.
It's possible that WFD will eventually be integrated into Windows as a generic driver, the way that UMS and MTP and HID and so forth are. In that case, assuming the mouse follows a reasonably standard interface convention (which is far from guaranteed from very early adopters of somewhat obscure technology...) it would probably work on whatever version of RT gets that generic driver (in the same way that BlueTooth -> HID can be used to load BT mice with a generic driver today). Otherwise, it will fall to HP and Microsoft to create a workign driver, and I doubt they'll bother.
my logitech mouse worked perfectly, just plug in the USB wireless receiver and a few secs later the mouse is working!
Turkishflavor said:
my logitech mouse worked perfectly, just plug in the USB wireless receiver and a few secs later the mouse is working!
Click to expand...
Click to collapse
this is a WiFi mouse not a usb mouse
Turkishflavor said:
my logitech mouse worked perfectly, just plug in the USB wireless receiver and a few secs later the mouse is working!
Click to expand...
Click to collapse
You didn't even bother to read the (at the time <1 page) thread, did you?
Related
USE ANY USB KEYBOARD WITH YOUR USB OTG SUPPORTED ANDROID DEVICE!!!!
I've been experimenting with Wifi cards and the samsung galaxy sII
and realized people where having the same problem as i was having with plugging in usb keyboards.
turns out it all has to do with a vendors permission issue. if your device is not in the list, it will seen as "unknown".
As it turns out you can simply add your device and it'll work. mind you it was to be a simple input device and will have the power constraints of 100mW. But if u can compile a driver and splice in dc power.... skies the limit!
steps:
1. Android must be rooted (not going over that) and must support USB OTG (on-the-go)
2. You can either buy a USB OTG micro to female adapter on ebay for like 4 bucks. i decided to make one myself since i have lots of spare parts.
Heads up: a simple micro usb to female usb connector IS NOT THE SAME AS A USB OTG CABLE, they may look the same but the OTG cable has Pin 4 grounded to pin 5 on the micro usb side. This is how the device distinguishes aach type of cable. WARNING: IF MAKING THIS YOURSELF DO NOT CROSS BLACK AND RED, this WILL fry your PHONE.if you don't know you rway around a soldering iron, just buy one
3. Check what manufacturer your device is on this chart, if it's not there, check on the internet or plug the usb device into a linux box and run "lsusb" in the command promt and look for your device, the number will look like this:
Bus ### Device ###:ID <THIS ONE!>:<more numbers> " Company"
here's the chart: (taken from here :http://developer.android.com/guide/developing/device.html)
Code:
Company USB Vendor ID
Acer 0502
ASUS 0b05
Dell 413c
Foxconn 0489
Garmin-Asus 091E
Google 18d1
HTC 0bb4
Huawei 12d1
K-Touch 24e3
KT Tech 2116
Kyocera 0482
Lenevo 17EF
LG 1004
Motorola 22b8
NEC 0409
Nook 2080
Nvidia 0955
OTGV 2257
Pantech 10A9
Philips 0471
PMC-Sierra 04da
Qualcomm 05c6
SK Telesys 1f53
Samsung 04e8
Sharp 04dd
Sony Ericsson 0fce
Toshiba 0930
ZTE 19D2
eg my keyboard is lenovo , so code is 17EF, you get it
4. log in as root, mount system as read-writeable, Create this file: /etc/udev/rules.d/51-android.rules
if its already there, then just append the command you want after.
if you dont have root explorer or otherwise installed here is how to in bash:
Code:
su
su
mount -o remount,rw system /system
mkdir -p /etc/udev/rules.d/
cd /etc/udev/rules.d/
now in the "51-android.rules" file add this line (or more for more device support):
SUBSYSTEM=="usb_device", SYSFS{idVendor}=="<VENDOR CODE>", MODE "0666", NAME=="<VENDOR>"
my example with my lenovo keyboard:
SUBSYSTEM=="usb_device", SYSFS{idVendor}=="17EF", MODE "0666", NAME=="lenovo"
save.
5. plug in the USB OTG cable and plug in your keyboard or other device. it sould say "usb host cable" then "usb device".
on some keyboards the numlock light wont work, due to the fact of power contraints on the phone, you can add support by plicing in 5v DC in to the line (soldering needed) or you can probably jsut attach a powered usb hub
And thats IT, now you can actually type documents at a reasonable pace, without paying an arm and a leg for a supported bluetooth keyboard!!!
-td8f4
* to moderators i know i have less than 50 posts hopefully i dont get banned, i thought this was considered dev*
Wow, really nice work - I wonder if some kindly ROM devs could just bake in support for all in their ROMs?
NZtechfreak said:
Wow, really nice work - I wonder if some kindly ROM devs could just bake in support for all in their ROMs?
Click to expand...
Click to collapse
wow really good work.
just another info on the price of an BT keyboard:
http://www.amazon.de/s?ie=UTF8&search-type=ss&index=ce-de&field-keywords=CHIN FAI
40 euro are not an arm and a leg
and this i ok to type on
Indeed, you can get some BT keyboards quite cheaply. I already have one, but I'd still like full USB keyboard support (I don't always have my keyboard on me, but lots of people have USB keyboards).
I tested this on an unrooted SGS (Logitech K340 unifying keyboard) and it worked fine without having to change any settings. Just plugged it into the USB OTG adapter and then plugged the adapter into the phone. It said the device was unknown but the keyboard worked when I went to type in the apps. Mice also worked. The logitech MX Performance worked fine. A bit weird seeing a mouse pointer on the phone though.
How about keyboard remapping?
Sent from my GT-I9100 using XDA Premium App
At first I thought:
"1) plug in OTG cable, 2) plug in USB keyb., 3) use"
*lol*
No, seriously, this information is VERY usefull and might open up the way not only for keyboard (as the OP stated, "get a driver compiled and the sky is the limit".
Will definitaly bookmark this thread and when I'm done with some other tinkerings try to "get the drivers compiled"
*clicksthanks*
reply
my ultimate goal is to have a external usb wifi adapter plugged into my phone so i can use it to pentest with a Backtrack 5 chroot session.
i'm working on cross compiling the RTL8187 driver for the ARM architecture.
look here for updates
HTML:
http://forum.xda-developers.com/showthread.php?p=16333147
and @ karl999999
40 euro are not an arm and a leg
and this i ok to type on
Click to expand...
Click to collapse
i know it's not expensive, but i'd really rather use something i already have, i've got a small flexible usb keyboard which works great.
As I'm trying to add joystick support on SGSII, I tried to add an xbox 360 controller and my device was not recognized. I tried this method and added "045E" as vendor but no luck, still not recognized... Any idea ?
Thanks
alx5962 said:
As I'm trying to add joystick support on SGSII, I tried to add an xbox 360 controller and my device was not recognized. I tried this method and added "045E" as vendor but no luck, still not recognized... Any idea ?
Thanks
Click to expand...
Click to collapse
Also interested in this... Sadly I dont have the skills to compile a driver myself...
Sent from my GT-I9100 using XDA Premium App
Thanks. This is so cool and I gotta try it at home later (Tried 2 different keyboards at home before but didn't work). Hopefully you could find a way to use PS3 joystick as well.
Maybe we collect a list of device code and update it a single file. Then rom developer can incorporate it into their roms.
Don't worry about post counts. The is definitively a very good finding and development progress for S2.
alx5962 said:
As I'm trying to add joystick support on SGSII, I tried to add an xbox 360 controller and my device was not recognized. I tried this method and added "045E" as vendor but no luck, still not recognized... Any idea ?
Thanks
Click to expand...
Click to collapse
We might have more luck with generic USB gamepads. I think all we need is someone who has the required knowledge to compile joydev.ko for our kernel.
testando said:
Also interested in this... Sadly I dont have the skills to compile a driver myself...
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
My skill is quite limited too but with some reading it's not that hard (and I can give some help too).
I am looking for support for my Plantronics USB Headset. I am able to control volume through the headset when connected to OTG, but can't route audio through them.
I believe we do need generic drivers for USB Headsets. Hope one of the elite developers can help us. I will be happy to donate 5 euros for the same
Also, my Microsoft Wireless combo (Desktop 6000 v3) do not work while my wireless mouse 1000 do work absolutely fine on the Phone.
I am also looking for NTFS Mass Storage support which seems to be currently limited to FAT32 (and possibly FAT16) only.
Prankey said:
I am looking for support for my Plantronics USB Headset. I am able to control volume through the headset when connected to OTG, but can't route audio through them.
I believe we do need generic drivers for USB Headsets. Hope one of the elite developers can help us. I will be happy to donate 5 euros for the same
Also, my Microsoft Wireless combo (Desktop 6000 v3) do not work while my wireless mouse 1000 do work absolutely fine on the Phone.
I am also looking for NTFS Mass Storage support which seems to be currently limited to FAT32 (and possibly FAT16) only.
Click to expand...
Click to collapse
There is a solution for that already. Search ntfs-3g or posts started by me.
Just tried my logitech wireless keyboard but doesn't work. May need to dig out some old wired keyboard to try later.
somebody can get the USB ID of EuroCase? i can't get it from the internet
takato23 said:
somebody can get the USB ID of EuroCase? i can't get it from the internet
Click to expand...
Click to collapse
Actually, you may found the id by S2 itself. Just install a terminal emulator and do the same lsusb command.
jackleung said:
Actually, you may found the id by S2 itself. Just install a terminal emulator and do the same lsusb command.
Click to expand...
Click to collapse
Okay i could get the usb id from eurocase (i've a keyboard+mouse 2.4ghz pack) It's 1D57. Now when i connect the recivier, says "connected a usb device". But when i try to use mouse or keyboard it get stuck on one letter. I've try with a genius keyboard also (ID 0566) and it does the same... the only device that it works is a Razer mouse (without doing a thing)
My Microsoft Wireless Mouse 1000 works perfectly fine. However my other Microsoft Wireless Desktop combo (6000 v3) doesn't.
Also, I am looking for a way to use my USB headsets. I am able to control volume through it, but can't route audio through it.
Hope one of the devs here would be generous enough to help us get our devices working
Writing a driver and firmware from scrarch is quite a bit more arguous than finding one that works with linux. Look for one.
Once I get this porting business figured out ill post a tut on porting. Maybe even a small vm of the ubuntu box, to avoid rebuilding the setup
Sent from my GT-I9100 using XDA App
Having Asus Vivotab RT faced with the serious problem - Windows RT has no drivers for a big (even most part) of peripherals (scanners. printers, MFP, usb-cameras etc). Its very sad for so expencive device (+OS). Peripherals manufacturers, seems, are not interested in drivers development for Win RT Becose of that, I can't use most part of peripherals at home or office. I've been trying to use win 7(8) drivers, installing them by clicking right button on .inf-file. But this way was unrealizable. So, is there any other way to solve the problem with less of peripherals drivers for Win RT???
Denis_63 said:
Having Asus Vivotab RT faced with the serious problem - Windows RT has no drivers for a big (even most part) of peripherals (scanners. printers, MFP, usb-cameras etc). Its very sad for so expencive device (+OS). Peripherals manufacturers, seems, are not interested in drivers development for Win RT Becose of that, I can't use most part of peripherals at home or office. This way was unrealizable. So, is there any other way to solve the problem with less of peripherals drivers for Win RT???
Click to expand...
Click to collapse
Read microsofts various pages and blog posts.
Manufacturers are not allowed to make drivers for windows RT. The jailbreak tool we have doesnt allow drivers to be added either.
Scanners and usb cameras are not supported in windows RT at all. Printers are.
We cant fix this problem. New drivers can only be installed via windows update. Microsoft has to do them. Its also a very difficult task for them to write drivers for the huge amount of hardware on the market.
Oh, we *can* install drivers manually... it's getting them past the signature enforcement that's a trick.
I suspect that the same jailbreak hack we have now can be modified to bypass the kernel mode driver signature enforcement. Either directly put the OS into Testsigning mode, or spoof the results of the signature check, or something else of that nature.
Of course, then you're in the same place as the desktop software problem: you can only run ARM code, and almost nobody is writing ARM drivers for Windows NT. Unlike with desktop software, there's also very few open-source NT drivers. Non-zero, but very, very few.
Scanner
Denis_63 said:
Having Asus Vivotab RT faced with the serious problem - Windows RT has no drivers for a big (even most part) of peripherals (scanners. printers, MFP, usb-cameras etc). Its very sad for so expencive device (+OS). Peripherals manufacturers, seems, are not interested in drivers development for Win RT Becose of that, I can't use most part of peripherals at home or office. This way was unrealizable. So, is there any other way to solve the problem with less of peripherals drivers for Win RT???
Click to expand...
Click to collapse
HP has an app for scanning, but only works for network capable scanners. I've tried it with my home scanner, which is actually an Epson, and to my surprise it actually worked. The name of the app is 'HP Scan and Capture'.
As far as printing goes, I've been able to connect to about a dozen or so. My Epson at home, and all of the HP LaserJets at work. A few I had to manually select a driver, on the older models, but they all printed. But that is HP, other brands are probably harder to work into it.
Other than reading storage, the cameras have no support. That is a bummer, especially since tethering a pro dslr would be awesome.
My Brother network printer worked perfectly but my Kodak didn't. I did have to select the driver manually in both cases
possible decision
So, may be there is possible way to resolve actual problem with poorest set of peripheral drivers (printers & scanners firstly) in win RT. The solution is to create some kind of the universal driver for all (most part of) printers with the simplest interface, containing minimal number of options. The main goal of those "unversal driver" is to make/force printer to print. The same way with scanners. If I'm not mistaken, such kind of work with peripheral is realized in some *unix-like OS.
Denis_63 said:
So, may be there is possible way to resolve actual problem with poorest set of peripheral drivers (printers & scanners firstly) in win RT. The solution is to create some kind of the universal driver for all (most part of) printers with the simplest interface, containing minimal number of options. The main goal of those "unversal driver" is to make/force printer to print. The same way with scanners. If I'm not mistaken, such kind of work with peripheral is realized in some *unix-like OS.
Click to expand...
Click to collapse
This is what windows RT does already. Tries to apply a set of unified drivers to multiple devices. doesnt really work as there is no set USB protocol for printers, nor a network one. Scanners are even worse.
If you go in device manager you will find most mice and keyboards appear as a USB HID device of some sort. This is because in this case a set standard was created for how mice and keyboards (and a few other devices too) should appear to an operating system. One USB HID Keyboard driver should work for all keyboards using the USB HID Keyboard protocol, basically, all of them Certain additional functions like variable dpi on mice and extra buttons might not work with that basic driver but the keyboard/mouse itself will still function as a basic keyboard/mouse, just none of the fancy features.
Printers dont do that. HP have a protocol they use. Epson have their own protocol. Lexmark have one. A lexmark driver wont work on an HP unit. Hell, the drivers for models with different features dont always work on another similar but not identical model from the same manufacturer. This means a driver is needed for each device. Windows RT makes a damn good attempt at covering many bases but there are too many printers out there for microsoft to make that many drivers, gets even worse when you consider microsoft are working on drivers for hardware not manufactured by them although I guess they get help from the OEM.
There are standard interfaces for keyboards, mice and removable media. There aren't any for printers, scanners, wifi adaptors or 3g modems etc.
SixSixSevenSeven said:
Printers dont do that. HP have a protocol they use. Epson have their own protocol. Lexmark have one. A lexmark driver wont work on an HP unit. Hell, the drivers for models with different features dont always work on another similar but not identical model from the same manufacturer. This means a driver is needed for each device. Windows RT makes a damn good attempt at covering many bases but there are too many printers out there for microsoft to make that many drivers, gets even worse when you consider microsoft are working on drivers for hardware not manufactured by them although I guess they get help from the OEM.
There are standard interfaces for keyboards, mice and removable media. There aren't any for printers, scanners, wifi adaptors or 3g modems etc.
Click to expand...
Click to collapse
There actually ARE standards for printers, like PS and PCL6. The problem is that for many of the cheaper printers, the manufacturers don't bother implementing them.
Also, Microsoft has implemented new class drivers for cellular modems, but the problem is that the older devices don't really support those.
May well be that microsoft are just supporting those 2 protocols then and hoping that the users printer complies with it.
SixSixSevenSeven said:
May well be that microsoft are just supporting those 2 protocols then and hoping that the users printer complies with it.
Click to expand...
Click to collapse
They didn't only use those, but they did rebuilt the print model. They then tried to cover a broad swath while at the same time knowing that they wouldn't cover all of them, at least partly because including a driver for every single printer ever would take a lot of work and a lot of storage space. They expected to cover 70-80% of the installed base of printers (whereas apparently Windows 7 only covered 60-65% out of the box), while cutting down storage by over half:
http://blogs.msdn.com/b/b8/archive/2012/07/25/simplifying-printing-in-windows-8.aspx
I know it's not really an answer for those with existing printers that don't work, but it is complicated to cover everything when manufacturers all have their own proprietary stuff (and often, multiple proprietary protocols, not just a single one for all their devices).
I'm trying to connect my Nexus 7 2013 with android 4.4 (didn't work on the 4.3 either) to my windows 7 PCs (both 64 and 32 bit). The pairing works but Windows won't install a driver. My Windows 7 Device Manager shows Bluetooth Peripheral Device - driver not found. I cannot find a driver anywhere.
I contacted Asus and asked which driver I can use and they replied that no such driver exists:
Dear Mister XXXX,
Thank you for your trust in our technical support.
Concerning the fact that you can’t find the Bluethooth drivers for Windows 7 I regret to inform you that doesn’t exist these types of drivers.
If your desire is to activate a tethering function, I regret to inform that this manipulation will not work, because the system of your product doesn’t support it.
Thank you for your understanding.
Have a nice day.
Best Regards,
Click to expand...
Click to collapse
Did anyone find a compatible driver? I searched already for a few hours the net and can only find problems with the bluetooth concerning connecting to devices like keyboard.One guy mentioned that bluesoleil provides a software which might work. Has anyone tried that?
My ultimate goal is to use my PC as a Bluetooth speaker for my tablet,
Arsneca said:
I'm trying to connect my Nexus 7 2013 with android 4.4 (didn't work on the 4.3 either) to my windows 7 PCs (both 64 and 32 bit). The pairing works but Windows won't install a driver. My Windows 7 Device Manager shows Bluetooth Peripheral Device - driver not found. I cannot find a driver anywhere.
I contacted Asus and asked which driver I can use and they replied that no such driver exists:
Did anyone find a compatible driver? I searched already for a few hours the net and can only find problems with the bluetooth concerning connecting to devices like keyboard.One guy mentioned that bluesoleil provides a software which might work. Has anyone tried that?
My ultimate goal is to use my PC as a Bluetooth speaker for my tablet,
Click to expand...
Click to collapse
Even I need a way to set this up. Any one knows the solution?
You shouldn't need to install a driver on the desktop or laptop. That defeats the whole purpose of Bluetooth as conveniently connecting two devices.
What kind of Bluetooth adapter do you have on the PC, built-in or an external adapter? Fire it up, turn on Bluetooth on your N7, and pair one to the other.
The dongles driver was all I needed. Then I just paired and connected like I do every Bluetooth device. My understanding is that there is no need for drivers for the tablet, simply for the Bluetooth dongle. After that they just pair the way all Bluetooth pairs.
I've been around Linux for a few years now, and have had my Galaxy Tab 3 7.0 for about a year. I've run into a bit of a problem that maybe someone knows how to get around. I have some knowledge of android because of the relationship to Linux... but still rather a newbie.
I'm trying to get my Tab 3 to communicate with a Bolutek BLK-MD-BC04-B serial to bluetooth adapter. I have no problems pairing it with my tablet, but once paired only certain software packages will connect with it... and I have no use for a bluetooth communications terminal (the usual software). I can get everything to work on my main computer (running Ubuntu 12.04LTS) the way I want, but I can't find /dev/rfcomm0 on my tablet. I've tried several software packages from the Google store, but to no avail (so far).
What I'm trying to accomplish overall is getting a piece of equipment I have to work with an android tablet, that at present only works with Windows software. I've got W95 working on a virtual machine in my tablet (a tiny tad slow, but it works well enough) using the no-longer-maintained program "Limbo" and the only thing stopping me now is getting the signal from the serial port (on the equipment) to the virtual machine in my tablet. The adapter works as it should, the only problem is the android bluetooth.
Does anyone know how to get the tablet to connect to the Bluetooth adapter (it's already paired), and then assign the communications to rfcomm0 (or maybe put a virtual link to ttyS0/ttyS1)?
Better yet, is there also anyone with experience working with this Limbo software who could give suggestions how to get a serial port working in it? (It should be easy to do once I figure it out - I've got the whole thing working fine on my main system using Virtualbox, and it was easy.)
I'm on an extremely tight budget (dirt poor actually - typical graduate student) and need to work with what I have, so please no suggestions of buying a new tablet or anything like that.
Thanks!
So I found a way on how to connect the darn thing to my Lumia, but it's still unusable. The phone does connect to the controller and says it's connected but the controller itself is having some difficulties in connecting... Not sure if this is a problem with cloned DS3 controllers (yes, I do have a clone, no money to buy a legit DS3 controller right now and I'm using that DS3 controller on my Nexus 7 with SIXAXIS Controller app, works great even for a clone)... Can anyone here try this with a legit controller?
Here's a video:
Sorry for my voice thou....
So how did I managed to get it paired? Simple... Changed my Bluetooth dongle's device class to 0x5 (applied 0x58030) and MAC address to the DS3 controller. You need Linux to change the MAC and Class as Windows doesn't allow that (used Kali Linux)
Some stuffs I read to make this possible: http://blog.petrilopia.net/linux/change-your-bluetooth-device-mac-address/ and http://www.slideshare.net/null0x00/hijacking-bluetooth-headsets
After BT's device class and MAC Address, paired the dongle to Lumia... The Lumia itself sees it as 0x5 and MAC Address to my DS3's MAC. After pairing, turned OFF Bluetooth on my Lumia, connected my DS3 to my Nexus 7 via USB for pairing with SIXAXIS Controller app , Paired to my Lumia's BT MAC Address, after doing that, turned on my Lumia's BT first, then turned on the controller, and voila.
Yes I know it's kinda complicated process because on how a DS3 controller works (it's not visible, you literally need something to pair it to your device or to your other devices) but hey at least we know that it's possible to connect a DS3 (or even a DS4 controller) to Windows 10 Mobile (and also Windows Phone 8, WP8 already had MOGA controller support).
Created this thread here so we can attract some clever devs for the possibility to make the DS3/DS4 controller (or even better, any Bluetooth controllers) to work with Windows Mobile. Android, iOS, and even WinMo 6 (yes, Microsoft's mobile OS before Windows Phone 7 lives, see CobaltController by @Cobaltikus ) already had DS3 support, so why not add WP/Win10 Mobile to the list? We already got Interop Unlock and access to device drivers so this stuff can be possible on WP/Win10Mo too...
Anyone agree with me?
Sent from Ponyville
You can install any of Android Sixaxis controller apps via Project Astoria (I have DualShock too, but have not yet tried to install any of the Android controller applications)
adijagiel said:
You can install any of Android Sixaxis controller apps via Project Astoria (I have DualShock too, but have not yet tried to install any of the Android controller applications)
Click to expand...
Click to collapse
That will simply not gonna work as Astoria doesn't allow Bluetooth (see build.prop on Astoria, it had a line of Bluetooth disabled). Also, root doesn't work for now... And also, minimizing an app on Astoria pauses it... We need a native Windows app to do so...
Sent from Ponyville