Press "Enter" to skip to content

Subsequent Nexus Flashing Post

admin 0

Yeah I know, it’s been more than a couple of days.  My intention was to provide a comprehensive, step-by-step, instructive ‘How To’ on the simplicity of unlocking, rooting, and flashing a new ROM to your tablet.

Due to everyday issues concerning family and life in general this article will have to wait.  I still have every intention of writing it, if only for my benefit.  Having it posted here means it will be available for me to peruse anytime I have issues with my Nexus 7.

In the meantime, a good place for you to start while waiting on my lazy butt, would be Cyanogenmod for the Nexus 7 WiFi (2012) [Grouper].  That will take you directly to the instruction page for the Cyanogenmod ROM for the specified tablet.  Another good link for perusal is at the XDA Forums, which is the “Chroma” ROM for the Nexus 7 WiFi (2012) tablet.

That should be a good start for anyone who was waiting for me to get to this.  I’m sure there are some people out there that are just apoplectic with rage that I’ve failed to come through on this pledged post.  My apologies, but alas, life comes along…

BTW, apoplexy is a terrible thing!  Be careful how mad you get. read more

Flashing Your Google Nexus 7 WiFi (2012)

admin 0

In the next couple of days, I hope to have a comprehensive article posted on how to successfully ‘flash’ your tablet. (this will specifically be written for the above titled “Google Nexus 7 WiFi (2012) also known as ‘grouper’)

The Nexus 7 WiFi (2012)

The Nexus 7 WiFi (2012)

There is an awful lot of uncertainty wandering around on the interwebs concerning bricking your tablet with OTA updates. Over the past weeks, I’ve been successful going from KitKat 4.4.4 to 5.0 to 5.0.2 and finally to Lollipop 5.1. This isn’t to say all was perfect and I didn’t pull out a few hairs in the process, however, I was able to flash all of the above ROM’s using the sideload method from a Linux laptop.

On Saturday, I had enough of being without a rooted device. With Lollipop 5.1, and the SELinux read more

What “Linux” To Choose

admin 0

If you are a Windows user who is sick of M$ and paying for what inevitably ends up being bug filled, security problematic software, (or Mac users for that matter) you should definitely read this. I wrote it for you. I used to be you! If you love computing, are on your computer all the time, or just someone looking for more control and freedom over “YOUR” PC, you should definitely come away from this a lot less hesitant about making the move to Linux! I wish there had been something this succinct when I was making the switch.

It was 2008, I was using Linux.(I have been since 1991 or ’92 off and on, though at that time, more ‘off’ than ‘on’) Over the last 8 to 10 years, I had been a wanderer on the Linux landscape. I was just off a career that spanned almost 30 years of working with nothing but computers, mostly MS servers. Toss in a couple of AS400’s, Apples, even an OS/2 Warp server. It wasn’t until going to work for UPS that I had my first taste of Unix. When I started at UPS there were still several systems that relied on their Unix servers. My job with UPS required a lot of database experience and being able to import usable data into the UPS shipping systems format. Fun stuff. In other words, I had my hands in a ton of different hardware, OS’s and yes, desktops too. (anybody remember 10Base-T and the fun of trying to find which one had the bad ‘terminator’ plugged into it?) This ended in Mar read more

DistroWatch Credibility Debacle

admin 0

As I sit here writing this tonight, I am totally amazed at the genuine stupidity of DistroWatch dot com. Some in the Linux world would have you believe that the writers at DW are all just an article/post away from a Pulitzer prize. Their statistics, when it comes to the “most popular” Linux distro available, based on a “Hits per day” method to gauge popularity, is about as accurate as any internet poll you’ll come across.

Many new to Linux hear of DW and truly believe it is Linux gospel. It is NOT! To bandy about a headline, “Community developments: The systemd project forks the Linux kernel”, that is such a hot button issue for Linux users today is totally irresponsible and, for me, conclusively proves they have zero credibility.

For those who come to their defense, claiming “Oh it was just an ‘April Fools’ joke, we are still in March! To post such an article with no disclaimer, no acknowledgement that it is comic relief, is not just poor editorial oversight, but truly poor judgement. For those in the land of make believe, pixie dust, and Yosemite Sam, (Ivan Gotyaovoitch?) look no further for what is “NOT” happening in the world of Linux than DW. DistroWatch must be fervent followers of PT Barnum, who is credited with coining the phrase, “There’s no such thing as bad publicity”.

After thoroughly searching for a read more

TRIM, Linux, and your SSD

admin 0

First, since 2011 or so, TRIM has been enabled by default in the Linux Kernel but not what you’d call optimally. I don’t know the why of that so don’t ask! I have learned over the last few weeks that enabling TRIM using the “discard” option in /etc/fstab will end up significantly slowing your drive down. That option will make Linux use TRIM the same way Windows does. (which can cause your drive to slow down) TRIM tells the SSD drive to delete the information in the blocks and then write to them. In reality, there is no need to do this every time you write to the disk in Linux. (yes I know it is arguable, but this seems to be the consensus of the majority)

The smart thing to do is to create a ‘cron’ job to deal with TRIM, say, once a day, or once a week. You can do this with the ‘fstrim’ command. To see if your SSD drive even supports TRIM try the following in your terminal;

“sudo fstrim -v /”

If you see no error, and it tells you “/: 19 GiB (20374241280 bytes) trimmed” you’ll know you have a TRIM capable drive! (obviously your size will differ from mine probably). The above command is a way for you to manually TRIM your SSD drive whenever you like. The above command was to TRIM the ‘/’ (or root) partition or your SSD. You would do the same for home with;

“sudo fstrim -v read more

Skip to toolbar