It is no secret that Android tablets are not as popular as they used to be. With the exception of the Amazon Kindle Fire and the Samsung Galaxy Tab line of tablets, it seems like many Android tablet manufacturers have given up on Android Tablets. Google has been working hard to replace Android with Chrome OS on future tablets and while this is a refreshing change, Could a Chrome OS Tablet replace your aging Android Tablet? For this post, we are going to put two leading flagship devices in a head to head battle – the Samsung Galaxy Tab S3 (Android) and the HP Chromebook X2 (Chrome OS).
Google has been working hard on a feature called “Better Together” which was designed to allow for deep integration between Android Phones and Chrome OS. Thanks to the latest build of Chrome OS to hit the developer channel, we now have a better picture on what the setup process will look like and it is not looking good for non-Pixel Phone owners.
I wrote an article yesterday highlighting some of the changes to ChromeOS 68.0.3440.4 however it turns out that I completely missed two major features. This build of ChromeOS finally brings one of the most requested features to ChromeOS – The ability to easily access your Android Filesystem from within the ChromeOS File Manager and more.
Heads up all Pixelbook Owners, ChromeOS 68.0.3431.0 is currently being pushed to those who are in the “dev” channel. It seems like Google has made several changes to the bottom dock (shelf) such as removing the Profile Photo, moving persistent notifications and allowing the ability to pin Linux applications to the shelf.
Heads up to all Pixelbook Owners who have been following my posts about ChromeOS Project Crostini, you will be in for a pleasant surprise if you head into your Settings Menu after updating to ChromeOS 68.0.3416.0 (Currently in the Dev Channel). You will now see a “Linux Apps” section that will enable Termina and automatically drop you into a new virtual machine. There are also several new changes that were made in this release.
A few hours ago, I made a blog post on how to get Firefox running on ChromeOS via a Project Crostini Container. I started getting questions asking if Android Studio works. Today I will be taking this one step further by providing instructions to get Android Studio Running on the Google Pixelbook via a ChromeOS container.
I often have a hard time passing up odd or unusual tech when I find it. While on vacation visiting family, we popped into a Wal-Mart in a small Texas City and I spotted one of the most unusual pieces of technology that I have ever seen – The Sylvania SLTDVD9220-C is a sub $100.00 portable DVD Player with a average (for a portable DVD player) 9 inch screen and a sub-par 4 hour battery. Where the SLTDVD9220-C falls short, it makes up in a big and strange way – it doubles as an Android Tablet!
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:
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.