I missed them the last time they were in town, so I was right chuffed today to catch them when I was out for lunch. I…may have followed him down a dead-end street to get this picture….
« Posts tagged Google
Streetview Comes to Town
Rogers MMS APN Settings for CyanogenMOD 7
I tried firing off an MMS from my Nexus One this morning to a friend only to have it hang on ‘Sending…’ with no network activity. The short version of it is the APN settings for Rogers that are built-in to CyanogenMOD 7 are incorrect. Here’s what you need.
For Data/Text:
Name: Rogers
APN: rogers-core-appl1.apn
Proxy: <Not Set>
Port: <Not Set>
Username: <Not Set>
Password: <Not Set>
Server: <Not Set>
MMSC: <Not Set>
MMS proxy: <Not Set>
MMS port: <Not Set>
MMC: 302 (might be different – is auto-set by your SIM card)
MNC: 720 (might be 72 – is auto0set by your SIM card)
Authentication type: <Not Set>
APN type: <Not Set>
APN protocol: IPv4
For MMS (edit the bottom entry in the APN list called ‘Rogers MMS‘):
Name: Rogers MMS
APN: media.com
Proxy: <Not Set>
Port: <Not Set>
Username: media
Password: mda01
Server: 172.25.0.107
MMSC: http://mms.gprs.rogers.com (IMPORTANT: in the default settings, this is listed as grps rather than gprs – make sure to correct this!)
MMS proxy: 10.128.1.69
MMS port: 80
MMC: 302 (might be different – is auto-set by your SIM card)
MNC: 720 (might be 72 – is auto0set by your SIM card)
Authentication type: <Not Set>
APN type: mms
APN protocol: IPv4
And that should be it. Make sure that the first ‘Rogers’ entry is selected, and your MMS messages should now send correctly.
Google Changing Free Apps Account Limits
I just received this message from Google. Good to know I’m safe, but if you were considering signing up for a free Google Apps account, better do it before May 10th, 2011 unless you only need 10 users:
Hello,
We recently announced upcoming changes to the maximum number of users for Google Apps. We want to let you know that, as a current customer, the changes will not affect you.
As of May 10, any organization that signs up for a new account will be required to use the paid Google Apps for Business product in order to create more than 10 users. We honor our commitment to all existing customers and will allow you to add more than 10 users to your account for laslow.net at no additional charge, based on the limit in place when you joined us.
Sincerely,
The Google Apps Team
Cheat: How to get Custom Routes on Google Maps for Android
One of my few complaints about the Maps app on Android, even the newly released 5.0 version, is that if you use the Directions feature there is no Alternate Route option. There isn’t even an option to manually re-draw the route, or to enter a second destination like in the web version.
So I found myself faced with an issue – I was about to go on a fairly long trip, however I was planning on taking a route different from the one Google had suggested. While I could use the web version of Google Maps on my phone, I wanted to use the actual app. The solution, as it turns out, is very simple.
The trick is to set everything up on the web version of Maps first. This gets tricky, depending on how sever the changes to the route are. I my case, I only needed to drag one route marker to change the route to go where I wanted it. Here’s the before route, and the after (not my real start and destination, just an example).
So the cheat is actually very straight forward – after finalizing your route in web Maps, copy the link for the map (don’t use the address bar – use the Link button in the top-right corner of the map) and paste it in to a URL shortener like Is.Gd, then enter that URL on your Android phone. The browser will ask if you want to open the link in Maps or another program, so just choose maps and your custom route will appear, with full directions, right before your eyes.
Edit: I should clarify that Google Navigation for Android has a ‘Recalculate Route’ option, however if you aren’t planning on using it, or it isn’t available in your area, this is the solution.
An HTC DoA: Part 5
Continued from Part 4 (read from the beginning).
I took a trip to the UK at the beginning of the month, and when I returned on the 13th immediately checked my credit card statement. I wasn’t surprised to see that the refund still hadn’t been processed (now past the 14-business-day cut-off mark for credit card refunds). I called HTC yet again, and after a bit of hold time was given some good-ish news.
The agent confirmed that yes, HTC’s warehouse had received my phone and they had accepted it. However, someone at said-warehouse hadn’t closed the ticket in their system which prevented the refund from being processed. I was promised that the ticket would once again be escalated and that the escalations team would get the warehouse to close the ticket and things would get moving again.
I asked if HTC would compensate me for the interest accrued on my credit card from having this charge sitting on it for nearly two months, but was told they wouldn’t do anything. It was worth asking about, though.
So, on Tuesday the 17th I once again checked my credit card statement and there it was! A line item showing a credit for the DoA Nexus One. Although I wasn’t happy with the time it took to deal with the issue, and the interest charges that built up from it, I was ready to put the issue to bed.
And then I got the following email from HTC:
Dear Laslow,
Thank you for using HTC Customer Service. We want to make your next visit even better and would like your feedback. If you haven’t already done so please help us improve by taking a quick survey on your experience using HTC Customer Service.
Thank you very much for your time. Be sure to visit us online at http://www.htc.com to read the latest announcements and check out our newly released products.
We are unable to receive replies to this email account. Please visit us at http://www.htc.com if you have any questions or need further assistance.
Sincerely,
HTC
I couldn’t pass it up. I filled out the survey and was completely honest about the experience I had with trying to get a refund for a DoA unit and how ridiculous that I had to choose that route in the first place, rather than having the option to simply get a new, non-refurbished replacement like American customers. I submitted it, and then completely forgot about it.
This morning, while I was off rebuilding a borked IPCop box, HTC left me a voice mail message that went something like this:
Good morning Mr. Laslow. My name <redacted> from HTC, and I’m just calling to follow up on your return. I am very, very sorry that it took so long to process your refund. I’m also very sorry that you received a DoA unit in the first place. If you need any further assistance with this, please call us at 866-449-8358. Once again, we appreciate your business and are very sorry about this whole thing.
I was stunned; I never expected to hear back from HTC at all. I’m not, however, surprised by the fact that they simply apologized rather than offering some form of compensation (be it an accessory, a t-shirt, anything really). Regardless, I’m happy that this is over and I can finally end the tale of an HTC DoA.
Wish: Preload Map Data on Maps App for Android
While driving back from the Scottish Highlands to the South of England, I noticed something annoying about the Maps application for Android – when you pick out a route via the ‘Directions’ feature, all is well and good until you enter an area with no cell reception. At this point, you’re screwed.
I know it’s impossible to expect Google to preload hundreds of megabytes of map data on to your phone (you know, those pesky storage restrictions and all), but how about this: after Maps provides the directions for your route in text form, and you click ‘Show on map’, Maps could pop up an option (this could also be a configurable setting) asking if you want to preload map data.
My crappy mock-up of the prompt made on my netbook with a trackpad.
If you choose yes, it downloads the map data from Google’s servers for the planned route and caches it to your SD card. If existing map data is present that overlaps, it uses that after checking to make sure it’s up-to-date.
Probably a long shot that something like this could ever be implemented, but it would make life for those using their Android device as a Sat Nav so much easier, especially if you’re going on a long trip.
An HTC DoA: Part 4
Continued from Part 3.
So the unthinkable has happened – I actually received the shipping label from HTC yesterday! I immediately boxed up the phone and dropped it at a nearby FedEx box, and then proceeded to hammer the F5 key on the FedEx tracking screen.
Also to my surprise was the fact that the shipping label was for Priority Overnight shipping, and that the package reached its destination at 7:45am (PST) this morning! I’ll update this post later on when HTC contacts me regarding my refund.
Update (07/16/2010): Still no contact from HTC. However, after re-reading the initial email they sent, it does state:
Once we receive the items we will review the condition and we will contact you by phone or email if we have any further questions. If no additional information is needed a refund should show on your credit card within 14 business days of receipt of the return.
So at this point I’ll be sitting back and waiting for my credit card balance to update. I did end up ordering the replacement phone from Google on Tuesday, and it arrived (in working condition, no less!) this morning! Good thing, to, because I hear that this is Google’s last batch of N1′s that they’ll be selling through the web store….
Concluded in Part 5.
An HTC DoA: Part 3
Continued from Part 2.
It’s day 5 now and still no shipping label. I called HTC again and got a slightly different answer out of this rep. This one told me that my ticket had *just* been escalated and was on it’s way to the warehouse now. When I told him that the other agents had told me it had already gone up to the escalation team, he started backpedaling and said that although the ticket had been escalated it takes them time to look things over.
4 days? Ya, right.
So I asked for a supervisor. After waiting on hold (no music, just silence so you never know if you’ve been cut off), a ‘supervisor’ came on the line (supervisor is in quotes as, having working in a call centre before I have first hand experience pretending to be a co-workers supervisor – it’s a very common practice). I asked again what was going on, and she had yet another story. Apparently, HTC’s shipping system has been ‘down’ for ‘a few days’, and they have no ETA on things. She assured me, though, that (for real this time!) my ticket has been escalated, it should be at the attention of the warehouse, and I should have a label by Monday or Tuesday.
So, starting Monday afternoon (as nobody’s around to man the phones on weekends), I’ll continue with my daily phone campaign trying to find out when I can possibly expect to send back my wife’s brick…err…Nexus One.
Continued in Part 4.
An HTC DoA: Part 2
Continued from Part 1.
Day four of the return process and no real progress to report. According to the details given to me by HTC on Monday (see part 1), I should have received a shipping label in my email the following day. When I didn’t, I called HTC support back. The agent I spoke with told me to check my spam folder (already done – nothing), and then said that she would ‘escalate the ticket’ and a label sent out right away. I thanked her, disconnected, and waited.
And waited.
End of day Wednesday rolled around and still no shipping label. I called HTC again and was told that it can take an extra day when things go through the escalation process and that I should expect it to show up in my email no later than Thursday.
Well, here we are on Thursday and still no label.
I called HTC yet again, and was told that yes, I should have received the shipping label today. The agent then proceeded to tell me that he update the ticket, ‘increase the priority’, and that I should keep waiting.
Really, HTC? I’m normally a pretty patient guy, but come on! I’ve heard of American customers getting new, replacement phones within days, but we Canadians need to go through this gong show of a return process and then re-purchase the device because otherwise we end up a refurbished phone instead of a new one. This is bad PR, people. It’s time to start spreading the news.
Find out what happens next in Part 3.
An HTC DoA: Part 1
When Google first offered the Nexus One in Canada (by making a GSM version for AT&T, which is compatible with Rogers, Telus, and Bell in Canada), I jumped on. I had my order in the day the web store was updated, and in my hands by the end of the same week. Despite the cost, I consider it the best gadget purchase I’ve ever made.
Fast-forward to last week. With my wifes birthday coming up, I thought it would be nice to surprise her with a trip to the local Telus dealer (her carrier) for a shiny new phone. After looking at their offerings (the only two real considerations were the Motorola Milestone and the HTC Hero), she decided that she’d come down with a case of Phone Envy and wanted a Nexus One as well.
So, no big deal – we ordered the phone and waited. Unfortunately, due to the stat holiday on July 1st, the phone didn’t arrive on Friday like expected and instead came in yesterday (the following Monday). I left the phone plugged in to charge, and when the light turned green to say all was well I fired it up.
And waited.
And waited some more.
The Boot Screen on my other, unlocked (and functional) Nexus One
After about five minutes of staring at the above picture (minus the lock on the bottom, as I hadn’t gotten around to doing that yet), I got the feeling something was wrong.
I powered off the phone by pulling out the battery, then booted in to HBOOT mode (hold down the VOLUME DOWN key while pressing Power). That worked fine, so I tried to enter recovery. Unfortunately, I was met with the same screen. I tried several more times for both normal mode and recovery without success. Then I gave up and called Google.
At this point, I’d like to point out that I’m fairly certain it’s just a software error. Unfortunately, the only way I could really do anything about that would be to Unlock the phone, which voids the warranty. As such, the call to support was warranted.
I called the number listed on the Google Phone Contact Support page (1-888-48-NEXUS) and after a few quick IVR choices I was greeted nearly immediately by a tech. He asked about the problem, what I had tried, and immediately agreed the phone was D0A and would need to be replaced. That’s when things started to go downhill.
The problem is that I live in Canada, and HTC has a different policy for international orders than their standard ‘send you a replacement and then send the old one back’ policy for domestic ones. If you live in Canada and get a DoA phone, you have two options:
- Send it back via their normal repair process and get a refurbished phone (no option for a new one)
- Initiate a ‘Buyers Remorse’ return, get a refund for the device, and then order a new one.
The choice was fairly obvious – I ordered my wife a new phone, so that’s what she was going to get. After gathering a little more information, the Google tech transfered me over to HTC support to process the return order.
As the new tech was going over the specifics, a thought occurred:
Me: Okay, so I do the return, and within 14 business days of you receiving the device and okay’ing everything, you credit the purchase price back, correct?
Tech: Yes, that’s correct.
Me: So what about the duty charge that I had to pay CoD?
Tech: Oh, that. Hang on. –Pause– Okay, I checked on that, and what happens is you’ll get some paperwork from us once the refund has been processed. Once you have that paperwork, contact Customs and they’ll be able to issue a refund.
So at this point, I may have to wait three weeks for credit from HTC (although apparently it usually doesn’t take that long), and then I can file a claim to get my ~$70CAD that I paid for taxes back.
All was said and done, and I prompted received a confirmation email repeating what the agent said. However, as of posting I still haven’t received a FedEx shipping label in my email as promised. I called HTC back, and they escalated the ticket and said they’d resend the label, so now I’m waiting on that. Once I’ve got the label in and the phone sent away, I’ll order another N1 and see what happens.
