MK808B & Dualshock 3 ?

[mini-pea-si]

Hello, I just bought a MK808B original running Finless 1.7 and i want to use my PS3 BT controller. Ive downloaded the Sixaxis controller app and followed an online tutorial but i can't pair it with my stick. It shows me that it failed. So can someone help me by giving me a link how to do it or is the MK808B still not able to handle DS3 by Bluetooth?

Thank you!

[Mandrake2]

Hi, you must change MAC address Joypad ps3 (or clone p3, i use a clone) with SixaxisPairTool (Windows). See tutorial web. Remember, write down on a sheet of paper (or save it in Notepad) the Mac address of your Joypad PS3.
Then with SixaxisPairtool change the Mac by entering the MAC of MK808B.
Now on MK808B with SIXAXIS controller selections start (in preferences remember to select gamepad), remember also to enable in Language and Keyboard : Controller Sixaxis. Here a tutorial xda for Xperia phone (but you can see it): http://forum.xda-developers.com/show....php?t=1834091

[mini-pea-si]

Thanks!!! I was doing it wrong!

[metri]

What range do you get with the PS3 remote and the MK808B... I get about 4 feet and then it stops responding. Just wondering about anyone else?

[mini-pea-si]

What range do you get with the PS3 remote and the MK808B... I get about 4 feet and then it stops responding. Just wondering about anyone else?

I did a test, I was like 20 feet away in the bathroom and it was still working fine. You should have a good range with bluetooth...Do you have real PS3 controller?

[metri]

I did a test, I was like 20 feet away in the bathroom and it was still working fine. You should have a good range with bluetooth...Do you have real PS3 controller?

No real PS3 controller.... I did but at the time PS3 controllers weren't compatible. I got a clone and took all the buttons out of the orignal and put them in the clone for better look and fee. Then a friend had his PS3 controller battery die and I sent him the guts.... No I don't have one. I'll get one though because you say it works well

Do you have any problems with any emulators and the controller working in the menus, but then not in the games? I have this problem and must unplug and re-plug USB controllers (or xbox 360 wireless) controller every time I enter a game in an emulator... very very odd.

[mini-pea-si]

Do you have any problems with any emulators and the controller working in the menus, but then not in the games? I have this problem and must unplug and re-plug USB controllers (or xbox 360 wireless) controller every time I enter a game in an emulator... very very odd.

Thats weird, I tried a Snes and Nes emulator and its working perfectly, I can navigate in the menus with ps3 controller and its still work in the game. I opened others apps and let the emulator in the background, i came back and controller was still linked and working good.

Theres a box that i checked in preferences in Sixaxis app, enable gamepad. Maybe its your emulator...idk?

[metri]

Thats weird, I tried a Snes and Nes emulator and its working perfectly, I can navigate in the menus with ps3 controller and its still work in the game. I opened others apps and let the emulator in the background, i came back and controller was still linked and working good.

Theres a box that i checked in preferences in Sixaxis app, enable gamepad. Maybe its your emulator...idk?

Thanks for trying it. For me it's a problem with USB controllers and the xbox controller. I don't have a PS3 controller to try. I do have 3 MK808B though so I'll pull another one out and try that. I'm using NES.emu, PCE.emu etc. I'll look into it more. I'm glad to here it's not everyone, there is hope for the perfect retro gaming toy!

[mini-pea-si]

Thanks for trying it. For me it's a problem with USB controllers and the xbox controller. I don't have a PS3 controller to try. I do have 3 MK808B though so I'll pull another one out and try that. I'm using NES.emu, PCE.emu etc. I'll look into it more. I'm glad to here it's not everyone, there is hope for the perfect retro gaming toy!

No prob! I have Nes.emu too and no bug. Yeah, it might be your controller or bluetooth. Its awesome for retro gaming, its working really well! My only problem is that for the games that dont support a controller, it didn't work for me trying to map the controls with the touch emulation. I only tried once though, ill have to do more tests

[mrfunnyman]

No prob! I have Nes.emu too and no bug. Yeah, it might be your controller or bluetooth. Its awesome for retro gaming, its working really well! My only problem is that for the games that dont support a controller, it didn't work for me trying to map the controls with the touch emulation. I only tried once though, ill have to do more tests

Yes this is a known issue with the TV Players that the sixaxis software cannot detect the touchscreen and disables the emulation mapping. Someone mentioned it might be driver related from the software checking for touchscreen hardware.

[Finless]

There is no touch screen drivers or support in any of the TV player ROMs (kernel). They removed it and modified framework to use only a mouse, joystick, etc. So any games that use only touch input will not work and the joy2center / sixaxis APPS will complain there is no touch screen!

Problem is, to really solve this a touch screen driver would have to be enabled in the kernel and set to the proper resolution. All the tweaks to make the mouse work like it does (which is not the same as a tablet with a touch screen) would have to be taken out.

Then you could use one of these joystick APP to map touches.

A prime example. My N101 ROM (tablet) will flash on a TV stick using the TV stiock kernel. You will see how different the mouse works! But because the TV stick kernel does not have a touch driver, touch still wont work.

BUT... if we could get kizs or omegamoon to put a touch driver in a kernel for say 1280x720 rez, then I could port a tablet ROM and BAM... we now have touch support. But this would be a "gaming ROM" as the mouse will now not work as it really should for a TV player (e.g. right mouse click will not go back, etc).

But it could be done.

Bob

[metri]

This brings up a question I have, and Bob I think you partly answered it. My flymouse (mele F10) has a middle mouse button, which in the stock ROM is mapped to the first mouse button so they do the same thing. Now with Finless 1.7, this button does nothing. I'm guessing now the kernel doesn't map BTN_MIDDLE: mapped to MotionEvent.BUTTON_MIDDLE to do anything. I read all about .idc files and Key Layout Files etc. but the ability to make this event do anything isn't there. So I'm guessing this has to be done in the kernel at compile time? Personally I'd like BTN_MIDDLE to be a key event, easy to deal with for customizing a flymouse...

While poking around I did learn about .kl files and mapped all my controllers to common button names, so my SNES, PSX, and XBOX 360 have compatible button names and I don't have to reconfigure my emulators when I change controller

[mrfunnyman]

There is no touch screen drivers or support in any of the TV player ROMs (kernel). They removed it and modified framework to use only a mouse, joystick, etc. So any games that use only touch input will not work and the joy2center / sixaxis APPS will complain there is no touch screen!

Problem is, to really solve this a touch screen driver would have to be enabled in the kernel and set to the proper resolution. All the tweaks to make the mouse work like it does (which is not the same as a tablet with a touch screen) would have to be taken out.

Then you could use one of these joystick APP to map touches.

A prime example. My N101 ROM (tablet) will flash on a TV stick using the TV stiock kernel. You will see how different the mouse works! But because the TV stick kernel does not have a touch driver, touch still wont work.

BUT... if we could get kizs or omegamoon to put a touch driver in a kernel for say 1280x720 rez, then I could port a tablet ROM and BAM... we now have touch support. But this would be a "gaming ROM" as the mouse will now not work as it really should for a TV player (e.g. right mouse click will not go back, etc).

But it could be done.

Bob

Bob I am not as wise in the ways of android as you but based on this seperate forum it appears that the virtual touch has already been developed and confirmed working with the MK802 stick.

Please read and help if possible.

http://www.rikomagic.co.uk/forum/viewtopic.php?f=11&t=3845

[Finless]

Bob I am not as wise in the ways of android as you but based on this seperate forum it appears that the virtual touch has already been developed and confirmed working with the MK802 stick.

Please read and help if possible.

http://www.rikomagic.co.uk/forum/vie...hp?f=11&t=3845

If you read that it is not really working as a "mutli" touch screen but a touch pad. Unless I missed something?

Bob

[mrfunnyman]

If you read that it is not really working as a "mutli" touch screen but a touch pad. Unless I missed something?

Bob

I understand what you are saying but this appears to be a possible working workaround for the sixaxis and other BT profile mappings for single touch gestures.

From the forum link ...

hello, just to update my test with your virtual touchscreen driver with Sixaxis Controller.

My device is Probox2 aka UHost2. The Official firmware has virtual touch screen built in so Sixaxis work out of the box (i havne't notice this before so i just wasting my time until your work showed up). I also have MK802IIIs in hand but i didn't test it because it can't play some games i want right now (Let's golf 3 = just back to home screen, Asphalt 7 Heat = license check loop). Even on UHost2, Let's golf 3 also can't play with same result but Asphalt 7 is working.

But i have tried Fineless 1.5 ROM for MK808B which modified from MK808B's Official FW on my UHost2 and found out that it doesn't have virtual touch screen driver. But with your virtual touch screen driver Sixaxis seems to work fine I just tested it for a short time with game Death Dome and back to Official UHost2 FW because on Finless ROM it can't play Asphalt 7 (license check loop). Let's Golf 3 can run but looks like screen size isn't right and cause incorrect button position on screen.

So at this point i can confirm that your touch screen driver can use with Sixaxis Controller to enable touch profile on device that not have hardware touch screen. But according to your screen orientation bug i can't confirm if it exist with Sixaxis for now. If you or others prefer more info or testing on Sixaxis + MK802IIIs + your driver, i can test with my available resource (the games i currently purchased)

For me, your virtual touch screen driver is a huge enhancement in gaming area for android mini pc. i think there're many users that suffer from lack of touch profile on Sixaxis Controller like me. i'd like to see your driver to be known by other users that have difference devices but may support your driver so they're more happy with thier devices