The Xiaomi Redmi Note 4X comes in a variety of versions, either with the Snapdragon 625 or with Helio X20. The latter is a blazing fast CPU that gives a respectable 20-30% more performance. The former instead is a well known 2017 mid-tier CPU performer, more for battery conservation, and adopted by many monster-battery equipped Chinese phones (Oukitel, Ulefone to name a few of the popular ones). The problem is that just a few weeks ago, my wife’s Redmi Note 4 of slightly more than one year-old began to overheat. It was averaging a heat level of 41° Celsius to 43° Celsius. It was like having an oven in the pocket and brought flashes of the infamous exploding Samsung Note 7 into mind!
I tried many things on the phone to find the culprit. First thing to do was to check on the CPU/Battery use under the ‘settings’ and to see what was the main offenders of straining the battery. Surprisingly most are from the Play store and social media apps. Turning syncing for these off was easy and can be done within 5 minutes. The Play store settings are a bit tricky for a complete beginner, but it is within the app itself, not the System’s settings. But it was all to no avail.
Being an avid Android user and advocate for 10 years (yes, I am a HTC Dream first adopter) made me irritated. This should be easy for me to diagnose, but there it is, even in flight mode the battery was at the lowest dipping only to 40 Celsius. I had a serious talk with my wifey: it may be a defective battery, and I fear having the thing explode while in use! This would mean the need to buy a new phone, which is honestly a waste of money at this point. The Helio X20 chip is only SLIGHTLY slower than the newly released Snapdragon 636. And this model has a whopping 4,100 mAh.
The other problem that my wife noted is that the device seem to drain the battery significantly. It should have clicked within me at that point, but I was still thinking it is an app problem. I took the problem online; seeing whether this particular model was prone to battery problems. But I found that overheating phones is actually something that usually is due to poor software optimization (the manufacturer is at fault). However, this is something that is immediately picked up by users within the release quarter of the phone. The Xiaomi Redmi Note 4 was already a year old and there is not much complaint on overheating.
Eventually, I remembered Sherlock Holmes famous adage:
…when you have eliminated the impossible, whatever remains,however improbable, must be the truth…
Since Xiaomi provides excellent updates of phone softwares, it boils down to the hardware itself. Is the battery within the phone spoilt? Or is it the charger itself that is defective. The usual charger was a common Xiaomi wall USB charger. I plugged in the phone to my new Xiaomi 10,000 mAh power bank with fast charging. After charging it to near 100%, I let my wife use it.
Note: never fully charge your battery to 100% if you want to lengthen the battery life on your phone. This is common knowledge that is written and re-posted many times, but ignored by many.
The phone did not overheat. It remained at a steady 35-37° Celsius! In fact, what was amazing is that the battery performance was as it was before – it could easily last a full day of heavy social media use!
Contrary to the long-time Android user, the problem may not be a software issue at all. Sometimes our chargers need to be replaced, especially if sudden undetected surges happened and damages the frail circuitry within it.
What people thought was the Nexus 2 (two) is now announced as the Nexus S. It is a collaboration between Google with Samsung. Full details about the phone can be read from http://www.google.com/nexus/#!/features. Being of a smartphone enthusiast and advocate, I would like to just share a few thoughts on the Google Nexus S and what I think should happen in the industry (and what we can do about it).
Wi-Fi 802.11 n/b/g
Near Field Communication (NFC)
Assisted GPS (A-GPS)
While the inclusion of wifi (N) is expected, especially so late in 2010, it seems that the rest are just the mundane specs from early 2010. Sure the NFC seems like a new technology for the general masses outside of Japan, but according to one, http://www.androidpolice.com/2010/12/07/nfc-in-gingerbread-is-crippled-its-one-way-only-and-not-the-way-we-want/, it is only a one way communication (with no transmitter from the device itself), and that is just bad. It makes the device, a glorified tag/bar-code scanner. Bluetooth 3.0 has been supported in recent high-end smartphones from Samsung, which makes it saddening to note the lack of it here. Galaxy S scores points here over the Nexus S.
4.0″ WVGA (480×800)
Contour Display with curved glass screen
Capacitive touch sensor
Anti-fingerprint display coating
It is understandable that Samsung is still determined to enforce their view that SuperAMOLED is much better than the Retina Display of the iPhone. Granted that is the case, but why then would they put out the PPI as one of its features if it will not match or be anywhere close to the iPhone’s RD PPI score of 330? It would have been a real game changer if Samsung had pulled a higher resolution display, like Sharp’s tablet. It is not something that is unachievable given that they own the manufacturing plants. The contour display is an interesting design; I suspect it provides better viewing angles that normal displays cannot deliver well (plus, it is attractive physically).
Size and weight
63mm x 123.9mm x 10.88mm
Very thin and very light for a 4 inch display phone 🙂 Plus point indeed.
These are the standard for current high end phones, so no complains, just a bit of a yawn, since it does not push any boundaries that already existed. The gaming ‘gyroscope’ of course is imported from the iPhone 4. I wonder whether Google/Samsung is merely being a ‘follower’ in this? They could have incorporated some 3D display or maybe even utilising the front camera for gesturing (ala, mini Kinect), or something. It seems too standard for my liking.
Here is the biggest disappointment; the same processor used by the iPhone (of course the iPhone’s is a modified form, re-modified by A4 in-house) and used by the Galaxy S and Wave. It is fast, but I doubt that it is faster than Texas Instrument’s processor used in the Droid X. An A9 processor would have blown everyone out of the water. My only reason (my assumption) would be the fine tuning of A9 to Android at the moment, which is not completed as yet. We see that problem in some of the released Tegra 2 tablet systems. This would have re-booted the gaming capabilities of Android, and to really ensure that the developer community would be charged up to try new things not only on the iPhone but on Android too. I have not much complain with the internal memory of 16GB, except that many are unhappy due to the problems of flashing (given that Android phones are mostly flashable and flash friendly). I personally think people are making too much of a complaint on something that is not important. How many of us totally use up the 16GB memory besides as a storage tool for our massive digital music library? In fact, the space saved could have been used for something else. Could have. Sigh.
Cameras and multimedia
Back-facing: 5 megapixels (2560×1920)
720 x 480 video resolution
H.264, H.263 MPEG4 video recording
Front-facing: VGA (640×480)
3.5mm, 4-conductor headset jack
(stereo audio plus microphone)
Earpiece and microphone
Droid X’s three microphones was game changing and definitely was intriguing for people to consider the need for good audio quality for calls and video recording. However, Nexus S seems like the standard fare; it gives of the, this is just for developers and not consumer use. An 8 megapixel camera would have been brilliant considering that Samsung’s lenses are some of the best in the industry. It is also telling when the best resolution for the video recording is only 720*480. The front facing is not surprising given that many Samsung Galaxy S models (in Malaysia at least) has the secondary camera.
1500 mAH Lithum Ion
Good size. Wireless charging would be a good addition, considering how often one would charge their smartphones nowadays.
Comments on Other things:
The main emphasis of the Nexus S seems to be this: An average phone that shows what Google’s Android can do with average components. I am sure this will succeed (if indeed this is their emphasis) because the focus is more on Gingerbread (Android 2.3) then on the hardware itself. Which is a real pity since Samsung is a well established company and Google is already getting into the groove of what works and what does not. They should have also focused on the hardware component like how HTC HD2 was the ultimate HTC-Microsoft design which is able to compete with many current generation phones even though it is more than a year old in design. That is what is needed in this industry that is changing TOO rapidly; a product that has a more significant life cycle. The first Nexus was something like this; many still use it and are loyal to it (see XDA forums for most active devices to note this). Instead, we find Android 2.3 fragmented in some ways already; the gaming parts are geared more for the upcoming PSP phone by Sony Ericsson. It would have been nice to see Nexus S incorporate that right out of the box, maybe with some physical buttons for gaming. We can only hope. Every time Android seems to be making headway, iPhone comes out just slightly ahead. Google has the resources, I am sure, it’s more of the risk-taking aspect which they seem not willing to take.
Picture above: Dell’s Stage UI, Sony Ericsson’s Timescape – all are lacking in user customization though it is miles better than iPhone’s offering.
I find that the best thing that Android has to offer for consumers like me is the ability to customize the phone at the software level. Tweaking the user interface at the moment is quite a challenge for the uninitiated. There seems to be many ready 3rd party developers there, but not enough traction to make it more acceptable for even new smartphone users. The age of users being forced to conform to one UI design needs to be thrown away. Personalisation is one of the key things that many power users would definitely want, which new users would be terrified of trying. Something of course cannot change, like for example, the way users select applications (by pressing a button regardless of how the apps are ordered, whether from a drawer or something else). There is much also that can be offered for Tablet design.
I personally find the iPad layout to be limiting and unfriendly (wasting too much space). We have barely scratched what is the best UI and most usable UI for the tablet medium, and so also for the smartphones. I think OS providers should provide means for the users (not just 3rd party developers) to extend their customisations beyond widgets, wallpapers, and see how a person may change their preferences depending on the device type and size. I would be very interested in dabble in this area given time and resources. UI design, speed, efficiency and utility is one of the most unexplored area in the apps development industry. Android, though it is more open than others, still do not grant users that freedom or liberty to the basic user. Let the user decide. Let them explore without fear of harming the experience (cloud syncing could be an option or preview modes or demo modes). This is the way to go in 2011 and 2012, as I foresee it.
It took a long while to get this final part out, but here it is. In this last article, I will try to be succinct in all the areas that were particularly important to me (and thus, to you readers too, I hope). Once again, I would like to thank CSL for loaning me a review unit.
I have had this device for nearly a month, and have put it under many conditions. Before evaluating the whole thing as a package, let’s look at some other important areas not covered before:
(DroidPad 3MP sample shot on the left, compared to HTC Dream 3.15MP sample shot on the right)
There two cameras on the unit. One is a 3.0 MP back facing camera (right smack at the middle) and the other is a lower VGA camera that is front facing. Frankly, the camera is alright. Granted that it is not good enough for you to replace your camera (which device would?), but it does make for some good quick shots. I compared a still photo that I had on a similar subject matter (taking a picture off the desktop screen) made on my old HTC Dream (sporting a similar 3.15MP camera). Even with the .15 camera size difference that should give the Dream an edge, I find that the picture from the DroidPad is still clearer. Maybe it is the algorithm used, but things are sharper on the DroidPad camera. Video is nothing to shout about, with the capability to capture VGA video at a paltry 16 frames per second. Not smooth and I found the audio not syncing correctly to the video by a few miliseconds.
The front facing VGA camera is just that… a VGA camera. It is sufficient for making video calls (if you can find a software that supports it on Android). I tried a few but could not manage to get any to work, except for using the test center modes. In that situation, I found the video quality to be acceptable, though not great (it’s VGA). You can use the front facing camera to record video too. Though it records at VGA quality, yet the fps is quite low, at 8 frames per second. It is not worth using, unless you really have something at the spur of the moment to capture on the front facing side. (A sample of video taken using the Front and Back facing cameras can be downloaded in their original format from: http://www.multiupload.com/JNPJWF8YET – 8+MB file size)
The main complaint of the use of the camera comes down to Android itself. It is the stock version that does provide some level of tweaking. For the main camera, you get the full options of selecting the ‘Picture Size’ (3MP, 2MP, 1MP, VGA and QVGA), ‘Picture Quality’ (superfine, etc.), ‘Color Effect’ (Mono, Sepia and Negative), ‘Metering Mode’, ‘Anti Banding’, ‘Saturation’ (5 levels given), Contrast (5 levels), Sharpness (3 levels), Brightness (7 levels), Grid mode and toggling the shutter sound. The front facing camera has lesser options of course since its priority is not for normal picture taking.
Making calls on the DroidPad is as simple as it is on other Android devices. However, let me caution the potential user; do not try to use it as a normal phone by pressing it against your ears, it just does not work that way. The best way is to use the speaker to listen and to speak normally towards the microphone on the side. It works in most situations except in a noisy environment.
Reception is actually quite good. It does not drop in signal strength as much as my other phone devices. Maybe the size of the device has something to do with it, but whatever it is, it works well as a phone. The best option I guess would be to pair it with a bluetooth device. I found that the headset given was inadequate. The quality is horrendous and not worth using to receive calls.
I am very particular with the speed in which calls are received, and I can honestly tell you that it is almost instantaneous. Regardless of what application you might be using, the DroidPad quickly switches to phone mode at the first ring. This was and still is a problem for Android devices running on lower CPUs like the dreaded MSM7201A, 528Mhz processors, which gave a 1 second lag or more. Whether or not you will use this as a phone depends on your comfort level in using a device this big. Those who have used HTC’s Shift would find this a better alternative.
Like I mentioned before in the earlier part, the GPS map installed (with free 1 year service) is one of the most horrible looking software I have ever seen. The User Interface is archaic and does not give much information for the user. I ended up using Google Map as my default GPS map navigator. The GPS performed adequately. It is not fast by any means, requiring more than two minutes to get a solid fix (within an accuracy of 5 meters). It is not terribly slow either. However, if you want a cheaper and yet better alternative (only applicable for Asian users), download Ndrive. It is almost similar to Garmin’s GPS navigation app. I found that using Ndrive was a breeze, and because of the screen size, navigating in the car becomes less of a hassle. The only problem is to get a proper mount for the DroidPad since it would be a pain to hold it one hand for long.
One of my other gripes that I find with the DroidPad is the inconsistent WiFi connection. Every time it comes out of the lock screen, the WiFi connection will not re-connect itself automatically. To solve this, one must turn it off (via the power control widget for fast access) and turn it back on again. It is irritating, and I wonder whether I am the only one facing this issue. Besides this one issue, there is nothing much to complain about the WiFi. It is fast. I managed to update all 17 applications from the Market in less than 15 minutes. Not bad right? Some of the apps were big sized ones (mostly games like Zenonia which clocks in at over 10MB).
I have not tested the 3G connection on this (I cut my data connection some time back) but based on feedback, it seems to be performing adequately.
Although we have noted earlier that the screen is average, it is another thing when it comes to multi-touch. The device suffers the same problem encountered in the Nexus One when you use the MultiTouch Visualizer 2 app. From the video uploaded here:
(http://www.youtube.com/watch?v=p3TslDLrhQw), we can see that the points become confuse when they converge, often misalignment will occur, followed by the flipping of point identification. This means that the device has a flawed multi-touch implementation. It will not affect simple applications like pinch-to-zoom gestures, but definitely on more delicate applications (e.g. games) it will be more obvious.
USB On The Go
Surprise, surprise… the DroidPad does support USB OTG. Basically, this allows the user to connect the DroidPad to any USB storage device, like your thumbdrives. Very handy indeed if you want to transfer files over without the hassle of communing with a middle device. The caveat on this is the need for a USB Mini A cable that is short (not more than half a meter). Some have tested it with great success (working with many different USB devices). For a list of tested USB devices on the DroidPad take a look at here: http://forum.xda-developers.com/showpost.php?p=8819448&postcount=163. The forum thread even have links to buy the cables from Ebay, if you are interested. The small downside is the lack of unmounting function for USB OTG. You need to just disconnect the device from the cable to unmount it.
The thrill of Android as an mobile OS comes down to its ‘hackability’. If this is not your cup-of-tea, then you might want to skip this section. Anyway, based on my impromptu visit to the CSL headquarters in Malaysia, I was told by both the Marketing deparment and CEO that CSL is committed in developing for the DroidPad and to help independent developers to utilising the device to its full potential. Unfortunately, this is a hard thing to do when the product sold is not within the control of CSL. Ultimately, the firmware upgrades would come from Foxconn’s subsidiary which produced and developed the DroidPad (or whatever the actual model name is). This is also one reason (I suspect) that the two developers from CSL were unable to reply to my queries on the firmware and on root access possibility. Enough about CSL’s involvement or openness on this front. What about the device itself? Can it be modified? Honestly speaking, the fear was that there would be too few developers who would be interested in the device itself, to find ‘root access’ which would allow users to permanently modify parts of the firmware. Fortunately, root access was found within the week of launch in Malaysia.
Along with root access, the small community of DroidPad users have also found a way to install a custom recovery to ensure that the device will not be ‘bricked’. These are the firstfruits of an increasing acts of making the DroidPad more efficient. Already there are some in the small community who have gotten rid of all the localised apps (which were irritating to say the least). It is only a matter of time before the kernel will allow for over and under-clocking of the processor chip. This certainly would mean that the lifecycle of this device is lengthened. With this in mind, the potential of a more polished DroidPad is a reality. It merely takes time and commitment from the development community. If you are interested in such matters, do visit http://forum.xda-developers.com/showthread.php?t=793071 for the latest news on modifying/hacking the DroidPad.
Videos of Walkthrough of the Device:
It took some time before I managed to get this up, but here it is –
http://www.youtube.com/watch?v=0XsdPapTJZo – Simple walkthrough beginning from the Homescreen (LauncherPro), Typing using a Note App, Ebook Reader and testing of Live Wallpapers. Sorry for the poor video quality. From my Android HTC HD2 device.
Here comes the hard part of the review: the verdict. Is this device worth buying? Can it stand up to the onslaught of Android tablets that will surely come either in Q4 or Q1 of 2011? The answer is never so straightforward as a yes or a no.
The Pros of this device are:
Capacitive screen (beats all the generic resistive android tablets out there)
It is small enough to be portable (at 7″ inch)
It is big enough to read websites without much problem (Sorry Mr. Jobs, but 7″ does work)
Expandable MicroSD slot
2 Cameras – Video Calling
Large RAM space
Relatively cheaper than Samsung Tab
The Cons for this device are:
Screen is only average and has too low resolution
Bulky and not slim enough
CPU is too low for the price point
Accessories included are redundant (car charger given is the wrong voltage, headphones are of poor quality)
Redundant applications included (merely shortcuts to website based applications)
Developer support uncertain
Buggy software experience
Price point a bit expensive
Stock Interface not friendly (this is solved by installing ADWLauncher or LauncherPro)
Some of these things may not be a dealbreaker for you, but for myself personally, I find that the price is the biggest problem for such a device. Will it come down? Eventually, but by that time, there would be newer products (maybe even the next iteration of the DroidPad with Snapdragon chip). The current price at RM1,599 (USD507) is not convincing enough, especially when the experience is not as polished as the iPad (even though it offers more functionalities than the iPad). However, when you compare this device with the Samsung Tab, especially with its price point (which is around USD700 and above) then you may have a good deal on hand. I find that that if one or two weaknesses were solved (particularly relating to the screen resolution), the USD507 might just be a good steal! I reckon that USD400 would be the best price for this device to sell like hot cakes.
Based on a simple survey and feedback from people who have already bought the device, the general opinion seems to be pretty positive. Most people were quite satisfied with the purchase (especially after Samsung Tab’s price was revealed). As usual, make sure you test the unit out for yourselves before making that call!
All the best!
It is most unfortunate, but I doubt that CSL will provide support of any kind for this device. It is just not possible when they do not even have developers in charge of the kernel updates. I suspect that whatever support will have to come down from Foxconn themselves. And remember that this is easily seen when the only customization done on the unit is the introduction of ‘CSL apps’ that are frankly quite useless. These are not enough to differentiate the product from other regions. If you do consider buying the unit, you will have to rely on independent developers (on XDA or equivalent) for more efficient updates to the firmware. There are many things that need to be changed (it is hard to know where to begin listing the bugs).
For myself, I believe that Google is telling the truth concerning Android 2.2’s incompatibility with tablets. It is sad but a reality that many have to face up to. Android Honeycomb (supposedly 3.0) will be the one to watch for. Until then, it is not worth committing more than RM1.3k on a subpar experience that has not been customized to fit the target market. But again, this is my opinion 🙂
I am want to finish up my extensive review on the Mi700. I would like to get some real consumer feedback on the device before writing the closing conclusions on this. I need your help (especially those who bought the phone/tablet). Even if you did not buy the product, I would appreciate your feedback on the product:
Those who bought:
1) Are you happy with the product?
2) Do you think it was worth your money?
3) What do you wish CSL would change in the product?
Those who did not buy:
1) What was the dealbreaker for you?
2) What could CSL change to make you buy the product?
Thank you. Acknowledgement will be given to those who have given constructive feedback on this matter.
Okay, the first part was the easy part. Now comes the hard part… the software aspect of the DroidPad. First of all, let us remind ourselves that this tablet is running on Froyo, Android 2.2. Take note that this is based on my full week’s experience of the tablet. In the week that has passed, I have already installed about 30 programs (mostly free and some paid). Not only that, I have transfered over 2GB worth of media files. All in all, this should be a more balanced review and not just a ‘first look’ at the device. Onwards with the review:
1. Mflops: Mflops basically stands for Million FLoating point OPerations per second. It is a calculation intensive test where the higher the numbers, the better. Using Linpack for Android, the device scored 7.5 Mflops on average in 11 seconds. This is considered reasonable when we take into account the CPU which is an MSM7227 600Mhz (a slight upgrade from the older, and much despised, MSM7201A 528Mhz). Comparing with similar CPU devices, we find that the HTC Aria scores 5.2 Mflops with a slight overclock to 806Mhz while LG Ally/Aloha scores 9.1 Mflops with 30% overclock and HTC Legend scores 9.8 Mflops with 37% overclock. Certainly the Mi700 can hold its own.
2. BenchmarkPi: Basically the time it takes to calculate Pi. The lower the better. The DroidPad scores an average of about 2,800 miliseconds, not too bad considering a Snapdragon processor averages about around 2,000 miliseconds.
3. Neocore: This is an OpenGL-ES 1.1 graphics performance benchmark test. The DroidPad’s MSM7227 actually shares the same GPU as the Snapdragon; Adreno. I am pretty surprised by the outcome, since the DroidPad performed slightly better than my HTC HD2 Android (using a Snapdragon CPU and running Froyo) with an average of 32fps while the latter only a paltry 30fps.
4. Boot Time
This was timed from the moment the power switch was pressed and slight vibration felt, until the time when everything was loaded and lock screen appeared (SD card finished mounted). The total average boot time was approximately 60 seconds (1 minute). Frankly, I think this is acceptable although it should be improved. Somewhere around 45 seconds would be good.
Home Screen Performance
1. Custom Shortcuts: This is the version that came with the DroidPad. It looks very much like Android 2.2 stock, but with the added difference of a strip to the left hand of the tablet screen which contains 4 distinct icons. The top most is for mails, followed by an e-book reader, media and social networking shortcuts. I found this to be a redundant add-on since the system already allows users to put on widgets of their own. However, I suspect that this is not part of CSL’s customization but Foxconn’s, since the same shortcuts strip is seen in the similar devices shown elsewhere (Camangi Webstation and Viewpad 7). I have to say that they were not efficient to use at all. I found that the mail program took time to load, and was laggy. Same also for the media player. To its credit, it had a ‘cover flow’ type interface, but again, it was laggy and I kept selecting the wrong song since it either went too far ahead or too short before the one I wanted. Same goes for the social networking program which incorporates Facebook and Twitter. They look too much like the old web 1.0 interface.
2. Scrolling: The saving grace comes in the parts that are untouched, mainly the apps drawer. There is no lag in using the apps drawer and it was all smooth no matter how many apps I had installed and have open at any one time. Scrolling between screens were slightly laggy on the stock version. I have no idea why, but it just is. Not noticeable if you have never used another Android device, but still, it is just a little annoyance that I wished they would have cleaned up a bit more before shipping the devices out. As a matter of comparison, it felt slightly jerkier than using CyanogenMod 6 (Froyo) on a G1/HTC Dream phone.
3. Resolution: Because the tablet shares the same resolution as many of the more advanced Android devices, the grid that is available for widgets remains 4 by 4 (in all, you can put up to 16 application shortcuts on a single screen). The stock version only allows 3 home screens. If there is one glaring weakness of the Mi700, it would be the resolution size. Even though we have a considerably large screen, stretching an 800 by 480 resolution on it wastes that spacious capacity. What we get is the same 4 by 4 grid available, which translates to widgets getting blown up double the size, making them look awkward at best and ugly at worst! And the result is big spaces between each widget or shortcut; wasted space! I think if it was using the conventional netbook resolution of 1,024 by 600 pixels, this would have made the DroidPad near perfect! For some people, this might be a dealbreaker. Certainly, it would improve on the utility of the home screen.
4. Live Wallpaper: One of the most loved features of Android 2.0+ is the introduction of live wallpapers. Basically these are your normal wallpapers plus added interactivity and animation that adds to the level of ‘fun’ and ‘zazziness’ of a phone OS experience. I found that the DroidPad could handle all live wallpapers fine, without any hitch in the interface. The only problem stems when you are coming back to ‘home’ from a memory intensive application; it takes time for the live wallpaper to reload. That is the only problem that I have encountered, and this is nothing to do with the device, but to the software itself.
5. Alternative (LauncherPro): Personally, I ditched the stock home screen launcher and installed LauncherPro from the market. Buy it. It is worth it. This made the home screen less of a bore for me, as I am able to reclaim the whole screen for myself (no pesky strip to mess with the symmetry), and have up to 7 home screens. Not only that, but LauncherPro allows the user to heavily customise the feel of the home screen. The transitions between screens were smooth and flawless. The app drawer opened speedily and scrolling is smooth when there are only a few apps installed. However, after more than 25 apps in the drawer, I notice that it does tend to lag just a little. But besides that, there is nothing else that I would recommend for speedy experience. LauncherPro also allows the user to change the size of the widgets on the screen to suit their wants. Resizing helps to save space, especially when there is a need to put as many widgets as possible into one single screen.
One last reason to change the home screen launcher to the new one? The stock version only allows the user to use the tablet in landscape mode. This limitation is very frustrating upon me because of my tendency to do work in portrait mode. Thankfully, LauncherPro allows for this.
Note that the more active widgets (auto update) the user uses on the home screens, the slower the UI performance will be. However, based on my usage, I found that the 512MB RAM is well worth its size; I rarely felt that the screen was lagging because of the many applications that are open and the widgets that are actively updating itself.
6. Inputs – Virtual Keyboard, Accelerometer and Touch
I have not much problems with the touch sensitivity of the screen (as mentioned in part 1). However, I notice that in some situations, my swipes are not registered at all. Somehow, at times, I notice that some applications cannot seem to register my swipes and touches. A good example would be in the app drawer (stock version); swiping using my left thumb would result in absolutely smooth scrolling. However, if I were to use my right thumb to do the same gesture or swiping motion, there would be no response from the application. Strange, but these small ‘problems’ appear almost randomly throughout the week.
The accelerometer worked well on games in general. The user is given the option to calibrate the accelerometer whenever the necessity arises. I could easily play the game “Labyrinth” and see how accurate the motions were. However, it is to be noted that the game “Abduction” was problematic to play, as the accelerometer just went haywire.
The virtual keyboard provided as default is the stock Android virtual keyboard. The keys are well spaced on the tablet, but it makes it a bit hard to thumb type, since our fingers will not be able to stretch that far out. Nevertheless, if the tablet is rested on a surface, typing is much faster and more accurate. It is unfortunate that the keyboard does not respond as fast as the iPhone’s; there is a very slight delay and this is more noticeable when the haptic feedback is turned on. I do not think I can type fast using the stock virtual keyboard provided. As an alternative, I used Smart Keyboard Pro (paid version) which is much faster in response, and supports multi-touch points.
The best news concerning apps on the DroidPad is the access to Google’s Marketplace. Depending on the country you are in, you will be able to either access only free apps (this limitation applies for places like Malaysia) or both free and paid apps (only selected countries). In this section, I will just give an overview of the type of performance experienced in using various types of applications on the DroidPad.
The DroidPad comes with the popular Android e-book reader Aldiko installed in the system. Aldiko is the best reader that allows for offline reading, unlike other reader apps like Kindle. What makes Aldiko popular stems from its intuitive graphical user interface and ease of transitioning between pages. When the pages are rendered on the DroidPad’s 7″ screen, I have to admit that the words are so easy to read. There is no more need to squint or to move the device closer to us like other smaller devices. The 7″ inch display allows for more words to be fitted into a single page. Though the resolution for such a device might be low, yet I did not find myself struggling to focus on the text. This is definitely one of the plus points of having a device with ample screen size. Just like LauncherPro, the user is able to customise the way they read using Aldiko, till they have satisfied their own requirement.
2. Video Player
The DroidPad’s player only plays a very limited type of video formats (mp4 being the chief of them). I find the video player to be too simplistic. In order to test the video rendering capabilities of the DroidPad, I installed two video players; Rockplayer and Yxplayer. Both of the players could play a common .avi (dvix, xvid) file smoothly. The file played had a resolution of 624 by 352 pixels. However, the playback was not so smooth when playing a true HD 1080 video. On Yxplayer, the result was choppy at best. I tested MKV files and both players failed to play it adequately.
One of the missed opportunities for this device is to provide adequate coverage on video file formats that it can play. This is more surprising considering that this device has a graphical processing unit. Here’s hoping for a better update for the customers, incorporating these suggestions.
3. Social Networking Apps
There are many in the market for free from which you can choose from. I have to confess that it is quite a joy to see a substantial amount of updates without having to zoom in and to subsequently zoom out from using the device. Sharing news, photos and other media are as provided under Android 2.2. Everything works efficiently (minimal battery usage). There are no real surprises here.
Most games played well using the MSM7227 chip. The only thing to be careful is to know the limits of the CPU; cannot play certain emulators that are made for Snapdragon or Cortex chips. Zenonia (something like Legend of Zelda) played on the tablet at full screen. The controls and the performance of the game was really good, without any lag. Besides that, I tested a few emulators on the DroidPad. It seems that all emulators (e.g. Gameboid, Gensoid) can work well with the device, except for the PSX emulation. The screen size really helps to make the game more immersive for the most part.
5. Voice Search
This is a Google app that is integrated in Android 2.2. To enable this search, one needs to only hold onto the “search” button for 1 full second, and the app will start to receive the voice input from the device’s microphone. It works well enough for me; I spoke the words, “Wikipedia” and “Great wall of China”. The results returned was almost instantenous, clocking in at 1 second. I am really impressed with this.
6. GPS Navigation
The device comes with 2 maps that can utilise the internal GPS; MapKing and Google Maps. The former is included as part of the DroidPad package. Malaysian buyers get to use MapKing products for free using the 1-year subscription that they offered. Somehow MapKing (from what I can see) is not a good GPS application. It is definitely not an attractive package, unlike Garmin (see picture of MapKing’s UI above). The only other option for me at the moment is to use Google Maps. Unfortunately, Google Maps can only be used with a data connection (either 3G or wifi). I found that the GPS fix was very fast on Google Maps, within a few seconds (with AGPS turned on and while I was in the house and not open air).
7. Music Player
The stock player is the same boring app that has not seen much changes since Android 1.6. There was no problem in detecting my whole library of songs which I transferred via USB from my desktop. I installed Mortplayer (free) from the Market and used the widget to play songs when I am on the go. Surprisingly, the widget requires a few taps before it registers my touch. Once the app starts, it works smoothly with not much delays.
8. CSL Custom Apps
You might be wondering what type of customization CSL made for the devices. There are a few that is quite obvious from the apps drawer; Blueberry Messenger, Blueberry Store, CSL Azan Alarm (for muslims) and CSL Fun Club. All these apps surprisingly (except 1) are web-based; the icons only bringing up a shortcut to the respective website. The Blueberry Messenger is their attempt to have an IM (Instant Messaging) app that encompass as many social sites as possible. Blueberry Store is their web-based online store, while the CSL Fun Club is just a sort of gateway for people to explore their offerings given to potential customers. The only useful application that I could observe was CSL Azan Alarm… basically it is an alarm clock to remind the user of their obligations for worship. I found that the work done on these apps were minimal and therefore quite deplorable.
Multitasking works with these apps. I am able to switch on the music player while surfing and reading an e-book from Aldiko. Again, this is the benefit of having ample RAM size, which I am glad this device have in spades! There is no need for the application to reload all the data all over again when you are switching between applications. I tried to test the limit of its multitasking by using several memory intensive applications and switching between them to see whether they needed to be reloaded (a sign of insufficient memory). I opened Engadget’s app, Astro file manager, Aldiko, CadreBible, Market, Music, Browser (to a specific website that is graphically intensive), Angry Bird Lite (the game) and Mortplayer. It is surprising, but I actually had NO problems switching from one to the other. They were all still working without reloading the contents. I am thoroughly impressed because this is one of the aspects that are important in daily usage; worrying over memory management (I had a G1/HTC Dream and it was always a horror to switch applications).
According to the specifications, the DroidPad houses a 3,240mAh Li-Pol battery. I have done some test on this and have found some approximation of how long the battery can last. For simple usage, some surfing, checking of mails, typing, music and reading, you can easily squeeze nearly a day’s life from it. For heavy usage, where the above are done more frequently, then you can squeeze probably 7 hours.
The playing of media files will drain the battery faster than surfing does. To test how durable is a single charge (from the wall charger and not from desktop) I performed the following things: I played a 20 minute divx clip for 7 times while at the same time playing music from Mortplayer (continuously) and also switching on the display to the brightest setting and watch the battery drain away. The test started at 10am and when the device powered down by itself, it was at 3.30pm. Based on my simple test, the device lasted for 5.5 hours of heavy media usage!
Take note: charging the battery takes time, even when it is done from the wall charger. It takes approximately 3 hours plus.
Unfortunately, for Adobe Flash 10.1 to run, the minimum requirement is for an Arm7 chipset, which the DroidPad does not have (it has only an Arm11 chip). Well, do not worry much, since the iPad also does not have this and people are well content with it. For small Flash usage, there are always alternatives that can be used on the DroidPad. A good substitute for websurfing Flash enabled sites is by using Dolphin HD browser. It is quite fast and shows off some Flash contents (I have not use it extensively). This is a limitation that is not due to the software, but rather the hardware of the device.
To round up this side concerning the software performance of the DroidPad, I would like to say that there are some other concerns that I would like to put forth. The main one being, there are a lot of ways that the DroidPad can be made more useful and attractive, and all these involves having more developers to thinker on the software itself. I can only imagine getting Cyanogenmod 6 working on this device, thereby solving any buggy code or inefficient coding. Many of the problems detected in this review can be solved. Unfortunately, in order to do that, we need to get ‘root access’ on the device. Something that is for now elusive.
I cannot even seem to get ADB (Android Debug Bridge) to work with the device! I found that even the “terminal emulator” that is ‘installed’ on the device cannot be accessed by users. I have to install Android Command Shell app to use command line actions. It makes me wonder whether the DroidPad and CSL is open to the developers community? For certainly, they can gain so much more when the developers are collaborating to extend the lifespan of this device.
From my initial discussions with them over the matter of open development, they have shown some interest in pursuing this, especially in line with the massive third-party independent developers for the first batch of Android phones. We can only hope that CSL will show their support for such endeavour instead of just seeing this as a product.
The last part of this review will cover the final parts of the DroidPad: Camera, Phone Functionality and Other Uses
1. Download the file “SuperOneClickv1.4-ShortFuse.zip” from http://forum.xda-developers.com/showthread.php?t=803682. Extract the zip file out into a folder.
2. Replace the adb.exe from SuperOneClick with the adb.exe from the Mi700 CDROM (this is the virtual drive created when you connect your data cable to windows).
3. Run SuperOneClick > and then click “Root“… it will hang after completing a few tasks. Do not worry. Exit the program.
4. Run the same program again… Click “Root” again and this time, it will finish the process and it would show that the Mi700 is ROOTED.
5. Install the ADB drivers from the CD ROM Drive that is specifically created when you plug the Mi700 to your desktop. Either double click on the drive to enter setup or using Windows Explorer, click on “Setup.exe”.
6. Open a command prompt from windows, go to your adb directory.
[For those who have used ADB on other Android devices and have installed AndroidSDK]
[For those who are using ADB for the first time]
Open Command Prompt (Start > Run > Type “CMD”, and press Enter). Then go to the directory where you extracted the zip file in step 1.
E.g. C:\Users\[your username]\Desktop\SuperOneClickv1.4-ShortFuse
7. Come out of the command prompt window and Copy the file “su” (there is no file extension) from where you extracted SuperOneClick.zip and put it into your “c:/AndroidSDK/Android-Sdk-windows/tools” folder (if you have AndroidSDK), if not, put it in the same folder as the SuperOneClick extracted file.
8. In your command prompt from step 6, type:
adb push su /system/bin
and the file will be copied to your device.
9. If you had no problems pushing (copying the file) then go straight to step 9. If you get “read-only file system” error. Type the following from the command prompt.
adb shell mount -oremount,rw /dev/block/mtdblock3 /system
10. Important last step… you need to change the permission of the file so that you do not lose the root.
and a # prompt will appear. Type the following:
chmod 4755 /system/bin/su
and you are done!
This was discussed and found solely by Malaysians. Malaysia boleh! 😛
I will be doing a mega detail review of the DroidPad Mi700 when I get the review unit (God willing) on Monday, 4th of October 2010. I hope to be covering many aspects that I am interested in, especially from a developer’s standpoint and a flash-crazy Android freak view point. Of course, there will be the common angles which I hope to be impartial on (‘hope’… notice that word there :P). Anyway, there seems to be many positive responses so far from the release of the product. My simple post on the unit has garnered over 1,200 views, with no signs of let up. Thanks to Carrypad and Mytechnews for the coverage! Seriously, I am not into any commercial aspect of this. As you can note, this is purely my ‘hobby’ and ‘interest’.
CSL is a local Malaysian company who has in recent days garnered some headlines when it supported Fusion Garage’s controversy-laden JooJoo tablet early this year and later with its entry into cheap Android devices. Early this month, it announced its entry into the Android tablet, with its own version, called DroidPad. No, it has nothing to do with Motorola (and it shows). I took the opportunity this evening to visit one of the sales outlet which had a fully functioning demo unit of the product that is being sold for RM1,599 (no discount, at least from their retail outlet). That would be approximately USD500.
Just for your information, this is not a detailed review, since I only managed to spend 30 minutes in the outlet before feeling a bit uneasy, not giving the sales person a definite yes or no, in purchasing it. Nevertheless, thanks go to the outlet for giving me free rein on the DroidPad, to test everything that came to mind (I missed a few critical ones, as I will point out below).
This is a compact tablet at 7 inch (same as the Samsung Tab). It can definitely be held with one hand, although do not expect that hand to hold it for too long since it weighs half a kg. The size of the device makes it seem less bulky than it really is. The build itself feels solid, since it is lined with metal (aluminium? or a knock off material? I couldn’t tell). It feels sturdy enough that I am confident it won’t break after a fall. However, this is not a beauty to behold. It really does look ‘fat’, at half an inch (see picture compared to a 20cent coin). The unit was still wrapped in a thin plastic wrap (cheap way to prevent scratches I guess). I did not take note of the speakers, although I believe they are located at the sides.
The resolution is only at 800 by 480 (WVGA). The colours seem washed and not as vibrant as it should have been. This is one of the downsides of the DroidPad since they needed to cut cost from somewhere. However, the viewing angles were not that bad. You could still make out the images even at 30-45 degrees. Nevertheless, the display is of the capacitive variant (yay!) and I have to admit that it feels quite sensitive to the touch. Typing was a breeze and with ample room, I was typing away fairly quickly.
Interface and Feel:
The DroidPad uses stock Froyo, Android 2.2. The good news is: you can customize your own homescreen to your hearts content! The bad news is: CSL has put their horrible looking widgets at the side of the screen [update: this seems to be the same horrible widgets on Viewpad 7 and Camangi FM600]. The unit I was using had both the stock Launcher and Launcher Pro on it. I also found that the accelerometer did not kick into action when I rotated the screen to potrait (it seemed stuck on landscape) even though I toggled to auto-rotate in the settings. I find this is just poor implementation on CSL’s part; just slap some of their own icons to make it ‘theirs’. I am confident most users would just ditch the whole custom interface provided and run their own (ADWLauncher or Launcher Pro).
The transitions were smooth and there were no lag (not surprising since the DroidPad uses Qualcomm’s improved MSM7227 600Mhz CPU to power the device). Things just zip open. The only problem that I could detect was in some crazy input detections while using Google Maps (the pinch-to-zoom was doing the opposite of what we wanted). The screen also froze once (before it had to be ‘forced close’). I’ve seen this sort of behaviour only in the ROM flashing scene, when using an un-optimised ROM that has been freshly released. I suspect this is the problem for the DroidPad… poor development quality control. The importance is that this is merely software-related and not hardware; it can be fixed!
According to the sales person, there is no Flash available for the unit. I tried downloading from the Market (yes, they have the Market available) but it did not show on it. Which brings me to the Market; it is available from the apps menu (but sorry, no paid apps).
I installed Linpack Benchmark to test out its score, and found that it performed relatively well for its CPU, at 7.258Mflops.
Games worked well too.
I tested out Aldiko on the device, and found it very usable as an e-reader (see the picture). Would I use this to read Kindle? Why not? The screen is as big as a paperback anyway, and from my normal reading angle and distance, the words and text seem clear enough to me. I also tested the GPS and found it very speedy (again using the wifi connection only); managed to get a lock on my location in Google Maps in a few seconds.
What about browsing? It is acceptable. It won’t beat the iPhone 4 and the latest Android devices (of course), but it is not slow either. The best thing is the screen size allows a full site to be viewed without zooming into its part (see Engadget’s homepage that fit nicely in landscape mode). Even at that size, the text on the website can be easily read off the screen (see screen for yourself). The sales person told me that the DroidPad comes bundled with MapKing and a free one year license (good for Malaysians!). I think this device can easily replace any Garmin standalone devices for the car.
It is a paltry 3.0MP camera in the back and a VGA (I believe) in the front (top right hand, see picture above for the smaller front facing camera). It takes adequate pictures (which reminded me of the camera on my old HTC Dream). Don’t expect much from it. For simple photo taking, it is quite fast. Video was basic and low quality. Unfortunately, I should have downloaded Fring/Skype or Qik to test out the front facing camera also. But I forgot all about that.
Besides not testing the front facing camera, I did not test the phone functionalities also. What I was told is that calls can be made via a handset that will be supplied along with the tablet. You can also pair it up with a Bluetooth headset if you want. Oh, please do not trust what the website says about their battery usage… CSL products are known for their poor battery quality. [Update: 3240mah battery made from an unidentified ODM, Original Design Manufacturer, is really hard to validate, without formal testing] Really sad but true. I think it should last at least 6 hours of heavy usage. It should, but again this is mere speculation until I get my hands on an actual unit (if ever).
Is the DroidPad worth the money, given that the screen is only adequate and has low resolution? Does the USD500 justify the 2 cameras, the GPS and phone functionalities? I think on the matter of hardware, it seems a good price to pay for those abilities that were non-existent on the iPad. But if you are looking for high-quality builds that you can show off to your friends, well, let me suggest that you just walk away from this one. DroidPad at the end of the day, may not be an iPad alternative, but it sure is a Tab alternative.
I suspect that the DroidPad would be popular among the developers and Android hardcore developers and users who would like to rebuild the ROM and fix all the software flaws that was inherent in CSL’s work. I am sure that there is just so many things that you can do on this device that were not possible in smaller phone screen sizes. On that hope, I think the Android fanboy would be more than willing to spend that money on something that is a much cheaper version of the Samsung Tab.
Or you can just wait a month or two for the price to go down another RM100-RM200 before buying it. At RM1,300, this device is a MUST buy, given that it really delivers the basic Android experience that we have come to love.
The device is already available locally in Malaysian stores. No word about international sales though.
I am planning to take a break (maybe a long one) from the world of Android and of phones in general. Actually, it is only from the Smartphone category. I find that I spend quite some time catching up on news particularly on the three main OSes as I perceive them, namely Android, iOS (aka iPhone OS) and Windows Phone. For that reason, I am selling off my faithful HTC Dream that served me very well for more than 1 year since I bought it back in May 2009. It is a worth while investment, in my honest opinion.
The Build, Keyboard and Display: HTC Dream is a solidly built phone. I got into a dispute over this on Facebook with an old (now) acquaintance over this point. It is solid. I have dropped this phone a few times over my usage of it and it has NEVER caused any problems or glitches at all. Sure there is a bit of ‘give’ in sliding the keyboard out and in, but it is nothing but a design aspect that may have been poorly executed. Typing on this is really fun since the keyboard is well spaced. In fact, this is one of those HTC devices that provides a 5 row QWERTY keyboard layout. People do not realise the convenience of not having to press the function or shift key to call up ‘numbers’. Personally, keyboards are fun and important because of the tactile feedback and because it gives more screen size when doing certain things. Playing emulator games in general is a bliss because I have an unhindered 3.2″ view of the screen, which is very different from having my hands cluttering most of the screen on a full touchscreen device. 4 buttons with a ‘Menu’ button, volume controls on the side and a dedicated camera button brings a lot of ‘buttons’ on the first Android phone. The good thing is that it is uncluttered, since the buttons are small and well spaced. But mine you, this device is heavy. If you have used a purely touchscreen device, do not expect the Dream to be equivalent in weight and size. It weights a heavy 158 grams. But if you compare this with other keyboard devices, it is considered alright (especially for its age).
Digital Compass: Besides all this, the existence of a digital compass was a first for any handset of its time. The value of this was explored in the initial application by Google, Google Sky Map, that allowed a person to identify the sky objects above him, wherever he was in the world. It was an amazing app that had frightening accuracy and worthy as a ‘show off’ app to friends who were ignorant of Android. Besides that, its integration into Google Maps was beneficial to provide more accurate directions for navigations, where before, it was done mostly by calculating the GPS location changes to determine driving directions.
Having said this, there are of course some negative aspects to be wary for the phone; the inconvenience of slotting the microSD card and the battery is at the top of this negative list. The other thing is of course the weight, since it is well over 100grams. But then again, some of us prefer such ‘weightier’ phones in order to ‘know’ that it is there. The weight does bring some reassurance of its presence, at least that’s the case for me.
Now, one issue that I think is a mixture of hardware and software, pertains to the sensitivity of the capacitive screen. I would have to admit that the sensitivity is alright but is not as sensitive as I would like it to have. It takes sometime to get use to the screen input, as sometimes it would register a touch, and other times it would only half register it. Maybe it is the screen protector that I use, but I have to say that it certainly needs to be tweaked to be more sensitive, especially for keyboard typing (using the virtual Android provided). The sensitivity seems to be more problematic towards the edges of the screen compared to the center. It is not a deal breaker for me, but definitely takes away some joy when compared to the iPhone screen (sourced from Samsung).
The lack of proximity sensors is a minor thing, especially when it was launched (in late 2008), but the lack is more pronounced now when most new handsets include that as part of the battery efficiency measure.
Having said enough about the physical appearance of the phone, it is time to get down to the main thing concerning the HTC Dream phone; it’s performance on Android. I have to say that the experience is not bad at all. Granted that I have rooted my phone and installed all the necessary components needed to run custom ROMS, but nevertheless, running Android 2.1 (aka Eclair) was a smooth transition from 1.6 (Donut). Probably it helped that I was running a modified kernel that allowed for overclocking of it’s weak CPU, the MSM7201A chip running at 528Mhz (originally only 384Mhz on stock ROM). With the CPU overclocked to a maximum of 633Mhz and underclocked to a minimum of 160Mhz, performance was snappy. The downside for the performance of Dream comes from its limited and poor RAM space, which is only 192MB. This is definitely not sufficient, and is shown by its lag, when the CPU tries to free up space to load other programs or applications. This can be circumvented by installing Swapper that uses the MicroSD card as a ‘virtual or fake’ RAM. It works to an extent, which is why it is always better to set the swap size to something small like 32MB or anything below 64MB. Using custom homescreen launchers like Launcher Pro (which I highly recommend) I find that the screen flies at the littlest swipes on the touchscreen. Applications could generally work pretty well (as long as it meets the criterion given, e.g. CPU speed) and does not have too much of a lag (especially when using Swap).
However, the down side is in the inevitable lag that is occasionally experienced due to the poor RAM size. This happens even with swapper, in the rare occasions when the swap size is more than 64MB. Not only that, the performance of ‘contacts’ and ‘dial panel’ is marred by a 2 seconds lag. Keeping the swap alive helps to make an instantaneous change to the phone function needed, but you will still need to initiate it first, in order for it to be stored in the phone’s memory. This is but a secondary solution to a main problem in switching between the phone functions. However, I find that this is slightly improved in Cyanogen’s ROM 5.0.8. final, when compared to Donut and Froyo (CyanogenMod’s 6.0 RC). This will not be fixed unless a developer comes out with a streamlined version of the ROMS without other resource hogging applications available. We have not seen such innovation on this front yet.
Playing Emulators on the HTC Dream is wonderful to say the least. Why? The physical keyboard actually allows the user to map any key to the keyboard without our hands occupying or covering at least 1/2 (half) the screen size. I usually get the full 3.2″ inch display whether I am using the Genesis or Gameboy Advanced on my keyboard! The effect is much better than the full touchscreen phone.
Camera and Video Recording
The 3.2MP camera was adequate for the job, although it does not produces much radiancy of colours. For quick shots, this is ideal. The waiting moment between shots is around 3-4 seconds. Video is pathetic, but will work for sending MMS quality files or for quick short clips. A new improvement on the camera has already been completed (only for rooted phones with CyanogenMod OS; a bump up in resolutions to 480*320 with an estimated frames-per-second (fps) of 13-14fps. This is not remarkable, but at least it is an improvement from the stock radio.
I sold my HTC Dream recently. I still miss the amount of hacking and tweaking made available to Android enthusiast from XDA and some other phone portals. However, I would not mind picking up a second HTC Dream if given a second set. It is useable as a daily driver and I would recommend it with minor qualifications. The solid build will ensure that it will give you what you need even though there might be the occasional bugs popping up whenever it feels like it.
Most G1/HTC Dream users would have rooted their phones to maximise the usage of the phone (and extend the lifecycle of the product). In so doing, they run many different ROMS; I use CyanogenMod. The ease and safety of changing ROMS (imagine the OS version for a typical desktop computer) is astounding especially with the use of recovery tools that allow one to make a full backup of the current ROM along with whatever extension drives that are in the SDcard (since it is based on Linux, Android ROMs utilises ext 2/3/4).
I was using Amon Ra recovery tool, an excellent tool for recovery. But sometimes in performing a full Nandroid Backup, you may come up with this error: “run nandroid-mobile.sh via console”. In such instances, don’t worry… just connect your device to your computer and perform an ADB connection.
From your desktop console (windows environment I presume), type:
adb shell mkdir /system/sd
Voila. Perform your nandroid backup again and it should work. Basically, the error occurs because there is a missing /sd folder in your /system folder.
Works every single time. Enjoy and happy flashing ROMs!