Hi Folks!
I'm a happy owner of a Galaxy Tab 10.1, and an EE engineer who frequently uses a small USB microscope while assembling boards.
I would be really happy to be able to use my Galaxy Tab as a lightweight portable screen for this microscope. This would be much more handy than having a bulky laptop stand in there.
So I've seen that the Galaxy Tab 10.1 has USB host capabilities. And after a quick verification, I've noted that the stock kernel has the uvcvideo driver builtin (the microscope is UVC compatible, actually it's a Logitech C310 hardware with added optics).
Seems like everything is in place to make it work. However when I plug the device in, I get an unrecognized USB device message popping up.
Here's the output from dmesg:
Code:
<6>[11734.027241] Board P4 : tegra_otg_en = 1<6>[11734.037361] tegra-otg tegra-otg: SUSPEND --> HOST
<6>[11734.037391] tegra-otg tegra-otg: tegra_start_host+
<4>[11734.038884] tegra_usb_phy_open() called instance :0
<6>[11734.038966] Board P4 : tegra_usb_ldo_en=1 instance=0 present regulator=1
<4>[11734.039001] utmi_phy_power_on() called. instance : 0
<6>[11734.040244] tegra-otg tegra-otg: Acc power on detect
<6>[11734.057205] Board P4 : tegra_acc_power token : (1,1) on
<4>[11734.057234] utmi_phy_clk_enable() called. instance : 0
<6>[11734.058757] tegra-ehci tegra-ehci.0: Tegra EHCI Host Controller
<6>[11734.059016] tegra-ehci tegra-ehci.0: new USB bus registered, assigned bus number 1
<6>[11734.067158] [ CONNECTOR_DRIVER (acc_notified,387) ] ACCESSORY=OTG : STATE=online
<6>[11734.087920] tegra-ehci tegra-ehci.0: irq 52, io mem 0xc5000000
<6>[11734.107159] tegra-ehci tegra-ehci.0: USB 2.0 started, EHCI 1.00
<6>[11734.107282] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
<6>[11734.107306] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[11734.107326] usb usb1: Product: Tegra EHCI Host Controller
<6>[11734.107343] usb usb1: Manufacturer: Linux 2.6.36.3 ehci_hcd
<6>[11734.107359] usb usb1: SerialNumber: tegra-ehci.0
<6>[11734.111805] hub 1-0:1.0: 1 port detected
<6>[11734.113078] tegra-otg tegra-otg: tegra_start_host-
<6>[11734.113101] host_notify: ndev name=usb_otg: from state=2 -> to state=1
<6>[11734.327059] usb 1-1: new high speed USB device using tegra-ehci and address 2
<3>[11734.592745] usb 1-1: device v046d p081b is not supported
<6>[11734.618692] host_notify: ndev name=tegra-ehci.0: from state=0 -> to state=5
<3>[11734.620877] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11734.787068] usb 1-1: new high speed USB device using tegra-ehci and address 3
<3>[11735.040504] usb 1-1: device v046d p081b is not supported
<6>[11735.076960] host_notify: ndev name=tegra-ehci.0: from state=5 -> to state=5
<3>[11735.077029] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11735.237112] usb 1-1: new high speed USB device using tegra-ehci and address 4
<3>[11735.505766] usb 1-1: device v046d p081b is not supported
<6>[11735.528455] host_notify: ndev name=tegra-ehci.0: from state=5 -> to state=5
<3>[11735.528541] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11735.687712] usb 1-1: new high speed USB device using tegra-ehci and address 5
<3>[11735.950203] usb 1-1: device v046d p081b is not supported
<6>[11735.978040] host_notify: ndev name=tegra-ehci.0: from state=5 -> to state=5
<3>[11735.978125] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11736.137097] usb 1-1: new high speed USB device using tegra-ehci and address 6
<3>[11736.393178] usb 1-1: device v046d p081b is not supported
<6>[11736.417207] host_notify: ndev name=tegra-ehci.0: from state=5 -> to state=5
<3>[11736.419203] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11736.580821] usb 1-1: new high speed USB device using tegra-ehci and address 7
<3>[11736.840702] usb 1-1: device v046d p081b is not supported
<6>[11736.866992] host_notify: ndev name=tegra-ehci.0: from state=5 -> to state=5
<3>[11736.867057] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11737.027074] usb 1-1: new high speed USB device using tegra-ehci and address 8
<3>[11737.279441] usb 1-1: device v046d p081b is not supported
<6>[11737.306990] host_notify: ndev name=tegra-ehci.0: from state=5 -> to state=5
<3>[11737.307086] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11737.467126] usb 1-1: new high speed USB device using tegra-ehci and address 9
<3>[11737.736913] usb 1-1: device v046d p081b is not supported
<6>[11737.758513] host_notify: ndev name=tegra-ehci.0: from state=5 -> to state=5
<3>[11737.758578] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11737.916947] usb 1-1: new high speed USB device using tegra-ehci and address 10
[email protected]:/ $ dmesg
Then it goes on and on with the 'new device [...] unable to enumerate' messages until I unplug it.
The device is found, and early init seems to go through (VID/PID are correct) but it doesn't seem to make it to the uvcvideo driver (or the driver is rejecting it, I don't know).
I am not very savvy as regards to linux's USB stack (though I know my way around linux, having cross compiled it, and tweaked it several times for boards I design), so I'm a bit lost as to what I could further investigate to pinpoint the issue.
I am certain that uvcvideo is present (dmesg shows 'usbcore: registered new interface driver uvcvideo' after boot).
Things works fine when I plug in a USB flash drive.
Things works fine too when I plug the microscope to my linux desktop (through uvcvideo).
Any idea or advices would be greatly appreciated!
Thanks,
Theo
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Hi tbeauchant,
I am also looking for same , till now i didn't get any success but after going through with the code , i have seen that samsung have disable the feature of detecting a few device , in my case it says , unkown usb device and
dmesg says :: device ######(product id) ######(vendor id) not supported ,
did you get any success or any approch which you will follow.
Question: How do I get USB to Ethernet to work on webtop? I don't have wifi and AT&T's coverage sucks!
Answer:
Of course AT&T's coverage sucks! We all know this. At my work I don't have wifi, but I do have a USB port (that is linked to my university, not my work network). AT&T doesn't allow IRC over it's network, and my signal sucks (or doesn't work at all) a lot of the time, so I looked into USB-over-ethernet. Contrary to what moto says, it works. I don't know why they don't try to implement it, since it's pretty easy. You just need a bit of terminal skills.
NOTE: THIS SHOULD WORK ON OTHER MOTO-WEBTOP DEVICES AS WELL SINCE THEY ALL SHARE THE SAME LINUX BASE... SORT OF.
DISCLAIMER: IF THIS SOMEHOW BREAKS YOUR DEVICE, LEG, DOG, OR LIBIDO I AM NOT RESPONSIBLE, ALTHOUGH I'M PRETTY SURE IT WONT UNLESS YOU FUBAR IT.
I had help from Luminary(IRC)/Zxo0oxz and AR_(IRC)/ar31791on this cause I'm kind of a linux noob.
So I purchased a USB-to-Ethernet adapter: http://www.amazon.com/Plugable-Ethe.../B00484IEJS/ref=pd_cp_e_3/180-6608578-4269610 ($15). It has an ASIX AX88772 chipset in it, ASIX chipsets were the first usb-to-ethernet chipsets and they are nearly universally supported , especially on linux.
I am using the lapdock, no idea if this works with usb-otg, but you can try it if you want, but these directions won't work for you.
This guide assumes you have installed webtopmod or webtop2SD! Cause you need terminal access.
Boot to webtop, let it do it's thing. Open up LXTerminal.
Plug in your usb-toethernet device into one of the USB ports. Have it already connected to the router or whatever you are connecting it to via ethernet.
Run 'dmesg'. You should see somewhere recently a new USB device, most likely ASIX chipset. It should have a name with 'eth' in it, mine happened to be usbeth0.
Substitute DEVICENAME with what you just found it's name to be where it says DEVICENAME below.
If you run ifconfig DEVICENAME, it should print out some network related stuff if it finds your device. If it does, great, if not, well you might need to better guess the name, or it might just not be supported.
If you just run ifconfig, you won't see the device cause it is not yet active. eth0 is the atrix's wireless, if you turn wireless off it'll go away (as you can see in dmesg after you turn it off)
[Note: iwconfig doesn't exist on this distro, or it might just not be in PATH, I didn't both to look]
Assuming you found your device, if you do:
sudo ifconfig DEVICENAME up
the device should come up, and should be viewable under the command ifconfig.
Assuming you are using DHCP as a address provider, now run:
sudo dhclient DEVICENAME
and if it 'bounds' to an address, you're good to go! Turn off wifi and you should still be able to connect without AT&T's restrictions. If you make a script, this will run easily on the desktop!
I tried adding this device to webtop's interfaces file, but it ruined XFCE's bottom bar so I have to manually bring it up otherwise it breaks webtop. Also, not sure if this is related, but the wifi menu won't go away anymore either, but I haven't done too much testing.
So here's an automagic script you can paste if your configuration works the same as mine (it most likely will):
Code:
sudo ifconfig usbeth0 up
sudo dhclient usbeth0
I know it's short, but I'm a noob, and I'm sure many others are noobs too, so I hope this helps.
Your milage may vary, but I hope this helps! If it does, click thanks Also be sure to thank the people who helped me!
Additional google tags:
Webtop USB to Ethernet Droid Bionic Photon Atrix lapdock
Hello,
HERE is an easier way.
Doum
Tried that, if the device isn't plugged in at webtop boot the dock will crash(at least xfce did) . I don't use usb to ethernet all the time.
Trolling from my ATRIX 4G's XDA premium app, still on the gold medal winner of worst customer satisfaction for the second year in a row! Congrats!
It works with the stock webtop as well. You just have to use the terminal app from the phone.
Once you plug in your adapter type netcfg if you have a usbeth0 you're golden, otherwise you probably need a different adapter. I've read where the adapters Apple sells for the MacBook Air work. I know my old ass trendnet 10/100 works, but my Linksys 10/100 doesn't.
Don't have it with me (I leave it at work), but does the phone data connection work if you turn it on airplane mode? I know the phone apps didn't when i turned off my apn, but webtop apps worked. (I didn't turn off cause i want phone calls... doesn't work if in airplane mode though)
Does it work on stock 2.3.4 unrooted
Hi all,
Sorry for digging up an old thread.
As in the title -- does this work on stock a 2.3.4, unrooted, unaltered Atrix?
I have an HD dock with an adapter plugged in. dmesg lists it as AX88x72A. netcfg shows usbeth0 DOWN.
Any pointers?
Thanks
the_ek
Hello, i bought usb ethernet AX88772B chipset.
I have it connected to my HD dock, The icon that appears usb is not defined ... I write in the terminal
$dmesg
shows It ....
[ 159.568498] usb 1-1.3: Product: AX88772B
[ 159.568505] usb 1-1.3: Manufacturer: ASIX Elec. Corp.
[ 159.568512] usb 1-1.3: SerialNumber: 000001
[ 159.569545] usb 1-1.3: configuration #1 chosen from 1 choice
[ 159.654475] usb 1-1.4: new full speed USB device using tegra-ehci and address 5
[ 159.698528] usb 1-1.4: New USB device found, idVendor=046d, idProduct=c52b
[ 159.698541] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 159.698550] usb 1-1.4: Product: USB Receiver
[ 159.698557] usb 1-1.4: Manufacturer: Logitech
[ 159.699546] usb 1-1.4: configuration #1 chosen from 1 choice
[ 159.706079] input: Logitech USB Receiver as /devices/platform/tegra-ehci.0/usb1/1-1/1-1.4/1-1.4:1.0/input/input11
[ 159.711373] generic-usb 0003:046D:C52B.0002: input,hidraw1: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-tegra-ehci.0-1.4/input0
[ 159.724949] input: Logitech USB Receiver as /devices/platform/tegra-ehci.0/usb1/1-1/1-1.4/1-1.4:1.1/input/input12
[ 159.731647] generic-usb 0003:046D:C52B.0003: input,hidraw2: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-tegra-ehci.0-1.4/input1
[ 159.749265] generic-usb 0003:046D:C52B.0004: hidraw3: USB HID v1.11 Device [Logitech USB Receiver] on usb-tegra-ehci.0-1.4/input2
[ 159.835111] cpcap_usb_det cpcap_accy_whisper: ioctl cmd = 0x20000001
[ 160.774804] kxtf9_irq_work_func: status=0x4
[ 160.952127] [ 160.952130] nvmap_open: pid=2424
[ 161.680322] lm3532_webtop_brightness_set: lcd-backlight-webtop, 0x0(0), webtop=0
[ 161.681118] lm3532_webtop_brightness_set: lcd-backlight-webtop, 0x0(0), webtop=0
[ 164.634304] usb 1-1.3: USB disconnect, address 4
[ 164.907459] kxtf9_irq_work_func: status=0x4
[ 168.498157] [ 168.498160] nvmap_open: pid=2492
[ 169.891953] usb_ether_get_stats
[ 171.410448] init: untracked pid 5862 exited
[ 171.412412] init: untracked pid 5866 exited
[ 174.172841] init: untracked pid 5886 exited
[ 175.223813] init: untracked pid 5843 exited
[ 175.332466] [ 175.332469] nvmap_open: pid=5893
[ 175.593724] usb_ether_get_stats[ 175.594964] usb_ether_get_stats
[ 175.774803] init: untracked pid 5904 exited
[ 175.905551] usb_ether_get_stats
[ 175.915405] usb_ether_get_stats
[ 175.930769] usb_ether_get_stats
[ 176.131303] init: untracked pid 5849 exited
[ 176.833385] init: untracked pid 5936 exited
[ 176.966487] init: untracked pid 5932 exited
[ 177.040167] init: untracked pid 5938 exited
[ 177.050725] init: untracked pid 5934 exited
[ 177.116540] init: untracked pid 5941 exited
[ 177.579153] init: untracked pid 5952 exited
[ 177.731212] init: untracked pid 5966 exited
[ 177.906299] [ 177.906302] nvmap_open: pid=5964
[ 178.297521] nvmap_open: pid=5968
[ 178.499540] usb_ether_get_stats
[ 178.508834] init: untracked pid 5975 exited
[ 180.297833] kxtf9_misc_ioctl: SET_DELAY 200
[ 180.384618] kxtf9_misc_ioctl: SET_DELAY 200
[ 180.477737] lm3532_webtop_brightness_set: lcd-backlight-webtop, 0xf(15), webtop=0
[ 182.758270] lm3532_webtop_brightness_set: lcd-backlight-webtop, 0xf(15), webtop=1
[ 186.215847] usb_ether_get_stats
[ 192.261014] CPU0 attaching NULL sched-domain.
[ 192.261038] CPU1 attaching NULL sched-domain.
[ 192.364916] CPU0 attaching NULL sched-domain.
[ 192.365442] CPU1: clean shutdown
[ 204.847261] init: untracked pid 6113 exited
[ 213.561522] [ 213.561525] nvmap_release: pid=3622, org_pid=3622CPU1: Booted secondary processor
[ 214.474831] CPU0 attaching NULL sched-domain.
[ 214.554338] CPU0 attaching sched-domain:
[ 214.554351] domain 0: span 0-1 level CPU
[ 214.554361] groups: 0 1
[ 214.554376] CPU1 attaching sched-domain:
[ 214.554384] domain 0: span 0-1 level CPU
[ 214.554392] groups: 1 0
[ 219.098833] CPU0 attaching NULL sched-domain.
[ 219.098886] CPU1 attaching NULL sched-domain.
[ 219.214408] CPU0 attaching NULL sched-domain.
[ 219.215582] CPU1: clean shutdown
[ 236.235491] lm3532_brightness_set: lcd-backlight, 0x1c(28), webtop=1
[ 733.438025] kxtf9_irq_work_func: status=0x4
[ 733.454909] usb 1-1.3: new high speed USB device using tegra-ehci and address 6
[ 733.508607] usb 1-1.3: New USB device found, idVendor=0b95, idProduct=772b
[ 733.508653] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 733.508692] usb 1-1.3: Product: AX88772B
[ 733.508721] usb 1-1.3: Manufacturer: ASIX Elec. Corp.
[ 733.508751] usb 1-1.3: SerialNumber: 000001
[ 733.513180] usb 1-1.3: configuration #1 chosen from 1 choice
[ 774.880346] usb_ether_get_stats
[ 774.883319] [email protected]:/$
But I can't find anywhere that was eth0 ....
You solve this issue with the usb ethernet?
Might be usb_ether, Im not very good with the linux shell yet so I don't know how to look it up. Mine always showed eth0. Ill look at it more later today and post my dmesg when I get the chance.
Sent from my Motorola Atrix 4G using Tapatalk on AT&T, the company that disappoints me so much that I have to use my tapatalk signature to tell everyone
Apple Macbook Air Ethernet
Has anyone tried to use the Apple Macbook Air Ethernet adapter? I'd love to get that to work.
Mine is an AX88x72A -- not sure if the B in yours makes a difference. Mine is listed as usbeth0 in dmesg and netcfg.
the_ek said:
Mine is an AX88x72A -- not sure if the B in yours makes a difference. Mine is listed as usbeth0 in dmesg and netcfg.
Click to expand...
Click to collapse
I assumed it worked for you, yes?
Sent from my Motorola Atrix 4G using Tapatalk on AT&T, the company that disappoints me so much that I have to use my tapatalk signature to tell everyone
I followed the instructions in
http://forum.xda-developers.com/showthread.php?t=1327165
Webtop seems to work o.k. The phone browser etc. does not automatically recognize it even though netcfg shows that usbeth0 is up and connected.
the_ek said:
Mine is an AX88x72A -- not sure if the B in yours makes a difference. Mine is listed as usbeth0 in dmesg and netcfg.
Click to expand...
Click to collapse
Hi, I tried to enter usb_ether ... Nothing helps. As far as I can see there is no difference between AX88x72A and B.
Maybe it's because of the fact that I connect to the HDDock?
Sorry for not being much help. My set-up is the same (apart from the adapter) --> Atrix in HD-Dock, USB to Ethernet Adapter in USB slot, and RJ45 from there. When I first plugged the adapter into the dock and then put the Atrix in the dock, the leds in the Adapter lit up, netcfg / dmesg showed that I had connected a new device (Asix ...), but that usbeth0 was down. After following the instructions I linked in post 12 above, netcfg showed that usbeth0 was up and had an IP address. Webtop, phone browser, market seem to be working o.k. (phone browser did not work at first, but did after a while).
the_ek said:
Sorry for not being much help. My set-up is the same (apart from the adapter) --> Atrix in HD-Dock, USB to Ethernet Adapter in USB slot, and RJ45 from there. When I first plugged the adapter into the dock and then put the Atrix in the dock, the leds in the Adapter lit up, netcfg / dmesg showed that I had connected a new device (Asix ...), but that usbeth0 was down. After following the instructions I linked in post 12 above, netcfg showed that usbeth0 was up and had an IP address. Webtop, phone browser, market seem to be working o.k. (phone browser did not work at first, but did after a while).
Click to expand...
Click to collapse
Hi,
what's your adapter ? ASIX AX88772 A or B ????????
As stated in posts 6, 10, 11, and the one you quoted yourself in post 13 --> it is an ASIX AX88x72 A
the_ek said:
As stated in posts 6, 10, 11, and the one you quoted yourself in post 13 --> it is an ASIX AX88x72 A
Click to expand...
Click to collapse
Hi,
I will buy third...and i will be collector
@praded2007
Did you get it to work?
Testing out CM7. Not sure if I like it over stock. Miss webtop and real fingerprint scannner...
Sent from my Motorola Atrix 4G using Tapatalk on AT&T, the company that disappoints me so much that I have to use my tapatalk signature to tell everyone
Just in case anyone is interested. The usb ethernet adapter also works via otg cable and hub.
Hello,
I tested with three different REDMI 3 devices and three different rom versions and have the following problem:
initially everything with connecting an external usb camera was ok. My usb camera app received events asking for permissions for using usb camera. But after 3 or 4 full charges the app stopped receiving permissions. I checked with couple other apps but again no permission. If my battery drops under 60% suddenly everything is ok again and the app detects the camera. It is stranger, that before full detect of the camera the app starts some kind of permission loop. I click allow and after 2 seconds the permission dialog shows again and so on... I checked the source code and appears my USBManager returns empty device list. For me it looks like some kind of battery optimizer or usb state optimizer doing it. I will be more than happy if someone can help me with this issue. Additionally I checked with all other stock rom version. It is all the same.
Here is some log from dmsg.
Code:
<6>[12449.627983] msm_otg 78d9000.usb: USB exited from low power mode
<6>[12449.647323] psy->name:usb
<6>[12449.652992] XXX::smb358_get_prop_batt_status:reg=0x0
<12>[12449.653558] healthd: battery l=94 v=4240 t=22.3 h=2 st=4 c=382 chg=
<6>[12449.744320] msm_hsusb_host msm_hsusb_host: EHCI Host Controller
<6>[12449.744844] msm_hsusb_host msm_hsusb_host: new USB bus registered, assigned bus number 1
<6>[12449.751356] msm_hsusb_host msm_hsusb_host: irq 166, io mem 0x078d9000
<6>[12449.769480] msm_hsusb_host msm_hsusb_host: USB 2.0 started, EHCI 1.00
<6>[12449.769624] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
<6>[12449.769636] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[12449.769646] usb usb1: Product: EHCI Host Controller
<6>[12449.769656] usb usb1: Manufacturer: Linux 3.10.49-perf-g48b885e ehci_hcd
<6>[12449.769665] usb usb1: SerialNumber: msm_hsusb_host
<6>[12449.772688] hub 1-0:1.0: USB hub found
<6>[12449.772729] hub 1-0:1.0: 1 port detected
<6>[12449.876761] msm_otg 78d9000.usb: USB in low power mode
<6>[12450.296922] msm_otg 78d9000.usb: USB exited from low power mode
<6>[12450.519306] usb 1-1: new high-speed USB device number 2 using msm_hsusb_host
<6>[12450.949089] usb 1-1: new high-speed USB device number 3 using msm_hsusb_host
<6>[12451.619450] usb 1-1: new high-speed USB device number 5 using msm_hsusb_host
<11>[12452.316729] init: Warning! Service eyecare needs a SELinux domain defined; please fix!
<11>[12453.339456] init: Warning! Service coloradjust needs a SELinux domain defined; please fix!
<6>[12453.759449] usb 1-1: new high-speed USB device number 13 using msm_hsusb_host
<6>[12455.879543] usb 1-1: new high-speed USB device number 21 using msm_hsusb_host
<6>[12456.212015] XXX::smb358_get_prop_batt_status:reg=0x0
<6>[12456.216663] psy->name:rk-bat
<6>[12456.216678] status=3, percent=94
<6>[12456.216684] status=3, percent=94
<6>[12456.222182] XXX::smb358_get_prop_batt_status:reg=0x0
<12>[12456.222723] healthd: battery l=94 v=4248 t=22.4 h=2 st=4 c=401 chg=
<6>[12456.319281] usb 1-1: new high-speed USB device number 22 using msm_hsusb_host
<11>[12457.382047] init: Warning! Service eyecare needs a SELinux domain defined; please fix!
<6>[12457.499222] usb 1-1: new high-speed USB device number 26 using msm_hsusb_host
<11>[12458.407239] init: Warning! Service coloradjust needs a SELinux domain defined; please fix!
<6>[12458.899381] usb 1-1: new high-speed USB device number 31 using msm_hsusb_host
<6>[12459.339269] usb 1-1: new high-speed USB device number 32 using msm_hsusb_host
Im now at tampered rom (the rom says miui global 7.1 | 7.1.1.0.0 stable) it not real global rom! gold colour. but i dont have any problem with otg or battery drops. All working fine. Except a few settings turns back to default if i reset the device. But its doesnt bothered me much.
Dear all
i'm trying to enable rndis communication between a tablet running Android 4.4.2 KOT49H rooted.
in the setting menu i'm not able to find any tethering option, so i've uploaded the script usb_tether_start.sh found here:
https://forum.xda-developers.com/showthread.php?t=2127850
After the start of the service, on andorid side i see that the rndis0 device is created and is up:
13: rndis0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether a2:63:00:89:3d:46 brd ff:ff:ff:ff:ff:ff
inet 192.168.2.1/24 scope global rndis0
inet6 fe80::a063:ff:fe89:3d46/64 scope link
valid_lft forever preferred_lft forever
Click to expand...
Click to collapse
On the laptop side (running ubunto 14.0.4 LTS) the device is created too
dmes:
[ 8643.359537] usb 3-1: new high-speed USB device number 10 using xhci_hcd
[ 8643.495555] usb 3-1: New USB device found, idVendor=10d6, idProduct=4d02
[ 8643.495564] usb 3-1: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 8643.495568] usb 3-1: Product: P706
[ 8643.495571] usb 3-1: Manufacturer: P706
[ 8643.495575] usb 3-1: SerialNumber: A03B610405C78BB9
[ 8643.512630] rndis_host 3-1:1.0 usb0: register 'rndis_host' at usb-0000:45:00.0-1, RNDIS device, 32:ff:48:ea:0c:df
Click to expand...
Click to collapse
and ifconfig usb0 reports the device:
# ifconfig usb0
usb0 Link encap:Ethernet IndirizzoHW 32:ff:48:ea:0c:df
indirizzo inet:192.168.2.3 Bcast:192.168.2.255 Maschera:255.255.255.0
indirizzo inet6: fe80::30ff:48ff:feea:cdf/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:12 errors:0 dropped:0 overruns:0 frame:0
TX packets:252 errors:0 dropped:0 overruns:0 carrier:0
collisioni:0 txqueuelen:1000
Byte RX:552 (552.0 B) Byte TX:40689 (40.6 KB)
Click to expand...
Click to collapse
I also see some TX/RX bytes but the ping or any other kind of communication between the laptop and the tablet isnt' working, i've tried both static ip configuration and request via dhcp client on laptop side (the dhcp request on the laptop hangs...)
Any idea or help?
Thanks to all in advance
Hello guys,
I am trying to bring back to life a dead Vivo 1901 (V15) phone using SP Flash Tools v5.2036. The Firmware I am using comes in a file named, "Vivo_Y15_PD1901BF_MT6765_EX_A_1.12.4_11062019_(by_vivofirmware.com)",
which also provides MT6765 scatter file.
The auth file, scatter file and DA file that I am using for flashing is attached with this post. Upon selecting these files and flashing ( first tried with download only, then using format all + download, but results are same), I the following messages appear in the output of the tool.
Code:
$ sudo sh flash_tool.sh
[sudo] password for sarkar4540:
sysname:Linux
nodename:sarkar4540-X556UQK
release:5.4.0-49-generic
version:#53~18.04.1-Ubuntu SMP Mon Sep 21 14:12:39 UTC 2020
machine:x86_64
domainame:(none)
cur_kernel_version = 5.4.0
QObject::moveToThread: Cannot move objects with a parent
support_dl_cert_to_storage: 0
Application asked to unregister timer 0xc00001b which is not registered in this thread. Fix application.
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0
add@/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2
[email protected]/module/cdc_acm
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/tty/ttyACM0
vid is 0e8d
device vid = 0e8d
pid is 0003
device pid = 0003
com portName is: /dev/ttyACM0
Total wait time = -1601887002.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
BROM connected
Downloading & Connecting to DA...
connect DA end stage: 2, enable DRAM in 1st DA: 0
Failed to Connect DA: STATUS_SHUTDOWN_CMD_EXCEPTION(-1073414142)
Disconnect!
BROM Exception! ( ERROR : STATUS_SHUTDOWN_CMD_EXCEPTION (-1073414142) , MSP ERROE CODE : 0x00.
[HINT]:
)((ConnectDA,../../../flashtool/Conn/Connection.cpp,149))
Following are the outputs of various commands in the system I am using.
Code:
$ uname -a
Linux sarkar4540-X556UQK 5.4.0-49-generic #53~18.04.1-Ubuntu SMP Mon Sep 21 14:12:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Code:
$ dmesg
.
.
.
[ 324.046688] usb 1-2: new high-speed USB device number 5 using xhci_hcd
[ 324.195603] usb 1-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 324.195605] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 324.248243] cdc_acm 1-2:1.0: ttyACM0: USB ACM device
[ 324.249509] usbcore: registered new interface driver cdc_acm
[ 324.249510] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 324.275093] usbcore: registered new interface driver usbserial_generic
[ 324.275106] usbserial: USB Serial support registered for generic
[ 324.300238] usbcore: registered new interface driver option
[ 324.300261] usbserial: USB Serial support registered for GSM modem (1-port)
I request you guys to please show me where to head. I shall always be grateful to you if you can help me out of this misery.
Regards,
A. Sarkar