OESF Portables Forum
General Forums => General Discussion => Topic started by: Guest_Bane on July 07, 2004, 05:29:54 pm
-
Is there any news on any kind of a blueZ gui ?
What ever happened to the one pictured here (http://www.killefiz.de/zaurus/showdetail.php?app=198).
Or is that gui from some rom other than the sharp rom ?
I know this is a repost but I am curious if anyone knows anything ?
BlueZ is great but really slow to configure new devices manually and slow to use through command line.
-
That GUI is for the Opie and even then I think development stopped.
I was working on a GUI for the Sharp ROM, but I haven't had much time: http://www.cpinkney.org.uk/zaurus.html#bluetooth (http://www.cpinkney.org.uk/zaurus.html#bluetooth)
-
Hi tumnus,
folloing your link and going through a couple of others, I got to :
http://bluez.sourceforge.net/download/zaurus/ (http://bluez.sourceforge.net/download/zaurus/)
It seams to have some files which are very new but an older bluez-zaurus file
Just wondering how the 2 relate.
-
Those older BlueZ SF ipks are for the SL5500 v2.x Sharp ROMs. I hadn't noticed those newer ipks. They're only a month old.
I emailed the BlueZ mailing lists several times, months and months ago, that I have created updated ipks and that those old ipks they have will not work on anything other that the 2.x ROMs, but I never heard anything back. I guess the previous maintainer finally got round to creating updated ipks.
-
Very cool. Good to hear things are still in progress. Should make interacting with blueZ alot more fast and user friendly.
-
Tumnus:
Are you still working on your bluetooth GUI? If so, when do you think it will be ready for outside testing? I am willing to be a beta-tester for you. Your bluetooth GUI should let me do some of the things discussed in this thread (https://www.oesf.org/forums/index.php?showtopic=5890)
Does the current Bluez-Zaurus implementation include the OBEX Push and/or File Transfer protocols? If so, how may I use them from the command line? BlueZ.org leaves a lot to be desired in the way of documentation...
Thank you!
-
Progress is a bit erm non-existant at the moment. Maybe once I've moved house I'll get started on it again. I need to keep up my C++ skills anyway since I've only been able to do VB stuff at work recently
The BlueZ OBEX stuff is still very rudementary at the moment. Last time I checked, there was a test OBEX app in their CVS that didn't do very much. I certainly don't know enough about the BlueZ drivers and OBEX to progress that any further and I couldn't even get the program and OBEX library compiled for ARM anyway.
-
I have made some modification for the PAN network applet to add DHCP PAN connections. I would like to help on the develop for the obex push utilities, but hate the idea of doing it from the beggining.
-
A good place to start for a BlueZ GUI would be to look at the KDE Bluetooth GUI apps. I use them on my laptop for doing OBEX file transfers to/from my phone (a Sony K700i) using the BlueMonkey card I originally bought for my Zaurus, but for some reason it doesn't work with the Z anymore (since a crash and full reboot wiped out my old setup)....I wish that BT faq would come back
-
What about Affix (http://affix.sourceforge.net)? It appears to be a continuing project (last update on July 23), is in it's third release, and has good documentation. Here are the profiles it supports:
- General Access Profie
- Service Discovery Profile
- Serial Port Profile
- DialUp Networking Profile
- LAN Access Profile
- OBEX Object Push Profile
- OBEX File Transfer Profile
- PAN Profile
- FAX Profile
There are already Affix packages available for the Zaurus. I would definitely like to try this out for myself, at least. How would I go about removing the built-in BlueZ in Cacko 1.21 (which I am assuming should be done before I install Affix)?
-
Would resuming work on the Opie bluetooth stuff be an option for anyone?
-
I am not a programer, so I cannot help with that part. However, I will donate some hardware to whichever development team satisfies my bluetooth needs (see this thread (https://www.oesf.org/forums/index.php?showtopic=5890))
-
Where are the affix ipks for the zaurus that support obex??!!
-
Affix Feeds:
Stable (http://affix.sourceforge.net/feeds/stable/zaurus/)
Unstable (http://affix.sourceforge.net/feeds/unstable/zaurus/)
More Info (http://affix.sourceforge.net/afe/) (old stuff, though, and several broken links)
-
Zaurus support from the Affix project kind of stopped a while ago. I think they had a developer or two leave but I may be wrong.
The BlueZ drivers support every profile and as cwaig said, the KDE Bluetooth framework uses OBEX and the BlueZ drivers (I've used it on my PC too). AFAIK, Affix still only has a test app for OBEX stuff. Also, the way in which RFCOMM works with BlueZ makes it much easier to work with other applications, like the Network applets.
It's just a case of finding time to look through the existing code and porting it to the Zaurus.
-
Tumnus,
The screenshots for bluez with obex push look very nice, would you be interested on sharing the sources?
Is there anywhere to commit changes to pannetworkapplet sources (to add the dhcp for pan)?
-
I might try to pick up this one at some point - it'd be nice to get it going, and I've been thinking about adding Bluetooth support to IRK for a while now (Pocketop have a Bluetooth PDA keyboard coming out RSN, which would be dead handy....).
Anyone got a copy of the old Bluetooth howto page for getting it to work again?
-
cwaig, the howto is back up on the ZUG site.
luimarma, there's practically no code behind the Obex stuff in the Bluetooth GUI. I need to finish some things off and rework some other bits and comment everything. When it's in a usable state I will release it with the basic working along with the source. Then someone (cwaig?) could add the Obex bit. As for the network applets, I could add you to the project here: http://community.zaurus.com/projects/bluez (http://community.zaurus.com/projects/bluez) . Are you registered there?
-
I have just registered into comunity.zaurus.com I will commit the changes when allowed to.
Thanks!
-
luimarma, Did you use the same username?
Also, can you login to the community section? I think you may have to email one of the admins to get your account setup correctly on the Community bit.
Here's a thought... Does anyone have a 6000W? That has bluetooth in it already, so what does it have in terms of a config app, Obex support, etc? If it's any decent, I wonder if we can legally nick the Bluetooth software in the 6000W ROM. Only problem then might be no source.
-
Yes, I used the same login and I can login and logout without problems.
-
The BlueZ OBEX stuff is still very rudementary at the moment. Last time I checked, there was a test OBEX app in their CVS that didn't do very much. I certainly don't know enough about the BlueZ drivers and OBEX to progress that any further and I couldn't even get the program and OBEX library compiled for ARM anyway.
Tumnus:
I'm confused... did you mean that the BlueZ OBEX is rudimentary, or just the Zaurus implementation? I took it to mean the former. There is also the matter of the OBEX library. Are you still working on getting it ported to the Zaurus?
I would be happy just to be able to use the OBEX utilities from the command line until somone releases a GUI. If that will not be happening in the near future, then I would like to at least try Affix. How difficult would it be to remove the built-in BlueZ from Cacko 1.21? I would greatly appreciate it if someone could tell me how to do this.
I appreciate tumnus, luimarma, and cwaig's comments and info, and your willingness to work on these issues. I hope to see some progress on your BlueZ-Zaurus enhancements soon. Thank you!
-
I'm confused... did you mean that the BlueZ OBEX is rudimentary, or just the Zaurus implementation? I took it to mean the former. There is also the matter of the OBEX library. Are you still working on getting it ported to the Zaurus?
The KDE Bluetooth Framework (http://kde-bluetooth.sourceforge.net/) shows the BlueZ Obex implementation is quite complete. For myself, at the moment, I am working on getting basic Bluetooth configuration working in a nice GUI instead of people having to edit text files. Obex support was last on the list. It may be someone (like Debian) has an ARM version of libopenobex, but I have a feeling that there may be libc version issues.
I appreciate tumnus, luimarma, and cwaig's comments and info, and your willingness to work on these issues. I hope to see some progress on your BlueZ-Zaurus enhancements soon. Thank you!
Yes, it's nice to see some more people interested in working on this. Maslovsk did an excellent job with the Bluetooth network applets and it's good to have some more support too.
-
The KDE Bluetooth Framework (http://kde-bluetooth.sourceforge.net/) shows the BlueZ Obex implementation is quite complete.
I wonder how much work it would be to get the KDE Bluetooth Framework running on the Zaurus ....
Having a quick look at the pages and links, I found some quite useful software for my project ( which will I start later this year ) to get a platform independent mobile phone manager implemented, which syncs Mobile phones with the PIM data stored in KO/Pi and KA/Pi.
I did not decide to use some specific bluetooth stuff ( I was thinking about to communicate to the phone via serial connection, that may be bluetooth, Irda or serial port) , but maybe it would be useful.
z.
-
It may be someone (like Debian) has an ARM version of libopenobex, but I have a feeling that there may be libc version issues.
libopenobex (http://packages.debian.org/cgi-bin/search_packages.pl?keywords=libopenobex&searchon=names&subword=1&version=stable&release=all)
Of course, I do not know where to go from here; I am learning Linux from the Zaurus (probably the most difficult way, I'm sure). A manual search shows both libglib 1.2 and libc6 present on my Zaurus (I'm sure there's a fancier way to see which dependencies exist). I do not know what do do with a .deb file, though.
Mickeyl:
I also see that OpenZaurus has libopenobex in the 3.3.5/Shepherd feed (http://openzaurus.org/official/3.3.5/shepherd/ipks/). Have you or anyone else in your team been able to test the functionality of bluetooth OBEX? I am already interested in trying OpenZaurus, and bluetooth support would be a deciding factor. By the way, have you seen this thread (https://www.oesf.org/forums/index.php?showtopic=5890&st=0&)?
-
Any word on the BlueZ gui. The last post I found was from many months ago. That last post in this thread was from July 2004. Did this thread move somewhere else? Or was the entire idea scrapped ?
-
I worked on it over Christmas, haven't got much further really, sorry. If my wife will let me, I need to take a weekend and try and get it to a usable state.
-
I use Cacko ROM 1.22 on a C860. There's it a command line tool called obexpush included. This and receiving OBEX transfers works. Does Cacko also use Bluez?
-
Tumnus, even if it isn't pretty, just release it. I'm sure some people here can fix it :-)
-
- Tumnus: the zaurus community link for BlueZ leads to the "Sharp Support Center". Patently useless, that. How would one go about getting the source for BlueZ alpha4 that runs on the C1000? And of course getting into the development community at large. (grin) Thanks for your time...
-
- Tumnus: the zaurus community link for BlueZ leads to the "Sharp Support Center". Patently useless, that. How would one go about getting the source for BlueZ alpha4 that runs on the C1000? And of course getting into the development community at large. (grin) Thanks for your time...
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=80527\")
Yeah, Sharp used to host projects, but they closed that down a while ago. I've written a quick howto for compiling BlueZ here:
[a href=\"https://www.oesf.org/forums/index.php?showtopic=12628&view=findpost&p=80976]https://www.oesf.org/forums/index.php?showt...indpost&p=80976[/url]
-
Tumnus, even if it isn't pretty, just release it. I'm sure some people here can fix it :-)
[div align=\"right\"][a href=\"index.php?act=findpost&pid=80086\"][{POST_SNAPBACK}][/a][/div]
Well, it's more a case of not being in a working state at the moment.
I blame my wife . She calls my Zaurus my mistress when I spend too much time on it
I'm beginning to think perhaps someone else with more time should start from scratch . I'm busier than ever at the moment, looking for a job since they announced the closure of the site I work at.
OK, in June I will seriously dedicate a weekend to it, to at least get it changing all the config options and scanning for other Bluetooth devices and put it up for someone else to finish.
-
Any updates on the blueZ GUI front. I would kill for a half working beta to play with.
-
Any updates on the blueZ GUI front. I would kill for a half working beta to play with.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=98057\"][{POST_SNAPBACK}][/a][/div]
Hi Bane,
What features are you looking for from the Bluez gui? I'm working on a Bluetooth GPRS GUI - for making simple network connections via your phone. Hoping to release in a week or so.
-
Just looking for basic functions from a gui interface.
To start I would like to be able to from the gui initiate a scan for devices and pair with the devices I detect. If your application is specific for bluetooth gprs connections thats great too.
My company has some bluetooth gps's mounted and turned on but not in use in some of their vehicles. I would love to be able to scan, pair and then map the gps into qpegps quickly. I have gotten my personal bluetooth gps going easily. It just takes time to reconfigure.
I assume it would be faster from the gui without the need to type in mac addresses over and over again.
Thats my wishlist.