Active Topics
-
Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 1 day, 4 hrs ago -
TLS 1.2 for N9 is ready (28)
to MeeGo / Harmattan by smartblu9 - 1 day, 5 hrs ago -
Maemo repository (3)
to Community by torsen - 1 day, 21 hrs ago -
Error after installing Leste on sdcard (11)
to Maemo 7 / Leste by Maemish - 2 days, 18 hrs ago -
Introducing ubiboot N9 (multiboot OS loader) (1,393)
to Alternatives by smatkovi - 4 days, 1 hr ago - more...
 |
|
2010-07-25
, 09:41
|
|
Posts: 664 |
Thanked: 160 times |
Joined on Jul 2008
@ Australia
|
#112
|
sorry for I forgot if I've already asked this question but guys having problem with BT headset, are youse using stock or titan's enhanced kernel?
EDIT: My bad, I completely missed out stock kernel
as it's working on titan's kernel but having problem in stock kernel.
Last edited by jaeezzy; 2010-07-25 at 10:38.
EDIT: My bad, I completely missed out stock kernel
as it's working on titan's kernel but having problem in stock kernel.
Last edited by jaeezzy; 2010-07-25 at 10:38.
|
|
2010-07-26
, 03:20
|
|
Posts: 664 |
Thanked: 160 times |
Joined on Jul 2008
@ Australia
|
#113
|
Here's the new version of psswitcher-0.2. I've added feature to answer call as well like ending call - long pressing camera button. NOTE: you have to give at least couple seconds before you can either answer/end calls. I've not yet added it to devel for I want to see how it goes otherwise its useless. About the bluetooth headset issues, when I first switched to stock kernel from titan's one, I'd bt issue as well, but now its gone and hopefully it does for others having problem with it as well . Anyway, if the problem still persists, can youse please run it as /usr/sbin/PSSwitcher from xterm and let me know the output while connecting/disconnecting bt headset. Note, you have to first run it then only add/remove bt headset or make/answer calls. Thanks
EDIT: This package is updated though not the version. So, plz reinstall coz it fixes one silly error addresed in bugs report
Last edited by jaeezzy; 2010-07-27 at 08:52. Reason: updated .deb file to 0.2-1
. Anyway, if the problem still persists, can youse please run it as /usr/sbin/PSSwitcher from xterm and let me know the output while connecting/disconnecting bt headset. Note, you have to first run it then only add/remove bt headset or make/answer calls. ThanksEDIT: This package is updated though not the version. So, plz reinstall coz it fixes one silly error addresed in bugs report
Last edited by jaeezzy; 2010-07-27 at 08:52. Reason: updated .deb file to 0.2-1
| The Following User Says Thank You to jaeezzy For This Useful Post: | ||
|
|
2010-07-26
, 13:33
|
|
Posts: 664 |
Thanked: 160 times |
Joined on Jul 2008
@ Australia
|
#114
|
Just to let know of the updated .deb file in my prev post. I've not updated the verson number but now it fixes the keyboard opend issues when connected via bt or headphone.
Notes:
1) if the package is installed with the device already connected to bt headset, it won't recognize bt headset. You have to disconnect and reconnect it.
2) Answering call by long pressing the camera button doesn't work sometimes as expected if its done immediately when the connection is established. Plz give at least 2 - 3 sec before doing so.
3) Similar while ending call, if the call is answered by answering machine, you have to give it do its talking for a while before you can actually end the call long pressing the camera button.
4) If you are still having problem with bluetooth headset, plz run the program in xterm with /usr/sbin/PSSwitcher and disconnect and reconnect bt headset and it should print its UDI if registered at all.
thanks
Notes:
1) if the package is installed with the device already connected to bt headset, it won't recognize bt headset. You have to disconnect and reconnect it.
2) Answering call by long pressing the camera button doesn't work sometimes as expected if its done immediately when the connection is established. Plz give at least 2 - 3 sec before doing so.
3) Similar while ending call, if the call is answered by answering machine, you have to give it do its talking for a while before you can actually end the call long pressing the camera button.
4) If you are still having problem with bluetooth headset, plz run the program in xterm with /usr/sbin/PSSwitcher and disconnect and reconnect bt headset and it should print its UDI if registered at all.
thanks
 |
|
2010-07-26
, 13:45
|
|
Posts: 623 |
Thanked: 289 times |
Joined on Jan 2010
@ UK
|
#115
|
This for me is one of the most useful apps for the N900, but... if I could request a few enhancements:
(I only use the proximity sensor setting, all other settings are switched off and I don’t have blue tooth)
1. The app's functionality miss behaves for me, bit of a iPhone4 problem as I obviously hold it incorrectly, because I press the camera key by mistake and the proximity sensor gets switched off. This probably happens because the camera key only requires the slightest pressure to operate it and been right handed my thumb sits between the power and camera buttons.
To prevent this could you add another setting that becomes available when the "Use Proximity Sensor" setting is selected, that allows controlling of the proximity sensor, with the camera button, to be switched off.
2. Another option that would be nice to have when using the proximity sensor to control the speakers would be, when making/answering a call (perhaps making/answering controlled separately) to have the speaker activate immediately on dialing/answering. This would be useful when making a call as you wouldn't have to hold the phone to your ear to listen for the call to be answered, this would be similar (ish) to http://talk.maemo.org/showthread.php?t=55886
Then again perhaps you could add a vibration setting for when the call is answered as this little app is rapidly becoming a complete call controller app, hmmm… maybe call ID screening as well…
(I only use the proximity sensor setting, all other settings are switched off and I don’t have blue tooth)
1. The app's functionality miss behaves for me, bit of a iPhone4 problem as I obviously hold it incorrectly, because I press the camera key by mistake and the proximity sensor gets switched off. This probably happens because the camera key only requires the slightest pressure to operate it and been right handed my thumb sits between the power and camera buttons.
To prevent this could you add another setting that becomes available when the "Use Proximity Sensor" setting is selected, that allows controlling of the proximity sensor, with the camera button, to be switched off.
2. Another option that would be nice to have when using the proximity sensor to control the speakers would be, when making/answering a call (perhaps making/answering controlled separately) to have the speaker activate immediately on dialing/answering. This would be useful when making a call as you wouldn't have to hold the phone to your ear to listen for the call to be answered, this would be similar (ish) to http://talk.maemo.org/showthread.php?t=55886
Then again perhaps you could add a vibration setting for when the call is answered as this little app is rapidly becoming a complete call controller app, hmmm… maybe call ID screening as well…
|
|
2010-07-27
, 02:41
|
|
Posts: 90 |
Thanked: 47 times |
Joined on Dec 2009
@ Sydney Australia
|
#116
|
jaeezzy,
I installed the new version and still have the bluetooth headset issue.
I ran PSSwitcher from xterm and there was nothing reported when I connected my bluetooth headset.
You mentioned kernels earlier. I think am using titan's kernel. The output from a uname -r is:
2.6.28.10power37
I installed the new version and still have the bluetooth headset issue.
I ran PSSwitcher from xterm and there was nothing reported when I connected my bluetooth headset.
You mentioned kernels earlier. I think am using titan's kernel. The output from a uname -r is:
2.6.28.10power37
|
|
2010-07-27
, 08:46
|
|
Posts: 664 |
Thanked: 160 times |
Joined on Jul 2008
@ Australia
|
#117
|
Originally Posted by atunguyd
PSSwitcher uses HAL to see any device added via UDI that gets registered and like mentioned earlier HAL is not registering any UDI for the connected device in some bt headset cases and I don't know how I can detect the connected device. Hopefully someone here can suggest something for this. I'm using S9 motorolla bt headset and UDI "/org/freedesktop/Hal/devices/computer_logicaldev_input_1" is registered when connected and this' how I'm getting it to work.
jaeezzy,
I installed the new version and still have the bluetooth headset issue.
I ran PSSwitcher from xterm and there was nothing reported when I connected my bluetooth headset.
You mentioned kernels earlier. I think am using titan's kernel. The output from a uname -r is:
2.6.28.10power37
|
|
2010-07-27
, 08:50
|
|
Posts: 664 |
Thanked: 160 times |
Joined on Jul 2008
@ Australia
|
#118
|
Originally Posted by JonWW
Thanks for the suggestions: for the case 1, I've uploaded new version 0.2-1 in my previous post. It now has option to use camera button to toggle proximity.
This for me is one of the most useful apps for the N900, but... if I could request a few enhancements:
(I only use the proximity sensor setting, all other settings are switched off and I don’t have blue tooth)
1. The app's functionality miss behaves for me, bit of a iPhone4 problem as I obviously hold it incorrectly, because I press the camera key by mistake and the proximity sensor gets switched off. This probably happens because the camera key only requires the slightest pressure to operate it and been right handed my thumb sits between the power and camera buttons.
To prevent this could you add another setting that becomes available when the "Use Proximity Sensor" setting is selected, that allows controlling of the proximity sensor, with the camera button, to be switched off.
2. Another option that would be nice to have when using the proximity sensor to control the speakers would be, when making/answering a call (perhaps making/answering controlled separately) to have the speaker activate immediately on dialing/answering. This would be useful when making a call as you wouldn't have to hold the phone to your ear to listen for the call to be answered, this would be similar (ish) to http://talk.maemo.org/showthread.php?t=55886
Then again perhaps you could add a vibration setting for when the call is answered as this little app is rapidly becoming a complete call controller app, hmmm… maybe call ID screening as well…
About switching to speakers, it switches to speakers immediately as soon as the ringtone starts if delay is set to "None" and accordingly for others.
| The Following User Says Thank You to jaeezzy For This Useful Post: | ||
|
|
2010-07-27
, 12:39
|
|
Posts: 90 |
Thanked: 47 times |
Joined on Dec 2009
@ Sydney Australia
|
#119
|
jaeezzy,
One suggestion - untill the bluetooth issue is fixed can there be a menu option that auto switching is disabled when either the keyboard is open or prehaps the camera cover is open. This way when I get into the car all I need to do is open the keyboard and I know that I can use my bluetooth without the phone automatically switching to the speakers.
I will try help and see if I can figure out how to detect the bluetooth - I have 12 years writing embedded software for set top boxes (including linux one) so I probably have the skills I just need to get the time together to work out how to install the SDK and get the build environment up and running. Just too busy at the moment with a project that we are working one.
Maybe HAL is not what you should be monitoring - have you looked into dbus?
I ran dbus-monitor from the command line today and saw the following:
Connect to my motorolla headset:
Disconnect from motorolla headset:
Connect to car's bluetooth
DIsconnect from car's bluetooth:
As you can see in both cases the same dbus messages are sent but for disconnect the int32 is -1 and connect it is 0. So if there was some way for you to be notified when Playback.Manager get told to enable bluetooth override you will know that a bluetooth headset has been connected.
One suggestion - untill the bluetooth issue is fixed can there be a menu option that auto switching is disabled when either the keyboard is open or prehaps the camera cover is open. This way when I get into the car all I need to do is open the keyboard and I know that I can use my bluetooth without the phone automatically switching to the speakers.
I will try help and see if I can figure out how to detect the bluetooth - I have 12 years writing embedded software for set top boxes (including linux one) so I probably have the skills I just need to get the time together to work out how to install the SDK and get the build environment up and running. Just too busy at the moment with a project that we are working one.
Maybe HAL is not what you should be monitoring - have you looked into dbus?
I ran dbus-monitor from the command line today and saw the following:
Connect to my motorolla headset:
Code:
signal sender=:1.2 -> dest=(null destination) serial=148 path=/org/maemo/Playback/Manager; interface=org.maemo.Playback.Manager; member=BluetoothOverride int32 0 signal sender=:1.48 -> dest=(null destination) serial=53 path=/com/nokia/mafw/renderer/gstrenderer; interface=com.nokia.mafw.extension; member=property_changed string "volume" variant uint32 50
Code:
signal sender=:1.2 -> dest=(null destination) serial=149 path=/org/maemo/Playback/Manager; interface=org.maemo.Playback.Manager; member=BluetoothOverride int32 -1 signal sender=:1.48 -> dest=(null destination) serial=54 path=/com/nokia/mafw/renderer/gstrenderer; interface=com.nokia.mafw.extension; member=property_changed string "volume" variant uint32 74
Code:
signal sender=:1.2 -> dest=(null destination) serial=146 path=/org/maemo/Playback/Manager; interface=org.maemo.Playback.Manager; member=BluetoothOverride int32 0 signal sender=:1.48 -> dest=(null destination) serial=51 path=/com/nokia/mafw/renderer/gstrenderer; interface=com.nokia.mafw.extension; member=property_changed string "volume" variant uint32 50
Code:
signal sender=:1.2 -> dest=(null destination) serial=147 path=/org/maemo/Playback/Manager; interface=org.maemo.Playback.Manager; member=BluetoothOverride int32 -1 signal sender=:1.48 -> dest=(null destination) serial=52 path=/com/nokia/mafw/renderer/gstrenderer; interface=com.nokia.mafw.extension; member=property_changed string "volume" variant uint32 74
| The Following User Says Thank You to atunguyd For This Useful Post: | ||
|
|
2010-07-27
, 13:23
|
|
Posts: 90 |
Thanked: 47 times |
Joined on Dec 2009
@ Sydney Australia
|
#120
|
Jaeezzy:
More info - the last dump i got was from using dbus-monitor which by default only logs the user session dbus messages. Logging the system messages with dbus-monitor --system is far more revealing and is in the attached files.
As you can see there are definitly messages being sent to the bluez bluetooth stack telling it that the headset is being connected and disconnected - i think if you can get this stack to send you a message via dbus you will be good to know when any sort of bluetooth device has connected or disconnected.
More info - the last dump i got was from using dbus-monitor which by default only logs the user session dbus messages. Logging the system messages with dbus-monitor --system is far more revealing and is in the attached files.
As you can see there are definitly messages being sent to the bluez bluetooth stack telling it that the headset is being connected and disconnected - i think if you can get this stack to send you a message via dbus you will be good to know when any sort of bluetooth device has connected or disconnected.
| The Following User Says Thank You to atunguyd For This Useful Post: | ||
EDIT: I've added the source files as .tar in #1 post. Thanks
Last edited by jaeezzy; 2010-07-23 at 13:36.