@shabbypenguin @mad cat rich, @Mad Catz Nate
Guys, any chance of a work around for getting the inbuild BT4 HW working on android 4.2.2?
Did a google search found:
http://forum.xda-developers.com/showthread.php?t=2492436
Don't worry, "Minumum Android 4.3 version required!"
Two usb ports, but we can only use one is a bit :laugh:
Info:
http://stackoverflow.com/questions/20332277/bluetooth-low-energy-api-for-jelly-bean-4-2
"Android's SDK doesn't have support for BLE prior to 4.3.
Third party libraries can enable BLE on Android 4.2 and lower where the device's hardware supports BLE,
such as on Samsung's S III, 4 and Note 2 and on the HTC One.
I only have experience using Samsung's SDK on 4.2 (which is now deprecated), so I can't really help you further.
I can't reiterate enough-- there is no standard BLE support on Android 4.2 and lower.
You'll need to use third party solutions on a per-device basis."
reading up on that link doesnt show promise for 4.2
ive been trying to get a custom recovery going so i could begin work on an aosp based rom, many of the "bugs" with the stock rom could then be fixed and people might start picking this up if it had support. i have kernel source downloaded and have been meaning to try out a custom kernel but i still havent even gotten a custom recovery booting. it doesnt appear they use a DTB file, so i believe my boot.img is packed correctly, yet all i get is a black screen. seeing as there hasnt been an update to the kernel source i dont expect much in terms of support, especially considering ive now asked multiple places and mad catz hasnt replied to any of my questions, it seems if i couldnt figure out how to pair my controller or turn the volume up i could get some answers but not if i have dev related questions :/.
shabbypenguin said:
reading up on that link doesnt show promise for 4.2
ive been trying to get a custom recovery going so i could begin work on an aosp based rom, many of the "bugs" with the stock rom could then be fixed and people might start picking this up if it had support. i have kernel source downloaded and have been meaning to try out a custom kernel but i still havent even gotten a custom recovery booting. it doesnt appear they use a DTB file, so i believe my boot.img is packed correctly, yet all i get is a black screen. seeing as there hasnt been an update to the kernel source i dont expect much in terms of support, especially considering ive now asked multiple places and mad catz hasnt replied to any of my questions, it seems if i couldnt figure out how to pair my controller or turn the volume up i could get some answers but not if i have dev related questions :/.
Click to expand...
Click to collapse
Yeah, it's not (re link), but it's funny on: http://madcatz.com/mojo/en-ca/
Ready to Root
As any Android power-user knows, the best way to get the most out of your device is to root it. Root access opens up all sorts of options including adding custom keymapping capabilities and installing custom ROMs. Mad Catz provides a short step-by-step guide to rooting, and our tech support team is ready to help.
The best part – rooting won’t void your warranty.
Click to expand...
Click to collapse
Seems such a waste of a usb port
Edit: Oh and the kernel src works fine, shame it isn't any help re the old BT stack
gwaldo said:
Yeah, it's not, but it's funny on: http://madcatz.com/mojo/en-ca/
Seems such a waste of a usb port
Edit: Oh and the kernel src works fine, shame it isn't any help re the old BT stack
Click to expand...
Click to collapse
@Mad Catz Nate, @Mad Catz Rich do you guys know Dalin from:
https://www.youtube.com/watch?v=iGlMAuKZoP0
Any chance he can answer some custom rom questions?
gwaldo said:
@shabbypenguin @mad cat rich, @Mad Catz Nate
Guys, any chance of a work around for getting the inbuild BT4 HW working on android 4.2.2?
Did a google search found:
http://forum.xda-developers.com/showthread.php?t=2492436
Don't worry, "Minumum Android 4.3 version required!"
Two usb ports, but we can only use one is a bit :laugh:
Info:
http://stackoverflow.com/questions/20332277/bluetooth-low-energy-api-for-jelly-bean-4-2
"Android's SDK doesn't have support for BLE prior to 4.3.
Third party libraries can enable BLE on Android 4.2 and lower where the device's hardware supports BLE,
such as on Samsung's S III, 4 and Note 2 and on the HTC One.
I only have experience using Samsung's SDK on 4.2 (which is now deprecated), so I can't really help you further.
I can't reiterate enough-- there is no standard BLE support on Android 4.2 and lower.
You'll need to use third party solutions on a per-device basis."
Click to expand...
Click to collapse
An article I read recently said that a firmware update is due soon which will make the MOJO controller useable with BT2.2. Not as good as an OS upgrade to 4.4, but at least it will remove the need for the dongle.
Domomojo said:
An article I read recently said that a firmware update is due soon which will make the MOJO controller useable with BT2.2. Not as good as an OS upgrade to 4.4, but at least it will remove the need for the dongle.
Click to expand...
Click to collapse
I didn't think the mojo's ctrlr had BT2.2 HW.
I thought the update was coming for the retail CTRLR to update it to BT4
http://store.madcatz.com/brands/mad-catz/Mad-Catz-C-T-R-L-R-Mobile-Gamepad.html
A first for gaming peripherals, this version C.T.R.L.R employs a premium dual-mode Bluetooth 4.0 chip to ensure power-efficient compatibility with current Bluetooth Classic devices. Courtesy of a USB to Micro-USB port, future firmware updates will help ensure compatibility with upcoming Bluetooth Smart devices. Future updates will also boost power efficiency and minimize latency.
Click to expand...
Click to collapse
Hope, I'm wrong though :/
gwaldo said:
I didn't think the mojo's ctrlr had BT2.2 HW.
I thought the update was coming for the retail CTRLR to update it to BT4
http://store.madcatz.com/brands/mad-catz/Mad-Catz-C-T-R-L-R-Mobile-Gamepad.html
Hope, I'm wrong though :/
Click to expand...
Click to collapse
Well...I was under the impression that the retail CTRLr already supported both BT2.2 and BT4.0, but after reading what you posted I'm not so sure. Also, I am unable to find find the review I read that stated that the MOJO CTRLr would soon receive a firmware update making it BT2.2 compatible. Seems rather odd that the first version of the CTRLr shipped (the version that came with MOJO) would support only the new BT4.0 standard, while the retail version, which shipped much later, only supports BT2.2. If that is the case, it would have made more sense to ship MOJO with the BT2.2 CTRLr, upgrade it to BT4.0 when the available firmware AND KitKat were available, and not even bother with a dongle.
Domomojo said:
Well...I was under the impression that the retail CTRLr already supported both BT2.2 and BT4.0, but after reading what you posted I'm not so sure. Also, I am unable to find find the review I read that stated that the MOJO CTRLr would soon receive a firmware update making it BT2.2 compatible. Seems rather odd that the first version of the CTRLr shipped (the version that came with MOJO) would support only the new BT4.0 standard, while the retail version, which shipped much later, only supports BT2.2. If that is the case, it would have made more sense to ship MOJO with the BT2.2 CTRLr, upgrade it to BT4.0 when the available firmware AND KitKat were available, and not even bother with a dongle.
Click to expand...
Click to collapse
I think:
BT4 only on mojo (cheaper not using the 'premium dual-mode Bluetooth 4.0 chip' - besides BT4 comes standard on phones/tablets since 2013 )
BT2 on retail, I guess it's the common denominator, get it working first and ship it out, patch it later.. good reason to have the micro-usb port.
It's a shame android 4.3 wasn't out when they started though :'(
Anyway, I'm still hopeful MC will deliver on kitkat and the CTRLR upgrade, IMO still too far from end of life (not like ouya!! 2010HW lol).
gwaldo said:
I think:
BT4 only on mojo (cheaper not using the 'premium dual-mode Bluetooth 4.0 chip' - besides BT4 comes standard on phones/tablets since 2013 )
BT2 on retail, I guess it's the common denominator, get it working first and ship it out, patch it later.. good reason to have the micro-usb port.
It's a shame android 4.3 wasn't out when they started though :'(
Anyway, I'm still hopeful MC will deliver on kitkat and the CTRLR upgrade, IMO still too far from end of life (not like ouya!! 2010HW lol).
Click to expand...
Click to collapse
From xpcoin.com/2014/05/09/mad-catz-ctrlr-android-bluetooth-gamepad/
"The retail CTRLR versus the MOJO CTRLR
If you have a MOJO CTRLR (mine is model: 32263) there are a few differences to the retail CTRLR (mine is model: 32266).
1. Obviously the retail Madcatz logo on the right grip is red instead of the grey of the MOJO CTRLR.
2. The media, start and select buttons are black instead of silver.
3. The mode switch has a nipple/tab instead of a groove which required nails!
4. The home button on the retail CTRLR has a shorter press, the MOJO CTRLR has a deeper button.
5. The most important difference is that the retail CTRLR also supports Bluetooth 2 (classic) devices, the MOJO CTRLR is Bluetooth 4 only."
Domomojo said:
From xpcoin.com
Click to expand...
Click to collapse
Yeah, that's my blog...
I've been looking more deeply into the MOJO's controller dongle, it's not a BT4 adapter as I initially thought, but specific to the MOJO's CTRLR.
Explains why it can't be removed.
I can also confirm the MOJO's controller doesn't connect to BT2.
I haven't tried the retail or the MOJO's controller on a BT4 device, but I expect the MOJO's controller to work.
The retail CTRLR *should* work on BT4, if not then we wait for the firmware update :/
I wrote in more detail on the same page at the bottom.
bluedroid
Anyone know anything about bluedroid?
With the BlueZ 5.21 release the support for Android is now fully comparable with Bluedroid. Using BlueZ for Android enables additional features on top of it.
When using Bluedroid, you get support for Bluetooth 4.0 core technology and for HFP 1.5, A2DP 1.2, AVRCP 1.3, PAN, HID, HDP, OPP, MAP, PBAP and GATT profiles.
With BlueZ for Android you get additional support for Bluetooth 4.1 core technology and upgraded profiles including HFP 1.6 + Wideband speech, A2DP 1.3, AVRCP 1.5 and MPS. It also provides full integration for aptX(R) high-quality low-latency codec from CSR (codec license not included).
This is significant upgrade of features that are additionally supported and fully integrated. BlueZ for Android is a real value add proposition.
For the Bluetooth qualification of Android, the full documentation of PICS, PIXIT and PTS instructions is available available. This makes qualification easy.
Click to expand...
Click to collapse
Looks like it's a BT stack replacement, maybe able to back port it.
https://gitorious.org/android-bluez
also looking at http://wiki.cyanogenmod.org/w/Doc:_porting_intro
:/
Just tried connecting the mojo controller to my nexus 5 and my nexus 5 wouldnt read it one bit, plugged in an otg cable and the dongle and instant connection. my guess is this will never work without the dongle, almost as if its hard coded to look for it. for it to be using BT 4.0 i must admit it has a pretty terrible range at that too.
shabbypenguin said:
Just tried connecting the mojo controller to my nexus 5 and my nexus 5 wouldnt read it one bit, plugged in an otg cable and the dongle and instant connection. my guess is this will never work without the dongle, almost as if its hard coded to look for it. for it to be using BT 4.0 i must admit it has a pretty terrible range at that too.
Click to expand...
Click to collapse
Thanks shabbypenguin, That's what I feared.. maybe a firmware update will fix that tho :/
On their site, called a 'USB Nano Dongle'
BLUETOOTH USB ADAPTER – The included adapter connects the C.T.R.L.R to computers or other systems that lack Bluetooth support.
Click to expand...
Click to collapse
What's terrible? I get great range.. from the other side of the house.. 15m through walls... i'm running cheap rechargeables.
odd, i have mine under my desk hooked to my monitor and if i have my controller on more than 3-4 feet away i get terrible lag until i move closer, the batteries could be an issue though...
shabbypenguin said:
it doesnt appear they use a DTB file, so i believe my boot.img is packed correctly, yet all i get is a black screen.
Click to expand...
Click to collapse
Hey,
I have no idea what a DTB file is, but I googled around and found this:
http://forum.xda-developers.com/showthread.php?t=2428117
benjaminwan said:
I modified the split tool to support dtb, please test it……
Modify permissions before you use it
chmod a+x split_bootimg_dtb.pl
View attachment 2229037
Click to expand...
Click to collapse
oh no, they dont use it which is odd because the shield does. you can take stock recovery and unpackl it and repack it and it will boot just fine with no dtb file. yet for some reason the kernel source has a dts/dtb file :/
i just wish i understood why nothing seemed to work, ive managed to port cwm/twrp and build an entirely working cm rom for another device in the time that its taken that i still dont know what is going on with the mojo.
shabbypenguin said:
yet for some reason the kernel source has a dts/dtb file
Click to expand...
Click to collapse
yip, I see them all in kernel/arch/arm/boot/dts
But it's it's just a feature of the kernel, how do you know if it's used or not used in a boot.img?
When you boot using your repacked boot.img does it show an error?
I guess because there's no adb there's no logging either :'(
Yeah, wow
gwaldo said:
yip, I see them all in kernel/arch/arm/boot/dts
But it's it's just a feature of the kernel, how do you know if it's used or not used in a boot.img?
When you boot using your repacked boot.img does it show an error?
I guess because there's no adb there's no logging either :'(
Yeah, wow
Click to expand...
Click to collapse
normally ive known by taking their boot.img from stock and extracting the dtb and that will tell me if they use it or not. when i repack it boots fine, just doesnt do much :/ and yea without adb this is kind of sucking, im gunna ask around today and see if i can make any headway with it.. :/
shabbypenguin said:
normally ive known by taking their boot.img from stock and extracting the dtb and that will tell me if they use it or not. when i repack it boots fine, just doesnt do much :/ and yea without adb this is kind of sucking, im gunna ask around today and see if i can make any headway with it.. :/
Click to expand...
Click to collapse
Not sure if you know about this or for anyone else interested.
The mojo.boot image has ADB capabilities, it has the server: /sbin/adbd
Android got a security feature you can turn on or off. Usually this should be enabled for production environment and disabled for development devices. By turning security off, you can gain root access.
Edit /default.prop in the root file system and set the property "ro.secure=0".
There's also a "ro.debuggable=0" which should be changed to 1
In file init.goldfish.rc has eth0 network settings, so I expect ADB to work via that.
on boot
setsebool in_qemu=1
restorecon /sys/qemu_trace/process_name
restorecon /sys/qemu_trace/state
restorecon /sys/qemu_trace/symbol
setprop ARGH ARGH
setprop net.eth0.gw 10.0.2.2
setprop net.eth0.dns1 10.0.2.3
Click to expand...
Click to collapse
init.mojo.rc also has ADB set up:
# Enable ADB over TCP
setprop service.adb.tcp.port 5555
Click to expand...
Click to collapse
init.mojo.rc and init.usb.rc files has USB ADB settings, not sure what it does or how to use ADB via USB.
edit: init.rc , the main boot script
# adbd is controlled via property triggers in init.<platform>.usb.rc
service adbd /sbin/adbd
class core
socket adbd stream 660 system system
disabled
seclabel u:r:adbd:s0
# adbd on at boot in emulator
on property:ro.kernel.qemu=1
start adbd
Click to expand...
Click to collapse
But no mention of init.goldfish.rc where the eth0 ADB settings are.
Anyone know what init.goldfish.rc does here or if it's used at all?
Tried pinging 10.0.2.2 and 10.0.2.3 in fastboot mode and recovery mode via ethernet but nothing
Goldfish isnt actually used, its the emulator, its included in every build of android because with a simple build.prop edit you can tuirn any device into an emulator (most of the time it breaks it). the default.prop you can edit every time to those values but thats actually part of the ramdisk from boot.img and is a temporary file, as soon as you reboot it will be rebuilt according to the file in the kernel. ive tried everything i could think of to get adb working via usb and it doesnt even detect the device, its infuriating because while adb over wifi "works" its a half ass attempt. even still now mad catz refuses to answer any of my questions , if i had to guess its because none of them actually klnow either.
Related
Hi!
I am developing an application which connects a Wiimote to a bluetooth enabled android phone/device.
I did this by interfacing with the native bluez bluetooth library directly, rather than via the Android API. The reason for this is that Android API doesn't support HID devices, which a Wiimote is.
A problem now is that on some devices, mostly those sold by HTC, my app simply doesn't work. After calling the hci_get_route(NULL), this function should return an id of the first bluetooth device available (most likely 0), but instead returns ERNODEV (-1) as if no bluetooth device is available.
I suspect it has something to do with our beloved HTC grossly modifying something in the libbluetooth library to make this fail to work.
Has anyone ever done this kind of bluetooth interfacing?
How could I make this work?
Rooting the phone and replacing a library or two would be fine too.
For a list of working and non-working devices, check out the 2nd post of this thread.
HTC support
I just sent a customer service message to HTC about this issue. I hope they can get back to me with a "we'll work on it" message, or something. I really want this on my incredible. I'm new to coding like this, but could you disguise the Wiimote as another kind of device?
Just a response from someone equally interested in a solution. I'm trying to set up a bluetooth keyboard (Freedom Pro) with my gsm Hero running the 1.5 based MCR 3.2. Available drivers (Freedom's own, BlueInput & KeyPro) should work with 1.5, but HTC devices, especially the Hero, seem to be lacking something that is present in most 1.5 builds.
Investigating, I find the same issue of no route to device, because there is no known device. AIUI when bluetooth is turned on hciattach is used to establish a link to the hardware. At that point an hciconfig should list the hci0 device as present but down. However I find this list remains empty at all times.
I found this for keyboards.
Since I can't post the link, it's called "KeyPro for Android"
Google "keypro android" and click the first link.
Maybe that could help. It says it works with any android device above 1.5, however, I did read that some keyboards use a different type of bluetooth profile, SPP rather than HID.
I haven't heard back form HTC yet either.
EDIT: Upon reading your post again, you have tried this. Sorry, my bad.
Thanks for looking though The Freedom Pro is switchable between spp & hid profiles, so I figured I was safe, lol. Not with HTC's butchered 1.5 bt it seems.
Did you ever try to use the most likely id 0 on an HTC device? Even though the call to get the id fails?
Maybe you could use also the Android API to synchronize if a device is present and then use the id that Android API gives you?
Just some thoughts since I would love to see that App running on my Desire with Snesoid
Edit: Double post
tobren said:
Did you ever try to use the most likely id 0 on an HTC device? Even though the call to get the id fails?
Maybe you could use also the Android API to synchronize if a device is present and then use the id that Android API gives you?
Just some thoughts since I would love to see that App running on my Desire with Snesoid
Click to expand...
Click to collapse
Believe it or not, I actually tried this. Unfortunately, the next command (to bind the bluetooth adapter) also fails, and of course every command after that one because the adapter is not bound.
Thanks for the idea anyway.
usb
does the wii remote have usb connectivity? could it be possible to have the communication pass through that connection rather than bluetooth? one advantage of this would be increased battery life and probably better compatibility across models.
i'm sure some people would prefer bluetooth, but i figure i'll always be using it very close to my phone so i can see the screen, so the wired option is actually a bit more attractive (considering battery performance).
i know ps3 has usb connectivity as well, you just might need an adapter (mini to micro).
rubber soul said:
does the wii remote have usb connectivity? could it be possible to have the communication pass through that connection rather than bluetooth?
[snip]
i know ps3 has usb connectivity as well, you just might need an adapter (mini to micro).
Click to expand...
Click to collapse
I'm pretty sure the first answer is no - our wii is round at a friend's atm. However even if it was yes, you'd need more than an adapter. USB operates with one device as master & the other as slave. To allow you to connect slave devices to your phone it would need to be in host mode. Some mobile phone hardware implementations support this, however I don't know of any mainstream Android kernels which do. Even if you workaround that, you're left with the huge issue that slave devices can assume it's safe to draw power from the USB bus which could do nasty things (tm) to a lower power device like a mobile. This can be worked around via a powered hub, but it all gets very messy.
I looked into this a few months ago, hoping I'd be able to use a usb keyboard with my Hero. I ended up with a BT keyboard instead. Of course that doesn't work either but for completely different reasons, as hinted at by this thread. Hopefully a 2.1 ROM will solve that, but that's the subject of numerous other threads.
Uh, just throwing stuff out, what if you have a pc with two bluetooth adapters, it connects to the wii mote, and then broadcasts that in someway the android api can understand?
Also please actually try working on something with a rooted phone, the HTC EVO 4g is rootable, and I will make man love(no homo) if you get it working.
Either one works lol.
Using a PC as a proxy is kind of useless. If you have a wiimote connected to a PC, you might as well play games on the PC itself (there are nes/snes/sega/etc emulators for PCs too).
At this moment, rooting doesn't help with the problem either.
@1 True
@2 That sucks.
Do we think that this will/could be fixed in HTC's Froyo update for 2010 devices? Not looking for definite answers, just a ponderin'.
well if you send the null pairing code to the wiimote from the default bluetooth pairing screen.. it will fail to communicate with the wiimote too
waffles004 said:
Do we think that this will/could be fixed in HTC's Froyo update for 2010 devices? Not looking for definite answers, just a ponderin'.
Click to expand...
Click to collapse
Doesn't it work in stock/vanilla Eclair? I thought the main problem was with Cupcake, though HTC seem to have done weird things to every stock firmware. I read that removing Sense from a 2.1 HTC ROM breaks bluetooth. Go figure. And there was I thinking Sense was a gui enhancement
I contacted HTC about their bluetooth issues and just received this response
My name is Courtney, and I would be glad to assist you today. I understand that you are unhappy with the Bluetooth connectivity on your HTC EVO. HTC is aware of the problems occurring with the EVO and Bluetooth. We are currently investigating this issue and are working on a solution. As soon as we have an update, we will inform our customers. Thank you for contacting HTC America Technical Support. If you need further assistance, please feel free to contact us via email or at 1-866-449-8358. We are open 7 days a week from 6 a.m.-1 a.m. EST. You can also check out our Community and Support pages at htc.com/us and our pages on Facebook and Twitter.
Click to expand...
Click to collapse
I contacted HTC about this issue with my incredible and I basically got the same answer except the guy was more knowledgeable and said that other people were complaining about certain bluetooth issues. I think they know what they did and are waiting to fix it in Froyo to be easy for them. No worries though, should be comin' in a few weeks. I can't freakin' wait. I have soooooooooo much Pokemon and Mario to play.
does anyone know if this works on samsung galaxy s, i dont have my phone yet to test, but as soon as it arrives (sometime next week) i will test this.
All I can say is that my wii controller is working really well on cyanogen on my evolution now!
http://www.geekbuying.com/item/MK80...ip-RK3066-Cortex-A9-Mini-PC-stick-307415.html
What everyone think? Anybody took the leap and bought it yet? I was thinking about getting one so I don't have to hookup my laptop to my TV anymore
Sent from my SGH-T999 using xda premium
nice gadget!!
richeazy said:
http://www.geekbuying.com/item/MK80...ip-RK3066-Cortex-A9-Mini-PC-stick-307415.html
What everyone think? Anybody took the leap and bought it yet? I was thinking about getting one so I don't have to hookup my laptop to my TV anymore
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I got mine mk808 yesterday. I bought a mk802 in august but it "burned" after 1 week. I also think that the mk802 was very laggish... The mk808 is far much better!!!
So far I am very very very happy with it!
regards
gillidk said:
I got mine mk808 yesterday. I bought a mk802 in august but it "burned" after 1 week. I also think that the mk802 was very laggish... The mk808 is far much better!!!
So far I am very very very happy with it!
regards
Click to expand...
Click to collapse
gillidk, Did you buy yours from geekbuying? How long was the delivery and which country are you
I was about to order the similar GV-20 mk808 based device from gadgetgreats but poeple have mentioned fraud etc
http://www.gadgetgreats.com/gv-20-a...i-a9-dual-core-android-4-0-mini-pc-gv-20.html
many thanks
I got mine today. I ordered it over a week ago. Weird because I didn't get my shipping information until last night, and when I tracked it, it was already out for delivery.
My Measy Air Mouse R11 is screwed though I think. It keeps sliding to the left hand side. I even tried on my PC and it does the same thing. I've tried to resync it and screw with it, but it keeps moving. Very hard to use a mouse that doesn't stay still. The MK808 is fun. I just got it tonight. I haven't had the time to get really crazy with it. Seems to run ok and would be far more enjoyable with a good input device.
Ordered mine today (only $60), if it really works as reviews say, it's quite a bargain
Do you still have problems with the rc11 or are they solved ?
send by an 42y old gio junkie™
player911 said:
I got mine today. I ordered it over a week ago. Weird because I didn't get my shipping information until last night, and when I tracked it, it was already out for delivery.
My Measy Air Mouse R11 is screwed though I think. It keeps sliding to the left hand side. I even tried on my PC and it does the same thing. I've tried to resync it and screw with it, but it keeps moving. Very hard to use a mouse that doesn't stay still. The MK808 is fun. I just got it tonight. I haven't had the time to get really crazy with it. Seems to run ok and would be far more enjoyable with a good input device.
Click to expand...
Click to collapse
Did you get it by express delivery or normal delivery
send by an 42y old gio junkie™
I fixed my Measy Air Mouse R11.
To reset the Gyros, you lay it flat and press and hold LEFT ARROW + G for a few seconds... making sure it is flat. Now it works great.
I'm having some weird issues with some misbehaving apps. Root explorer started freaking out. And now my FPse won't use OpenGL for the life of me. I'm interested in trying the CM10 build for it but the operation requirements are bland. Supposedly it requires CWM recovery, which is supplied but doesn't give specifics how or what order or process to get it done.
I have to say that it is a fun unit to work with and chews through FPse roms. I'm surprised how well it runs for a chinese chipset.
Flashing is a bit of a chore and instructions aren't very clear, so I'll post them here:
With the unit OFF:
Insert a paper clip into the reset hole and press it in and HOLD IT down.
Awkwardly insert the MicroUSB-PC cable into the OTG. This will power the unit and it should boot into Flash mode given you've held the paperclip down properly.
Trying to install eGalax Touch Screen linux driver
I'm trying to install the eGalax Touch Screen driver for Linux 2.6 that came with my liliput 7 inch touch screen. The touch screen is for use in my car. Using the mk802 II or ug808 to replace my audio system. I just need to get the driver installed. The driver installation script is looking for the locations "usr/local" and "usr/bin", but the only "usr" directory I can find is in "system/usr"... I'm not sure if I should use that location and create the local and bin directories there or not. But when I created the usr/local and usr/bin at the same level as system (which is in the "mnt" directory which is also at the same level as "root" directory (btw, I cannot find a "home" directory), the install seemed to work fine using Better Terminal Pro android app with the bash shell. However, when I restarted the device, the "usr" directory that I create was gone, so the driver install was wiped apparently, and the usb HDMI touch screen still does not work... I can post the bash script if that helps. This is the last thing I need to get this to work, then I can have a full Android ICS system in my car. Thanks in advance.
FYI The HDMI works great to view and use a usb mouse or the RII keyboard. they work great. It's just the touch screen input does not work. It used to when I first turned on the device with the touch screen on, but the x-y coordinates were reversed, hence attempting to install the driver. I have ICS compiled from source and may attempt to add the drivers into it and create an img to them load on the mk802 II, but I fear that I'll loose any proprietary hardware drivers that came with the mk802 II.
I also wanted to make a img backup using ROM Manager, but ClockworkMod is not available for the MK802 II. ANy leads on this would help. Been researching and testing this for a month now.
rscreen said:
gillidk, Did you buy yours from geekbuying? How long was the delivery and which country are you
I was about to order the similar GV-20 mk808 based device from gadgetgreats but poeple have mentioned fraud etc
http://www.gadgetgreats.com/gv-20-a...i-a9-dual-core-android-4-0-mini-pc-gv-20.html
many thanks
Click to expand...
Click to collapse
Ordered on the 26th for 65$ (actually cost £42 through paypal),
they shipped on the 29th (tracking never worked).
And it arrived on the 6th. So quicker than expected.
I've applied the firmware update which was a slightly newer build of 4.1. Mentioned in both these places (applied the tweaked one from deadhp1 for the play store location fix in case needed)
http://blog.geekbuying.com/index.php/2012/11/03/mk808-mini-pc-firmware-update-on-3th-nov/
http://www.armtvtech.com/armtvtechforum/viewtopic.php?f=13&t=53
It now seems to play any avi / mkv / mp4 i've given it (usually on a usb stick or micro SD). It happily plays avi's over the network (using ES file explorer).
Its definitely better than the out of sync UG802 which wasn't quite right and the power lead came out too easily.
I use the custom stock video app (seems to come with most of the RockChip devices) and MX player (it looks a lot nicer)
I was looking for a device like this one and the reviews are really helpful
Anyone know of GPS that works with these?
jcps said:
I was looking for a device like this one and the reviews are really helpful
Click to expand...
Click to collapse
Anyone know of GPS (USB or embedded) that works with these? Thanks for your help.
So confused... it's a USB drive that turns a TV into an Android PC? Does the TV require any special functionality to allow for that?
Avuja said:
So confused... it's a USB drive that turns a TV into an Android PC? Does the TV require any special functionality to allow for that?
Click to expand...
Click to collapse
It is a mini PC that has HDMI output. Your TV must have a vacant HDMI input so you can plug the mini PC into it. My TV supports 1080p. And so I can set the output resolution on the mini PC to 1080p. But it also could be set to 720p as well. These don't come with any display so you have to plug it in to your TV or a monitor that supports HDMI. The audio is pushed through the HDMI as well. To control it you can use a USB mouse and/or USB keyboard. Your cheap wireless mouse will work but the USB ports do not have power to them so I've had to use a powered USB hub to make my wireless keyboard work further than a foot away from the USB dongle for the keyboard. The hub also allows you to plug in other devices like a USB camera. But the ones that work are somewhat limited , be aware. Does that help you understand it?
Maxx57 said:
I'm trying to install the eGalax Touch Screen driver for Linux 2.6 that came with my liliput 7 inch touch screen. The touch screen is for use in my car. Using the mk802 II or ug808 to replace my audio system. I just need to get the driver installed. The driver installation script is looking for the locations "usr/local" and "usr/bin", but the only "usr" directory I can find is in "system/usr"... I'm not sure if I should use that location and create the local and bin directories there or not. But when I created the usr/local and usr/bin at the same level as system (which is in the "mnt" directory which is also at the same level as "root" directory (btw, I cannot find a "home" directory), the install seemed to work fine using Better Terminal Pro android app with the bash shell. However, when I restarted the device, the "usr" directory that I create was gone, so the driver install was wiped apparently, and the usb HDMI touch screen still does not work... I can post the bash script if that helps. This is the last thing I need to get this to work, then I can have a full Android ICS system in my car. Thanks in advance.
FYI The HDMI works great to view and use a usb mouse or the RII keyboard. they work great. It's just the touch screen input does not work. It used to when I first turned on the device with the touch screen on, but the x-y coordinates were reversed, hence attempting to install the driver. I have ICS compiled from source and may attempt to add the drivers into it and create an img to them load on the mk802 II, but I fear that I'll loose any proprietary hardware drivers that came with the mk802 II.
I also wanted to make a img backup using ROM Manager, but ClockworkMod is not available for the MK802 II. ANy leads on this would help. Been researching and testing this for a month now.
Click to expand...
Click to collapse
probably you will need the kernel sources. also, you need root access. that error (directories that get lost after reboot) might be due to yo need to remount the /system partition in rw mode (by default is ro) and perhaps you will neet to do some symlinks on /bin to /system/xbin.
other thing you..must get in considwration is that android is different from linux.. and that you might need to compile the kernel module, such thiing im not sure that is posible from within the device itself...
or.. i just might be way off track, in which case jyst dismiss my answer
Enviado desde mi MB860 usando Tapatalk 2
Maxx57 said:
Anyone know of GPS (USB or embedded) that works with these? Thanks for your help.
Click to expand...
Click to collapse
I'm very interested to know as well, I have an MK808 and would love to add a GPS dongle.
Anyone know if a headset can be paired over bt for voip calls and or voice commands and search /google now?
Sent from my GT-N8013 using XDA Premium HD app
killerskincanoe said:
Anyone know if a headset can be paired over bt for voip calls and or voice commands and search /google now?
Sent from my GT-N8013 using XDA Premium HD app
Click to expand...
Click to collapse
just so you know it doesn't have built in bluetooth.
if you need bluetooth google for imito mx1. this one seems to be the best mk808 model so far. i got mine last month but haven't tried bluetooth yet. antutu gives a score around 6500. it's a nice toy to play with on bigscreen tvs.
I read up on this one. Good vid review at http://youtu.be/X8pozwuAq7w
Anyone know the spec diff between this and the MX2?
and is geekbuying the best seller for this device or ???
c
h-guy said:
if you need bluetooth google for imito mx1. this one seems to be the best mk808 model so far. i got mine last month but haven't tried bluetooth yet. antutu gives a score around 6500. it's a nice toy to play with on bigscreen tvs.
Click to expand...
Click to collapse
---------- Post added at 11:31 AM ---------- Previous post was at 11:24 AM ----------
can anyone comment on this non-support of XBMC for Rockchip? and if not Rockchip, which stick-PC gets it right?
one comment also that I would like more info on is that both iMITO units underperform compared to MK808
"Lack of XBMC support for HD hardware acceleration is a major issue that Rockchip needs to address if they want to keep selling SoC chips to the Stick PC mfgrs. Stick PC makers need 2 take action on this as well and if Rockchip won't play ball, they need to consider alternative SoC. We need more processing power anyway to get close to current smart-phone level and play the latest 3D games."
I just received my new Tronsmart T428 from Geekbuying on Monday
The biggest problem I'm having though is getting any bluetooth keyboard or mouse to actually work on it. I can pair them all up - but they don't work.
I can pair them to my Nexus 7 and they work just fine (both the T428 and the N7 are running 4.2.2)
Kind of defeats the purpose of having it attached to the TV if I can't actually control anything without sitting within USB tethered range.
That being said - it works great with the Synology apps (DS Video/DS Audio) to get my media to the TV.....haven't tried xbmc yet but that's next up after I get this BT thing figured out....
Argent36 said:
I just received my new Tronsmart T428 from Geekbuying on Monday
The biggest problem I'm having though is getting any bluetooth keyboard or mouse to actually work on it. I can pair them all up - but they don't work.
I can pair them to my Nexus 7 and they work just fine (both the T428 and the N7 are running 4.2.2)
Kind of defeats the purpose of having it attached to the TV if I can't actually control anything without sitting within USB tethered range.
That being said - it works great with the Synology apps (DS Video/DS Audio) to get my media to the TV.....haven't tried xbmc yet but that's next up after I get this BT thing figured out....
Click to expand...
Click to collapse
I'm having the same issue with the Tronsmart T428. I can pair them to my Asus TF700 and they work fine. Any remidies to fix the issue?
I haven't found a solution yet - I was trying to roll back the firmware to 4.1.1 to see if that would fix it - but having problems finding the appropriate drivers to get it to work.
so basically - this is a really cool Android computer - that I have to sit next to my TV to use (wired mouse)
It's an awesome computer I agree. I'm downloading the 4.1.1 firmware as I speak. Have to see if I can get it to flash...
Good luck with that let me know if you manage to figure it out!
UPDATE: I managed to get it backdated to 4.1.1 - video playback is choppy (dropped frames?) but my BT keyboard/mouse works now..
I did get an email back from geekbuying finally...
hi frend
thanks for telling us the troubles u met
pls reset it to the factory first.
if it is the same , pls wait for days.
next week there will be a firmare of ROCKCHIP. to solve that troubles
after we get it ,we will upload to our blog
thanks for ur waiting in advance
anna
Click to expand...
Click to collapse
so maybe this new firmware will fix it
I managed to get 4.1.1 installed as well. I didn't notice the choppy video using BS Player but it did fix my bluetooth problem although the bluetooth connection doesn't seem to be very strong. I can be 10 feet away from it and it won't hardly work. Wonder if my wifi is interfering wth it since the router is on the other side of the wall. Glad to hear rockchip is supposed to release an update.
On my note 10.1 after my keyboard is paired I have to go into the connection and check a box to enable it
Sent from my SPH-L900 using xda app-developers app
neudof said:
On my note 10.1 after my keyboard is paired I have to go into the connection and check a box to enable it
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
There was a box to enable they keyboard but it was already checked...so it should've worked but it didn't. 4.1.1 solved the problem...must be a hardware/software issue somewhere.
Since on Android 4.1 it can work, so it must be a system problem, hope they can release a new firmware soon to fix it.
except that, a really little cool device!
GeekEric said:
Since on Android 4.1 it can work, so it must be a system problem, hope they can release a new firmware soon to fix it.
except that, a really little cool device!
Click to expand...
Click to collapse
I read somewhere that google replace in android 4.2.2 the bluez stack by a broadcom stack. It mean that some devices are not compatible anymore. Aparently broadcom will be better, but in the mean time some of us will have to use 4.2.1 and below to make our devices working. Broadcom will support bluetooth 4.0 and will be less power draining. I ckecked om google code and there lot of devices reporting not working anymore, we will have to wait until further upgrade.
Firmware May 30 fix
The new firmware relase May 30 fix the bluetooth issue :laugh:
Bluetooth 2.1 SSP works with MK908 V3 if you recheck the option
neudof said:
On my note 10.1 after my keyboard is paired I have to go into the connection and check a box to enable it
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
I'm using my kernel (based on marvin) without any changes regarding bluetooth and Finless 1.6 system img.
Bluetooth 2.1 devices with SSP pairing work if after pairing you select de device and do check&uncheck&check the input device checkbox.
haha I like calling it blu toot!
anyone had success using six axis ps3 controller app with nook hd+?
I was looking forward to finally having jelly bean on this tablet since
ICS has a tendency to change blue tooth addresses every time it's rebooted.
I ran the free compatibility checker from the play store, it said the nook would work.
So I used the pc pairing tool to change my ps3 controller to the address of the nook.
It won't connect.
I even got a usb gender changer to connect it directly to the nook and pair it, it won't do it.
Anyone have success pairing ps3 controller with nook hd+?
pdx1138 said:
I even got a usb gender changer to connect it directly to the nook and pair it, it won't do it.
Anyone have success pairing ps3 controller with nook hd+?
Click to expand...
Click to collapse
USB connection with the controller most definitely works, I tried it myself (you can also see it working in my original usbhost video).
I did not look into BT support as it sounds to be somewhat more involved than just pairing (usb connection very easy on the other hand, just plug the controller in and it jsut works (don't forget to turn it on by pressing the "start" button (triangle shaped)).
Where's the video?
pdx1138 said:
Where's the video?
Click to expand...
Click to collapse
Referenced from the original usbhost support announcement
aha! but you used a usb hub in the middle! didn't know I needed that.
The thing is though, the ps3 controller SHOULD definitely be able to connect
over blue-tooth, but it isn't with CM 10.1 for some reason...
I can't be the only one that would rather connect it wirelessly.
It works on nearly every tablet ever made as long as root is enabled.
if you don't mind, maybe you could download the free six axis compatibility checker
so you can see what I mean.
pdx1138 said:
aha! but you used a usb hub in the middle! didn't know I needed that.
Click to expand...
Click to collapse
You would know if you'd check your dmesg to see that the ps3 controller claims it needs too much power to operate (Which it does not).
Also it's addressed in all other usb threads that devices that claim they need more than 100mA need to be hidden behind USB hub (unpowered is usually fine too).
The thing is though, the ps3 controller SHOULD definitely be able to connect
over blue-tooth, but it isn't with CM 10.1 for some reason...
Click to expand...
Click to collapse
With BT overhaul in Android 4.2 a lot of things broke on fundamental level, I know wiimotes are totally broken, it well might be that ps3 controllers are in the same boat and you'll need to wait until Google gets around to actually release unbroken implementation in 4.3
if you don't mind, maybe you could download the free six axis compatibility checker
so you can see what I mean.
Click to expand...
Click to collapse
I guess I might try it one day. But my cursory reading indicates thre's some nonfree tool needed at one point in the process.
The six axis compat checker seems to only check that you have rooted device, and that's all it does.
That makes sense...didn't know it was broken implementation.
thanks very much for your words.
I can verify Sixaxis does work with CM 10.1 because I am running CM on my At&t Galaxy S2. I do not understand why with Verygreen's CM version it does not work. I mean since he is building from CM source.
very interesting...I wonder if it has to do with tablet aspects of cm 10.1
thanks for posting that Ederok.
I did get the controller working, by hooking it up to a non powered hub via usb cable, but would be so much better to use wireless blue tooth.
pdx1138 said:
very interesting...I wonder if it has to do with tablet aspects of cm 10.1
thanks for posting that Ederok.
I did get the controller working, by hooking it up to a non powered hub via usb cable, but would be so much better to use wireless blue tooth.
Click to expand...
Click to collapse
Your welcome. I really hope the issue gets resolved in future releases. [crosses fingers]
ederok said:
Your welcome. I really hope the issue gets resolved in future releases. [crosses fingers]
Click to expand...
Click to collapse
If it's not fixed soon I might be getting the new N7 when it releases and give my nook to someone else. A big reason that I bought this thing in the first place was so I could have a bigger screen for playing games wirelessly and knew that it was supported by CM but apparently not without its quirks
Hi there! I bought a Tegra Note7 which is equipped with Tegra4 Chipsets.Now I want to play games with DualShock3 via SIXAXIS CONTROLLER. The thing is that the app worked very well on my Moto Droid Bionic,but it did not work on my Tegra Note7. When I clicked "start" with every necessary steps done and the screen displayed address of bluetooth and listening for controllers,the "bluetooth" icon did not appear on the top status bar. So the DS3 controller was continuous flashing its 4 red lights,then no other things took place.
I have restored original android 4.3 rom,no changes. Could*you*please*tell me how to work it out? Thank you!
Before I rooted tablet I was able to plug ps3 controller in and was able to map buttons m8 I also used sixaxis enabler and everything fine until rooted then lost all ps3 controller mappings there's very little info on this subject I asked before ,something to do with Bluetooth drivers !
Sent from my TegraNote-P1640 using XDA Premium 4 mobile app
How about open your eyes, read old threads, use the search function. this issue has been discussed a hundred times now..
e: for the lazy ones..
http://forum.xda-developers.com/showthread.php?t=2633221
http://forum.xda-developers.com/showthread.php?t=2541873&page=3
cars10k said:
How about open your eyes, read old threads, use the search function. this issue has been discussed a hundred times now..
e: for the lazy ones..
http://forum.xda-developers.com/showthread.php?t=2633221
http://forum.xda-developers.com/showthread.php?t=2541873&page=3
Click to expand...
Click to collapse
Yeah,you are right.It does has been discussed for 100 times.,but no one exactly figure it out.
generalradec said:
Yeah,you are right.It does has been discussed for 100 times.,but no one exactly figure it out.
Click to expand...
Click to collapse
There's really nothing to figure out. The bluetooth stack on the stock ROM just doesn't work with PS3 controllers. Until someone can make a custom ROM with some sort of changes to bluetooth (or until Nvidia releases a ROM with decent bluetooth support), it's just not going to work, and there's nothing we can do to change that.
rchrdcrg said:
There's really nothing to figure out. The bluetooth stack on the stock ROM just doesn't work with PS3 controllers. Until someone can make a custom ROM with some sort of changes to bluetooth (or until Nvidia releases a ROM with decent bluetooth support), it's just not going to work, and there's nothing we can do to change that.
Click to expand...
Click to collapse
Thank you for your definite answer! Anyway I now understand what is going on with Tegra Note7, and I have substituted DS3 for wamo pro2 .I hope it can function on my device via bluetooth.
generalradec said:
Thank you for your definite answer! Anyway I now understand what is going on with Tegra Note7, and I have substituted DS3 for wamo pro2 .I hope it can function on my device via bluetooth.
Click to expand...
Click to collapse
The 4.4 Update is supposed to address controller usage.
e8hffff said:
The 4.4 Update is supposed to address controller usage.
Click to expand...
Click to collapse
Yeah,wamoPro can work on TN7 via BT now.But there is a pity for Sixaxis controller still not functioning in TN7.
I've had some success using the USB/BT Joystick Center app with an otg cable and a Bluetooth dongle.
Sent from my TegraNote-P1640 using Tapatalk
PS3 SixAxis controller - USB/BT Joystick Center
yes USB/BT Joystick Center GOLD worked wired with PS3 sony.
H T T P jaredmorgs.github.io/#FAQ_PS3_Sixaxis
Wireless PS need dongle CSR bluetooth
Ragnorok64 said:
I've had some success using the USB/BT Joystick Center app with an otg cable and a Bluetooth dongle.
Sent from my TegraNote-P1640 using Tapatalk
Click to expand...
Click to collapse
Please send Link of bluetooth dongle and USB-BT apk version
anilmaurya said:
Please send Link of bluetooth dongle and USB-BT apk version
Click to expand...
Click to collapse
Not 100% sure what you're asking for but hopefully this is it.
http://www.ebay.com/itm/321254758547?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1497.l2649
https://play.google.com/store/apps/details?id=com.poke64738.usbjoygolddemo
https://play.google.com/store/apps/details?id=com.poke64738.usbjoygold
I can't get it to work as consistently on my tablet as Better DS3 works on my PC though.
rchrdcrg said:
There's really nothing to figure out. The bluetooth stack on the stock ROM just doesn't work with PS3 controllers. Until someone can make a custom ROM with some sort of changes to bluetooth (or until Nvidia releases a ROM with decent bluetooth support), it's just not going to work, and there's nothing we can do to change that.
Click to expand...
Click to collapse
Any Idea if this is actually possible? sitting with a rooted TN7 which I spent a while figuring out how to root (not particularly learned in android atm) and pretty pissed off that my dreams of having a nice practical ghetto shield without cables have been crushed.
admiralaverage said:
Any Idea if this is actually possible? sitting with a rooted TN7 which I spent a while figuring out how to root (not particularly learned in android atm) and pretty pissed off that my dreams of having a nice practical ghetto shield without cables have been crushed.
Click to expand...
Click to collapse
It's technically possible, but there has been almost no developer interest in this device. There are no custom ROMs available, and there's only one alternative kernel available, though I never did try a Sixaxis with that kernel... I do know that it broke support for my Moga, so that's not exactly promising. I'll have to give the Sixaxis a try here in a bit.
rchrdcrg said:
It's technically possible, but there has been almost no developer interest in this device. There are no custom ROMs available, and there's only one alternative kernel available, though I never did try a Sixaxis with that kernel... I do know that it broke support for my Moga, so that's not exactly promising. I'll have to give the Sixaxis a try here in a bit.
Click to expand...
Click to collapse
Assuming you mean shaky156 kernel I can confirm that it doesn't help the bluetooth issue
Just tried the latest version of Sixaxis with the latest OTA. And it seems to finally work on the built in blutooth stack without a usb dongle!