Sunday 28 December 2014

Lumina 830 review

I'm not a professional reviewer, but I've used iPhones and Android and I use them fairly extensively (podcasts, audiobooks, social media publishing, etc.)

(^;  Charges when plugged into Mac OSX via it's USB cable

)^;  How do you find your own phone number?  No idea.  Googled it and the suggestions I found are not correct for this handset/service provider. Gave up and called another phone from the Lumia and looked at the caller-id to get it.  Silly.  This helpful chap showed me exactly where to go, but there's nothing there.

Keyboard

Better than the Android keyboard on the Samsung Galaxy S4. I've added the Swype one on my Android, but it's still not as good as Apple's IOS built in keyboard.  This Lumina/Windows

Placement of the @ key and the Num key and Caps are pretty smart.  The touch response is good too, giving a little vibration feedback so you know when it's realised you've pressed a key.  So, it's as good as IOS, very good indeed.

Screen:  The image quality is very good, bright clear images with good colors.



Icons

Had to learn a new icon, the logo for "send" or "apply" or "ok" which looks like an email icon with motion lines at the side to make it look like it's to send.   Not too bad, mostly intuitive, but don't expect too many new icons to learn these days.  I thought they used this for posting on BaseFook as well as sending emails, universal and all. But, no, there's another new icon to learn for "share".  Social media and gadgets have been around long enough for them to avoid making new symbols for existing functions.  It's companies ways to try to mark out their own influence but it's confusing and rarely works.

Screenshots are always important to me to be able to do quickly and easily.  The Samsung Galaxy uses the swipe motion gimmick, which doesn't always work, but is ok mostly, while the IOS equivalent is similar to this Nokia Lumina--press and hold two physical buttons.  On this Nokia it's the power button and the volume-up button.

send icon



share icon
Speaking of physical buttons, the having three spread out all along the right side means it's almost impossible to put this handset in a car holder so you can use the GPS for navigating.  While traveling and using the SatNav, the camera randomly activates, the volume goes up or down, or the phone gets sent into power save mode.  Not clever.

Camera  I'm not a photographer, but counted almost 8 seconds between pressing the button and the camera being loaded and ready to go.  That's too slow to avoid missing those important shots!

Apps:  When I switched from IOS to Android, I first made a list of my priority apps to see if I could swap them over.  Runkeeper, iPlayer, Amazon Cloud Player, Amazon, Dropbox, SoundCloud, Gmail, Google Maps, Google Docs, Password Manager, Kindle, Audible.  They were all there, even streaming Amazon Instant Video right there from my Android device.  Here's my list including the Windows Phone:



Apple IOS
iPhone 4S
Google Android
Samsung Galaxy S4
Windows 8.1
Lumia
Facebookno problemsno problems crashes occasionally
navigationGoogle Maps
works well
hangs GPS works very well
Runkeeperworks wellworks well not available!
Skype
works well
Amazon


works well does not include Amazon Instant 
Video Player
Amazon
MP3 Player
not testedworks well not available!


DropBoxworks wellworks well Doesn't sync, this or anything else, until plugged into USB connection
Audibleworks wellworks well buggy! doesn't work
SoundCloudworks wellworks wellnot available for recording/posting or streaming

As an example, I downloaded Audible and signed in and downloaded a book.  Started listening--so far so good.  Then I stopped the app and when I came back to it later the eBook would not play. I restarted the handset, uninstalled the App, reinstalled the App and re-downloaded the eBook--no go.  Downloaded a different book, listened to it then tried switching to my original eBook--no go again. I still haven't figured out how to get my eBook to play again.     

In Short
In summary, the look and feel of the software interface is good. The glass face is solid and it feels well made.  But the reliability and lack of choices and features of the Apps combines with other weaknesses to show that this phone is only to be recommended for the most basic smartphone user who is happy with all the drawbacks to get the reduced cost.

Friday 12 December 2014

hostd disconnect & ESXi5 SAN storage issues with PowerPath 5.9.1.00

Symptoms:  Adding more than 2 luns caused hostd to disconnect hosts from vCenter.  Underlying issue is storage related.

We learned a lot about the PowerPath Adaptive policy (autostandby and proximity) but the fix for our problem was to upgrade PowerPath on our hosts.  Seems there's a VMware bug that shows when too many paths are presented for a disk.  Until VMware fixes the issue, taking PowerPath Version 5.9 SP 1 (build 11) to Version 5.9 SP 1 P 02 (build 54) stops our headaches.

The problem shows on our cross connect VPLEX, but it seems it's the number of paths to the storage rather than whether it's cross connect or not.

Still need to confirm this is the smoking gun, as their kbase article mentions APD and I  haven't seen that.  But out internal testing looks pretty good. We were reproducing the issue on demand in a test cluster with only two ESXi hosts (no VMs) and with less than 10 distributed volumes (VPLEX luns).

Got this from EMC:

Article Number:000190540 Version:7
Key Information

Audience: Level 30 = Customers Article Type: Break Fix
Last Published: Thu Nov 20 19:18:35 GMT 2014 Validation Status: Final Approved
Summary: ESXi host becomes unresponsive after adding or removing LUNs.

Impact ESXi host becomes unresponsive after adding or removing LUNs.
ESXi host has to be rebooted.
ESXi host cannot be managed in vSphere.
Issue Adding or removing LUNs on an ESXi host and rescanning storage can cause the host to stop responding in the management GUI.
The host becomes unmanageable and must be rebooted to restore management abilities.
Virtual machines continue to run normally, even though the ESXi host is not responding.
The hostd Daemon is a management daemon and it stops responding.
All paths down messages will sometimes be seen in the host logs just before the host stops responding.
Environment System: VMware ESXi 5.1
System: VMware ESXi 5.5
EMC SW: PowerPath/VE for VMware 5.9.1
Cause A bug in NMP contributes to a bug in PowerPath causing the host to leave a device in an All Paths Down state.
While the device is in All Paths Down it will continue to consume resources until the hostd daemon cannot start any new management threads.
When this happens the host becomes unresponsive because the hostd daemon cannot respond to managment requests.
Change Adding or removing a LUN to an ESXi host or cluster.
Resolution Solution:
Upgrade PowerPath to version 5.9 SP1 P02 (5.9.1.2) or later.


Workaround:
Once the host has stopped responding there are two options to bring it back.  You can try undoing the storage change that triggered the host to become unresponsive, or you can reboot the host.
The VM's are still running normally, so they can be gracefully shut down.  Because the host is not responding you will not be able to vMotion virtual machines to another host.

This problem is partially triggered by the presence of an ACLX or LUNZ device.
Removing these devices will greatly reduce the chances of the host going unresponsive.

Symmetrix: Unmap any ACLX devices from the FA's that the ESXi hosts are zoned to.
CLARiiON / VNX: Add a real LUN as lun 0 into the storage group and then reboot the ESXi host.

Place hosts in maintenance mode before adding or removing LUNs, so that they can be rebooted without affecting production if it is needed.
Notes This issue is seen with Symmetrix, VNX, CLARiiON and VPLEX arrays.   There is a separate OPT for this issue when seen with VPLEX arrays.

The kernel.log from the ESXi host may show evidence of entering and exiting an All Paths Down state similar to this:
cpu4:16629)ScsiDevice: 4108: Setting Device naa.60000970000298701034533030333844 state back to 0x2
cpu4:16629)ScsiDevice: 6121: No Handlers registered!
cpu4:16629)ScsiDevice: 4126: Device naa.60000970000298701034533030333844 is Out of APD; token num:1
cpu4:16629)StorageApdHandler: 277: APD Timer killed for ident [naa.60000970000298701034533030333844]
cpu4:16629)StorageApdHandler: 402: Device or filesystem with identifier [naa.60000970000298701034533030333844] has exited the All Paths Down state.
Attachments
Article Metadata
Product PowerPath/VE for VMware5.9 SP1
Operating System VMware ESX Server
Requested Publish Date 8/1/2014 1:11 PM