If you’re supporting an end user on Windows XP, Vista, 7, 8, or 10, and don’t want to completely log them out, you can use Run As on a Command Prompt as an administrator and then run the following:
Now edit your variables and relaunch your application. This is very useful if you find yourself needing to correct the PATH, let’s say, for Java.
I’ve been a Project Fi customer for over 2 years. We went from a Verizon bill of $140+ per month for 2 phones with 800 minutes, 100 texts, and unlimited data to Project Fi with unlimited talk and text and $10/GB on data, with an average bill of $50-55/mo. If you’re always on Wi-Fi, it’s a no-brainer.
Project Fi uses towers from Sprint, TMobile, and US Cellular, switching when the signal from the current carrier gets low. Also, Wi-Fi calling and texting works flawlessly – I’ve even taken calls over satellite Internet.
The only caveat with Project Fi is that you pay for your phone up front, and it has to be a phone that gets its updates directly from Google: the Pixel 2, Pixel 2 XL, Moto X4, Pixel, Pixel XL, Nexus 6P, and Nexus 5X.
Here’s a referral code to get a $20 credit when you join Project Fi! Redeem it at https://g.co/fi/r/JFD22V
Recently on my Chromebook running Crouton, I’ve had trouble running applications using xiwi after entering my chroot. I would receive the following error repeatedly:
write_image: Cannot find shm, moving on…
find_shm: Cannot connect to findnacl daemon. (Connection refused)
I tried re-updating my chroot, checking drivers, reinstalling the crouton integration extension, and none of those worked, but this did:
- Enter the chroot
- Run the following command: chown -R 1000:1000 “$HOME”
Apparently, permissions can get messed up and stop xiwi from functioning properly.
After sideloading Android 8.0 Oreo on my Nexus 6P, I found that Android Pay no longer considered my device secure. There’s apparently a bug in the OTA version Google posted publicly on their website, OPR6.170623.017. Luckily, the OTA that went out to most people, OPR6.170623.019, does not have this bug. You can wait for an OTA notice from Google, which might take a couple of weeks, or you can sideload OPR6.170623.019.
Here’s the download link: https://android.googleapis.com/packages/ota-api/google_angler_angler/fa6c32666b341b882089fc8e1207f435921723f9.zip
Lately, I’ve had a rash of Lenovo N22 Chromebooks that would lose their G Suite Admin Console enrollment. Re-enrollment wasn’t sticking and the next update would make them lose their enrollment.
To solve this, a full device factory reset is needed. Follow this process:
- Turn off the Chromebook. Shutdown or long holding Power are both fine.
- Press and hold Escape, Refresh, and Power for 3 seconds. Let go.
- It will come up to a screen with a yellow exclamation. Press CTRL + D.
- It will tell you to press Enter to turn OS verification off. Press Enter.
- It will restart with a red exclamation. Press CTRL + D again.
- It will transition to Developer Mode. This can take 5-10 minutes.
- At the next bootup, it will tell you that it is going to start in Developer Mode and to press Space to turn OS verification back on. Press Space then Enter.
- It will transition back to Verified mode, this will take a minute or two.
- It will boot to the Welcome screen. Connect it to the wireless and enroll it with CTRL + E.
You’re done! Now your Chromebooks shouldn’t ask for Wi-Fi credentials on bootup as if they weren’t enrolled.
Web Developers, Sysadmins, and their ilk lamented the day when Google decided to remove the detailed certificate window from Google Chrome. Now, it’s back. Here’s how:
- Put the following in the address bar: chrome://flags/#show-cert-link
- Click Enable