Active Topics
-
[HOWTO] Comprehensive Firmware Flashing Guide for N9 (1,580)
to Nokia N9 / N950 by aspergerguy - 15 hrs, 42 mins ago -
Nokia N9-00 Prototype Build S1.12 (RM-680 codename "Dali") (250)
to Nokia N9 / N950 by en0s - 3 days, 12 hrs ago -
[Announce] Maebble - Pebble support for Maemo (118)
to Applications by glo-worm - 4 days ago -
Possible to flash Leste to eMMC? (6)
to Maemo 7 / Leste by Eri - 4 days, 14 hrs ago - more...
 |
|
2010-06-08
, 14:06
|
|
Posts: 1,030 |
Thanked: 792 times |
Joined on Jun 2009
|
#92
|
Oddly enough, I don't encounter this issue. It works as it should for me. When I have my headset / A2DP paired, sliding out the keyboard or covering/uncovering the proximity sensor doesn't activate the loud speaker.
I've tested every possible way I can think of, pairing before a call, pairing and transferring audio during a call, dropping bluetooth off, turning off the headset without disconnecting.
No idea why this would be.
I've tested every possible way I can think of, pairing before a call, pairing and transferring audio during a call, dropping bluetooth off, turning off the headset without disconnecting.
No idea why this would be.
 |
|
2010-06-09
, 10:30
|
|
Posts: 664 |
Thanked: 160 times |
Joined on Jul 2008
@ Australia
|
#93
|
Originally Posted by davall
Can you please let me know the output of lshal -m in x-terminal when you connect/disconnect bluetooth headset? Mine says "computer_logicaldev_input_1 added"
Can confirm this partly. If i switch off the proximity sensor in settings when using bluetooth headset everything is fine.
So until this is fixed, i cannot use pss with proximity sensor. What a pity.
Regards, davall
|
|
2010-06-09
, 13:39
|
|
Posts: 1,030 |
Thanked: 792 times |
Joined on Jun 2009
|
#94
|
Same values here as last time. Can we just confirm what type of hardware everybody is using? I'm not sure if BT profiles are being set differently. I'm using headphones and A2DP at all times during my testing.
| The Following User Says Thank You to hawaii For This Useful Post: | ||
|
|
2010-06-09
, 19:32
|
|
Posts: 33 |
Thanked: 8 times |
Joined on Dec 2009
|
#95
|
Originally Posted by jaeezzy
I tried it several times. Mine says nothing in xterm during connect or disconnect
Can you please let me know the output of lshal -m in x-terminal when you connect/disconnect bluetooth headset? Mine says "computer_logicaldev_input_1 added"
In xterm i only get battery status info with lshal -m
On the desktop i get the yellow notice that it is connected with the BMW bluetooth car kit.
Any clue?
|
|
2010-06-09
, 23:30
|
|
Posts: 664 |
Thanked: 160 times |
Joined on Jul 2008
@ Australia
|
#96
|
Originally Posted by davall
To be honest I don't have a clue either. What about you copy the outputs of just lshal, first without connecting and second after connecting with bluetooth and let me know the diff. However, n900 doesn't have inbuilt package to do so, so if you have Linux computer it will be easier. Anyways, there's package named "diffutils-gnu" in extras-testing but again the warning on using devel and testing applies and do it on your own risk.
I tried it several times. Mine says nothing in xterm during connect or disconnect
In xterm i only get battery status info with lshal -m
On the desktop i get the yellow notice that it is connected with the BMW bluetooth car kit.
Any clue?
If you've decided to go ahead
here's what you can do in x-term in N900:lshal >> ~/before_conn (before connecting to BT)
lshal >> ~/after_conn (after connecting to BT)
gdiff before_conn after_conn
and let me know the output.
|
|
2010-06-10
, 02:59
|
|
Posts: 1,030 |
Thanked: 792 times |
Joined on Jun 2009
|
#97
|
So this isn't a headset you're using? Can the other poster confirm what hardware they are using so we can track this issue down?
|
|
2010-06-10
, 10:28
|
|
Posts: 33 |
Thanked: 8 times |
Joined on Dec 2009
|
#98
|
...
If you've decided to go ahead
lshal >> ~/before_conn (before connecting to BT)
lshal >> ~/after_conn (after connecting to BT)
gdiff before_conn after_conn
and let me know the output.
--------------snip
40,41c40,41
< battery.charge_level.percentage = 100 (0x64) (int)
< battery.charge_level.rate = 0 (0x0) (int)
---
> battery.charge_level.percentage = 99 (0x63) (int)
> battery.charge_level.rate = 1 (0x1) (int)
43c43
< battery.reporting.rate = 0 (0x0) (int)
---
> battery.reporting.rate = 1 (0x1) (int)
98c98
< battery.voltage.current = 4141 (0x102d) (int)
---
> battery.voltage.current = 4111 (0x100f) (int)
--------------snip end
Regards davall
PS: I'm using the n900 in a BMW car with integrated bluetooth headset/car kit
|
|
2010-06-10
, 10:49
|
|
Posts: 664 |
Thanked: 160 times |
Joined on Jul 2008
@ Australia
|
#99
|
Originally Posted by davall
Thats talking about only battery power changes inbetween the cmds, so nothing is registered.. Now that leaves me clueless as to how N900 is recognizing that bluetooth device is added so sorry I'm gonna have to seek for help here myself
Here comes the output. Nothing more as before i guess
--------------snip
40,41c40,41
< battery.charge_level.percentage = 100 (0x64) (int)
< battery.charge_level.rate = 0 (0x0) (int)
---
> battery.charge_level.percentage = 99 (0x63) (int)
> battery.charge_level.rate = 1 (0x1) (int)
43c43
< battery.reporting.rate = 0 (0x0) (int)
---
> battery.reporting.rate = 1 (0x1) (int)
98c98
< battery.voltage.current = 4141 (0x102d) (int)
---
> battery.voltage.current = 4111 (0x100f) (int)
--------------snip end
Regards davall
PS: I'm using the n900 in a BMW car with integrated bluetooth headset/car kit
so plz anyone who can help/suggest as to what could be done here would be great.. Thanks
thanks
So until this is fixed, i cannot use pss with proximity sensor. What a pity.
Regards, davall