E75 owners may wish to avert their eyes as their phone becomes disassembled in this instructional video.
It can help if you’re into DIY fascia/cover changing.
I tried this a while back with my N82 and kinda broke the microphone (had to send off for repair). so be careful when taking anything on like this. Most likely it will VOID your warranty.
From NokiaPort, a supposed Nokia C3, the newest family member to Nokia’s Cseries Range. No actual details.
It slightly resembles the also rumoured E73/Nokia Mystique (though proportions are different – C3 more curved, smaller camera). Proportion wise C3 could have a QWERTY keyboard and not the usual alphanumeric T9 keyboard.
The Much awaited MeeGo seems to be available for the Nokia N900 (and Atom/Moorestown based devices).
Today is the culmination of a huge effort by the worldwide Nokia and Intel teams to share the MeeGo operating system code with the open source community. This is the latest step in the full merger of Maemo and Moblin, and we are happy to open the repositories and move the ongoing development work into the open – as we set out to do from the beginning.
What are we opening? The MeeGo distribution infrastructure and the operating system base from the Linux kernel to the OS infrastructure up to the middleware layer. The MeeGo architecture is based on a common core across the different usage models, such as netbooks, handheld, in-vehicle, and connected TV. The MeeGo common core includes the various key subsystems including the core operating system libraries, the comms and telephony services, internet and social networking services, visual services, media services, data management, device services, and personal services. More on this will be described on meego.com over the next few days.
The downloaded images will boot from a USB stick or directly flashed on the device from your Linux PC, but since the MeeGo User Experiences for the usage models mentioned previously are not yet included in today’s MeeGo core, these images will boot into terminal.
After Day 1, the rest will follow soon – in the next few days, we will post the next steps leading to the first release of MeeGo in May.
NOTE: You will need some considerable expertise to carry out installation it’s extremely likely you will BREAK your N900 otherwise. Do this at your own risk.
Update: From Maemo.org:
it has no gui and is command only like xterm hence why it is for devolopers and not end users
please dont expect a finished fancy ui as it isnt there from what ive read
Is this a sign that N900 should get official MeeGo support?
If you aren’t a risk taker, there’s the official PR 1.2 firmware that’s coming real soon that’s gonna refresh the N900 up a bit.
According to Jussi
“…PR1.2 to my N900 and gotta say the computer feels again like new…make sure to update it when it comes”
So. Where to Get MeeGo?
MeeGo Repositories and Images
The available MeeGo repositories now include the operating system base from the Linux kernel to the OS infrastructure up to the middleware layer. The downloadable images available now will boot from a CD or from a USB stick, but since the MeeGo User Experiences for the usage models are not yet included in today’s MeeGo core, these images will boot into terminal.
Maemo Arena have instructions should you want to try MeeGo on your N900.
Here’s a pretty cool find, an app built by iPhone blogger and coder Melfar (Vsevolod Buzinov) with Qt. Audelicious: Music Appreciation app.
I’m not sure if they are visualizations for music being played through the music player though that’s what I’m assuming.
You’ve got a couple of spectrum analyzers and an amplitude meter. All three can be viewed simultaneously as well as possibly sensitivity, range and colour settings. Each can then go into full screen mode.
Here’s a Vimeo version:
(on your desktop:)
wget http://www.fftw.org/fftw-3.2.2.tar.gz tar xzf fftw-3.2.2.tar.gz && cd fftw-3.2.2
(in scratchbox dev environment:)
./configure --prefix=/usr make && make install
- You need Qt 4.6 installed in scratchbox to proceed.
qmake && make
AudeliciousQTfile to the device, make sure you have Qt 4.6 installed on the device. If you have both 4.5 and 4.6, move 4.5 away from
/usr/libto a temporary directory and set env
LD_LIBRARY_PATHto qt4.6 directory. NOTE: you won’t need to worry about it on PR 1.2 🙂
./AudeliciousQTfrom the terminal or install
.desktopfile to application manager. Enjoy!
Nokia seem to keep on rolling out the updates and the latest one is Ovi Contacts which has now gone to 1.5 for S60 5th edition (Touch) devices.
The 2 main updates which were driven from requests from users are:
- Pop-up note for incoming chat messages
- Additional file types for file sharing: contact card & presentation
Head over to Nokia Beta Labs to get the latest update: http://betalabs.nokia.com/apps/ovi-contacts
(You need to be signed in to download)
Yesterday the guys over at Ovi blog announced an updated version of the Ovi store which is available to download now which takes it from version 1.05(611) to 1.06(18) on my X6 and I would assume it would be the same on other handsets.
The 4 main changes are:
- Make it easier to browse, search and discover content
- Improve the quality of content reviews (eg: change from 3 to 5 star rating system)
- Provide more product information to help you decide what to buy
- Improvements to the desktop version of the store
You will have noticed that the annoying scroll wheel for selecting your device has gone and an easy to use selection tool (took me a second to figure out where the option was, and it’s at the top right next to the language option)
Nokia seem to be rolling out these updates every month and if they keep it up, hopefully they can truly turn this good store into a great one, only a few more steps I think remain!
An intense discussion on the topic is occured over at twitter this Sunday Evening, 28th March 2010. I don’t know if this will make any sense, I am extremely tired and over simplifying certain issues which have many more facets.
It’s a frequent debate that comes near supposed product launches. Topic: Product leaks.
- For a more in depth post on product leaks, this one from Nokia conversations, back in 08 is a really good read.
- MickyFin also has an excellent blog post about it (and really good discussion) but my googlefu can’t find the link. Will update.
They’re exciting on many levels. For geeks who want to know the latest tech, for journalists who need something hot to publish and for cutting edge consumers who need to know about future devices to guide their product purchases. Product leaks can be great if the product receives rave reviews. It gets people hyped up and excited. Good for the reputation of the company. It’s even more exciting when it’s you delivering the news first.
On the flip side, leaks can be damaging. An incomplete product can be harshly reviewed and damage the products reputation. Hype also needs to be built up. Trickling information, especially a review, destroys uncertainty and excitement at product launch because you know everything about the device. There is no simultaneous reaction. For the workers of new devices, it’s very discouraging when something you’ve been working on for maybe a year in secret is just blurted out.
To leak or not to leak – that is the question:
It’s very interesting to see that there are popular blogs/news sites out there choose NOT to jump on leak stories and let them pass by, despite the obvious positive effect it may have on their traffic. Some explicitly choose not to publish those type of stories, whether out of respect to the manufacturer/relationships with that manufacturer or perhaps confidentiality agreements.
For me, I have my own reasons for what I do and don’t post. Mainly if I find a story/item interesting enough, I post it. If I don’t, I don’t care even if everyone’s talking about it. Not really an ideal journalistic attitude eh? haha. Also I try not to post things that you might have read about a million times already in other blogs, unless I find it really interesting and have an opinion to add to the discussion. It is after all, a very informal, just a hobby type blog.
A side topic to debate is whether or not product leaks are intentional and staged (why would said manufacturer send out products to people who leak info if you want to keep it secrets) or whether it’s an unfortunate and ghastly security blunder (the latter is extremely frightening).
What solutions could there be to reducing leaks? At least in the case of the legend that is Eldar, if the leaks are unintended by Nokia, my naive* mind wants to suggest that perhaps Nokia get in touch with him first, get devices out to him and let him sign confidentiality documents so he can’t discuss things with the public. That’s if Eldar would agree to such things and if Nokia wants his feedback.
This isn’t the full discussion. There are way more pros and way more cons to discuss, but this post will get even longer than it already is.
*As with most things, the more you learn about something, the more you learn that there’s so much more that is unknown. That’s the case here with Nokia. From speaking with Nokia reps, I’m getting the gist that in Nokia, there’s a reason for everything. Seemingly stupid decisions, only appear stupid if lacking the full story. At Nokia, there’s a secret story of a whole bigger picture where when you know it, everything makes sense.
Having such a narrow, pinhole view of Nokia, I only have an incomplete picture and can’t really accurately respond. Thus, without the bigger picture I may often rant about either irrelevant things, or issues Nokia are already deeply aware of.
There is always a chance that Nokia genuinely aren’t aware of certain issues and in that sense, I think it’ll always be good to criticize. Plus, Nokia discussions are always quite fun.