Posts Tagged ‘Vodafone’

UMTS / 3G standard video calling (or the lack of it!)

December 8, 2011

One of the new features 3G phones introduced was the front facing camera and the ability to make video calls between them.

As far as I know, this feature was initially a flop: video calling was much more expensive than traditional phone calls which led most consumers away.

In the last couple of years, at least in my country, carriers like Vodafone introduced new prepaid plans that not only allowed free voice calls between phones (using the same plan) but also free video calling (again, between phones with the same prepaid tariff).

I noticed that, thanks to these new prepaid plans a lot of consumers rediscovered video calling and, especially if living away from their loved ones, started to use this feature a lot more often.

At the same time, a lot of people started to dump their old 3G dumb and feature phones and joined the smartphone revolution. Unfortunately most have discovered an inconvenient truth: Most smartphones can’t make the standard good old video calls!

– iOS devices are able to make video calls through data networks (FaceTime) but are not able to make standard 3G video calls.

– Android also do not support natively standard video calling, although is able to do so via Google Talk or Skype.

– Windows Phone just recently started having phones with a front facing camera in the market, but, like Android or iOS, do not support UMTS video calling.

I have to recognize that, apparently, the only manufacturer concerned about this and that’s making an effort to make both Android and Windows Phone smartphones compatible with the old video calling standard is Samsung, as you can see in the video below (made by HDblog)

All other phone manufacturers I had the opportunity to try, such as standard Google Nexus phones (including the Samsung ones), HTC, Sony Ericsson and Apple are not able to do it, which is really a shame, since this was a feature available in older mobile OS such as Symbian or Windows Mobile.

Final thoughts on Samsung’s Galaxy S

December 2, 2011

As you might have noticed, I’ve been using (since mid-2010) Samsung’s 2010 flagship, the i9000 Galaxy S.

I bought it carrier-locked to Vodafone for €420. In the European country I currently live in, it’s almost the minimum wage!

Besides all the marketing efforts Samsung put behind it (especially at the European airports!), the phone was €250 cheaper than the iPhone 4, packing almost the same (or better) hardware:

– The 1GHz Hummingbird SoC, co-developed by Samsung with Intrinsity (later acquired by Apple) is similar to Apple’s A4 chip

– It has 512 MB of RAM (as the iPhone 4/4S)

– The SGX540 is better than iPhone’s SGX535

– The Super AMOLED 4″ display is bigger and offers deep black levels

Spec-sheet wise, this was the super-smartphone I was waiting for to replace my old Symbian-powered Nokia.

There were a few things hardware-related the spec-sheet did not mention I’ve only discovered after some time:

– The SIM-card hold mechanism (or the lack of it!) was not very good. The phone was losing the SIM-card all the time in the first weeks and I initially thought it was the SIM-card fault. I asked Vodafone for a new SIM-card and with this one things got much better. The problem was not completely solved, as I had this problem again with the new one, although much less frequently.

– The battery was not completely still inside the phone. When I grabbed the phone I often felt the battery moving inside, but I did not care about this very much since the battery never actually lost contact (unlike the SIM) with the phone.

– The back cover, made of cheap plastic, did not provide a premium quality that a flagship phone is supposed to have. It was prone to scratches, which over time made the phone look used prematurely.

– The Super AMOLED screen has awesome deep blacks but after about 6 or 8 months of usage there was some burn-in, especially at the top where the notification bar with the clock is. I believe this was one of the reasons led Samsung to change the notification bar color from grey to black.

– Antenna performance was definitely not great: at my place’s basement, where any old Nokia could get 1 or 2 bars my Samsung frequently lost connectivity to the network and even when there was connectivity, making a phone call was almost impossible. Same thing happened at my University’s library.

So, there were a few issues with the phone’s hardware, that revealed it not as high-quality as I thought initially it was.

When I bought the phone, Android 2.2 Froyo was already in the wild, but the Galaxy S was still running Android 2.1 Eclair. It didn’t take long till I find some annoying problems with the phone’s software:

– Android was noticeably slow and the performance was underwhelming (Quadrant score was around 700 or 800 points, slower than it’s main competitor, the HTC Desire)

– It wasn’t able to get a lock with the GPS satellites (maybe this was also a bit related to the antenna performance)

– There was some overheating after playing some games

– Animations were not smooth, such as the Vodafone logo when starting up and shutting down

I looked for the issues on the web and apparently they were pretty much common knowledge among the owners, but there was Android 2.2 coming and this update was supposed to fix everything for everyone. So, instead of returning the phone within the first 15 days, I just kept the phone waiting for the promised update.

This belief was my mistake as I found out later! In fact, Samsung took a long time (several months) after the launch to release Android 2.2, postponed the update several times, and when finally released it, Vodafone took some extra time to release it to their own branded-handsets. I’ve lived without Skype or Flash for a long time, as both required the Galaxy S to have Android 2.2. It’s worth mentioning that my previous phone, a Nokia with Symbian S60v5, ran both Skype and Flash Lite, so Android, at this point, was some sort of a regression.

By the end of 2010 the update was eventually available! After some weeks, even after factory resetting the phone, I concluded that, beside now having Flash and Skype, everything else was still the same: the lag was really noticeable, Quadrant score was just around 150 points up from the previous version, GPS would lose the satellite fix all the time (making it impossible to use in the car) and then there was the overall stability: instead of getting better, it seemed even worse, with games such as Angry Birds crashing the phone entirely as you can see below.

When it crashed like this, I had to pull the battery off or press the power button for a very long period of time until the phone restarted by itself. Another problem was that, despite the performance improvements of Android 2.2, the phone slowed down as time passed by. Eventually the phone would be so slow and lag so much the only solution would be to factory reset it again, lose all the progress and data of the apps and games and start all over again, since there is no official way of backing up the data without rooting the OS.

My new hope by then was to believe that the future Android 2.3 Gingerbread would make a miracle. It wasn’t until the summer that the Gingerbread update was finally released by Vodafone and I updated the phone and reset it… again!

In the first week I truly believed the miracle have been made: the phone was now blazing fast, GPS seemed ok, Quadrant score made a huge jump, almost doubling the original Android 2.1 score!

I finally had this amazing phone I was expecting to get when I bought it one year before!

Unfortunately this great performance did not last for long and soon I was feeling the old lag back again, the GPS was not that good after all (although improved, the precision was much worse compared to a friend’s Sony Ericsson Xperia Neo), the performance was decreasing (Quadrant Score was scoring lower results as time passed by), the stability was hitting all time lows (both games and popular apps such as Facebook often force closed as you can see below) and then there was a new bug I already wrote about in another blog post: the Android OS battery drain bug!

Another thing that really annoyed me was the browser! Samsung made a few changes ruining it even more:

– In Eclair the browser supported up to 8 tabs, but in Froyo and Gingerbread it is limited to 4 tabs!

– Samsung removed the + and – button that allows you to zoom in and out without using the pinch to zoom gesture

– Unlike other Android competitors, the browser did not fit the text automatically to the screen when zooming in, you needed an extra double tap after pinching to zoom

– Browser performance is far from good, the SunSpider score is not impressive at all and there was a problem with the kinetic scroll I mentioned in a previous blog post

– Stability was never something to brag about, and in my opinion it got worst in the latest Gingerbread updates

– There was some rendering issues with some websites (e.g.: lists that did not appear), as you can see below

– I suspect the browser had frequent memory leaks, and since only about 300 of the 512 MB of RAM were actually available to Android I believe this was one of the reasons Samsung limited the browser to 4 tabs from Froyo onwards.

It’s amazing how the most expensive and sophisticated phone I’ve ever bought turned out to be the worst I’ve ever had!!!

After I’ve searched for a while there was a recurring answer to all my problems: surrender and enjoy the dark side of custom ROM’s, such as Cyanogenmod 7!

The community had come up with some of their own-made firmwares that improved noticeably the performance of the phone but in most of these custom ROMs there’s always a few drawbacks:

– First of all, you lose the manufacturer’s warranty (which is a big deal to me!)

– Battery life is apparently even worse compared to the official Samsung firmware

– I would also lose the ability to make standard UMTS/3G video calls

– The camera performance would decrease, since 720p HD video recording was not possible or not entirely smooth

– Some features at some point were not yet developed (such as FM Radio)

So, even though this kind of custom ROMs actually solved some performance-related issues, I would not get as many features as in a Samsung ROM.

The community also came up with some “lagfix” apps that, as far as I know, change the original Samsung filesytem to a faster one, which solved, at least temporarily, the lag problem but required rooting the OS.

My personal belief is that a manufacturer should be responsible for supporting their own products, especially one such as the Galaxy S that sold millions of units and was the company’s flagship phone in 2010.

I really respect how great (and big) the Galaxy S community is and their continuous efforts to solve for free what Samsung is being paid by the customers to solve, but in the end what I really want is a brand to take full responsibility for the things they have put out in the market!

I’m writing my final thoughts on this because recently I’ve met someone that was looking to buy a used smartphone and the Galaxy S was fortunately one of the models he was interested in: this sounded to me as a sign it was time to let my phone go and I didn’t miss the opportunity to sell it: problem solved!

Where is the Daily Briefing app / widget?

October 8, 2011

One of the most publicized feature of the Galaxy S smartphone was the Daily Briefing application (and widget). It was a Samsung exclusive pre-installed app that allowed the Galaxy users to quickly glance at the weather, the news, the stock market and at the calendar.

Most pre-installed software manufacturers put in their devices are usually not very useful, but in this case it was a pretty nice piece of code that actually served a purpose. And apparently a lot of people used it.

Vodafone, in the Gingerbread firmware update to the i9000 Galaxy S, simply removed the app / widget. Without a warning, or an explanation, Vodafone just made it disappear, one of the key features of the phone, the main Samsung app that appeared in most Samsung pictures of the model as you can see below.

Since it’s a Samsung exclusive app, if the user wants Daily Briefing back, he can’t find and install it from the Android Market and I can’t find it in the Samsung Apps store either, so the user will have to find an alternative on their own.

Branded Android smartphones

September 17, 2011

Some (or probably most) carriers around the world sell their Android devices with custom firmwares that usually bring the operator’s applications and branded theme. This allows the customer to use some of the carrier specific services.

The problem is that most of the times branding:

– implies the phone is always running some background process or services which always use some RAM and CPU cycles even when you don’t use or need it, as you can see below

– is frequently not very well implemented, so the phone is usually slower or unstable as you can see in the next picture

In case the customer doesn’t want to use the carrier services, or want to free some memory, or save the CPU some unnecessary work, in most cases he just can’t simply uninstall the software since that possibility is most of the times disabled!

If carrier’s want to put their own software in the devices it’s their choice to do that, but I believe everyone would be happier with, at least, an uninstall option to remove some of the bloatware they usually end up putting in the phones. Besides that, they can always provide the customer with the option to install the operator’s software from the Android Market. I think that would serve better everyone’s interest!

Android OS battery drain bug

September 3, 2011

About a month ago, several Vodafone customers across Europe got the Gingerbread version of Android on the Samsung i9000 Galaxy S.

It took a while to get this update because the Android update process works like this:

– Google releases a new Android version and make it available to the manufacturers

– Manufacturers like Samsung take their time to adapt the OS to their specific model and send it to the carriers

– Carriers like Vodafone take their time to add some of their own customizations and test it thoroughly before allowing it to be available to the customers

One might think that with all those eyes at different companies looking and testing the firmware, the final release would be solid as a rock and pretty much bug free.

The Galaxy S was last year’s Samsung flagship smartphone and sold millions of units all over the world, the manufacturer claims the phone can remain in standby mode for up to 750 hours in a 2G network and up to 625 hours in 3G networks. Of course nobody expects it to actually be even close to those very optimistic numbers but with the latest Gingerbread update I got a feeling things got worst.

During the holidays I decided to see what was happening: I took the phone off the charger in the middle of the morning and didn’t use it at all during the day, except for a very short phone call (less than 1 minute) and to take some screenshots of the battery usage menu to see how things were going:

As you can see in the first screenshot, even though WiFi, GPS and Mobile Data are all disabled, in just 3 hours and a half there is a significant drop in the battery apparently caused by the Android OS process.

One hour later the Android OS process is still the most significant battery consuming process, though there is this weird process called “orientationd” I suspect might also be related to the battery drain.

As you can see above I received a short phone call, and the corresponding entry appears as responsible for 1% of the total power consumption.

9 hours and 18 minutes have passed and although the percentage is decreasing, the Android OS process is still the main reason of this excessive power consumption. By this time there is less than half of the battery capacity remaining.

Finally, after 15 hours and a half the battery is dead and the phone eventually shutdown by itself.

If I was using the phone in a normal workday, sending and receiving text messages, making phone calls, using the WiFi or playing some game, the battery wouldn’t last for half of the day, which is really bad if you consider the supposed 750 hours of standby Samsung announces.

I searched around for this bug and saw this Android OS battery drain bug reported in several internet forums. Apparently it exists at least in the 2.3.3 version of Android for the Galaxy S, though there are some similar problems reported in other Android phone models and manufacturers but I can only assure the existence of the bug in the Vodafone branded Galaxy S with 2.3.3 firmware.

I’m amazed how neither Samsung nor Vodafone noticed this bug in their extensive tests and despite taking a lot of time before releasing the updates they are still released with some serious problems like this!

I’m also surprised how the media didn’t notice a serious bug like this but sometimes report on other minor problems affecting other phones or gadgets.