There are a lot of n900 reviews online talking about specifications of the hardware/software and how all of the applications work to the nth degree of detail. My post is from using the n900 as my main device for a period of 4 weeks (the length of time will become significant later).
Before Christmas 2009, after much deliberation I decided to purchase an N900. The phone was bought through a reseller where the price was competitive with what they where being sold for on eBay. When the phone arrived I promptly unpacked it and charged it up but within 1 hour of use it rebooted. I over looked this and promptly set about configuring the exchange sync, my email accounts and looking at what applications were available. I used various sources from NokiaAddict.com to allow me to access all of the development and testing resources and twitter for recommendations which gave me access to more applications. Previously being an N810 user I was aware of the issues around using test applications and that you might cause the device to become unstable, but I didn't care. For my N810 I have completely repartitioned the internal disk to increase the available installation space which has lead to the device being more usable. Considering I usually push things to the limit the enabling of these repositories was just another "walk in the park" for me.
Over the first few days I began experiencing several reboots a day which initially because the device was new I wasn't worried about but it got the point of becoming annoying. Doing investigations through searching on the web and posting to twitter wasn't really conclusive as there were two camps. People who were returning their n900s for replacements as they believed it was a hardware fault. This went to the extent of people commenting on how long they charged the battery from when the device was first switched on to discussions of battery replacements, battery charging voltages, what types of chargers were being used, the variety and quality of components inside the n900 and even people suggesting it was applications from the testing repositories. Other people were suggesting it was something to do with the device being in the middle of a process and trying to go into idle mode where it would force it to reboot.
The error I was getting of which could be displayed in a command prompt using "cat /proc/bootreason" was wd32_to.
Through following the link I was able to disable enable_off_mode which whilst reduced the battery life as power management had effectively been switched off it made the reboots from 8 a day to 0.
After 12 hours use I also came across another issue related to the reboot count where each time the device reboots due to the above it adds a value of 3 onto the reboot count. When the reboot counts goes over 50 and the phone reboots it will not load the OS, merely sitting at "2nd dot " of the "5 dots". Effectively the n900 was bricked where I had to reload the firmware to restore it. Again there was a fix for the reboot count. Recently I have managed to brick the device again but used this link to resurrect the device without the need for a reflash.
So whilst all of this was happening up until the first week of January 2010 through trying to use the device daily, I had come to the decision that should a fix not be released shortly then the device would be on EBay.
On January 12, a small fix was released that essentially allow the larger update to be done over the air when this would be released. Sadly, this fix didn't resolve the reboot issues and I had to resort to the workarounds mentioned above. Again, I was of the same opinion if no reboot fix was to be issued then the device was bound for EBay. It was fun trying to get this firmware on due to the fact I had filled the root filesystem so had to remove applications to make space in order to load the new firmware on.
PR1.1 firmware was released on 14 January, again this would not go on so was forced to take a backup, reflash using a cable and restore from backup. Firstly, the backup/restore was flawless in that it both restored all of my data and reinstalled my applications - although it had to download these again. This was nice to see bearing in mind I had seen some concoctions over the years claiming to me mobile backup solutions but wasn't any good. I had to laugh about the application reinstall because to my horror it needed to download 670mb of data so there is no wonder I filled up the root filesystem. The other advantage was any garbage that had been installed previously had been removed and my root filesystem is now back to a reasonable size although I do question the partitioning considering there is over 32gb on board and to only use a minimal amount for rootfs is ridiculous. In the forums it has been said my rootfs has gone due to me installing test applications of which are not installing to the correct partitions but this is just an excuse. Should someone repartition the n900 and provide instructions in a similar vain to my n810 then I will do this.
Now to the question did it fixed the reboots?
After reading up on the issues around the reboots I came to the conclusion it looked like a software bug as the workaround was to disable power managment. I also had assumed that this could be fixed through software. My conclusions were correct, the device since the firmware updates is getting zero reboots to the extent I was proud to publish an up time of over 24 hours on my twitter.
Daily I am enjoying using the n900 for Internet web browsing, Instant Messaging, Twitter. Email - in fact everything it was intended to be used for. The keyboard and form factor are great and as a two handed device it really works for me especially considering I am a fan of the Nokia Communicators. It could be used in portrait mode and there is movement to make more applications and the OS to work in this form factor but I am not convinced. Other than the phone application I see no need for this feature as it is just as easy to pull out the keyboard and work in landscape.
The main issue with the n900 is lack applications even though the device is new. Whilst there is a back catalog of Maemo 4 applications these all need porting. Because the web browser is full featured you can use this instead of applications for example you can use Google Docs, Google Maps, Twitter and edit your blogs without the need for dedicated applications. But because the browser can be resourceful having several windows of web open can slow the device down and ultimately when web crashes it closes all of the windows. Whilst the screen resolution is wide enough for browsing again everything within an application can seem cramped so you either have to zoom in/out. But until applications are released you have an alternative available.
After spending over two years gradually converting form windows to Linux through having to find alternative solutions to things that I naturally accept within windows I can be patient with the n900. Through this approach should I not be able to find an application I know there will always be an online alternative that I can use within the web browser. On this basis, I am keen to tell people who are looking at the n900, that should they accept this shortcoming, realise the device is a work in progress still then they will enjoy using the n900. If they are looking for something to work out of the box and do everything an iPhone currently does then n900 isn't for them. Whereas if you are looking for a device that has the potential to do everything an iPhone can and are prepared to wait then the n900 is for you.
I have found that you begin using the n900 for example Twitter, I can tweet, post pictures, post vide, post audio and complete searches but I am using a combination of the built in conversation/IM app, a python application called Witter, another application called MAKU and the web browser. Not exactly seamless but working. So you can begin doing something on the n900 but suddenly find you cannot complete because there is some missing functionality in your current approach so you have to find a workaround.
Another example of this is the OVI Maps solution. This isn't a satellite or personal navigation application on the n900 as it is on other symbian solutions. Currently there is no other navigation application available, however Sygic are making an application to fulfill this void. Hopefully this will be released soon. Google maps can be used with real time GPS navigation using this guide where I had to use this yesterday because OVI Maps was completely useless. Again, in time this will change.
There is an argument that the n900 is not a phone it is an Internet tablet. I have avoided using the reference to phone within this post as I believe it is a new breed of device. The n900 being one of the first devices with this blend of phone, Mobile Internet Device, Navigation Device with a high specification that can genuinely multitask has the opportunity to set the bar from which other devices will be judged. It can be compared and will be compared to the IPhone but they are aimed at two different markets. The n900 can hold its own without connection to a PC whilst the IPhone needs Itunes to benefit using all of its features. For example, I can take 350mb encoded divx file, put it on the n900 and it plays whereas the IPhone needs conversion to be done. Being niche is where the n900 might not be as successful because people want simplicity where lack of functionality and customisabiilty can occur. Most people want to be told what they can do within an application for example, send as an email or mms, whereas the n900 offers more choice share over bluetooth and share via a pipe where they can be extended without having to wait for the manufacturer to build in the functionality. Therefore the N900 has the opportunity to set the bar for this breed of device it also at the very beginning of a new open culture for Mobile Technology which needs to be embraced or it will fail. Android, Windows mobile and Symbian are very similar in that they can potentially and already do everything the n900 does but if you use the n900, look at the possibility that device can be a fully functional computer in your hand and wait (the key factor) here for the applications to be developed then you will recognise the potential and how far beyond the other mobile OSes this
can take you.
However, remember this is the future and not now.
Before Christmas 2009, after much deliberation I decided to purchase an N900. The phone was bought through a reseller where the price was competitive with what they where being sold for on eBay. When the phone arrived I promptly unpacked it and charged it up but within 1 hour of use it rebooted. I over looked this and promptly set about configuring the exchange sync, my email accounts and looking at what applications were available. I used various sources from NokiaAddict.com to allow me to access all of the development and testing resources and twitter for recommendations which gave me access to more applications. Previously being an N810 user I was aware of the issues around using test applications and that you might cause the device to become unstable, but I didn't care. For my N810 I have completely repartitioned the internal disk to increase the available installation space which has lead to the device being more usable. Considering I usually push things to the limit the enabling of these repositories was just another "walk in the park" for me.
Over the first few days I began experiencing several reboots a day which initially because the device was new I wasn't worried about but it got the point of becoming annoying. Doing investigations through searching on the web and posting to twitter wasn't really conclusive as there were two camps. People who were returning their n900s for replacements as they believed it was a hardware fault. This went to the extent of people commenting on how long they charged the battery from when the device was first switched on to discussions of battery replacements, battery charging voltages, what types of chargers were being used, the variety and quality of components inside the n900 and even people suggesting it was applications from the testing repositories. Other people were suggesting it was something to do with the device being in the middle of a process and trying to go into idle mode where it would force it to reboot.
The error I was getting of which could be displayed in a command prompt using "cat /proc/bootreason" was wd32_to.
Through following the link I was able to disable enable_off_mode which whilst reduced the battery life as power management had effectively been switched off it made the reboots from 8 a day to 0.
After 12 hours use I also came across another issue related to the reboot count where each time the device reboots due to the above it adds a value of 3 onto the reboot count. When the reboot counts goes over 50 and the phone reboots it will not load the OS, merely sitting at "2nd dot " of the "5 dots". Effectively the n900 was bricked where I had to reload the firmware to restore it. Again there was a fix for the reboot count. Recently I have managed to brick the device again but used this link to resurrect the device without the need for a reflash.
So whilst all of this was happening up until the first week of January 2010 through trying to use the device daily, I had come to the decision that should a fix not be released shortly then the device would be on EBay.
On January 12, a small fix was released that essentially allow the larger update to be done over the air when this would be released. Sadly, this fix didn't resolve the reboot issues and I had to resort to the workarounds mentioned above. Again, I was of the same opinion if no reboot fix was to be issued then the device was bound for EBay. It was fun trying to get this firmware on due to the fact I had filled the root filesystem so had to remove applications to make space in order to load the new firmware on.
PR1.1 firmware was released on 14 January, again this would not go on so was forced to take a backup, reflash using a cable and restore from backup. Firstly, the backup/restore was flawless in that it both restored all of my data and reinstalled my applications - although it had to download these again. This was nice to see bearing in mind I had seen some concoctions over the years claiming to me mobile backup solutions but wasn't any good. I had to laugh about the application reinstall because to my horror it needed to download 670mb of data so there is no wonder I filled up the root filesystem. The other advantage was any garbage that had been installed previously had been removed and my root filesystem is now back to a reasonable size although I do question the partitioning considering there is over 32gb on board and to only use a minimal amount for rootfs is ridiculous. In the forums it has been said my rootfs has gone due to me installing test applications of which are not installing to the correct partitions but this is just an excuse. Should someone repartition the n900 and provide instructions in a similar vain to my n810 then I will do this.
Now to the question did it fixed the reboots?
After reading up on the issues around the reboots I came to the conclusion it looked like a software bug as the workaround was to disable power managment. I also had assumed that this could be fixed through software. My conclusions were correct, the device since the firmware updates is getting zero reboots to the extent I was proud to publish an up time of over 24 hours on my twitter.
Daily I am enjoying using the n900 for Internet web browsing, Instant Messaging, Twitter. Email - in fact everything it was intended to be used for. The keyboard and form factor are great and as a two handed device it really works for me especially considering I am a fan of the Nokia Communicators. It could be used in portrait mode and there is movement to make more applications and the OS to work in this form factor but I am not convinced. Other than the phone application I see no need for this feature as it is just as easy to pull out the keyboard and work in landscape.
The main issue with the n900 is lack applications even though the device is new. Whilst there is a back catalog of Maemo 4 applications these all need porting. Because the web browser is full featured you can use this instead of applications for example you can use Google Docs, Google Maps, Twitter and edit your blogs without the need for dedicated applications. But because the browser can be resourceful having several windows of web open can slow the device down and ultimately when web crashes it closes all of the windows. Whilst the screen resolution is wide enough for browsing again everything within an application can seem cramped so you either have to zoom in/out. But until applications are released you have an alternative available.
After spending over two years gradually converting form windows to Linux through having to find alternative solutions to things that I naturally accept within windows I can be patient with the n900. Through this approach should I not be able to find an application I know there will always be an online alternative that I can use within the web browser. On this basis, I am keen to tell people who are looking at the n900, that should they accept this shortcoming, realise the device is a work in progress still then they will enjoy using the n900. If they are looking for something to work out of the box and do everything an iPhone currently does then n900 isn't for them. Whereas if you are looking for a device that has the potential to do everything an iPhone can and are prepared to wait then the n900 is for you.
I have found that you begin using the n900 for example Twitter, I can tweet, post pictures, post vide, post audio and complete searches but I am using a combination of the built in conversation/IM app, a python application called Witter, another application called MAKU and the web browser. Not exactly seamless but working. So you can begin doing something on the n900 but suddenly find you cannot complete because there is some missing functionality in your current approach so you have to find a workaround.
Another example of this is the OVI Maps solution. This isn't a satellite or personal navigation application on the n900 as it is on other symbian solutions. Currently there is no other navigation application available, however Sygic are making an application to fulfill this void. Hopefully this will be released soon. Google maps can be used with real time GPS navigation using this guide where I had to use this yesterday because OVI Maps was completely useless. Again, in time this will change.
There is an argument that the n900 is not a phone it is an Internet tablet. I have avoided using the reference to phone within this post as I believe it is a new breed of device. The n900 being one of the first devices with this blend of phone, Mobile Internet Device, Navigation Device with a high specification that can genuinely multitask has the opportunity to set the bar from which other devices will be judged. It can be compared and will be compared to the IPhone but they are aimed at two different markets. The n900 can hold its own without connection to a PC whilst the IPhone needs Itunes to benefit using all of its features. For example, I can take 350mb encoded divx file, put it on the n900 and it plays whereas the IPhone needs conversion to be done. Being niche is where the n900 might not be as successful because people want simplicity where lack of functionality and customisabiilty can occur. Most people want to be told what they can do within an application for example, send as an email or mms, whereas the n900 offers more choice share over bluetooth and share via a pipe where they can be extended without having to wait for the manufacturer to build in the functionality. Therefore the N900 has the opportunity to set the bar for this breed of device it also at the very beginning of a new open culture for Mobile Technology which needs to be embraced or it will fail. Android, Windows mobile and Symbian are very similar in that they can potentially and already do everything the n900 does but if you use the n900, look at the possibility that device can be a fully functional computer in your hand and wait (the key factor) here for the applications to be developed then you will recognise the potential and how far beyond the other mobile OSes this
can take you.
However, remember this is the future and not now.
Comments
Post a Comment