Hey all,
There's nothing that I could find that's recent (ICS & up) about USB to ethernet adapters. I've been following several threads for months and they've seemed to die down since the releases of ICS and JB. To my understanding, driver packs and terminal usage are no longer necessary to use a USB to ethernet adapter. I've read that you just plug it in and you're good to go!
Well, since about mid 2012 (and earlier), these USB to ethernet threads have been dying, and now that USB 3.0 has become more available (and cheaper!), new adapters are on the market. I'm hoping that hard line usage has become more practical than it was in some of the developmental threads, as my line of work requires testing and troubleshooting of lots cat5 cables.
I hope that this thread can clear some confusion that I have, and also that I've seen in many other similar threads.
List of working adapters
Linksys USB300M - quote - 10/100
List of several adapters in this post
I just ordered the Rosewill RNG-406U USB 3.0 gigabit adapter and will try that out. The description shows full Android 1.x, 2.x, 3.x, 4.x support on Newegg's page. (PS, it's on Newegg's Shell Shocker today only for $10 off)...
With ICS and JB (or even HC?) I've read that HC and up may be working without a driver pack (as opposed to this). Which means it should just be plug and play now.
Current questions (if you have it working):
What rom are you running (with kernel # please)?
Does a 10/100/1000 adapter work? (Will find out for my specific device when I get mine in the mail)
What is the brand & model name of the adapter you're using?
Plug and play? Or do you need terminal emulator to run commands?
Hi guys
At the moment I have 3 Motorola devices, all running CM10.1: A Wingray Xoom, RAZR XT910, and RAZR HD XT925. I have official CM from get.cm on the first two, the 3rd one is an unofficial build.
I've been looking to run old-school emulators and use an spare dualshock. With this configuration I can run my device as a portable Ouya-like emulation system. I downloaded the Sixaxis app. So far, I am having mixed results:
In all three devices, the device is confirmed to be working in theory, according to the compatibility test However, there is a problem with the BT connection
Xoom CM10.1 official does not connect.
XT910 CM10.1 official does not connect, however, rooted stock ROM works perfectly <<this one is annoying
XT925 CM10.1 unofficial works perfectly
I think this is a coding thing that is in the official CM.
In the instances that it works, the BT symbol lights up in the system bar. When it doesn't, nothing.
I suspect it has something to do with the Blutooth protocols.
Does anyone have any ideas how I can get this working?
UPDATE: on my XT910, I tried both Carbon ROM and AOKP, both have the same problem. This is perplexing.
Kang-A-rom
What is it?
a kang of purity rom with a few added functions. It is based on the hard work of others and no credit to me is implied, other than merging and building. All sources are available at:
https://github.com/lostdeveloper
Features:
* Full dac support, on boot, hot plug, volume control
*OC of CPU and GPU
*OTG while charging, fastcharging
*support for most dvbt tuners including the newer r820t tuners.
*automatic mounting of ntfs and exfat storage drives with read and write support
*easycap support, plug n play (requires carcam app)
*firm sleep
*wakelock blocker
*usb/bluetooth tethering (unconfirmed)
*more, and more coming....
Kangarom V2 03/09/2014
Changes:
*plug and play any easycap device (needs carcam app, and one model also needs firmware)
*added support in ramdisk and frameworks/base for USB tethering and bluetooth tethering. I have no way to test this, it needs testing, and I need logcats with any issues. I am completely unsure If I have everything here.
*included dashclock and simple explorer, both open source and useful, while not consuming a lot of space
*Wakelock Blocker, selectively prevent certain wakelocks to save battery
*all purity rom updates from DariosF
Download
http://d-h.st/qOT
________________________________________________________________________________________
Older Changelogs and
Downloads:
Kangarom v1, initial release
http://d-h.st/QXB
_____________________________________________________________________________
other info:
-some models of easycap may also require a firmware to function properly. These firmwares must be obtained by the end user and cannot be included by me for legal reasons. However, they can be downloaded freely from proper sources.
-use of dvbt tuners requires a script to load the needed modules and set up for chrulri's droidtv app.
-firm sleep, and dac on boot require crue's powermanager app to set options for firm sleep, fixed install mode, and fastcharge in hostmode
**The latest version of crue's app may be found here:
http://forum.xda-developers.com/showpost.php?p=50265682&postcount=411
Credit is his, so hit his thanks button.
More INFo about this can be found in my kernel thread, as well as links to the source code used for this:
http://forum.xda-developers.com/showthread.php?t=2558717
Im working on a tilapia build.....not yet.
feel free to ask any questions... Im not too concerned about hardcore dev stuff only. Anything that helps others find answers works for me.
reserved
one more.
would be cool if you could post more information for the dvbt driver
i used mine on usb rom as radio with wavesink and this driver: https://play.google.com/store/apps/details?id=marto.rtl_tcp_andro&hl=de
do i need the driver app now or only wavesink? or wavesink and a script?
EDIT:
and should i flash your kernel over the rom or is includet?
Awesome. Going to try this out right away. Thanks.
michiil said:
would be cool if you could post more information for the dvbt driver
i used mine on usb rom as radio with wavesink and this driver: https://play.google.com/store/apps/details?id=marto.rtl_tcp_andro&hl=de
do i need the driver app now or only wavesink? or wavesink and a script?
EDIT:
and should i flash your kernel over the rom or is includet?
Click to expand...
Click to collapse
Yea....I wanted to get the build up for you all, but I need to set up the OP properly just really busy. Kernel is included already...... dvbt will work as it use to with sdrtouch and other radio apps that use the userpace driver. To watch tv youll need to use a script to insmod the right modules....again ill link to the exact post when I have time, just search my kernel thread for r820t you will find it.
While these modules are loaded, your radio app wont work....it depends on that userspace driver and it wont have a device to "drive" because it is already loaded at the kernel level. So, the solution is a "load" script for kernel modules, then watch tv, then, an "unload" script...... and now your radio app will work again.
I will seriously fill those first three posts will all the needed info, but Im swamped right now with work. All the info is there in the kernel thread for now just need to search.....sorry.
Flashed this and worked right out of the bag, no need for external OTG apps. Ran PAGAPPS mini modular and is perfect for my needs. This came just in time as I'm getting my DAC in the mail tomorrow and plan on putting this in the dash of my car very soon thereafter. Thanks for all your hard work!
The only thing I think would be awesome is if you could incorporate volume buttons on the nav bar. I've never used Timur's rom but saw some videos and saw he had those. If not it'll be easy enough to get by. Thanks again!
sreister said:
Flashed this and worked right out of the bag, no need for external OTG apps. Ran PAGAPPS mini modular and is perfect for my needs. This came just in time as I'm getting my DAC in the mail tomorrow and plan on putting this in the dash of my car very soon thereafter. Thanks for all your hard work!
The only thing I think would be awesome is if you could incorporate volume buttons on the nav bar. I've never used Timur's rom but saw some videos and saw he had those. If not it'll be easy enough to get by. Thanks again!
Click to expand...
Click to collapse
Yes, its kindve on the list......sort of. The new kitkat framework only supports five total buttons on the navbar. Purity allows you to add two more already, but due to framework limitations I think it will be difficult to do this in a stable way. I was browsing around and i noticed that carbon ROM has a more involved navbar framework where you can set the navbar to launch volume control via "slim shortcuts." I got excited and thought it just needed to be cherry picked but....... I downloaded carbon ROM to try it and when i set it up the systemui crashed and repeatedly crashed until I rebooted. Once rebooted it once again crashed, I had to re flash the ROM and the same thing happened, so no go. This behavior is what I read should be expected if you try anything other than a menu button or a search button, or keyboard cursors on the kitkat navbar. In other words, any other button type would need to be fully implemented into the framework, no shortcuts. Im still researching this.....as time permits
The more likely scenario involves the quick launch shortcuts. With this ROM you can set up the home button for three on screen shortcuts via long-pressing the home button. If you download a volume control app, not a widget, an app, then you could use this quick launch method to access it. Or, you can already set it to open up settings>sound with the activity picker. I use "slider widget" for now.....simple desktop widget for volume control.
Super super suuuppperrrr silly question, but this is 4.4.2 right?
ZenInsight said:
Super super suuuppperrrr silly question, but this is 4.4.2 right?
Click to expand...
Click to collapse
Absolute latest from Google, yes.
This works pretty good on my in dash nexus 7. Couple of issues though... I use Bluetooth tethering from my phone, the tablet will connect but I have no internet connection. Also, I use an external microphone for voice commands, but it doesn't work on this ROM. I normally use AOKP ROM with Timur's kernel, this disables the internal mic and allows me to hook my external mic directly to the inputs of my Behringer UCA202 DAC. Also, the easycap issue that you've already mentioned in your kernel thread. Good work so far!
Sent from my SGH-I747 using xda app-developers app
And it goes in as the daily driver. Thanks for your efforts.
Sent from my SM-N900T using Tapatalk
gregthomas129 said:
This works pretty good on my in dash nexus 7. Couple of issues though... I use Bluetooth tethering from my phone, the tablet will connect but I have no internet connection. Also, I use an external microphone for voice commands, but it doesn't work on this ROM. I normally use AOKP ROM with Timur's kernel, this disables the internal mic and allows me to hook my external mic directly to the inputs of my Behringer UCA202 DAC. Also, the easycap issue that you've already mentioned in your kernel thread. Good work so far!
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I did not know about the external mic in usbrom.... Im not sure how easy it will be to figure out, but usb tethering and bluetooth tethering I can kang from cm11....
Ive got a fix for easycap devices as well..... if tilapia build tests well then ill try the tethering thing next.
redeyedjedi said:
I did not know about the external mic in usbrom.... Im not sure how easy it will be to figure out, but usb tethering and bluetooth tethering I can kang from cm11....
Ive got a fix for easycap devices as well..... if tilapia build tests well then ill try the tethering thing next.
Click to expand...
Click to collapse
Its actually a combination of Timur's kernel and AOKP ROM, not USBrom. So I guess the kernel is what makes it work because if I run plain AOKP and the kernel that comes with it, then it operates the same as your ROM does... internal mic works, DAC inputs do not. I install AOKP and then Timur's kernel over top of it. Not really sure if it was intended that way but its the only way I've been able to get the DAC inputs to work. I'm more than happy to do any testing you need... I'd love to see an in car useable 4.4 rom as I'm sure a lot of the other "android in car" crowd would too!
Sent from my SGH-I747 using xda app-developers app
So I've tested this a little today and DAC is working on boot every time which is awesome! One thing I did notice is if I boot with DAC and flash drive my flash drive isn't recognized until I unplug the flash drive and replug it in. Anyone else notice this?
I'll have to do more testing after my exams but just thought I'd see if anyone else has experienced this.
Sent from my Nexus 7 using xda app-developers app
Kuchar09 said:
So I've tested this a little today and DAC is working on boot every time which is awesome! One thing I did notice is if I boot with DAC and flash drive my flash drive isn't recognized until I unplug the flash drive and replug it in. Anyone else notice this?
I'll have to do more testing after my exams but just thought I'd see if anyone else has experienced this.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I noticed this too. I installed Stickmount and it seemed to work OK after that.
Sent from my SGH-I747 using xda app-developers app
Kuchar09 said:
So I've tested this a little today and DAC is working on boot every time which is awesome! One thing I did notice is if I boot with DAC and flash drive my flash drive isn't recognized until I unplug the flash drive and replug it in. Anyone else notice this?
I'll have to do more testing after my exams but just thought I'd see if anyone else has experienced this.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Hmmmm..…...does it remount for you after deep sleep?? Or do you have to replug after that too?
I guess I'll add this to the list. I'll go test this out. I think we could use the jellybean vold if it mounts on boot.
redeyedjedi said:
Hmmmm..…...does it remount for you after deep sleep?? Or do you have to replug after that too?
I guess I'll add this to the list. I'll go test this out. I think we could use the jellybean vold if it mounts on boot.
Click to expand...
Click to collapse
Haven't tried deep sleep but I just tried booting it up and it didn't show so I unplugged power for my y-charge cable let the screen turn off then reconnect power and the the flash drive showed up in the file system. So this isn't a huge issue just looks like a little something might be missing.
Sent from my Galaxy Nexus using xda app-developers app
does this kernel extend otg+charge functionality to properly sense charging after boot (exactly as plugging in a wall charger)?
I've tried several kernels and they all have the same behavior in that they do not show a charging battery, (only in the pull down notification). this makes Tasker unable to know that power is actually plugged in.
issue is described here in relation to USB Accessory Charger
http://2dindroid.wordpress.com/2013/09/01/more-notes-on-usb-otg-charging-nexus-7-2013/
http://en.wikipedia.org/wiki/USB_OTG#OTG_micro_plugs
EDIT: just realized i was linked here from the Nexus 2013 forum.. ignore the question.
This is not directly rom related but since I assume most people here are doing a fixed install I will ask here.
So during the average commute I am running waze, torque, and Spotify.
I can't seem to catch my tablet up on the charging. During the drive it just slowly goes down while (maybe 1% over a hour). I am using a startech powered USB hub with a powered otg cable going to the tablet. The power side of the otg is plugged into the hub which should provide ample power to charge the nexus.
Is it possible for the nexus to draw more than it is capable of charging? Should I be focusing on my charging selection? Anyone else having a similar issue?
Can anyone tell me an accurate way to measure the draw being used by the tablet and the charging current?
My next option is a hardwired 3amp charger with a toggle switch that will either route the power to a source that is only on when the car is running and the other side of the switch will route it directly to a lead I have coming from the battery (attempt to get ahead while I am grocery shopping or times when I am only out of the car for an hour or so.)
Sent from my SM-N900T using Tapatalk