The sneak peak thread

[justchat_1]

FYI, Hal is being replaced with DeviceKit on Linux systems. The cool thing is that it's actually easier to detect added/removed devices. Just in case you didn't know already.

Figures just when I get something working they would change it (ok maybe i should have noticed that hal has been depreciated since '08 but still)..... Looks like the properties were just renamed but hopefully I can use the same trick for device mount notifications. Right now they tell you when a device is added but not when its actually mounted (which is useless). Maybe one day they'll actually add them in and make it easy......who am I kidding, this is linux

Three versions and still only an audio server stub...no access to volume change notifications. Last I saw, even gnome didn't have audio change notifications it just listened for the volume change keys and queried the audio server for the new volume.

[tripzero]

Figures just when I get something working they would change it (ok maybe i should have noticed that hal has been depreciated since '08 but still)..... Looks like the properties were just renamed but hopefully I can use the same trick for device mount notifications. Right now they tell you when a device is added but not when its actually mounted (which is useless). Maybe one day they'll actually add them in and make it easy......who am I kidding, this is linux

Mount notifications would come in the "PropertiesChanged" signal on the device. Which you than can check the IsMounted property if it's mounted or not. Not sure on the exact signal or property names, but that's what's coming off the top of my head...

Three versions and still only an audio server stub...no access to volume change notifications. Last I saw, even gnome didn't have audio change notifications it just listened for the volume change keys and queried the audio server for the new volume.

The new version of pulseaudio (0.9.22) has a dbus api that should give you this kind of notification. Unfortunetly, the dbus-protocol-module for pulse doesn't seem to be included in Ubuntu Lucid yet. I'm making a push for it to be included in MeeGo though. I'm having major headaches dealing with pulseaudio's c api right now, so i can definitely relate to some of the issues you are likely having.

[justchat_1]

Mount notifications would come in the "PropertiesChanged" signal on the device. Which you than can check the IsMounted property if it's mounted or not. Not sure on the exact signal or property names, but that's what's coming off the top of my head...

Yea i was listening for device added notification and then grabbing the device object and listening for the ismounted to change....so I guess its close enough. Still not as nice as a "your drive is now ready and located here" notification

The new version of pulseaudio (0.9.22) has a dbus api that should give you this kind of notification. Unfortunetly, the dbus-protocol-module for pulse doesn't seem to be included in Ubuntu Lucid yet. I'm making a push for it to be included in MeeGo though. I'm having major headaches dealing with pulseaudio's c api right now, so i can definitely relate to some of the issues you are likely having.

yup exactly.... any idea if 0.9.22 will get released as an update for previous versions? (i'm really not familiar with the whole ubunutu update model)

[BigBadWolf]

I just found this and downloaded it. After being frustrated with the lack of real movement on CF3 and the dev of SD disappearing, I'll be giving it a bit of a workover this evening.

[bakin113]

What bluetooth stack are you using with your verizon android?

[justchat_1]

What bluetooth stack are you using with your verizon android?

Its a custom bluetooth stack developed by my company....the version in the demo is currently unofficially known as OMBluetooth.

[tripzero]

yup exactly.... any idea if 0.9.22 will get released as an update for previous versions? (i'm really not familiar with the whole ubunutu update model)

(a little late, but...) After a ubuntu release, only security and critical bugfixes will be pushed out to users. Also, ubuntu 10.04 doesn't have 0.9.22 with the nice dbus interface. Maybe in 10.10... we shall see.

[bakin113]

Its a custom bluetooth stack developed by my company....the version in the demo is currently unofficially known as OMBluetooth.

That looks really good. I have just downloaded version 0.6 and replaced roadrunner with openmobile. RR has officially broke my last nerve. I'm still testing OM but I don't think I'll keeping RR.

Is OMBluetooth in 0.6, or is it planned to be included in 0.7?


Also please let me know if I can help the project, or test. I am a third year CS major and have experience with c++; c#; and java.

[justchat_1]

That looks really good. I have just downloaded version 0.6 and replaced roadrunner with openmobile. RR has officially broke my last nerve. I'm still testing OM but I don't think I'll keeping RR.

Is OMBluetooth in 0.6, or is it planned to be included in 0.7?

Neither...still in development. It takes a tremendous amount of R&D to get a universal bluetooth solution for hadnsfree, a2dp, avrcp, sync, pbap, etc so its gonna be awhile longer before something is available to end users.

Also please let me know if I can help the project, or test. I am a third year CS major and have experience with c++; c#; and java.

Were always open to new developers...if you have any areas in particular your interested in helping out just let me know. The dev team uses google wave for development, feel free to shoot me a wave (jdomnitz) and ill add you in.

[gothate]

RR has officially broke my last nerve. I'm still testing OM but I don't think I'll keeping RR.

Ugh, so so true.
Can't wait to start testing 0.7, I'm stuck using winamp in my car for now and 0.6 wasn't solid enough to test for even basic music usage. Excited about this!