Here’s how to re-map the default Calculator keyboard “shortcut key” to instead send the Play/Pause media command under Windows 10; alot more useful!
This guide is aimed at the Amazonbasics Wired Keyboard but applies to any keyboard making use of the standard Windows media/shortcut key codes. A requirement is that you are using a supported media player including iTunes, Spotify, Windows Media Player or VLC.
- Download Command Line Media Controller (it’s free) and copy it to the Program Files (x86) directory
- Open up the Registry Editor (regedit64.exe) by clicking the Start button and typing regedit into the search bar
- Expand Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\AppKey\18
- Create a new String with the Value name: ShellExecute
- Set the String Value data to: “C:\Program Files (x86)\Command Line Media Controller\CLMControl.exe” Spotify -pp
- Click OK
That’s it! Hit the Calculator keyboard shortcut with Spotify open and it will toggle play/pause. Happy listening! 🙂
I brought my XPS 15 9550’s hard disk back from the brink today. I hope this will help other affected XPS 15 9550 users or just Windows users in general.
The XPS 15 9550 was powered down as usual and on reboot would go directly from the Dell POST logo to the Dell diagnostic software (Enhanced Pre-Boot System Assessment). That’s not a good sign.
After running through common diagnostic steps with Dell Support a new hard drive was ordered and installation scheduled for the following day (unit was covered under a Next Business Day support contract). As Dell Support put it the hard disk was dead without any chance of recovery… or was there? 😉
Here’s how to recover your Windows instance in the case where the hard disk hardware is still being detected and simply has no UEFI boot entries:
- Open BIOS Setup by powering up the XPS 15 and tapping F12
- Open the Settings > General > Boot Sequence screen
- Ensure that UEFI is selected under Boot List Option
- Click Add Boot Option
- Provide a Boot Order Name (it can be anything, I used
- Select the available File System List
- Set the File Name to:
\EFI\Boot\bootx64.efior click the ‘…’ button and expand the EFI > Boot directory and select bootx64.efi before pressing OK
- Click OK to create the new EFI boot entry
- Select the new EFI boot entry
- Click Apply
- Click Exit
Fingers crossed! That’s it, I hope you’re back up and running again. 🙂
Here’s a walkthrough for setting up the Xiaomi Plant Flower Care BLE device on an Android device.
- Unpack the device from the packaging
- Install the free Mi Home App (Google Play Store/iTunes App Store)
- Turn Bluetooth on your Android device
- Open the Mi Home App
- Sign in or create a new Mi Home account
- From the opening My Devices screen click the top right “+” (plus) symbol
- Select “Add device” from the dropdown menu
- Pull the exposed plastic tab from the Xiaomi Plant Flower Care device to turn it on, if you have previously done this open the cover and unset/re-set the battery
- When the “Flower care” device appears select it
- Wait while the Bluetooth connection is established and the latest device firmware is installed
- From the initial Devices tab select the Flower Care device
That’s it! You’re good to go!
I’ve had my XPS 15 9550 almost 18 months now, here’s my replacement history so far… all covered under Dell’s Premium Support NBD contract:
- 5 motherboards
- 1 battery
- 2 CPU fan
- 2 graphics card fan
- 1 heatsink
- 1 keyboard
I can put at least 3 of the above motherboard replacements down to me telling them “the CPU fan is too loud” which was blamed by Dell Support and on-site technicians on issues with the motherboard and promptly replaced.
The fix for the loud CPU fan – especially when a Thunderbolt device is connected – is to turn on passive cooling within Power Options and using Intel XTU undervolt the CPU 0.100 V dramatically lowering the thermal profile of the XPS 15 9550 followed by setting Dell Command Power Manager to Quiet.
Today I have a silent machine with no noticeable effect on daily usage or CS:GO gaming performance, that’s with 2 Dell U2414H monitors occupying the HDMI and Thunderbolt connectors. I have multiple Chrome tabs open (10+), Slack and other typical CPU hogs running without the CPU fan attempting to rise off the desk.
Here’s how to fix the loud CPU fan on the Dell XPS 15 9550:
Part 1: Turn on passive CPU cooling
- Right click the battery icon in the start taskbar
- Select Power Options
- Click Change plan settings beside the Balanced power plan
- Click Change advanced power settings
- Expand the Processor power management list
- Expand the System cooling policy list
- Set the On battery and Plugged in options to Passive
- Click OK to save changes
- Click Save Changes on the Edit Plan Settings window to save changes
Part 2: Undervolt the CPU 0.100V
- Download the Intel Extreme Tuning Utility from the Intel website
- Install and open Intel Extreme Tuning Utility (ala Intel XTU)
- Open the Advanced Tuning > Core section
- Find the Core Voltage Offset slider
- To the right of the Core Voltage Offset slider hover over the 0.000 V value to show the decrease/increase toggles
- Click the decrease toggle until the Core Voltage Offset indicator shows -0.100 V
- Click Apply
- Close Intel XTU and restart the computer
Part 3: Dell Command | Power Manager
- Download and install Dell Command | Power Manager from Dell’s website
- Open Dell Command Power Manager from the Start menu
- Switch to the Thermal Management tab
- Set the Thermal Setting to Quiet
That’s it! 😀
By default Mazda Connect’s Watchdog service restarts the CMU on any error, to the general public this is a god send as the Watchdog resolves common issues by rebooting the system (e.g. Navi going silent, any screen lock-ups, etc.) but for developers this can have the unintended action of locking us out of SSH access from a simple mistyped character.
Here’s how to turn the Mazda Connect Watchdog service off, keep in mind this command only persists until the Mazda Connect system is rebooted (e.g. after turning the engine off for a short period of time).
echo 1 > /sys/class/gpio/Watchdog\ Disable/value
You can check if the Watchdog service is now inactive by running:
cat /sys/class/gpio/Watchdog\ Disable/value
There are ample instructions online for how to set up the above command to persist even after rebooting but I won’t provide this here.
That’s it! 🙂
Locked yourself out of SSH/SFTP access on Google Cloud Compute Engine? Does the below look familiar… Fun times…
Status: Connecting to domain.com... Status: Connecting to domain.com... Response: fzSftp started, protocol_version=8 Command: open "...@domain.com" 22 Error: Server sent disconnect message Error: type 2 (protocol error): Error: "Too many authentication failures for ... from 18.104.22.168 port 7145 ssh2" Error: Could not connect to server
Here’s how to increase the number of allowed login attempts within sshd_config and then restart the sshd service so you can get back to work. 🙂
- Open up Google Cloud Console
- From the Menu button open Compute Engine > VM Instances
- Beside your Compute Engine instance hit the SSH button within the Connect column
- When your terminal connection is established enter the following:
sudo nano /etc/ssh/sshd_config
- By default the sshd_config file does not have a MaxAuthTries entry but scroll through the file using the up/down keys and check just incase…
- I set the maximum number of login attempts to 10, change this number to suit your security needs. Add the following lines anywhere within the sshd_config file:
# Max login attempts MaxAuthTries 10
- Save and close the file by using the following keyboard combinations:
CTRL+O followed by the enter key to save the file changes CTRL+X to close the Nano file editor
- Reboot the sshd service using the following commands (I’m not sure which one works so let’s do all of them…)
sudo service sshd restart sudo systemctl restart sshd
- Try and reconnect to your Compute Engine instance using Putty (SSH) or Filezilla (SFTP)
That’s it 🙂
Following on from Fixing Installation Failed message on Bitnami WordPress and Google Cloud Compute Engine I recently tried installing WordPress within Google Cloud Platform using Google Click to Deploy.
As always the installation and initial setup is a breeze, open up Google Cloud Platform and within the search bar type in “WordPress”, one of the available options is called “WordPress – Click to Deploy”, select that then enter the following details:
- Deployment name (this cannot be changed so think about it…)
- Zone (where you want your instance to exist; us-west1-b is my favourite)
- Machine Type (small 1 shared vCPU is plenty to start with and can be changed at any time without affecting site downtime)
- Administrator E-mail (your e-mail address)
- whether you want phpMyAdmin installed (if you’re using WordPress then this is very handy to have access to)
- Disk type and size (Standard Persistent Disk and 10 GB is plenty to start with)
- Automatic firewall rules for HTTP/HTTPS traffic (turn this on or you’ll need to do it later)
Then hit Click Deploy and away it goes, a minute or so later a set of logins are provided including a default admin WordPress User and login details, if phpMyAdmin was selected a default root User login is provided.
By default a dynamic IP is allocated to your WordPress instance so you’ll need to open Menu > Networking > External IP address and change the type to Static for persistent WordPress sites.
If you intend to manage your WordPress site via SFTP (FTP over SSH) then you’ll need to adjust your SSH user so that it can create and edit files within the base WordPress directory, to do this open the Google Cloud Shell within your WordPress instance by opening Menu > Compute Engine > VM Instances > under the Connect column beside your WordPress instance click SSH.
id sudo useradd -G visser www-data
(replace visser with your SSH user name displayed when you enter id)
Adjust the file permissions and ownership of wp-config.php within your base WordPress directory then create a new .htaccess file.
sudo chown www-data wp-config.php sudo chgrp www-data wp-config.php sudo chmod 664 wp-config.php sudo touch .htaccess sudo chmod 664 .htaccess sudo chown www-data .htaccess sudo chgrp www-data .htaccess
Lastly let’s change the WordPress URL from the IP address allocated (e.g. http://22.214.171.124 to http://visser.io) and turn on Permalinks.
To change your WordPress URL open the WordPress Administration using the logins provided when your WordPress instance was created then open the Settings > General screen. Change only the WordPress Address (URL) field to your preferred URL – do not change the Site Address (URL) field – then hit Save Changes.
To enable Permalinks open up the General > Permalinks screen, within the Common Settings section change the radio button selector to Custom Structure and within the text input field paste the following (or your preferred Permalink structure):
Hit Save Changes to apply changes.
That’s it 🙂
After a recently purchased Philips Hue White bulb died on me this past week I went about contacting the Philips Hue support team regarding a replacement. After a fortnight of different support channels (website, Facebook, phone, e-mail…) my local Philips Lighting supplier – Philips Lighting Australia Ltd. – declined a replacement and has pointed me to the Philips Lighting US team. The saga continues…
Here’s what I learned and why I now have two Philips Hue White bulbs gathering dust due to the potential of a safety risk… not cool Philips Lighting.
First off, if you have been silly enough to purchase Philips Hue bulbs from Amazon.com or another US-based online marketplace and had products sent internationally where 110 VAC electricity is not used (e.g. everywhere) stop using those products and contact the Philips Lighting US team for a replacement.
Here’s the interaction with my local Philips Lighting team:
From the markings it looks to be a US bulb. These would run on 110v and not 240v and therefore and not usable outside of the US. It would be best for you to check all bulbs for the voltage range printed on the bulbs and if it does not say 220-240v you should stop using them as it could have the potential of a safety risk.
Unfortunately this would also mean that we could not replace them under warranty since we accept claims/complaints only for products sold by us in Australia.
– Customer Order Manager, Philips Lighting Australia Ltd
- Philips Lighting teams will only accept claims/warranties for products sold by their company in that given country (e.g. a Amazon.de purchase from Philips Lighting DE will not replaced by Philips Lighting AU).
- Philips Lighting teams have no trade or express direct contact with other teams. You as a consumer must reach out to the Philips Lighting team where your product was purchased (e.g. in my case buying from Amazon.com means the US team and track them down).
- Philips Lighting teams (e.g. the Philips Lighting US team selling on Amazon.com) are aware that customers are using their products internationally and not informing prospective customers or restricting international sales knowing of the potential safety risk when using their products in non-US markets.
The first two points I understand. The last riles me up and is reason for this Post. Lift your game Philips Lighting!
Knowing the above I now source Philips Hue products from local suppliers, currently Apple.com/au/… are the cheapest online retailer with free shipping in Australia and they have confirmed via pre-sales support to only sell international Philips Hue products rated for 220-240V at 50/60Hz and safe for use in non-US markets. I have since purchased multiple bulbs from Apple.com/au/… and all have been internationally rated.
I will forward the following post to Philips Hue Facebook team for comment as that is the only online channel that seems to respond to customer queries and if possible return my Philips Hue White US-bulbs as I have no further use for them.
- Visit the Mazda Connect update website
- Click the Download Mazda Toolbox menu link
- Click the Download for Windows button *1
- While the download is running click the Register link from the top menu to create a new Mazda Toolkit user account
- Open the confirmation e-mail and hit the link to verify your user account
- Open the installer once it has completed downloading (~20MB) and run it
- Retrieve the SD-card installed in your Mazda 3 from the center console, above the USB ports; it is protected by a rubber holder
- Insert the SD-card into your computer and ensure it is detected as a hard drive
- Open Mazda Toolbox from your computer
- Click Login from the opening screen using the user details entered above
- Click Available Updates to check for new map updates
- Click Install if a new map update is available
- Click Backup to save a backup of the existing map files on the SD-card
- Click Updates to load the latest map files onto the SD-card, be patient, this can take awhile…
- When the download and transfer is complete hit Exit to close Mazda Toolkit
- Remove the SD-card from your computer and re-insert it in the SD-card port of your Mazda 3
- Press the Start engine button once to initialize the infotainment system
That’s it! 🙂
*1 If you’re using a Mac then hit the Download for OS X button