After getting Android Notifier working on my machine by installing OBEX, I installed Blueman on my Ubuntu 10.10 machine. I’m not sure why, but Blueman seems to work better with Android than Gnome Bluetooth. I like the interface of Gnome Bluetooth better than Blueman, but I could only get file transfers to run from Android to Ubuntu and not the other way around. Additionally, it’s fairly easy to change the download directory for Bluetooth file transfers to Ubuntu using Blueman. If anyone has a solution to either of these two issues, I’m all ears.

Anyway, back to Android Notifier. Once I installed Blueman, the notifier stopped working. Everything was still paired correctly and all that, but Notifier just wasn’t getting the messages. Turns out, Blueman seems to use an Indicator plugin that hijacks those notifications. Solution? Turn off the Indicator plugin. From what I can tell it doesn’t do much anyway… of course maybe I should retest sending/receiving files from my Nexus.

QUICK ANSWER:

Right click on the Blueman icon in your Notification Area. Select Plugins. And now un-check Indicator from the list on the left side. Done.

Again, I don’t know if there are any adverse effects to turning off Indicator. But I can’t imagine it’ll break anything.

I’ve been using the Android Notifier with my MacBook for some time. If you haven’t checked it out, please do. The application sends notifications to your desktop for everything from incoming texts to a low battery warning to third party notifications. It’s a great little app if you’re into that sort of thing. So when I made my switch to Ubuntu, naturally I wanted to get the Android Notifier working with my new machine.

I won’t get into how the application works or how to pair your phone with Ubuntu. There’s plenty of info on those out there. The issue that I was running into, was with my Nexus S paired and being able to send files to and from Ubuntu, I could not get Android Notifier to pick up on any of my test notifications. When setting up Bluetooth on my computer to allow for file transfers I’d discovered that Android uses OBEX to push and receive file transfers over Bluetooth. So, with this in mind, I decided to investigate how Android Notifier listens for notifications. After checking out the wiki on the project page for Notifier, I found this article regarding the protocols used by Android Notifier (thank you to the Notifier team for posting the documentation on this). Turns out for the Bluetooth connection, Notifier uses a UUID (Universally Unique Identifier) when sending notifications.

QUICK ANSWER:
While this may vary between distributions of Linux, on my Ubuntu 10.10 setup, I had to install the UUID command-line tool in order to get Android Notifier working. To do this, run the following command:

$ sudo apt-get install uuid

I hope this helps someone solve their issue using Android Notifier. I’d hate for someone to miss out such a sweet app.

First a quick review:
Quite a while ago I purchased the Logitech DiNovo Mac Edition wireless keyboard. And I have to say, I really love this keyboard. Especially compared to the Apple’s wireless keyboard. First off, it’s a full keyboard with a number pad, compared to Apple’s. Apple does make a full keyboard, but not a wireless version (at least as of this post date they don’t). Next up is battery life. The DiNovo runs extremely efficiently. I’ve had mine for months now and the battery still reads as full. Whereas when I was using the Apple wireless keyboard, my batteries would be drained after a few months of use. Granted the DiNovo takes four AAA batteries vs Apple’s three AA (or two AA with the newer keyboards). But still. I’d rather not have to worry about it, and from my experience the DiNovo lasts at least twice as long with extra batteries. Finally connectivity. The DiNovo uses a wireless USB adapter which works flawlessly. For me, I use an extra monitor with USB ports, so there’s no issue of having to constantly plugin and unplug the USB adapter from my laptop. I have a few usb devices I use in my workstation and only use one plug when hooking into my laptop. Apple’s keyboard on the other hand uses bluetooth to connect. I have had several problems with connectivity on these. My wife also has used one of these and having two in the house makes everything more difficult. In short, when they work, great. When the don’t, they’re a huge hassle and not worth the trouble shooting time.

So, although I’m annoyed with the functionality of the Dashboard Key and Brightness Keys on the DiNovo, I still would, will, and do choose the Logitech DiNovo wireless keyboard over Apple’s Wireless Keyboard hands down. It’s simply better in every respect for what I’m looking for and need.

Now for the issue at hand…
So the issue here is really quite simple. On the keyboard, as is standard on all Mac keyboards, a number of the F* keys (F1, F2, etc.) have dual functionality, mainly media control (play, pause, etc.), volume levels and brightness. For the most part everything on the keyboard works as expected. The media controls and volume controls work without a hitch. The rest however do require you to download and install the Logitech Control Center for Mac. This installs an preference pane that allows you to configure those special function keys. However, for me at least, even after installing the Logitech Control Center, my brightness (F1 and F2) and dashboard (F4) keys still didn’t work. To this date, I still don’t know why.

Hackintosh…
However, I have figured out a quick fix for the dashboard key. This hack opens the dashboard, but unfortunately does not close it the way the key works on a native Apple keyboard. To accomplish this, open the Logitech Control Center from the System Preferences on your Mac. If your keyboard is connected, you should see it listed. Click on the keyboard you wish to configure and press the Configure… button. A new window will open. Select the Keys tab in the upper left if it has not been selected already. Now you should see a list of all the special function keys and their assigned actions. If you select F4, you should see that it is set to Exposé, Dashboard & Spaces. Again, I don’t know why this doesn’t work, but it just doesn’t. As a fix, change this to Open Application. From here on the bottom of the window under Details you should be able to set which Application opens. Select Other… and find the Dashboard Application in your Applications directory. This should now cause the F4/Dashboard key to launch the Dashboard Application. Again though, pressing the key again, unfortunately, does not close the Dashboard as a native keyboard will.

EDIT:

A better fix…
So I just figured out a better fix for the Dashboard key. Essentially, what you want to do is set up a hotkey control for the Dashboard under System Preferences -> Keyboard and then set the action of the Dashboard key to Keystroke and enter the given hot-key-stroke. Ya dig?

So go to System Preferences -> Keyboard (under Hardware). Select the Keyboard Shortcuts tab. Now, select Dashboard & Dock under the left column. In the right column you should see Dashboard listed. If you double click the right side where it shows the shortcut, you should be able to enter whatever keystroke you want.

Now, go back into the Logitech Control Center and configure your keyboard (as described above). Select the dashboard button and select Keystroke as the Assigned action. Now at the bottom under Details you should be able to enter the keystroke you just entered in the Keyboard Shortcuts. Ta-Da!! Should work instantly.

With this solution, the Dashboard key will now both open and close the Dashboard.

Short Rant
It’s upsetting that things don’t just work the way they should. In addition to this issue, I use Songbird as my media player. Unfortunately, the media keys don’t work with Songbird and there’s not easy way to reset them so they do. I think these issues are all more related to Apple’s “closed box” system rather than poorly designed/implemented technologies on Logitech and Songbirds part. Of course that could just be my anti-trust conspiracy theories at work.

EDIT:

I actually just read that this is a known issue for Logitech. From what I read it appears to be something that Apple just does. Basically, media controls and brightness controls will only work on a non-Apple external keyboard if there is not an Apple keyboard connected to the computer. So if you’re on a desktop, and for some reason have two keyboards and one is a Logitech and one is an Apple, the controls will work on the Apple, but not the Logitech. Disconnect the Apple keyboard and the Logitech media controls should work. However, if you’re on a laptop, you’re pretty much just screwed as you can’t “disconnect” the laptop’s keyboard. I really fucking hate Apple’s proprietary bullshit. I’ll leave it at that.

A wise man once told me, “You have to be smarter than the machine you’re working with.” I hope this post helps someone solve an issue that I put up with for far too long.

I upgraded to Snow Leopard (OS X 10.6) from Leopard (OS X 10.5) last week and everything seemed to go off without a hitch, until…

I have a bluetooth, wireless, keyboard that I use for work. At some point in the past week, not initially, my keyboard started acting up. At first I didn’t think anything of it because the lady’s computer is also paired with the same keyboard and when the problem first occurred it was because the keyboard was connected to her computer, also on Snow Leopard, rather than mine. I ended up removing the keyboard from her bluetooth setup and re-pairing (no pun intended) the keyboard to my computer. Everything worked fine and I went through my day.

The next day, I found that my keyboard would not pair up again. WTF!? So I go through the process again, thinking maybe Laura and I did a keyboard swap or something and that was the problem. Re-paired, everything’s cool. Whatever. If it happens again, I’ll deal with it.

Finally, today, day 3, I start up my computer and the keyboard won’t connect. Immediately I try to re-pair the keyboard and suddenly the computer tells me there must be some compatibility issue. Thanks Apple. I have an Apple keyboard I’m using with an Apple Macbook Pro and I have a f***ing compatibility issue. You’d think they would make sure that bluetooth continued to work between upgrading from Leopard to Snow Leopard. Oh well.

So I resort to Google. And basically what I find is that I have to reset my System Management Controller (SMC). Do I know what an SMC is? No. Do I care? Not really… okay, so I do a little. Apparently the SMC handles a lot of the lower level operations performed by the computer like “the power button”. Sweet Apple. Okay, so what to do. You have to reset the SMC. To do this follow the steps specified here. Be sure to read through the process and select the procedure that matches your computer. Different laptops, desktops, etc. will have a different method for resetting the SMC.

All in all, it’s disappointing that Apple overlooked this issue. Seems too often that companies can be aware of an issue be keep it quiet for the majority of users that don’t use (in this case) bluetooth, while those that due have to spend have their day in frustration.