Hello, first of all, I want to thank you for doing this great application. This application is a must have!!
@ MrThunderfield : I had the same problem, I did the following things to make it work on my pc (Windows 7 professional x64). Remove the pairing (on devices and printers). Then, open BlueMaemo on your n900. Click on "Wait for connection". After that, on your pc, find the n900, and pair with it. I had the same problem, some drivers weren't installed, but all the funtions of maemoblue still work on my cellphone.
I found a bug, I installed the one in extras-devel. When I use the "Media control" and I change the settings (actions of the buttons), I need to restart the application so all the buttons take effect of the new settings. Please keep up the good work, and if you accept donations, please tell me you website to be able to support you.
Hello, first of all, I want to thank you for doing this great application. This application is a must have!!
@ MrThunderfield : I had the same problem, I did the following things to make it work on my pc (Windows 7 professional x64). Remove the pairing (on devices and printers). Then, open BlueMaemo on your n900. Click on "Wait for connection". After that, on your pc, find the n900, and pair with it. I had the same problem, some drivers weren't installed, but all the funtions of maemoblue still work on my cellphone.
I found a bug, I installed the one in extras-devel. When I use the "Media control" and I change the settings (actions of the buttons), I need to restart the application so all the buttons take effect of the new settings. Please keep up the good work, and if you accept donations, please tell me you website to be able to support you.
1 - Plug my USD BT Stick into my PC.
2 - Turn BT on , on my N900
3 - Load BlueMaemo
4 - Click "Establish Connection" on my N900
5 - Select My PC from the list of BT devices
6 - When prompted if I want to connect I press yes.
7 - I then see "Trying to Connect"
8 - After a few seconds I get this message "unable to connect to ... damn"
1 - Plug my USD BT Stick into my PC.
2 - Turn BT on , on my N900
3 - Load BlueMaemo
4 - Click "Establish Connection" on my N900
5 - Select My PC from the list of BT devices
6 - When prompted if I want to connect I press yes.
7 - I then see "Trying to Connect"
8 - After a few seconds I get this message "unable to connect to ... damn"
Step 2 is not needed, but you missed step 0 :
* Remove any existent pairings between your N900 and your computer (in both devices).
ok I removed all pairings from PC and N900.
Turned off N900 bt before loading BlueMaemo.
I'm using Windows 7
I then get asked to pair.
I finish pairing then wait for the pc to finish install drivers.
I think click yes to connect on my N900
I get the same messages as above :-(
installed bluemaemo but it got a veir error.
I do not have any paired deviced by the way.
And my device name is N900 so no spaces even.
~ $ bluemaemo
False
Running BlueZ 4
Traceback (most recent call last):
File "/opt/bluemaemo/bluemaemo", line 1306, in <module>
gui = GUI( options, args )
File "/opt/bluemaemo/bluemaemo", line 758, in __init__
self.check_bt_status()
File "/opt/bluemaemo/bluemaemo", line 869, in check_bt_status
self.paired_devices[str(client_name)] = str(client_addr)
UnicodeEncodeError: 'ascii' codec can't encode character u'\u2019' in position 10: ordinal not in range(128)
installed bluemaemo but it got a veir error.
I do not have any paired deviced by the way.
And my device name is N900 so no spaces even.
~ $ bluemaemo
False
Running BlueZ 4
Traceback (most recent call last):
File "/opt/bluemaemo/bluemaemo", line 1306, in <module>
gui = GUI( options, args )
File "/opt/bluemaemo/bluemaemo", line 758, in __init__
self.check_bt_status()
File "/opt/bluemaemo/bluemaemo", line 869, in check_bt_status
self.paired_devices[str(client_name)] = str(client_addr)
UnicodeEncodeError: 'ascii' codec can't encode character u'\u2019' in position 10: ordinal not in range(128)
That's a known bug.
Worksforme: Remove any apostrophe (') or other special character from your PC name and start again. This bug is already fixed and the fix will be released in the next alpha version.