Can you help me with this:
My tablet Galaxy Tab 10.1, after reset pressing power button 15 seconds making a soft reset because freeze loading an app, not load touchscreen driver.
Dmesg message:
<6>[ 7.163493] mXT1386: mxt_probe
<6>[ 7.163501] maXTouch driver
<6>[ 7.163507] "sec_touch"
<6>[ 7.163513] addr: 0x004c
<6>[ 7.163519] irq: 220
<6>[ 7.163525] flags: 0x0000
<6>[ 7.163531] adapter:"Tegra I2C adapter"
<6>[ 7.163537] device: "(null)"
<3>[ 7.163685] tegra-i2c tegra-i2c.1: I2c error status 0x00000008
<3>[ 7.169602] tegra-i2c tegra-i2c.1: no acknowledge from address 0x4c
<3>[ 7.176023] tegra-i2c tegra-i2c.1: Packet status 0x00010009
<6>[ 7.182700] Warning: To wake up touch-ic in deep sleep, retry i2c communication!
<3>[ 7.222752] tegra-i2c tegra-i2c.1: I2c error status 0x00000008
<3>[ 7.228727] tegra-i2c tegra-i2c.1: no acknowledge from address 0x4c
<3>[ 7.235061] tegra-i2c tegra-i2c.1: Packet status 0x00010009
<3>[ 7.241798] sec_touch 1-004c: Failure accessing maXTouch device
<3>[ 7.247800] sec_touch 1-004c: Chip could not be identified
<6>[ 7.253434] p3_touch_exit_hw
<4>[ 7.253455] sec_touch: probe of 1-004c failed with error 255
<6>[ 7.253510] Successfully added driver sec_touch
How can I sure of if is a hardware issue or a configuration issue?
I clean cache, data, system folders from CWM and reinstall stock rom p7510uekmm and nothing happend
I had this problem with my Galaxy Tab and tried the ideas mentioned above but it just didn't work for me. I have, however, figured out what's really going wrong.
I always had this failure showing up in dmesg:
tegra-i2c tegra-i2c.1: no acknowledge from address 0x4c
So, it can't read from the touchscreen controller at address 0x4c because the chip isn't responding. One fix mentioned was to re-write the configuration, with the assumption that the device was somehow wedged. That doesn't work either, since you can't write to 0x4c - same lack of acknowledgement. So, if 0x4c is the right address, the chip must be dead, right?
I tried adding a reset. No change. Disconnected the battery overnight. Also no change.
Then, I realized what's going on. The MXT1386 has a "Firmware Update" mode. When you put it into update mode, the device address changes from 0x4c to 0x26! Once it gets into that mode, it doesn't respond to the original address. Since I don't have the docs for the device, and thus don't know how to get out of firmware update mode, I updated the Linux kernel to call the driver function that updates the firmware. Once that process is complete and the chip reset, it reverts to its original address. At that point (after a final reboot), all is well.
I have a replacement kernel that you can install and boot which re-enables the touchpad. I'd suggest making a nandroid backup first, installing my kernel, then restoring the nandroid once it's fixed.
It's trying to contact the touch controller over the I2C bus and failing. It does one retry and then gives up. The address 0x4C is correct for the mXT1386 on that unit.
You should try a hard power off/on by taking out the battery.
You could try taking apart the
unit and reseating the connector to the touch controller. It is
on a separate board connected with a flexi cable which might have become dislodged.
Another possibility is that the touch chip itself is damaged.
Related
I am trying to connect to my Wifi router with my Xiaomi Mi Max 2. I can connect to every router, but not to this one. Also, every other phone can connect to that router. I already tried changing protocols or resetting the router / phone.
Looking at logcat, I get the following:
wpa_supplicant: wlan0: Event ASSOC_REJECT (12) received
wlan0: CTRL-EVENT-ASSOC-REJECT bssid=6c:99:24:0f:51:d2 status_code=1
wpa_supplicant: Continuous association failures - consider temporary network disabling
wpa_supplicant: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED [...]
Does anyone know what's going on and how I can solve this?
Best,
Trim
I have a ViewSonic touch screen display connected to an Android PC (kernel 3.0.36+) via HDMI & USB. The display shows everything correctly. Furthermore, the Linux kernel recognizes it.
dmesg:
<6>[ 99.699034] usb 2-1.2.3: new full speed USB device number 8 using usb20_host
<6>[ 99.800896] usb 2-1.2.3: New USB device found, idVendor=0408, idProduct=3008
<6>[ 99.800993] usb 2-1.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=4
<6>[ 99.801099] usb 2-1.2.3: Product: OpticalTouchScreen
<6>[ 99.801169] usb 2-1.2.3: Manufacturer: Quanta
<6>[ 99.801226] usb 2-1.2.3: SerialNumber: 0000
<4>[ 99.805402] quirks: 0x00000000
The problem is that the screen, while I can touch anywhere, only registers the tap at the curser location (wireless keyboard/mouse connected). If I move the cursor and tap anywhere on the screen, the new location receives the tap. If I remove the keyboard/mouse dongle the behavior remains, but now I can't move the cursor.
The USB connection to the monitor is being displayed (highlighted) in dev/usb:
Input device configuration file located in /system/usr/idc/Vendor_0408_Product_3008.idc
# Input device configuration file.
# This is an external device, attached to the USB or Bluetooth bus.
device.internal = 0
# The device should behave as a touch screen, which uses the same orientation
# as the built-in display.
touch.deviceType = touchScreen
touch.orientationAware = 0
touch.gestureMode = spots
# Orientation
touch.orientation.calibration = vector
# Output Ranges
output.width = 1920
output.height = 1080
output.diag = sqrt(output.width ^2 + output.height ^2)
Any guidance or suggestions are appreciated!
I try to connect 2 Android devices via WiFi Direct so that I could use Miracast sometime but always get the same error.
Im working 3 days on that now but can't figure out, why this isnt working.
My logcat error:
I/wpa_supplicant( 4244): p2p0: P2P-FIND-STOPPED
D/myOnda ( 4533): onReceive action:android.net.wifi.p2p.DISCOVERY_STATE_CHANGE
D/myOnda ( 4533): Discovery state changed: 1 ->1:stop, 2:start
I/ethernet( 3755): event: NEWLINK(16), flags=0X1002
I/ethernet( 3755): flags: BC MC
I/ethernet( 3755): poll state :(null):17:
I/wpa_supplicant( 4244): p2p0: Failed to start AP functionality
V/EthernetStateTracker( 3755): report new state DISCONNECTED on dev (null) current=null
Ok it says "Failed to start AP functionality" but I just don't know how and where to solve that.
I try that connection 1 time with a Samsung Note Pro and 1 time with a Nexus 4 and it's always the same.
Another curious part is that the mac is always different from the original (found that here too).
I want to discover all Android devices IP and Port in same wifi network using ZeroMQ?
My app basically connect all device in same wifi network (no internet needed) and message to each other. Once ip and port I know I am send message successfully but how to know all device internet Protocol (ip) Using ZeroMQ?
Principle
Part A)
Every IEEE 802.x CSMA/CD network "collision domain" ( wifi AP/SSID is such one ) has to be managed so as to work well. Thus the Address Resolution Protocol [ARP] will help you in the task to find all ISO-OSI-Layer-3 IP Addresses. Wifi Access Point [AP] host, to which all live devices register and handshake with, is the choice to start with.
HG520i> ip arp status
received 54205 badtype 0 bogus addr 0 reqst in 12105 replies 196 reqst out 14301
cache hit 63152696 (24%), cache miss 19455672 (23%)
IP-addr Type Time Addr stat iface
192.168.0.230 10 Mb Ethernet 290 00:15:af:e6:b1:79 41 enif0
192.168.0.62 10 Mb Ethernet 300 00:0c:29:98:d4:3b 41 enif0
192.168.0.55 10 Mb Ethernet 300 00:27:0e:07:c5:9e 41 enif0
192.168.0.255 10 Mb Ethernet 0 ff:ff:ff:ff:ff:ff 43 NULL
num of arp entries= 4
Part B)
Scanning all the ports on all the known IP hosts is a dumb brute force approach to the second issue.
Scanning just a subset of "reasonable" ones would save you both the time and efforts on peer-recognitions.
Using some smarter, active "visibility self-advertisement policy" will save you even more.
Solution
Decide on multi-party system architecture, whether an individual passive scan, a central/distributed proxy-assisted scan or an active self-advertisement policy will be used to build and maintain live records in a neighbouring hosts register.
ZeroMQ per-se brings you a lot of power for the smart solutions, while the dumb-force solutions would have to wait till fully fledged ZeroMQ services will be ready. Low level L2/L3-inspections will have to bring their fruit before ZeroMQ can first .bind()/.connect()
Needless to say, that uncoordinated CSMA/CD networks do not guarantee that all the L2-visible hosts will have "compatible" L3-ip-adddress ( will belong to / have the same L3-ip-network address ).
Thus you never know about all IP addresses without a truly low-level sniffer.
I want to connect a custom device with cp2102 to Android powered tablet. I connect it in VCP mode (using PID EA60) and use JavaComm to find it,
#SuppressWarnings("unchecked")
Enumeration <CommPortIdentifier> ports = CommPortIdentifier.getPortIdentifiers();
while (ports.hasMoreElements())
{
final CommPortIdentifier port = ports.nextElement();
Log.d(null, port.toString());
}
but I never enter the loop.
I have an option to use FTDI instead of silabs. They have a variant of using their D2xx dll through JNI. I followed their guide but I have a memory crash (signal something and heap corrupted message in LogCat), when I connect ft232r and try to determine the number of connected devices. When I unplug the device from the tablet, the same code (their sample code) works just fine, returning zero, which is true.
When I use JavaComm with FTDI the result is the same as with cp2102: the loop is not entered.
I guess I miss something or do something wrong.
If I'm to use, say, usb-mode instead of VCP, I'm ready to start searching, I just need a hint.
Any help would be greatly appreciated.
The issue here is that the CP210x driver is not enabled in the Android kernel by default. So you will either need to build this driver in to your kernel to get the tty access and ability to use JavaComm.
The other option is to use the USB Host functionality and access your CP210x directly with it's API.