Re: Cant update to latest firmware
 

Re: Maemo 5 PR1.1 released today (January 14)
 

The 44 update is required before you can install the 51 update OTA.

Re: Maemo 5 PR1.1 released today (January 14)
 

ahh damn!! i tried installing that last time via the NSU and it crashed at 1 sec left! so i reflashed back to 42 the way it was.

Hmm....i guess ill wipe the emc then try it again via NSU

Re: Maemo 5 PR1.1 released today (January 14)
 

Hello, please seeking you advice here, as I really can't send any SMS since I had my last update.. anyone has the same issue?
How can this be solved? I restored my system settings, and restored my last backup before this last update.. but nothing happened, i still can't send any sms! it says delivery failed!
I also checked my Center number and it was ok..

Re: Maemo 5 PR1.1 released today (January 14)
 

the flashing info site is down :( so much for that wikki page

Re: I CAN'T update via OTA!!
 

I had the same issues, but did he following

made a backup of everything with the included app to a memory card

uninstalled everything i downloaded from extras and devel

my N900 then allowed the update OTA

I then restored the backup, and a menu appeared in the download manager about restoring applications, I let it do it's thing and everything was downloaded automatically, even my preferences were kept...

Give that a go!!

Re: Maemo 5 PR1.1 released today (January 14)
 

The thread "I CAN'T update via OTA!!" with five posts has been merged into this thread.

Re: Maemo 5 PR1.1 released today (January 14)
 

Hi,

I have installed the new firmware, but I am still not able to check my minutes or usage by using #646#, it says incorrect number?

I was seeing a some website this PR 1.1 has a fix for it, looks like it is not fixed or do i need to do anything to get that done?

Regards,

RR

Re: Maemo 5 PR1.1 released today (January 14)
 

This is still not fixed. PR1.1 has a fix for some of the special codes but not all of them.

Re: Maemo 5 PR1.1 released today (January 14)
 

I really didn't want to use a PC to upgrade, so tried to do my upgrade entirely on the phone. The application manager sat for a moment and then said I needed to plug it in to usb and use the pc... So I tried apt-get dist-upgrade and it claimed I needed 100M. I had 50M on / free.

I moved /var/cache/apt/archive to a symlink to /home/ hoping that the download of the .deb files in to there wouldn't eat as much disk and then when overwriting the apps they were installing over the top of, I'd be good to go. Unfortunately as I watched it run through the upgrade my / quickly started to drop to 0% free, after it got there the used space increased towards the same as the total filesystem size! (Using the 5-10% root only allocation some filesystems have I assume).

I quickly looked for some big wins, like moving /usr/lib/libQt* libs to /home and symlinking back so stuff could still work, also I was confused by my for looped du commands and tried to move python out of the way. I knew about the bind mounted optification of it, I just assumed enough other parts of python were still eating space.

The panicked moves of stuff helped greatly but I did eventually run out of space. I found more space as best I could and reran the dist-upgrade. I had to use dpkg --configure -a and let that complete before it would carry on, but eventually I was able to finish. A reboot command later and crossed-fingers and it did some progress bar firmware flashing thing (I assume the equivalent of running lilo ;)) and it all came up perfectly!

I think I managed it, and in the process had almost cleared all the space it needed to be able to do it entirely on / even if I hadn't symlinked the archive/ directory.

Stuff that broke:

As I'd tried a mv of python2.5 to /home it was slowly wiping stuff and only failing when it realised it couldn't move a mount point that was busy.

This meant python was quite upset, and apt-get was not playing ball at all, crashing out badly. I found that the .postint scripts for the python modules which couldn't be reinstalled or removed, contained a call to update-python-modules -i /path/to/special/package/file. This was failing causing non zero return codes upsetting everything. The files it was pointing at were not there. Removing this test, let me install the modules, which included fixing this very problem. I'm still sure a few python modules need a reinstall but now I've got apt/dpkg happy (apt-get -f install completes cleanly now), I can --reinstall packages as and when I need. I just hope none were core for parts of the phone, and that they were only needed for stuff like mirror*, that I'd installed before. Of course this is a fault of basically typing the equivalent of rm -rf /usr/lib/python* and then expecting stuff to work. Not really PR1.1 related.

*This update almost completely fixed the problem with the front camera, it's still a little bit noisy and poor quality for a 0.3MP cam, but WOW much better than before and pretty much usable IMO for vid.conf calls. Thank you!

Stuff that I realised:

The reason I needed 100M was due to a number of things I had installed which weren't using /home/opt, and it seems that during install, stuff is left by the side of stuff which is live so on the next reboot it can be moved in to place and the old stuff removed. This makes sense for some stuff like libc, but it was a great pain for how much space on / was required.

The biggest offender was the latitude updater with a 20+MB libQtWebKit.so.* in /usr/lib. The next biggest are the offscr- apps which use massive libQt* libs in /usr/lib.

If I'd removed these first then not only would I have had much more space left, but also the number of updates would have decreased so I'd have needed less space altogether.

As far as I can tell, you need 50ish MB on / free and very few / using apps installed. I had enough space but many apps which used / and had updates in the pipeline.

If the install had been staged in parts this would have worked. If offscr had not used libQt, or not needed it in /usr/lib then this would be much better.

So far I'm 98% certain I've not buggered up my phone by kludgingly klunking through the dist-upgrade ;) It all seems fast, smooth and better since the update. I'm pleased. But I do wonder why things like /usr/ aren't mounts in to the block device.