sixaxis controller will work on Andorid 6.0.1 ? i got a Moto Maxx ( XT1225 ) With android 6 ( brazil Soak update 3) and when i tried to connect my PS3 controller (original)the app shows this log.
Code:
Attempting connecttion type 1...
driver Starting...
Could not load bluetooth library
Touchscreen device create successfully
ERROR: failed to configure bluetooth
Attempting connecttion type 2...
driver Starting...
Could not load HCI library
Touchscreen device create successfully
ERROR: failed to configure bluetooth
Attempting connecttion type 3...
driver Starting...
Touchscreen device create successfully
ERROR: failed to configure bluetooth
Attempting connecttion type 4...
driver Starting...
Touchscreen device create successfully
ERROR: failed to configure bluetooth
Attempting to close server...
restoring previous bluetooth state
Disconnected
Does this happen to anyone else ?
im on a Stock motorola rom 6.0.1 with ROOT
Related
Okay so I recently updated my Ipaq hx4700 to 6.1 Alkor Build 21054 and installed MobileSRC's Mobile Remote v1.1 on it. I want to use it as a bluetooth remote for my PS3 but I keep getting two errors over and over again:
Error 1 (shown at boot up of mobile remote): Failed to load driver: 87
Error 2 (shown after selecting legacy mode, and then checkmark to begin connecting):
Error Connecting: [1062] Listen INTR failed
There was an error connecting to the computer. Please ensure that your computer is on, has Bluetooth enabled, and has an active pairing with this machine.
Any help is much appreciated.
Thanx in advance
Hi,
I’ve got a Samsung Galaxy Nexus device and I would like to run the FTDI Android D2XX Driver on it.
The instruction can be found on ftdichip.com/android.
The device is unlocked and rooted, so I can change the USB permissions. The image is the original Samsung Android 4.0.2.
I installed the libftd2xx-jni.so on my device as described in the TN_134 document and opened the sample project in eclipse. The project is compiled with the Android 4.0 API.
The demo application is running fine on my device except if I press the “Info” button.
If I do and no device is attached to the USB port, I can read “Number of devices: 0” and “No device” on the display.
If I do and a device is attached, the application crashes without any notice.
It doesn’t matter if I change the permissions in /ueventd.rc:
/dev/bus/usb/* 0666 root usb
/dev/mtp_usb 0666 root mtp
/dev/usb_accessory 0666 root usb
Does anyone have an idea how to solve this problem?
Edit: Added some log
06-12 07:41:40.531: I/ftd2xx-java(17157): loading JNI library...
06-12 07:41:40.531: I/ftd2xx-java(17157): JNI library loaded!
06-12 07:42:10.937: A/libc(17157): @@@ ABORTING: INVALID HEAP ADDRESS IN dlfree
06-12 07:42:10.937: A/libc(17157): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)
I had the same problem om my 4.0.3 tablet and noticed that it sometimes worked and sometimes not.
I found that running 'USB host controller' (see google play) somehow solved the problem, maybe because it enumerates the usb devices.
Not a very satisfactory workaround but good enough to be able to test, maybe there is some way to built a comparable usb enumeration into the app.
No luck yet on earlier versions of android.
Success
gosa_ said:
Hi,
I’ve got a Samsung Galaxy Nexus device and I would like to run the FTDI Android D2XX Driver on it.
The instruction can be found on ftdichip.com/android.
The device is unlocked and rooted, so I can change the USB permissions. The image is the original Samsung Android 4.0.2.
I installed the libftd2xx-jni.so on my device as described in the TN_134 document and opened the sample project in eclipse. The project is compiled with the Android 4.0 API.
The demo application is running fine on my device except if I press the “Info” button.
If I do and no device is attached to the USB port, I can read “Number of devices: 0” and “No device” on the display.
If I do and a device is attached, the application crashes without any notice.
It doesn’t matter if I change the permissions in /ueventd.rc:
/dev/bus/usb/* 0666 root usb
/dev/mtp_usb 0666 root mtp
/dev/usb_accessory 0666 root usb
Does anyone have an idea how to solve this problem?
Edit: Added some log
06-12 07:41:40.531: I/ftd2xx-java(17157): loading JNI library...
06-12 07:41:40.531: I/ftd2xx-java(17157): JNI library loaded!
06-12 07:42:10.937: A/libc(17157): @@@ ABORTING: INVALID HEAP ADDRESS IN dlfree
06-12 07:42:10.937: A/libc(17157): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)
Click to expand...
Click to collapse
Hello. I have the same problem of driver FTDI, libftd2xx-jni.so.
The problem comes when you call D2xx.createDeviceInfoList() in D2XXSampleActivity. Do you've found the solution? Thank you.
How to root the CX 919 II Tv stick
link for software here should work on any "CX-919" device / TVstick
http://www.share-online.biz/dl/54FMSCQM0U
1. plugin cx-919 II with usb-cable on "usb" to usb-slot on computer and wait for detection as "cx-919".
2. a new device detected, called "cx-919" or "CX-919 II), go to device manager and install the
latest usb google sdk driver from sdk android 4.2.2 file "android_winusb.inf"
path to file: RK3188_ROOT\usb_driver
(included in this file, modded for x64 and x86 os for rk3188 detection).
3. after installation usb-driver, cx-919 now detected as "android composite adb interface"
for test driver install go to root directory from attached file and go to cmd and call:
adb devices
you should see a message like this:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
0123456789ABCDEF device 4. next call "TPSparkyRoot.bat"
5. follow the onscreen instruction, 3 reboots and you have root
(wait for every step at least 2 minutes, so you are sure your device is rebooted and ready for next step...)
6. plug in cx-919 in tv and start app "Super SU" execute binary update and upgrade to latest version through google play store...
http://www.share-online.biz/dl/54FMSCQM0U
What kind of usb cable to use? I've never seen a USB to USB. The only thing that came with this thing is a micro USB to regular USB.
UPDATE: it's the OTG jack which worked.
Only one problem, I followed the instructions, seems to go fine and says completed however I still don't have root. I have SuperSU but says "There is no SU binary installed, and SuperSU cannot install it.".
What did I do wrong?
Android Launch!adb is running normally.
Performing com.example.hellofriend.MainActivity activity launch Automatic Target Mode: using existing emulator 'emulator-5554' running compatible AVD 'AsdPh'
Uploading HelloFriend.apk onto device 'emulator-5554'
Installing HelloFriend.apk...
Installation error: Unknown failure
Please check logcat output for more details.
Launch canceled!
Hello everybody! Noobing the shoozle out of my:
OnePlus One, model A0001 / 64GB currently with: Android 6.0.1 / Cyanogen OS version: 13.1.2-ZNH2KAS3P0-bacon / CyanogenMod API level: Elderberry(5) (just FYI, not sure if helpful)
Kernel version: 3.4.112-cyanogenmod-g8fbc62e
Unlocked, rooted with BaconRootToolkit/ TWRP ROM, downloaded latest ver -3.0.2-0 via official App, from Play Store
Kali images from: build.nethunter.com/nightly, as offensive-security's kali-nethunter wiki on github says (no external links for noobs, sorry )
apt-get updated, upgraded and dist-upgraded via KALI terminal
The first issue is with the OTG, not powering the USB WiFi adapter properly... with the regular USB-OTG adapter, lsusb WORKS, and returns proper info about 3 different adapters (Alfa Awus036h, TP-link WN725N and WN722N), BUT does not power them. No indicator lights get lit whatsoever 0mA status from lsusb -v
I bought a powered USB-OTG hub, that appears to not charge my phone, when plugged in two different chargers AND a powerbank. Still lsusb -v returns: 100mA current for the hub.
I tried plugging an A4Tech receiver for kbd+mouse, both work fine, with the tplink WN725N plugged in the second USB socket. lsusb shows the hub, the receiver and the WN725N data... Both regular and hub OTG's work fine with mouse+kbd, read and write data to USB Memsticks. Regular OTG transfers files to a computer and charges the phone.
I noticed that when in Android, the WiFi is turned off, ifconfig omits wlan0 and p2p0, that is the phone's main WiFi adapter.
So I thought that manually loading (insmod) the rtl drivers would start the OTG wlan.... Thus coming to the second issue:
The kernel is without LKM support - no modprobe, lsmod returns:
Code:
libkmod: ERROR: ../libkmod/libkmod-module.c: 1655 kmod_module_new_from_loaded: could not open /proc/modules: no such file or directory
Error: could not get list of modules: No such file or directory
When "apt-get install linux-headers-$(uname -r)" is typed, returns:
Code:
E: Unable to locate package 'linux-headers-3.4.112-cyanogenmod-g8fbc62e'
E: Couldn't find any package by glob 'linux-headers-3.4.112-cyanogenmod-g8fbc62e'
E: Couldn't find any package by regex 'linux-headers-3.4.112-cyanogenmod-g8fbc62e'
"apt-cache search linux-headers" returns some options for version linux-headers-4.9.0-kali1-all-armhf (the only armHF, others are armmp)
I cannot find a way to recompile my kernel and enable Loadable Kernel Modules support. Would you say this would be necessary for the external WiFi to work?
Do you know if there is any way out of this mess, as I am really tired fighting a "Our preferred device"-release issues??? Overall I'd love it if I could run external antenna
I am kind of new around.... In forums - in general, so I kindly ask for understanding. If any screenshots/pics/additional info is required - I'll make sure I update this thread. Not sure if I could've posted this thread in XDA assist, so I did it here.
EDIT: everything went fine when I tried third, different USB - WiFi adapter. Works properly. Still no LKMs.