It has been some time since I have taken a serious look at ChromeOS but this changed earlier this month when I purchased the newly released Samsung Chromebook Plus (2017) to allow me to do some research for a future work related project. The Samsung Chromebook Pro is currently one of the highest end Chromebooks – only succeeded by the Samsung Chromebook Pro and Google’s Chromebook Pixel. I spent a few weeks using ChromeOS for as much as I could and can say that it has come a long way since the last time I played with ChromeOS however there are still a fair amount of shortcomings and several features that are best described as “half baked”. Here are my thoughts:
days months ago, I posted a set of instructions on how to get the LG Watch Sport to work on T-Mobile. Unfortunately this did involve users having to pay for an additional phone line at ~$40 per month so this solution was less than ideal. I do now have a better option that will cost a lot less and ultimately work better.
Many, including myself, were disappointed to see that Google partnered up with AT&T to be the exclusive carrier for the new LG Watch Sport. Many were unsure if it would work with T-Mobile but after some trial and error, I found out it does indeed work but there is a catch.
While browsing social networks, it is not common for users to point out that Android is a security mess with no data to actually back those statements up. Some users try to fabricate facts without doing any research. Over the next few weeks, I will be releasing a series of posts on KMyers.me called “Facts about Android Security and Malware” to try to shine some light on this and hopefully debunk some of the data that it floating around and to help users understand more about the security of their mobile devices.
In this first installment, I would like to make sure that we are all using the same common vocabulary. This post contains several of the common types of Android Malware as well as details for each. In future posts, I will be going over best practices to avoid malware and to explain why many of the details floating around the internet are not based in facts.
As a disclaimer – I am a huge Android Fanboy and will be doing my best to produce well researched and objective content for this series – each post takes several hours of research and writing. This series is mainly about Android however a lot of this could apply to other platforms. If you happen to spot any errors or content that you disagree with, please feel free to get in contact with me via my contact page, social networks or simply leave a comment below.
On July 25th of 2014, Amazon took a major leap of faith with their entry into the mobile phone market with the Amazon Fire Phone. This was an Android Phone that was completely devoid of Google’s Application Ecosystem. This AT&T exclusive phone was released and failed to sway users away from existing ecosystems into the new Amazon ecosystem. Despite everything Amazon tried including aggressive price cuts, bundling a year of Amazon Prime, Firesales and unlocking the phone – it still failed to sell. This post will take a close look at the Amazon Fire Phone to try to understand the reason for its failure.
The company Jide Software released a new multi-tasking centric build of Android known as RemixOS. Unlike Android, RemixOS focuses on multi-tasking by allowing you to run applications in a “windowed mode”, similar to a desktop computer. Unfortunately the instructions published on the XDA Developers website and Jide’s own website had several issues that left many (including myself) with a tablet that would not boot. This post will go over the instructions to get RemixOS working on your (Affiliate Link)Nexus 9 (WiFi Only)
OnePlus’s announcement video was a leap forward in product announcements, easily setting the bar higher for other OEM manufactures. Due to several product leaks, we already knew quite a bit about the OnePlus Two prior to the livestream. What did surprise me however was the fact the OnePlus seemed to hide several invite codes all over the livestream for wandering eyes to find, essentially creating a geek filled Easter Egg Hunt. It is worth noting that all of these have been claimed. I managed to capture a screenshot of several of them.
In the weeks leading to Google I/O, it is not uncommon for Android Fanboys to let their imaginations go wild when it comes to guessing the latest hardware that Google will release in the upcoming year, if any. Back in 2014, Google took a gamble on partnering up with HTC to release the Nexus 9. The Nexus 9 was a very nontraditional Android Tablet and many Android fans will agree that while it did have a lot of positive attributes, it failed to reach the market share that Google wanted. Here are the reasons that I personally feel that Google should work with Samsung to build the next generation of Nexus 10 tablet.
Over the years, I have amassed a large collection of Google Home Entertainment products including several Google TV set-top boxes and a handful of Google Chromecasts. Google made a somewhat expected announcement late last year that they would discontinue the Google TV system and at the same time announced the successor, Android TV. I managed to pick up a Nexus Player about a month ago and spent the past few weeks kicking the tires. Here is my review of both the Nexus Player and Android TV.
It should not come as a shock that I am a huge Android Fanboy who is often an early adopter of the the latest offerings from Mountain View however I will also be the first to admit that Google has often failed miserably in capturing a fair share of the Home Entertainment market. Google’s “Google TV” platform was in many ways ahead of its time but in other ways but in other ways suffered from some serious problems such complicated controls and a lack of OTA upgrades. With the release of the Nexus Player last year, has Google made a comeback?