Greetings....
(This post is regarding my Nook Touch, however; as I believe the development setup is the same as a Nook Tablet, I am posting here also)
I am hoping to get my Asix Usb to Ethernet adapter working with my nook STG. I believe the only remaining requirement is to compile the drivers for it (which are android 2.x compatible according to the driver manufacturer website).
I am rooted and have 'usb host mode' successfully working.
When my adapter is plugged in, it displays as a 'connected device' in my Usb Host information app and shows the details; make/model etc - so its connected successfully.
It works plugnplay with my other droid devices, however in these devices there is an Asix driver folder in /sys/bus/usb/drivers and there is not in my Nook, thus I believe i simply need to compile the drivers which will create the Asix driver folder.
There are no errors displayed in Terminal Emulator after a typing "dmesg" once connected.
If you have the correct setup and can compile the drivers for me (and potentially other Nook users), i will exchange them for => 10GPB or 10 of your currency, via your desired means.
I was trying myself on an ubuntu vm in windows but have had to stop due to eye troubles; hence trying to use a Nook eink as my sole computer.
INFO:
Device: Nook STG firmware 1.21 - kernel source file link = images.barnesandnoble.com/PResources/download/Nook/source-code/nook2_1-2.tgz
Adapter Driver: Asix AX88772 - driver source file link = www.asix.com.tw/FrootAttach/driver/AX88772C_772B_772A_760_772_178_LINUX_Driver_v4.11.0_Source.tar.bz2
Adapter Info: BobjGear Adapter made for Android Tablets = www.amazon.co.uk/BobjGear-Ethernet-Exceptions-Description-Ultrabooks/dp/B007RTACDM
Other info: An XDA thread compiling the same drivers - http://forum.xda-developers.com/showthread.php?p=37548841
I don't know how to apply the drivers so I need to learn how to do so, I have ADB set up and have Noogie, CWM and NookManager .img also.
My Nook Touch thread - ]http://forum.xda-developers.com/showthread.php?t=2570149
Any other info needed i will provide
Sam
Related
Will my huawei e1550 work under android?
I see that some other Adroid devices (china tablet pc like Zenithink and other) have the software, which can config internet connections.
Will Gen8 init this device?
ncuxxx said:
Will my huawei e1550 work under android?
I see that some other Adroid devices (china tablet pc like Zenithink and other) have the software, which can config internet connections.
Will Gen8 init this device?
Click to expand...
Click to collapse
For now, no. Unless Huawei or 3rd party develop driver for it.
My E1550 now also collecting dust coz i'm using 101 most of the time rather than laptop.
If i understand, we need root access to add 3rd party driver? Or there uis no way to compile driver?
This would be quite interesting if it would work.
Would this also enable call/sms functionalities?
I have an AT&T Laptop Connect Dongle which does not work. I have been able to bluetooth tether using PAN. I would rather use adhoc, i haven't found a way yet.
I prefer Archos to improve the stabilities of his 2.2 firmware first before adding more "new" features.
3G dongles
Correct me if I'm wrong, but as far as I was able to digg around, it seems that USB host mode (wich is already in Archos), __usbserial.ko__, and adeqaute parts of devfs rules, are only three really necessary things that are needed on any linux, for USB 3G dongles to get properly recognized (at least Huawei ones).
rest of the things regarding "dial-up" a 3G connection, are done with commands from ppp package (should be in froyo), can be done from shell (busysbox __should__ be sufficient) for a start.
usb_modeswitch package is needed also, but only for the modems that are USB composites with virtual CD-ROM and/or MMC card reader (like mine E1552) in order to switch them to a serial mode (because their are detected as mass-storage initialy). For a start, this can be overcomed by sending adequate AT command's to dongle, that disable dongle's virtual CD-ROM and/or MMC card reader, from some windows machine prior to experimenting with dongle on linux/archos (setting is saved on dongle - you only need to do it once).
Since I still don't have my A101 (should receive it beggining of 2011), can someone tell me from kernel .config file is USB serial support compiled in archos kernel, and if not can we compile it as a additional module (like archos unionfs/ntfs modules is see in other thread) ?
I have an Ainol Novo 7 Paladin tablet running android ICS 4.0.3 (rooted) that I want to use in one of my projects. And I need it to communicate with an arduino - one with FTDI or prolific PL2303 serial interface. Now I know that the Paladin should work as an USB host but I need something more. I need an high level Java library that can use this serial interface. I've worked with rxtx on a desktop machine before and that is the most complicated that I would like to get. The main reason is that I simply don't have enough knowledge to write myself an serial driver. I just need a simple character based two way communication.
I've found this http://slickdevlabs.com/slick-usb-2-serial-library/ but I don't think that it will work for me - at least the test application doesn't since the Paladin has an Ingenic JZ4770 CPU that isn't ARM based. And the second problem - I don't like the price.
So I have made an USB OTG cable that is working - I can connect a mouse, keyboard, usb drive,... . Getting the serial interfaces working is another problem. When I plug the arduino with an PL-2303 controller to the tablet I get this (with dmesg):
Code:
USB AS HOST MODE
...
hub 1-0:1.0: unable to enumerate USB device on port 1
usb 1-1: new full speed USB device number 82 using musb-hdrc
usb 1-1: device v067b p2303 is not supported
we are entering usb_match_id!!!!!
Simillar with the arduino with FTDI controller.
As far as I know android should have the drivers for the PL-2303 and FTDI chips included. So any ideas?
I am quite interested in usage USB host ability on my china no-name tablet based on Allwinner A13 CPU. I'd like to use it as GUI front-end for my embedded project with STM32F4 ARM microcotroller. So far I use laptop as the GUI for this device. STM32F4 is connected via USB as a vendor-specified device. I use WinUSB library on laptop to enumerate connected device and to open endpoints.
I'd like to use tablet instead of PC. So I looked to the USB host API on Android and tried to enumerate devices. However I couldn't enumerate any device - includes mouse or flash drive, which works perfectly in the system, but getDeviceList from UsbManager returns emtpy list.
I installed USB Host Diagnostics application and run a test. All results are yes, only items "Claims support" and "Device detected" in Android API shows no. But there's an item "Device detected" in Rooted API, which is yes.
I'm quite new to Andoroid developing. What is Rooted USB host API? How can I use it? Thank you for your answer.
hi.
forum search did not help with this
after successfully setting up and using adb for a couple of days with my viewpad 7e (device-id is 0x0bb0 - this value is in my adb_usb.ini - although i believe it once worked with 0xbb0 - now both doesnt) adb decided not to see my tablet anymore.
EDIT: of course usb debugging is enabled.
i can use the binaries, only my device does not show up anymore. mac os x knows about the device:
Code:
ViewPad 7e:
Product ID: 0x0005
Vendor ID: 0x0bb0 (Concord Camera Corp.)
Version: 2.27
Serial Number: ViewSonic
Speed: Up to 480 Mb/sec
Manufacturer: VS
Location ID: 0xfd120000 / 4
Current Available (mA): 500
Current Required (mA): 500
mac osx 10.7.5
android-sdk downloaded again yesterday, so it should be pretty damn new.
besides the adb_usb.ini the installation is straight forward what you'll find in almost any howto on setting up adb. so where did i go wrong? or, what other stuff between my macbook and adb could keep adb from seeing the device? i got no ideas. if you need any more info about the device or the host, please let me know.
EDIT2: i use vmware fusion on my macbook. this normally asks me wether to pass on a usb device to the VM or connect it to the host. it does _NOT_ (however, settings regarding this are correct as in 'always ask') ask me anymore. i suspect this could be the problem. did anyone have this issue before?
[SOLVED] VMWare Fusion
solved.
as i suspected, VMWare Fusion/Mac OS X had their way with the devices. cleaning this up, rebooting, everything works again.
Hi all,
I'm sorry, I tried to provide direct links/images but unfortunately only after 10 posts I'm allowed to post URLs
The most recent, much welcomed, update to ChromeOS has introduced ADB over USB for a select few models ( find the chromium org url "chrome-os-systems-supporting-adb-debugging-over-usb" ).
However, I have yet failed to get this to work by connecting my brand new Pixelbook (as of yesterday) to a Windows 10 machine, and using the guide provided on developer (dot) android topic/arc/#adb-usb
Did anyone get this work successfully?
If so, can anyone point me in the right direction?
Using hardware:
- Pixelbook with Stable Build 67, and also attempted Dev Channel with build 69.
- Connected USB0 (left side) to my Windows 10 laptop USB-A port, but also attempted connecting it to my laptop's USB-C port (so a USB-C to USB-C cable).
My steps:
- Powerwashed the Pixelbook
- Set Pixelbook to 'Developer Mode', see image:
h ttps://ibb.co/cRmiEo
- Enable Android Developer Options by going to Settings in ChromeOS, Manage Android --> 7 taps on Build Number and then opening the 'Android Developer Options' and enable ADB Debugging:
h tt ps://ibb.co/mLikS8
- Run the setup commands in crosh/shell as described in the guide (link above), such as dev_enable_udc , and dr_swap commands. As stated by the guide on developer.android: "Use this command each time you disconnect and reconnect a USB cable. To ensure your Chromebook is in UFP mode, you can run ectool usbpd <port number>" . See attached:
h tt ps://ibb.co/j8m5S8
- Attached the USB-C cable to the W10 laptop and run ADB devices.
- No devices show up in cmd (adb devices)
- Android Studio also does not list any devices to run on
- This is what I'm seeing in Device Manager, a 'malfunctioning adb device'
h tt ps://ibb.co/cpXen8
Any help would be greatly appreciated if anyone has already managed to the ADB USB to work!
No solution (yet)
Let me know whenever someone has given this a shot with their Chromebook.
I still haven't managed to solve it, also posted it to the Google Product forums now
Quick search of this forum shows this.
https://forum.xda-developers.com/ha...oks/guide-setting-adb-fastboot-x8664-t3806428
Brounzer said:
Hi all,
I'm sorry, I tried to provide direct links/images but unfortunately only after 10 posts I'm allowed to post URLs
The most recent, much welcomed, update to ChromeOS has introduced ADB over USB for a select few models ( find the chromium org url "chrome-os-systems-supporting-adb-debugging-over-usb" ).
However, I have yet failed to get this to work by connecting my brand new Pixelbook (as of yesterday) to a Windows 10 machine, and using the guide provided on developer (dot) android topic/arc/#adb-usb
Did anyone get this work successfully?
If so, can anyone point me in the right direction?
Using hardware:
- Pixelbook with Stable Build 67, and also attempted Dev Channel with build 69.
- Connected USB0 (left side) to my Windows 10 laptop USB-A port, but also attempted connecting it to my laptop's USB-C port (so a USB-C to USB-C cable).
My steps:
- Powerwashed the Pixelbook
- Set Pixelbook to 'Developer Mode', see image:
h ttps://ibb.co/cRmiEo
- Enable Android Developer Options by going to Settings in ChromeOS, Manage Android --> 7 taps on Build Number and then opening the 'Android Developer Options' and enable ADB Debugging:
h tt ps://ibb.co/mLikS8
- Run the setup commands in crosh/shell as described in the guide (link above), such as dev_enable_udc , and dr_swap commands. As stated by the guide on developer.android: "Use this command each time you disconnect and reconnect a USB cable. To ensure your Chromebook is in UFP mode, you can run ectool usbpd <port number>" . See attached:
h tt ps://ibb.co/j8m5S8
- Attached the USB-C cable to the W10 laptop and run ADB devices.
- No devices show up in cmd (adb devices)
- Android Studio also does not list any devices to run on
- This is what I'm seeing in Device Manager, a 'malfunctioning adb device'
h tt ps://ibb.co/cpXen8
Any help would be greatly appreciated if anyone has already managed to the ADB USB to work!
Click to expand...
Click to collapse
I have suceeded in doing this in my Samsung Chromebook Pro. There are a few problems off the bat.
1) Chrome OS ships with a very outdated version of ADB
2) There is no rule by default for accepting usb connections from vendors. You have to add it to your rules.d folder.
If you know what you're doing you can install the dependencies directly to your system and update the shipped adb using debian resources. You could also use crouton. I made a tutorial a while back. Things have changed a tab, but not much. tutorial link
Also I will attatch the script I made to automate the process on my CBP. With a little tweaking you could make it work for yourself. I know this probably isn't what you are looking for. But installing the debian resources will almost certainly get it running in the native crosh shell.