Database Users

[Q][Kernel] Support for HIDRAW devices

Hi there,
I am trying to port this: engadget. com /2011 /09 /16 / brain-scanner-app-lets-you-show-off-your-smarts-on-the-go (I can't post links, sorry) to the Acer A500 with Android 3.1. This requires connecting the receiver to the tablet and reading raw binary data it feeds through the USB port.
The way it was done for the Nokia N900 was to compile the hidraw.ko kernel module and insmod it on the device. I thought it would be the same for Android. I did the following:
1) I downloaded the source code of the 2.6.36.3 kernel and the toolchains from github
2) I pulled the default config from the device
3) Changed
Code:
#CONFIG_HIDRAW is not set
to
Code:
CONFIG_HIDRAW=y
and
Code:
CONFIG_USB_HID=y
4) Compiled modules with cross compilation
5) got only usbhid.ko and some other irrelevant modules but no hidraw.ko
6) Could not even insmod usbhid.ko, because it is already loaded. Could not rmmod the current usbhid.ko (I do have root).
7) When I plug the receiver into the USB port it is recognized, but then the dmesg says:
Code:
<6>[ 1591.572355] usb 1-1: new full speed USB device using tegra-ehci and address 2
<6>[ 1593.633364] usb 1-1: New USB device found, idVendor=1234, idProduct=ed02
<6>[ 1593.634022] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 1593.634377] usb 1-1: Product: Receiver Dongle L01
<6>[ 1593.635002] usb 1-1: Manufacturer: Emotiv Systems Pty Ltd
<6>[ 1593.635350] usb 1-1: SerialNumber: SNXXXXXXXXXXXXXX
<3>[ 1593.651672] generic-usb 0003:1234:ED02.0001: claimed by neither input, hiddev nor hidraw
<3>[ 1593.662383] generic-usb 0003:1234:ED02.0002: claimed by neither input, hiddev nor hidraw
Finally the question is:
How to enable HIDRAW on the Acer A500 and get this thing to work?

[Q] how can I debug otg connections

SOLVED: defective otg cable
useful tools:
any android terminal emulator plus root
dmesg
lsusb
2nd otg cable
I cannot seem to get otg working with any of the various USB storage devices I have.
Any ideas on how I can debug this?
If it were normal Linux it would be easy enough, however it's not.
Any suggestions would be appreciated.
Running AOKP buttered right now but sentinel stock and paranoid all do not work either. So it might be a cable or the tablet even.
Hmm not sure but I wonder if the kernel with this rom is missing the fat kernel modules
Thanks
Sent from my Nexus 10 using xda premium

tazmeister said:
I cannot seem to get otg working with any of the various USB storage devices I have.
Click to expand...
Click to collapse
I had the same problems with rooted Stock and various custom ROMs. Try installing "USB OTG Helper [root]" then retest. This app helped get me RW access to OTG storage from SD cards to powered HDD drives in various formats (ext2,3,4 and NTFS).
It worked so well I paid for the donate version just to support the developer. It even has exFAT support although I never tried it. Personally I think it should be part of standard Android.

Have you checked "lsusb" or "udevadm" in terminal if the device recognizes anything?

KasF said:
Have you checked "lsusb" or "udevadm" in terminal if the device recognizes anything?
Click to expand...
Click to collapse
Thanks more commands to jog my memory and try
I installed a console app and can check dmesg and other stuff.
Lsmod and related seem to be mostly obsolete.
Dmesg shows something is seen but the system keeps failing after this.
I see the same messages regardless of which device I try, powered and unpowered.
<6>[ 6171.135316] s5p-ehci s5p-ehci: S5P EHCI Host Controller
<6>[ 6171.136622] s5p-ehci s5p-ehci: new USB bus registered, assigned bus number 1
<6>[ 6171.137173] s5p-ehci s5p-ehci: irq 103, io mem 0x12110000
<6>[ 6171.145031] s5p-ehci s5p-ehci: USB 0.0 started, EHCI 1.00
<6>[ 6171.145636] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
<6>[ 6171.146150] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[ 6171.146439] usb usb1: Product: S5P EHCI Host Controller
<6>[ 6171.146925] usb usb1: Manufacturer: Linux 3.4.5-gb44fbc0 ehci_hcd
<6>[ 6171.147202] usb usb1: SerialNumber: s5p-ehci
<6>[ 6171.150947] hub 1-0:1.0: USB hub found
<6>[ 6171.151298] hub 1-0:1.0: 3 ports detected
<6>[ 6171.153725] exynos-ohci exynos-ohci: EXYNOS OHCI Host Controller
<6>[ 6171.156783] exynos-ohci exynos-ohci: new USB bus registered, assigned bus number 2
<6>[ 6171.157031] exynos-ohci exynos-ohci: irq 103, io mem 0x12120000
<6>[ 6171.214330] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
<6>[ 6171.214522] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[ 6171.214630] usb usb2: Product: EXYNOS OHCI Host Controller
<6>[ 6171.214813] usb usb2: Manufacturer: Linux 3.4.5-gb44fbc0 ohci_hcd
<6>[ 6171.215052] usb usb2: SerialNumber: exynos-ohci
<6>[ 6171.220588] hub 2-0:1.0: USB hub found
<6>[ 6171.220946] hub 2-0:1.0: 3 ports detected
<6>[ 6171.225049] manta_otg manta_otg_work: b_idle -> a_host
<6>[ 6171.705161] usb 2-1: new full-speed USB device number 2 using exynos-ohci
<3>[ 6171.835100] usb 2-1: device descriptor read/64, error -62
<3>[ 6172.070121] usb 2-1: device descriptor read/64, error -62
<6>[ 6172.300093] usb 2-1: new full-speed USB device number 3 using exynos-ohci
<3>[ 6172.430142] usb 2-1: device descriptor read/64, error -62
<3>[ 6172.665754] usb 2-1: device descriptor read/64, error -62
<6>[ 6172.895140] usb 2-1: new full-speed USB device number 4 using exynos-ohci
<3>[ 6173.305043] usb 2-1: device not accepting address 4, error -62
<6>[ 6173.430032] usb 2-1: new full-speed USB device number 5 using exynos-ohci
<3>[ 6173.840038] usb 2-1: device not accepting address 5, error -62
<3>[ 6173.840490] hub 2-0:1.0: unable to enumerate USB device on port 1
Sent from my Nexus 10 using xda premium

None of the org helper apps have helped.
I don't think the org cable is bad though maybe this detail means otherwise
one device starts charging itself of the musb port when i plug it in.
Sent from my Nexus 10 using xda premium

KasF said:
Have you checked "lsusb" or "udevadm" in terminal if the device recognizes anything?
Click to expand...
Click to collapse
udevadm doesn't seem to be present but lsusb lists 2 devices when I have something plugged in.
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0001
Sent from my Nexus 10 using xda premium

ok problem solved.
The final debugging step was to "get another otg cable and test to make sure the first otg cable isn't defective"
Since I only owned a single OTG cable at the start, it was sort of difficult to perform this ultimate debug step.
But once I tried a different cable, almost everything worked just fine.
Only my 64gb micro-sd cards gave me a little trouble, but they all work now.

Problems getting pit file -- discovered a curious error. -- need help figuring it out

So I currently am running ubuntu 15 and another computer with mint 17.
ON both computers I have tried heimdall and Jodin. Both have been unable to obtain a pit file. I get that error -7 which appears to be something related to not receiving any packets back from the phone.
When I connect the phone outside of download mode - adb works also
$Dmesg | tail
[email protected]:~$ dmesg | tail
[ 2663.619751] cdc_acm 3-1.1:1.1: failed to set dtr/rts
[ 2663.691610] cdc_acm 3-1.1:1.1: ttyACM2: USB ACM device
[ 2663.693138] usb 3-1.1: USB disconnect, device number 7
[ 2663.911119] usb 3-1.1: new high-speed USB device number 8 using ehci-pci
[ 2664.021218] usb 3-1.1: New USB device found, idVendor=04e8, idProduct=6860
[ 2664.021231] usb 3-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2664.021238] usb 3-1.1: Product: SAMSUNG_Android
[ 2664.021245] usb 3-1.1: Manufacturer: SAMSUNG
[ 2664.021250] usb 3-1.1: SerialNumber: 4b6bda34
[ 2664.023462] cdc_acm 3-1.1:1.1: ttyACM2: USB ACM device
[email protected]:~$ adb devices
List of devices attached
4b6bda34 device
In download mode...$dmesg | tail
[email protected]:~$ dmesg | tail
1062.584521] usb 3-1.1: new high-speed USB device number 3 using ehci-pci
[ 1062.693317] usb 3-1.1: New USB device found, idVendor=04e8, idProduct=685d
[ 1062.693328] usb 3-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1062.693334] usb 3-1.1: Product: MSM8960
[ 1062.693339] usb 3-1.1: Manufacturer: Sasmsung
[ 1062.807263] cdc_acm 3-1.1:1.0: ttyACM0: USB ACM device
[ 1062.807597] usbcore: registered new interface driver cdc_acm
[ 1062.807601] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[email protected]:~$ adb devices
List of devices attached
Not quite sure what to make of this. Especally the spelling of "Samsung" ...the product doesn't match. I don't know why its showing as a CDC_ACM modem. I was toying with the idea of blacklisting it again. But I tried that on my mint distro and it had no effect. ADB also shows no devices but Heimdall detects it. Fastboot also shows no devices during download mode. I'm kind of stuck here. Not sure how to fix this error.
-All drivers are installed
- 51 rules don't fix it
-blacklisting cdc doesn't work
-swapping doesn't work
Anyone have any ideas?

?
http://www.droidviews.com/how-to-extract-pit-file-from-samsung-galaxy-devices/

LeEco-2 x526 doesn't work on Ubuntu 14.04

Hi,
I am attaching USB to my Ubuntu 14.04 but getting following logs. Looks like USB-C type is not supported on Ubuntu. Could you please guide me how to enable, or any driver?
lsusb logs:
Code:
[ 127.987537] usb 1-1.1: new high-speed USB device number 5 using ehci-pci
[ 128.081611] usb 1-1.1: New USB device found, idVendor=2b0e, idProduct=1714
[ 128.081622] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 128.081627] usb 1-1.1: Product: Android
[ 128.081631] usb 1-1.1: Manufacturer: Android
[ 128.081635] usb 1-1.1: SerialNumber: 57638e68
[ 146.986991] usb 1-1.1: USB disconnect, device number 5
[ 147.184969] usb 1-1.1: new high-speed USB device number 6 using ehci-pci
[ 147.279176] usb 1-1.1: New USB device found, idVendor=2b0e, idProduct=1714
[ 147.279184] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 147.279187] usb 1-1.1: Product: Android
[ 147.279190] usb 1-1.1: Manufacturer: Android
[ 147.279193] usb 1-1.1: SerialNumber: 57638e68
Adb devices:
Code:
adb devices
List of devices attached

I'm using Debian 8.8 and it works fine for me. Try updating your system. Ubuntu 17 is out now.
Sent from my X526 using Tapatalk

Does it work with 'sudo'?

Errors with SP Flash tools on Ubuntu 18.04

I have been trying to flash some old M2 Note units and so far I can't get the Preloader to talk over USB:
Code:
[ 1774.167123] usb 1-1: new high-speed USB device number 35 using xhci_hcd
[ 1774.320150] usb 1-1: New USB device found, idVendor=0e8d, idProduct=2000, bcdDevice= 1.00
[ 1774.320152] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1774.320153] usb 1-1: Product: MT65xx Preloader
[ 1774.320153] usb 1-1: Manufacturer: MediaTek
[ 1774.344085] cdc_acm 1-1:1.0: Zero length descriptor references
[ 1774.344093] cdc_acm: probe of 1-1:1.0 failed with error -22
[ 1774.384238] cdc_acm 1-1:1.1: ttyACM0: USB ACM device
[ 1776.971989] usb 1-1: USB disconnect, device number 35
I tried adding the vendor ID and product ID to the new_id of the cdc_acm driver and also masking/disabling the ModemManager service in case it was interfering.
I had the same issue on WIndows... it would reset immediately and kick into normal Android mode.
Anyone has any advice? I'm going to trying using the OTA zip with the modified/unlocked images for the preloader.
Flashing TWRP via Flashify did not work out.... rebooted into recovery to the default Meizu one.