I'm new to linux and Ubuntu and am wondering if there is a way to get 3 finger swipe working so you can scroll back/forward when using Firefox or Chrome.
Multitouch in Ubuntu
irishrally said:
I'm new to linux and Ubuntu and am wondering if there is a way to get 3 finger swipe working so you can scroll back/forward when using Firefox or Chrome.
Click to expand...
Click to collapse
Depends on your mouse and version of Ubuntu. Are you using a multitouch trackpad like the Magic Trackpad? I've written some sweet mutlitouch gestures for it (and other multitouch trackpads) including three-finger back/forward. It should work in 10.10 and 11.04. Let me know if you're interested.
I have the Official HP TouchPad Wireless Keyboard and I'm running cm9 0.6
Some keys on the Keyboard are non functional with ICS. For example
Brightness Control
Back and Forward Music
Notification Key
Card View Key (Could be used as home button)
Virtual Keyboard Toggle Key
and some others I cant think of
My point is, how can I make these keys functional to actually work
and
Is there any way someone could probably develop a driver that can be flashed via Clockwork Mod Recovery as a ZIP?
It would be a great help to us TouchPad Users running CM9 ICS
BUMP!
Sent from my Galaxy Nexus using xda premium
I'm actually very curious about this as well, I own the HP touchpad keyboard too and I really like it, it works really well on WebOS but when it came to android, many of the buttons don't work and it would be really great if these buttons could be remapped in some form or another.
Yeah, I would be interested in this too.
Some of the keys are easily fixable by editing /system/usr/keylayout/qwerty.kl - such as the media back/forward buttons. There's a keytest app out there which will capture keystrokes and spit out the numerical codes. You can then edit these codes in together with the desired commands into the kl file.
Other keys (keyboard toggle, brightness toggle etc...), however, do not trigger numerical keycodes at all when pressed; they seem to be using some WebOS specific command, or the Android driver simply is not written to recognise these codes. It looks like the driver would need to be modified for those keys to work - but I am no expert.
I'll try and post an edited kl file with all the keys which are recognised working later.
I have no idea on Android inputs work, but in Linux/X server there was a command line command that allowed you to directly capture keystrokes/events from a keyboard. Does android use X?
Just so you know, this thread will probably get moved, but I thought I would provide a link before it does.
http://forum.xda-developers.com/showthread.php?t=1379863
I havent applied this to CM9, but I would imagine that it shouldn't be too different.
Bump
Bump
Bump
Try using this app:
External Keyboard Helper
https://play.google.com/store/apps/...id.hwkeyboardhelperdemo&feature=search_result
You can use it to remap keys into android. Please report back if it works, as I want to buy a keyboard for my tablet, but dont want to deal with useless keys
I did find this review in the UK that mentions this app does help remap and get those uesless keys working:
http://www.amazon.co.uk/product-reviews/B0058CZX70?pageNumber=2
Quote:
This high quality Bluetooth keyboard measures 28.5cm by 13cm and weighs about 360g, including the two AA batteries that are supplied with it: slightly longer than my tablet is wide, but still small and light enough to carry round.
It is solidly made, matt black metal rather than plastic, with a stylish curving shape firmly supported on rubber feet - no wobble even on slightly uneven surfaces. The slope is perfect for fast typing. The keys are low profile and short-travel, full size, responsive and quiet. No sign that any of them is likey to come loose. There is no numeric keypad, but there is a row of function keys at the top to control the tablet - search, brightness, volume, on/off etc. Battery life is claimed to be about six months as the keyboard powers down when not in use and comes back to life as soon as you press a key.
The keyboard paired with my Sony S and with my Galaxy (both Android devices) without fuss and worked immediately, although three or four key mappings needed adjusting to match the GB layout. For this the External Keyboard Helper app is highly recommended - you just press "autodetect keyboard" and everything comes right.
As other reviewers have mentioned, there is no on/off indicator. The light next to the on/off switch on the underside of the keyboard seems to show that the device is visible for pairing, rather than that it is on. Again, the External Keyboard Helper is useful here because it flashes up a discreet message when a keyboard is not detected. I only found the lack of a light a problem on one occasion - the second time I used it. The batteries supplied were flat, so nothing worked. Fortunately, before hurling it at the wall, I remembered the old principle "check the simplest explanation first".
The lack of a caps lock light I did not find a problem - this probably depends on your style of typing.
Excellent value for money.
First, I want to thank JCSullins for all of his hard work.
I've been in the shadows of this forum mooching on everyone's efforts for a few years now...
Just wanted to point out a small bug I've found in your nightly JCSullins...
Working form a fresh install, as the very first action... if you bring down the dropdown from the top right (clock area), it displays "Owner". When you select this and enter your information, it instantly prevents the contacts application from loading properly in the future. Something to look into?
Hello all
Im trying to solve the issue that emulators such as Dos Box, ScummVM, UAE etc have when using a real mouse (plugged in with bluetooth or usb). The 2 main problems are the built in android cursor / pointer being displayed on top of the cursor from the emulator, and the mouse not going past the edge of the screen (for things like turning laying games such as doom).
Would this sort of change be possible by creating an Xposed module? Is so, does anyone have any pointers as to which classes i need to be modifying? Im guessing that the edge wrapping issue will be something in the MotionEvent.java class, but no idea about the pointer icon yet.
My end goal would be to create an easily togglabe solution that allows changing between default mouse behaviour, and a modifed style for emulators.
Thanks
Adam
Made some progress with this so far. Got the cursor hiding working. Ive attached the APK of what ive done so far. It works great for hiding the system pointer within ScummVM. To enable this set the pref and reconnect your mouse (turn off and on again). The cursors seem to only be updated when the mouse is connected to the system.
Does anyone have any ideas how to allow things like DosBox to not get stuck on the edge of the screen mouse wise? This is for things like turning in FPS games etc.
Adam
Thanks to jtxdriggers' glass launcher, I have been able to install and launch a number of legacy android apps on my glass. Unfortunately since xe12+ the touchpad no longer allows us to change focus in these apps which makes them pretty limited. Right now I am using a usb Favi keyboard to 'tab' through different elements to regain some control over legacy apps. In most cases this works fairly well.
There are some elements however that are not selectable through tab, and a mouse would be pretty useful. However, all I can get out of the touchpad of my favi is cursor movements. I've also installed synergy, and although the keyboard support works great, again the mouse cursor moves but no clicks ever make it to ui elements.
When I connect through adb and call a getevent -l, I can see that both the favi and synergy create new /dev/input/event# to control the mouse. I can also see left_btn and right_btn down and up events firing as well as scroll wheel events and cursor movement events. This leads me to believe that the drivers for the mouse is installed and working properly.
It appears to me that there is some disconnect between the system events of a mouse click and the UI event listeners. What I don't know is where those two meet up in the system. Any direction or advice from here would be greatly appreciated.