Anyone know why "logcat" works when run via ADB but not when run from a local console (EG via connectbot)? I assumed they would use the same UID but in hindsight I'd guess that any android app that starts a shell would be running with the parent app's UID and ADB would provided a different UID again .
I'm trying to investigate what the N1 currently does with a powered (hacked together) USB OTG cable (say connected to a flash drive) I know the kernel doesn't currently support the host mode switch (or at lease it didn't when I was messing with my G1, don't know about 2.1 ) but I wanted to see if anything at all happened.
Anyone done any OTG experimentation of the N1?
I haven't done debugging yet, but I'm interested in your efforts. I'm looking to USB OTG support in an Android phone for MIDI sequencing purposes (record MIDI data on the phone from a USB powered MIDI device). Many people are saying that WiFi/Blutooth solutions are the way to go, but that requires the devices to be powered separately. USB OTG would solve the power problem and in the case of MIDI, solve the latency problem (not to mention that most devices are USB and don't have wifi/bluetooth support...so that would mean making an in-between widget to convert USB to wireless on the device side while powering it).
what can be done via USB on the nook?
can it do host mode? (to connect to USB accessories, I would assume the need for a powered hub as I do not epect the nook to be able to power the USB bus)
with the standard firmware it acts like a drive when connected to a PC, with the cyanogen firmware, what other devices can it be made to look like? I haven't been able to access it as a drive since flashing it.
can the USB be made to look like a network?
dlang said:
what can be done via USB on the nook?
can it do host mode? (to connect to USB accessories, I would assume the need for a powered hub as I do not epect the nook to be able to power the USB bus)
with the standard firmware it acts like a drive when connected to a PC, with the cyanogen firmware, what other devices can it be made to look like? I haven't been able to access it as a drive since flashing it.
can the USB be made to look like a network?
Click to expand...
Click to collapse
Look in the Dev section. They're working (and getting very close?) to being able to do this (hello external hard drive!).
which feature are they close to getting working?
The one where we can have hosting enabled
So...everything-ish
glad to hear this. any pointers on what threads to look at? (unfortunantly I'm not allowed to post questions there yet)
dlang said:
glad to hear this. any pointers on what threads to look at? (unfortunantly I'm not allowed to post questions there yet)
Click to expand...
Click to collapse
Under deveopment, but working for some devices. Take a look here:
http://forum.xda-developers.com/showthread.php?t=1105497&highlight=USB
Does mojo have a micro usb port for debugging mode/adb? Also what about official usb drivers for connecting to a windows PC?
Sent from my SM-N900V using XDA Premium 4 mobile app
It doesn't have a micro otg USB port. It has 2 full sized USB ports. a single USB 2.0 and single USB 3.0 port. I'm going to buy a full sized male to male USB cable and try to see if it will work with debugging/adb with that.
dheku-00 said:
It doesn't have a micro otg USB port. It has 2 full sized USB ports. a single USB 2.0 and single USB 3.0 port. I'm going to buy a full sized male to male USB cable and try to see if it will work with debugging/adb with that.
Click to expand...
Click to collapse
You don't need to use USB - connect to M.O.J.O. over the network instead.
(1) <PC> Download Android sdk from Android website
(2) <Mojo> connect ethernet or connect wifi to get a ip address xxx.xxx.xxx.xxx
(3)<Mojo> Settings -> About M.O.J.O. --> Build number ==> click 8 times, Developer options will appear in Settings
(4) <Mojo> Settings -> Enable USB debugging
(5) <PC> Execute in command line==> adb.exe connect xxx.xxx.xxx.xxx
(6) <PC> type adb shell logcat to get debug message
Okay, thank you! That works a lot better for my setup then stringing a usb cable across the room anyways.
alexp1289 said:
Does mojo have a micro usb port for debugging mode/adb? Also what about official usb drivers for connecting to a windows PC?
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It has a micro USB. Right under the hdmi input! So small you missed it!
It accepts up to 128gb cards, must be FAT 32 format.
I believe that is MicroSD above the HDMI.
ExtremeRyno said:
I believe that is MicroSD above the HDMI.
Click to expand...
Click to collapse
You are correct.
Mad Catz Rich said:
You don't need to use USB - connect to M.O.J.O. over the network instead.
(1) <PC> Download Android sdk from Android website
(2) <Mojo> connect ethernet or connect wifi to get a ip address xxx.xxx.xxx.xxx
(3)<Mojo> Settings -> About M.O.J.O. --> Build number ==> click 8 times, Developer options will appear in Settings
(4) <Mojo> Settings -> Enable USB debugging
(5) <PC> Execute in command line==> adb.exe connect xxx.xxx.xxx.xxx
(6) <PC> type adb shell logcat to get debug message
Click to expand...
Click to collapse
That's awesome! I was wondering were the dev options were.
Thanks for the info!
gwaldo said:
That's awesome! I was wondering were the dev options were.
Thanks for the info!
Click to expand...
Click to collapse
As a game dev, maybe you have an answer for me, LimeLight + Mojo ? Limelight is an apk being developed by the xda community in the shield forum, it allows pc games to be streamed to android (aside from shield)
jjprichards said:
As a game dev, maybe you have an answer for me, LimeLight + Mojo ? Limelight is an apk being developed by the xda community in the shield forum, it allows pc games to be streamed to android (aside from shield)
Click to expand...
Click to collapse
Hard to say, I don't see why it wouldn't... I'll have to download it, but don't have an NVIDIA PC card.
http://forum.xda-developers.com/showthread.php?t=2505510
Bought A/A USB Cable, but M.O.J.O wouldn't be recognized from PC, tried USB2 and USB3.
Over wireless ADB "adb shell logcat" and "adb reboot bootloader" is working, but loosing connection while reboot. Also no USB detection.
Anyone else played around a bit? I whish i could root it^^
saenta said:
Bought A/A USB Cable, but M.O.J.O wouldn't be recognized from PC, tried USB2 and USB3.
Over wireless ADB "adb shell logcat" and "adb reboot bootloader" is working, but loosing connection while reboot. Also no USB detection.
Anyone else played around a bit? I whish i could root it^^
Click to expand...
Click to collapse
That was expected, that ADB over USB don't work.
I have tried to "adb reboot boot loader", bot the device seems only to reboot to OS.
"adb reboot recovery" loads till the lying Droid with exclamation mark.
One thing, I tinker around is, what's the use of the microUSB port in the battery hole of the controller. Maybe we can use the connection to enter the recovery while booting ?
I have the M.O.J.O since today. I had many Androids (Smartphones/Tablets/TV-Boxes and Sticks and even an OUYA) but this device is from software side a holy overpriced piece of crap.
MAD CATZ, please "leak" some more informations to get root access and other basics. Bring the Play Store in a working condition. Even cheap chinese Androids have more APP access.
I've bought it to use it as a Mediacenter, XBMC is working and Watchever too, but to control the Box from my Smartphone or PC i need root, also to hide the buttons and use apps in fullscreen, for mediacenter its obligatory to have root...
hopefully Mad Catz itself will help us with it, looks like they give pretty good support.
saenta said:
I've bought it to use it as a Mediacenter, XBMC is working and Watchever too, but to control the Box from my Smartphone or PC i need root, also to hide the buttons and use apps in fullscreen, for mediacenter its obligatory to have root...
hopefully Mad Catz itself will help us with it, looks like they give pretty good support.
Click to expand...
Click to collapse
Try asking the live online support guy found on their website.
He's been super helpful for me thus far.
Mad Catz Rich said:
You don't need to use USB - connect to M.O.J.O. over the network instead.
(1) <PC> Download Android sdk from Android website
(2) <Mojo> connect ethernet or connect wifi to get a ip address xxx.xxx.xxx.xxx
(3)<Mojo> Settings -> About M.O.J.O. --> Build number ==> click 8 times, Developer options will appear in Settings
(4) <Mojo> Settings -> Enable USB debugging
(5) <PC> Execute in command line==> adb.exe connect xxx.xxx.xxx.xxx
(6) <PC> type adb shell logcat to get debug message
Click to expand...
Click to collapse
Hi,
Do you know how to connect via adb while the mojo is in fastboot or from the recovery option "apply update from ADB"?
I've tried using USB & eth0 and both not working.. is there a trick to it?
saenta said:
Bought A/A USB Cable, but M.O.J.O wouldn't be recognized from PC, tried USB2 and USB3.
Over wireless ADB "adb shell logcat" and "adb reboot bootloader" is working, but loosing connection while reboot. Also no USB detection.
Anyone else played around a bit? I whish i could root it^^
Click to expand...
Click to collapse
Theirs another method to rooting that doesn't require the male to male cable
Geohot released an app called towelroot v1 which roots it for u just run the app on the mojo and click a few buttons.
Proceed to towelroot.com on the mojo web browser and click the image on the right side of the screen that looks like an upside down y this will download the app to the mojo proceed to install and click the big button in the centre, you now are rooted my friend
I can't remember how it took ages I had massive issues with the male to male method initially. Had to mess around with some terminal commands before my PC would recognise the mojo. but it was so long ago now I can't remember them.
Edit: Just saw how old OP was imagine hes rooted by now
Hi guys,
as the M.O.J.O. obviously lacks USB debugging, I was wondering if some of you where able to deploy/debug apps using NVidias Tegra plugin for Visual Studio.
Sadly the plugin seems to be using a internal adb instance, which you don't have access to. Apparently the internal adb instance only scans for USB devices and AFAIK there is currently no way to tell it to connect to a specific ip address
So either there has to be a way to tell the Tegra plugin to connect to tcp/ip devices OR to get somehow USB debugging working on the M.O.J.O using a USB A Male to A Male cable.
Help is highly appreciated.
Hi!
Have you tried ADB via WLAN?
Code:
adb connect xxx.xxx.xxx.xxx
EDIT - solved! I've never noticed that apparently some cheap micro usb cables will not work for adb data connections though they work with other devices such as external drives just fine. Grabbed a 3rd cable out of desperation and it hooked right up. What are the odds? Learn something new every day.
Either I'm being thick or this is just fubared - I have a non-rooted Asus z380m running Android 7.0 firmware ww_v5.3.20_20180809. I cannot for the life of me get it to connect to any of my pc's in order to enable write secure settings for something I'm trying with Tasker (turn gps off requires security?). I've Googled forever, tried every usb driver I can locate (including unsigned installs), ensured that Developer mode, USB debugging and USB config on device is set to MTP protocol. NOTHING seems to enable usb connection to pc. The only way I've been able to get files on & off device is through Asus file manager utility that provides web interface (which sucks).
I also tried a Win7 laptop with the "latest_usb_driver" package and no joy there either.
I'm not the most savvy Android guy around, but doing IT for many years I have more than the average clue. Except here apparently.
Any insights would be _greatly_ appreciated.
Click to expand...
Click to collapse