MultiROM Once Again Available for the Galaxy S4

Multiboot, or the ability to select betweenmultiple operating systems on a single device at … more

Build an Impractical But Awesome Lego Mindstorm Dock

The vast majority of what we cover here on the XDA-Developers News Portal relates to … more

MultiROM Makes its Way Over to the HTC One (M8)

While browsing our forum, you will undoubtedly find more than a few enticing ROMs available … more

Welcome to the New XDA-Developers Portal!

You may recall that a few weeks ago, we opened up the XDA-2015 forum themesto intrepid users … more
Post Reply

Connecting a HID Mouse to the Nexus Q

3rd July 2012, 08:38 AM   |  #1  
OP Junior Member
Thanks Meter: 1
 
2 posts
Join Date:Joined: Feb 2010
Hi folks...

My contribution by to the community...

Over the weekend, I figured out how to get a HID Mouse to connect to the Nexus Q.





I wrote about it here..


goto : droidcloudshare.blogspot.com

*DISCLAIMER: PROCEED AT YOUR OWN RISK.

This is really pre-beta...

I am not responsible for any damage that your device that may result from doing this. Specifically, DON'T COME COMPLAINING TO ME IF YOU BRICK YOUR NEXUS Q. At this moment, the ability to unbrick a Nexus Q maybe very limited....

SO ONCE AGAIN, PROCEED AT YOUR OWN RISK.



Let me know if you have trouble and I'll try to fix.
Next thing will be to get HID Keyboard and Headset working too.
Last edited by fredc888; 3rd July 2012 at 08:50 AM. Reason: added picture
The Following User Says Thank You to fredc888 For This Useful Post: [ View ]
5th July 2012, 02:56 AM   |  #2  
gdi2290's Avatar
Senior Member
Thanks Meter: 104
 
208 posts
Join Date:Joined: Nov 2009
More
could you github NexusQTools Source Code
5th July 2012, 03:43 PM   |  #3  
Junior Member
Thanks Meter: 0
 
3 posts
Join Date:Joined: Oct 2010
You can also use a usb OTG cable and hook up a usb keyboard / mouse. The cable I use for my XOOM worked just fine.
8th July 2012, 01:19 AM   |  #4  
Junior Member
Thanks Meter: 6
 
24 posts
Join Date:Joined: Dec 2010
I couldn't make the Q boot into clockworkmod recovery, it boots to the normal UI with this img, so I used another one, if you are having problem with this step, just reply here and I will give you the link, I'm not sure if I can put links from another forum...
Last edited by auad; 8th July 2012 at 02:10 AM. Reason: duplicated information
The Following User Says Thank You to auad For This Useful Post: [ View ]
9th July 2012, 01:42 AM   |  #5  
Junior Member
Brooklyn
Thanks Meter: 1
 
6 posts
Join Date:Joined: Mar 2010
auad, I'd love that link, and if you could also perhaps toss some backups of your Q my way, that'd help me bring it out of a bricked state... thanks!
11th July 2012, 10:08 PM   |  #6  
Junior Member
Thanks Meter: 0
 
1 posts
Join Date:Joined: Jul 2012
Followed all the steps, but the Nexus Q Tools baffles me. Attaching a screenshot and some logs.

07-11 17:01:55.968: D/OpenGLRenderer(483): Flushing caches (mode 1)
07-11 17:01:55.984: D/OpenGLRenderer(483): Flushing caches (mode 0)
07-11 17:01:56.007: D/HidConnectActivity(2065): Remote BDADDR = 58:1F:AA:EA:FBC
07-11 17:01:56.015: D/HidConnectActivity(2065): Turning on Bluetooth...
07-11 17:01:56.015: D/BluetoothAdapterStateMachine(163): PowerOff process message: 1
07-11 17:01:56.015: D/BluetoothAdapterStateMachine(163): Bluetooth state 10 -> 11
07-11 17:01:56.015: I/bluedroid(163): Starting hciattach daemon
07-11 17:01:56.023: I/bluedroid(163): bt_enable: ret: -1, errno: 19
07-11 17:01:56.039: D/HidConnectActivity(2065): BT state change: STATE_TURNING_ON
07-11 17:01:56.117: I/bluedroid(163): bt_enable: ret: -1, errno: 19
07-11 17:01:56.171: I/ActivityManager(163): Displayed com.droidcloudshare.bt/.HidConnectActivity: +249ms
07-11 17:01:56.218: I/bluedroid(163): bt_enable: ret: -1, errno: 19
07-11 17:01:56.320: I/bluedroid(163): bt_enable: ret: -1, errno: 19
07-11 17:01:56.421: E/brcm_patchram_plus(2078): Done setting line discpline
07-11 17:01:56.507: I/bluedroid(163): bt_enable: ret: -1, errno: 114
07-11 17:01:56.507: W/bluedroid(163): Bluetoothd already started, unexpectedly!
07-11 17:01:56.507: I/bluedroid(163): Starting bluetoothd deamon
07-11 17:01:56.515: E/BluetoothEventLoop.cpp(163): get_adapter_path: D-Bus error: org.freedesktop.DBus.Error.ServiceUnknown (The name org.bluez was not provided by any .service files)
07-11 17:01:56.531: E/BluetoothEventLoop.cpp(163): get_adapter_path: D-Bus error: org.freedesktop.DBus.Error.ServiceUnknown (The name org.bluez was not provided by any .service files)
07-11 17:01:56.546: E/BluetoothEventLoop.cpp(163): get_adapter_path: D-Bus error: org.freedesktop.DBus.Error.ServiceUnknown (The name org.bluez was not provided by any .service files)
07-11 17:01:56.578: I/BluetoothEventLoop.cpp(163): agent_event_filter: Received method org.bluez.Agent:Release
07-11 17:01:56.687: D/BluetoothAdapterStateMachine(163): WarmUp process message: 101
07-11 17:01:56.710: D/OpenGLRenderer(483): Flushing caches (mode 1)
07-11 17:02:06.687: D/BluetoothAdapterStateMachine(163): WarmUp process message: 104
07-11 17:02:06.687: E/BluetoothAdapterStateMachine(163): Bluetooth adapter SDP failed to load
07-11 17:02:06.695: E/BluetoothService.cpp(163): setBluetoothTetheringNative false
07-11 17:02:06.734: I/bluedroid(163): Stopping bluetoothd deamon
07-11 17:02:07.234: I/bluedroid(163): Stopping hciattach deamon
07-11 17:02:07.234: D/BluetoothAdapterStateMachine(163): Bluetooth state 11 -> 10
07-11 17:02:07.234: D/BluetoothAdapterStateMachine(163): PowerOff process message: 101
07-11 17:02:07.242: D/HidConnectActivity(2065): BT state change: STATE_OFF
07-11 17:02:07.273: D/DockEventReceiver(427): finishStartingService: stopping service
07-11 17:02:11.289: D/OpenGLRenderer(483): Flushing caches (mode 1)
07-11 17:02:11.390: D/dalvikvm(637): GC_CONCURRENT freed 464K, 5% free 12609K/13191K, paused 4ms+4ms
07-11 17:04:14.281: D/dalvikvm(163): GC_CONCURRENT freed 513K, 6% free 15453K/16327K, paused 5ms+4ms
07-11 17:05:35.359: D/OpenGLRenderer(483): Flushing caches (mode 2)
07-11 17:05:35.367: I/EventLogService(444): Aggregate from 1342038935272 (log), 1342038935272 (data)
07-11 17:05:35.421: I/ServiceDumpSys(444): dumping service [account]
07-11 17:05:35.453: D/dalvikvm(444): GC_CONCURRENT freed 331K, 4% free 12860K/13319K, paused 5ms+3ms
07-11 17:07:00.187: D/PermissionCache(99): checking android.permission.READ_FRAME_BUFFER for uid=2000 => granted (244 us)
07-11 17:07:02.804: D/dalvikvm(163): GC_CONCURRENT freed 578K, 5% free 15513K/16327K, paused 5ms+5ms
Attached Thumbnails
Click image for larger version

Name:	nexusq-screen.jpg
Views:	251
Size:	16.0 KB
ID:	1192031  
31st July 2012, 03:53 PM   |  #7  
Junior Member
Thanks Meter: 0
 
16 posts
Join Date:Joined: May 2012
Quote:
Originally Posted by fredc888

Hi folks...

My contribution by to the community...

Over the weekend, I figured out how to get a HID Mouse to connect to the Nexus Q.





I wrote about it here..


goto : droidcloudshare.blogspot.com

*DISCLAIMER: PROCEED AT YOUR OWN RISK.

This is really pre-beta...

I am not responsible for any damage that your device that may result from doing this. Specifically, DON'T COME COMPLAINING TO ME IF YOU BRICK YOUR NEXUS Q. At this moment, the ability to unbrick a Nexus Q maybe very limited....

SO ONCE AGAIN, PROCEED AT YOUR OWN RISK.



Let me know if you have trouble and I'll try to fix.
Next thing will be to get HID Keyboard and Headset working too.

This works well, a small revision in the directions that may help a few people are:

Step #5 item 7 should read:

Update the main.conf ownership and permissions

adb shell chown bluetooth /system/etc/bluetooth/main.conf

adb shell chmod 440 /system/etc/bluetooth/main.conf


I also had a question regarding connecting a second input device such as a wireless keyboard, would I just repeat the Stpe #6 item 4 with the Bluetooth address for the device I wish to input? Also would you happen to know why an on screen keyboard doesn't appear? I can't type anything nor can I open any application that has keyboard input such as Google Play & Gmail (to sign in)
3rd August 2012, 02:42 AM   |  #8  
Junior Member
Thanks Meter: 0
 
21 posts
Join Date:Joined: Apr 2010
Quote:
Originally Posted by mrjaymillz

This works well, a small revision in the directions that may help a few people are:

Step #5 item 7 should read:

Update the main.conf ownership and permissions

adb shell chown bluetooth /system/etc/bluetooth/main.conf

adb shell chmod 440 /system/etc/bluetooth/main.conf


I also had a question regarding connecting a second input device such as a wireless keyboard, would I just repeat the Stpe #6 item 4 with the Bluetooth address for the device I wish to input? Also would you happen to know why an on screen keyboard doesn't appear? I can't type anything nor can I open any application that has keyboard input such as Google Play & Gmail (to sign in)

To put it back exactly like it was, you'd issue

chown bluetooth.bluetooth main.conf

note the period, as help for chown on android shows USER[.GROUP] for setting the permissions.

Either way, this worked great for pairing a magic trackpad. Interestingly if i multitouch all 10 fingers on the pad, there's representations for each finger that show up on the display output on the Q
20th August 2012, 09:55 PM   |  #9  
Member
Thanks Meter: 1
 
34 posts
Join Date:Joined: Jan 2012
Scrambling my brain!
Hey all, just giving a bump to see if anyone is still watching. I'm sort of novice, but trying hard to wrap my head around this. My Q is rooted properly I believe. Been able to sideload and get the launcher to work, so I'm now onto the bluetooth mouse.

1. I noticed when I ADB SHELL MOUNT, where it should say "rootfs on / type rootfs (rw)" it says "rootfs / rootfs ro,realtime 0 0". If that is not read/wright will it cause me issues down the road?

2. When I fastboot the recovery image I downloaded, it doesn't go into CWM recovery, just boots normally. EDIT: Solved this by using the steelhead boot img.

3. What string would I use to list the main.conf so that I could confirm that my chmod worked?

4. When I get to the step "adb shell am start -a android.intent.action.MAIN -n com.droidcloudshare.bt/.HidConnectActivity --es 00:07:61:EB:1D:DD", I am returned with a list of am usage commands followed by "Error: Argument expected after "00:07:61:EB:1D:DD"". EDIT: So I didn't realize that {HID Mouse Bluetooth Address} was part of the string. So this time I entered adb shell am start -a android.intent.action.MAIN -n com.droidcloudshare.bt/.HidConnectActivity --es 00:07:61:EB:1D:DD {HID Mouse Bluetooth Address} and was returned with this:

Starting: Intent { act=android.intent.action.MAIN pkg=Mouse cmp.droidcloudshare.bt/.HidConnectActivity (has extras) }
Error type 3
Error: Activity Class {com.droidcloudshare.bt/com.droidcloudshare.bt.HidConnectActivity} does not exist.


5. I've been retracing my steps, and when I perform adb install -r NexusQTools.apk I get the amount of data transferred and how fast, but then adb just hangs, no "Success". Originally I just closed the command window and restarted and moved on assuming it installed. If Success isn't confirmed is it safe to say it didn't properly install? Is this apk essential to get the mouse to pair on the Q?

So for now I'm kinda stuck, if anyone has a bit of advice I'll gladly take it and push on.

Cheers
Last edited by HomeR365; 20th August 2012 at 11:52 PM. Reason: Solved problem #2 and missed a step in #4. Added #5.
2nd November 2012, 03:25 AM   |  #10  
THE_KINGDOM's Avatar
Senior Member
Thanks Meter: 103
 
877 posts
Join Date:Joined: Sep 2011
More
can this be used to connect a keyboard and mouse at the same time?

I think they only reason it won't work for a keyboard right now is because there needs to be a driver present for the keyboard

Post Reply Subscribe to Thread

Tags
bluetooth, hid, keyboard, mouse, nexus q
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes