Lumia Icon, best Windows Phone ever, receives tepid reviews

by
in mobile on (#3GC)
story imageNokia's latest offering for Windows Phone 8, the Lumia Icon is out for review, and though early reviewers approve of the hardware's build quality, battery life and high-resoution screen and camera, many cite concerns about the OS and its app ecosystem and conclude the phone fails to compel.

Sporting a 2.22Ghz quad-core Snapdragon 800 processor, 2GB of RAM, 32GB internal storage (but no SD slot), a 20 megapixel rear-facing camera, a 1.2 megapixel front-facing camera, and a 5" 440ppi, HD-capable 1920x1080 resolution screen, the phone is no slouch. But reviews by Wired , Digital Trends , Gizmodo , The Verge , and IGN all use conflicting language like "best Windows phone ever made" and "pretty but flawed," "fantastic," and "bland," or "beautiful" and "unrefined." What's going on here? Is this a winner for the struggling Windows Phone brand, or does it fall short of the mark?

Lastly, rumours are circulating that Microsoft is considering Android compatibility. Is this going to be the secret sauce, or will it undermine WinPhones the way Windows compatability led to poor sales of IBM's OS/2?
Fatal Error - sql [select reason, count(reason) as reason_count, value from comment_vote where comment_id = ? group by reason order by reason_count desc] arg [715] msg [SQLSTATE[42000]: Syntax error or access violation: 1055 Expression #3 of SELECT list is not in GROUP BY clause and contains nonaggregated column 'pipedot.comment_vote.value' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_by] - Pipedot
Fatal Error
sql [select reason, count(reason) as reason_count, value from comment_vote where comment_id = ? group by reason order by reason_count desc] arg [715] msg [SQLSTATE[42000]: Syntax error or access violation: 1055 Expression #3 of SELECT list is not in GROUP BY clause and contains nonaggregated column 'pipedot.comment_vote.value' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_by]