Active Topics
-
[ANNOUNCE] MeeShop - new app store (8)
to Applications by Maemish - 2 hrs ago -
HTTP-401 Sfos-Builder when using /etc/ssu credentials (0)
to SailfishOS by insanelysexy - 6 hrs, 30 mins ago -
Longtime users: What device(s) are you using today? (54)
to General by ryu1 - 2 days, 11 hrs ago -
Registering (1)
to General by Halftux - 5 days, 4 hrs ago -
Applications Wishlist (55)
to Maemo 7 / Leste by sixwheeledbeast - 6 days, 6 hrs ago - more...
Breathoffire |
2010-08-15
, 02:35
|
|
Posts: 18 |
Thanked: 0 times |
Joined on Feb 2010
|
#131
|
Originally Posted by AgogData
That's what i'm trying to figure out too :/
 |
|
2010-08-15
, 18:18
|
|
Posts: 870 |
Thanked: 133 times |
Joined on Aug 2010
|
#132
|
i've been going everywhere in the root and didn't found out
i guess neither the creator of the application knows
i guess neither the creator of the application knows
|
|
2010-08-16
, 08:13
|
|
Posts: 208 |
Thanked: 220 times |
Joined on Apr 2010
|
#133
|
Originally Posted by AgogData
how can i reach the (GConf key/apps/headset-control) ??
Originally Posted by Breathoffire
You are supposed to type the following command as is in terminal
That's what i'm trying to figure out too :/
Originally Posted by Biga
To set it back put false instead of true.You can also use a gconf editor (risky if you don't know what you are doing) from repos to do the above.
I guess,
gconftool-2 --set /apps/headset-control/next-mode --type bool true
Maybe it would be better to make this default behavior?
__________________
With Linux-powered N900..ANYTHING is possible
| The Following User Says Thank You to techie For This Useful Post: | ||
 |
|
2010-08-16
, 11:14
|
|
Moderator |
Posts: 3,718 |
Thanked: 7,420 times |
Joined on Dec 2009
@ Bize Her Yer Trabzon
|
#134
|
Originally Posted by shadowjk
Is it possible to get this to work? (Maybe in a future release?)
AD-54 does not work. It's not listed as compatible with N900 either.
|
|
2010-08-16
, 12:35
|
|
Posts: 1,258 |
Thanked: 672 times |
Joined on Mar 2009
|
#135
|
Well nobody knows how it actually works, or if N900 is able to energize whatever microcontroller sits in it. Heck, we don't even know if it actually transmits commands over the cable or if it sneakily creates a bluetooth connection.
|
|
2010-08-17
, 06:26
|
|
Posts: 870 |
Thanked: 133 times |
Joined on Aug 2010
|
#136
|
Originally Posted by techie
i've tried (gconftool-2 --set /apps/headset-control/next-mode --type bool true) in terminal but didn't get me anywhere i guess it was "wrong input"
You are supposed to type the following command as is in terminal
To set it back put false instead of true.You can also use a gconf editor (risky if you don't know what you are doing) from repos to do the above.
|
|
2010-08-17
, 19:20
|
|
Posts: 208 |
Thanked: 220 times |
Joined on Apr 2010
|
#137
|
Originally Posted by AgogData
Didn't take you anywhere?? where did you think it will take you. Where do u wanna go? The command simply changes the behavior of the headset button to switch to next track instead of pausing.The value "false" makes the button pause/play the song again.It isn't going to take you anywhere
i've tried (gconftool-2 --set /apps/headset-control/next-mode --type bool true) in terminal but didn't get me anywhere i guess it was "wrong input"
__________________
With Linux-powered N900..ANYTHING is possible
|
|
2010-08-17
, 23:11
|
|
Posts: 870 |
Thanked: 133 times |
Joined on Aug 2010
|
#138
|
Originally Posted by techie
by not taking me anywhere i meant leads to nothing and leads to nothing is not like i'm in the road and i took the wrong way so it lead to nothing its just expression
Didn't take you anywhere?? where did you think it will take you. Where do u wanna go? The command simply changes the behavior of the headset button to switch to next track instead of pausing.The value "false" makes the button pause/play the song again.It isn't going to take you anywhere
anyway in the terminal it says "gconftool-2 --set is not a command type gconftool-2 --help for help" and in help didn't really help me
did u do it and worked ?
 |
|
2010-08-26
, 13:20
|
|
Posts: 2,222 |
Thanked: 12,651 times |
Joined on Mar 2010
@ SOL 3
|
#139
|
all multi button wired headsets won't work with N900 without massive wizardry to the AV detection drivers. Maybe hardware is completely incapable of dealing with them.
A usual one button headset simply shorts the mic ring to ground on button push, that's why mic ceases to record during button hold, and that's also the reason mic(-bias) has to be enabled for button to work.
I probed on one of those multi button wired Nokia headsets, and found no reasonable behaviour of mic, by using a voltmeter for resistance probing. As I got no N95 or similar, I wasn't able to probe the thing in action, so protocol used to signal button press is unknown (maybe it's really BT as shadowjk suggested :-P). Without one of a) headset schematics, b) N95 (or similar) schematics, c) protocol specs, the only way to find out is somebody with N95 and MB headset and scope does some probing.
Until then, no luck with multi button, positively
[edit] meanwhile somebody allowed me to have a look at N95 schematics, and it seems the *hardware* isn't that much different to N900 for AV. Means it might be actually feasible to implement proper support for multibutton wired headsets, by patching the kernel drivers. Still missing is a proper analysis or spec of the protocol
/j
Last edited by joerg_rw; 2010-09-10 at 11:55.
A usual one button headset simply shorts the mic ring to ground on button push, that's why mic ceases to record during button hold, and that's also the reason mic(-bias) has to be enabled for button to work.
I probed on one of those multi button wired Nokia headsets, and found no reasonable behaviour of mic, by using a voltmeter for resistance probing. As I got no N95 or similar, I wasn't able to probe the thing in action, so protocol used to signal button press is unknown (maybe it's really BT as shadowjk suggested :-P). Without one of a) headset schematics, b) N95 (or similar) schematics, c) protocol specs, the only way to find out is somebody with N95 and MB headset and scope does some probing.
Until then, no luck with multi button, positively
[edit] meanwhile somebody allowed me to have a look at N95 schematics, and it seems the *hardware* isn't that much different to N900 for AV. Means it might be actually feasible to implement proper support for multibutton wired headsets, by patching the kernel drivers. Still missing is a proper analysis or spec of the protocol
/j
__________________
Maemo Community Council member [2012-10, 2013-05, 2013-11, 2014-06 terms]
Hildon Foundation Council inaugural member.
MCe.V. foundation member
EX Hildon Foundation approved Maemo Administration Coordinator (stepped down due to bullying 2014-04-05)
aka "techstaff" - the guys who keep your infra running - Devotion to Duty http://xkcd.com/705/
IRC(freenode): DocScrutinizer*
First USB hostmode fanatic, father of H-E-N
Maemo Community Council member [2012-10, 2013-05, 2013-11, 2014-06 terms]
Hildon Foundation Council inaugural member.
MCe.V. foundation member
EX Hildon Foundation approved Maemo Administration Coordinator (stepped down due to bullying 2014-04-05)
aka "techstaff" - the guys who keep your infra running - Devotion to Duty http://xkcd.com/705/
IRC(freenode): DocScrutinizer*
First USB hostmode fanatic, father of H-E-N
Last edited by joerg_rw; 2010-09-10 at 11:55.
| The Following 4 Users Say Thank You to joerg_rw For This Useful Post: | ||
|
|
2010-09-10
, 11:40
|
|
Posts: 364 |
Thanked: 128 times |
Joined on Sep 2010
@ Australia
|
#140
|
Originally Posted by joerg_rw
Really usefull, should have read this first !
all multi button wired headsets won't work with N900 without massive wizardry to the AV detection drivers. Maybe hardware is completely incapable of dealing with them.
A usual one button headset simply shorts the mic ring to ground on button push, that's why mic ceases to record during button hold, and that's also the reason mic(-bias) has to be enabled for button to work.
I probed on one of those multi button wired Nokia headsets, and found no reasonable behaviour of mic, by using a voltmeter for resistance probing. As I got no N95 or similar, I wasn't able to probe the thing in action, so protocol used to signal button press is unknown (maybe it's really BT as shadowjk suggested :-P). Without one of a) headset schematics, b) N95 (or similar) schematics, c) protocol specs, the only way to find out is somebody with N95 and MB headset and scope does some probing.
Until then, no luck with multi button, positively
/j
 |
| Tags |
| ad-54/hs-45, headset button |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 20:04.