The Update

To update your Hero, go to Settings->About phone->System updates->Firmware update.

The update took about 10 minutes to install, weighed 3.7MB or so, and rebooted the phone twice – once to install and once to reboot after the installation, so make sure you don't need to make any important phone calls during that time.

After the update, I immediately noticed the broken application icons (issue #4 on my bug list) fixed. The phone seems is definitely quite a bit snappier, which I hope points in the direction of some fixes in the battery and lag department (issues #1 and #2).

Since there don't seem to be any official details out from HTC or Sprint at the moment (I found out about the update by doing a random Google search and arriving at a random Facebook post), I cannot see the final bug fix and feature list, but here's what I managed to gather so far from my own observations and online [1] [2]:

What's New

Fixes

• broken app icons are fixed. This issue was also known as the boot caching issue
• broken app names are somewhat fixed. Some of mine weren't but I reinstalled them and so far they display correctly
• the major battery draining 100% awake SMS and letting the phone go to sleep after boot bugs are fixed. I've gone ahead and uninstalled HandcentSMS to see if my visual voicemail notifications will come back (they seemed to have gone away after I switched to Handcent)
• not receiving SMS when low on space is fixed
• memory leak related to bluetooth is fixed
• dialer app using too much CPU bug is fixed
• daylight savings time calendar issue is fixed
• the stereo headphone issue is fixed

Improvements

• the phone is a lot snappier – the lag is pretty much gone in a lot of cases but it's still there in others, especially in the Phone app and the browser. For example, I killed the browser and started it again – it took 20 seconds before google.com was loaded, 10 of which I spent staring at an almost completely white screen
  I have a feeling it is due to fixing something with the cleaning up of the old uninstalled apps. My theory is that the Hero didn't uninstall the apps properly, perhaps leaving their cache behind, thus slowing down more and more as I tried out more and more apps
• Update: I just charged the battery and I think the battery charged a lot faster than before, which is a really good sign
• loading of app lists seems to be a lot faster. By that I mean any time the phone shows a list of installed applications, it seems to show up a lot faster than before (Add shortcut, Manage, etc)
• camera quality is improved

New Features

• app search – if you push the search button from anywhere inside the Market app, it now pops up the app search dialog rather than the regular google search
• there are 2 new icons during a phone call: mute and speaker. I took a photo of this, which you can see below
• the green Android dude looks more 3D-ish now – a minor but nice UI change

Problems

• a lot of users are reporting that some of their apps, including paid ones, have gone missing
• the haptic feedback (vibrate on press) in the Phone app is now permanently on, even though I turned it off in the keyboard settings. I am fairly sure it's either a bug or a new "feature" that we didn't want, as it doesn't respect phone-wide settings

Miscellaneous Notes

• the update did not fix the all-day event 1 day too early notification problem
• I did not find an update for the voicemail app that some people mentioned (mine is at v5.0.0.32)
• the "linked program is no longer installed on your phone" problem that I'm having with my Twidroid shortcut every time I update it is still there (it goes away after phone reboot)

Overall, I'm very happy that Sprint and HTC are coming through. I was really afraid they would wait for the next big thing (Android "Eclair" 2.0) instead of releasing the necessary bug fixes but, thankfully, that didn't happen.

What else did you notice with the new upgrade that I missed? Is anything broken?

• The Not So Good, The Bad, And The Ugly: My List Of 20+ Problems With HTC Hero
• HTC Hero Coming To Sprint October 11th! $179.99, Powerful, And Sexy. Here Is Why You Need To Own It
• How I Doubled My Android Phone's (HTC Hero) Battery Life or Just How Much Email Polling Affects Your Battery
• How To Fix Redrawing Problems In Your VNC
• My New Android Phone Wants Me To Do WHAT?

HTC, first of all, what. the. fuck. The idea of a more attractive UI was great, by all means, but did it really have to come at the expense of lagging down the whole phone? And by that I mean LAGGING. I would much rather have no added pwetty fluff than to literally be amazed when using my Garmin GPS because its UI is so responsive (until I got the Hero, this thought would have never crossed my mind).

Why is it that I have to miss phone calls because the Hero only gives me one or two rings before they go to voicemail? And half the time, right as I pull down the message on the screen that tells me that's what I have to do to answer the call, it doesn't pick up. Instead, I'm staring at a missed call.

Before I go on, I'd like to clarify that I'm still enjoying the Hero, mostly for making me feel a lot more connected on the go. However, the experience could have been a lot more enjoyable had HTC done a better job on the polish of the Hero core.

Some of these issues might be caused by Android, some might be caused by the fact that even though Android 2.0 has been available for a few weeks and 1.6 for a few months, the Hero is still running 1.5 – all thanks to the Sense UI.

But let me organize my thoughts in a nice numbered list. Everyone likes those, right? Be prepared – when a device affects me so much, I've got a lot to say.

My List Of Problems

1. Lag

This phone lags. At least the Sprint version of it, running Sense UI. And by lags, I mean most of the time it's worse than the Pre. Yeah, I went there. If you love lag, you will adore the Hero.

I'm not going to argue about rooting it or not using Sense. No. This is what HTC is making thousands of consumers use – and most of them won't ever consider touching the underlying OS. If you have an underpowered processor, HTC, don't you think the best thing you could have done is to try to compensate for it by making things faster instead of bloating it with garbage? Sprint, you didn't help either with your force-fed Nascar and NFL Mobile Live that we can't remove.

The browser lag is just beyond bearable. 16 seconds on average to load my plain Google.com homepage (not even iGoogle – just google.com). That's 10 seconds of staring at a blank screen, 4 more of staring at "getting sign-in details" and 4 more of loading the webpage. This is compared to 4 seconds on the Motorola Droid, side by side.

The keyboard lags. Often. Both typing and flipping.

Flash (the Adobe one) is cool but its performance on the Hero is pretty much unusable most of the time.

The lag is everywhere but this one takes the cake – the lag operating the dialer and the phone in general. Because each button press is unpredictable and can take between 0.5 and 5 seconds, there is no way to tell if the screen just didn't register the click or if it's just lagging behind. Thanks to this, I've dialed wrong numbers, hung up, and performed wrong functions multiple times.

My favorite is that it takes about 2-3 seconds for the last dialed number to show up in the recent numbers list after I finish the call, which means it then pushes all of the recent numbers down by one. So if I click a number I want to dial during that period of time, after the lag settles I will find that I actually just pressed a number above the one I wanted.

This list goes on.

2. Bad Battery Life

I thought the 1500mAh battery would give me plenty of juice. How foolish of me.

Between such battery draining bugs as letting your phone go to sleep when first turning it on, simply sending an SMS message, and using the Hero for email a few times a day, I'm left with 0-15% battery life by 10pm (even after applying known fixes).

In the morning, between the time I wake up and the time I get in the car, my battery would sometimes run down to 85%. Sometimes, however, it would still be at 98%, without doing anything differently. Does that make sense to you?

3. Long Bootup Time

There's nothing better than staring at the bootup screen for good 3-4 minutes before the phone becomes usable. If you think the Pre load time is bad, check out the Hero for some added fun.

Fine – it loads a pretty complex Linux based OS, I get it. But damn – it sure takes its time doing so.

Well, at least it doesn't say "Droid" in a robotic voice.

4. Application Chaos

Some applications' names change to their Java versions (such as com.p1.chompsms). Without me touching or updating them – it just happens over time. Some examples include Unit Converter (FCs upon start), Astro File Manager, Estos, ChompSMS, and Voice Caller ID.

Some applications' icons are randomly changed and mutilated (for example, Remember The Milk and Flixster).

Some applications stop working and start force closing (for example, Flixster, WP To Go, Unit Converter).

Some applications say "shortcut is no longer available" when clicked from the home screen or the All Programs list (for example, Twidroid). This seems to sometimes go away after a restart but surely comes back upon the next program update.

Not sure who to blame for all these but it seems like non-Hero owners don't seem to be experiencing such issues.

And the solution? "Without rooting, the only workaround for the issue is to uninstall the app and reinstall it. Still, after rebooting, you may have the same issues. Again, a reinstall is the only fix," suggests a post on AndroidForums.

Someone on the XDA-Developers forums provides more details – this is, apparently, due to a mismanaged boot cache.

5. Voicemail/SMS Problems

Problem – "after Internal Memory reaches a certain low level of free space (one user heard around around 40MB free from HTC Support), you may stop receiving SMS messages and voicemail. No amount of clearing space will allow messages to resume" – description credit AndroidForums.

Solution? "The best method of prevention currently is to ensure adequate memory is available on the device to prevent the flag from being set" – SprintUsers forum.

On a related note, the following bug has also been reported: "Over time, Internal Memory free space dwindles and no amount of clearing apps frees the space. This will also cause the above issue of SMS & Voicemail messages not being received once a critical amount of free space is reached".

I stopped getting my voicemail notifications a long time ago. Texts are still getting through somehow but they should definitely be afraid of stepping on these landmines any day now.

There are 3 ways to get your voicemail – are you kidding me? You can use the visual voicemail app (mine doesn't work anymore), you can dial your phone number (which is the same as pressing on the envelope or holding the 1 key), or you can dial some 408-970-0000 number (which seems to be for voice SMS but yet handles my voicemail). Did you just hack voice SMS to do visual voicemail, HTC and Sprint? This is a job not so well done.

6. The Keyboard

Let me say this – the keyboard on the Hero kind of sucks. It is very inaccurate, even after calibration, and doesn't guess letters nearly as well as the iPhone does.

To be fair, the Hero shines at the spelling correction. I can type 5 letters wrong in a single word, and the Hero will still suggest the right correction most of the time. My complaint here is that it doesn't detect missed spaces at all, so 2 words run on each other would not be recognized and corrected.

Now, the keyboard flip – it is uncomfortably laggy (see point #1 again). 2-5 seconds per flip is not good enough.

7. Calendar Notifications Are Broken

Sometimes I'm alerted about a calendar event a day early.

Sometimes an hour early (that's what happened after the daylight savings time shift).

Some users reported that their Hero shifted to daylight savings a week early.

How in the world does this even get through QA, HTC?

No remind me on time option? A 5 minute reminder is as close as I can get. Bleh.

8. GPS Randomly Thinks I'm All Over California

At times, my Google Maps app can no longer lock onto the GPS signal and starts jumping all over the state. Last time it first told me I was in Sacramento (one of the turn directions next to it had a misspelling "Socramento", wtf?), then Santa Rosa, then as I kept driving and pressing My Location, it switched to a random street about a mile away, then dumped me in the ocean.

During this time, the GPS icon kept blinking and didn't stay solid. Also, once it picked up a location, it didn't continue to update it as it should do.

Only a phone restart solves the problem but not for long.

Sometimes, the Sprint GPS can no longer get a lock on my location at all and any route calculations get stuck.

Sometimes, the blinking GPS icon stays on all the time, thus, I'm assuming, draining the crap out of my battery.

9. Usability: No Easy Way To Switch Between Running Apps

Alright, here's where the Pre has everyone beat – the card switching is superior to any app management I've seen. Here I was thinking Android would have a decent way of switching between apps – at least as good as Palm's.

Imagine my surprise when I found out that switching between running apps is completely impractical on Android. You simply can't do it. Ever use Alt-TAB in Windows? Feel like you feel powerless without it? That's how I feel on the Hero.

The closest things I figured out so far are:

• hold the Home button, which brings up a list of 6 most recently used apps. Not only is this longer than I am comfortable with, but it also fails to actually accomplish what I want – and that is switch between running apps
• get a task manager app, such as Advanced Task Manager. This works but this is even slower than the previous method and requires even more clicks
• go back to the home screen/app list and run the program I want again. Chances are, this would summon the sleeping program from the background. Not the best approach either.

Of course, this is not HTC's fault – Android really let me down here (take note from Palm on this one).

10. The 5MP Camera – It Sucks

The Hero has a notoriously bad camera, which doesn't even have a flash (a big drawback). It does a pretty bad job at autofocusing. Both the camera, the camcorder, and the albums take uncomfortably long to load (see point #1 again).

11. Plastic Chrome Trim Cracking And Falling Apart

Out of nowhere a pretty large chunk (1/2 to 3/4 inch) of the plastic chrome trim broke off around the USB plug. I do not seem to be the only one.

I do not expect the case to last much longer either. The "teflon" does feel nice to the touch but it's still plastic.

12. The Phone Unlocks In My Pocket

Did you know the double press on the Menu button unlocks the phone? It's a great feature, isn't it (until it unlocks the phone in your pocket)?

And no, it's not possible to disable it.

13. Out Of Space? No More Apps For You

I ran out of the built-in [measly] space recently. Why? Because it's not possible on the Android (even as of 2.0) to install apps to the SD card, unless you root the phone. This is not an HTC issue and more of an Android limitation but it is definitely part of my Hero experience.

14. Dust Under The Glass?

Many users are reporting that dust is getting under the Hero's screen. Thankfully, I'm not one of those users. For now.

15. Can't Remove Words Added To The Dictionary

The keyboard suggest mechanism in the Hero is great – I can't argue about that. In fact, without it, the Hero would be doomed.

However, sometimes a mistyped word gets added to the internal dictionary and there is no way to get it out of there, without clearing the whole thing. Annoying.

16. No Way To Turn Screen Off During Call

The Hero doesn't have a proximity sensor, which results in a few problems:

• sometimes I press buttons with my face
• sometimes I want to turn off the screen to at least try to prevent my face from doing the above, except there is no way to do so. The reflex to press the Power button which usually turns the screen off results in an immediate end of the current call. I am embarrassed to say how many times I've done this. Oh, and to end the current call when the screen is on, a single press of the Power button is sufficient but two are needed when the screen is off – took me a while to get this right.

17. No Application Access To Bluetooth

I know this is purely an Android 1.5 issue as Android 2.0 has the new bluetooth API but we still can't utilize it because we're stuck at 1.5. Thus, I can't have bluetooth turned on and off on a schedule (via Timeriffic, for example) and, of course, the biggest issue – no bluetooth tethering.

18. High Latency Wireless Network

From what I can tell, there's a much higher latency (the time between a request is sent and a response is on its way) on the Hero than on the Droid. I'm willing to actually accept that it's probably 90% due to Sprint's 3G network vs Verizon's. I never imagined the difference was this vast, however. When I was playing with the Droid, it seemed like I had a device from the future in my hands.

WiFi performance is not great either – in fact, the Market application downloads often hang in the "starting…" mode until I turn WiFi off.

19. Trackball Almost Useless In Text Editing

I like having the trackball, in theory. However, when editing text, it is almost unusable, unless I want to move only a few characters over. If I want to go to the beginning of the line from the middle, it will take ages, as each swipe only moves one character at a time (there is no built-in acceleration).

I'm not alone in this conclusion.

20. Unneeded Junk Keeps Running

I don't need some of the apps that come stock but they insist on running every time I start the phone. Some insist on running all the time, even if I set up Taskiller or Advanced Task Manager to hunt them down. A few good examples are: Peep, IM, Footprints, Gmail (I use the Mail app for gmail), Messages, and Stocks.

Conclusion

The Hero changed the way I do things on the go. The email, calendar, all kinds of syncs, apps – they've all changed my life and I love the Hero for that. I will not be able to go back to a regular phone. I feel too… connected.

There are lots of bugs. Lots. Perhaps Android 2.0 will fix some of them and the rest will be fixed over time. However, I am not sure HTC will be ever able to fix the lag without revamping the Hero's hardware. Although, I also heard that the HTC Droid Eris, which runs the same hardware, is not nearly as laggy. I will have to check it out to confirm.

I apologize in advance for any omissions, inaccuracies, or grammatical errors but it is 3am now as I'm finishing this article. Also, if you find the language harsh – well, that's just me.

Are you happy with your Hero? Are you experiencing any of these problems? Share with me.

• Sprint And HTC Release The First HTC Hero Firmware Update 1.56: Fixes Major Bugs, Adds Small Tweaks
• How I Doubled My Android Phone's (HTC Hero) Battery Life or Just How Much Email Polling Affects Your Battery
• HTC Hero Coming To Sprint October 11th! $179.99, Powerful, And Sexy. Here Is Why You Need To Own It
• My New Android Phone Wants Me To Do WHAT?
• Meet Firefox For Mobile [Video + Feature Highlights + More Info]

Introduction

Dear Skype,

you are great. You have the convenience of a nearby, well, convenience store and the UI that is acceptable to even an Apple fanboy (I'm not one, I'm just saying).

Skype also has a Firefox extension which finds all pieces of text that resemble phone numbers on web pages you are visiting and converts them into clickable Skype buttons . One click and you're dialing the number. The premise is great but the execution… When it comes to your Firefox extension, Skype – you suck. You really suck.

The Problem Bullshit

So what makes me say these mean things? Is it the fact that when simply searching Google for "skype firefox", one finds mostly blog posts and references to major fail? Or is it the fact that MozillaZine's Problematic Extensions page lists Skype as one of the buggiest?

Well, yes. Those are great, aren't they? However, what really prompted me to write this post is my own experience with this extension.

As I am getting into Android development nowadays, I read the Android dev guide quite a lot. Thus, it was no surprise that yesterday I was happily reading the page about Handling UI Events. What was a surprise, however, is that when I clicked over to the View API reference page (in case that page ever changes for documentation reasons, I also saved it here), my Firefox went into a painful agony and exploded in a few minutes.

What the fudgemonkeys? Let's do this again and watch the Process Explorer. 

This is what we call a memory leak – a prime example at that. In the screenshot above, the CPU usage spikes to 100% (shown as 50% because it's a dual core CPU), Firefox's memory usage jumps to around 2GB from 100MB, in 500MB/s increments. Finally, at 5GB total system memory consumption, either the OS kicks in or some major swapping starts to occur – I'm not sure which of the two is happening exactly but you can see it when the green CPU marker gets overtaken by the red one.

As I have a large number of extensions installed, I was dreading the next step: disabling them until the culprit was found. Ugh…

Sure enough, after about half an hour of starting Firefox, observing the memory leak, killing, and restarting it, I narrowed it down to the Skype extension. Somebody at Skype needs to fess up. And here's the kicker – it only exposes the memory leak in the following configuration:

If you turn number highlighting on – it's fine. If you turn name highlighting off – it's fine. But if you turn number highlighting off but leave name highlighting on – major fail.

The Conclusion

So where am I going with all this? Here is the summary:

• somebody at Skype doesn't know how to program
• this is the worst memory leak in a Firefox extension I've ever seen
• this extension is notorious for its crashes, bugs, and memory leaks
• keep using this extension if you're
  • a masochist
  • need to perform burn-in tests for your CPU or RAM

Have you had problems with the Skype extension? If so, share in the comments.

• Essential Firefox Extensions (Plugins, Add-Ons) And Tips – A Comprehensive Guide :: Part 1 :: Tips
• Meet Firefox For Mobile [Video + Feature Highlights + More Info]
• A Detailed Depiction Of The Job Interview Process At Google (by Peteris Krumins)
• Twitter.com Autocomplete, Auto URL Expansion, Auto URL Shortener, RT Button, Nested Replies, Inline Media Embed, Search Tabs, And More
• Essential Firefox Extensions (Plugins, Add-Ons) – A Comprehensive Guide :: Part 2 :: Pragmatic Extensions

Navicat For MySQL is a GUI for MySQL developers. I've tried a few tools before but somehow got attached to Navicat due to a few nice features that I'm not going to go into right now. Navicat suffers from a couple of annoying bugs and random crashes. I don't know if I can help fix the random ones but if I can at least file the ones I can reproduce, everyone wins. I have the latest as of today version 8.0.23.

Bug [NAL-15328]: Structure Sync Fails to notice encoding differences

Structure sync doesn't see the difference between my columns that are utf8 and that are latin1. This is a severe bug. I relied on it to compare some production tables and wasn't aware some fields weren't utf8 in one of the tables until I dumped the DDL.

In 2 different databases:

1
2
3
4
5
6
7
8
9

-- Table "test" DDL
CREATE TABLE `test` (
`a` varchar(255) default NULL
) ENGINE=MyISAM DEFAULT CHARSET=latin1;
 
-- Table "test" DDL
CREATE TABLE `test` (
`a` varchar(255) character set utf8 default NULL
) ENGINE=MyISAM DEFAULT CHARSET=latin1;

Now run Structure Sync. It will not report any differences and won't even show utf8ness in the 2nd table.

Bug [VXL-67626]: Navicat crash

If I open the Server Monitor and there's a really long query running (I don't have the exact length), for example a really long SELECT with A OR B OR C, etc, it just crashes. I think there's a buffer overrun somewhere in Navicat's code, so when it does SHOW FULL PROCESSLIST internally, it overruns that buffer.
I would appreciate a fix for this as I lose all my open queries and tables when this happens. I'd be glad to answer any additional questions, but I hope the gist of it is clear.
A fix would involve at least letting a user select between SHOW PROCESSLIST and SHOW FULL PROCESSLIST as well as fixing the crash.

I was able to come up with a test case. I did warn you the query had to be really large :-].

1
2
3
4
5

CREATE TABLE `media` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`index_status` enum('none') DEFAULT NULL,
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

Take an instance of navicat and start a transaction:
> begin;
> select * from media for update;

Now open another Navicat session and issue the attached quite long sql vxl-67626.txt. Because I locked up the table in the previous step, you'll have plenty of time to open up the Server Monitor. The query should remain in the
process list until the first transaction is canceled or completed. Now launch Server Monitor and observe it crash.

• How To Diagnose And Fix Incorrect Post Comment Counts In WordPress
• Swapping Column Values in MySQL
• MySQL Conference Liveblogging: Portable Scale-out Benchmarks For MySQL (Wednesday 10:50AM)
• MySQL Conference Liveblogging: Benchmarking Tools (Wednesday 4:25PM)
• MySQL Indexing Considerations Of Implementing A Priority Field In Your Application