|
2010-04-03
, 08:45
|
|
Posts: 876 |
Thanked: 396 times |
Joined on Dec 2009
|
#72
|
that would be great also, if possible, i would love to have double clicking action to go to previous or sth.
-support input gestures such as double tap and long press
The Following User Says Thank You to Bec For This Useful Post: | ||
|
2010-04-03
, 10:09
|
|
Posts: 81 |
Thanked: 109 times |
Joined on Apr 2009
@ Brasov/Cluj, Romania
|
#73
|
That would explain why my usage of inotify-tools didn't help much...
thp uses a GIOChannel to monitor /sys/devices/platform/gpio-switch/headphone/state and headphoned sleeps for most of the time so I guess using one to monitor the file cb42 told us about wouldn't do any harm...
@jaeezzy, that's a good idea. Will come up with logical ways to handle that one
|
2010-04-03
, 10:21
|
|
Posts: 4,274 |
Thanked: 5,358 times |
Joined on Sep 2007
@ Looking at y'all and sighing
|
#74
|
|
2010-04-04
, 16:37
|
Posts: 82 |
Thanked: 214 times |
Joined on Jan 2010
@ Cape town
|
#75
|
I hacked a bit on the headphoned code adding another watch for the file /sys/devices/platform/nokia-av/detect but it doesn't detect any change
Then I've tried with inotifywait for both files /sys/devices/platform/nokia-av/detect and /sys/devices/platform/gpio-switch/headphone/state
I've been surprised to see that a change is detected only for the latter. So I think there's no other way than polling the file.
Making a replacement /usr/lib/ohm/libohm_accessories.so that would register the headset in the first place as a headset wouldn't be hard work (riiiight...) thanks to IDA Pro and the examples of plugins found in the OHM package but there's no point when you can just modify nokia-av.ko to not disable the button, which is what I will be doing soon. **** you, Nokia, and your stupid decisions.
The Following 5 Users Say Thank You to cb22 For This Useful Post: | ||
|
2010-04-04
, 18:17
|
Posts: 14 |
Thanked: 4 times |
Joined on Jan 2010
|
#76
|
The Following User Says Thank You to rojicha07 For This Useful Post: | ||
|
2010-04-04
, 19:47
|
Posts: 82 |
Thanked: 214 times |
Joined on Jan 2010
@ Cape town
|
#77
|
The Following User Says Thank You to cb22 For This Useful Post: | ||
|
2010-04-07
, 16:43
|
Posts: 3 |
Thanked: 1 time |
Joined on Apr 2010
|
#78
|
Cancel that above post, it seems I've found a way to do it
cat /sys/devices/platform/nokia-av/detect will give 4 when the button is not pressed, and 2 when it is pressed!
EDIT: Unfortunately, this seems to be useless, unless you feel like polling a file repeatedly for changes.
The Following User Says Thank You to NLChris For This Useful Post: | ||
|
2010-04-19
, 13:53
|
Posts: 66 |
Thanked: 26 times |
Joined on Apr 2010
|
#79
|
Indeed. Nokia's ****ish behaviour regarding this is pissing me off. I'm tempted to upload a nokia-av.ko file that doesn't disable the button.
--
I've figured out what happens: When inserting a headset, /usr/lib/ohm/libohm_accessories.so will register it to the system as plain headphones. Plain headphones do not have a button, so why would pressing it do anything? When the policy changes to "phone", this file will re-register the headset as a - *gasp* - headset; this is why (if you monitor HAL) you "see" the headphones being "removed and reinserted".
Making a replacement /usr/lib/ohm/libohm_accessories.so that would register the headset in the first place as a headset wouldn't be hard work (riiiight...) thanks to IDA Pro and the examples of plugins found in the OHM package but there's no point when you can just modify nokia-av.ko to not disable the button, which is what I will be doing soon. **** you, Nokia, and your stupid decisions.
The Following User Says Thank You to e0x For This Useful Post: | ||
|
2010-05-15
, 13:32
|
|
Posts: 4,274 |
Thanked: 5,358 times |
Joined on Sep 2007
@ Looking at y'all and sighing
|
#80
|
Tags |
ad-54/hs-45, headset button |
|
thp uses a GIOChannel to monitor /sys/devices/platform/gpio-switch/headphone/state and headphoned sleeps for most of the time so I guess using one to monitor the file cb42 told us about wouldn't do any harm...
@jaeezzy, that's a good idea. Will come up with logical ways to handle that one