Posts Tagged ‘cell phone’

A Long Overdue Thunderbolt Review-type-thing

June 23rd, 2011

Two months ago I said I would write something about the Thunderbolt..it was only supposed to be about two weeks but life happens I suppose.  Honestly, I wasn’t expecting to cave-in and buy the thing but I found a coupon for $50 off and thought, “well, this might be good!”  I bought the phone only a few weeks after I decided to root my original DROID (which from now on will be referred to as OG, Original Gangsta) and install cyanogenmod 7.  Being the happy owner of one of the best Android phones to ever come out I had high hopes for what was supposed to be Verizon’s new super flagship phone as well as the first phone to use their 4G LTE network.  What I got from it was a mixed set of feelings that make me miss my OG sometimes.

Let me get this out of the way first, I like this phone a lot.  It’s a great device, it’s fast, it’s sexy, it’s big..but it’s not perfect…far from it, and most of the reason is due to the crap software that is on it…let me explain.

The UI and Software

My OG ran stock vanilla Android (what devs call AOSP: Android Open Source Project). This basically means it’s the bare Android OS with no added UI tweaks and no added bloatware crap (with exception to some Verizon apps).  This is the best way to run Android for the most part because it’s not using the CPU or RAM to run some fancy/ugly user interface over top of it, it’s not going to have built-in apps syncing crap in the background, it’s just plain ol’ vanilla ice cream (and I like vanilla ice cream).  And it works!  It doesn’t waste CPU (meaning it’s faster) and it doesn’t background sync unnecessary apps constantly (meaning battery savings) unless you install them.  But of course, HTC and other companies want to change it to suit their own phones and needs.

Stock Android Screenshot from N1

This is a Screenshot from a Nexus 1 running AOSP 2.2

Now, the Thunderbolt (as with many HTC phones) doesn’t do AOSP Android, they use Sense UI, it’s their own user interface which they designed to put on mobile devices for a “sleek” and “unified” look.

HTC Sense UI Screenshot

This is Sense UI

While some people like the look (which I don’t think is terrible mind you) and the feel, I don’t like it, I hate it.  There are several reasons I hate it actually the first and most important being that it’s clunky and slow to respond VERY often; it feels like my OG before I rooted it…this shouldn’t happen on a 1Ghz phone with 700+MB or RAM.  So what I did to “fix” this was install ADW.Launcher and use that as my home app.  It’s faster, and it looks and feels more like a stock phone now.  Second, they package a whole mess of crap in with it; they have a “friendsteam” which gathers your Twitter and Facebook and whatnot into a widget on your screen and displays it and updates it for you; a weather widget (which is actually nice, but i should have a choice to remove it);  and their own Facebook and Twitter syncing built in.  This is stuff I’d like to install on my own and not have running in the background constantly asking me to log in and sync; if I want Twitter and FB, let me install them myself.  They also use their own MMS app which is very slow compared to the AOSP app.

 

You might be thinking, “man, this is cool that it’s all built-in, why are you hating on this?”  Because I like to be able to choose what to have installed on my device.  Because of these built in apps (which mind you, aren’t really apps, they’re more like utilities) I have two Facebook apps, and two Twitter apps and it’s kinda dumb to waste space on stuff like that.  I also find it annoying that they START UP WITH THE DEVICE…even when I DON’T USE THEM.  What a waste of CPU and battery.  Once CM7 is released for the phone (not Alpha-builds) that will be my savior.  Verizon is also guilty of bundling tons of bloatware with this device.  When I received the phone it was PACKED with tons and tons of useless crap..and you can’t remove this stuff!  I’ve written about carriers loading bloatware onto phones before, this shit needs to stop with Android.

The Battery

Smartphones are notorious for having crummy batteries.  My OG was actually pretty great before the last few months of using it.  I used to get over a day with it and I was happy.  When deciding on a new phone every review I read had the same complaint with regard to the Thunderbolt: The battery is terrible.  Now, I’m never far from a power source, and I have around 4 or 5 micro-USB chargers from my older devices and ones that I found around the lab, so this wasn’t too much of an issue for me.  My first day on the phone I got through the entire day of heavy use and texting without it dying, it got to about 5% by midnight (from 8am or so).  The second day, same thing.  On the third day that’s when it ended.  Without using it too much I made it to about 2pm before it started dying on me, I charged it and it was low again by 9pm.  Now I see what the complaints were about.  I tried using task killers to kill unwanted tasks, I synced data less, I lowered brightness, nothing helped.  I read around online and found the best way to get more mileage was to turn off 4G.  I figured, I don’t need 4G all the time, so it’s fine, if I get more battery time out of it this is what needs to be done.  After turning off 4G, I get through the day again.  A few weeks ago an update was released that helped the 4G radio consume less power, so since then I’ve actually been able to leave 4G on and get through most of my day with it…so good on them for fixing that.

The Hardware Itself

This is where the phone really does come out.  This phone has some weight to it (it’s heavier than my OG which was a brick) and it’s got that big bright screen.  The screen makes it so easy to read things on and to watch videos, the rubberized back makes it easy to hold, the weight makes it feel like you’re not going to crush it in your hands.  It is a nice, solid phone.  It’s also fast when you need it to be.  Playing games, running apps, downloading, it just runs fast (especially with ADW.Launcher).  Of course Verizon’s network helps too, I get 4G everywhere in NYC, and the 4G speeds are really good (EVEN INDOORS! Take that WiMax!).  I have plenty of space on the 32GB MicroSD card they give you and on the internal storage (8GB but only about 2.5 are available).  The only complaints I have about the hardware and design: no dedicated camera button, I really miss this, but it’s fairly minor; the bluetooth volume is super low, I’ve read that it only does it with some headsets but my Jabra is so low I cannot use it; and the GPS takes forever to lock on, sometimes 5-10 minutes.  Now, some of this is probably software-based so a fix may be in line (apparently there might be an update in the next month or so to address some of these issues as well as the random reboots caused by the last update) but until that fix is out these problems will remain.

Overall

So to sum this up in a few lines (TL;DR); I really like this phone a lot, it is a great phone by design.  The 1Ghz Snapdragon processor and the large amount of RAM really make this phone fly with apps and games and with Verizon’s 4G it really is a speedy phone in all faces.  However, the phone has many kinks due to some bad software that comes bundled with it and a broken update from HTC.  Most of it’s issues are solely based on the software so hopefully we will see fixes for them in the future.

 

That didn’t last as long as I was expecting…

April 18th, 2011

I decided to upgrade to the Thunderbolt after all.  Main reason: I got $50 off from a web coupon.  I’m going to write a little bit about it after I’ve used it a bit more.

Some first impressions: This thing is super fast, it’s got a nice feeling to it (not as solid as my DROID but still pretty well built), and the screen is really really nice.  The battery life isn’t as bad as everyone says it it…I got a full day out of it with fairly heavy use…we’ll see if that continues though.  I hate SenseUI…so I replaced it with ADW Launcher right away and I’m waiting for CyanogenMod to come out for it (it’s currently being worked on).  So expect some sort of review in the coming days/weeks…

Getting more from my Original DROID (Part 2: Restoring and Troubleshooting)

April 13th, 2011

In part 1 I described (in little detail) how I rooted my phone and installed CyanogenMod 7 on it to get some more mileage out of it until I upgrade to a newer device this year.  But of course every upgrade and every hack isn’t without it’s issues and every hack isn’t perfect at all.  Cyanogen never claims to be 100% trouble-free, and every users’ experience will vary depending on device and applications installed; after all, it is technically a hack made by third-party developers…and no developer is perfect. The methods for flashing are also different for each user.

I installed CM7 when it was at RC1 for the DROID (still buggy, but still good for everyday use) and I originally flashed my phone by doing a factory reset of the device (removes everything) and then installing the ROM. This gave me an endless boot screen.  What I had to do to fix this was not only do a factory reset, but wipe the cache partition AND the Dalvik cache partition.  This was easy with the ClockworkMod and it was also nearly 100% risk free since I had a complete Nandroid backup.  After wiping the two it booted successfully!

I noticed that in Android 2.3 Google will restore all of your previously purchased and downloaded apps if you want it to automatically on a new device (only the app itself, not the data..like game save data).  This is great, but I already decided to use MyBackup Root for this, mainly because I wanted to have my stuff there with all of the data.  So i just told the phone not to download everything and I’ll just restore everything from my backup.  What this left me with was broken installed apps with no way to update them because the Market links were all hosed.  This sucked, now what was I supposed to do?  I decided to flash again and allow Google to push the apps to my phone.  This process took some time but everything was downloaded for the most part; unfortunately, I didn’t have my app data, so all of my game data and all of my settings were gone…I check MyBackup and sure enough I was able to restore data only!  I did that and bingo, everything worked again with all of my old data!  A few apps needed to be reinstalled or needed their data wiped (Google maps and Facebook I think) but for the most part everything worked just as it was supposed to.

Choose which to restore? Yay!

So now that I had my apps on my phone, I was nearing happiness with my hacked DROID.  I say nearing because I was still having many issues with other things.  I won’t go into every little one but I will talk about the two that almost made me decide to go back to stock.

LED Notifications

The one thing I love about Android phones is the LED notifications.  A simple little LED in the corner of my phone blinks different colors for certain things (texts, emails, etc) so I don’t need to turn the screen on, or unlock my phone to see what I missed or see what that beep was from…I can just look at the color of the LED.  Funny thing happened after installing, it stopped working.  I would look down and nothing would be blinking but when I unlocked my phone I’d notice an e-mail that I missed!  What was going on here?  I looked in the settings and found that CM has basically rewritten the notification system and you can customize colors and blink rate from it if you so desired, but instead it broke the damn thing.  This wouldn’t fly with me, I was about to go back to stock because one of my favorite features was broken…then I found the forums.  I searched the issue on the forums and found a lot of people with the same issue, on different phones even!  Reading through many of the posts they all usually came around to the same solution, un-check everything in the LED settings then check them again then hit “Reset all LED notifications” and reboot. And it worked!  I had my LED back and working and now it was even better because I can change the settings for every program and even change the colors and blink rate for them, pretty neat.

Change color and rate for LED notifications

Missing Messages

Now that my LED notifications worked I was happy that I could look down and see if I missed any emails or (more importantly) text messages…but strangely I felt that I was receiving less messages.  I went an entire day without a text message, which is very odd for me actually.  I looked at my phone, no blinking LED, I unlocked the phone, no notification in the menu, I opened the messaging app and boom, new texts, some as old as a day!  What the hell was going on with this?  I’m missing text messages now?  This used to happen with my EnV Touch, never my DROID!  I tried resetting my notifications for the app, and it would work for a while after I opened the app.  I figured, okay, it’s fixed, but then it would stop later on in the day.  I was getting very frustrated with this now and was again thinking about going back to stock.  I hit the forums again and found one post about the issue with one simple solution:

The solution! Check that box!

Once I checked that, never missed another message.  It locks the message app in the memory so it’s always running.  Sure it uses up memory, but my messages are more important to me than the amount of apps I can run at one time.

Side note: But why does the DROID do this with CM7?  The DROID has 256MB RAM, this was a lot when the phone came out and with 2.1 it was fine.  Once 2.2 was released memory was becoming a problem for the phone.  The phone had trouble even keeping the Home app in memory; if you ran a program that was memory hungry and went back to the home screen you’d have to wait for it to redraw because Android’s memory management would kill it.  So in CM7 you can see the two check boxes for home and messaging, this stoped the redrawing(relaunching) and the missing messages…but it took some memory away of course which means you can only do so much multitasking before apps start getting killed.  Android 2.3.3 uses more memory, and the DROID just doesn’t have that much…so CM7 also allows asset purging to free up RAM as well as compucache (memory compression).  These use a little CPU but allow you to multitask fairly well;  it’s nowhere near as good as other newer phones, but it works.

There were some other small odds and ends that I had fixed by tweaking settings and installing updates but I thought that these two were really the most damming for me.  I managed to fix them with help from other nerds at the CyanogenMod Forums who were running into similar issues and there are some I managed to fix by trial and error.  Now, he ROM still has it’s occasional reboots and hiccups (not very often) and they usually happen with two programs; Google Maps and the Camera app, but these crashes happen less and less with each update.

CM7 is now out of RC and was released as Gold…but not for the DROID yet.  It still is very much a work in progress, but the progress is going very quickly, and I really like the direction it’s heading.  They’ve managed to give DROID users Android 2.3 even after Motorola decided it “wouldn’t work” on the phone.  Well, it is working (for the most part) and I’m fairly happy with it.  It has really allowed me to use my phone a bit longer than I was expecting.  I’m probably going to wait until August to upgrade my phone instead of going for the Thunderbolt, but time may change that.  What I do know is that my phone still works well and I will get more time out of it because of the ROMS.

Getting more from my Original DROID (Part 1:Rooting and CM7)

April 11th, 2011

I love my DROID, I have since I got it over a year ago.  But in a year, a lot can happen with technology of course.  My phone was originally equipped with Android 2.1 (the first phone to have it actually) and had an ARM 600MHz processor (underclocked to 550 for battery life), and 256MB RAM.  It was fast, really fast…and it took a while for phones to be that fast…but it didn’t last long.  Soon after the DROID came out every new phone that came out just got faster and faster very quickly..I mean, that’s what technology does, right?  But the DROID looked slow very quickly.

So when Froyo (Android 2.2) came out the DROID got it down the line and that’s when the DROID started to show it’s age; extremely slow…a big drop in performance.  So I decided to root it to get a little more millage out of it before my upgrade.  Mind you, I was waiting for the Thunderbolt to come out to replace it…but decided against upgrading for the time…another story I suppose.  I decided to use SuperOneClick to root my phone, and damn it was simple.  Literally one click and it was done…but what can I do with this root?  Well, first thing was overclocking to see if I can get some more speed.  I overclocked it to 800MHz and really didn’t notice much of a difference besides the fact that I could now have a wireless hot-spot…oh and I could take screen shots now (why doesn’t Android have this functionality built in? Seriously!).

Android Screen shot

Hey look, I need to ROOT to take a screen shot!

So I decided to take it a step further.  My buddy was telling me about CyanogenMod and how he loved it on his MyTouch and basically brought life back into it.  So I said “Why the hell not?”  Not only does it add a lot of functionality, it will give me Android 2.3.3 (Gingerbread)…something the original DROIDs won’t ever see normally.  I backed-up my apps and text messages phone using MyBackup Root then flashed my recovery ROM to ClockworkMod which allows me to install firmware from the SD card and allows me to backup my entire phone to an image just in case anything goes wrong.  After the backup with MyBackup Root I rebooted into recovery mode and backed-up the entire phone using the Nandroid backup (in the recovery) then started to flash CyanogenMod 7 on my phone..this meant I had to do a complete wipe of the phone which is always scary but with the backup I should be cool!

Wiped the phone, flashed the ROM, and booted the phone. It worked! I had the Release Candidate (at the time it was RC1) of CyanogenMod 7 on my phone!

I had some issues with CM7 at first and some issues with getting my apps back (which I’ll talk about in Part 2) but after some initial bumps I was up running as smooth as I could be on a release candidate.  I had some reboots and some programs would crash but reinstalling them from scratch helped for the most part.

After a few updates it became more and more stable.  I am now running RC4 with a new ultra-low voltage kernel (which allows me to overclock to 1GHz and uses less battery power than the stock kernel). which gives me good battery life, pretty good performance, and all around a pretty good experience.

Android 2.3.3 and 1.1GHz!

So if you’re looking to get some more time from your old DROID this seems like a great way to do it.  It’s not up there with the new phones, but it does give your device a nice little jolt until you decide to retire it.

In Part 2 I’ll talk about installing all of the apps from backup and troubleshooting the many issues I had with memory issues and how they were resolved.

Another Stupid TUAW post: “Why I’m staying with AT&T” and a moron too!

January 12th, 2011

I always enjoy reading tech blogs the day after a big announcement.  Not because I want to see coverage about the previous days event but because I I love seeing all of the weeping and moaning about what “failed” with said announcement (even though all of the expectations were rumors and speculation) and I like seeing the people who were so gung-ho about the event suddenly drop down and go back to their old crap.  I’ve seen the posts about the “failure” of the Verizon iPhone, and now I’m seeing the posts about “sticking with AT&T.”  Again, that’s totally fine of course; don’t switch companies for a single phone, but if you have various complaints and problems, isn’t that enough to switch?

This post by Mel Martin on TUAW, The Unofficial Apple Weblog, really confused the hell out of me.  I saw the title “Why I’m Staying with AT&T” and was expecting to see things like “I haven’t had the issues everyone talks about,” or “I like their customer service!” No, what I found was a long list of complaints with some reasons why he’s sticking with AT&T through all of his problems.  Let me break this down a bit more.

I admit, AT&T has been sloppy and at times downright incompetent. Who can forget the massive foul up when the first iPhone came out and literally millions of customers couldn’t get AT&T servers to sign them up? It happened again with the 3G iPhone and the iPhone 4.
There’s the really nasty rate of dropped calls, lousy or inconsistent reception, and how AT&T always seemed to put endless roadblocks before developers who wanted to use the iPhone in the way it was designed. Months of delays on the SlingPlayer app, no Wi-FI tethering, and more delays delivering a 3G tethering plan that was overpriced and forced you to give up your unlimited data plan. Oh yes, AT&T dropped unlimited data so it could start enabling some of those features that might force you to go over AT&T’s newly imposed limits. Nice. The list goes on and on.

Let’s see.  That is a list of eleven complains or problems faced on AT&T with the iPhone, not to mention that he put “the list goes on and on” at the very end, meaning there are more complaints!  Any normal, competent person would have tossed their provider out on their ass a long time ago with this list, I know I would have, but that’s because I actually like being able to make and receive calls and texts and data anywhere I like.  This is a VERY bad list of complaints for any cell service and sticking with someone this bad is just insane.

Now, with this list of eleven you figured there would be a much longer list of good reasons he’s straying with AT&T, right? Let’s take a look now, one by one, and try to keep count!

Big Fee to drop my AT&T plan. Way too much. $325 for those who purchased after June 1, 2010, and $10 off of that for every month of completed contract.

This is a good reason! Why would you want to pay a fee to drop your cell company only to have to pay another $200 to buy a new phone which you already own!  Let’s hope a trend of smart follows.

Coverage. We all know that AT&T coverage is generally worse than Verizon, but AT&T ponied up and let me have a MicroCell device for free. It solves the ‘no coverage at home’ problem, and after some initial growing pains it works well

There goes the smart…out the window.  This is where I start getting very confused.  You’re claiming you want to stay with AT&T because of their coverage but you say in the very next sentence that they generally have worse coverage than Verizon?  And because you had such bad service they gave you a personal 3g device to make calls in your home?  So you’re sticking with AT&T because they have bad coverage but solved your home service issue?  Why bother have a cell phone then? Isn’t the point of a MOBILE PHONE to be able to use it…mobile-ly?

Competition is good. I expect AT&T to step up and compete, not because they want to, but because they have to. Maybe there will be a reinstatement of unlimited data plans. Maybe FaceTime will finally work on 3G.

Another stupid point.  While I agree that because Verizon now has an iPhone that AT&T will have to step it up, AT&T has always had this problem and still haven’t resolved it for the most part.  Why would they all of a sudden just start to “compete” now?  Haven’t they been competing in the past, or were they just  riding the dollar waves of the Apple fanboys turning a blind eye to their crappy service just to have an iPhone?  Not to mention that you’re basing this on speculation that “maybe” something will happen.  I don’t know about you but when I’m paying for something now I want it to work now, not “maybe” in the future.

Simultaneous voice and data are huge. I often fire off an email or web link when I’m on the phone. Going to Verizon means I kiss all that goodbye.

Okay, a valid reason to stay on AT&T.  CDMA cannot do voice and data simultaneously and if that’s a big issue for you then you should have no questions to ask, just don’t switch. That’s two instances of sanity.

Speed. At least here in Arizona, I get really fast data on the iPhone. Yes, the Verizon voice network is more reliable, but in local side by side tests on the data side, my AT&T phone really is faster than a Verizon smartphone.

Speed is another thing that I have trouble viewing as a major issue to switch cell carries.  For one, the difference in speed isn’t really that much, unless you’re using 4G on a device.  Now, I would say that this is another good reason if you really need that speed, except for the fact that you point out AT&T’s flaw right in the next statement.  You say AT&T is faster than Verizon (true) but Verizon is more reliable.  Tell me, what’s more important to you: getting something done quickly while praying that you keep a steady connection, or getting something done a little slower, but knowing it’ll get done because you have a strong, reliable connection?  If you say anything other than the latter, you’re a moron.

New iPhones. There will likely be a new iPhone this summer. I expect it will be a lot easier to talk AT&T into an upgrade than Verizon.

Guess what, you’re probably right! It really doesn’t take a genius to figure out Apple’s release schedule. But I also think that if someone wanted to upgrade early they will pony up the dough.  If they switched to Verizon and paid the fees they won’t have an issue upgrading their device.  Not to mention that so many people will probably wait for a new device before switching to Verizon anyway.

And that’s the end of his list. Five reasons he’s staying, five. And only two of them are valid.

Explain that to me please: 11 complaints vs. 5 reasons (of which only 2 of them are valid in any way).  How can someone who apparently knows something about technology see this as a good decision?  If I had half the list of complaints this guy has, I’d drop Verizon like a bad habit.  I have maybe two complaints about Verizon and neither of them has anything to do with service or call quality (mainly cost and devices).  His entire post seems to me like he’s sucking the AT&T pee pee all the way home while getting his free cell service too.

I should also point out that I have called TUAW out on a very misleading title in one of their other posts and they responded by sending me tweets to rumored stories about the iPhone 4G on Verizon.  It seems they do not understand the concept of a rumor.  Over there they seem to be a bunch of AT&T and Apple fanboys…and dealing with fanboys is a hard thing to do.

Sound off in the comments if you have anything to say!

Update note: I found this post on a blog I frequent (The Adventures of Systems Boy!) and I was so happy to read it.  Three sentences and it’s already the best post on the Verizon iPhone. Thank you, Systems Boy!