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?

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/

USB Debugging On Linux

USB debugging on Linux
Maybe it's just me being blind, but does anyone have `adb` working on Linux? Device ID shows up as 0fca, and I've added this to my udev rules, but still no device. Notification shows "USB debugging connected - Touch to disable USB debugging" with "Media device (MTP)" and "Camera (PTP)" USB connections.
Code:
07:32:04 ~$ lsusb |grep Research
Bus 001 Device 003: ID 0fca:8032 Research In Motion, Ltd.
Code:
[ 397.648593] usb 1-1: new high-speed USB device number 3 using ehci-pci
[ 397.920791] usb 1-1: New USB device found, idVendor=0fca, idProduct=8032
[ 397.920796] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 397.920798] usb 1-1: Product: BlackBerry
[ 397.920799] usb 1-1: Manufacturer: BlackBerry
[ 397.920801] usb 1-1: SerialNumber: <x>
Code:
07:39:49 ~$ adb devices
List of devices attached
Thanks!

Figured it out. My Linux environment (Ubuntu 14) had the package 'android-tools-adb' installed, but that version of `adb` doesn't seem to work. The `adb` binary with the SDK tools works fine. I removed the 'android-tools-adb' and all is well again. :laugh:

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.