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.
I have an old system (only the hardware, it runs -current) which reboots itself from time to time (mostly during the daily periodic(8) run, but also during a lot of compiling (portupgrade)). There is no obvious reason (no panic) why it is doing this. It could be that there is some hardware defect, or something else. It is not important enough to get a high enough priority that I try hard to analyze the problem with this machine. The annoying part is, that sometimes after a restart apache does not start. So if this happens, the solution is to login and start the webserver. If the webserver would start each time, nearly nobody would detect the reboot (root gets an EMail on each reboot via an @reboot crontab entry).
My pragmatic solution (for services started via a good rc.d script which has a working status command) is a crontab entry which checks periodically if it is running and which restarts the service if not. As an example for apache and an interval of 10 minutes:
*/10 * * * * /usr/local/etc/rc.d/apache22 status >/dev/null 2>&1 || /usr/local/etc/rc.d/apache22 restart
For the use case of this service/machine, this is enough. In case of a problem with the service, a mail with the restart output would arrive each time it runs, else only after a reboot for which the service did not restart.
Since a week we (7−10 people) can not make or receive phone calls with the phones at work. Luckily this is only the remote-half of the team which works for this client, the onsite people do not have this problem.
As bad as this is from the client-relations side of view, I have to say this makes it quiet and relaxing here ATM… We get requests via EMail or our ticket-system (or a coworker provides some info on the mobiles) and we can handle them without much disturbance.
Before you think bad about the company I work for… we are just a subcontractor, the phone lines are not handled by us (but I was told that the issue is now looked at by the big boss).
The running gag of the week is making the error-noise of the phone.