Samsung Droid Charge Software Review (Video)
The Samsung Droid Charge ships with Android 2.2.1, but will probably get Android 2.3 Gingerbread in an update later this year.
Alongside Froyo, Samsung has also integrated the TouchWiz 3.0 user interface. Even though TouchWiz 3.0 debuted last year on the Galaxy S line the user interface is still simple enough for anyone to customize while being graphically pleasing. The similarities between the stock Android UI, which many consumers are accustomed to, and TouchWiz 3.0 will most likely not distract from the usability of Android. With TouchWiz 3.0 come a few widgets that help to unify status updates to social networks, get important information about finances or news, and change settings from the Droid Charge’s seven home-screens quickly. Some other apps that come standard on Android 2.2 have been re-skinned to form a cohesive look to keep them matching the other TouchWiz 3.0 alterations. With future updates the Droid Charge might also see the TouchWiz 4.0 UI that is integrated into Samsung’s flagship device for 2011, the Galaxy S II, if the hardware is able to handle it.
Verizon, like all other cellular providers, have added their own software to the mix. Of course there are some good applications that will keep track of usage, allow contacts to be backed up to Verizon’s Backup Assistant server, and display the context of voicemails visually. But with the good must also come the bad, and there is quite a bit of it. Most of the apps that come preloaded on the Droid Charge are trials, which cannot be removed without rooting. They include apps like BitBop, Blockbuster, City ID, Lets Golf 2, Mobile IM, Rhapsody, Rock Band, Slacker Radio, and much more. Some users may find these apps desirable and others, particularly the tech savvy shopper, will find them obnoxious.
For the benchmark testing the Droid Charge preformed fairly mediocre for such a pricey Android. The speeds of the Quadrant Standard were hovering around 1000. LinPack for Android was calculating an average of 12.1 MFLOPS in 6.9 seconds. Smartbench 2011 was also scoring below par for an Android 2.2.1 device at about 900.