René Rebe

Finally, after a month on some outdated 1.1.3 version, we Europeans (maybe all GSM Pré’s?) get the long awaited 1.3.1 update.

Why the Palm Pré (unlike Apple’s iPhone) does not have one universal software build for all phone variants, areas, is a mystery to me.

My favorite Change: Fast forward and rewind (current play position change), yay!

However some recent speedup, e.g. hardware accelerated graphics would be welcome, too, …

Just needed to fixup some photos. Basically because I was sorting some 1600 pictures, from various cameras and people, mostly to bring them in-order and pick the best shots. Unfortunately some cameras even did not had the date set properly. Some where up to 2 year and something off (manufacturing date reset?), another just 4 months and something, yet one more about 2 and a half dayo, and the last was still running on daylight saving (winter time) and thus was one hour off, :-(

As a reminder for myself, for the next batch:

Adjust the timestamp:

exiv2 -Y 2 -O 3 -a -8:10 adjust *

Remove some random comment noise:

exiv2 -M”set Exif.Photo.UserComment charset=Ascii” *

Normalize the filenames:

exiv2 -r ‘%Y%m%d_%H%M%S_:basename:’ *

Suprisingly based on eglibc 2.10.1 (not just glibc, guess Ulrich Drepper really annoyed the last fellow developers away), GCC 4.4.1. Given the X.org log, built on an Ubuntu system.

Login auth via an custom pam_google.so.

Boots without a single message, not a single text character from neither the boot loader, nor the Linux kernel. Actually the first time I thought it did hang, failed to load something (booter, kernel, …) until the X based login mask popped up. Comes with all X drivers (even the old, esoteric ones - in contrast to Moblin, which only ships the Intel one, and VESA). But neither with an Intel Poulsbo (GMA500) driver, :-(

However, whether I want to use a system that auth’s at Google, only works when connected, and reception is good (forget most airplanes, trains, abroad (e.g. weekend, holiday) areas, etc.

And mind you: With ChromeOS Google does not even know what you searched, it even knows when you power on your NetBook, authenticate on the system, suspend, resume, certainly can track every move just with your All-Google-OS.

Enjoy!

So for decades we had 3.5mm (⅛″) and 6,3mm (1/4″) headphone jacks on nearly any audio equipment. From the Revox A77 all the way down to the Sony Walkman and Apple iPhone. Nowadays they often carry a fourth ring, usually for the microphone for handsfree use on cell phones.

In the second week with the Nokia Booklet I thought to finally checkout the audio quality. Well, what should I say, I nearly fall off my office chair when I plugged in my V-Mode Vibe Duo headphone ( I got for use with the iPhone). It sounded like good old PC speakers (well beeper) plugged into a coke can. Awful, at best. Still shocked, I plugged in the standard headphone that came with the Palm Pré, which was not a bit better, rather worse.

Puzzled if it should be possible to mangle a DA convert’s output lines that badly, I grabbed the box, in which Nokia shipped the Booklet, from the shelf to give the Nokia headphones, which came with the Booklet, a try. All to my surprise they sounded somewhat better. Still sub-standard, but at least not like a PC beeper thrown into a tin.

I quickly checked the headphones in front of me:

• the iPhone’s work in the iPhone (obviously), the Pré, a MacBook, but not in the Booklet
• the Pré’s work in the iPhone, Pré, MacBook and neither in the Nokia Booklet
• the Booklet’s only have reasonable sound quality in the Booklet itself, in the iPhone, Pré or a standard outputs, such as the MacBook, they sounds awful
• at least a regular Sennheiser (without microphone ring) worked in all devices, puh

I get the feeling Nokia uses a different signal combination. One could have thought the vendors would be smart enough to all use the same, … Well, I guess they where smart enough to all use their own variant, sell matching accessories.

At least Apple and Palm where smart enough to make their variants work with good old standard devices, while Nokia somehow managed to make them incompatible with probably all the last decades audio equipment, …

This morning’s newspaper, Norah Jones commented here previous style, new album: my style was really boring (German: Mein Stil hat mich total gelangweilt.).

Yeah Norah, I couldn’t agree more. Hope your new CD digital-bitstream is better. Much luck and all the best.

Update: Ok, a little progress, a little better: listen yourself.

Mac OS 10.6.2 update just trickled in, complained I did not had 2,95 GB of free disk space (a little less when Safari 4.0.4 is deselected):

Ok, admitted, I had multiple GBs of test scanned image data lingering all over the place. But 157,7MB becoming over 2GB? Ok, maybe some snapshotting and backup involved, but they could certainly patch on-the-fly a little more efficient.

Remember: Intel Atom CPU support might be degraded (#ifdef’ed out). I only updated genuine Apple Mac’s, the above was my MacBookPro3,1.

So recently I mangled my PowerPC G5’s Apple partition map while installing Mac OS X on my Nokia Booklet 3G. Yeah, all this zero-based, one-based, everyone names them different device enumeration, …

So after the Chameleon Master Boot Record hit the Apple Partition Map of the G5, OpenFirmware was not able to read the remaining partition table anymore (I actually should lookup the layout, maybe just some magic was hit, or a backup copy resists somewhere, whatever).

So after about a week without the G5 I thought it would be a good day to install all the OS X flavors, which I need for testing, alongside my Linux, again.

Loading the T2 installable disk, Linux did neither recognize a valid partition table, anymore - however mac-disk still displayed all the 8 partitions just fine. It just wouldn’t save it without changes (at least I found no “forced write, really I mean it, yes I know I have not modified it” switch). So the last partition removed, re-added, re-written (yuck), and all was there again. Yay!

This year we have quite some celebrations in Germany: 20 years since the fall of the Berlin wall, and 60 years Federal Republic of Germany. Next year follows 20 years of German reunification.

As follow up to one of the celebration events today, an art project made a Berlin Wall from giant dominos. The domino wall will be toppled this evening.

… more in the whole gallery

According to an O2 employee I just spoke to (regarding my memory glitching device) the Nokia Booklet 3G is already on the list of soon to be End-Of-Life’d devices? Given that it just went on sale just slightly more than a week ago this makes a pretty short lifespan. Even for cellphone standards, … I wonder if there is more behind this, such as a batch of faulty memory chips, PCBs, high return rate in general?

My last days experience with the Nokia Booklet 3G were not too superb, the Google memory stress tester spotted some miscompares:

Hardware Error: miscompare on CPU 1(0×2) at 0×5bd98480(0×0:DIMM Unknown): read:0×0000000004000000, reread:0×0000000004000000 expected:0×0400000004000000
Hardware Error: miscompare on CPU 1(0×2) at 0×49363240(0×0:DIMM Unknown): read:0×0000000004000000, reread:0×0000000004000000 expected:0×0400000004000000
…

Could explain some things.

Question is who’s to blame? Memory, Chipset, CPU, OS?

Given this, and Google’s latest paper on memory errors I consider making an stressapptest run part of my standard system installation procedure, …

Update: With the same binary, (Linux) kernel and (Google) test-application, from the same USB stick the Google memory tester does not find an issue with any other machine int the office, from other Atom 330, over VIA C7, Intel Core 2 Duo, to 8-way Xeons. I even just walked over the the Sony Style Store in Berlin, checked a Sony Vaio VGN-X with 1.86GHz Z-series Atom - which did not report a glitch in some minutes of testing, either. So the “generic” Intel Poulsbo chipset option becomes less likely (well, you’d never know, I just say Intel F00F, FDIV bug).

While we are at it: The Nokia support is a huge joke, they claim no warranty if the OS was formatted, e.g. the Win 7 Starter updaeted, manually installed, even just Win 7 Home Premium / Professional, whatever. Forget about Linux. They stress not to remove the “hidden” recovery partition. I just had the worst support call, ever!

Update 2: The same happens on an US (mine is DE) Booklet in a Best Buy store over in the US. So it’s certainly not a single incident. However, given other server hardware shows the same in the google stresstest application list I have hope this is a bug in the tester :-)