Posts tagged reason

ARM-Chip cuts OLPC-XO Power Consumption in Half

0

“While the availability of power in certain regions of the world cannot be solved by the OLPC, it can improve upon the power use of the XO Laptop. And with v1.75 they have managed to half that power use. The reason this has been made possible is the move to use an ARM rather than an x86 processor. So now rather than drawing 4 watts of power, the XO-1.75 draws 2 watts. The new chip being used is a 1GHz Armada 610 from Marvell.”

Original

Sick and twisted fruit

1

To scratch the topic of Mobile Computing once again I want to take you through the processes of setting up an iPhone and a Nokia N97 Mini with a Bluetooth driven wireless Keyboard. The reason I’m doing this is of course due to recent events I experienced and – SPOILER ALERT – the iPhone fails miserably under almost all circumstances. Successful ones could unfortunately not be tested.

The Keyboard used can be seen on the following picture, accompanied by the successfully paired N97 Mini:

HPIM0277

Why it’s a Bluetooth Keyboard designed by Apple themselves, just to make it a little less tough for the iPhone one might think. But I digress.

The step-by-step Instructions for the N97 Mini (or basically any Symbian S60 device) go as follows:

  1. Download the free Bluetooth Keyboard Application from Nokia.com. Choosing the right one shouldn’t be too hard, I didn’t find one for Symbian S60 5th Edition so i just took the first one which popped up an incompatibility alert but still installed and worked fine.
  2. After opening said Application, turn on your Keyboard and pair it with the Phone. In my case this included defining a Passkey like “123456” and then entering exactly that Passkey on the Keyboard. Pressing Return should finish the pairing process. I assume this works the same on all Bluetooth enabled Keyboards.
  3. That’s it. You’re set to write some text messages or even emails with your Bluetooth Keyboard.

On the iPhone on the other hand, the situation looks as follows. (At least that’s all I found out on a jailbroken iPhone 3G with the latest jailbreakable iPhone OS 3 on it).
When you turn on Bluetooth and search for devices, the (Apple !!) Keyboard does not show up. So if I’m not wrong that takes care of our first approach. The second approach then would be taking advantage of the freedom of a jailbroken iPhone. Do some searching on Google/Youtube and what I found was a Video explaining how to use an App (namely BTStack Keyboard) from the Cydia Store (which of course comes with jailbreaking the device) to use Bluetooth Keyboards with your iPhone. The only catch you ask? It costs 5 Dollars and since I neither own an iPhone, nor a Cydia Store Account (or whatever is needed to buy their Apps) my trail to success stopped there.

If there is another approach, be it for jailbroken or non-jailbroken iPhones please let me know. Nothing would please me more than knowing that Apple isn’t having such a tight stranglehold on its customers after all. Smartphones set aside, I’m one of them as you can see from the picture.

Of course it’s not surprising that the Nokia Device works with an Apple Keyboard. The Bluetooth Standard is the same for everybody, also for Apple luckily. And of course it might not make perfect sense to everybody that I’m connecting a Keyboard to a Mobile Phone that has a QWERTZ Keyboard built-in. To be honest I’d know a lot more to do with such a keyboard on an iPhone than on this N97 Mini. Seems like it’s not supposed to happen.

Windows Search Lamp going berserk

0

Once upon a while my Internet Service Provider who i am very dissatisfied with “decides” to pull the plug on my internet connection for no reason whatsoever for a little while. So knowing that I have a HSDPA USB Modem laying around with a 3GB monthly dataplan i thought i could install its Hutchison 3G software on my Windows Server 2003 to have a backup internet connection at hand.

After some restarts the software still wouldn’t recognize the Modem so I thought I could run it in Compatibility-Mode for Windows XP. This resulted in the program window not showing up at all while it would make the “explorer.exe” stop responding entirely. When I killed the “3DataManager.exe” however this happened:

So this Flashlight we all know from the XP-days seems to try to catch up on all the CPU cycles it missed while the Data Manager was open. It stopped pretty soon afterwards though as you can see.

Go to Top