Related
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
Hi everybody!
Today I had a problem with my tablet Onda Vi40 Elite v3 9.7" 1024x768.
I wanted to update it to the last official firmware (http://file2.mydrivers.com/ondata/download/driver/oamp3/Vi40/Vi40J-V1_v1.4rc3.rar), and accidently I flashed a firmware I was analyzing from KNC-902 that has almost the same specs (http://pan.baidu.com/netdisk/singlepublic?fid=924378_480365957) using LiveSuite 1.07.
The firmware flashed ok, but my touch was not working (it was normal, because it wasn't the same hardware).
So I took the correct firmware from Onda and flashed it to my tablet. The problem now is that the touch keeps not working!
I have looked around on internet, and found maybe a similar behavior on Ainol Fire tablet, where the firmware update also flashed a new touch IC firmware.
I already have opened my tablet and found the touch IC controller (FT5406EE8) and I think firmware for it to (http://forum.xda-developers.com/showpost.php?p=28451445&postcount=22).
My question is: how can I know what is the right firmware for my touch IC controller (I have seen more than one for 1024x768) and how can I flash this firmware again to my touch IC controller?
Thank you for any help!
Regards,
Michael
P.S.: Sorry for my bad english, but this is not my mother language.
Here is more info from KNC902: hxxp://w.w.w.iknc.net/product_show.asp?id=870
And here from Onda Vi40 Elite: hxxp://w.w.w.onda.cn/Tablet/ProductInfo.aspx?ProductId=179
Thanks again!
P.S.: Please correct hxxp and w.w.w links.
Hey there,
I have a similar problem with my tablet as well. A rom flashed the IC controller and the stock one won't fix it back. Anyway, I have a vague idea on how to fix your problem but i need the firmware you accidentally flashed since its able to flash controllers. (not all firmwares do that)
Hi DoiX,
A rom that can flash the IC touch controller does not fix my problem. I have seen this tutorial http://www.freaktab.com/showthread.php?1545-How-to-fix-a-A10-AllWinner-ft5X-touch-screen! and managed to change my stock rom with the necessary changes to flash the IC touch controller but without luck.
This is what I get from dmesg when it tries to flash it with a modded ft5x_ts.ko (force blind update).
You can see that at STEP 3 it does not recognize the ID's (maybe because it is empty) and after blind update the ECC check at STEP 6 is wrong.
<6>[ 4.597896] ===========================ft5x_ts_init=====================
<6>[ 4.604736] ctp_fetch_sysconfig_para.
<6>[ 4.608540] ctp_fetch_sysconfig_para: after: ctp_twi_addr is 0x38, dirty_addr_buf: 0x38. dirty_addr_buf[1]: 0xfffe
<6>[ 4.619357] ctp_fetch_sysconfig_para: ctp_twi_id is 2.
<6>[ 4.624657] ctp_fetch_sysconfig_para: screen_max_x = 1024.
<6>[ 4.645314] ctp_fetch_sysconfig_para: screen_max_y = 768.
<6>[ 4.653656] ctp_fetch_sysconfig_para: revert_x_flag = 0.
<6>[ 4.669949] ctp_fetch_sysconfig_para: revert_y_flag = 0.
<6>[ 4.686678] ctp_fetch_sysconfig_para: exchange_x_y_flag = 0.
<6>[ 4.706604] ft5x_ts_init: after fetch_sysconfig_para: normal_i2c: 0x38. normal_i2c[1]: 0xfffe
<7>[ 4.733892] script parser fetch err.
<4>[ 4.739458] ctp_init_platform_resource: tp_wakeup request gpio fail!
<6>[ 4.745955] ctp_reset.
<6>[ 4.790950] ctp_detect: Detected chip ft5x_ts at adapter 2, address 0x38
<6>[ 4.797933] ====ft5x_ts_probe begin=====.
<6>[ 4.802197] fts_ctpm_fw_upgrade_with_i_file.
<6>[ 4.912802] =========buf[0] = 0xa6
<6>[ 4.916313] =========buf[1] = 0xa6
<6>[ 4.919798] a == 166, b== 7
<6>[ 5.090518] Step 1: Reset CTPM test
<6>[ 5.130378] Step 2: Enter update mode.
<6>[ 5.150167] ====Step 3:check READ-ID====
<6>[ 5.170068] Step 3: CTPM ID,ID1 = 0x0,ID2 = 0x0
<6>[ 6.680059] Step 4: erase.
<6>[ 6.682863] Step 5: start upgrade.
<6>[ 6.730060] upgrade the 0x0 th byte.
<6>[ 7.060073] upgrade the 0x400 th byte.
<6>[ 7.390074] upgrade the 0x800 th byte.
<6>[ 7.720084] upgrade the 0xc00 th byte.
<6>[ 8.050066] upgrade the 0x1000 th byte.
<6>[ 8.380059] upgrade the 0x1400 th byte.
<6>[ 8.710124] upgrade the 0x1800 th byte.
<6>[ 9.050178] upgrade the 0x1c00 th byte.
<6>[ 9.380077] upgrade the 0x2000 th byte.
<6>[ 9.710075] upgrade the 0x2400 th byte.
<6>[ 10.040082] upgrade the 0x2800 th byte.
<6>[ 10.370093] upgrade the 0x2c00 th byte.
<6>[ 10.700095] upgrade the 0x3000 th byte.
<6>[ 11.030099] upgrade the 0x3400 th byte.
<6>[ 11.360096] upgrade the 0x3800 th byte.
<6>[ 11.690104] upgrade the 0x3c00 th byte.
<6>[ 12.020105] upgrade the 0x4000 th byte.
<6>[ 12.350071] upgrade the 0x4400 th byte.
<6>[ 12.680043] upgrade the 0x4800 th byte.
<6>[ 13.010043] upgrade the 0x4c00 th byte.
<6>[ 13.340034] upgrade the 0x5000 th byte.
<6>[ 13.670041] upgrade the 0x5400 th byte.
<6>[ 14.000046] upgrade the 0x5800 th byte.
<6>[ 14.330038] upgrade the 0x5c00 th byte.
<6>[ 14.660042] upgrade the 0x6000 th byte.
<6>[ 14.990037] upgrade the 0x6400 th byte.
<6>[ 15.320041] upgrade the 0x6800 th byte.
<6>[ 15.660516] Step 6: ecc read 0xcc, new firmware 0x7c.
<6>[ 15.700034] [FTS] upgrade successfully.
<6>[ 15.703878] [FTS] start auto CLB.
<6>[ 16.330523] [FTS] calibration OK.
<6>[ 17.370038] [FTS] store CLB result OK.
<6>[ 17.374138] input: ft5x_ts as /devices/virtual/input/input2
<6>[ 17.379946] ==register_early_suspend =
<6>[ 17.384511] CONFIG_FT5X0X_MULTITOUCH is defined.
<6>[ 17.389219] ctp_set_irq_mode: config gpio to int mode.
<6>[ 17.394508] INTERRUPT CONFIG
<6>[ 17.397948] ==ft5x_ts_probe over =
Please post a link to the rom you used to mess your tablet up in the first place. The solution is not as easy as implied in the freaktablet post.
What android version are you on? You may need to downgrade before you can actually flash the controller firmware.
Hi DoiX,
The rom I used was from the KNC902 that I have downloaded from here: http://www.baidupcs.com/file/我的文档/M...&digest=1f7fbec6fdd0a13774938a40dfddbb53&sh=1
This rom is ICS and my tablet came with ICS too.
I don't know what you mean about downgrading, but my tablet never had any rom lower than ICS in the official homepage.
Do you think I can really recover my touch controller?
Thank you for your time and help!
If above link does not work, use this one:
http://pan.baidu.com/share/link?uk=3459136109&shareid=2349&fr=480365957&fa=480365957
Just hit the white button (below the file date) to start the download.
I'm downloading it now, may take a while. I'm asking what version of ICS you're on, 4.0, 4.0.4, etc. I need to know what kernel is your current rom using, Settings> About tablet. Also, please execute this command: adb shell lsmod and post the result here.
Hi,
I have upload the first available original firmware for my tablet, version 0.6.
This firmware is based on Android ICS 4.0.3 with kernel version 3.0.8+.
This is the dmesg regarding the touch IC flash:
<6>[ 18.290000] ===========================ft5x_ts_init=====================
<6>[ 18.290000] ctp_fetch_sysconfig_para.
<6>[ 18.310000] ctp_fetch_sysconfig_para: after: ctp_twi_addr is 0x38, dirty_addr_buf: 0x38. dirty_addr_buf[1]: 0xfffe
<6>[ 18.330000] ctp_fetch_sysconfig_para: ctp_twi_id is 2.
<6>[ 18.330000] ctp_fetch_sysconfig_para: screen_max_x = 1024.
<6>[ 18.350000] ctp_fetch_sysconfig_para: screen_max_y = 768.
<6>[ 18.360000] ctp_fetch_sysconfig_para: revert_x_flag = 0.
<6>[ 18.370000] ctp_fetch_sysconfig_para: revert_y_flag = 0.
<6>[ 18.370000] ctp_fetch_sysconfig_para: exchange_x_y_flag = 0.
<6>[ 18.380000] ft5x_ts_init: after fetch_sysconfig_para: normal_i2c: 0x38. normal_i2c[1]: 0xfffe
<7>[ 18.390000] script parser fetch err.
<4>[ 18.390000] ctp_init_platform_resource: tp_wakeup request gpio fail!
<6>[ 18.400000] ctp_reset.
<6>[ 18.440000] ctp_detect: Detected chip ft5x_ts at adapter 2, address 0x38
<6>[ 18.450000] ====ft5x_ts_probe begin=====.
<6>[ 18.450000] fts_ctpm_fw_upgrade_with_i_file.
<6>[ 18.570000] =========buf[0] = 0xa6
<6>[ 18.570000] =========buf[1] = 0xa6
<6>[ 18.570000] a == 166, b== 7
<6>[ 18.750000] Step 1: Reset CTPM test
<6>[ 18.790000] Step 2: Enter update mode.
<6>[ 18.810000] ====Step 3:check READ-ID====
<6>[ 18.830000] Step 3: CTPM ID,ID1 = 0x0,ID2 = 0x0
<6>[ 18.830000] ====Step 3:check READ-ID====
<6>[ 18.850000] Step 3: CTPM ID,ID1 = 0x0,ID2 = 0x0
<6>[ 18.850000] ====Step 3:check READ-ID====
<6>[ 18.870000] Step 3: CTPM ID,ID1 = 0x0,ID2 = 0x0
<6>[ 18.870000] ====Step 3:check READ-ID====
<6>[ 18.890000] Step 3: CTPM ID,ID1 = 0x0,ID2 = 0x0
<6>[ 18.890000] [FTS] upgrade failed i_ret = 2.
<6>[ 18.890000] input: ft5x_ts as /devices/virtual/input/input2
<6>[ 18.900000] ==register_early_suspend =
<6>[ 18.900000] CONFIG_FT5X0X_MULTITOUCH is defined.
<6>[ 18.910000] ctp_set_irq_mode: config gpio to int mode.
<6>[ 18.910000] INTERRUPT CONFIG
<6>[ 18.920000] ==ft5x_ts_probe over =
This is lsmod:
8192cu 519648 0 - Live 0xbf0ab000
rtl8150 8910 0 - Live 0xbf0a4000
mcs7830 6557 0 - Live 0xbf09e000
qf9700 8513 0 - Live 0xbf097000
asix 22500 0 - Live 0xbf08c000
usbnet 23745 3 mcs7830,qf9700,asix, Live 0xbf080000
sun4i_lockrotation 2236 2 - Live 0xbf07c000
sun4i_csi0 25693 0 - Live 0xbf071000
mt9m112 11425 1 - Live 0xbf06a000
ov5640 16121 1 - Live 0xbf062000
videobuf_dma_contig 5659 1 sun4i_csi0, Live 0xbf05d000
videobuf_core 18067 2 sun4i_csi0,videobuf_dma_contig, Live 0xbf053000
mma7660 5671 0 - Live 0xbf04d000
mali 129534 4 - Live 0xbf020000
ump 42202 9 mali, Live 0xbf00f000
ft5x_ts 42329 0 - Live 0xbf000000
Hope this is what you want to know.
Thanks again for any help!
Yep, thats what i wanted .
I've flashed the rom, TS dead, time to do some serious debugging.
P.S Could you upload the modded ft5x_ts.ko file?
Edit: i'm looking through the original firmware right now to find how it flashed over/removed the eeprom in the first place then reverse the process with a proper IC firmware.
Hi DoiX,
I'm attaching the modded ft5x_ts.ko I think. I've tested so many ft5x_ts.ko that I don't remember if it was this one.
This modded ft5x_ts.ko file should ignore the ID Read error at step 3 and the ECC check at step 6.
Hope this will help you fix the touch IC controller.
Thanks!
Just a question, do you think the IC flash happend when the tablet boot up on the first time or is it done while flashing with LiveSuit?
I've read here http://forum.xda-developers.com/showthread.php?t=1629478 that in the Nook Tablet they where unable to flash the IC touch controller because the ft5x_ts.ko driver is not able to detect the ID on ICS and to do that, they downgraded to Gingerbread.
I can't test this, because I don't have any Gingerbread rom that could work on my tablet.
Maybe this info could help you further.
I got a gingerbread rom around, i'll test it. I can't tell if it was during live suite or during first boot. If it was during livesuite it probably used a direct to chip flash method that doesn't involve android. If this is the case it's possible that the ownership got messed up (which shouldn't even happen). For now, i didn't find anything related to i2c in the rom.
Here is the post where someone had the same problem while flashing the IC controller, the driver can not read the ID from the IC:
http://forum.xda-developers.com/showpost.php?p=33566499&postcount=70
Here is someone writting an app that will flash the firmware to the IC controller:
http://forum.xda-developers.com/showpost.php?p=34081048&postcount=91
Maybe he can help you. I have tried to post on their thread, but my post was deleted because my tablet was not a Nook one...
The Nook uses a particular android version, i'm not sure it even works on A10 tablets. Anyway, the situation looks grim, for both of us now . I'll have to compile the kernel myself and find a way to bypass the errors. The .ko file you posted doesn't really flash from what i could tell, it just rolls the output of what a successful flash would look like
You could just replace the chip/touchscreen on the device and the situation will be fixed.
So you think we can not recover our IC touch controller?
How do you think the Nook guys have done it?
What do you mean about changing the chip/touch?
I'm sure it can be recovered by a direct eeprom rewrite, like the guys on the Nook forums did or via eeprom programmer.
Earlier today i tried manually resetting the chip based on the datasheet i found http://www.displayfuture.com/Display/datasheet/controller/FT5x06.pdf Unfortunately i wasn't successful, this data sheet doesn't say exactly how to reset it.
By changing the chip/touch i mean this: 1. replace the touchscreen completely (as the problem lies with the corrupted IC controller (which is a microprocessor). 2. order the chip online (it can be found) and solder it on the touchscreen instead of the "bad" one.
I've asked the guy from Nook tablet thread who is making the flash software and he told me that he recompiled the driver without the ID read check.
I think he made the same as the patched driver I post earlier and it worked. What I think is that this procedure only works for upgrading an older firmware and not flash an empty eeprom. Can it be?
Hi DoiX,
I think we can recover our touch! But I need your help if you know how to compile the driver.
This is what I found from the guy at Nook tablet thread after I showed him the results of the patched driver we have tested:
Yeah, I had same result after removing CTPM chek on old driver. Someone brokes flashing firmware from it. We succesfully setuped flashing only on new driver: https://github.com/Kuzma30/kernel3NookTablet/commit/9da5fade51895577cf09414021d148a72caa9572
Click to expand...
Click to collapse
So, the problem is our driver! They already fixed the update on the driver, but I don't know how to compile it to a valid ft5x_ts.ko.
Do you know how to do it?
Hope this is our salvation!
Hey, i'm already on it. Been trying for the past hours to find the proper kernel sources for my tablet so i can try modifying the kernel.
I'm having problems locating an upgrade enabled ft5x_ts.c kernel file that is compatible with our devices, feel free to help me find one.
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.
<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)
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
My G5 has been crashing a lot since I got it, I did a factory rest hoping it was a firmware issue, but then it crashed and I didn't noticed. So I turned it on, and almost immediately after the boot it crash and it won't turn on anymore. Is it just some sort of hardware failure? Is anyone else having this issue?
Same here, after the battery drains it will turn on eventually, but in my case it was stuck in a bootloop, so im going to exchange on warranty. I think it is a hardware issue.
If you are succefull booting it up the first thing try updating it and see if it fixes it
Same thing happened to me i was taking a picture the phone had about 40% charge froze then shut down got stuck in lg boot screen for a while then shutdown now won't charge boot nothing like its dead tried plug it in to my computer doesn't recognize it pulled the battery nothing it's LG-H831... Anyone any suggestions?
did you factory reset using the power and volume button or the menu.
I've tried hold down the Volume Down and Power button together to boot nothing like the phone is dead.. I won the phone from wind and it worked well for like 10 days. Thanks in advanced..
I was beginning to think if was just me!
I'm now on my third phone because of this problem. Happened once so soon after launch that AT&T had no reconditioned phones and gave me a new one for the warranty replacement. That one failed with the same problem within about 2 weeks. In both of those cases I had just removed the battery, so I thought the problem was in that somewhere.
However, on this third( reconditioned) phone, this morning I woke to find that it had shut down over night, even though it was plugged in to a dock ( not the OEM charger ). Now it won't charge/boot/etc.
At this point the only thing I can think of is that it's related to using non OEM charger s or cables.
Is there such a thing as a lemon law for phones?
I lost one too. It began restarting once or twice a day for about three days, then I plugged it in and it shut down. Nothing would restart it. I had to get a replacement.
Sent from my LG-H830 using Tapatalk
what a bad story
I use the original cable (i only have that with usb-c) but different wall adapter but fortunately I don't have that issue (i'm no longer under warranty because of bootloader unlock...too bad for me)
I won the LG-H831 from Wind Mobile so no warranty LG is charging me 169.49 CAD flat rate plus one way shipping. I did have too Sim Unlock it to work on rogers I think the phone was a lemon i did nothing at all to the phone no mods just google play store updates. and used it for about 10 day's I sent the phone back to LG Canada on Friday. I'm DMing @LGCanada in twitter hoping they can tell me what happened to the phone so i can report it here to see how common this is. I kind of think this should maybe in the boot loop thread until it died. I will keep the thread updated as to what happened if they do tell me the truth..
had the same problem. started with boot looping and eventually bricked.
Had to send it to LG for repairs. The cause on the update email was PMIC failure. This is apparently pretty common, at least with the first batch of G5s. Sprint wouldn't touch it...only offered to file an insurance claim for me and stick me with a deductible or charge me $75 to diagnose the problem at the service center.
LG asked me to send the phone back and repaired it under warranty but it was out for almost 2 weeks.
It appears to be the same problem the G4s suffered from...the power management module fails. Nobody is admitting anything but from the conversations I had (and the little info I was asked for) it sounds like they're aware of the problem and deal with it quite often.
I should have my phone back today so we'll see how it works after the repair.
I called LG Canada yesterday about the status of my G5, They said the motherboard needed to be replaced and they ordered it and i would receive a email when it was complete. Just wanted to update the thread on what the fault was..
Update Got my LG G5 (LG-H831) back this morning after 9 days and now the WiFi didn't work, it would take my password show icon but no connection to router. When Google tried to update with Data off and WiFi on it said No Network Available. Carrier data worked no problems So i sent it back again after calling LG trying to resolve the problem without success .. Lemon
Mine only lasted 13 hours before I had to send it for repair. I was still restoring my data until sudden crash following by reboot which immediately crashed again for about 3~4 loops and it doesn't boot up at all. Charging did nothing, new battery didn't help, leaving the battery out for few hours didn't help. So now my H815 is off to repair (bootloop, and if they can repair at all since I am in Canada) and now the LG G5 went to the same repair shop (FutureTel). LG needs to step up their game.
I'm having similar problems, my G5 (Verizon) has been locking up and then crashing/rebooting at least 3 - 4 times a day, usually in the middle of doing something important. It's really annoying and I'm contacting LG for help.
Those whom have had problems, what is you manufactured Date? Mine was 03/2016.
Just got an H831 a week ago but it's been freezing + rebooting more and more often... very frustrating. Sometimes it crashes hard enough the power button doesn't work and I have to remove/reinsert the battery. Software version is H831 10a and apparently that's the latest available.
I captured a bug report, the dmesg kernel log is below. Can anyone tell me if there's signs of a Power Management IC failure like others have reported?
Code:
------ KERNEL LOG (dmesg) ------
<3>[ 0.410484 / 01-01 00:00:00.409][2] rpm_vreg_device_probe: regulator_register failed: pmi8994_boost_5v, rc=-517
<6>[ 0.410508 / 01-01 00:00:00.409][2] platform soc:qcom,rpm-smd:rpm-regulator-bstb:regulator-bst: Driver qcom,rpm-smd-regulator requests probe deferral
<6>[ 0.410705 / 01-01 00:00:00.409][2] pmi8994_boost_pin_ctrl: no parameters
<3>[ 0.410754 / 01-01 00:00:00.409][2] qcom,rpm-smd-regulator soc:qcom,rpm-smd:rpm-regulator-bstb:regulator-bst-pin-ctrl: Failed to find supply parent
<3>[ 0.410849 / 01-01 00:00:00.409][2] rpm_vreg_device_probe: regulator_register failed: pmi8994_boost_pin_ctrl, rc=-517
<6>[ 0.410873 / 01-01 00:00:00.409][2] platform soc:qcom,rpm-smd:rpm-regulator-bstb:regulator-bst-pin-ctrl: Driver qcom,rpm-smd-regulator requests probe deferral
<6>[ 0.411616 / 01-01 00:00:00.409][2] msm_thermal:sensor_mgr_init_threshold threshold id already initialized
<6>[ 0.411643 / 01-01 00:00:00.409][2] msm-thermal 70000.qcom,msm-thermal: probe_vdd_mx:Failed reading node=/soc/qcom,msm-thermal, key=qcom,mx-restriction-temp. KTM continues
<3>[ 0.411897 / 01-01 00:00:00.409][2] msm_thermal:update_cpu_freq Unable to update policy for cpu:0. err:-19
<3>[ 0.411916 / 01-01 00:00:00.409][2] msm_thermal:update_cpu_freq Unable to update policy for cpu:2. err:-19
<3>[ 0.411932 / 01-01 00:00:00.409][2] msm_thermal:update_cpu_freq Unable to update policy for cpu:2. err:-19
<3>[ 0.412736 / 01-01 00:00:00.409][2] msm_thermal:update_cpu_freq Unable to update policy for cpu:0. err:-19
<3>[ 0.412755 / 01-01 00:00:00.409][2] msm_thermal:update_cpu_freq Unable to update policy for cpu:2. err:-19
<3>[ 0.412770 / 01-01 00:00:00.409][2] msm_thermal:update_cpu_freq Unable to update policy for cpu:2. err:-19
<6>[ 0.412994 / 01-01 00:00:00.409][2] pmi8994_boost_5v: no parameters
<3>[ 0.413057 / 01-01 00:00:00.409][2] qcom,rpm-smd-regulator soc:qcom,rpm-smd:rpm-regulator-bstb:regulator-bst: Failed to find supply parent
<3>[ 0.413162 / 01-01 00:00:00.409][2] rpm_vreg_device_probe: regulator_register failed: pmi8994_boost_5v, rc=-517
<6>[ 0.413186 / 01-01 00:00:00.409][2] platform soc:qcom,rpm-smd:rpm-regulator-bstb:regulator-bst: Driver qcom,rpm-smd-regulator requests probe deferral
<6>[ 0.413378 / 01-01 00:00:00.409][2] pmi8994_boost_pin_ctrl: no parameters
<3>[ 0.413426 / 01-01 00:00:00.409][2] qcom,rpm-smd-regulator soc:qcom,rpm-smd:rpm-regulator-bstb:regulator-bst-pin-ctrl: Failed to find supply parent
<3>[ 0.413522 / 01-01 00:00:00.409][2] rpm_vreg_device_probe: regulator_register failed: pmi8994_boost_pin_ctrl, rc=-517
<6>[ 0.413545 / 01-01 00:00:00.409][2] platform soc:qcom,rpm-smd:rpm-regulator-bstb:regulator-bst-pin-ctrl: Driver qcom,rpm-smd-regulator requests probe deferral
<6>[ 0.413917 / 01-01 00:00:00.409][3] gdsc_mmagic_video: no parameters
<6>[ 0.414224 / 01-01 00:00:00.409][3] gdsc_mmagic_mdss: no parameters
<6>[ 0.414498 / 01-01 00:00:00.409][3] gdsc_mmagic_camss: no parameters
<6>[ 0.414837 / 01-01 00:00:00.409][3] gdsc_venus: no parameters
<6>[ 0.414879 / 01-01 00:00:00.409][3] gdsc_venus: supplied by gdsc_mmagic_video
<6>[ 0.415157 / 01-01 00:00:00.409][3] gdsc_venus_core0: fast normal
<6>[ 0.415432 / 01-01 00:00:00.409][3] gdsc_venus_core1: fast normal
<6>[ 0.415719 / 01-01 00:00:00.409][3] gdsc_camss_top: no parameters
<6>[ 0.415759 / 01-01 00:00:00.409][3] gdsc_camss_top: supplied by gdsc_mmagic_camss
<6>[ 0.416045 / 01-01 00:00:00.409][3] gdsc_vfe0: no parameters
<6>[ 0.416083 / 01-01 00:00:00.409][3] gdsc_vfe0: supplied by gdsc_camss_top
<6>[ 0.416354 / 01-01 00:00:00.409][3] gdsc_vfe1: no parameters
<6>[ 0.416390 / 01-01 00:00:00.409][3] gdsc_vfe1: supplied by gdsc_camss_top
<6>[ 0.416673 / 01-01 00:00:00.409][3] gdsc_mdss: no parameters
<6>[ 0.416712 / 01-01 00:00:00.409][3] gdsc_mdss: supplied by gdsc_mmagic_mdss
<6>[ 0.417147 / 01-01 00:00:00.409][3] gdsc_jpeg: no parameters
<6>[ 0.417183 / 01-01 00:00:00.409][3] gdsc_jpeg: supplied by gdsc_camss_top
<6>[ 0.417454 / 01-01 00:00:00.409][3] gdsc_cpp: no parameters
<6>[ 0.417489 / 01-01 00:00:00.409][3] gdsc_cpp: supplied by gdsc_camss_top
<6>[ 0.417746 / 01-01 00:00:00.409][3] gdsc_pcie_0: no parameters
<6>[ 0.417988 / 01-01 00:00:00.409][3] gdsc_pcie_1: no parameters
<6>[ 0.418235 / 01-01 00:00:00.409][3] gdsc_pcie_2: no parameters
<6>[ 0.418470 / 01-01 00:00:00.409][3] gdsc_usb30: no parameters
<6>[ 0.418720 / 01-01 00:00:00.409][3] gdsc_ufs: no parameters
<6>[ 0.419002 / 01-01 00:00:00.409][3] gdsc_fd: no parameters
<6>[ 0.419037 / 01-01 00:00:00.409][3] gdsc_fd: supplied by gdsc_camss_top
<6>[ 0.419306 / 01-01 00:00:00.409][3] gdsc_gpu: no parameters
<6>[ 0.419596 / 01-01 00:00:00.409][3] gdsc_gpu_gx: no parameters
<6>[ 0.419709 / 01-01 00:00:00.409][3] gdsc_gpu_gx: supplied by gfx_corner
<6>[ 0.419974 / 01-01 00:00:00.409][3] gdsc_hlos1_vote_aggre0_noc: no parameters
<6>[ 0.420285 / 01-01 00:00:00.419][3] gdsc_hlos1_vote_lpass_adsp: no parameters
<6>[ 0.420537 / 01-01 00:00:00.419][3] gdsc_hlos1_vote_lpass_core: no parameters
<6>[ 0.420787 / 01-01 00:00:00.419][3] gdsc_aggre0_noc: no parameters
<3>[ 0.482048 / 01-01 00:00:00.479][3] qcom,qpnp-pin qpnp-pin-ffffffc0f8769c00: qpnp_pin_probe: no device nodes specified in topology
<4>[ 0.482084 / 01-01 00:00:00.479][3] qcom,qpnp-pin: probe of qpnp-pin-ffffffc0f8769c00 failed with error -22
<3>[ 0.482667 / 01-01 00:00:00.479][3] qcom,qpnp-pin qpnp-pin-ffffffc0f8794000: qpnp_pin_probe: no device nodes specified in topology
<4>[ 0.482691 / 01-01 00:00:00.479][3] qcom,qpnp-pin: probe of qpnp-pin-ffffffc0f8794000 failed with error -22
<6>[ 0.483773 / 01-01 00:00:00.479][3] KPI: Bootloader start count = 57585
<6>[ 0.483788 / 01-01 00:00:00.479][3] KPI: Bootloader end count = 159063
<6>[ 0.483800 / 01-01 00:00:00.479][3] KPI: Bootloader display count = 74440
<6>[ 0.483812 / 01-01 00:00:00.479][3] KPI: Bootloader load kernel count = 3606
<6>[ 0.483825 / 01-01 00:00:00.479][3] KPI: Kernel MPM timestamp = 182032
<6>[ 0.483836 / 01-01 00:00:00.479][3] KPI: Kernel MPM Clock frequency = 32768
<6>[ 0.483862 / 01-01 00:00:00.479][3] socinfo_print: v0.11, id=246, ver=3.1, raw_id=2375, raw_ver=4, hw_plat=8, hw_plat_ver=12
<6>[ 0.483862 / 01-01 00:00:00.479][3] accessory_chip=0, hw_plat_subtype=0, pmic_model=65545, pmic_die_revision=131072 foundry_id=3 serial_number=746745691 num_pmics=2
<6>[ 0.484140 / 01-01 00:00:00.479][3] gdsc_mmagic_bimc: no parameters
<6>[ 0.484893 / 01-01 00:00:00.479][3] usb_otg_vreg: no parameters
<3>[ 0.484962 / 01-01 00:00:00.479][3] reg-fixed-voltage soc:usb-otg-switch: Failed to find supply vin
<3>[ 0.485073 / 01-01 00:00:00.479][3] reg-fixed-voltage soc:usb-otg-switch: Failed to register regulator: -517
<6>[ 0.485099 / 01-01 00:00:00.479][3] platform soc:usb-otg-switch: Driver reg-fixed-voltage requests probe deferral
<6>[ 0.485265 / 01-01 00:00:00.479][3] rome_vreg: no parameters
<6>[ 0.485975 / 01-01 00:00:00.479][3] vgaarb: loaded
<5>[ 0.487415 / 01-01 00:00:00.479][3] SCSI subsystem initialized
<6>[ 0.488451 / 01-01 00:00:00.479][3] usbcore: registered new interface driver usbfs
<6>[ 0.488512 / 01-01 00:00:00.479][3] usbcore: registered new interface driver hub
<6>[ 0.488667 / 01-01 00:00:00.479][3] usbcore: registered new device driver usb
<4>[ 0.489068 / 01-01 00:00:00.479][3] soc:usb_nop_phy supply vcc not found, using dummy regulator
<6>[ 0.489729 / 01-01 00:00:00.479][3] media: Linux media interface: v0.10
<6>[ 0.489785 / 01-01 00:00:00.479][3] Linux video capture interface: v2.00
<6>[ 0.492078 / 01-01 00:00:00.489][3] cpufreq: driver msm up and running
<6>[ 0.492665 / 01-01 00:00:00.489][3] platform soc:qcom,ion:qcom,[email protected]: assigned reserved memory node qseecom_region
<6>[ 0.492795 / 01-01 00:00:00.489][3] platform soc:qcom,ion:qcom,[email protected]: assigned reserved memory node secure_region
<6>[ 0.493010 / 01-01 00:00:00.489][3] ION heap system created
<6>[ 0.493100 / 01-01 00:00:00.489][3] ION heap kmalloc created
<6>[ 0.493112 / 01-01 00:00:00.489][3] ION heap qsecom created at 0x00000000fe800000 with size 1400000
<6>[ 0.493121 / 01-01 00:00:00.489][3] ION heap secure_display created at 0x00000000f8c00000 with size 5c00000
<6>[ 0.493131 / 01-01 00:00:00.489][3] ION heap secure_heap created
<3>[ 0.494139 / 01-01 00:00:00.489][0] msm_bus_fabric_init_driver
<<< continues but I'm at the character limit >>>
4/2016
Same problem here. Mine died as I was listening to music and taking a picture, I thought it overloaded, after shutdown I couldn't get it back on no matter what.
My question is did any of you guys recover your data? I have photos, notes on it that I would absolutely hate to lose... PC won't recognize the phone while it's bricked like this. Do you think ATT might be able to save my stuff?
This is my third phone . First phone crashed when I was installing whats app after 15 min when I bought first phone. Then I got another phone that also crashed after 30 min. Third phone worked for a month and yesterday suddenly battery drained and it didn't turn on after that.
lgg5crashed said:
This is my third phone . First phone crashed when I was installing whats app after 15 min when I bought first phone. Then I got another phone that also crashed after 30 min. Third phone worked for a month and yesterday suddenly battery drained and it didn't turn on after that.
Click to expand...
Click to collapse
Definitely waiting 5-6 months after launch to get LG G6. Knock on wood don't have problems some people have. Got newer version when I purchased G5. Did that on purpose because of what I read. Tell those bastards at LG to give you newer version? That's ridiculous your going through that and others. If that happened to me wouldn't buy an LG for a long time.
Sent from my LGE LG-H830 using XDA Labs