So iOS 8 has been released and it shows Android how to do things properly in terms of advanced notifications as well as the sharing menu
iOS 8 advanced notifications allow you to respond right in the notification itself
On Android you may some extra actions (there was none in the messaging app a.k.a Hangouts), but taking a reply action on an email bumps you into the Gmail app itself to reply
Android has had sharing capabilities for ages (possibly since the first public Android release) however it is not consistent and seems to exists in at least 4 different variations.
1) Sharing in the Android Photos app (1st party application from Google): grid of large icons
2) Android sharing in Skitch (3rd party application): a quick touch to share with the last application and going to the “See all” option expands the list and adds extra items to the bottom of an existing list
3) Android sharing in QuickPic (3rd party app). Selecting “More…” shows a whole new menu that has no correlation with the initial shortcut share menu
4) Android sharing in Chrome (1st party app from Google): another 1 touch quick share with last app but otherwise a full alphabetical list of share intents.
iOS 8 sharing: consistent look and ability to order sharing activities (order seems different based on app, i.e. Safari vs Photos, but at least the order is configurable)
As an Android fan, it really bugs me that Android has had a lot of functionality but never seem to fully polish things up and strengthens the argument where Apple doesn’t necessarily innovate with new features but implement features in more usable forms.
After the last post, I gave Google yet another call and found out that there have been similar issues: getting a confirmation on the website but no emails nor courier. They set things up yet again and thankfully the courier finally came to pick up the goods on Tuesday (they came on Monday but we were out for a company lunch, and didn’t even ring my number).
So after 3 weeks, 2 emails and about 5 calls, I have finally managed to get a replacement Nexus 4 and returned my old one. That totally felt much harder than it sounds (more reason to buy from physical brick and mortar stores?)
P.S. Recorded the hold music and found out that it is “The Lighthouse and The Whaler-Untitled (This Is an Adventure)” – listen on YouTube thanks to Shazam (at first I though it couldn’t find it due to the name having “Untitled” in the name…
So after the last post, I followed up with an email to Google Support and this time there was a response within 30 minutes, with the RMA details as below (full email). Hurrah!
2 days later I got my replacement device. Double hurrah! Backed up and restored data to the new device and on to returning the old device
Packing the device on Friday 29th and re-reading these directions, I realised that I didn’t get any confirmation email nor shipping labels. Cue a another call to Google support and Google Support lady (first one I’ve spoke to, previous 2/3 calls have all been guys) says that they don’t email shipping labels to Australia and that the courier man should have it.
Courier man never came yesterday, so retried requesting another return request today and got a “Collection for given RMA Number has already been requested”. So yet another Google Support call….
After my last post on Google’s Support, I gave Google another call and thankfully William managed to further process my support ticket: he said that it was lodged and escalated but there wasn’t any updates on it.
He asked me to check my Google wallet billing and shipping address and after some verification with him, that it would be processed accordingly. He was saying something along the lines that it takes 2 days for the system to get updated after changing my billing/shipping address and it would then be processed. But alas still nothing.
Is this what customer support is meant to be? The customer having to manually follow up on things only to get things done?
So my Nexus 4 started acting up 2 weeks ago: the left section of the screen doesn’t respond to touch: essentially anything between the vertical red and blue lines is non-responsive to touch. Watch the video to see it in action.
So I called Google and they advised to do a factory reset, which I did 8 days ago, and proceeded to reply the email I got for my case (which I still have no reply as of today).
So I gave them a call the following day, which they told me that my device is still under warranty and that their “Termination Team” would get back to me. It’s been a full week since I called them and they have yet to get back to me.
A twisted idea that came to mind, is that the longer they make me wait, the more chances I have for accidentally dropping my phone and getting it cracked or something that puts it out of warranty, and thus my wanting to document my perfectly fine looking phone (i.e. not physically damaged) just in case they were to try pull this stunt if I do accidentally drop it (I am being too paranoid aren’t I?).
But anyway, Google support, where art thou? Can you please terminate me/my Nexus 4 in a good way?
P.S. If Google support is having manpower issues, I wouldn’t mind helping them out to ensure customers aren’t getting left waiting for a week without a response.
TLDR: Sublime Text’s plugin Examples page is out of date as of 30th May 2014. Look at “How to Create a Sublime Text 2 Plugin” for proper guidance.
For the popularity that Sublime Text gets, it seems that their plugin documentation has been left by the wayside
Their Plugin Examples page is out of date showing an example for SublimeText 1. I found that out when creating the plugin only to see the following error message in the Sublime Text console (Ctrl+~ in Windows)
ImportError: No module named sublimeplugin
Searching for this error I landed on this forum post which the link to “How to Create a Sublime Text 2 Plugin” from Tuts+ which seems to work.
There seems to be a change from camelCase to snake_case for functions thus all the instructions on the plugin page are incorrect.
Links API References: choose appropriate link for Sublime Text version
A couple years back I though that Android had a big problem with Low Available Phone Storage Space for apps and after reading Ausdroid’s recent review of the Medion 4, it seems that this is still an on-going issue.
The device in question is the Medion 4 which is advertised with “4GB Memory” on Aldi’s site, but according to AusDroid, there is only 500MB allocated for apps (the rest of the space can still be used to store photos/files but not apps without some rooting and hacking).
Filesystem Size Used Free Blksize
/data 503M 151M 351M 4096
My 16GB Nexus 4 has 12.9GB allocated to the /data partition which is a bit less than 13.6GB of a 16GB iPhone 4 (can’t seem to find a definitive answer for the iPhone 5) but is still a majority of its storage unlike the Medion 4. The Samsung Galaxy S4 has a separate issue which is not exactly the same but gives the same results to the end user: a false sense of storage space (only 8.8GB free from the 16GB model due to Samsung’s customization of Android with its own skin & apps). While it’s not as bad as the Microsoft’s Surface RT storage debacle (15GB free in a 32GB Surface RT, 28GB free in a 64GB Surface Pro. Source: Microsoft’s Surface Disk Page FAQ), both of these situations don’t give me much confidence when recommending non-Nexus Android devices with X GB of storage.
At least if it is just Android customization (ala Samsung), flashing a custom ROM should be able to solve the problem. I’m not sure if the partitioning (ala the Medion 4) can be solved using a custom ROM, but even if it does, you will need to find a ROM that supports your device: so you hope that your devices isn’t a weird obscure one.
So when you buy an Android device, you can’t say for certain that you have a majority of the advertised storage available for apps. I can only assume that Nexus devices would give you the best experience in terms of not being ‘cheated’ for storage space, but I guess this gives more credence to the fact that Google has lost control of Android and that some manufacturers are still giving Android a bad name.