YouTube Classic Extension on Firefox

Turtle YouTube

I have noticed as of late how clunky YouTube has become. The “dynamically loading content”, which I don’t remember asking for, has these weird pulsating boxes and you have to wait longer to get what you want. In what world does slower loading text make sense?

A Solution Presents Itself

I was listening to one of my favorite podcasts, Linux Action News, and on episode 64, one of the items discussed was this YouTube Classic extension and how having it installed improves load times. I was interested in trying it. I installed the extension through the Add-on manager and boom, done, nothing else to do but enjoy the reduced wait time with YouTube. Visually, it takes YouTube back a few years to, what I consider, a much better YouTube experience.

YouTube Classic Extension.png

Interestingly, there is a Chrome extension but Google has decided to remove it from the Google Chrome Web Store. One could draw the conclusion that Google prefers a less efficient YouTube experience. It is still possible to “side load” the extension. You can read more here on the GitHub page if you are interested. I have been drifting away from using Chrome so it is not really a priority to get it working.

Final Thoughts

Although, I have increased the usage of the Falkon browser, I still prefer to use Firefox for YouTube for the Plasma Integration plus KDE Connect which allows me to start and stop YouTube from the phone or my not-so-fancy Bluetooth headphones (no KDE Connect necessary for that).

If you are annoyed by pulsating boxes of dynamically loading content and want a more zippy static feel, this is most certainly the extension to have in Firefox. It would be fantastic if I could fix all websites “dynamic content” but that is not available… yet…

Further Reading

Linux Action News, episode 64

YouTube Classic Extension

YouTube Classic Extension GitHub page

Falkon Browser Home Page

 

openSUSE Leap 15.0 Early Adoption Experience

Dell Latitude D830 openSUSE Leap 15.0-sm

I have a “sidekick” machine in my cubicle that has been happily running openSUSE Leap since I started using it. It is a recovered Dell Latitude D830 with an Intel Core 2 Duo T9300 CPU at 2.50 GHz, 4 GiB of RAM and the Nvidia Quatro NVS 140M. It just has a standard hard disk drive for storage. I put this unit back together 3 years ago only expecting to get a year or two of use out of it. Thankfully, the way Linux, and specifically openSUSE rolls the distribution, I have far extended the life of this machine.

Since this hardware is older everything is generally supported out of the box without any tweaking. I have decided, for now, to not use the proprietary drivers and see if Nouveau will work using KDE Plasma and not lock up on me.

Installation

I downloaded the DVD Image (now released as an official version) and used SUSE ImageWriter to write it to a USB. Like virtually every other openSUSE installation, it was pretty uneventful. I did choose to do a “Nuke and pave” for this installation as I wanted to set everything up from scratch. There have been a number of changes in openSUSE since the last static release, namely, the BTRFS subvolume structure, the location of the RPM Database move and SuSEfirewall2  migration to the new firewalld. I also experimented with a number of applications on this system and just wanted to have a fresh start.

Outside of the warning of the usage of Nouveau drivers with KDE Plasma, there as nothing to note on the installation process.

First Run

To start out, I needed to ensure that I covered my bases for my preferences. Since I like to add a little Oxygen Theme into the Breeze Theme I immediately ran this in terminal:

sudo zypper install oxygen5

I also like Konqueror and one of it’s specific features, the File Size View.

 sudo zypper install konqueror konqueror-plugins

Then I added the Multimedia Codecs along with VLC Player.

So far, everything seems to be working just as expected and the Nouveau drivers are holding up. I will continue to use them until I have any issues

Dell Latitude D830 Leap 15.0 20180523.png

One Week Later

I have since updated the machine to the current release version and I am still operating, trouble free. The System seems to be humming away well with the Nouveau drivers. I have tested many things I know would have caused the graphics drivers to bug out and crash X. At this point, there hasn’t been any weirdness whatsoever. The compositor is running just fine without any glitching. I have been using this machine in the same mannor as I had previously used it under openSUSE Leap 42.3 with the propriatary Nvidia drivers. Should I have an issue, I will see if the propriatary drivers fix it.

What I Like

After installing the necessary packages, all of my system settings were just as I wanted them to be. I didn’t have to fiddle around with any settings. KDE Plasma 5.12 is the Long Term Support version of the Environment and I know that from my expeirience with the transition to 5.12, it is more memory efficient than previous versions. In only one week, I haven’t run into any issues where Swap Space was needed. In monitoring the memory usage, I fluctuated between 2.8 GiB to 3.4 GiB in usage with Firefox being biggest memory hog. This has prompted me to start playing around with the Falkon web browser which I downloaded here. So far so good but I need more time to use and play with it before I can say more.

What I don’t Like

So far, I haven’t found any issues, but it has only been a week that I have been using it. Maybe, I could say, I don’t like that openSUSE doesn’t have wider adoption as it is technically very sound and very stable. I am hoping with the release of openSUSE Leap 15.0 that it will reach a wider audience.

Conclusion

openSUSE Leap 15.0 has been polished up very nicely. It it very much an incramental improvement over 42.3. The software selection meets my needs and if the software you want is not in the official repository, there is likely a repository available on the Open Build Service.

Since most of my systems are pretty low-end, I have them generally set up for specific purposes. Although I can happily run openSUSE the way I want with 2 GiB of RAM, I have come to the conclusion that in order to have a real positive experience, you need to have at least 4 GiB of RAM.

This Dell Latitude D830 is now 11 years old. It is far past it’s end of life but thanks to the all the fine engineers involved from kernel development, the applicaitons all the way to package maintainers and testers, this computer still remains very useful and not quite obsolete. I am impressed with the stability open source Nouveau graphics drivers which gives me a lot of confidence that as Nvidia abaondons the older hardware, I have options. I just may get several more years out of this machine.

Further Reading

openSUSE Leap Download

SUSE Imagewriter

Falkon Web Browser

Falkon Web Browser Download for openSUSE

Multimedia Codecs along with VLC Player

KDE Breeze Theme with Oxygen Enhancements

Dell Latitude E6440 all on SSDs

e6440-01-sm

I have wanted to upgrade the 500 GB SSHD hybrid drive in my Dell Latitude E6440 since I purchased it but i just wasn’t prepared to spend the asking dollars for a new SSD. The only adequate solution I determined reasonable was to go with a used SSD and just accept the risk that goes with used.

After much searching and bidding, I purchased a Micron M500 with 960GB SSD which ends up being 894GiB of storage. When it comes to SSDs this is NOT, by any stretch, considered top of the line. Here are the specs that many seem to be fixated.

  • Sequential 128KB READ: Up to 500 MB/s
  • Sequential 128KB WRITE: Up to 400 MB/s
  • Random 4KB READ: Up to 80,000 IOPS
  • Random 4KB WRITE: Up to 80,000 IOPS
  • READ/WRITE latency: 5ms/25ms (MAX)

Not the most performant drive but certainly much faster than the SSHD that I was using. If you are interested, here are the full specifications from Micron on this line of drives.

Since I already put the root and swap file system on a 128 GB mSATA SSD with very positive results, I was encouraged about how this upgrade was going to go. I could expect better performance with less power usage.

s-l1600

In preparation for upgrading, I did what any reasonably prudent, Linux using, data conscious, user would do. I backed up the contents of my home directory, well, another snapshot using Back In Time.

Performing the Modification

The great thing about every Dell Latitude I have ever owned is the ease of serviceability of the machines. No crazy tools are needed or long list of instructions to perform a simple modification. Just a small Phillips screw driver.

IMG_20180512_081253811.jpg

Two screws and the drive can be removed from it’s bay. The drive is held in place by these isolation rubber rails and a caddy cover. I appreciate this design, it is easily assembled, the rails have a nice, snug interference fit, and the caddy cover is held in place with a clip and screw.

SSD drive assembly

Troubles I Had

I am not sure what I did wrong but I couldn’t get the system to not look for the, to-be-replaced SSHD. I tried unmounting the drive before a reboot but still, it would continue to wait for the drive. The system would get stuck looking for the old drive and fsck didn’t correct the issue. I became impatient so I just decided to do a complete re-installation of the openSUSE Tumblweed, because I was too lazy to keep searching for a solution. There is probably a great simple solution that just escaped me.

Restoring the Data

There was a bit of a struggle in understanding how to restore the data from Back In Time into my home directory but once it was done, everything was back to normal. It took a bit longer than I expected but everything restored, all the files and settings. Like it never even happened…

A quick check of the SMART monitoring tools:

smartctl -a /dev/sda

=== START OF INFORMATION SECTION ===
Model Family: Crucial/Micron MX1/2/300, M5/600, 1100 Client SSDs
Device Model: Micron_M500_MTFDDAK960MAV
Firmware Version: MU05
User Capacity: 960,197,124,096 bytes [960 GB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 6
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Mon May 21 10:10:56 2018 EDT
SMART support is: Available – device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

My favorite line is the last one that says the test result: “PASSED.”

Experience

I am running openSUSE Tumbleweed with KDE Plasma as my desktop environment. The aAverage energy consumption before the upgrade, using the SSHD plus the mSATA drive was 21 watts; under similar loads with the mSATA and the 2.5″ SSD, I am consuming about 17 watts. These numbers, are of course, just estimates at approximate similar loads. It is not a very well controlled power study. Between the two drives I now have a total of 945 GiB of storage available; the most I have had on a laptop.

Opening up Steam is much quicker than before. Starting a game does indeed load a lot quicker than it did on the SSHD. I didn’t take any before and after benchmarks but there is most certainly the feeling of increased speed in everything. The computer was no slouch before but now there is an increased sharpness in using it.

The computer is oddly quite with only the fan left as a moving part. However, the only time I notice there is a fan is when my hand goes past he vent and I can feel a little warmth coming from it. Logging in isn’t quite instantaneous, I do have to wait a few moments but I blame much of that on the fact I heavily use the Akonadi storage service for personal information management. I have more information than most people likely save but suffice to say, the machine starts very quickly.

I didn’t take any external thermal readings from the computer before the upgrade but it feels like the thing does operate a bit cooler. It is only an impression.

Final Thoughts

This Dell Latitude E6440 seems to have an extra boost of speed, as to be expected. What I didn’t expect was how much I notice the censorial changes of using this laptop now. I have used other solid state only machines before and didn’t think much of them. Perhaps their less than stellar keyboards out weighed the silence of their operation or possible that I use this machine more than most. Regardless, I appreciate the change.

Was the upgrade worth the price I paid for the drive? So far, yes, very much, indeed it was worth it, but as I did buy it used, and although it passed the health self-assessment, I don’t really know how long it is actually going to last. For now, it’s pretty great and I don’t think I would want to go back to “spinning rust” for storage.

External Links

Micron M500 Specs

Back In Time

128 GB mSATA SSD

My Dell Latitude E6440

Using a 3.5″ Floppy with openSUSE Linux in 2018

floppy.png

I recently came upon two needs for needing to use a 3.5″ floppy in Linux. First was to go through this stack of disks to recover any data off of them. Secondly, in my latest effort to dig up the musical talents I once used regularly about two decades ago, I acquired a Korg N364 that has a 3.5″ floppy drive on it and I wanted to transfer data on and off of it.

USB Floppy Drive

The great news is, openSUSE Tumbleweed running KDE Plasma recognized and utilized the drive immediately but oddly, I could not write to the drive. My first task was to go through the stack of floppies and copy all the data off and archive it. I found some great files from the 90s that I rescued from bit-rot.

Floppy drive on E6440

The problem I ran into was my inability to write to disk. So much so that I even called into the Ask Noah Show. With some poking around and help from the IRC channel, I tried a few things:

sudo mount -o remount,rw /run/media/user/disk

Which was seemingly successful as it did remount the disk. I had one particular disk that I could not modify its contents. I had to double check that the disk was write enabled as it seems that I can’t remember what I did in the 90s to write protect or enable a disk.

back of floppy disk
Write-enabled disk

My next step was to format some of the problem / unreadable disks. I tried to format the disk from KFloppy with this error

Internal error: device not correctly defined.

I can’t be sure as running KFloppy in terminal didn’t yield much more information.

Fortunately, I am able to format the floppy disks in terminal with this:

sudo /sbin/mkfs.vfat /dev/sdc

This seems to have worked for most of my disks but it looks like some of the disks are far too degraded which seems to be the source of my problems. To correct the issue which has only been somewhat successful I ran this in terminal to fix the file system:

sudo fsck /dev/sdc

Even though the output looks unsuccessful, it actually was quite successful.

fsck from util-linux 2.31.1
e2fsck 1.43.9 (8-Feb-2018)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks…
fsck.ext2: Bad magic number in super-block while trying to open /dev/sdc

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>

I wouldn’t trust any critical data on this disk but I am able to transfer files back and forth without issue and I tried several files including making directories, so I am quite sure it is working well enough, at least for my purposes.

Floppy Drives are Cool

Many of our modern Solid state devices just lack something special to them that I don’t know how to capture in words. You just can’t have fun with USB flash drives like this hugely creative and industrious techy did with 3.5″ floppies.

Conclusion

The issue with KFloppy maybe that it is likely expecting a non-USB floppy, meaning, it is looking for the floppy drive at /dev/fd0 or /dev/fd1. The USB floppy disk mounts as an /dev/sdc on my system since it is being attached to the computer via the USB bus.

I don’t know how much I am actually going to use the floppy drive but I do have some more disks to at least pull data from. I wasn’t able to transfer any data to the Korg N364 due to a floppy drive failure but that is another project for another time.

Additional Information

nixCraft | How To format floppy disks, Zip disk in Linux

KDE Utilities – KFloppy

 

Panasonic CF-19 Toughbook | Touch Panel Calibration

panasonic-cf-19-toughbook

I don’t have loads of experience with using a touch screen interfaces on Linux but every setup to date has not required any fiddling around in any of the configuration files for proper operation. Thankfully, the folks at Panasonic made the CF-19 with some one-off technology to offer me that experience of understanding how to tweak and configure the touch panel interface.

The Problem

Everything about this machine configured perfectly from the openSUSE installer. Not a single component required extra prodding to use. Even the touch panel was recognized and somewhat usable, however the further away from the center of the screen you would touch, the further off the pointer was from where you touched.

Calibration Attempt One

Doing some searching on the webs, I came upon this tool called xinput_calibrator that creates a set of rules in xorg.conf.d folder (/etc/X11/xorg.conf.d/). It was a such a straight forward approach that I was sure it would work. Running it displays a screen with 4 cross-hair points of which you use the stylus to touch each of them. When it completes, you have a nice little configuration file to drop into xorg.conf.d. Unfortunately, it didn’t work at all.

Calibration Attempt Two

This method was not as easily understood or accomplished and brought with it a good share of trial and error.

First, I needed to find the input name of the touch panel. This was accomplished in my favorite terminal, Konsole:

> xinput list

⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Fujitsu Component USB Touch Panel id=9 [slave pointer (2)]
⎜ ↳ ImPS/2 Generic Wheel Mouse id=11 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Power Button id=8 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)]
↳ Panasonic Laptop Support id=12 [slave keyboard (3)]

Now that I identified that the touch panel was identified, I needed to find further information about the touch panel itself

> xinput list-props “Fujitsu Component USB Touch Panel”

Device ‘Fujitsu Component USB Touch Panel’:
Device Enabled (143): 1
Coordinate Transformation Matrix (145): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
libinput Natural Scrolling Enabled (280): 0
libinput Natural Scrolling Enabled Default (281): 0
libinput Calibration Matrix (282): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
libinput Calibration Matrix Default (283): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
libinput Left Handed Enabled (284): 0
libinput Left Handed Enabled Default (285): 0
libinput Middle Emulation Enabled (286): 0
libinput Middle Emulation Enabled Default (287): 0
libinput Send Events Modes Available (263): 1, 0
libinput Send Events Mode Enabled (264): 0, 0
libinput Send Events Mode Enabled Default (265): 0, 0
Device Node (266): “/dev/input/event6”
Device Product ID (267): 1072, 1282
libinput Drag Lock Buttons (288): <no items>
libinput Horizontal Scroll Enabled (289): 1

I had to modify the line containing the Coordinate Transformation Matrix:

Coordinate Transformation Matrix (145): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000

Some of those comma separated values corresponded to specific properties of the panel matrix. What I learned about those nine numbers that seem to matter:

Touch_area_width, 0, touch_x_offset, 0, touch_area_height, touch_y_offset, 0, 0, 1

I used some trial and error to get this to line up correctly. The best way I knew how to accomplish it was to concentrate on one axis at a time. First adjust the offset and then the width or height.

This is what I ended up with:

1.115, 0, -0.073, 0, 1.14, -0.04, 0, 0, 1

Using nano, I created a little script and called it fujitsu_touch_panel.sh

#!/bin/sh

# Coordinate touch panel to screen

xinput set-prop “Fujitsu Component USB Touch Panel” –type=float “Coordinate Transformation Matrix” 1.115 0 -0.073 0 1.14 -0.04 0 0 1

Saved it and made it executable:

chmod +x ~/bin/fujitsu_touch_panel.sh

Then I moved it to the root directory in a location that seems to make sense… to me:

sudo cp ~/bin/fujitsu_touch_panel.sh /usr/local/bin

I tried several things to get this script to start as soon as the login screen manager, SDDM, started but that was without success. I was advised to try this location: /usr/share/sddm/scripts/. I tired several things, all didn’t work. Perhaps it just may work for someone else and if they are successful, I would be more than happy to edit this post with a better way. Feel free to comment below or contact me.

What I ended up doing was to add a script on startup of KDE Plasma.

System Settings > Startup and Shutdown > Autostart

Select Add Script… and entered the location of the script:

/usr/local/bin/fujitsu_touch_panel.sh

Screenshot_20180422_093443Next, I needed an onscreen keyboard to use. Not that I am a fan of those, as I think they are all terrible, I needed one just to be functional.

sudo zypper in kvkbd

I had to change the color scheme to Dark, because the default was not to my liking, nor was it usable.

Screenshot_20180422_093912.png

It is kind of fun putting this computer into tablet mode and poking around on it with the stylus and also makes me think about how nice KDE Plasma works with a touch interface. It certainly would have been much more fun to play with this if it were a multi-touch interface instead but still, fun and very usable. I certainly prefer a real keyboard but I see the value of this setup.

Final Thoughts

This is a fine little machine that is great for taking to less hospitable (to electronics) type of environments. The keyboard is just a bit cramped for my liking and the touchpad is a bit on the small side. The touch screen, once properly calibrated works wonderfully and even better with a stylus. I will find out this year how well they hold up in a “field” type environment and perhaps blather about that experience.

This is yet another fine case of where openSUSE just works on hardware with very little fussing about. Aside from the touch panel calibration, everything else about this machine works perfectly.

External Links

https://wiki.archlinux.org/index.php/Calibrating_Touchscreen

https://wiki.archlinux.org/index.php/Touchscreen

https://forums.opensuse.org/showthread.php/429517-Can-t-calibrate-touchscreen

HP TouchPad in 2018

HP_TouchPad_Title.png

I purchased two HP TouchPads a few years ago when they were fairly inexpensive. I wanted a larger tablet that wasn’t built cheaply. They worked great for a while but started to act up. I used them less and less until they just stopped working all together. I put them on a shelf and forgot about the for quite a while.

A buddy of mine who is still seemingly a huge fan of the HP TouchPad diagnosed that one had a main board and battery failure while the other just a battery failure. I put them back on the shelf and that is where they sat, once again. He followed up with me wondering if I bought a battery yet (keeping me accountable) to which I did not. He told me he had an extra battery and dropped it off along with the needed tools to disassemble and make the repair.

HP_TouchPad-01The guide I looked at made it seem like it would be easy to take the tablet apart, just work your way along the sides, as described and carefully separate the two halves. What seemed to be missing from the article was that you have to shim the screen from the backing to keep it from clipping itself back shut again.

Once the tablet was apart, I disconnected the halves and started the process of removing more pieces until I could get the battery out. I only ended up taking out 3 of the internal components.

Upon removing the HP_TouchPad-02.jpgUSB board, I noticed that one of the wires for the little vibrator motor had somehow broken free from the board. A fine explanation for why this unit didn’t have haptic feedback. Thankfully, my soldiering skills were adequate enough to correct the issue.

HP_TouchPad-04

There were only 4 screws retained the battery and it should be noted that once the screws have been removed, the battery will not come out easily as it is also adhered to the device. Very careful and slow removal of the battery was warranted as I learned my lesson about removing a lithium polymer battery years ago on another project. I didn’t want to rupture the sells and have a little fire or at least lots of heat and smoke.

Once I freed the battery from the case, I noticed that I could take a shortcut and remove the battery without disassembling all of the components as outlined in the guide. I freed the battery from it’s compartment, set it aside, took the new battery and using a flat tipped screwdriver, was able to insert the connector of the new battery into the board and fasten it to the tablet body.  I effectively skipped the last 15 steps of the guide I used and reassembled it.

Success… but it didn’t turn on.

I figured that the thing needed to be charged so I let it charge overnight. It still didn’t turn on and I felt obligated to let my buddy know that this TouchPad is dead and asked if he wanted the battery back. Then, he asked if I did the hard reboot, hold power and volume down for 30 seconds.

HP_TouchPad-06-Boot Loader.jpg

I did just that and immediately it went to the ClockworkMod boot loader menu. I selected the CyanogenMod image already installed on this TouchPad and I was very pleased to see that it was fully functional.

Since I wasn’t going to leave this with a 2 year old version of Android on it, I began my search for an updated ROM. There are several options out there and some of the newer versions of Android seem to have Bluetooth or camera issues. I didn’t want to have any hardware issues so I ended up going with this version here. Everything works but it is an older version of Android with security patch updates.

 

Another requirement I made is that I wanted to ensure that there were no Google Services on this tablet as I didn’t want to weigh it down with all the data scraping and mining services. All I want from this tablet is to do causal web browsing, reading ebook and PDF documents so there is no need to install the Gapps package. I also wanted to see how useful a simple de-Googled tablet would be.

F-Droid-siteSince I did want to have access to applications on this device, I installed F-Droid. F-Droid is similar to the Play Store, an available catalog of FOSS (Free and Open Source Software) Android applications. Most of the applications I want to run are available there and anything else it is possible for me to sideload or install using Yalp.

The applications I installed:

  • KDE Connect
  • Telegram
  • Syncthing
  • Fennec F-Droid, a Mozilla based web browser
  • Barcode Scanner
  • Book Reader
  • Yalp, allows you to download apps directly from Google Play Store as apk files.

Installed Using Yalp:

  • Discord
  • ASTRO File Manager

HP_TouchPad-05-apps

Modifications to improve my usage experience

I turned off the KDE Connect Telegram Notification. Not because I don’t like Telegram but because I don’t want multiple notifications on my Desktop Linux machine for the same message.

To do so, withing the KDE Connect Application on the paired device Menu > Plugin settings > Notification sync configure button, scrolled down to Telegram and uncheck it.

HP_TouchPad-07

Next, I made the KDE Connect Keyboard an input option by going into System Settings > Language & Input and checked KDE Connect Remote Keyboard

HP_TouchPad-08-Input

I set up a folder on the Tablet called Sync and using Syncthing have it tied to two of my openSUSE desktop Linux machines. It is an easy and efficient drag and drop method of putting files on the tablet instead of using KDE Connect. I figure, more options are better than fewer options for sharing data.

HP_TouchPad-10-syncthing.png

Using Dolphin in KDE Plasma to drag and drop files right on the HP TouchPad file system is such a fantastic feature. This, combined with having a folder that I can use to sync between all my systems and a shared clipboard gives me the truly practical form of desktop/mobile convergence.

HP_TouchPad-11-file manager

What I like

HP_TouchPad-09The size of this tablet is perfect for how I intend on using it. I can check things, look up things, and use it for accessing references in either PDF, ebook or my favorite resource, the openSUSE Wiki. To copy and paste from the tablet is made super easy, thanks to KDE Conenct. Copy on the tablet, paste on the Desktop. This tablet has such a nice weight and feel about and the protective folio-style case is great. I have all the functions and features I need to do what I set out with this 2011 built tablet. Sure, it is old and well past a tablet end of life but it is fast, very snappy and responsive.

What I Don’t Like

I have an outdated version of Android but with the security patches back-ported though, I do like the dark look of the older Android UI, so lets call this point a wash. The downside is, it doesn’t allow for certain newer KDE Connect features as noted here by one of the developers.

I also may have done something to disconnect the internal speakers as I don’t hear sound unless I plug into the headphone jack or Bluetooth speaker. I am not really using this for multimedia and the workaround is satisfactory.

I am not a fan of the rear facing only camera on the tablet. It also distorts the image during the “live view” but the picture itself has the proper aspect ratio. Unless if I want too take some awkward selfies, I don’t see this as a terrible issue.

Final Thoughts

I am very glad to have a working HP TouchPad once again. Is it indeed limited but I am not using it like a brand new tablet, I am using it closer to how a tablet was used 7 years ago. I am also not using this tablet like I would a proper computer as that would require a keyboard and mouse and once I have added those items, I may as well use a laptop. This fantastic little device does just what I want it to do, superbly.

Using KDE Connect and Syncthing, I can have the proper mobile/desktop convergence with my openSUSE Linux desktops in a highly practical manner anywhere I go, without the need for a third party service.

I am not sure what I will do with the other tablet now. This one is just so great, I might have to get the other one working just to keep in my cubicle. Would I recommend this tablet to someone else? For most people, probably not, unless they like to noodle around with technology.  Was it worth taking the time to fix it? Also, probably not but the satisfaction for me out of making this older yet perfectly usable hardware functional once again makes it more than worth the time and effort.

Further Reading, useful links and such

I Fix It Guide for the HP TouchPad

Tenderloin Android ROM I have installed on my HP Touchpad

openSUSE Wiki

KDE Connect Developer Nico’s Blog Post

KDE Connect Community Site

KAlarm and Kronometer | Time Applications for KDE Plasma

Time Applications

I am not a big fan of smart Phones and tablets but I do like some of the convenient, appliance-like features of a few applications. I do find that I go for my phone for the stopwatch and timer features but sometimes, I just don’t have my phone on me and need that darn stopwatch or countdown timer. I had forgotten that I used to use such things back in my Mandrake / Mandriva Linux days, before, I had a smart phone.

The two applications, Kronometer and KAlarm are in the main repository of openSUSE Leap (v15) and Tumbleweed. I also appreciate that these applications have stuck with the traditional KDE naming convention and begin with a “K”. It makes my Komputer happy.

Installation

Search in the YaST Tool or on software.opensuse.org for these bits of software to click-install or you can use my favorite method, the terminal!

sudo zypper install kalarm kronometer

They are small applications so installation won’t take long.

Kronometer

This is a stopwatch application with lap feature similar as you may have used on other devices but adds the feature to enter notes next to each line, sort by lap times, or even by the Notes column.

Kronometer-01You can save this data and “name” the current session for use or review later. To do so select Save As… and you are given a prompt to name the Session.

Kronometer-03

This will store your data as a JSON file in your home directory:

~/.local/share/kronometer/sessions.json

File > Open… will give you a list of all your previously saved sessions.

Kronometer-06

Double click on the number of one of the lines and you can bring up a previous session and continue using it. I don’t know how useful that would be but it’s nice to know it’s available.

What is pretty dang cool is that it can export into CSV format. CSV in an open format readable by LibreOffice or any other spreadsheet application where you can make pretty graphs or pie charts and so forth. In order to export the data, to CSV you have to Select File > Export Laps As… and put it someplace you will remember.

To test it out, I opened the File in LibreOffice and the title you used for Save As… doesn’t exist in the exported data. Something else to note, if you put a comma in the “Notes” field, the CSV import will put whatever was placed after that comma into another cell… hence the name, Comma Separated Values.

Kronometer-02

Over all, this is a great, basic application and very useful when needing to time something, many somethings or to collect data on a study you are conducting.

KAlarm

KAlarm is a personal alarm message, command and email scheduler built for the KDE Plasma environment. This can be useful in many ways and can also be integrated into the calendaring application, Korganizer. It has more features than you will probably need so I will just outline what I currently use.

KAlarm-01

KAlarm-02

For just a simple alarm that displays a pop up on the screen with a message and optional sound, select New > New Display Alarm and just follow down the dialog box to set your alarm with whatever constraints you wish. There are a couple neat options. One being you can add an entry in KOrganizer if you want, set Recurrences and so forth.

I like that you can make this as simple or as “exciting” as you would like to make the alarm.

There is also an option to create an alarm that will execute a command or script and log to a file. You can even have the alarm send an email at a specific time as well. The options are literally limited by your imagination.

One particular use for this application is in the kitchen. Just off the cuff, I see where I can backward plan to start different parts of dinner so that everything is done at the desired time.

Final Thoughts

These are smaller, simple applications that won’t ever see any big fanfare but, in my opinion, are extremely important and can be used to help you manage your time, track your time and so forth. I know that when I am eyeballs-deep into a task, I can lose track of time and I need to have an audible reminder to take care of some other task that is time sensitive. I am so glad that there are developers out there that take care of the small and truly needed, useful and less “exciting” applications.

External Links

KDE Plasma

Kronometer for openSUSE

KAlarm for openSUSE

 

 

KDE Connect Remote Keyboard

KDE-connect-02I recently stumbled into this cool little feature with KDE Conenct, the ability to use your desktop Linux machine as your keyboard input to your Android device. I tested this on my Samsung Galaxy S5, Moto X and HP TouchPad running Android. Assuming you have given KDE Connect a try, you may or may not have used this feature. If you haven’t tried it, you may want to see how it works for you.

I am not a fan of the touch input on tablets and phones, the input is just too slow and cumbersome, so I tend to use a laptop for just about everything. There are unfortunately a few applications that will only work on mobile devices. I do have a Bluetooth keyboard that I have connected from time to time to more efficiently use the mobile device but I don’t need another keyboard on my desktop that I would use intermittently, at best. Being able to type from my Desktop Linux machine right into my Android powered phone or tablet whenever needed is a welcome feature and far better than using the screen to touch or swipe type.

For instructions on setting up KDE Connect in openSUSE, follow this link or here for everyone else.

On the Linux Desktop side, make sure you have selected Remote keyboard from the Desktop

KDE Connect Settings-01

Screenshot_Samsung_S5_Language_InputFor your Android device(s):

Go into your Settings menu. Search for Language and input > Set up Input Method (Might be under “Default” on some Android devices)

You will then see several options, check KDE Connect Remote Keyboard to activate it as an available keyboard.

The notification drop down on the Android device, There is an option to “Select keyboard”. Assuming that the Android device is working properly, you will be able to select the input keyboard.

The Keyboard switcher is either in the in the notification drop down of which I see on my Samsung Galaxy S5, and my HP TouchPad. On my Moto X, I have an option in the global keys along the bottom to select my Input Keyboard.

Moto X Keyboard SelectorIt appears that my Samsung Galaxy notification on the keyboard doesn’t actually do anything when selected but the HP TouchPad works like one would expect. I find that the Moto X method to be the best demonstration of exposing the keyboard input selection.

Now, back on KDE Plasma (I can’t speak for any other desktop), you can input into the Mobile Device clicking on the KDE Connect icon in the System Tray and enter text next to Remote Keyboard.

As you type in this dialog, you will see the text immediately display on the connected device. I find it strangle pleasurable to type on my computer to input text on the tablet, or SmartPhone. I spent several minutes sending messages thru Telegram even though I have a Telegram client for Linux Desktop, realizing that was a bit KDE Connect System Tray-Keyboard Inputsilly, I opened the SMS app on my phone to send messages to those friends that I know wouldn’t care at all or just fire off a few pejorative comments regarding my excitement for this newly discovered feature.

I have used it several times and find this feature to be very stable, reliable and for the few days I have been using it, I can count on it to work as expected. All around, this is a great feature that is built right into KDE Plasma.

Final Thoughts

I am not sure how often I will use this feature but I am certainly appreciative to have it available. I do tend to avoid any services that lock me to a “mobile device” for communication but there are a few that unfortunately have me locked, for now. Thankfully, the hard working folks of the KDE Connect Community have been working hard to make life a bit better for those that prefer keyboards to touchscreens.

Further Reading

KDE Connect Desktop Mobile Convergence

openSUSE wiki installation and configuration of KDE Connect

KDE Connect Community Site

Albert Vaca’s blog about KDE and KDE Connect

 

 

Wii U Pro Controller on openSUSE Linux

e6440-WiiU-Pro-Controller.pngI don’t do much serious gaming on Linux but I do like to play the occasional Steam or older games in an emulator. I have historically liked the PS3 controllers in Linux. There is nothing you have to do to get it to work. Plug the dongle in a USB, pop in some batteries and away you go.

The Wii U is now a deprecated gaming console, which makes me much more interested in it. I have had one for a little while but the Gamepad digitizer has been broken for some time. I originally set out to fix the game pad but the issue with some of the buttons not working along with the digitizer, it had me thinking I should just replace the whole thing so I can start using the console. On the hunt for the replacement Gamepad, I also acquired a couple of these Wii U Pro Controllers. I wanted these in order to play this “New Super Mario Wii U” game and compare it against my favorite of the franchise. I think putting “New” in the title is a bit silly because it isn’t new now.

Upon holding the Wii U Pro Controller in my hand, it felts so good… almost perfect for my somewhat long and gangly fingers. I wanted to try out these Wii U pro Controllers on Linux, play some Steam games but fully expecting the process to be a headache; you know, because Nintendo. I made the assumption that I would have to install xwiimote to get it to work but upon reading and some further understanding of all the work some incredibly smart people have done, I only need that for the Wii Remotes. The machine I tested this on is running openSUSE Tumblweed Kernel 4.16.0 and it is my understanding that the wiimote kernel drivers have been in place since 3.1.

Setting up the Wii U Pro Controller

Screenshot_20180402_122527Nintendo chose to use Bluetooth technology in the Wii and Wii U so I started off by Pressed the Sync button on the controller and it showed when selecting Add Device on the KDE Plasma Bluetooth configuration tool. It connected, the lights stopped flashing on the controller with one solid light glowing. I checked the capabilities of the controller, to see that it was usable, in the System Settings > Input Devices > Joystick. It was just as I would expect from any other controller I own.

I opened terminal to see the kernel messages concerning this device by running: dmesg

[86905.904160] wiimote 0005:057E:0330.000B: hidraw1: BLUETOOTH HID v0.01 Gamepad [Nintendo RVL-CNT-01-UC] on 80:00:0b:82:a8:1f
[86905.904169] wiimote 0005:057E:0330.000B: New device registered
[86905.981821] wiimote 0005:057E:0330.000B: detected device: Nintendo Wii U Pro Controller
[86906.011799] wiimote 0005:057E:0330.000B: detected extension: Nintendo Wii U Pro Controller
[86906.011889] input: Nintendo Wii Remote Pro Controller as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/bluetooth/hci0/hci0:34/0005:057E:0330.000B/input/input33

Now I was excited.

I opened up Steam and started the game, “River City Ransom: Underground”, completely bypassing any of the configure input device to see what would happen. To my shock and blissful amazement, everything worked as expected. I hopped out of the game to see the controller settings and it was recognized it as a Wii U controller.

Detected Controller Wii U

I also checked out this “Desktop Configuration” setup with Steam. As long as Steam is running, I can use this Wii U controller to as an input device for controlling my Linux Desktop. I like this particular interface because I can define what each button does. This is a feature that KDE Plasma doesn’t seem to have built in and I don’t want to create an Xorg configuration for this either.

Desktop Configuration

This truly is a lot of fun to play with. Sure, it is probably just a novelty for now but I am thinking that I might want to make this a controller for my living room media machine along with the wireless keyboard/touchpad device as that is almost overkill when you just want to browse and watch some Netflix.

Final Thoughts

I really was expecting to do so more to do to get this working. On one hand I am very pleased on how easy it was to get working. On the other had I am a bit disappointed as I expected a bit of a project out of this and I was going to make the whole process “easy” and simple in a short write up. Instead, I get to tell you that the Wii U Pro Controller works great in Linux and is a great choice for modern (what little I do) and retro gaming. Best of all, no USB dongles to worry about losing!

External Links

XWiimote open-source Linux device driver for Nintendo Wii / Wii U Remotes

Wii U Pro Controller

openSUSE Linux on a Lenovo ideapad 110S Laptop

Lenovo 110S Transparent Title.pngI have a Chromebook that I have been using for causal browsing and occasional writing but the problem with ChromeOS is that is is so limited and restrictive. I installed Crouton to get a more genuine Linux experience out of it but the performance was a bit lack luster and frankly, the keyboard layout on Chromebooks is terrible. Why Google decided on such a design is beyond me. Delete, Page Up, Page Down, Home and End are nowhere to be found. When the Chroot environment is working, it’s fine but it is an Ubuntu based environment and I didn’t like the limitations that came with it. All this has lead me into the desire to get a simple, low cost but reasonably capable machine of which I would have more control. Since I have perfectly fine working netbooks, albeit a bit long in the tooth, I had no real strong demand for anything new. So, I waited for something to present itself, and it did.

I walked into Best Buy on a whim, I had some time and thought I would just see what they had available. There were several acceptable, low end machines machines between the $150 to $200 range. Specifically, a Dell that was real tempting, as it had better specifications than I really needed for my purposes but had a nice keyboard (for the price). I just wasn’t prepared to spend $200 on something I didn’t NEED. I asked the nice folks there if they had any small Nuk like computers so we walked over to the “Geek Squad” area to the returns cage (the place they keep the bad computers?) where there were a couple out of box laptops. Some where display models of discontinued models that had been re-baselined to be sold. One was marked “$86” and I was VERY interested. I asked the employee if I could just type on it, you know, to see how the thing types, as that is what I plan to do with it… type… things… He said it was against policy to power it on but they had an identical machine behind the counter running Ubuntu on it. It booted up, albeit rather slowly but the screen looked good and if Ubuntu runs on it, openSUSE would certainly run on it. The keyboard wasn’t spectacular but typed well enough to be in my “acceptable” range.

I was sold.

Lenovo 110S Scary Message-transparent
Scary Windows message

When I got the machine home, I wanted to run Windows 10. You know, see what I had been missing out on. I did a series of updates, started browsing the web with the Edge Browser, played in the control panel and so forth. I also had the opportunity to test out the Microsoft store and install a few things. Unfortunately, nothing I wanted would install. I could also only effectively do one thing at a time and it ran all herky-jerky. It was not an enjoyable experience at all, but what can you expect from an $86, discontinued computer. I would say that this laptop was not the right machine to show off what Windows 10 has to offer… But how would it run openSUSE Linux?

Specifications of this machine:
– Intel Celeron CPU N3060 @ 1.60 GHZ
– 2 GiB RAM with 1.81 GiB Available
– 32 GB SSD which ends up being 28.5 GiB
– 11.6″ – 1366 x 769 screen
– HDMI video out
– 1x USB 3
– 2x USB 2
– Micro SSD slot
– 1x 3.5mm Analog input/output

Recommended System Requirements for openSUSE:
– 2 Ghz dual core processor or better
– 2 GB system memory
– Over 40GB of free hard drive space
– Either a DVD drive or USB port for the installation media
– Internet access is helpful, and required for the Network Installer

This laptop meets 4 out of 5 requirements.

Regardless, I decided to go with openSUSE Tumbleweed as my distribution of choice for this machine and because this is not a “mission critical” machine, I also decided to play it just a bit more risky and went with the defaults of BTRFS on root and XFS on /home. Based on some discussion in the openSUSE IRC, I should use ext4 to be safe… but what fun is that. I’ll use the safe recommendations on machines I set up for other people.

Installation

To start, I accessed the Bios by pressing F2 rapidly as it started up from a cold boot. I left the machine on EFI and Secure boot. I modified the boot parameters to boot from USB
first, save and exit then completed the install process with all the defaults with KDE Plasma.

Here is the default drive layout set up by the installer:

/dev/mmcblk0p1 256M /boot/efi
/dev/mmcblk0p2 16G /
/dev/mmcblk0p3 11G /home
/dev/mmcb1k0p4 2G swap

After installation, I added a few additional packages and applications to enhance my experience: Oxygen5 (for the window decoration), Telegram Desktop, Insync (Google Drive synchronization) and Synergy. Outside of one X crash that seemingly happened out of nowhere (while writing this using Nano), I have had no issues with this machine. I want to see if I have issues with BTRFS snapshot with limited memory as I was warned about it and should I have problems or should I be problem free for an extended period of time, I will let it be noted on this review at a later date.

What can you do with an $86 laptop

More than you might expect. Since I am running KDE, which is fairly lightweight, I have a lot of memory left over with which to work. Under Windows 10, after it settled from booting up, I had about 240MB available of physical memory to do work. Nothing ran smooth, except for the menu button, that fancy Windows 10 menu popped up quite nicely and is, frankly, very pretty and fun looking. I would find it terribly annoying after a while. On KDE Plasma 5.12 with openSUSE Tumbleweed, before I installed my extras, I had about 1,458 MiB of physical memory available, according to KinfoCenter. It fluctuates a bit when it just sits so that is an approximation.

I use the default choice of Firefox for the browser as I am sure that this machine cannot handle the Chrome bloat. Watching local and streaming media is without any issue though, when streaming Netflix, the machine does dip fairly significantly into the SWAP partition. It’s nice to know this machine can handle Netflix tho that is not the reason I bought it. Running any native Linux application doesn’t seem to really tax this machine. Where I do seem to have issue is when running any multimedia heavy web site. Hopefully, browsers do indeed become more memory efficient as to make this better in the future (not holding my breath). My only real criticism of this machine is the amount of RAM. If it only had 4GB of RAM, it really could have been a great laptop for just about anyone.

Build Quality

I like how this machine is put together. It it is light but has a heavy enough of a feel that gives the impression of being sturdy and of decent quality. The keyboard doesn’t flex
under my typing and is most certainly rigid enough. The Screen articulates a full 180 degrees and doesn’t have that cheap creek or pop sound you would expect on a lower end machine. The The ports all feel like they will hold up when peripherals are inserted. The case is made of some sort of high durometer rubbery plastic that feels sturdy. I really cannot complain at all on the build quality.

Lenovo ideapad 110S_guts
Unused Mini-PCIe

It is easy to disassemble 11 screws and a few clips hold the bottom cover in place. Not much you can do under the hood. It appears that the onboard SSD is a soldered component but there appears to be what looks like an unused mini-PCIe slot. I may investigate that some other time.

The keyboard meets my needs. It is not as nice as my Dell Latitude E6440 or my Latitude D630 laptops but this will do well enough. I have experienced much worse keyboards on higher end machines so I am calling the keyboard a win. The only thing I don’t really care for is the function key row. Instead of F1 actually being F1, it actually mutes the sound. I have to hit Fn + F1 to get F1. I am sure that there is a Bios switch for it but I haven’t taken the time to look. This is only an annoyance. I am glad that F5 is refresh, regardless if you are pressing Fn.

The touchpad has two physical buttons which is a huge win. Ideally, having three physical buttons is best but having none makes for an unacceptable setup and I consider button-less touch pads utter garbage. The caps lock has an LED indicator. I can’t tell you how many times I have used laptops that only have on-screen software indicators… terrible…

Lenovo ideapad 110S 180The screen is very acceptable. Not as high resolution as I would like but how many dots do you really need? For my purposes, it is perfectly acceptable. I can see text very well in the terminal. The screen hing articulates 180°, which can be handy.

Final Thoughts

opensuse-logo2No buyer’s remorse here, I’m glad I bought it. It has almost become a daily drive for me as the thing is light and small. I can take it on the couch without worry of it falling or being inadvertently crushed by one of my kids. It doesn’t have a fan or even vents on the underside so the airflow requirements are evidently not very stringent.  The fact I can go 6 to 8 hours on this machine is fantastic.

After running this machine on with BTRFS on root, I did end up having issues with the snapshots filling up the root partition. I don’t want to do snapshot maintenance on this rather small machine so I ended up using XFS for root as well as /home. The automated openQA hasn’t pushed any updates that have killed any of my Tumbleweed machines so I am comfortable with XFS as root. One might say I should run Leap instead but I just like rolling release model very much.n

Putting openSUSE Linux on this machine made it very usable and I can’t help but think how great it is that Linux gives under-powered hardware a great lease of extended life. I would recommend this machine with openSUSE Linux on it to anyone that needs a simple Chromebook-like ++ machine.

External Links

Lenovo ideapad 110S Review