c_c wrote:
>
> Hi,
>
>>Also, I need a way to enable/disable bluetooth without editing configs
>>and restarting frameworkd and ophonekitd, as doing so takes several
minutes.
>
> Best solved by making two bash scripts and their associated .desktop
> files.
> Inconvenient hack - but it's worki
Yes, it can be done with bash scripts, but there's no avoiding restarting
frameworkd and ophonekitd. That's the part that takes so long.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Hi,
The Digital Pioneer wrote:
>
>>Glad to hear you got it working, c_c. :)
>
Thanks to this thread and the people here!
The Digital Pioneer wrote:
>
>> If I suspend the phone, then it disconnects from the
>>headset, and I can't answer calls until I run the dbus command
>
I use the spea
Glad to hear you got it working, c_c. :)
In the mean time, I've had to disable bluetooth entirely since it's just not
ready to use yet. If I suspend the phone, then it disconnects from the
headset, and I can't answer calls until I run the dbus command, which isn't
realistic to do while the phone i
c_c writes:
>> did you add the rules to
>> /etc/freesmartphone/oeventsd/rules.yaml?
>>
> Yup. Did that. But had not uncommented the SCORouting = PCM line in
> /etc/bluetooth/audio.conf. Once that was done a reboot, followed by mdbus -s
> org.bluez /org/bluez/`pidof bluetoothd`/hci0/dev_xx_xx_xx
> mdbus -s
> org.bluez /org/bluez/`pidof bluetoothd`/hci0/dev_xx_xx_xx_xx_xx_xx
> org.bluez.Headset.Connect and the headset is up.
> Thanks - finally I can use it!
>
> A few suspends later - I need to org.bluez.Headset.Connect, but the pid
> has
> changed.
that's why you use
pidof bluetoothd
in
Hi,
arne anka wrote:
>
> did you add the rules to
> /etc/freesmartphone/oeventsd/rules.yaml?
>
Yup. Did that. But had not uncommented the SCORouting = PCM line in
/etc/bluetooth/audio.conf. Once that was done a reboot, followed by mdbus -s
org.bluez /org/bluez/`pidof bluetoothd`/hci0/dev_xx_x
did you add the rules to
/etc/freesmartphone/oeventsd/rules.yaml
?
they actually do the loading of the gsmbluetooth.state file -- and
theoretically should do the unloading resp loading of gsmhandset.state,
when no bt headset is connected.
___
Openmok
Aargh!
The Digital Pioneer wrote:
>
> You say it was already commented... Did you uncomment it? That line MUST
> be
> uncommented (so bluez parses it) before bluetooth calls will work.
>
So - I've managed to spend over 5 hrs doing and redoing everything after
mis-reading that as __comment__ S
On Tue, Jul 28, 2009 at 9:43 PM, c_c wrote:
>
> Hi,
> Well, I've been trying to get my headset (Jabra 125) to work and I must
> say I've not been able to get anything going.
> Steps taken - (/etc/bluetooth/audio.conf SCORouting=PCM was already
> commented)
You say it was already commented...
Hi,
Well, I've been trying to get my headset (Jabra 125) to work and I must
say I've not been able to get anything going.
Steps taken - (/etc/bluetooth/audio.conf SCORouting=PCM was already
commented)
1. shr-settings bt on
2. /etc/init.d/bluetooth start
3. simple-agent hci0 {my headset add} 1
On Mon, Jul 13, 2009 at 06:11:25PM +0200, kimaidou wrote:
> I followed some earlier talks of people who tryed manually to set up gsm
> talks through BT headset, but it was very low level (with scary command
> lines, and about 10 different manipulations to do).
Someone has to do so and report b
Anyone tried Nokia BH-103 with SHR? The bluetooth does not radiate directly
into your head, which is kinda cool, I guess. And the price is also nice -
around 35 EUR.
2009/7/16 The Digital Pioneer
> Note of interest to those looking for a bluetooth headset: you can get mine
> from Newegg for a re
Note of interest to those looking for a bluetooth headset: you can get mine
from Newegg for a really good deal (for that headset, at least) and it's
known to work. URL is:
http://www.newegg.com/Product/Product.aspx?Item=N82E16875978056
For those who don't like clicking links, it's $34 with free shi
On Thu, 16 Jul 2009 10:44:31 +0200
"arne anka" (AA) wrote:
>> setting up bt-headset-enabled: 0
>
>where?
/etc/freesmartphone/opreferences/conf/phone/default.yaml
please read up this
http://wiki.openmoko.org/wiki/Manually_using_Bluetooth#Once_Again.2C_Bluetooth_Headset_on_Freerunner
Petr
__
> setting up bt-headset-enabled: 0
where?
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Yup, I figured it was something like that.
Now the question goes, if I have a no-bluetooth profile, and I set it then
restart the services, will that do the trick, or do I have to edit the
default profile every time?
___
Openmoko community mailing list
c
>doesn't that imply it doesn't work? having to reboot the phone to go
>back to handset really means to me that it doesn't work.
setting up bt-headset-enabled: 0 and running
killall ophonekitd
/etc/init.d/frameworkd restart
ophonekitd&
will turn switch to handset without rebooting.
to re-enabl
>
> I could if I knew what services need to be restarted exactly, I had to
>
do a reboot then anyways so that would have been easier than figuring
> out which services to restart and why mokonnect wouldn't stop even with
> a killall mokonnect.
Did you try killall -9 mokonnect? If that won't kill
The Digital Pioneer wrote:
> Reboot with the headset off? If that works, then why couldn't you just
> restart a few services (ophonekitd, frameworkd and the like)?
>
>
I could if I knew what services need to be restarted exactly, I had to
do a reboot then anyways so that would have been easier th
doesn't that imply it doesn't work? having to reboot the phone to go
back to handset really means to me that it doesn't work.
Adam Jimerson wrote:
> David Ford wrote:
>
>> hmm, perhaps the phone should ping the BT earpiece and see if it's
>> available before assuming it is :D
>>
> That sh
Reboot with the headset off? If that works, then why couldn't you just
restart a few services (ophonekitd, frameworkd and the like)?
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
David Ford wrote:
> hmm, perhaps the phone should ping the BT earpiece and see if it's
> available before assuming it is :D
>
That should work, at this point right now to go from BT headset to
phone, the user needs to restart the phone with the headset off.
> Adam Jimerson wrote:
>> Yes thanks t
Petr Vanek writes:
> so bluetooth support is working, thank you! now, how is the bluetooth
> support supposed to work? seems like at this point my phone is
> configured for bluetooth (one particular device) and nothing else
> (cannot make phones via handset). the bluetooth section in default.yaml
On Tue, 14 Jul 2009 22:00:33 -0400
David Ford (DF) wrote:
>hmm, perhaps the phone should ping the BT earpiece and see if it's
>available before assuming it is :D
>
>Adam Jimerson wrote:
>> Yes thanks to the updated wiki page I also got my bt headset
>> working, but does the phone see when the bt
Steven King writes:
> On Tuesday 14 July 2009 12:28:47 The Digital Pioneer wrote:
>> Confirming again, I have my headset working perfectly after uncommenting
>> the line Paul mentioned and rebooting. :D
>
> Now I just need to figure out how to get the AVRCP bits working so I can use
> the
> cont
Adam Jimerson writes:
> On Tuesday 14 July 2009 06:58:45 pm Steven King wrote:
>> On Tuesday 14 July 2009 12:28:47 The Digital Pioneer wrote:
>> > Confirming again, I have my headset working perfectly after uncommenting
>> > the line Paul mentioned and rebooting. :D
>>
>> After following the lates
hmm, perhaps the phone should ping the BT earpiece and see if it's
available before assuming it is :D
Adam Jimerson wrote:
> Yes thanks to the updated wiki page I also got my bt headset working, but
> does
> the phone see when the bt headset is turned off? After turning off my bt
> headset and
On Tuesday 14 July 2009 06:58:45 pm Steven King wrote:
> On Tuesday 14 July 2009 12:28:47 The Digital Pioneer wrote:
> > Confirming again, I have my headset working perfectly after uncommenting
> > the line Paul mentioned and rebooting. :D
>
> After following the latest instructions in the wiki, re
>Now I just need to figure out how to get the AVRCP bits working so I can
>use the controls on the bt3030 to answer/hangup...
I've wanted to start a separate topic around this, but would cvoicecontrol
be a suitable solution to get voice dialing working? So a BT headset button
push notifies cvoi
On Tuesday 14 July 2009 12:28:47 The Digital Pioneer wrote:
> Confirming again, I have my headset working perfectly after uncommenting
> the line Paul mentioned and rebooting. :D
After following the latest instructions in the wiki, rebooting the phone and
restarting my headset, I got it working w
Confirming again, I have my headset working perfectly after uncommenting the
line Paul mentioned and rebooting. :D
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Petr Vanek writes:
>>full log here: http://www.pastebin.cz/20912
>>
>>so it's not really the way Paul says... yet
The error you see (method SetBTHeadsetPlaying emited error:
org.bluez.Error.NotAvailable: Operation not Available) has nothing to
do with FSO, it's bluetoothd misconfiguration.
Uncom
>full log here: http://www.pastebin.cz/20912
>
>so it's not really the way Paul says... yet
no restart, just several few calls and now it looks different...
http://www.pastebin.cz/20913
Petr
___
Openmoko community mailing list
community@lists.openmo
>> any idea, have i missed something?
>>
>> Petr
>>
>>
>
>I had a similar problem, after editing
>/etc/freesmartphone/opreferences/conf/phone/default.yaml and rebooting
>I had no sound at all and the phone would never register for some
>reason.
i had the same. started kind of fresh again end ende
Petr Vanek wrote:
> On Tue, 14 Jul 2009 11:22:43 +0400
> Paul Fertser (PF) wrote:
>
>> The Digital Pioneer writes:
BTW, have you tried disabling esco or not?
>>>
>>> Give me a command to run or a conffile to edit, or a page of
>>> instructions to follow and I'll do it.
>>
>
> i am trying it
On Tue, 14 Jul 2009 11:22:43 +0400
Paul Fertser (PF) wrote:
>The Digital Pioneer writes:
>>> BTW, have you tried disabling esco or not?
>>
>> Give me a command to run or a conffile to edit, or a page of
>> instructions to follow and I'll do it.
>
i am trying it now but somehow no luck at all.
Just noticed this in my frameworkd.log when making a call trying to use
headset:
2009.07.14 08:45:57.857 oeventsd.action ERRORmethod
SetBTHeadsetPlaying emited error: org.bluez.Error.NotAvailable: Operation
not Available
Could that be the cause?
__
Paul Fertser ha scritto:
> DJDAS writes:
>
>> Consider I didn't change anything in my distro (kernel, packages, libs,
>> etc) but there were cases of both working (to be honest the Nokia one
>> worked only two times and it isn't broken as I use it with my Nokia cell
>> phone in some cases) a
DJDAS writes:
> Consider I didn't change anything in my distro (kernel, packages, libs,
> etc) but there were cases of both working (to be honest the Nokia one
> worked only two times and it isn't broken as I use it with my Nokia cell
> phone in some cases) and the audio is correctly routed (I
Paul Fertser ha scritto:
> The Digital Pioneer writes:
>
>> Paul said that the connection for bluetooth runs straight from one chip to
>> the other, without really
>> involving ALSA at all. Is there a way we can make it involve ALSA, since
>> bluetooth works perfectly
>> through ALSA?
>>
The Digital Pioneer writes:
>> BTW, have you tried disabling esco or not?
>
> Give me a command to run or a conffile to edit, or a page of
> instructions to follow and I'll do it.
I don't have much hope for it but here's what i meant:
rmmod sco
modprobe sco disable_esco=1
--
Be free, use free
On Tue, Jul 14, 2009 at 11:14:29AM +1000, Denis Johnson wrote:
> If what you are suggesting is that it is now expected to work at the
> FSO dbus level albeit needing some initial pairing to be setup without
> a gui (which is fine if it is a one time exercise)
Only one external cli command is neede
>
> BTW, have you tried disabling esco or not?
Nope, I'm afraid I still don't know how. Sorry, but I'm a dumb Jerry. Give
me a command to run or a conffile to edit, or a page of instructions to
follow and I'll do it. Short of that, IDK anything. :(
I understand you when you say bluetooth support
there's plenty of end-user interest, but none of the BT headsets i've
tried are functional. i'm not willing to keep buying BT toy after BT
toy that doesn't work. for headsets they pair but then there's nothing
but silence. buttons are useless and playing audio outside phone calls
is also useless
On Tue, Jul 14, 2009 at 10:29 AM, Paul Fertser wrote:
> Denis Johnson writes:
>> On Mon, Jul 13, 2009 at 11:21 PM, Paul Fertser wrote:\
>>> BT support for FSO already works for quite some time (several
>>> months). Lack of interest from end-users is something that clearly
>>> shows the developers
Denis Johnson writes:
> On Mon, Jul 13, 2009 at 11:21 PM, Paul Fertser wrote:\
>> BT support for FSO already works for quite some time (several
>> months). Lack of interest from end-users is something that clearly
>> shows the developers that they shouldn't waste time improving it.
>
> On the cont
On Mon, Jul 13, 2009 at 11:21 PM, Paul Fertser wrote:\
> BT support for FSO already works for quite some time (several
> months). Lack of interest from end-users is something that clearly
> shows the developers that they shouldn't waste time improving it.
On the contrary, I feel this is one of the
The Digital Pioneer writes:
> Paul said that the connection for bluetooth runs straight from one chip to
> the other, without really
> involving ALSA at all. Is there a way we can make it involve ALSA, since
> bluetooth works perfectly
> through ALSA?
Bluetooth for you works perfectly only one
Jim Morris writes:
> The Digital Pioneer wrote:
>> Well, as yet another Jerry, I don't need a GUI for bluetooth. I'm
>> perfectly happy to edit configs and run commands all day long, so long
>> as at the end of the day (or week... Month... Year) it works. Only once
>> we've gotten that far do I
Paul said that the connection for bluetooth runs straight from one chip to
the other, without really involving ALSA at all. Is there a way we can make
it involve ALSA, since bluetooth works perfectly through ALSA?
___
Openmoko community mailing list
commu
The Digital Pioneer wrote:
> Well, as yet another Jerry, I don't need a GUI for bluetooth. I'm
> perfectly happy to edit configs and run commands all day long, so long
> as at the end of the day (or week... Month... Year) it works. Only once
> we've gotten that far do I see a point in creating a
Well, as yet another Jerry, I don't need a GUI for bluetooth. I'm perfectly
happy to edit configs and run commands all day long, so long as at the end
of the day (or week... Month... Year) it works. Only once we've gotten that
far do I see a point in creating a GUI.
So if there are any Toms out th
> I followed some earlier talks of people who tryed manually to set up gsm
talks through BT headset, but it was very low level (with scary command
lines, and about 10 different manipulations to do). Then I heard FSO5.5 will
have >the "famous" bt headset support. I was happy, and thought : "Ok, I
wi
Hi all !
Let me explain why you are frustrated : they is somtimes a big gap between
power coder who follow all the lists and tracs and wikis ("Tom") AND some
end users who know a bit of linux, are opensource lovers too, but have not
enough time and skill to understrand everything ("Jerry")
Tom wo
The Digital Pioneer writes:
> Well here's an end user who's interested. :\
One end-user is not enough i'm afraid. Moreover i'm personally _very_
frustrated by the absence of interest from general public. There were
so many complains about lack of bluetooth support and when it's
finally there it o
Well here's an end user who's interested. :\
Currently i have no other ideas except disabling eSCO
> support in kernel and bluez (probably it's even a bug in the firmware
> of the chip we use), but i haven't tried it yet as i don't have access
> to that non-working headset currently.
OK, how do
kimaidou writes:
> hum... I heard here the FSO 5.5 will provide a "bt headset
> thing". Will this change something here ? Like help people to
> connect the bt and transfer audio with a dbus command ?
BT support for FSO already works for quite some time (several
months). Lack of interest from end-
hum... I heard here the FSO 5.5 will provide a "bt headset thing". Will
this change something here ? Like help people to connect the bt and transfer
audio with a dbus command ?
Kimaidou
2009/7/13 Paul Fertser
> The Digital Pioneer writes:
> > Progress!!! After reflashing, it now loads the gsm
The Digital Pioneer writes:
> Progress!!! After reflashing, it now loads the gsmbluetooth statefile. I hear
> nothing over my
> headset, but that's progress!
>
> Am I supposed to have a defined bluetooth device in asound.conf or something?
Of course not. This method (with gsmbluetoothfile) uses
Progress!!! After reflashing, it now loads the gsmbluetooth statefile. I
hear nothing over my headset, but that's progress!
Am I supposed to have a defined bluetooth device in asound.conf or
something?
___
Openmoko community mailing list
community@lists.
Well, screw it. I'm reflashing and hoping for the best. :P Wish me luck.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
The Digital Pioneer writes:
> Perhaps it is and frameworkd isn't logging it. What log level does
> it appear as for you?
Hm, i have DEBUG for oeventsd and ogsmd, others are INFO. I don't
remember and i've already lost the logs.
> Also, which wiki page are you referring to? I'm looking at Manuall
Perhaps it is and frameworkd isn't logging it. What log level does it appear
as for you?
Also, which wiki page are you referring to? I'm looking at Manually Using
Bluetooth
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.ope
The Digital Pioneer writes:
> Well, I did the usual setting of variables in the profile, but
> nothing of interest appears in frameworkd.log anyways.
> Surely there are some dbus calls I can make to see the state of this
> thing, aren't there??
Yes, but it doesn't look like bluez4 api is well-doc
Well, I did the usual setting of variables in the profile, but nothing of
interest appears in frameworkd.log anyways.
Surely there are some dbus calls I can make to see the state of this thing,
aren't there??
___
Openmoko community mailing list
community
The Digital Pioneer writes:
> OK, I've beaten this horse to death several times now, but I'm ready
> to start beating afresh. I want to use my bluetooth headset for GSM
> calls. I have already paired my headset with my phone, and I can
...
> So! Has anyone actually managed this? If so, how?! If no
67 matches
Mail list logo
