Short Non-Tech Rant: Tim Hortons
Wow. I've got quite a long history with Tim Hortons, but for some reason I keep going back (probably because of Roll Up The Rim). This morning at the drive-through was about par for the course.
Her: Welcome to Tim Hortons, how can I help you?
Me: Hi. Can I please get an extra-large tea, with two milk and two sugar?
Her: <several seconds of silence> Ummm, so you want a decaf tea?
Me: Actually, I just want a regular tea.
Her: Okay. Do you want anything in it?
Me: Yes. Two milk, and two sugar.
Her: <several seconds more of silence>. So two cream, and one sweetener?
Me (trying not to sound frustrated): No. Two milk. <pause> And two sugar.
Her: Oh! Okay!
I'm surprised that I didn't end up with a Double-Double instead, as has been known to happen before.
Rogers, Android, and You
I've posted before about my HTC Dream, and some of the run-arounds I've had with Rogers, but I haven't posted about that recently. Rogers, it seems, is out to alienate Android users and seemingly could care less.
A little back story first:
In September of 2009, an Android user reported a problem with the Android 1.5 ROM where, if you had GPS enabled and attempted to call 911, your phone would crash and reboot. The issue was promptly fixed in the Android source, and all was good. The user then reported the problem to Rogers, who did nothing.
Fast-forward to January. Rogers comes under fire for the issue and disputes having known about the problem for several months. The make an update to fix it, and push it out. To make sure that their asses are covered, though, they tell everyone that it's a Mandatory Upgrade. "If you don't upgrade, we're going to disconnect your data." And, on January 24th, 2010, they did. All HTC Dream and Magic users lost data for at least a day. The official word was that if you upgraded to the new ROM, you're connection would be restored within 24 hours.
Those who didn't update not only lost data, but starting receiving daily telephone calls and text messages telling them to upgrade. Some people even had their outgoing calls redirected to Rogers Customer Support (and reportedly, even 911 calls were affected by this, although Rogers denies this happened -- Update: see the comment from RogersMary below).
Eventually, Rogers released a waiver users could sign that would allow them to continue using their old ROM and get their data back (although some people had gotten around this by phoning Technical Support and having them manually enable the data connection, with mixed results).
Then, for a five-day period (February 9th through 14th), Rogers re-instated their free HTC Dream to HTC Magic upgrade program (for users who purchased an HTC Dream before December 31st, 2009). I took part and received a shiny new HTC Magic at no charge, and promptly sold my still-rooted HTC Dream.
Okay, back story over. What's the deal with the new ROM?
Well, there's what you need to know. If have a Dream or Magic that's still rooted, you can simply upgrade to the newest Radio image (available on the XDA forums if you do a little searching). This will allow you to keep your root, and the system Rogers uses to detect if you've performed the upgrade will thing you have (as it simply looks at the radio version string when your phone connects). Alternatively, you can sign the waiver above and you're fine as well.
If, however, you already performed the ROM upgrade (or received/purchased a new Dream or Magic from Rogers after the beginning of February), you're in a little bit of trouble. Here are the relevant details. The new ROM contains:
- An updated Kernel, which contains a fix to the Root Privilege Elevation Exploit used by Flashrec. In short, the One-Click Root no longer works.
- A new 'perfect' SPL (version 1.76.2010 SAP50000). This one comes with Security On and Fastboot disabled. As such, Magic users can no longer simply boot from a new recovery image and flash.
- Strict sigchecks are now in place, preventing running the RUU with the previous ROM from updating (HBOOT reports a version error if you try to run the RUU or use the rom.zip as a SAPPIMG.zip).
- The Gold Card method no longer works. This is an odd one, because it seems to process, but then exits without error. It isn't likely that Rogers disabled it - rather, they probably changed how it operates.
- There is an engineering SPL floating around the internet, however without a way to flash it, it currently does us no good.
As such, Rogers users with the Mandatory Update are currently boned. In order to gain root, we need one of the following:
- A new Kernel Root Elevation Exploit that will allow an application like Flashrec to load a new recovery image.
- A newer ROM that we can inject the engineering SPL in that will allow Fastboot.
- An answer to why the Gold Card method is failing, and a fix for that.
Until one of these solutions is found, we're stuck with 1.5. So far, solution number 2 looks like our best bet, as Rogers has announced that Magic users will receive an Android 2.1 update (with Sense UI) sometime soon - when this update comes out, it should be possible for an engineering SPL to be injected in to the update. Until that happens, we're stuck without access to a number of newer apps (like Google Goggles and Google Earth), and flaky Bluetooth.
The important things to take away from this are the following:
- If you care about rooting, NEVER perform a ROM update unless you're prepared to lose the ability to root, possibly forever. When the 2.1 update comes out, avoid it like the plague until it has either been deemed safe, a de-fanged version has been released, or someone has 'fixed' it to allow rooting.
- Watch the XDA forums for information regarding updates.
- Don't trust Rogers.
Support: I Want This Guy On Speed Dial
Although today has been a real Gong Show, my morning was brightened by, of all things, a chat with Dell Support:
10:04:03 AM System You are now being connected to an agent. Thank you for using Dell Chat
10:04:03 AM System Connected with ***_Oliver_******10:04:08 AM ***_Oliver_******: Hi, thank you for contacting DELL Canada support, my name is Oliver, how may I help you?
10:05:01 AM Laslow: I have a system that is unable to POST. If I remove the video card and use the onboard video, it POSTs fine. If I take the video card from an identical unit and try that, it also works fine. It appears that the video card is defective, and I need a replacement sent out.
10:07:13 AM ***_Oliver_******: I'll do my best to assist you with this one.
10:07:48 AM ***_Oliver_******: I could see here that system is an ***** and warranty is active until *****.10:07:55 AM Laslow: That is correct.
10:08:58 AM ***_Oliver_******: I'll replace this.
10:09:13 AM ***_Oliver_******: Would you like me to send an onsite tech ?10:09:21 AM Laslow: No thank you - the part will be fine.
10:09:33 AM ***_Oliver_******: May I have the shipping address?
10:09:58 AM Laslow: ***** ***** ***** *****
10:11:23 AM ***_Oliver_******: By the way, may I know who's the registered owner of the system?
10:12:46 AM Laslow: ***** ***** ***** *****
10:13:28 AM ***_Oliver_******: Thanks. I'll go ahead and process the case and dispatch. This would take me about 5 minutes. Hold on.
10:13:34 AM Laslow: Thank you.
10:13:39 AM ***_Oliver_******: Would you like me to send the reference numbers thru email instead?
10:13:50 AM Laslow: That would be greatly appreciated.
10:14:49 AM ***_Oliver_******: Please wait for the part next business day. Return to us the old part not later than ten days once the replacement part is received. You could use the same box that came in with it.
10:14:54 AM ***_Oliver_******: Anything else I can help you with?10:15:09 AM Laslow: No, that is fine. Thank you very much! You have been very helpfull!
10:15:19 AM ***_Oliver_******: Would you like me to contact you to followup on this?
10:15:36 AM Laslow: No, that will not be required.
10:17:39 AM ***_Oliver_******: Ok. Thank you! Thank you for choosing DELL, have a good day!
10:17:51 AM Laslow: Thanks again!
Exchange Sync With Android: Possible, But Not Pretty
One of the things I loved about my old iPhone was the built-in Exchange sync. I could sync my email, my calendar, and even my contacts (although I only did the first two). Life was good.
After moving to the Android platform, however, I was disappointed to discover that although an Exchange email app was included, it wouldn't allow you to directly sync an Exchanged-based calendar. A little searching provided a way, though.
- Make sure you're running Office 2003 or 2007 - if you have the Office 2010 Beta installed, it won't work. If you still want to sync, uninstall 2010 and install 2003 or 2007, then follow the Special Note at the end of the post.
- Download the Google Calendar Sync tool.
- Install, follow on-screen instructions.
- ???
- Profit!
Now it should be noted that I did this, and at first it didn't work as I was using Office 2010 Beta 2. Even after uninstalling it and installing Office 2007, I still couldn't sync and received this error:
Could not connect to Microsoft Outlook: error -2147319779
A little searching turned up this link, which contained a hint at the solution. When you install Office 2010, it creates the following registry key:
HKEY_CLASSES_ROOT\TypeLib\'{00062FFF-0000-0000-C000-000000000046}\9.4
In the same key, there should also be a '9.3' entry. With Office 2010 uninstalled, you can safely remove the '9.4' key. Now, restart Google Calendar Sync, and everything should work just fine.
One major caveat with this solution is that your computer has to be up-and-running for the calendar to actually synchronize - fortunately, this isn't much of a problem if you're the only one updating your calendar. With any luck, though, Google will eventually support full Exchange syncing with Android.
Edit: I probably should point out that this is for ROMs without official Exchange support (such as Cyanogenmod, which syncs Exchange mail, but not the calendar). Some official ROMs, like HTC's, actually include Exchange calendar syncing out-of-box.
Short Rant: WSUS
I'm running WSUS 3.0 SP2, and it really helps to not only track the update status of my machines, but also because we're only on a DSL connection, and the update caching is a lifesaver. My main complaint with WSUS, though, is the update filtering.
In WSUS, you can tell it what products you want to get updates for, what classification (driver, critical update, service pack, etc...), and even whether to auto-approve them or not, but for some unknown reason, WSUS doesn't let you specify the damn architecture that you want.
Our organization doesn't have any Intanium hardware - why doesn't WSUS let me specifically block that architecture? I only want x86 and x86_64 updates. Is that so hard? Instead, my auto-approve rules happily let those updates download, and then sit and take up space until I run the cleanup wizard.
Come on, Microsoft. Think this one through, please? Maybe introduce it in the 4.0 update?
Because I Can: Trackmania Nations ESWC
Progress!
Not horribly news worthy, however I finally got all the damn gold medals on the original Track Mania Nations. Next up, the Forever update (the last five tracks are a pain in the ass!).
Short: Quantum Linux
Due to a failed kernel upgrade earlier today, I decided to wipe my MSI Wind and start over with the LXDE spin of Fedora 12. After the install, I went through installing my favourite packages, and notice the following while yum processed the dependencies for VLC:
schroedinger i686 1.0.8-3.fc12 updates 208k
Closer inspection revealed the package to be a codec, but that only led to further questions. Does this package transport video, and then only determine whether it is encoded/decoded when your media player first tries to render it? Does the process involve acid, or radioactive material? Does it work with Boxee?
This has been your annual dose of quantum humour. I now return you to your Superbowl Sunday. Thank you.
Tales from Support: The Battery
During my run at Gordita technical support, I had more than a few calls regarding laptop batteries. This one really took the cake, however, and even has a surprise twist ending!
Me: Thank you for calling Gordita technical support, this is Laslow. How can I help you today?
Her: Well, the battery in my laptop doesn't charge, and as soon as I unplug the power it turns off. I need you to send me a replacement battery.
Me: Okay, I just need to verify a few account details....
After gathering all of the need information from her, I pulled up the warranty information on the account - although the laptop had a three year warranty extension on it, it was a month out of warranty. To make matters worse, batteries were only covered during the original warranty period and not at all under extended warranties.
Me: Well, ma'am, unfortunately your laptop is no longer under warranty, and the battery itself is only covered by the original warranty. The extended warranty you purchased explicitly states it's not covered.
Her: But it's been like that since I bought it!
Now, if there's one thing I hate, it's when people use the line "it's been like that since I bought it". Sometimes it's legitimate, and they return it right away, or even a few days/weeks later if they're busy. But when people try it months or even years after the fact, it's usually pretty obvious that they're just trying to get something for free. I hated it when I worked retail, I hated it when I worked in call centres, and I still hate it now, even to the point where I called someone out about it in line at a local London Drugs store.
Me: I'm sorry ma'am, but at this point I can't do anything about it. If it did it when you got it, why didn't you return it to the store, or call us right away? I mean, the battery is now three years out-of-warranty.
Her: Well, the laptop has been in my closet for a few years. I traveled for a while and never really thought about it.
Me: But if it's done it since you got it, you had to have used it to know about that, right? Why didn't you take care of it right away?
Her: I just didn't have time. Now, if you won't do something about this, transfer me to someone who will!
Those, folks, are the magic words that were my ticket out of an annoying call. As soon as she said them, I prompted ask to put her on hold while I got Customer Relations on the line. She agreed, and three minutes later I had an agent connect.
Now, at Gordita, Customer Relations was handled overseas. I really felt bad for these guys, because the only customers that ever got to them were usually pissed off, obnoxious, or just plain annoying. No matter how much they got paid, it wasn't enough, as they only dealt with the bottom-of-the-barrel. Regardless, I was very happy they were there.
CR Agent: Customer Relations, this is Mary.
Me: Hi, Mary, this is Laslow from Level 1 support. I've got a customer on the line who is OOW [out of warranty] and wants us to replace her battery because "it's been like that since she bought it".
Mary: Is she just out of her standard warranty?
Me: Nope, she's a month out of her three year extended warranty.
Mary: Okay, I'll set her straight - put her through.
I couldn't have been happier - a no-nonsense CR Agent willing to take the call immediately. Were it possible, I probably would have kissed her right then.
However, as I went to bring the customer in to the call, instead of hitting the Conference button, I accidentally hit the Disconnect button immediately below it. Shit.
Thinking fast, I got the customer back on the line.
Me: Sorry for the delay, ma'am - there's a bit of a wait in the queue, so it's taking longer than expected. Do you mind waiting a few more minutes?
Her: That's fine.
So, back to the Customer Relations queue I went, and was connected to a different agent almost immediately.
CR Agent: Thank you for calling Customer Relations, this is Jen.
Me: Hi, Jen. I was actually just speaking with Mary over there. <snip the re-explanation of the problem>
Jen: Oh, so the customer wants a new battery, and she's just out of her extended warranty?
Me: That's correct. Should I put her though?
Jen (to the sound of furious typing in the background): No, that's alright - I'm just adding an exception to the case authorizing the OOW replacement of the battery. Is there anything else I can do for you?
Refreshing my screen, I verified that yes, Jen had in fact authorized me to send the customer a replacement battery. I slowly thanked her, then went back to the customer.
Me: Ma'am, I have to say that you must be made out of a leprechauns, because Customer Relations authorized me to send you a replacement battery.
Her: Well, Laslow, I knew you could do it! I'm not happy that I had to wait so long, but I'm glad to see your superiors corrected you.
Me (grumbling): Yes, well, in order to process this, I need to go through the order process and inform you of what you need to do....
After reminding her that she would need to send us back the old battery and filling out the order form, I thanked her again and disconnect. Then, to the amusement of the people sitting around me, plowed my head in to my keyboard a few times.
I don't remember ever getting Jen again on future calls to Customer Relations, but this whole incident just goes to show that it doesn't hurt to try - the worst that can happen is they say 'No', and even if it goes against the odds, you might end up with what you want.
Short: Windows 7 Misreporting CPU Speed? Try This.
I noticed almost immediately after installing the first beta of Windows 7 that it wasn't reporting the correct speed of my processor. I'm currently running an Intel Core 2 Quad Q6600 (2.4Ghz) overclocked to 3Ghz. Oddly, Windows XP and Vista both reported the clock speed to be 3.00Ghz, but Windows 7 only reported 2.4Ghz. I made sure to verify that the overclock was still active with CPUID which confirmed that yes, the correct clock speed was 3Ghz. Several people suggested just re-running the Windows Experience Assessment, however that didn't do anything.
I'd mostly forgotten about the issue until I installed Rainmeter, and it started showing the stock clock speed as well. On a hunch, I went in to BIOS and, sure enough, Intel EIST (aka, SpeedStep) was enabled. After I disabled it and rebooted, Windows and Rainmeter immediately started showing the correct clock speed, 3.00Ghz.
Now why didn't I think of that sooner?