I (still) use a Nexus S phone. I am using Cyanogenmod on it. After an article in a computer magazine I decided to give the ART-runtime a try instead of the default Dalvic-runtime. Unfortunately I do not have enough free space free (and all what I can is moved to the USB storage already) to really use the ART-runtime.
After switching back to the Dalvic-runtime, I had only 2⁄3 of the previously available space free. After a little bit of looking around I found /data/dalvik-cache. I deleted with a file manager the content of the directory (you will get some “app crashed/died” messages) and rebooted the phone (this is not the same as formatting the cache partition in the recovery system).
During boot it populated the directory again and now I have more than 4⁄3 of free space on the internal storage.
Maybe not all… my colleagues wouldn’t have gone there if I wouldn’t have said something…
To be honest, I would have expected something a little bit more shiny/geeky/… to take a picture of (anyway, if you don’t see it: I have a real smile in my face on the picture, so the geek in me enjoyed taking the photo).
As toldbefore, I have the ICS as provided by Samsung (to it is not the stock ICS, it is the Samsung-version of ICS) on the Galaxy Tab 10.1. Now that it is nearly two months of using it, I want to share a little bit of my experience.
Basically it just works. If you know ICS already, you more or less know how it is on the Galaxy Tab 10.1.
The calendar app is different, it is the Samsung app, not the native ICS one. I have a problem to sync it with the exchange-connector as it is in Horde 4, but I did not take the time to investigate the issue. My Nexus S connects just fine, so it must be some modification by Samsung which is causing the issue.
Sometimes the tablet hangs, and I have to shutdown by pressing the power button for some seconds. This only happens when connected via WLAN. When I start the tablet again, it will hang again if I am not fast enough to enter the PIN of the SIM, unlock the screen and to deactivate the WLAN. But even then it will hang after the deactivation of the WLAN. After rebooting the second time (with WLAN already deactivated), everything works again.
The email app is also stuttering sometimes. This happens when I open a folder with a lot of emails and the email app is trying to determine if there are attachments or not. Either the app is not multi-threaded, or it is not well done.
In the review of the Email app of Android 3.2, I complained that the message-list moves in a way that the selected message is in the first place of the message-list. This was annoying for my workflow. In the Android 4.0.4 app (at least as it comes from Samsung for the Galaxy Tab 10.1) this changed so that it is the second item in the list in some circumstances (this does not happen always). This is better (somewhat acceptable) for my workflow, but still, I would prefer if it is at least configurable. Do not move the list when I select a message, except for making a partially visible list-item completely visible.
The other point I did not like about the 3.2-app was the folder list moved so that the inbox is first when returning to the list. Thank god this changed too.
The two big disappointing points I had about this app are mostly fixed in the ICS version.
Last week I had a look if there are some news for an official update of the Galaxy Tab 10.1 to ICS. To my surprise there is one at least in Italy. The one I found to download was marked more or less for the European market. Well… that was good enough for me and the night from Friday to Saturday I have spend to update the Tab by hand (unfortunately this includes a factory reset, no smooth migration from an old version, but at least I still have root access).
What I noticed so far:
OpenGL ES speed improved from 4.2 to 6.6 FPS.
I had some lock-ups so far, I do not know if this may be related to some restored data (app data and e.g. Bluetooth/WLAN config restored with TitaniumBackup) or to bugs (Dalvik cache and cache partition where clean, factory reset was done too prior to restoring from the backup). I had to press the power button for some seconds to initiate a reboot. Most of the time it helped to wait a minute before entering the PIN for the SIM. One time it did not help at all, the only way to get it working was to take my WLAN Access Point (AP) offline, start the Tab, enter the PIN, and to restart the AP. At that point I had GPS and WLAN in the Tab activated, in the lock-ups before I did not have GPS active. I had something similar like this with my Nexus S when it got ICS, somehow this resolved itself. Update 2012-08-14: I googled a bit, there was a bug in ICS 4.0.3 related to WLAN, but I have 4.0.4 on the Tab, so this may not be this. I also got the freeze without WLAN but with the mobile data connection active. 2nd update 2012-08-14: If I disable account syncing with the mobile data connection it does not freeze. I have not yet tried this with the WLAN connection. Update 2012-08-16: The synchronization of the calendar data caused the problem. Deleting all data for any app with calendar in the name and re-syncing fixed the problem. No freeze since I did this yesterday.
When I open/close a folder (much missed feature in Android 3.x), the Tab speaks with me (something like “Folder XXX opened” in the configured language… that is a bit annoying).
I like the default background image.
Update 2012-08-14: The battery icon does stay green even when the battery is nearly empty. 🙁
I was not able to test the Email APP yet, I am waiting for a warranty-replacement of the PSU of my server at home (Murphy’s law: Your PSU will break when you just started a big renovation of your kitchen and do not have time to take care about it, and when you get time a lot of people from the PSU-manufacturer which take care about warranty-replacements are in holiday).
I also need to check the mobile data connectivity (quality and speed), but I would expect that it is not worse than before. Update 2012-08-14: The download speed test shows similar results than before, the upload speed test is slower, but this may be the mobile network here where I tested. At least I can confirm that it works, modulo the problem of the freezes described above.