[Q] Help! Touch screen not working - Galaxy Tab 10.1 Q&A, Help & Troubleshooting

I''ve apparently broken my Galaxy Tab.
It's a GT-P7510. Galaxy Tab 10.1 WiFi only.
It doesn't respond to any screen input. I've done a bunch of things to try to resolve this with no solution.
The relevant info from the startup ("dmesg" output) is:
<7>[ 1.706171] maXTouch driver
<7>[ 1.706409] "sec_touch"
<7>[ 1.706571] addr: 0x004c
<7>[ 1.706735] irq: 220
<7>[ 1.706895] flags: 0x0000
<7>[ 1.707125] adapter:"Tegra I2C adapter"
<7>[ 1.707290] device: "(null)"
<4>[ 1.707677] tegra-i2c tegra-i2c.1: I2c error status 0x00000008
<4>[ 1.707913] tegra-i2c tegra-i2c.1: no acknowledge from address 0x4c
<4>[ 1.708080] tegra-i2c tegra-i2c.1: Packet status 0x00010009
<7>[ 1.709363] Warning: To wake up touch-ic in deep sleep, retry i2c communication!
<4>[ 1.748037] tegra-i2c tegra-i2c.1: I2c error status 0x00000008
<4>[ 1.748355] tegra-i2c tegra-i2c.1: no acknowledge from address 0x4c
<4>[ 1.748523] tegra-i2c tegra-i2c.1: Packet status 0x00010009
<3>[ 1.749788] sec_touch 1-004c: Failure accessing maXTouch device
<3>[ 1.750031] sec_touch 1-004c: Chip could not be identified
<6>[ 1.750199] p3_touch_exit_hw
So, it can't see the touchscreen driver, so no screen input. Can't unlock, can't do much of anything.
I've factory reset. Cleared everything. Installed CM10. Opened it up and disconnected the battery for 15 minutes. Nothing works.
Something (probably triggered from reading every file on the device due to a "find" shell command), has wedged the touchscreen interface.
Are there any tools I can use to probe the Tegra/i2c interface to find out what's happened? Or reset everything?
It's almost bricked,but not quite. Will an older or newer kernel wake up the touchscreen?

k1mu said:
I''ve apparently broken my Galaxy Tab.
It's a GT-P7510. Galaxy Tab 10.1 WiFi only.
It doesn't respond to any screen input. I've done a bunch of things to try to resolve this with no solution.
The relevant info from the startup ("dmesg" output) is:
[ 1.706171] maXTouch driver
[ 1.706409] "sec_touch"
[ 1.706571] addr: 0x004c
[ 1.706735] irq: 220
[ 1.706895] flags: 0x0000
[ 1.707125] adapter:"Tegra I2C adapter"
[ 1.707290] device: "(null)"
[ 1.707677] tegra-i2c tegra-i2c.1: I2c error status 0x00000008
[ 1.707913] tegra-i2c tegra-i2c.1: no acknowledge from address 0x4c
[ 1.708080] tegra-i2c tegra-i2c.1: Packet status 0x00010009
[ 1.709363] Warning: To wake up touch-ic in deep sleep, retry i2c communication!
[ 1.748037] tegra-i2c tegra-i2c.1: I2c error status 0x00000008
[ 1.748355] tegra-i2c tegra-i2c.1: no acknowledge from address 0x4c
[ 1.748523] tegra-i2c tegra-i2c.1: Packet status 0x00010009
[ 1.749788] sec_touch 1-004c: Failure accessing maXTouch device
[ 1.750031] sec_touch 1-004c: Chip could not be identified
[ 1.750199] p3_touch_exit_hw
So, it can't see the touchscreen driver, so no screen input. Can't unlock, can't do much of anything.
I've factory reset. Cleared everything. Installed CM10. Opened it up and disconnected the battery for 15 minutes. Nothing works.
Something (probably triggered from reading every file on the device due to a "find" shell command), has wedged the touchscreen interface.
Are there any tools I can use to probe the Tegra/i2c interface to find out what's happened? Or reset everything?
It's almost bricked,but not quite. Will an older or newer kernel wake up the touchscreen?
Click to expand...
Click to collapse
U can try to go back to stock using Odin and in the mean while also whipping all data this way it should make sure that no corrupt data is left
Sent from my GT-P7510 using XDA Premium HD app
---------- Post added at 10:23 PM ---------- Previous post was at 10:22 PM ----------
k1mu said:
I''ve apparently broken my Galaxy Tab.
It's a GT-P7510. Galaxy Tab 10.1 WiFi only.
It doesn't respond to any screen input. I've done a bunch of things to try to resolve this with no solution.
The relevant info from the startup ("dmesg" output) is:
<7>[ 1.706171] maXTouch driver
<7>[ 1.706409] "sec_touch"
<7>[ 1.706571] addr: 0x004c
<7>[ 1.706735] irq: 220
<7>[ 1.706895] flags: 0x0000
<7>[ 1.707125] adapter:"Tegra I2C adapter"
<7>[ 1.707290] device: "(null)"
<4>[ 1.707677] tegra-i2c tegra-i2c.1: I2c error status 0x00000008
<4>[ 1.707913] tegra-i2c tegra-i2c.1: no acknowledge from address 0x4c
<4>[ 1.708080] tegra-i2c tegra-i2c.1: Packet status 0x00010009
<7>[ 1.709363] Warning: To wake up touch-ic in deep sleep, retry i2c communication!
<4>[ 1.748037] tegra-i2c tegra-i2c.1: I2c error status 0x00000008
<4>[ 1.748355] tegra-i2c tegra-i2c.1: no acknowledge from address 0x4c
<4>[ 1.748523] tegra-i2c tegra-i2c.1: Packet status 0x00010009
<3>[ 1.749788] sec_touch 1-004c: Failure accessing maXTouch device
<3>[ 1.750031] sec_touch 1-004c: Chip could not be identified
<6>[ 1.750199] p3_touch_exit_hw
So, it can't see the touchscreen driver, so no screen input. Can't unlock, can't do much of anything.
I've factory reset. Cleared everything. Installed CM10. Opened it up and disconnected the battery for 15 minutes. Nothing works.
Something (probably triggered from reading every file on the device due to a "find" shell command), has wedged the touchscreen interface.
Are there any tools I can use to probe the Tegra/i2c interface to find out what's happened? Or reset everything?
It's almost bricked,but not quite. Will an older or newer kernel wake up the touchscreen?
Click to expand...
Click to collapse
U can try to go back to stock using Odin and in the mean while also whipping all data this way it should make sure that no corrupt data is left
Sent from my GT-P7510 using XDA Premium HD app

wtgserpant said:
U can try to go back to stock using Odin and in the mean while also whipping all data this way it should make sure that no corrupt data is left
Click to expand...
Click to collapse
I've tried that - wiped data/cache/dalvik and re-installed using Odin with no improvement. I'm currently trying to restore a nandroid made under Honeycomb but I doubt that's going to fix it either.
(edit: yep. still no touchscreen input. Nice HC lockscreen, can't enter the PIN.)

Searching using mxt1386 finds the cause of this problem. http://forum.xda-developers.com/showthread.php?t=1252829
If you read certain files in the /sys/devices directory tree, you corrupt the state of the touchscreen controller. Until you write the configuration to reset it, the touchscreen controller will be stuck in a state where the kernel refuses to initialize it. Based on the thread above, it's likely a fix to the maXTouch driver can recover from this problem. I'm going to have to learn how to build kernels and do some testing.

Sorry to keep replying to myself on this, but I have it figured out and have a fix. My gtab is now happily accepting touchpad input.
I'll post details over in the thread mentioned above, but it's a modification to the kernel that repairs the wayward touchscreen controller.

k1mu said:
Sorry to keep replying to myself on this, but I have it figured out and have a fix. My gtab is now happily accepting touchpad input.
I'll post details over in the thread mentioned above, but it's a modification to the kernel that repairs the wayward touchscreen controller.
Click to expand...
Click to collapse
can u do this kernel package fo a i957?
do u think changing the touch screen would solve the prob

jamracer said:
can u do this kernel package fo a i957?
do u think changing the touch screen would solve the prob
Click to expand...
Click to collapse
If the i957 uses the same tegra chip as the Tab 10.1 it's very likely fixable. The way to tell is to look at the dmesg output immediately after startup adb shell dmesg >dmes.txt
then edit dmesg.txt. If you see the "no acknowledge" error, then the same fix is likely to work:
<4>[ 1.707677] tegra-i2c tegra-i2c.1: I2c error status 0x00000008
<4>[ 1.707913] tegra-i2c tegra-i2c.1: no acknowledge from address 0x4c
<4>[ 1.708080] tegra-i2c tegra-i2c.1: Packet status 0x00010009
<7>[ 1.709363] Warning: To wake up touch-ic in deep sleep, retry i2c communication!
Click to expand...
Click to collapse
As far as changing the touch screen: no, that won't help. The touchscreen controller chip is on the main board, which means that changing the touchscreen itself won't help. You've got to kick the chip back to life by feeding it the proper firmware.

k1mu said:
If the i957 uses the same tegra chip as the Tab 10.1 it's very likely fixable. The way to tell is to look at the dmesg output immediately after startup adb shell dmesg >dmes.txt
then edit dmesg.txt. If you see the "no acknowledge" error, then the same fix is likely to work:
As far as changing the touch screen: no, that won't help. The touchscreen controller chip is on the main board, which means that changing the touchscreen itself won't help. You've got to kick the chip back to life by feeding it the proper firmware.
Click to expand...
Click to collapse
I get what
u say but, I tried s freezer method n after 5 mins in d touch started to work but just for a few mins

k1mu said:
If the i957 uses the same tegra chip as the Tab 10.1 it's very likely fixable. The way to tell is to look at the dmesg output immediately after startup adb shell dmesg >dmes.txt
then edit dmesg.txt. If you see the "no acknowledge" error, then the same fix is likely to work:
As far as changing the touch screen: no, that won't help. The touchscreen controller chip is on the main board, which means that changing the touchscreen itself won't help. You've got to kick the chip back to life by feeding it the proper firmware.
Click to expand...
Click to collapse
how or where can i get the proper firmware to fix this prob?

jamracer said:
I get what
u say but, I tried s freezer method n after 5 mins in d touch started to work but just for a few mins
Click to expand...
Click to collapse
Ok, so you've got a hardware problem. The fix I've come up with is to recover the touchscreen controller when it gets stuck in firmware update mode, which is clearly not what you're seeing. Time to return the tablet to Samsung for repair, I suspect.

jamracer said:
how or where can i get the proper firmware to fix this prob?
Click to expand...
Click to collapse
The firmware binary is distributed with the Linux kernel. For the Tegra, it's in drivers/input/touchscreen/mxt1386_fw_ver10.h - the prior release is mxt1386_fw_ver09.h.

my gtab gt-p7500 touch screen not responding
k1mu said:
Sorry to keep replying to myself on this, but I have it figured out and have a fix. My gtab is now happily accepting touchpad input.
I'll post details over in the thread mentioned above, but it's a modification to the kernel that repairs the wayward touchscreen controller.
Click to expand...
Click to collapse
please need help my gtab gt-p7500 touch screen stop working, l have change the digitizer and everything i cant get it to work, please if anyone has a solution kindly post it and help me

tofeek1 said:
please need help my gtab gt-p7500 touch screen stop working, l have change the digitizer and everything i cant get it to work, please if anyone has a solution kindly post it and help me
Click to expand...
Click to collapse
The kernel that I posted in the other thread *should* work for your 7500, at least to fix the touchscreen. You'll need to re-flash a stock kernel to get 3G back afterwards.
Also, The A1 kernel already has the fix incorporated. Go to the Galaxy Tab 8.9 Android Development forum, find the A1 kernel, and install it on your tab. That should fix it for you.

my p7500 screen touch not working
k1mu said:
The kernel that I posted in the other thread *should* work for your 7500, at least to fix the touchscreen. You'll need to re-flash a stock kernel to get 3G back afterwards.
Also, The A1 kernel already has the fix incorporated. Go to the Galaxy Tab 8.9 Android Development forum, find the A1 kernel, and install it on your tab. That should fix it for you.
Click to expand...
Click to collapse
i downloaded the A1 kernel for p7500 3G tab since the tab is not functioning i tried flashing the kernel with odin but seems odin could not recognize the files since the files is not md5,tar, img please i need a help

Related

Let's get the new HC update working on the HC updated WiFi flyers

So, it seems that there are a bunch of Flyers out there ('Best Buy Flyers') that are on the original HC update and can't roll back to their original Gingerbread release because there's no RUU. I want to understand what we can do for these users and help if I can.
For users in this situation, I have a couple of questions...
- Have you tried installing the new HC version from ClockworkMod (without radio / hboot) from here - http://www.filesonic.com/file/2895621975/stock-hc-flyer-system-3.41.405.1.zip ?
- If so, does it boot?
- What happens when you try to roll back to a Gingerbread RUU using a Goldcard?
If the new HC leak doesn't work after flashing via ClockworkMod, we might be able to make a 'hybrid' that will work... let me know.
P
Paul:
I have not done this myself, but one BB Wifi owner that is on the original leak reported that he flashed just the new system image and it boots and runs, but he cannot turn on wifi.
DigitalMD said:
Paul:
I have not done this myself, but one BB Wifi owner that is on the original leak reported that he flashed just the new system image and it boots and runs, but he cannot turn on wifi.
Click to expand...
Click to collapse
Here is that thread
http://forum.xda-developers.com/showthread.php?t=1329834
Before I went to HC with my wifi Flyer, I upgraded to GB 2.27. So in theory, shouldn't that RUU work for me?
I finally have enough posts to post here!
This is what I have done so far:
1. I started with my Best Buy Wifi Flyer running the first Honeycomb leak. This was accomplished using Paul's standard procedure.
2. I flashed the system zip in recovery. This boots. One time, I cleared the cache, etc. The first time I did not. In both cases, the Flyer boots into the new HC leak. Most things seem fine with two exceptions - No Wifi and I have issues restarting/shutting down.
Wifi - Under the Wifi settings it simply says "error"
Restart - Whe I press the power button the restart/shutdown menu pops up. But, the Flyer will not restart/shutdown. Instead, the Flyer freaks out a little and becomes partially unresponsive. I have to manually restart.
3. Gold Card - I have not tried this because I thought it does not work.
4. Radio Image Flash - Since Wifi does not work, I thought that I could flash the radio image. I can't. Revolutionary does not work with my Hboot version and as a result, no flashign is possible.
I am open to suggestions.
lawguy said:
I finally have enough posts to post here!
This is what I have done so far:
1. I started with my Best Buy Wifi Flyer running the first Honeycomb leak. This was accomplished using Paul's standard procedure.
2. I flashed the system zip in recovery. This boots. One time, I cleared the cache, etc. The first time I did not. In both cases, the Flyer boots into the new HC leak. Most things seem fine with two exceptions - No Wifi and I have issues restarting/shutting down.
Wifi - Under the Wifi settings it simply says "error"
Restart - Whe I press the power button the restart/shutdown menu pops up. But, the Flyer will not restart/shutdown. Instead, the Flyer freaks out a little and becomes partially unresponsive. I have to manually restart.
3. Gold Card - I have not tried this because I thought it does not work.
4. Radio Image Flash - Since Wifi does not work, I thought that I could flash the radio image. I can't. Revolutionary does not work with my Hboot version and as a result, no flashign is possible.
I am open to suggestions.
Click to expand...
Click to collapse
Have you or can you flash the kernel for the new leak? This is just a guess but it may be the cause of the wifi error
OK, so WiFi not starting is a nice simple module mismatch at a guess.
Boot the flyer, remount ('adb remount') then unzip and push this module to /system/lib/modules - http://www.filesonic.com/file/2948892275/flyer-leak1modules.zip
P
And it's Paul for the win...
{+1 for the missing kernel module idea. I've run into that working on ports on other devices. I've also had to try different versions of wpa_supplicant as well ( again on other devices ) I have the BB Flyer, currently running the FlyHoney rom quite happily, but I'm always willing to wipe / flush ( er, flash ) for the good of the community. Won't have time until after the day job though... If there is anyone who could post the logcat output while trying to turn the wifi on, that might speed things along a bit.}
paulobrien said:
OK, so WiFi not starting is a nice simple module mismatch at a guess.
Boot the flyer, remount ('adb remount') then unzip and push this module to /system/lib/modules - http://www.filesonic.com/file/2948892275/flyer-leak1modules.zip
P
Click to expand...
Click to collapse
Couldn't you just unzip and copy over using root explorer set permissions and reboot?
I'll give this suggestion a try tonight. I am at work all day. It is still 9 in the morning here.
If anyone has others, I'll try those too.
---------- Post added at 02:38 PM ---------- Previous post was at 02:36 PM ----------
mcord11758 said:
Have you or can you flash the kernel for the new leak? This is just a guess but it may be the cause of the wifi error
Click to expand...
Click to collapse
I have not tried this. My plan was to flash the radio and then try all the others if that did not work. I gave up when I could not flash the radio.
I have wifi working- flash boot.img via fastboot then boot into recovery via fastboot, and flash system zip wifi is working have not tried restarting yet...
now power off or restart problems flashing boot.img via fastboot for those who already flashed system via CWM should fix all issues! WE HAVE 3.2.1, we just don't have update hboot or radio. or root yet... Never mind installed super user and was granted Root Access! Awesome much more responsive than all the prior HC builds and I tried every single one.
Thanks Paul!
timtucker said:
And it's Paul for the win...
{+1 for the missing kernel module idea. I've run into that working on ports on other devices. I've also had to try different versions of wpa_supplicant as well ( again on other devices ) I have the BB Flyer, currently running the FlyHoney rom quite happily, but I'm always willing to wipe / flush ( er, flash ) for the good of the community. Won't have time until after the day job though... If there is anyone who could post the logcat output while trying to turn the wifi on, that might speed things along a bit.}
Click to expand...
Click to collapse
Code:
11/03/2011 09:41:48 [INFORMATION] [WLAN] wifi_set_power = 1
11/03/2011 09:41:48 [INFORMATION] flyer_wifi_power: 1
11/03/2011 09:41:48 [INFORMATION] [WLAN] wifi_set_carddetect = 1
11/03/2011 09:41:48 [INFORMATION] flyer_wifi_set_carddetect: 1
11/03/2011 09:41:48 [DEBUG] mmc1: card_present 1
11/03/2011 09:41:48 [INFORMATION] mmc1: Slot status change detected (0 -> 1)
11/03/2011 09:41:48 [INFORMATION] [WLAN] Dongle Host Driver, version 4.218.204.2
11/03/2011 09:41:49 [WARNING] [BATT] [x0]3 [x8]d c0 7f f0 69 50 f3 ec 29 d0
11/03/2011 09:41:49 [WARNING] [BATT]battery.id_ohm=614753300, battery.id_index=2, batt_id_index=2, st_counter=0
11/03/2011 09:41:49 [WARNING] [BATT] V=4111(695) I=-305(fffffcfb) C=3734.0/3850(29d0) id=2(7fe) T=320(dc) KADC=100
11/03/2011 09:41:49 [INFORMATION] [BATT] ID=2, level=97, vol=4111, temp=320, curr=-305, chg_src=1, chg_en=1
11/03/2011 09:41:49 [INFORMATION] [BATT] htc_battery_update_change() power_supply_changed: battery
11/03/2011 09:41:49 [WARNING] [BATT]S=3 P=970 chg=1 cable=100 flg=1100 dbg=0000 fst_dischg=990/3848 [1783545188]
11/03/2011 09:41:51 [DEBUG] mmc1: queuing CIS tuple 0x91 length 3
11/03/2011 09:41:51 [INFORMATION] mmc1: new high speed SDIO card at address 0001
11/03/2011 09:41:51 [INFORMATION] [WLAN] DHD: dongle ram size is set to 294912(orig 294912)
11/03/2011 09:41:51 [INFORMATION] [WLAN] irq: 275
11/03/2011 09:41:51 [INFORMATION] [WLAN] firmware version: wl0: Aug 2 2010 16:45:25 version 4.218.207.0
11/03/2011 09:41:51 [INFORMATION] [WLAN] dhd_preinit_ioctls:str=0x6e756c6c207061636b657400
11/03/2011 09:41:51 [INFORMATION] [WLAN] eth0: Broadcom Dongle Host Driver mac=64:a7:69:ed:79:e7
11/03/2011 09:41:51 [INFORMATION] [WLAN] enter dhd_set_multicast_list
11/03/2011 09:41:51 [INFORMATION] [WLAN] enter dhd_set_multicast_list
11/03/2011 09:41:51 [INFORMATION] [WLAN] enter dhd_set_multicast_list
11/03/2011 09:41:51 [INFORMATION] [ATS][press_widget][launch]
11/03/2011 09:41:51 [WARNING] [WLAN][WRN] wl_iw_set_country: scan in progress, retry 1!
11/03/2011 09:41:52 [INFORMATION] [WLAN] Send Event ISCAN complete
11/03/2011 09:41:52 [INFORMATION] [WLAN] disassoc client!
11/03/2011 09:41:52 [INFORMATION] [WLAN] wl_iw_iscan_get_scan return to WE 1093 bytes APs=6
11/03/2011 09:41:53 [INFORMATION] [WLAN] wl_iw_iscan_get_scan return to WE 1093 bytes APs=6
11/03/2011 09:41:53 [INFORMATION] [WLAN] pfn: set ssid = xxxxxxxx
11/03/2011 09:41:53 [INFORMATION] [WLAN] lightest is 0, weightest is 0, samessid = 65535
11/03/2011 09:41:53 [INFORMATION] [WLAN] power active. usb_type:1
11/03/2011 09:41:53 [INFORMATION] [WLAN] power active. usb_type:1
11/03/2011 09:41:53 [INFORMATION] [WLAN] Enter set packet filter
11/03/2011 09:41:53 [INFORMATION] [WLAN] start to add pkt filter 100
11/03/2011 09:41:53 [INFORMATION] [WLAN] RXFILTER-ADD MULTICAST filter
11/03/2011 09:41:53 [INFORMATION] [WLAN] Enter set packet filter
11/03/2011 09:41:53 [INFORMATION] [WLAN] start to add pkt filter 104
11/03/2011 09:41:53 [INFORMATION] [WLAN] Enter set packet filter
11/03/2011 09:41:53 [INFORMATION] [WLAN] start to add pkt filter 102
11/03/2011 09:41:53 [INFORMATION] [WLAN] Enter set packet filter
11/03/2011 09:41:53 [INFORMATION] [WLAN] start to add pkt filter 100
11/03/2011 09:41:53 [INFORMATION] [WLAN] RXFILTER-ADD MULTICAST filter
11/03/2011 09:41:53 [INFORMATION] [WLAN] Enter set packet filter
11/03/2011 09:41:53 [INFORMATION] [WLAN] start to add pkt filter 104
11/03/2011 09:41:53 [INFORMATION] [WLAN] Enter set packet filter
11/03/2011 09:41:53 [INFORMATION] [WLAN] start to add pkt filter 102
11/03/2011 09:41:53 [INFORMATION] [WLAN] iscan retry!
11/03/2011 09:41:53 [INFORMATION] [WLAN] iscan retry!
11/03/2011 09:41:54 [INFORMATION] [WLAN] wake lock 15 secs!
11/03/2011 09:41:54 [INFORMATION] [WLAN] Link UP
11/03/2011 09:41:54 [INFORMATION] [WLAN] STA connect received 1
11/03/2011 09:41:54 [INFORMATION] [WLAN] getpower: and_pm = 1, dhd_pm: 0, ctrl_mask: 0x0, usb_act: 1
11/03/2011 09:41:54 [INFORMATION]
11/03/2011 09:41:55 [INFORMATION] [WLAN] Send Event ISCAN complete
11/03/2011 09:41:55 [INFORMATION] [WLAN] wl_iw_iscan_get_scan return to WE 921 bytes APs=5
11/03/2011 09:42:02 [DEBUG] eth0: no IPv6 routers present
paulobrien said:
OK, so WiFi not starting is a nice simple module mismatch at a guess.
Boot the flyer, remount ('adb remount') then unzip and push this module to /system/lib/modules - http://www.filesonic.com/file/2948892275/flyer-leak1modules.zip
P
Click to expand...
Click to collapse
So with my US BB Flyer, I performed the suggested steps and all seems to be well so far, I have working wifi and a working HC (Updated beta install) this with the same radio, boot, recovery and other components form the origional HC leak. (i should note that I was running the FlyHoney HC rom, not the stock version) I will post any additional observations here. (these may be limited for as I am at work, did this on my lunch)
Cheers
BR
---------- Post added at 10:22 AM ---------- Previous post was at 10:14 AM ----------
tech247 said:
I have wifi working- flash boot.img via fastboot then boot into recovery via fastboot, and flash system zip wifi is working have not tried restarting yet...
now power off or restart problems flashing boot.img via fastboot for those who already flashed system via CWM should fix all issues! WE HAVE 3.2.1, we just don't have update hboot or radio. or root yet...
Click to expand...
Click to collapse
Not sure about your Flyer, I have root (or at least looks like I have root) root explorer asked and was granted root priv..
Cheers
BR
Great news! Thanks guys.
Brau0303 said:
So with my US BB Flyer, I performed the suggested steps and all seems to be well so far, I have working wifi and a working HC (Updated beta install) this with the same radio, boot, recovery and other components form the origional HC leak. (i should note that I was running the FlyHoney HC rom, not the stock version) I will post any additional observations here. (these may be limited for as I am at work, did this on my lunch)
Cheers
BR
---------- Post added at 10:22 AM ---------- Previous post was at 10:14 AM ----------
Not sure about your Flyer, I have root (or at least looks like I have root) root explorer asked and was granted root priv..
Cheers
BR
Click to expand...
Click to collapse
I'll have to give this a try on my lunch break too.
Are these instructions needed to be modded?
CWM Recovery method
>Run backup
>Wiped data and caches
>Flash Honeycomb system image zip file from MoDaCo
>Boot and remount ('adb remount') then unzip bcm4329.ko from .zip provided by Paul and push module to /system/lib/modules
Great news! Thanks everybody! Gonna try this
Sent from my HTC Flyer P510e using xda premium
lpasq said:
I'll have to give this a try on my lunch break too.
Are these instructions needed to be modded?
CWM Recovery method
>Run backup
>Wiped data and caches
>Flash Honeycomb system image zip file from MoDaCo
>Boot and remount ('adb remount') then unzip bcm4329.ko from .zip provided by Paul and push module to /system/lib/modules
Click to expand...
Click to collapse
Yup, That would be it.
Cheers
BR
Awesome, will give this a go tomorrow
Sent from my ADR6400L using xda premium
this worked for me...
downloaded the HC system image for CWM from MoDaCo to sdcard
download and unzip bcm4329.ko module provided by Paul to sdk platform-tools folder
used revolutionary CWM Recovery method:
nandroid backup
wipe data/factory reset
wipe cache partition
install zip from sdcard/choose zip from sdcard
reboot system
adb remount
adb push bcm4329.ko /system/lib/modules
------------------------------------------------------------------------------
DO NOT DO TRY THE FOLLOWING (you risk bricking or loss of S-OFF): i think that because i was running flyhoney and had pushed the flyhoney hboot trying to get mail widget to work i was getting blackscreen after flash-reboot. so i reapplied Paul's 'fastboot flash boot stock-hc-flyer-boot-3.41.405.1.img' and 'adb push stock-hc-flyer-hboot_1.11.0010.nb0 / && adb shell dd if=/stock-hc-flyer-hboot_1.11.0010.nb0 of=/dev/block/mmcblk0p18'...
update: i'm running running 3.2.1 and have all working fine until i rebooted device to check hboot and now no wifi upon reboot...
update: re-flashed system zip and all working including wifi even after a few reboots to check...
lpasq said:
adb shell dd if=/stock-hc-flyer-hboot_1.11.0010.nb0 of=/dev/block/mmcblk0p18'
Click to expand...
Click to collapse
I imagine this was silently ignored, what hboot version do you have now?

[Q] wifi module problem with faux123 kernel-MB860

I am trying an experiment with my Atrix in which I need to be able to build the kernel and have a working wifi module. I have successfully built the faux123's kernel-MB860 (thanks very much!).
I then downloaded faux123's atrix-wifi-module in order to get wifi working. I have built the module, and pushed it to /system/lib/modules. However, wifi doesn't work. Under settings, it just displays "error". dmesg doesn't show nearly as much as a kernel packaged by faux123. Here is my output:
Code:
<4>[ 24.504982] sdhci_tegra_wlan_detect Detecting WLAN
<4>[ 24.504998] mot_wifi_set_carddetect: Nobody to notify
<4>[ 24.507937]
<4>[ 24.507940] Dongle Host Driver, version 4.218.248.31
<4>[ 24.507944] Compiled in /home/kenny/android/atrix-wifi-module/open-src/src/dhd/linux/../.. on Apr 17 2012 at 06:54:15
<6>[ 24.724025] request_suspend_state: wakeup (3->0) at 13492036210 (2012-04-21 19:25:46.351491984 UTC)
<6>[ 24.725196] lm3532_brightness_set: lcd-backlight, 0x4c(76), webtop=0
<7>[ 25.088713] mmc1: queuing CIS tuple 0x91 length 3
<6>[ 25.088824] mmc1: new SDIO card at address 0001
<6>[ 25.534772] usb_ether_get_stats
Whereas, dmesg from a kernel/module packaged by faux123 displays:
Code:
[ 49.811365] sdhci_tegra_wlan_detect Detecting WLAN
[ 49.811403] mot_wifi_set_carddetect: Nobody to notify
[ 49.812815]
[ 49.812818] Dongle Host Driver, version 4.218.248.31
[ 49.812822] Compiled in /home/paul/Froyo/system/vendor/bcm/wlan/osrc/open-src/src/dhd/linux/../.. on Dec 17 2011 at 19:58:57
[ 50.108317] mmc1: queuing CIS tuple 0x91 length 3
[ 50.108350] mmc1: new SDIO card at address 0001
[ 50.136595] alloc static buf at e9980000!
[ 50.136975] F1 signature read @0x18000000=0x9934329
[ 50.139716] DHD: dongle ram size is set to 294912(orig 294912)
[ 50.143537] wl_iw_attach thr:6d0 started
[ 50.143598] wl_iw_bt_init thr:6d1 started
[ 50.143655] dhd_attach thr:6d2 started
[ 50.143706] dhd_attach thr:6d3 started
[ 50.143749] dhd_attach thr:6d4 started
[ 50.191722] dhdsdio_write_vars: Download, Upload and compare of NVRAM succeeded.
[ 50.273753] wifi_get_mac_addr
[ 50.274700] Firmware version = wl0: May 6 2011 13:09:01 version 4.218.248.31
[ 50.442416] eth0: Broadcom Dongle Host Driver mac=40:fc:89:13:a8:83
If I try to do a insmod, I get an invalid argument message.
Code:
# insmod /system/lib/modules/dhd.ko
insmod: init_module '/system/lib/modules/dhd.ko' failed (Invalid argument)
Can someone suggest what I might be missing or doing wrong?
as far as i've researched this problem, it's hardware related. i get the same error (and an accompanying reboot) every time i try to toggle wifi.
http://forum.xda-developers.com/showthread.php?t=1205775
if you have any more success please let me know.
dLo GSR said:
as far as i've researched this problem, it's hardware related.
Click to expand...
Click to collapse
I'm not convinced it is hardware related (other than maybe having the wrong driver), since wifi works great using a true faux123 kernel/module.
I suspect my problem has something to do with how I compiled module or other files that I need to put on the phone.
How did you build it? A little more background might help
Build process ... it works!?!?
First, the good news...the module now works. But I don't understand what I may have done differently this time other than do the builds consecutively.
I retrieved the source:
Code:
$ cd ~/android/faux123-olympus-cm7-kernel
$ git clone https://github.com/faux123/kernel-MB860.git
$ cd ~/android
$ git clone https://github.com/faux123/atrix-wifi-module.git
Then I built:
Code:
$ cd ~/android/faux123-olympus-cm7-kernel/kernel-MB860
$ make ARCH=arm tegra_olympus_cm7_defconfig
$ make ARCH=arm CROSS_COMPILE=/home/kenny/tools/arm-2011.09/bin/arm-none-eabi- -j1
$ cd ../../atrix-wifi-module/open-src/src/dhd/linux/
$ export LINUXSRCDIR=/home/kenny/android/faux123-olympus-cm7-kernel/kernel-MB860
$ make ARCH=arm CROSS_COMPILE=~/tools/arm-2011.09/bin/arm-none-eabi- -j1
$ adb push /home/kenny/android/faux123-olympus-cm7-kernel/kernel-MB860/vendor/bcm/wlan/osrc/open-src/src/dhd/linux/dhd.ko /system/lib/modules/dhd.ko
I had kernel built a few days before I had found the wifi module source. I then tried building the wifi module and pushing the module as shown above.
Since then (over last week or so), I have tried a number of things, including copying files (/etc/firmware/wifi/*) from another phone which has a faux123 kernel. Are these files required? Are there steps in here that I missed?

USB-to-Ethernet Helper App

Delock USB 2.0 Ethernet Adapter and HG20F9-based adapters added.
Davicom DM9600 and QF9700-based devices added. Please give it a shot and report back your findings in this tread. Thanks.
It's me again ... I've updated the USB2Ethernet-Helper to a new version. I added support for dongles containing a QF9700 chip. Please note, I don't own such a device and thus can't testify if it is working correctly or not. Give it a shot and report your findings back to this thread so that I have a chance to fix it.
The best way to assist is to post a logcat from your Mediapad. Start an "adb logcat" over Wifi, connect your OTG cable and the dongle, and then start my App. Record the output in case you encounter errors.
For the initiated : Please also provide a dmesg log.
Thanks, DFahren
Hi all,
I developled a small App that can be used to connect our Mediapad to an Ethernet-based Internet router.
You can find it as attachment to this post.
Why does one need such an App? Here's the case...
Picture yourself in a hotel. You have got your Mediapad with you and would like to surf a bit in the Internet. The hotel does not offer wireless lan, but nevertheless has Ethernet-based Internet access. Since Ethernet-to-Wifi converters are kinda expensive, you think of getting yourself a USB-to-Ethernet adapter dongle to help you out of this misery. However, our Mediapad does not support Internet-by-Ethernet-adapter right out of the box....
Click to expand...
Click to collapse
You need to know a few things about this App.
In order to run this App successfully you need to have the 'su' binary installed on your Mediapad, i.e., your pad needs to be rooted. The App will fail if you don't have a rooted phone.
You need to have a USB-to-Ethernet adapter such as the "Edimax USB2.0 Fast Ethernet Adapter" and a USB-to-Go cable. Currently, my App only supports adapters that have the following chips from Asix built in: AX88772, AX88760, AX8817. If you have an adapter that uses a different controller chip, please contact me via this forum or write a PN. Linux has drivers for almost every controller chip and I might be able to compile the appropriate one for you and bundle it with this App.
You need to have a router that has DHCP enabled. This App does everything automatically. It won't work with IP addresses that need to be statically assigned.
You must have a non-modified Linux kernel on your Mediapad! That is, a 3.0.8 kernel that comes with the original Android ICS. If you have a modified kernel such as bart543's one, then this App won't work for you. May be in the future I gonna support those modified kernels.
Once you managed to install this App, you can surf the Internet using one of your favorite browsers.
Although Android has rudimentary support for Ethernet devices built in (as far as I can tell from looking at the source code), Android ICS on our Mediapad only supports Wifi and Mobile data. What this means to you is some Apps from the Market that need Internet access may work, unfortunately many Apps don't seem to work (e.g. TuneIn Radio, Skype, etc.). If your favorite App(s) do(es) not work, I'm afraid I can't help you. Blame it on Android. Usually all Apps that access networking functions right away without querying Android which network types may be available and up should run correctly.
How to install this app
Download this App to your PC.
Type
Code:
adb install USB2Ethernet-Helper.apk
What if I run into errors?
The UI will show a short message as to why a specific step fails. Post this message in this thread.
Install "TerminalIDE" from the Market, if you don't have yet.
Open a shell and type
Code:
logcat
Post the logcat output in this thread. Maybe I can help.
Please be aware that I will do my best to help you, but I'm not the quickest to respond because I have a lot other commitments to follow.
That's it. Have fun!
Cheers, Dfahren
dfahren said:
It's me again ... I've updated the USB2Ethernet-Helper to a new version. I added support for dongles containing a QF9700 chip. Please note, I don't own such a device and thus can't testify if it is working correctly or not. Give it a shot and report your findings back to this thread so that I have a chance to fix it.
The best way to assist is to post a logcat from your Mediapad. Start an "adb logcat" over Wifi, connect your OTG cable and the dongle, and then start my App. Record the output in case you encounter errors.
For the initiated : Please also provide a dmesg log.
Thanks, DFahren
Hi all,
I developled a small App that can be used to connect our Mediapad to an Ethernet-based Internet router.
You can find it as attachment to this post.
Why does one need such an App? Here's the case...
You need to know a few things about this App.
In order to run this App successfully you need to have the 'su' binary installed on your Mediapad, i.e., your pad needs to be rooted. The App will fail if you don't have a rooted phone.
You need to have a USB-to-Ethernet adapter such as the "Edimax USB2.0 Fast Ethernet Adapter" and a USB-to-Go cable. Currently, my App only supports adapters that have the following chips from Asix built in: AX88772, AX88760, AX8817. If you have an adapter that uses a different controller chip, please contact me via this forum or write a PN. Linux has drivers for almost every controller chip and I might be able to compile the appropriate one for you and bundle it with this App.
You need to have a router that has DHCP enabled. This App does everything automatically. It won't work with IP addresses that need to be statically assigned.
You must have a non-modified Linux kernel on your Mediapad! That is, a 3.0.8 kernel that comes with the original Android ICS. If you have a modified kernel such as bart543's one, then this App won't work for you. May be in the future I gonna support those modified kernels.
Once you managed to install this App, you can surf the Internet using one of your favorite browsers.
Although Android has rudimentary support for Ethernet devices built in (as far as I can tell from looking at the source code), Android ICS on our Mediapad only supports Wifi and Mobile data. What this means to you is some Apps from the Market that need Internet access may work, unfortunately many Apps don't seem to work (e.g. TuneIn Radio, Skype, etc.). If your favorite App(s) do(es) not work, I'm afraid I can't help you. Blame it on Android. Usually all Apps that access networking functions right away without querying Android which network types may be available and up should run correctly.
How to install this app
Download this App to your PC.
Type
Code:
adb install USB2Ethernet-Helper.apk
What if I run into errors?
The UI will show a short message as to why a specific step fails. Post this message in this thread.
Install "TerminalIDE" from the Market, if you don't have yet.
Open a shell and type
Code:
logcat
Post the logcat output in this thread. Maybe I can help.
Please be aware that I will do my best to help you, but I'm not the quickest to respond because I have a lot other commitments to follow.
That's it. Have fun!
Cheers, Dfahren
Click to expand...
Click to collapse
Hi
I am trying to connect a HUAWEI MediaPad 7 (ICS 4.0.3 kernal 3.0.8) to wired internet (ADSL) connection through a USB ethernet adapter (found on ebay)
OTG cable & above adapter yet to arrive and mean time I saw this post
Do I need any driver for this or will your workaround could solve it?
I'm not sure about the chip of this USB Ethernet adapter, I bought it since they mentioned its supporting Android
I don't want to use Wifi and very eager on fixing this with ADSL. I have a router and no need to dial to connect when I'm connecting from PC password is saved in the router.
Thanks
Indunil
Hi Indunil,
ok, your kernel specs seem to fit to my app.
But with your adapter I doubt that it will work with my app right out of the box. If you do not know the transceiver chip in the adapter, then chances are that it might be the wrong one. Try my app and if it works, cool, if not, please come back and I might find a solution to your problem.
Please be aware that a driver for adapters containing a AX88772 chip is included in the app. This is currently the only driver in the app.
Recall, you need to have an SU binary installed on your Mediapad!
Best wishes,
DFahren
living_legend said:
Hi
I am trying to connect a HUAWEI MediaPad 7 (ICS 4.0.3 kernal 3.0.8) to wired internet (ADSL) connection through a USB ethernet adapter (found on ebay)
OTG cable & above adapter yet to arrive and mean time I saw this post
Do I need any driver for this or will your workaround could solve it?
I'm not sure about the chip of this USB Ethernet adapter, I bought it since they mentioned its supporting Android
I don't want to use Wifi and very eager on fixing this with ADSL. I have a router and no need to dial to connect when I'm connecting from PC password is saved in the router.
Thanks
Indunil
Click to expand...
Click to collapse
I installed this app in my galaxy s3. This recognize the adapter but it give an error which said that that application could not download the right driver could anybday helpme.
Sent from my GT-I9300 using xda app-developers app
Hi
Thank you very much for the reply, I just wrote to the ebay seller asking about the chip in that adapter. BTW to install SU binary I have to root the media pad is it? I'm an extreme new b to android but was able to root n install cyanogen mod 7 on a Samsung galaxy pop previously but that was following a chrystal clear user guide from web. But when it comes to Huawei media pad I'm not sure any accurate and valid info available... If you know a good source pls help!
Thanks again for coming forward with this idea! I'm actually nervous to use WiFi at home because of the baby :cyclops:
Hi Fausto,
could you please give the exact error message the app outputs on the screen. (The one that is written in small print).
Fausto89 said:
I installed this app in my galaxy s3. This recognize the adapter but it give an error which said that that application could not download the right driver could anybday helpme.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
whePubl avenger
Hi living_legend,
hmmm, you need to browse a bit the forums on how to root the Mediapad. I think there are some pretty good posts out there.
Of course, you are right. Installing SU means rooting the pad.
Indeed the less electromagnetic waves you produce around human beings the better. I second your attitude.
living_legend said:
Hi
Thank you very much for the reply, I just wrote to the ebay seller asking about the chip in that adapter. BTW to install SU binary I have to root the media pad is it? I'm an extreme new b to android but was able to root n install cyanogen mod 7 on a Samsung galaxy pop previously but that was following a chrystal clear user guide from web. But when it comes to Huawei media pad I'm not sure any accurate and valid info available... If you know a good source pls help!
Thanks again for coming forward with this idea! I'm actually nervous to use WiFi at home because of the baby :cyclops:
Click to expand...
Click to collapse
dfahren said:
Hi living_legend,
hmmm, you need to browse a bit the forums on how to root the Mediapad. I think there are some pretty good posts out there.
Of course, you are right. Installing SU means rooting the pad.
Indeed the less electromagnetic waves you produce around human beings the better. I second your attitude.
Click to expand...
Click to collapse
Rooting process look very tedious (sigh!) & I'm so confused! (no knowledge about Linux) also No info in cyanogenmod.org regarding rooting this particular device
I received the adapter today and the chip seems to be AX88772A. When I plug everything nothing pop up or no activity happen in the device
Is there any way to write a patch like the Ethernet patch used in Android-x86 4.0.4 ICS RC2 devices. Currently my device got only Bluetooth, wifi and mobile network
no Ethernet though :silly:
If rooting is so tedious, you could flash a pre-rooted image, such as HWMOD's boot.img. Look here: http://forum.xda-developers.com/showthread.php?t=1725345&highlight=root
Here someone presents a rooted image, too: http://forum.xda-developers.com/showthread.php?t=1544855&highlight=root
Good to hear you've finally got your adapter that day. This is perfectly normal that once you plug in the adapter together with the USB-OTG cable into the Mediapad nothing happens. You have to use my app to see the lights flickering.
Just try it once again and if anything goes wrong, note down the error message.
Best wishes,
DFahren
living_legend said:
Rooting process look very tedious (sigh!) & I'm so confused! (no knowledge about Linux) also No info in cyanogenmod.org regarding rooting this particular device
I received the adapter today and the chip seems to be AX88772A. When I plug everything nothing pop up or no activity happen in the device
Is there any way to write a patch like the Ethernet patch used in Android-x86 4.0.4 ICS RC2 devices. Currently my device got only Bluetooth, wifi and mobile network
no Ethernet though :silly:
Click to expand...
Click to collapse
Hi,
I found this thread of yours and thought it could help me getting my USB-to-Ethernet Adapter to work on Android 4.0.4.
My device is a cheap rootet X7GS tablet, the Adapter is a UA0025C from LogiLink.
When running your App it tells me on the second step:
"Both host adapter and Usb-to-Ethernet adapter not found".
Usb-Host is definately supported (connected an SD-Card-Reader for testing) and the driver seems to be related to asix. It's a MosChip MCS7830, I have the linux driver on a disc here. I'll try to create this logcat you mentioned and post it here later. How can it be that the host adapter is not found?
Many thx in advance,
Technose
Edit: This should be the device (I bought it in germany where it is distributed by LogiLink):
MCS7830 -- USB 2.0 to 10/100M Fast Ethernet Controller from Asix
It can be found on the asix website, I can't post the link though due to Forum restrictions.
Thx again
Ok, here is the logcat output (the part I would assume to be relevant):
Code:
I/CmdRunner( 1669): Running command: id
D/dalvikvm( 1669): GC_CONCURRENT freed 470K, 10% free 6058K/6663K, paused 2ms+31ms
E/su ( 2537): sudb - Opening database
E/su ( 2537): sudb - Database opened
E/su ( 2537): sudb - Database closed
D/su ( 2537): 10056 de.df.usbethernethelper executing 0 /system/bin/sh using shell /system/bin/sh : sh
I/USB2Ethernet-Service( 1669): Capable to SU? true
D/USB2EthernetHelper( 1669): Shared prefs key: SU binary installed?_feedb
D/USB2EthernetHelper( 1669): Shared prefs key: SU binary installed?
D/USB2EthernetHelper( 1669): Shared prefs key: Host and ethernet adapter up and running?_feedb
I/USB2Ethernet-Service( 1669): ProdID: 0001
I/USB2Ethernet-Service( 1669): ProdID: 8176
I/USB2Ethernet-Service( 1669): ProdID: 0002
I/USB2Ethernet-Service( 1669): ProdID: 0002
I/USB2Ethernet-Service( 1669): ProdID: 7830
D/USB2EthernetHelper( 1669): Shared prefs key: Host and ethernet adapter up and running?
D/USB2EthernetHelper( 1669): Shared prefs key: Host and ethernet adapter up and running?_feedb
E/USB2Ethernet-Service( 1669): Service thread finishes with failure.
I/USB2EthernetHelper( 1669): Stopping service.
I/USB2EthernetHelper( 1669): Stopping alarm.
E/audio_hw_primary( 899): start_output_stream() persist.sys.spdif_setting=
D/audio_hw_primary( 899): pcm_open out: card(0), port(0)
D/USB2Ethernet-Service( 1669): +++ USB2EthernetHelperService Destroy called +++
D/USB2EthernetHelper( 1669): +++ Called onPause! +++
W/HardwareRenderer( 1197): Backbuffer cannot be preserved
W/InputManagerService( 999): Starting input on non-focused client [email protected] (uid=10056
pid=1669)
D/USB2EthernetHelper( 1669): +++ onDestroy called +++
D/dalvikvm( 1073): GC_CONCURRENT freed 340K, 69% free 6968K/22087K, paused 4ms+5ms
Hi Technose02,
thanks for the log. It may be that Mediapads differ from one another in certain parts of the hardware, I'm not sure about this. It's irritating that my app tells you it didn't find the host adapter. This really puzzles me since I always thought USB host adapters would be the same on all Mediapads. That said, the log does not show too much information, unfortunately....
Anyway, do you know how to do "adb shell" but not via USB cable but via WIFI? If so, could you please plug in your OTG cable and your adapter in the USB port and type on the command line in the shell "cat /d/usb/devices" and after that "dmesg" (of that the last, say, 20 lines) and post the output here? Would be great!
In fact, MosChip has been acquired by Asix some time ago. However, I'm unsure whether Asix develops MosChip Linux drivers any further. Logilink provides its own drivers for your adapter, but they seem to be 2.4 or 2.6 drivers - really old stuff. The may need tweaks to get them running on Linux 3.0.
Ok, first things first, would be great if you provided the other logs as well.
Cheers,
DFahren
Technose02 said:
Ok, here is the logcat output (the part I would assume to be relevant):
[.. log deleted ..]
Click to expand...
Click to collapse
Hi and thanks a lot for your reply.
I managed to get the adb connection over wifi and here you go:
result of cat /d/usb/devices:
Code:
T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 1
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0001 Rev= 3.00
S: Manufacturer=Linux 3.0.8-tcc ohci_hcd
S: Product=TCC OHCI
S: SerialNumber=tcc
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
T: Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0bda ProdID=8176 Rev= 2.00
S: Manufacturer=Realtek
S: SerialNumber=00e04c000001
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=500mA
I:* If#= 0 Alt= 0 #EPs= 4 Cls=ff(vend.) Sub=ff Prot=ff Driver=rtl8192cu
E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=03(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=84(I) Atr=03(Int.) MxPS= 64 Ivl=1ms
T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 1
B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0002 Rev= 3.00
S: Manufacturer=Linux 3.0.8-tcc ehci_hcd
S: Product=Telechips EHCI HS
S: SerialNumber=tcc-ehci
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 1
B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0002 Rev= 3.00
S: Manufacturer=Linux 3.0.8-tcc dwc_otg_hcd
S: Product=DWC OTG Controller
S: SerialNumber=dwc_otg.0
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms
T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 4 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=ff(vend.) Sub=00 Prot=ff MxPS=64 #Cfgs= 1
P: Vendor=9710 ProdID=7830 Rev= 1.00
S: Manufacturer=Moschip Semiconductor
S: Product=UA0025C
S: SerialNumber=6e000001
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=500mA
I:* If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=ff Driver=(none)
E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=31875us
E: Ad=83(I) Atr=03(Int.) MxPS= 16 Ivl=125us
[email protected]:/ #
Result of dmesg (my apologies if it's too large), I called dmesg after plugging in the USB-Ethernet-Controller and trying to connect to it via your app:
Code:
<4>[ 6.238149] link to Broadcom AP
<4>[ 6.238216] <=rtw_wx_set_essid, ret 0
<4>[ 6.238352] Set BSSID under fw_state=0x00000088
<4>[ 6.519609] link to Broadcom AP
<4>[ 6.522108] OnAuthClient
<4>[ 6.522142] network.SupportedRates[0]=82
<4>[ 6.522153] network.SupportedRates[1]=84
<4>[ 6.522163] network.SupportedRates[2]=8B
<4>[ 6.522173] network.SupportedRates[3]=96
<4>[ 6.522183] network.SupportedRates[4]=24
<4>[ 6.522193] network.SupportedRates[5]=30
<4>[ 6.522204] network.SupportedRates[6]=48
<4>[ 6.522214] network.SupportedRates[7]=6C
<4>[ 6.522224] network.SupportedRates[8]=0C
<4>[ 6.522234] network.SupportedRates[9]=12
<4>[ 6.522244] network.SupportedRates[10]=18
<4>[ 6.522254] network.SupportedRates[11]=60
<4>[ 6.522266] bssrate_len = 12
<6>[ 6.523791] usb 2-1: USB disconnect, device number 2
<4>[ 6.524279] ###=> usb_read_port_complete => urb status(-108)
<4>[ 6.524354] +rtw_dev_remove
<4>[ 6.524366] rtw_sta_flush
<4>[ 6.524446] (2)871x_drv - drv_close, bup=1, hw_init_completed=1
<4>[ 6.524461] -871x_drv - drv_close, bup=1
<4>[ 6.645561] ===> rtw_dev_unload
<4>[ 6.648566] usb_read_port_cancel
<4>[ 6.651827] usb_write_port_cancel
<4>[ 6.655306] ###> rtw_cmd_thread break.................
<4>[ 6.667830] <=== rtw_dev_unload
<4>[ 6.667843] +r871xu_dev_remove, hw_init_completed=1
<4>[ 6.668292] free_recv_skb_queue not empty, 3
<4>[ 6.668310] rtw_unregister_early_suspend
<4>[ 6.668324] =====> rtl8192c_free_hal_data =====
<4>[ 6.668334] <===== rtl8192c_free_hal_data =====
<4>[ 6.668365] -r871xu_dev_remove, done
<6>[ 6.945572] usb 2-1: new high speed USB device number 3 using tcc-ehci
<3>[ 7.605726] hub 2-0:1.0: unable to enumerate USB device on port 1
<6>[ 8.085681] usb 3-1: new full speed USB device number 2 using tcc-ohci
<6>[ 8.767894] usb 3-1: not running at top speed; connect to a high speed hub
<4>[ 8.800305] register rtw_netdev_ops to netdev_ops
<4>[ 8.804843] CHIP TYPE: RTL8188C_8192C
<4>[ 8.808704] ------------------usb_dvobj_init
<4>[ 8.812809]
<4>[ 8.812814] usb_endpoint_descriptor(0):
<4>[ 8.823099] bLength=7
<4>[ 8.825201] bDescriptorType=5
<4>[ 8.828301] bEndpointAddress=81
<4>[ 8.831300] wMaxPacketSize=40
<4>[ 8.834287] bInterval=0
<4>[ 8.836698] RT_usb_endpoint_is_bulk_in = 1
<4>[ 8.840716]
<4>[ 8.840721] usb_endpoint_descriptor(1):
<4>[ 8.846048] bLength=7
<4>[ 8.848255] bDescriptorType=5
<4>[ 8.851201] bEndpointAddress=2
<4>[ 8.854253] wMaxPacketSize=40
<4>[ 8.857596] bInterval=0
<4>[ 8.859866] RT_usb_endpoint_is_bulk_out = 2
<4>[ 8.864031]
<4>[ 8.864036] usb_endpoint_descriptor(2):
<4>[ 8.869497] bLength=7
<4>[ 8.871594] bDescriptorType=5
<4>[ 8.874561] bEndpointAddress=3
<4>[ 8.894440] wMaxPacketSize=40
<4>[ 8.897312] bInterval=0
<4>[ 8.899671] RT_usb_endpoint_is_bulk_out = 3
<4>[ 8.903819]
<4>[ 8.903822] usb_endpoint_descriptor(3):
<4>[ 8.912184] bLength=7
<4>[ 8.914281] bDescriptorType=5
<4>[ 8.917335] bEndpointAddress=84
<4>[ 8.920348] wMaxPacketSize=40
<4>[ 8.923294] bInterval=1
<4>[ 8.925764] RT_usb_endpoint_is_int_in = 4, Interval = 1
<4>[ 8.930930] nr_endpoint=4, in_num=2, out_num=2
<4>[ 8.930937]
<4>[ 8.937358] NON USB_SPEED_HIGH
<4>[ 8.940889] Chip Version ID: VERSION_NORMAL_TSMC_CHIP_88C.
<4>[ 8.948746] RF_Type is 3!!
<4>[ 8.955890] EEPROM type is E-FUSE
<4>[ 8.959065] ====> ReadAdapterInfo8192C
<4>[ 8.963886] Boot from EFUSE, Autoload OK !
<4>[ 9.584921] [set_dma_outbuffer], original len[8192]
<4>[ 11.209991] EEPROMVID = 0x0bda
<4>[ 11.213135] EEPROMPID = 0x8176
<4>[ 11.216151] EEPROMCustomerID : 0x00
<4>[ 11.219716] EEPROMSubCustomerID: 0x00
<4>[ 11.223255] RT_CustomerID: 0x00
<4>[ 11.226633] _ReadMACAddress MAC Address from EFUSE = 00:12:05:06:07:43
<4>[ 11.233234] EEPROMRegulatory = 0x0
<4>[ 11.236625] _ReadBoardType(0)
<4>[ 11.239719] BT Coexistance = disable
<4>[ 11.243298] RT_ChannelPlan: 0x0a
<4>[ 11.247052] _ReadPSSetting...bHWPwrPindetect(0)-bHWPowerdown(0) ,bSupportR
emoteWakeup(0)
<4>[ 11.255213] ### PS params=> power_mgnt(1),usbss_enable(0) ###
<4>[ 11.261136] ### AntDivCfg(0)
<4>[ 11.264094] readAdapterInfo_8192CU(): REPLACEMENT = 1
<4>[ 11.269161] <==== ReadAdapterInfo8192C in 2310 ms
<4>[ 11.276801] rtw_register_early_suspend
<4>[ 11.280782] rtw_macaddr_cfg MAC Address = 00:12:05:06:07:43
<4>[ 11.288350] MAC Address from pnetdev->dev_addr= 00:12:05:06:07:43
<4>[ 11.318266] +871x_drv - drv_open, bup=0
<4>[ 11.322380] bDriverStopped:0, bSurpriseRemoved:0, bup:0, hw_init_completed
:0
<4>[ 11.375083] ===> FirmwareDownload91C() fw:Rtl819XFwImageArray_TSMC
<4>[ 11.381534] FirmwareDownload92C accquire FW from embedded image
<4>[ 11.387594] fw_ver=v79, fw_subver=0, sig=0x88c0
<4>[ 11.781025] fw download ok!
<4>[ 11.783696] Set RF Chip ID to RF_6052 and RF type to 1T1R.
<4>[ 12.479616] IQK:Start!!!
<4>[ 12.652988] Path A IQK Success!!
<4>[ 12.777034] Path A IQK Success!!
<4>[ 12.853028] IQK: final_candidate is 0
<4>[ 12.857129] IQK: RegE94=102 RegE9C=11 RegEA4=fe RegEAC=2 RegEB4=0 RegEBC=0
RegEC4=0 RegECC=0
<4>[ 12.857158] Path A IQ Calibration Success !
<4>[ 13.115043] pdmpriv->TxPowerTrackControl = 1
<4>[ 13.196053] MAC Address from REG_MACID = 00:12:05:06:07:43
<4>[ 13.201443] rtl8192cu_hal_init in 1880ms
<4>[ 13.205321] MAC Address = 00:12:05:06:07:43
<4>[ 13.283044] ------------------usb_intf_start
<4>[ 13.287861] -871x_drv - drv_open, bup=1
<6>[ 13.297729] ADDRCONF(NETDEV_UP): wlan0: link is not ready
<4>[ 13.303158] [rtw_wx_set_pmkid] IW_PMKSA_FLUSH!
<4>[ 13.307612] set_mode = IW_MODE_INFRA
<4>[ 13.336356] [rtw_wx_set_pmkid] IW_PMKSA_FLUSH!
<4>[ 15.305716] ==>pwr_state_check_handler .fw_state(8)
<4>[ 15.310552] ==> rtw_ps_cmd , enqueue CMD
<4>[ 15.351211] ==>rtw_ps_processor .fw_state(8)
<4>[ 15.355365] ==>ips_enter cnts:1
<4>[ 15.362107] ==>power_saving_ctrl_wk_hdl change rf to OFF...LED(0x00020808)
....
<4>[ 15.362132]
<4>[ 15.371440] ===> rtw_ips_pwr_down...................
<4>[ 15.379104] ====> rtw_ips_dev_unload...
<4>[ 15.625779] usb_read_port_cancel
<4>[ 15.632101] usb_write_port_cancel
<4>[ 15.635503] ==> rtl8192cu_hal_deinit
<4>[ 15.639168] bkeepfwalive(0)
<4>[ 15.641799] card disble without HWSM...........
<4>[ 15.719126] <=== rtw_ips_pwr_down..................... in 350ms
<4>[ 17.245539]
<4>[ 17.245560] rfpwrstate_check call ips_leave....
<4>[ 17.254263] ==>ips_leave cnts:1
<4>[ 17.257405] ===> rtw_ips_pwr_up..............
<4>[ 17.261702] ===> ips_netdrv_open.........
<4>[ 17.319221] ===> FirmwareDownload91C() fw:Rtl819XFwImageArray_TSMC
<4>[ 17.325372] FirmwareDownload92C accquire FW from embedded image
<4>[ 17.331369] fw_ver=v79, fw_subver=0, sig=0x88c0
<4>[ 17.730218] fw download ok!
<4>[ 17.732894] Set RF Chip ID to RF_6052 and RF type to 1T1R.
<4>[ 18.396201] IQK:Start!!!
<4>[ 18.556209] Path A IQK Success!!
<4>[ 18.665202] Path A IQK Success!!
<4>[ 18.741213] IQK: final_candidate is 0
<4>[ 18.744759] IQK: RegE94=102 RegE9C=11 RegEA4=fe RegEAC=2 RegEB4=0 RegEBC=0
RegEC4=0 RegECC=0
<4>[ 18.744786] Path A IQ Calibration Success !
<4>[ 19.004229] pdmpriv->TxPowerTrackControl = 1
<4>[ 19.085234] MAC Address from REG_MACID = 00:12:05:06:07:43
<4>[ 19.090802] rtl8192cu_hal_init in 1830ms
<4>[ 19.094582] ------------------usb_intf_start
<4>[ 19.099067] <=== rtw_ips_pwr_up.............. in 1840ms
<4>[ 19.105234] ==> ips_leave.....LED(0x00028008)...
<4>[ 21.195299] survey done event(3e)
[...]
<4>[ 21.270595] rtw_select_and_join_from_scanned_queue: candidate: localWifiFi
VoRoe(90:a4:de:21:e1:2c)
<4>[ 21.279507] link to Broadcom AP
<4>[ 21.283431] <=rtw_wx_set_essid, ret 0
<4>[ 21.294413] Set BSSID under fw_state=0x00000088
<4>[ 21.471355] link to Broadcom AP
<4>[ 21.477323] OnAuthClient
<4>[ 21.479738] network.SupportedRates[0]=82
<4>[ 21.483643] network.SupportedRates[1]=84
<4>[ 21.487555] network.SupportedRates[2]=8B
<4>[ 21.491449] network.SupportedRates[3]=96
<4>[ 21.495313] network.SupportedRates[4]=24
<4>[ 21.499244] network.SupportedRates[5]=30
<4>[ 21.503101] network.SupportedRates[6]=48
<4>[ 21.507043] network.SupportedRates[7]=6C
<4>[ 21.510913] network.SupportedRates[8]=0C
<4>[ 21.514832] network.SupportedRates[9]=12
<4>[ 21.518741] network.SupportedRates[10]=18
<4>[ 21.522689] network.SupportedRates[11]=60
<4>[ 21.526724] bssrate_len = 12
<4>[ 21.536384] OnAction_back
<4>[ 21.538992] OnAssocRsp
<4>[ 21.541242] report_join_res(1)
<4>[ 21.544393] rtw_joinbss_update_network
<4>[ 21.548185] +rtw_update_ht_cap()
<4>[ 21.551296] rtw_joinbss_update_stainfo
<4>[ 21.555201] rx bc/mc packets, to perform sw rtw_aes_decrypt
<4>[ 21.563967] HW_VAR_BASIC_RATE: BrateCfg(0x15d)
<6>[ 21.577530] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
<4>[ 21.597332] WMM(0): 0, a42b
<4>[ 21.600305] WMM(1): 0, a44f
<4>[ 21.603302] WMM(2): 0, 5e4322
<4>[ 21.615305] WMM(3): 0, 2f3222
<4>[ 21.619306] [HW_VAR_ACM_CTRL] Write 0x0
<4>[ 21.623298] HTOnAssocRsp
<4>[ 21.710327] update raid entry, mask=0xfffff, arg=0xa0
<4>[ 21.738309] rtl8192c_set_FwJoinBssReport_cmd mstatus(1)
<4>[ 21.747397] OnAction_back
<4>[ 21.749872] OnAction_back, action=0
<4>[ 21.753342] issue_action_BA, category=3, action=1, status=0
<4>[ 21.778459] SetFwRsvdPagePkt
<4>[ 21.781378] Set RSVD page location to Fw.
<4>[ 21.796742]
<4>[ 21.796764] ~~~~stastakey:unicastkey
<4>[ 21.804713]
<4>[ 21.804734] ~~~~stastakey:groupkey
<4>[ 21.809898] ==> rtw_set_key algorithm(4),keyid(2),key_mask(4)
<4>[ 21.826097] =>mlmeext_joinbss_event_callback
<4>[ 24.192385] rtl8192c_dm_RF_Saving(): RF_Save
<4>[ 28.106532] rtw_set_ps_mode(): Enter 802.11 power save mode...
<4>[ 28.131502] rtl8192c_dm_RF_Saving(): RF_Normal
<4>[ 28.135869] rtl8192c_set_FwPwrMode_cmd(): Mode = 1, SmartPS = 2
<4>[ 28.845670] rtw_set_ps_mode(): Busy Traffic , Leave 802.11 power save..
<4>[ 28.853477] rtl8192c_set_FwPwrMode_cmd(): Mode = 0, SmartPS = 0
<4>[ 30.106590] rtw_set_ps_mode(): Enter 802.11 power save mode...
<4>[ 30.112324] rtl8192c_set_FwPwrMode_cmd(): Mode = 1, SmartPS = 2
<7>[ 31.876233] wlan0: no IPv6 routers present
<4>[ 32.106677] rtw_set_ps_mode(): Busy Traffic , Leave 802.11 power save..
<4>[ 32.126840] rtl8192c_set_FwPwrMode_cmd(): Mode = 0, SmartPS = 0
<4>[ 32.264611] rtl8192c_dm_RF_Saving(): RF_Save
<4>[ 36.106787] rtw_set_ps_mode(): Enter 802.11 power save mode...
<4>[ 36.131745] rtl8192c_dm_RF_Saving(): RF_Normal
<4>[ 36.136101] rtl8192c_set_FwPwrMode_cmd(): Mode = 1, SmartPS = 2
<4>[ 36.926694] rtw_set_ps_mode(): Busy Traffic , Leave 802.11 power save..
<4>[ 36.934915] rtl8192c_set_FwPwrMode_cmd(): Mode = 0, SmartPS = 0
<4>[ 38.106781] rtw_set_ps_mode(): Enter 802.11 power save mode...
<4>[ 38.112457] rtl8192c_set_FwPwrMode_cmd(): Mode = 1, SmartPS = 2
<4>[ 40.108352] rtw_set_ps_mode(): Busy Traffic , Leave 802.11 power save..
<4>[ 40.115913] rtl8192c_set_FwPwrMode_cmd(): Mode = 0, SmartPS = 0
<4>[ 40.225908] rtl8192c_dm_RF_Saving(): RF_Save
<4>[ 42.116544] rtw_set_ps_mode(): Enter 802.11 power save mode...
<4>[ 42.140880] rtl8192c_dm_RF_Saving(): RF_Normal
<4>[ 42.145156] rtl8192c_set_FwPwrMode_cmd(): Mode = 1, SmartPS = 2
<4>[ 62.438236] [set_dma_outbuffer], original len[8192]
<4>[ 63.010087] UMP<2>: New session opened
<4>[ 70.121821] rtw_set_ps_mode(): Busy Traffic , Leave 802.11 power save..
<4>[ 70.130852] rtl8192c_set_FwPwrMode_cmd(): Mode = 0, SmartPS = 0
<4>[ 72.107909] rtw_set_ps_mode(): Enter 802.11 power save mode...
<4>[ 72.113646] rtl8192c_set_FwPwrMode_cmd(): Mode = 1, SmartPS = 2
<4>[ 72.185319] ID change ISR : Host (0)
<4>[ 72.188869] Set ID to host mode(0)
<4>[ 72.192119] set wakelock for otg0
<4>[ 72.388612] Using Buffer DMA mode
<4>[ 72.391761] Periodic Transfer Interrupt Enhancement - disabled
<4>[ 72.397689] Multiprocessor Interrupt Enhancement - disabled
<4>[ 72.447551] Init: Port Power? op_state=1
<4>[ 72.451293] Init: Power Port (0)
<3>[ 72.454561] DWC_OTG : [tcc_set_vbus] vbus_state:1
<4>[ 72.459243] SRP: Host mode
<4>[ 72.461869] Start called p = d61126a0
<4>[ 72.465505] starting connect time
<3>[ 72.567584] DWC_OTG : [tcc_set_vbus] vbus_state:1
<6>[ 73.157651] usb 1-1: new high speed USB device number 2 using dwc_otg
<3>[ 73.973286] usb 1-1: device v9710 p7830 is not supported
<4>[ 75.747908] rtw_set_ps_mode(): Busy Traffic , Leave 802.11 power save..
<4>[ 75.757782] rtl8192c_set_FwPwrMode_cmd(): Mode = 0, SmartPS = 0
<4>[ 76.176019] rtl8192c_dm_RF_Saving(): RF_Save
<4>[ 78.108101] rtw_set_ps_mode(): Enter 802.11 power save mode...
<4>[ 78.133073] rtl8192c_dm_RF_Saving(): RF_Normal
<4>[ 78.137408] rtl8192c_set_FwPwrMode_cmd(): Mode = 1, SmartPS = 2
<4>[ 92.228164] unset wakelock for otg0
<4>[ 106.108973] rtw_set_ps_mode(): Busy Traffic , Leave 802.11 power save..
<4>[ 106.117312] rtl8192c_set_FwPwrMode_cmd(): Mode = 0, SmartPS = 0
<4>[ 106.205992] rtl8192c_dm_RF_Saving(): RF_Save
<4>[ 108.109033] rtw_set_ps_mode(): Enter 802.11 power save mode...
<4>[ 108.134011] rtl8192c_dm_RF_Saving(): RF_Normal
<4>[ 108.148733] rtl8192c_set_FwPwrMode_cmd(): Mode = 1, SmartPS = 2
<4>[ 109.725123] [set_dma_outbuffer], original len[8192]
<4>[ 110.155226] rtw_set_ps_mode(): Busy Traffic , Leave 802.11 power save..
<4>[ 110.168053] rtl8192c_set_FwPwrMode_cmd(): Mode = 0, SmartPS = 0
<4>[ 112.109163] rtw_set_ps_mode(): Enter 802.11 power save mode...
<4>[ 112.115168] rtl8192c_set_FwPwrMode_cmd(): Mode = 1, SmartPS = 2
[email protected]:/ #
I expect the problems are here?
Code:
<3>[ 7.605726] hub 2-0:1.0: unable to enumerate USB device on port 1
<6>[ 8.085681] usb 3-1: new full speed USB device number 2 using tcc-ohci
<6>[ 8.767894] usb 3-1: not running at top speed; connect to a high speed hub
Does this mean, that my USB-Port is not 2.0? To be honest, it is not promoted to have USB 2.0, just "micro USB with Host Mode". Now who would expect a tablet designed for running Android 4 to ship with a slow USB Connector these days...
Well but even if this was the case and even if it would be a very slow lan-connection: the USB-Ethernetcontroller claims to be complaint to USB 2.0/1.1 Standard.
Thx again for your help!!
Hi Technose02,
ok, now I see why I thought it must be a non-standard configuration. I think you are operating a Realtek USB Wifi dongle and your Usb-Ethernet dongle together plugged in an external hub. This configuration differs from mine since I simply have an OTG cable plugged into the USB port and my Edimax Usb-to-Ethernet dongle.
In fact the line that shows, that this configuration doesn't currently work is
Code:
<6>[ 73.157651] usb 1-1: new high speed USB device number 2 using dwc_otg
<3>[ 73.973286] usb 1-1: device v9710 p7830 is not supported
Ok, I see the problem, but I think I can solve it. Please stay tuned, it's going to take a little while.
So long,
DFahren
Technose02 said:
Hi and thanks a lot for your reply.
I managed to get the adb connection over wifi and here you go:
result of cat /d/usb/devices:
Code:
...
Result of dmesg (my apologies if it's too large), I called dmesg after plugging in the USB-Ethernet-Controller and trying to connect to it via your app:
Code:
...
Does this mean, that my USB-Port is not 2.0? To be honest, it is not promoted to have USB 2.0, just "micro USB with Host Mode". Now who would expect a tablet designed for running Android 4 to ship with a slow USB Connector these days...
Well but even if this was the case and even if it would be a very slow lan-connection: the USB-Ethernetcontroller claims to be complaint to USB 2.0/1.1 Standard.
Thx again for your help!!
Click to expand...
Click to collapse
Thanks a lot! I flashed OsiMod and so far its working fine appart from few glitches in battery progress indicator.
And your app is working perfectly with the adapter I purchased through ebay....! Means this app works with ASIx chips ?
You can place the app in google play cz it really works
Sent from my HUAWEI OsiMood MediaPad using Tapatalk 2
It's me again.
I managed to compile a driver suitable for your dongle. I used the most recent mcs7830 driver source code I could find on kernel.org, compiled it for Android and did test it on my Mediapad. Testing, howver, is limited to checking if it can be "insmod-ed". It can.
Then I registered your otg host adapter with my app. Altogether you will find my updated app in the first post. Download it, give it a shot and if there are still problems, you can also write me a PN with the logs you formerly provided. There is no need to clutter this thread with log files any further.
Yep, I can tell you my app works with my Edimax adapter like it should. Please notice, you need to read my first post carefully. I wrote not each and every app that uses networking will work with an ethernet adapter. This is not due to my app being uncapable, but Android 4.0 not having full ethernet support. So there are some networking apps that work, some (perhaps most) don't. The browser, though, works like a charm.
That's why I don't want to put it in the play store, since it has too many drawbacks and there are other (most notably Asus) Android portings that have full ethernet integration right out of the box.
Cheers,
DFahren
living_legend said:
Thanks a lot! I flashed OsiMod and so far its working fine appart from few glitches in battery progress indicator.
And your app is working perfectly with the adapter I purchased through ebay....! Means this app works with ASIx chips ?
You can place the app in google play cz it really works
Sent from my HUAWEI OsiMood MediaPad using Tapatalk 2
Click to expand...
Click to collapse
yes true, browser works like a miracle
Skype, playstore downloads (searching ok), google talk won't work any alternative as you may know for video calling
Sent from my HUAWEI OsiMood MediaPad using Tapatalk 2
Hmm, no, unfortunately not. I think you need to try potential video calling apps yourself.
Good to know my app now works for you, sounds very good. May be, once I finde lots of time, I do an integration of my app in Android so that you don't need any app and can activate ethernet support right from Settings menu ...
Cheers,
DFahren
DFahren,
As You have environment up and running, would You be so kind to compile module for D-Link DUB-E100 H/W Rev. C1 ?
It is AX88772B, but with 2001:1a02 ID's.
I hope DUB_E100_Linux_v420.zip along with
Code:
--- DUB_E100_Linux_v420/asix.c 2011-09-19 12:48:58.000000000 +0600
+++ asix.c 2012-12-24 13:35:18.000000000 +0600
@@ -3412,6 +3412,10 @@
USB_DEVICE (0x2001, 0x1a00),
.driver_info = (unsigned long) &dlink_dub_e100_info,
}, {
+ // DLink DUB-E100 H/W Rev. C1 (AX88772B)
+ USB_DEVICE (0x2001, 0x1a02),
+ .driver_info = (unsigned long) &ax88772b_info,
+}, {
// DLink DUB-E100B
USB_DEVICE (0x2001, 0x3c05),
.driver_info = (unsigned long) &dlink_dub_e100b_info,
will do the trick?
@skleroz: Might well be, that this diff will do the trick. Stay tuned a bit longer. I gonna give it a shot next year. This year my time left is a little too short to get a new driver compiled for my App.
Wish all of you an incredible New Year!!
DFahren
skleroz said:
DFahren,
As You have environment up and running, would You be so kind to compile module for D-Link DUB-E100 H/W Rev. C1 ?
It is AX88772B, but with 2001:1a02 ID's.
...
Click to expand...
Click to collapse

[Q] Please help, phone won't stop randomly rebooting.

This has happened to me with every single ROM I install. I wiped everything and did a clean install with each of them. I don't know why this is happening. I'm rooted, I have SuperUser, and I'm S-OFF. Right in the middle of restoring my apps with Titanium, my phone just froze and rebooted itself. I use this phone all day and this is becoming a huge problem. Somebody please help.
Thank You sincerely.
Possible Fix
xX760Xx said:
This has happened to me with every single ROM I install. I wiped everything and did a clean install with each of them. I don't know why this is happening. I'm rooted, I have SuperUser, and I'm S-OFF. Right in the middle of restoring my apps with Titanium, my phone just froze and rebooted itself. I use this phone all day and this is becoming a huge problem. Somebody please help.
Thank You sincerely.
Click to expand...
Click to collapse
Try taking the battery cover off of the phone if it just continually reboots. Then go into your settings, power, and turn fast boot off.
Did you use and flash the "update.zip" option that titanium backup offers?
Makr sure you are not restoring system data
CyanogenMod 10.1 Predictable Reboot while Wifi Tethered
<First Post><Tried to find the right place><Watched the video><noob>
Last night I used the HTCDev HBoot Unlock technique to Unlock my Hboot 2.28 on my HTC Rezound. S-ON.
It now reflects "TAMPERED, UNLOCKED" - no problems to speak of with the process.
I installed TWRP 2.6 recovery, did a factory reset and multiple wipes across the partitions shown as available on TWRP.
I installed the Unofficial CyanogenMod 10.1 here: vp-zp com snuzzo roms flyhalf205 cm10 I used the 0819-NIGHTLY.
I've since loaded the device up with my usual apps and and decided to try the WIFI AP/WIFI Tether option.
I had only 1 random reboot prior to attempting the WIFI AP.
On the surface WIFI AP appears to work - devices can connect with WPA2 PSK, obtain IP, routing works, etc.
If I try speedtest on tethered device, however, the phone almost immediately reboots to the white HTC screen (and has gotten stuck in a loop several times requiring a battery pull).
I'd like to help diagnose what's happening, but I'm afraid I need some assistance for the best way to start.
What's the best way to start diag? Gather kernel logs? Gather wpa_supplicant logs? Look @ HBoot versions? Look @ Radio Firmware versions? Go S-OFF?
Here's a quick post from /dev/log/kernel_log -- note, I'm not OC'd (1512Mhz)
08-20 01:09:15 <4>[ 2.592498] ------------[ cut here ]------------
08-20 01:09:15 <4>[ 2.592681] WARNING: at arch/arm/mach-msm/clock-local.c:376 __branch_clk_disable_reg+0xd4/0xec()
08-20 01:09:15 <4>[ 2.592742] sdc3_p_clk status stuck at 'on'
08-20 01:09:15 <4>[ 2.592926] Modules linked in:
08-20 01:09:15 <4>[ 2.593170] [<c00532d4>] (unwind_backtrace+0x0/0xf0) from [<c00da384>] (warn_slowpath_common+0x4c/0x64)
08-20 01:09:15 <4>[ 2.593353] [<c00da384>] (warn_slowpath_common+0x4c/0x64) from [<c00da41c>] (warn_slowpath_fmt+0x2c/0x3c)
08-20 01:09:15 <4>[ 2.593505] [<c00da41c>] (warn_slowpath_fmt+0x2c/0x3c) from [<c00986f4>] (__branch_clk_disable_reg+0xd4/0xec)
08-20 01:09:15 <4>[ 2.593658] [<c00986f4>] (__branch_clk_disable_reg+0xd4/0xec) from [<c009876c>] (branch_clk_disable+0x28/0x44)
08-20 01:09:15 <4>[ 2.593750] [<c009876c>] (branch_clk_disable+0x28/0x44) from [<c005a8c0>] (clk_disable+0x6c/0xf4)
08-20 01:09:15 <4>[ 2.593933] [<c005a8c0>] (clk_disable+0x6c/0xf4) from [<c0373950>] (msmsdcc_switch_clock+0x390/0x3e4)
08-20 01:09:15 <4>[ 2.594085] [<c0373950>] (msmsdcc_switch_clock+0x390/0x3e4) from [<c0373ac4>] (msmsdcc_runtime_suspend+0x98/0xf4)
08-20 01:09:15 <4>[ 2.594268] [<c0373ac4>] (msmsdcc_runtime_suspend+0x98/0xf4) from [<c02a041c>] (pm_generic_runtime_suspend+0x2c/0x38)
08-20 01:09:15 <4>[ 2.594421] [<c02a041c>] (pm_generic_runtime_suspend+0x2c/0x38) from [<c02a287c>] (rpm_callback+0x44/0x5c)
08-20 01:09:15 <4>[ 2.594604] [<c02a287c>] (rpm_callback+0x44/0x5c) from [<c02a2d38>] (rpm_suspend+0x270/0x458)
08-20 01:09:15 <4>[ 2.594757] [<c02a2d38>] (rpm_suspend+0x270/0x458) from [<c02a3c70>] (pm_runtime_work+0x7c/0x98)
08-20 01:09:15 <4>[ 2.594848] [<c02a3c70>] (pm_runtime_work+0x7c/0x98) from [<c00ed1b4>] (process_one_work+0x248/0x3a4)
08-20 01:09:15 <4>[ 2.595031] [<c00ed1b4>] (process_one_work+0x248/0x3a4) from [<c00ed6ec>] (worker_thread+0x224/0x3e0)
08-20 01:09:15 <4>[ 2.595184] [<c00ed6ec>] (worker_thread+0x224/0x3e0) from [<c00f3050>] (kthread+0x80/0x88)
08-20 01:09:15 <4>[ 2.595336] [<c00f3050>] (kthread+0x80/0x88) from [<c004e69c>] (kernel_thread_exit+0x0/0x8)
08-20 01:09:15 <4>[ 2.595428] ---[ end trace 65f8ea860415c054 ]---
<Update>
I found another forum post with similar issue and I raised my min clock speed from 192Mhz to 384Mhz and re-ran the test and it did NOT reboot. Will continue testing and update if I get another reboot. 2 days solid @ the new min clock speed, no more reboots, battery remains dreadfully bad, but no worse.
VIGOR PVT SHIP S-ON RL
HBOOT-2.28
RADIO-2.23.10.0123r/2.23.10.0124r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Sep 20, 2012

Modem reset problem? why?

Hi all, I have a Note 2 that randomly rebooted when I was charging it. It didn't always do it, but occasionally. This time, after it rebooted when connected to a wall charger (it was already fully charged as the green LED was on for several hours), I disconnected the charging cable and connected it to my computer to do a dump:
adb shell cat /proc/last_kmesg > last_kmesg_11212013.txt
Here is the link of this log file:
https://www.dropbox.com/s/6b4f6ygrtg...g_11212013.txt
and here is the section that was related to the reboot from the attached log file. There was a panic and the system rebooted. I'm not familiar with Android internal. I hope someone could help me to identify why that happened?
** The phone was in airplane mode (no wifi/data/voice/GPS) when the reboot happened. It's rooted and running stock JB 4.1.2. My phone has the sane emmc chip.
** Noticed that it kept powering on 'mdm' every 5 seconds. The phone was in airplane mode, why Android kept powering on the modem? It was during one of these 'powering on mdm' that it failed and rebooted.
** reboot did not happen when phone was disconnected from the charger (I tried 2 different chargers and same problem)
I'd appreciate all the help I can get. Thank you.
Code:
<6>[ 3178.869129] c0 mdm_subsys_powerup: mdm modem restart timed out.
<0>[ 3178.869289] c0 Kernel panic - not syncing: subsystem_restart_wq_func[e85f0cc0]: Failed to powerup external_modem!
<4>[ 3178.869498] c0 Backtrace:
<4>[ 3178.869666] c0 [<c0061cd0>] (dump_backtrace+0x0/0x114) from [<c06495cc>] (dump_stack+0x20/0x24)
<4>[ 3178.869851] c0 r7:e563c540 r6:c0abfc34 r5:c0ac6ff0 r4:c0b6f5a0
<4>[ 3178.870056] c0 [<c06495ac>] (dump_stack+0x0/0x24) from [<c0649654>] (panic+0x84/0x1b8)
<4>[ 3178.870269] c0 [<c06495d0>] (panic+0x0/0x1b8) from [<c00802c0>] (subsystem_restart_wq_func+0x21c/0x258)
<4>[ 3178.870464] c0 r3:c0919200 r2:e85f0cc0 r1:c0650f7c r0:c0919b00
<4>[ 3178.870678] c0 [<c00800a4>] (subsystem_restart_wq_func+0x0/0x258) from [<c00bbc18>] (process_one_work+0x14c/0x4a0)
<4>[ 3178.870923] c0 [<c00bbacc>] (process_one_work+0x0/0x4a0) from [<c00bc304>] (worker_thread+0x18c/0x3e8)
<4>[ 3178.871149] c0 [<c00bc178>] (worker_thread+0x0/0x3e8) from [<c00c2edc>] (kthread+0x98/0xa0)
<4>[ 3178.871367] c0 [<c00c2e44>] (kthread+0x0/0xa0) from [<c00a5da4>] (do_exit+0x0/0x754)
<4>[ 3178.871532] c0 r7:00000013 r6:c00a5da4 r5:c00c2e44 r4:dba8feb0
<6>[ 3178.972415] c0 notifier_call_chain : NOTIFY BAD sec_debug_panic_handler
<0>[ 3178.972575] c0 Rebooting in 1 seconds..
<7>[ 3179.754044] c0 s5p-ohci s5p-ohci: auto-stop root hub
<0>[ 3179.976977] c0 sec_reboot (104, emergency)
Did you or anyone find a solution to this problem or even any further information?
I'm facing this problem with my Note 2 LTE and after getting many restarts that seemed to be normal restarts regarding the kernel logs, no kernel panic / ooops but normal reboot that some non-kenel module requested perhaps, (see logs in my thread; but had some errors with a usb device that probably is the modem), I now got a kernel panic with your exact messages for the restarting modem, the panic line and the words (functions?) in the backtrace, but other hex values!!
I also have backtraces after each CPU shutdown, but your log file isn't available anymore, so I can't tell if that's specifically my log.
Here's my log: http://pastebin.com/VHkakBCF
fightcookie

Categories

Resources