Antennagate passed, Glassgate has just started. What's up next, Apple?

The antennagate madness seems to be finished now (everybody knows now that Apple's faulty design is causing signal lose, or even call drops), and the next problem, generically named glassgate, has just started. It was believed that it was just the creation of the competitors, but it seems to be quite real now because Apple has taken measures against this problem.

It is not clear how resistant the glass from the back of the device is, as there were reports which said that after the device has been repeatedly taken out and inserted back from and in some cases, scratches occurred on that glass. It seems that dust particles can get stuck when the cases are inserted (between the case and the glass), causing serious scratches on the glass. In fact, these scratches will, eventually, create cracks on the whole glass surface from the back of the iPhone 4.

It seems that Apple is aware of this issue, because they pulled from the Apple Stores from all around the world all cases of this type (at least until this problem is clarified). So, if you don't have a case, you'll get call drops because of the way Apple designed iPhone's antenna. But if you get one (anything else except the bumper), you risk to have the glass from the back of the device even cracked.

I already see Apple telling everybody that their products doesn't have any issues, and users are the only ones responsible for that scratches/cracks (just as they did with Antennagate).

Samsung S2 are quite good external HDDs. Unless you're going to use them with Multimedia Players (Popcorn Hour/WD HD TV).

Samsung S2 external HDDs are quite attractive products. Mostly because of the variety of capacities, and because of the available colors. So, they look good, they are perfect for backups, and they work well (I get somewhere around 25-30 MBs reading/writing rates on my computers). But if you're planning to use them with multimedia players, such as Popcorn Hour or Western Digital HD TV Media Player, they are going to give you an enormous headache.

I also got one, a blue one, with 640 GB, and I have some issues with it. As long as it is on FAT32 file system or HFS+ (Apple native), it works like a charm, both on my Popcorn Hour and on my WD HD TV. But when I'm converting it to NTFS, it is completely unreadable by my both multimedia players.

WD HD TV used to say that it didn't recognize it, but after I was told that an unofficial firmware might make it work with my HDD, now it doesn't react at all when I'm connecting my HDD to it. On Popcorn Hour, it simply says that "USB failed". I tried connecting it through an external USB hub (which was externally powered), in order to exclude the possibility of failing because of not getting enough power, but the S2, formatted on NTFS, won't work at all.

I found on some forums users complaining of this (reproducing exactly the same situation, the S2 work on these multimedia players as long as it isn't formatted as NTFS), but there's no fix for this (only some suggestions that were tried by everybody having these issues, suggestions that don't help).

If you're stuck here, you can format the external HDD as HFS+ (FAT isn't an option, as it has  limitations), and then install MacDrive on your Windows computer (unfortunately, you have to buy it), which will give you the possibility of both reading and writing to HFS+ partitions from Windows. I don't know if MacDrive can format the HDD as HFS+, because I did it from my MacBook.

Anyway, the idea is that if you want to buy an external HDD and you're planning to use it with a multimedia player, you should avoid Samsung's S2 external HDD.

Solving AccuWeather's app force close problem (Android).

If you're an Android user, you probably know that after the latest update, AccuWeather app stopped working and everybody complains about this (any device, any Android version). It simply force closes after the launch. It seems that AccuWeather is never going to update that app, so I found a way of getting AccuWeather data on your device, under the same interface.

There are more AccuWeather apps in the Market, if you search for them. However, I've found one which really works, so if you search for "ACCU WEATHER Quick" (yes, ACCU WEATHER with capital letters), you'll get an AccuWeather app which really works. It seems to be released by Accuweather.com (nobody knows exactly), and it has a few bugs, but at least it works. Some users reported problems with the widget, problems that I don't confirm. There were also reported some problems with the accuracy of displayed information, but as I've just downloaded it, I think that the information is quite accurate.

So, go to the Market and download "ACCU WEATHER Quick" app to see if that one works for you.

Is Facebook down at this moment? Some users report so.

There are some users currently (1:50 PM GMT time) reporting that Facebook is down, via Twitter. It is not clear, however, what's happening, because there are other users reporting that Facebook works just fine for them. I have to mention that Facebook works for me quite well. Downrightnow.com, which is the website that monitors lots of services and reports if a service or another is working or not, is currently displaying Facebook as "Likely Service Disruption".

This state comes from users that reporting both on Twitter and on downrightnow that Facebook is down, while the Facebook officials didn't confirm (yet) that their service has any kind of problems.

If you want to see the progress of Facebook, just follow downrightnow.com. If you are an user of Facebook, please leave a comment telling us either if you have problems in accessing Facebook, or if works fine for you.

HootSuite say Twitter API is currently experiencing a critical issue that affects some third-party clients.

HootSuite announced on their official blog that Twitter's API is currently experiencing a critical issue, and that is the reason of which some third-party clients (including HootSuite), have some problems. They said that "Home" and "Mention" streams are currently not updating correctly, and this also affects the users of iOS and Android. Additionally, some users may also experience crashes when they try to view certain streams.

They also said that the guys from Twitter are aware of the problem, and they are working in order to fix this.

You can view the current status of Twitter's API here.

Fixing "SD card damaged. You may have to reformat it" issues on HTC Nexus One/Desire.

I've got today this issue after I transfered a file from my computer (Ubuntu) to my Nexus One (which runs the stock Android 2.2). After I clicked "Safe Remove Hardware" in Ubuntu, I got the following error on my Nexus One: "SD card damaged. You may have to reformat it". I've searched for more hours on many forums, and it seems that this is more a regular problem for HTC Desire, rather than for the Nexus One (only a few Nexus One users reported this problem).

To be more exactly, this problems seems to be caused by a poor quality of the microSD with which these devices come. I've tried fixing this by rebooting the phone with/without the microSD card inserted, or with apps from the Market, but neither of them worked. I was not at home and I didn't have a (external) card reader with me, so I got stuck there for the moment.

After I got home, it took me some tens of minutes after I got this fixed, so here is what I recommend you doing. Insert the microSD into a card reader, because in this case you have access to what's inside it. Copy all the files on your computer (for backup), and then, using a utility application which can deal with storage drives and partitions, try to completely format the microSD using FAT file system. 

I've done it using "Disk Utility",  a program which comes preinstalled with Ubuntu. I'm not sure, but the default Windows partitioner should be able to do do the same. I've also tried formatting the microSD directly from the phone but it didn't work.

After you finish formatting the microSD, copy back all your data to it (do not delete your data from the computer yet! keep that for backup), insert it in your phone, power it up, and wait. If everything is fine, the device will start, slowly, to display all data you copied back to the microSD. Music and pictures are going, for example, to be displayed gradually (it may take a few minutes to display all music and pictures). If this happens, you may now delete the data kept for backup in your computer. The only problem is that I don't have anymore all apps I had installed on the microSD. Excepting this, everything is back and working.

If you still have problems or you need help with formatting your microSD, don't hesitate to request help via a comment.

Ubuntu 10.10 Alpha 2 getting out of control.

A few days ago I presented you Ubuntu 10.10 Alpha 2 (here), telling you that it has some bugs at sound (it doesn't work at all with some sound cards) and at booting procedure (or more exactly, it fails the installation procedures and is forced to boot in live CD). However, there is another critical bug that I experienced a few minutes ago.

Here are some details: Pidgin + Chrome were running (nothing else) while I was notified that Gwibber crashed (it was not running, I didn't open it). Everything is...normal until now, I periodically receive notifications telling me that Gwibber crashes (even without running it). But what happened after was....let's say, normal for a pre-release version of Ubuntu. The main problem is that you it makes it difficult to save what you were working on at that time. This is what I'm talking about.

When Gwibber crashed, "Report a problem" has opened, in order to let me send details to developers, to help them fixing the problem. And it seems that, I don't know why, "Report a problem" crashed after that, too. And again. And over and over again. I think that every second, two windows of that type were appearing. That's not much, I know, but for my desktop, which doesn't have video hardware acceleration (lack of drivers), they are a real problem, as it is hard to save anything.

So, here's a new bug that developers need to fix for the final release of Ubuntu 10.10.