Tag Archive: N900


N900 – No sound after boot

Hi!

Just wanted to save this information somewhere in the hope of it being useful to someone sometime 😛

If you have no sound after boot and increasing volume doesn’t work it is likely pulseaudio failed to start. Some minutes after boot it is possible to start pulseaudio via terminal (as root) (

start pulseaudio

) but if you forget you end up with no sound which is I’d say pretty bad for a phone… -.-

So what do you have to do?

Execute this command as root:

cp /opt/maemo/usr/lib/libFLAC.so.8.2.0 /usr/lib/libFLAC.so.8.2.0

What causes the problem seems to be that pulseaudio wants to start when /opt is not mounted yet and libFLAC seems to have been (accidently) moved to /opt when it should have stayed out…

I do not guarantee it works but at least for me (and some guys on tmo) it worked 🙂

After some googling I found the solution here (no it is not from me)

Hope this helps you 🙂

Advertisements

In case you are not an active reader of talk.maemo.org I have something very interesting for you.

You already read the title of this post (or you probably wouldn’t have read the post) so you probably… maaaybe are already going to know what I’m writing about.

THIS – will hopefully grow into a full blown navigation solution. They are working on POI showing/hiding (including different categories), voice navigation with nokia provided speech files and automatic language detection – as well as reading out street names using espeak or other solutions. And what is also on their TODO is offline routing support =)

Sounds great doesn’t it? 🙂 The project is still pretty early – and I don’t think it will help OVI maps get faster on N900 but it for sure will help boost its features =) For those not knowing: OVI Maps is based on HTML/JS! So they are just editing one single index.html which originally was about 800KB and is now already up at 1.2MB.

Tracking the GPS position and automatically following the map already works but I couldn’t get speech to work. Also it has problems with loosing GPS connectivity (e.g. in tunnels) or if you choose another route (no automatic route recalculation yet).

Still it is REALLY great someone is working on this 🙂 On the other hand it is really sad that some volunteers who are not even programmers succeed at something Nokia failed to do for quite some time…. I hate business…

To end this post with something nice… here a screenshot 🙂 (yeah I know those were rare lately on my blog)…

Yeah I know this isn’t a picture of my (at least I didn’t know I live in taiwan…) – but taking a picture while driving may not be the brightest idea… 😉

How to install (as of 23.1.2011)

N900 Maemo 5 – PR 1.3 available

PR 1.3 is available since yesterday. See for example this post for more details. For a list of bugfixes see this one. Not that long/impressive – but we take what we get 🙂

What else does it contain? Updated Qt, Qt-mobility… though I can not yet confirm that dualbooting Meego has become easier… we’ll see…

For the moment I’m busy reinstalling/reconfiguring all my programs as I had to do a update via Nokia PC Suite which erased all my programs (as I had not enough space on root…)

Stay tuned for updates on how to boot Meego using PR 1.3.

PS: no OVI maps hasn’t received any visible updates =(

PPS: PR 1.3 now supports syncing with OVI Suite (not tested yet)

 

 

 

 

As mentioned in my last blog entry about Dinjam I’m in the progress of separating the core stuff of Dinjam into a library (libdinjam) and creating Uis for different scenarios (like mobile usage).

There are 4 different uis in the works – even though I’m not sure all of them will ever be finished (more about that later).

1.) Desktop (QWidget based)

This is the traditional Ui as it has always been with the Ui designed using Qt Designer and the QGraphicsScene created from within the scripts.


Atm Scripts are broken in the sense of that there are no C++ exports of for example documentmanagement. (and there are some other broken pieces everywhere)

2.) Meego Touch Framework (MTF) (QGraphicsView based)

A new ui based on the MTF developed by Nokia/Intel for Meego. Atm I’m trying to setup a devel environment but it is not as easy as I had hoped – I’m trying the qemugl approach from the wiki – but the image won’t boot using kvm (just stops at loading the kernel) and without it starts X and then stops (no handset UX shows up). How to get network up and running can be found here.

After packaging libmeegotouch and meegotouchtheme for ArchLinux I can now sort of execute/link/use meego applications although there is some really weird gconf stuff going on and I’m not sure if my system is correctly set up now. Maybe I’ve got to set up a Fedora VM or something similar. Or just wait for PR 1.3 of Maemo to easily dualboot Meego natively on my N900 to execute directly on my N900.


Basically everything here are placeholders – as I just recently found out that meego applications run at all (before I had a white square and nothing else appearing).

3.) QML Ui (QDeclarativeView based)

QML or “Qt Quick” how the cool guys at Nokia are calling it seems to be the future Nokia envisions for app development. Combined with their ongoing lab project QSceneGraph which should bring enormous performance gains as all painting will shift from QPainter to OpenGL/on GPU based painting, this may really be the future – at least in the long run. I must admit that the whole affair is really new stuff to me so I’m having a pretty hard time figuring out how to transform a traditional ui into a QML based version.

I’m currently trying basic things like navigating between a basic menu to another page showing an about dialog – and I want to make that happen using a nice transition – and not showing/hiding elements but instead loading them as I need them (to save ressources). Sadly I wasn’t able to find any QML application out there using such an approach… I’m looking for the pages concept of MTF I think…

Anyway… here’s my first try…


So what works? The quit button – and About switches to another page – but atm without a nice sliding transition effect and using show/hide of the different rectangles… not nice imho.

4.) Qt Components (QML based)

The last frontend Dinjam may provide in the future is the Qt Components based one – although atm there isn’t much progress as Qt Components itself are not really anywhere atm. Afaik there exists some sort of a Meego “style” atm and an incomplete MX “style”, with a plasma (KDE) “style” in the working (see this post on plasma-devel mailing list) but there is not really anything useable atm I could plug into. At least to my knowledge.

So no screenshot for that one 😦

TODO

So what is still left to do? A LOT! It starts out with library recompiles as soon as I switch platform (3 object files want to relink again), cmake fixes to incorporate the possibility to build not only one but many/all platforms at once. And of course: finish those uis.

I think the best step would be to first get the desktop ui working again and then slowly start creating the others. It remains to be seen how to integrate a QGraphicsScene/View with MTF/QML. Interesting times ahead… that’s for sure.

Stay tuned for more updates. I hope I won’t disappoint you

To end this post: Orbit/Directui anyone? 😛 anyone strange enough to create a KDE ui? 😛

Hi!

Again no updates for quite some time… sry… just a short one this time again…

PR 1.3 for N900 is finally coming =) and according to Nokia staff not too far away 🙂

Also Meego on N900 is progressing quite nicely even though it won’t be really useable with its 1.1 release at the end of October…

You can read more about it here (and the pages which are linked on it)

Cya next time