About hardware buttons

Started by Stager, February 20, 2018, 11:23:23 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Stager

As it known, mostly android devices has a capacitive touch screen. And this touch screen perform poorly under rain. So may be a good idea to turn off a touch screen, and use hardware knobs only. In my experience, zoom by volume buttons as a already sufficient. In typical rain cases :-)

But I found some problem: all apps for turn touch screen off on GooglePlay get handled the hardware volume keys on locked mode. So volume keys not usable in OruxMaps on locked mode.



Also, I would like to use with OruxMaps this device:

https://aliexpress.com/item/China-Rugged-Industrial-Waterproof-Tablet-Phone-PC-UHF-VHF-PTT-Radio-7-1920x1200-Dual-Sim-Android/32794890728.html">

But it not have volume knobs!



So my question: it is possible to map control functions in OruxMaps directly to hardware knobs? Is this problem important enough?

orux

#1
Quote from: Stager post_id=12908 time=1519165403 user_id=2645
As it known, mostly android devices has a capacitive touch screen. And this touch screen perform poorly under rain. So may be a good idea to turn off a touch screen, and use hardware knobs only. In my experience, zoom by volume buttons as a already sufficient. In typical rain cases :-)

But I found some problem: all apps for turn touch screen off on GooglePlay get handled the hardware volume keys on locked mode. So volume keys not usable in OruxMaps on locked mode.



Also, I would like to use with OruxMaps this device:



But it not have volume knobs!



So my question: it is possible to map control functions in OruxMaps directly to hardware knobs? Is this problem important enough?


Hello;



It is not usual to find devices with more keys than the standard ones.



The app has the option to use a trackball (I still remember the HTC ONE!). You can activate it in configuration -> app. Maybe it responds to trackball events.



I think it would be easier if the device allows you to map the keys to the normal Android keys,





orux

Stager

#2
Quote from: orux post_id=13004 time=1520458920 user_id=2
I think it would be easier if the device allows you to map the keys to the normal Android keys,

I need to root'ed it :-)



Pls, see this topic: http://oruxmaps.com/foro/viewtopic.php?f=8&t=4834">http://oruxmaps.com/foro/viewtopic.php?f=8&t=4834

Is it possible to implement the idea about assigned specific actions to some Android keys, and documented it?

orux

#3
Quote from: Stager post_id=13006 time=1520462022 user_id=2645
Quote from: orux post_id=13004 time=1520458920 user_id=2
I think it would be easier if the device allows you to map the keys to the normal Android keys,

I need to root'ed it :-)



Pls, see this topic: http://oruxmaps.com/foro/viewtopic.php?f=8&t=4834">http://oruxmaps.com/foro/viewtopic.php?f=8&t=4834

Is it possible to implement the idea about assigned specific actions to some Android keys, and documented it?




Are you sure that root is necessary? https://play.google.com/store/apps/details?id=flar2.homebutton&hl=en">https://play.google.com/store/apps/deta ... tton&hl=en">https://play.google.com/store/apps/details?id=flar2.homebutton&hl=en



I can add a set of keys and map them to some actions, from here: https://developer.android.com/reference/android/view/KeyEvent.html">https://developer.android.com/reference ... Event.html">https://developer.android.com/reference/android/view/KeyEvent.html





orux

Stager

#4
Quote from: orux post_id=13027 time=1520695209 user_id=2
Are you sure that root is necessary?

I don't have enough knowledge. In my opinion, app to mapping keys without root is a additional proxy, therefore, possible side effects.


Quote from: orux post_id=13027 time=1520695209 user_id=2
I can add a set of keys and map them to some actions

That would be very good!



Tell me, please: is it so hard to make feature to turn off touchscreen? Chaotic touches under rain make use navigation tablet impossible.

orux

#5
Quote from: Stager post_id=13033 time=1520721138 user_id=2645
Quote from: orux post_id=13027 time=1520695209 user_id=2
Are you sure that root is necessary?

I don't have enough knowledge. In my opinion, app to mapping keys without root is a additional proxy, therefore, possible side effects.


Quote from: orux post_id=13027 time=1520695209 user_id=2
I can add a set of keys and map them to some actions

That would be very good!



Tell me, please: is it so hard to make feature to turn off touchscreen? Chaotic touches under rain make use navigation tablet impossible.




It is not possible to turn off screen touchscreen, but I can disable touch events on all views except action bar.



Tell me which actions would you map to key events.



orux

Stager

#6
@
Quote from: orux post_id=13034 time=1520758830 user_id=2
It is not possible to turn off screen touchscreen, but I can disable touch events on all views except action bar.

Ok, I understood.


Quote from: orux post_id=13034 time=1520758830 user_id=2
Tell me which actions would you map to key events.

IMHO:

Scroll a map (4 keys and 2 axis?)

Zoom by layers +

Zoom by layers -

"Hand scroll" on/off

"Lateral dashboard" on/off

Touch events on map on/off



Also may be:

Digital zoom +

Digital zoom -

Reset digital zoom

SOS alarm on

...



Also I would like to switch between two or three selected maps in a circle by one button. Between satellite and topo maps, for example. But I don't insist :-)

Stager

#7
Another important action which I forgot:

Is it possible to assign key events to "Create waypoint" action, same as 'Wpts.'—'Create', but without ask name and type?

This can be used to set point of "man overboard" in rescue action on the sea.

orux

#8
Quote from: Stager post_id=13067 time=1521053297 user_id=2645
Another important action which I forgot:

Is it possible to assign key events to "Create waypoint" action, same as 'Wpts.'—'Create', but without ask name and type?

This can be used to set point of "man overboard" in rescue action on the sea.


Added for next version, you can find key code here: https://developer.android.com/reference/android/view/KeyEvent.html">https://developer.android.com/reference ... Event.html">https://developer.android.com/reference/android/view/KeyEvent.html



(keyCode == KeyEvent.KEYCODE_DPAD_DOWN_LEFT)

            scroll down-left

(keyCode == KeyEvent.KEYCODE_DPAD_DOWN_RIGHT)

           scroll down right

(keyCode == KeyEvent.KEYCODE_DPAD_DOWN)

            scroll down

(keyCode == KeyEvent.KEYCODE_DPAD_LEFT)

            scroll left

(keyCode == KeyEvent.KEYCODE_DPAD_RIGHT)

            scroll right

(keyCode == KeyEvent.KEYCODE_DPAD_UP)

            scroll up

(keyCode == KeyEvent.KEYCODE_DPAD_UP_LEFT)

            scroll up left

(keyCode == KeyEvent.KEYCODE_DPAD_UP_RIGHT)

            scroll up right

(keyCode == KeyEvent.KEYCODE_VOLUME_DOWN)

            digital zoom out

(keyCode == KeyEvent.KEYCODE_VOLUME_UP)

           digital zoom in

(keyCode == KeyEvent.KEYCODE_ZOOM_IN)

            zoom in

(keyCode == KeyEvent.KEYCODE_ZOOM_OUT)

           zoom out

(keyCode == KeyEvent.KEYCODE_BOOKMARK)

            create wpt auto

(keyCode == KeyEvent.KEYCODE_CLEAR)

            reset digital zoom

(keyCode == KeyEvent.KEYCODE_WINDOW)

            show/hide lateral dashboard

 (keyCode == KeyEvent.KEYCODE_MOVE_HOME)

            tweak hand/gps map scroll







orux



orux