Hi all,
is it possible to buy external 3G modem for my toshiba folio 100?
I wanna use the SIM card which I already have. All I need is any external device with 3G modem, SIM card slot, drivers for android 2.2(I reinstalled OS) and it should be powered from folio(no power adapter). thnx
I don't know who is your internet provider, but you can buy a portable 3g to wifi router from Vodafone. Its small enough to fit your pocket (2.5 ") and it will accept up to 6 wireless connections and 7.2 Mbps, which is not bad at all!
bastospn said:
I don't know who is your internet provider, but you can buy a portable 3g to wifi router from Vodafone. Its small enough to fit your pocket (2.5 ") and it will accept up to 6 wireless connections and 7.2 Mbps, which is not bad at all!
Click to expand...
Click to collapse
T-mobile(Slovakia). We don't have Vodafon in Slovakia.
But, I already have a sim card with 3GB data limit per month. I wanna use that one. I know there is USB 3G modem with SIM card slot on the market, but it cost around 40-50 €. I will spend that much money only if somebody make me sure that the modem will work with android 2.2 on toshiba folio 100.
I wanna use USB modem, bacause those are powered from USB port. So, no battery, no kabels, no adapters.
Miro.J said:
But, I already have a sim card with 3GB data limit per month. I wanna use that one. I know there is USB 3G modem with SIM card slot on the market, but it cost around 40-50 €. I will spend that much money only if somebody make me sure that the modem will work with android 2.2 on toshiba folio 100.
Click to expand...
Click to collapse
Kernel has so far no drivers embedded i know off, that would enable usb 3g modems.. i tried some Huawei 3g modems but all usb dongles fail to work, and we need driver for them to make it work and get them working with our kernel.
i dont think its easy right now..
probably best choice right now is a old htc magic or tattoo with Wifi Tether app on top, and connect using adhoc from folio..
Hi Dexter,
I installed today your Mod 1.3 on a Folio 100.
I tryed a Hauwei E160 and a Qualcom GI0225 3G without success.
I read Malata T2 support 3G dongles,
do your mod TNT based in Malata support 3G dongles?
Thanks
claudioggs said:
do your mod TNT based in Malata support 3G dongles?
Click to expand...
Click to collapse
its all in the kernel, and im not using their kernel here, only the libs+framework .. kernel is not hardware compatible.
Hi,
Dexter_nlb said:
its all in the kernel, and im not using their kernel here, only the libs+framework .. kernel is not hardware compatible.
Click to expand...
Click to collapse
It should be no problem to add huawei drivers to the kernel, as we can recompile it without any problems.
The more difficult part is to add support to android for it, but I can take a look on it. The ZT-180 has support for Huawei datacards. We can check how they are doing it...
DerArtem said:
The more difficult part is to add support to android for it, but I can take a look on it. The ZT-180 has support for Huawei datacards. We can check how they are doing it...
Click to expand...
Click to collapse
if the driver and usb handling is added, we can probably make it work..
Toshiba already included a driver for some SonyEricsson card, and if Malata T2 has a driver, we can re-use theirs for sure..
I'm not stopping anyone here would be great if huawei devices would work, i got 2 here i can test with..
Hi,
THIS IS OBSOLTE PLEASE CHECK http://forum.xda-developers.com/showthread.php?p=10617881
Dexter_nlb said:
if the driver and usb handling is added, we can probably make it work..
Toshiba already included a driver for some SonyEricsson card, and if Malata T2 has a driver, we can re-use theirs for sure..
I'm not stopping anyone here would be great if huawei devices would work, i got 2 here i can test with..
Click to expand...
Click to collapse
Attached is update.zip with a recompiled kernel.
Here are the changes:
* Added drivers for USB datacard (especially huawei)
* Added a lot of USB-Serial drivers
* Added support for DVB devices - maybe someone want to watch TV using a DVB-T stick on the folio
* Removed SMB driver - it is obsolete - CIFS should be used insted
* Added support for a few USB Ethernet cards
* Added USBFS support
THIS IS OBSOLTE PLEASE CHECK http://forum.xda-developers.com/showthread.php?p=10617881
You can now connect the huawei datacard to the folio and it will be recognized by the kernel. The next part is to add the userspace apps to control the modem.
Here is the dmesg of connecting a Huawei K3765-HV (Vodafone):
Code:
<6>[ 481.811357] usb 2-1.2: new high speed USB device using tegra-ehci and address 3
<6>[ 481.859931] usb 2-1.2: New USB device found, idVendor=12d1, idProduct=1001
<6>[ 481.866823] usb 2-1.2: New USB device strings: Mfr=3, Product=2, SerialNumber=0
<6>[ 481.874178] usb 2-1.2: Product: HUAWEI Mobile
<6>[ 481.878543] usb 2-1.2: Manufacturer: HUAWEI Technology
<6>[ 481.884588] usb 2-1.2: configuration #1 chosen from 1 choice
<6>[ 481.912162] option 2-1.2:1.0: GSM modem (1-port) converter detected
<6>[ 481.936345] usb 2-1.2: GSM modem (1-port) converter now attached to ttyUSB0
<6>[ 481.959700] option 2-1.2:1.1: GSM modem (1-port) converter detected
<6>[ 481.974394] usb 2-1.2: GSM modem (1-port) converter now attached to ttyUSB1
<6>[ 481.984637] option 2-1.2:1.2: GSM modem (1-port) converter detected
<6>[ 481.993997] usb 2-1.2: GSM modem (1-port) converter now attached to ttyUSB2
Important:
The Huawei datacards present only the internal storage when connected to a PC/device without the correct userspace programms. Before connecting it to the Folio you must disable the internal storage of the Huawei datacard. Otherwise only the internal storage will be detected by the Folio.
You can do this in Windows by opening the correct COM port with Hyper Terminal or Putty and enter:
Code:
AT^U2DIAG=0
In order to avoid this step we should add (usb_modeswitch) into the folio firmware. There is also a static arm build availible.
Update 1.1:
I have also added USBFS support to the kernel. This is required by usb_modeswitch.
You can also use lsusb now.
Before using lsusb you must mount it first:
Code:
mount -t usbfs -o devmode=0666 none /proc/bus/usb
THIS IS OBSOLTE PLEASE CHECK http://forum.xda-developers.com/showthread.php?p=10617881
Update 1.2:
I have added ppp-async and sync support to the kernel and also activated the ril servie.
It is possible to connect to GSM / UMTS networks with a custom ppp script now.
DerArtem said:
Hi,
Attached is update.zip with a recompiled kernel.
Here are the changes:
* Added drivers for USB datacard (especially huawei)
* Added a lot of USB-Serial drivers
* Added support for DVB devices - maybe someone want to watch TV using a DVB-T stick on the folio
* Removed SMB driver - it is obsolete - CIFS should be used insted
* Added support for a few USB Ethernet cards
You can now connect the huawei datacard to the folio and it will be recognized by the kernel. The next part is to add the userspace apps to control the modem.
Click to expand...
Click to collapse
Wow,
Just think what FolioMod 1.4 will offer...
One question though, do you guys that changes the kernel cooperate ?
/\/\artin
ma1999 said:
Wow,
Just think what FolioMod 1.4 will offer...
One question though, do you guys that changes the kernel cooperate ?
/\/\artin
Click to expand...
Click to collapse
Sorry? What do you mean?
I think ma1999 is asking if the people working on FolioMod is working togheter.
3G support will be a great new feature! Thank you alot!
DerArtem said:
Sorry? What do you mean?
Click to expand...
Click to collapse
DerArtem unt Weeds2000 and more(?) people are modifying the kernel.
I'm no kernel developer (mainly C++/PHP) but I know that when several developers change the same code they may "reinvent the weel" and/or do things that spoils for eachother.
Anyway, I understand adding modules to the kernel might not be rocket science but to me and probably all other of us "Folio-heads" the things you people do are really GREAT !!!
/\/\artin
DerArtem said:
Hi,
Attached is update.zip with a recompiled kernel.
Here are the changes:
* Added drivers for USB datacard (especially huawei)
* Added a lot of USB-Serial drivers
* Added support for DVB devices - maybe someone want to watch TV using a DVB-T stick on the folio
* Removed SMB driver - it is obsolete - CIFS should be used insted
* Added support for a few USB Ethernet cards
You can now connect the huawei datacard to the folio and it will be recognized by the kernel. The next part is to add the userspace apps to control the modem.
Here is the dmesg of connecting a Huawei K3765-HV (Vodafone):
Code:
<6>[ 481.811357] usb 2-1.2: new high speed USB device using tegra-ehci and address 3
<6>[ 481.859931] usb 2-1.2: New USB device found, idVendor=12d1, idProduct=1001
<6>[ 481.866823] usb 2-1.2: New USB device strings: Mfr=3, Product=2, SerialNumber=0
<6>[ 481.874178] usb 2-1.2: Product: HUAWEI Mobile
<6>[ 481.878543] usb 2-1.2: Manufacturer: HUAWEI Technology
<6>[ 481.884588] usb 2-1.2: configuration #1 chosen from 1 choice
<6>[ 481.912162] option 2-1.2:1.0: GSM modem (1-port) converter detected
<6>[ 481.936345] usb 2-1.2: GSM modem (1-port) converter now attached to ttyUSB0
<6>[ 481.959700] option 2-1.2:1.1: GSM modem (1-port) converter detected
<6>[ 481.974394] usb 2-1.2: GSM modem (1-port) converter now attached to ttyUSB1
<6>[ 481.984637] option 2-1.2:1.2: GSM modem (1-port) converter detected
<6>[ 481.993997] usb 2-1.2: GSM modem (1-port) converter now attached to ttyUSB2
Important:
The Huawei datacards present only the internal storage when connected to a PC/device without the correct userspace programms. Before connecting it to the Folio you must disable the internal storage of the Huawei datacard. Otherwise only the internal storage will be detected by the Folio.
You can do this in Windows by opening the correct COM port with Hyper Terminal or Putty and enter:
Code:
AT^U2DIAG=0
In order to avoid this step we should add (usb_modeswitch) into the folio firmware. There is also a static arm build availible.
Click to expand...
Click to collapse
It does not update
should probably move this as it's turning into a dev-thread
thank you guys for responding, I hope you can add this into your next foliomod update. I see more people are having this problem. For now I will use my nokia N95 as an acces point(if AD HOC realy works).
I have also added USBFS support to the kernel. This is required by usb_modeswitch.
You can also use lsusb now.
Before using lsusb you must mount it first:
Code:
mount -t usbfs -o devmode=0666 none /proc/bus/usb
Please see previous post for the download.
DerArtem said:
I have also added USBFS support to the kernel. This is required by usb_modeswitch.
You can also use lsusb now.
Before using lsusb you must mount it first:
Code:
mount -t usbfs -o devmode=0666 none /proc/bus/usb
Please see previous post for the download.
Click to expand...
Click to collapse
Now I'm getting confused. Is it working already? This is only adding it into kernel, right? We still need to install some application that will provide us with some control over the modem. Am I right?
Miro.J said:
Now I'm getting confused. Is it working already? This is only adding it into kernel, right? We still need to install some application that will provide us with some control over the modem. Am I right?
Click to expand...
Click to collapse
correct, and currently the Japanese tablets has drivers for huawei cards.. but driver might be incompatible.
and Advent vega i think do have a driver for these too.. so with the help of their work, we might be able to get our folio online, but its still in a early stage..
and im still looking for my own huawei card i misplaced...
Hello, I just got my disaster "baby" today. I was surprised, that really ALL the negative rumors are true, hope the mod will help After a superb HD2 Superram "Android" phone..
Where is the problem to take a small 3G pocket Router instead. Besides the price of course ? I saw really a few nice compact Models, some with ethernet port, even better...
For me, it would be better to have the router in the Jacket or backpack, then having this stick hanging out of the usb port, or even connected via cable...
Or did I miss here somthing ? ...Always the same, I could not wait. The 3g Model is not yet available here.
Thanks
P.s. I dont know, but it feels like gliding with a rubber on the screen. Goose Skin...
Are you all doing it without protection ? Or is there a protector, which adds some smooth silkyness ? In this area is my omnia7 number one at the moment...
I want to use a usb ethernet card (ASIX AX88xxx), so I need to build my own kernel. I also want sshd and root access, so I would like to use Urukdroid.
How do I do this? Alternatively: What could I use instead of Urukdroid?
I tried chulri's [HOWTO] Build custom kernel, libraries and applications on your own and it compiles fine. I also compiled it with builtin support for my USB ethernet card. (There are some warnings with both stock and my kernel config but chulri mentions in the thread that some of this is to be expected.)
I used the new zImage as the zImage for the UrukDroid 1.5 installer. It installs fine, but when it tries to boot Urukdroid, the Urukdroid bootimage shows but after "Switching to rootfs" the tablet restarts (stock Archos bootscreen shows) and boots the standard archos system. This happens with both the stock kernel config and my kernel config.
Is this my fault, because I have the wrong rootdevice in my kernel? (I installed it on internal storage, not on a sd card.) I'm a bit rusty when it comes to linux kernel builds. Where do I enter the rootdevice and which is the right rootdevice for Urukdroid on internal storage?
Then I tried chulri's build environment but replaced the linux kernel sources with the kernel soruce from Urukdroid 1.5. The result was the same: When Urukdroid switches the rootfs , the screen turns blank, the standard Archos boot image shows and the standard android system gets loaded.
I would be very grateful, if somebody could point me in the right direction. (I would be even more grateful for a zImage, but that is a bit much to ask and I rather would like to know my way around kernel builds...)
[EDIT] OK, the question about the root device is probably silly, since it has been AGES since this was compiled into the kernel. The Main Question still remains: How can I use my USB ethernet card?
Marcus
Building a kernel with stock SDE + chulri works, but still no ethernet
Since I was unable to get a custom kernel for Urukdroid working, I reflashed the tablet with stock firmware and SDE.
I basically followed Chulri's Root easily your gen8 device
Then I built a custom kernel with compiled-in ethernet support and compiled-in usb device support for my ethernet card. Again just like Chulri says.
I used the resulting zImage together with chulri's initramfs.cpio.gz from the +rw kernel.
Thanks for the great HOWTOs, Chulri!
When I now boot the developer edition and connect to it via adb (How I miss urukdroid already ) this is the dmesg output for the usb ethernet card:
Code:
usb 2-1: new high speed USB device using musb_hdrc and address 2
usb 2-1: default language 0x0409
usb 2-1: New USB device found, idVendor=0b95, idProduct=1780
usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-1: Product: AX88178
usb 2-1: Manufacturer: ASIX Elec. Corp.
usb 2-1: SerialNumber: 000003
usb 2-1: uevent
usb 2-1: usb_probe_device
usb 2-1: configuration #1 chosen from 1 choice
usb 2-1: adding 2-1:1.0 (config #1, interface 0)
usb 2-1:1.0: uevent
asix 2-1:1.0: usb_probe_interface
asix 2-1:1.0: usb_probe_interface - got id
eth0 (asix): not using net_device_ops yet
eth0: register 'asix' at usb-musb_hdrc-1, ASIX AX88178 USB 2.0 Ethernet, 00:11:6b:73:75:ac
/root/archos/archos-gpl-gen8/linux/drivers/usb/core/inode.c: creating file '002'
hub 2-0:1.0: state 7 ports 1 chg 0000 evt 0002
hub 2-0:1.0: port 1, status 0100, change 0001, 12 Mb/s
usb 2-1: USB disconnect, address 2
usb 2-1: unregistering device
usb 2-1: usb_disable_device nuking all URBs
usb 2-1: unregistering interface 2-1:1.0
eth0: unregister 'asix' usb-musb_hdrc-1, ASIX AX88178 USB 2.0 Ethernet
usb 2-1:1.0: uevent
usb 2-1: uevent
So ethernet is still not working, but at least I got a lot further.
Does anybody have any ideas on how to go on from here?
Am I missing any userland components?
Any help would be greately appreciated.
I keep on trying to get it to work on my own and will post any progress.
Marcus
Hi!
Same problems here form me with an FTDI chip.
The musb_hdrc thing is a bit tricky, here are some of my experiences.
You can alter the kernel config when building a custom kernel, but the msub_hdrc is built by default as a module, which is bundeled with the stock firmware, so if you for example want to change something this will mess up the whole stack.
The modules built are under lib/modules and i couldn't see them neither in rootfs nor in initramfs so they probably arrive on the device when you install the stock firmware (the step before you flash the custom initram and zImage in chulri's tutorial)
For example my problem is that I have an FTDI chip <-> CA-157 micro-A plug which is plugged in into a70IT's micro plug. But it only works if I plug the micro A without the attached FTDI chip and as a second step attach the FTDI chip
There is probably something connected to the state changes because first the musb needs to go to a_idle and the to a_host to pick the FTDI
This is the reasong why I started to investigate the state machine of musb but I faced a big problem, namely if I remove musb_hdrc.ko from lib/modules and compile my modified version in the kernel then nothing happens after host attached dmesg message. The funny thing is that the only modification is a verbose log level nothing serious. If the musb_hdrc.ko stays in lib/modules and I compile the kernel with my musb_hdrc for sure the module already loaded message comes up -> this is totally normal as we don't want to load it twice.
I think there are some let's call it archos specific things and not "dirty hacks" which prevents me to modifiy some drivers in the way I want it...
I tried to post some questions to the platform thread but I'm still too green for it
I gave an FTDI related thread where my problem is detailed...
It would be very useful for me if a senior could explain how the full custom firmware is built up. What stays from the stock part and what is overwritten, yes I know that th initramfs and zImage is overwritten but I'm interested could we for example build a full .aos like firmware file where the lib/modules and all othe content is defined by the platform developer...
I know the most of the post is off topic but I'm really interested to in customization of platform like this but still have to learn a lot...
br, sodjas
THings that should be easy, never turn out to be easy on embedded devices.
Thanks for your insights on the topic, sodjas.
This nicely explains why I got stuck.
Somehow the things that should be easy, are never easy on embedded devices.
I will keep trying when I have some free time again....
Hi,
inresting thread indeed...
Though i did not take a deeper look into the archos kernel structures, maybe the solution is much simpler... maybe it's more complex
When compiling a custom kernel/modules both must match in the end.
In other words all modules should be replaced with the ones of your new kernel.
Stock firmware uses squashfs so it's little tricky to remove or insert modules to the right place...
The best thing to start with custom kernel development would be Urukdroid which uses "real" rootfs on ext4. By using the SDCARD install method there's a comfortable way to modify the rootfs (replace modules etc.).
At least if you got a linux machine at hand.
Urukdroid uses links to point to the real modules here.
EDIT: Here are the Urukdroid 1.5.1 kernel sources
Not sure if there are kernel modules in initial ramdisk already... had to take a look.
Maybe you already knew this, maybe not... anyway could be helpful
Best regards,
scholbert
True enough, the userland alone makes urukdroid a much better environment for experimentation...
But I only managed to compile a kernel according to chulri's HOWTO which works with the stock development environment.
I tried booting urukdroid with such a kernel but failed. The device did show the urukdroid boot screen and progress bar but then restarted and loaded the stock archos android environment.
Maybe I'm not doing my forum searches/gooogle searches right. I will try again. But how do I set up a cross compilation environment for urukdroid kernels?
Are the urukdroid developers using the build environment and kernel sources according to chulri and I just didn't chose the right mix of modules to compile?
I tried using chulri's build environment and replaced the linux kernel sources with the urukdroid kernel sources, but did not manage to compile a bootable kernel.
This doesn't get easier since archos modified the kernel sources and urukdroid probably has some special modifications, too.
There must be some information missing that I wasn't able to find yet. (Or maybe I am just stupid . Hey, I would welcome a nice insulting rant about now that tells me what a sucky noob I am and includes some nice links about how I can pull myself out of this swamp by my own bootstrings .)
EDIT: I just saw your edit, scholbert. Thanks for the helpful link. Could you help with setting up a cross compilation environment? Even just a few links and pointers would be welcome.
Are you saying that I should invest in an sdcard and manipulate the rootfs directly, instead of using the kernel update function of the tablet's developer boot menu? Or does the rootfs only help me including self compiled modules? Couldn't I just integrate the devices directly into the kernel, avoiding any rootfs manipulation?
Hi,
yeah i think Urukdroid uses the same/similar environment.
In fact you'll have to, if you use propietary kernel modules from stock firmware (e.g. hdmi modules).
mmkhd said:
Could you help with setting up a cross compilation environment? Even just a few links and pointers would be welcome.
Click to expand...
Click to collapse
So you said you followed chulris way... you'll have to built a toolchain from the archos sources first.
How did you compile your kernel then?
Anyway here's another interesting post...
http://forum.xda-developers.com/showthread.php?t=978564&styleid=15
EDIT: The cross toolchain in fact is build from scratch using the buildroot system and the modified sources from archos.
Check this for more information about buildroot toolchain generation.
I wonder if someone already built a standalone cross toolchain ready to use on different linux systems. Might be a quite useful thing
mmkhd said:
Are you saying that I should invest in an sdcard and manipulate the rootfs directly, instead of using the kernel update function of the tablet's developer boot menu? Or does the rootfs only help me including self compiled modules?
Click to expand...
Click to collapse
You should always use the update function for kernel and initial ramdisk.
So using a sdcard system will just help you to modify the rootfs very easily (e.g. integrating the modules).
mmkhd said:
Couldn't I just integrate the devices directly into the kernel, avoiding any rootfs manipulation?
Click to expand...
Click to collapse
Honestly i'm not sure if this will work properly for any peripheral... AFAIK some drivers are required to be loaded as a module.
Anyway, i guess i will also do some kernel work the next months... if i find useful information i'll keep you informed
EDIT: Ah, i nearly forgotten... there are no modules in inital ramdisk.
Everything is located in /lib/modules (as sodjas already pointed out).
Cheers,
scholbert
Hi mmkhd,
i don't know if you made some progress with this issue.
Anyway, i build an Archos specific standalone toolchain in the meantime.
Attached are the modules for Asix based USB2LAN adaptors.
Works very well with UrukDroid 1.5.1 on my A101.
Though you'll have to load the modules and setup the network manually at the moment.
At the shell:
su
insmod mii.ko
insmod usbnet.ko
insmod asix.ko
ifconfig eth0 xxx.xxx.xxx.xxx
You'll have to set the gateway and nameserver as well to use your browser.
I'm working on an automated solution...
Regards,
scholbert
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?
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
Hi all,
I try to get USB-OTG support for my mt6753 phone running. Lots of websites show that the device should offer OTG support and you find several phones with this chipset having this option. I have a DOOGEE T3 that should have that, too.
But nothing happens when connecting different USB storages to the phone. Neither the device internal LEDs flashes nor kmsg / dmesg shows something USB related (phone is rooted).
I already ran several USB OTG checkers from google app store that added android usb host permissions in /etc/permissions in several xml files.
I also added the usb.host setting in build.prop and disabled the charger only option.
I also added a seperate USB power supply for definitively providing enough power for the USB storage. When using this additional cable the USB storage blinks twice but nothing happens on the phone.
There are a lot of items in /sys on the phone (e.g. usb20_host) that should point me to the capabilities for OTG.
I don't see a real "hardware" usb host controller in lsusb (like an uchi or ehci controller I know from Intel based systems) - only the "Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub"
How to proceed? If you need more information to determine the next steps, just let me know.
Best regards,
RX1901
Changing the cmode property to 2 (host mode only) causes some kernel debugging lines that state at the end "switch_int_to_host is done" but the "is_host" stays 0.
Am I on the right track?
After further checkings, it looks as if the usb20_otg_if is not compiled into the kernel. How can I add this? As a quick test a .ko file would be sufficient.
RX1901 said:
After further checkings, it looks as if the usb20_otg_if is not compiled into the kernel. How can I add this? As a quick test a .ko file would be sufficient.
Click to expand...
Click to collapse
Find a kernel source for your chip. However, I'm concerned about your phone not powering up the guest device. I think it should do that regardless of the driver. Is your OTG cable good? Proper cable should have OTG pin pulled to the ground on the phone's side and floating on the device's side.