[Q] Customized Keylayout For Gamepad - Android Q&A, Help & Troubleshooting

Greetings!
I Have created a gamelayout for my ps2 usb adapter controller, the problem is that it doesn't get detected in Android, it's detected under linux (I attach some images) and the .kl file -It's inside "Vendor_12bd_Product_e002.zip" yes it's codified in UNIX, not MAC or DOS-.
I followed the tutorial from here.
I don't know if this has to anything but my tablet is a chinese Pipo S1 dual core Rockhip 1.6ghz gpu mali 400 with the stock software -Jellybean 4.1.1-.
As I stated, the controller gets detected, but the problem is that I want it to get detected as it should -Since it has plug for 2 usb controllers- in "Android" not in "Linux", hence, the .kl I used is not being detected and doesn't apply my mapping.
Any ideas?
PS: I already did the changes for r w r r, I used the terminal too -command ls -l /system/usr/keylayout- (image attached) Do I need to declare this new Keylayout somewhere?
Edit: The new configuration does get dettected though, the device isn't is because the modules are lacking due to the kernel source is not released and haven't compiled the .ko for generic gamepads

So finally is the Customised layout working?? If yes please let me know how?? Because for me it's not working.

Yes for games with native support, I havn't been able to make it work with USB Joystick center due to the lack of modules for generic gamepads

Related

[Q] urukdroid with hauppauge wintv aero dvb-t

hi.
i wish to get my dvbt dongle working in urukdruid, i own a hauppauge wintv aero.
the driver i loaded is smsusb which should be fine, because under opensuse 11.4 it works great witch this module, and like in opensuse i copied the right firmware from hauppauges side into
/lib/firmware.
dmesg recognized the stick, but by loading the firmware causes an error in dmesg:
...
usb 2-1: firmware: requesting sms1xxx... .fw
init: untracked pid 1565 exited
smscore_set_device_mode: firmware download success: sms1xxx....fw
the end is that there are no devices like /dev/dvb0* or else and no tuner available
lsmod | grep dvb
does only give me
dvb_core
dvb_usb
while lsmod sais that
smsusb
smsmdtv
are loadet. someone any ideas?
another problem is that urukdroid sometimes freezes by pluggin in the dvbt dongle!
thnk you for reading!
If your device is not supported by the linux kernel, it probably won't work. Check the list here: http://linuxtv.org/wiki/index.php/DVB-T_USB_Devices
Also, you can't really use the same drivers on an Android device from a Desktop/Laptop/Netbook due to differences in hardware. At least, that's my limited knowledge. Good luck!
sure...
but the drivers i use are build by sauron for urukdroid dvbt usage, and they are similar named like the drivers for opensuse so i guess they are te same only build for urukdroid kernel.
i think i use the right modules and the problem depends on the firmware implemetation, what i read is that its possible to use a firmware that didnt come with urukdroid.
i think it should work im using linux now for years, the problem is not the wrong module or firmware, both should work in urukdroid, the problem seems for me to be anywhere else.
maybe usb or kernel itself im not sure.
any more ideas to solve that?
sauron where are you?
btw not all devices that work are listet on the page! it doesent depent on the modell it depends on firmware and build in chip...
my modell isnt listet i know but with the firmware at /lib/firmware it works out of the box, driver is in kernel.

[Q] Using an xbox 360 controller w/ pershoot's kernel and stock 3.1

Hi, so I'm trying to use an xbox 360 for pc controller. I have a galaxy tab 10.1 running stock 3.1 (w/ touchwiz). It is rooted and I flashed pershoot's kernel (http://forum.xda-developers.com/showthread.php?t=1138167). It says it supports 360 controllers, so I'm not sure what the problem is. Do i have to flash a custom rom?
When I attach the usb receiver to the tab through the usb adapter, it lights up, stays lit up, and it seems like the controller can even connect to it, but the controller doesn't work at all. Nothing shows up in the input settings area either.
Thanks for any help
edit:
In case anyone finds this through searching and is having a similar problem, reddit user misfeasor answered the question for me, here is his response/solution:
"It does support it, unlike the stock kernel, but the modules (or drivers in other words) aren't built-in to the kernel but have to be installed so to speak after every reboot. Some roms have init.d support which would allow you to create a script that can run the commands at startup.
I believe the two modules you would need are ff-memless.ko and xpad.ko and both are in the lib-2636.4.tar.gz at http://droidbasement.com/db-blog/. You need to put these files somewhere on your tablet storage. Then, to insmod the modules run these commands in a terminal app or adb shell:
insmod <path-to-file>/ff-memless.ko
insmod <path-to-file>/xpad.ko
Finally, plug in your controller receiver and it should hopefully work.
Edit: You might need to run "su" before the commands above depending on if you are executing commands as root by default or not."

[Q] Help with updating 8192cu.ko Wireless Driver

I have a JXD S5110, the wireless card is a Realtek RTL8188CUS, running the 8192cu.ko driver.
At this point I also know several android devices ran this driver, not sure which ones other than the Raspberry Pi, and what version the driver was on them or on currently on mine, don't have all the cmds compiled and installed to check versions or modules
Currently running [ROM] JXD S5110 Rabid ROM v1.0 (ICS)
The last thing I do know is the driver is on realteks site, attached the source zip file from their site.
The main part I'm stuck on is this is a chinese tablet so I'm not sure if I can just compile the driver in a generic android environment or if it has to be specific to the device, if it has to be specific to the device then I need help finding a touchscreen driver to make this all work, since most of the other chipsets are standard (i.e. ARM, and a USB controller).
Or is there an easier way of just compiling it on the device itself?

Mediatek mt6753 OTG support

Hi all,
I try to get USB-OTG support for my mt6753 phone running. Lots of websites show that the device should offer OTG support and you find several phones with this chipset having this option. I have a DOOGEE T3 that should have that, too.
But nothing happens when connecting different USB storages to the phone. Neither the device internal LEDs flashes nor kmsg / dmesg shows something USB related (phone is rooted).
I already ran several USB OTG checkers from google app store that added android usb host permissions in /etc/permissions in several xml files.
I also added the usb.host setting in build.prop and disabled the charger only option.
I also added a seperate USB power supply for definitively providing enough power for the USB storage. When using this additional cable the USB storage blinks twice but nothing happens on the phone.
There are a lot of items in /sys on the phone (e.g. usb20_host) that should point me to the capabilities for OTG.
I don't see a real "hardware" usb host controller in lsusb (like an uchi or ehci controller I know from Intel based systems) - only the "Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub"
How to proceed? If you need more information to determine the next steps, just let me know.
Best regards,
RX1901
Changing the cmode property to 2 (host mode only) causes some kernel debugging lines that state at the end "switch_int_to_host is done" but the "is_host" stays 0.
Am I on the right track?
After further checkings, it looks as if the usb20_otg_if is not compiled into the kernel. How can I add this? As a quick test a .ko file would be sufficient.
RX1901 said:
After further checkings, it looks as if the usb20_otg_if is not compiled into the kernel. How can I add this? As a quick test a .ko file would be sufficient.
Click to expand...
Click to collapse
Find a kernel source for your chip. However, I'm concerned about your phone not powering up the guest device. I think it should do that regardless of the driver. Is your OTG cable good? Proper cable should have OTG pin pulled to the ground on the phone's side and floating on the device's side.

Kernel driver mod

hi to all, I'm not sure if I presented my problem well .. I have a problem with a simple idea but in solving it complex, I have two otg devices to connect to a tablet, one and an easycap, and one is a uvc for drones, the devices are detected but do not give video output because the drivers that are in / sys / bus / usb / driver are missing I tried to copy them from an android device where they work, but I have no read permissions on those folders. The question is senplice .. I know that those folders are part of the kernel I can decompile the kernel, but I don't know how to find and implement such drivers, if anyone knows something about it? Thanks

Categories

Resources