bradb: the "musgo" phantom network was from some of the multiplayer games (Doom, Battlegweled etc.) - since these haven't yet been ported (AFAIK), you won't get the phantom network back until you run them.
I really have to say even if this beta is really "beta" the enhancments and addons, usability features are great.
For me the nokia was never really stable, opera went away sometimes mail openend or didn't depending on the weather and the angle i hold the tablet
So the Password saving and url completion get a big plus
also that possibility to arrange columns is great.
Goggle talk hmmmm google talk, i tried it it works really fine, the soundquality is ok on both sides and also the instant messaging works BUT
how many people do you know who use googletalk???
there isnt even a VoIp client fpr GoogleTalk available for linux.
So this is alittle problem for me, because i have a big skype buddylist but goggletalk seems for me being a hermit.
Probably there is a posibility to get the static skype package with qt compiled in running?? anyone tried, i cant at the moment becaus of missing xterm in the 2006 os
I can confirm, re-flashing back to the previous version with flasher-2.0 in Linux works. See http://maemo.org/maemowiki/HOWTO_Fla...ImageWithLinux for details. The only step left out from the instructions is to make flasher-2.0 executable by chmod a+x flasher-2.0 before running it.
Only reason for flashing back is that I've just got my windscreen mount and I want to try out Maemo-mapper.
** Screen problem **
Updated to 2006 beta OS last night. Went through the wizards to make a phone and WAN connection. I was enjoying the experience but got a problem when I restored my backup to access my bookmarks. First thing I noticed was that my connections would not load. The 770 seemed confused between my old and new data. I rebooted and the screen developed a problem: grey vertical bar running through the G of the Google search box and streaking of all images. I tried rebooting, taking out the battery, recharging but no effect on the screen problem. I then tried to reflash the device, but the Windows update wizard stops after 10% and throws up a Code 3 error, invalid image. Anyone experienced this or any advice on what to do next? Thanks for your help.
Bom
You'll get no sympathy here. The rocket surgeons round these parts seem to think it's OK for a label 'beta' on a piece of software to mean you can't remove it. Me, I thought the non-beta flasing software should still be able to flash in the non-beta image and that only the software in question -- the new image -- was 'beta'.
i love it 