| In short, the workaround that eventually sorted it for me was to create a second profile on my phone (with the same Google Account details) allowed Google Play within that to update WebView properly. | |
| ---- | |
| Background: I had just bought a refurbished Pixel 6a, a phone that was first released about 9 months ago (https://endoflife.date/pixel) and was in the process of setting it up and bringing the software up to date and found that WebView was the only thing that wouldn't update. | |
| At first, I suspected that it was because the System Updates hadn't caught up (it requires multiple reboots, and will tend to pause after each reboot; so each time you need to go into system Settings and resume the update over there). But I got it up to May 2023 and WebView still didn't update via Google Play, despite also making sure Google Play had the latest updates (which can be done the confusing navigation of Settings > About phone > Android version > Google Play system update). | |
| Still no dice. I also tried several other sugges |
First, this page offers a nice collection of wisdom: www.boox.net/topics/bicycles/external/stein.dommel.be/brompton/sections/Tricks.html
Mine is currently five years old and it's still a fantastically compact and manoeuvrable bike. Constructed mostly of steel, so it's certainly real and durable.
Swipe left on JuiceSSH's popup keyboard to use the autocomplete input field.
I've been using JuiceSSH about a year now (as of 2018-09) with tmux & irssi and have only just realised that there's an autocorrect/autocomplete area hidden in the pop-up keyboard. >_<
I now realise the changelog from October 2014 mentions it as well as the extremely lengthy FAQ (it should probably be a second manual...), but this feature isn't made obvious through the JuiceSSH website screenshots nor discoverable design indicators within the app (think SwiftKey's red dots).
The reason I didn't read the FAQ entirely was due to its size and the apparent straightforwardness of everything else - see also: https://www.improbable.com/ig/winners/#ig2018 (Ig Nobel Prize Literature Prize for 2018)
I hereby claim:
To claim this, I am signing this object:
This is about documenting getting Linux running on the late 2016 and mid 2017 MPB's; the focus is mostly on the MacBookPro13,3 and MacBookPro14,3 (15inch models), but I try to make it relevant and provide information for MacBookPro13,1, MacBookPro13,2, MacBookPro14,1, and MacBookPro14,2 (13inch models) too. I'm currently using Fedora 27, but most the things should be valid for other recent distros even if the details differ. The kernel version is 4.14.x (after latest update).
The state of linux on the MBP (with particular focus on MacBookPro13,2) is also being tracked on https://github.com/Dunedan/mbp-2016-linux . And for Ubuntu users there are a couple tutorials (here and here) focused on that distro and the MacBook.
Note: For those who have followed these instructions ealier, and in particular for those who have had problems with the custom DSDT, modifying the DSDT is not necessary anymore - se
Mosh is a great way to overcome lag and flakey connection issues when accessing remote terminals over SSH: https://mosh.org/
Unfortunately, there's still not a lot of clear documentation for "idiots" because a lot of the existing guides assume a) "it just works", or b) you're already skilled enough to set everything up from scratch (assumed knowledge/use cases).
One of the problems I ran into for quite a long time yesterday was getting the darn thing to connect to my Google Cloud instance. I kept running into the mosh: Nothing received from server on UDP port 60001. [To quit: Ctrl-^ .] error (by the way - to quit, you have to press . after Ctrl-^ - it's not just Ctrl-^, there is a dot there too!)
FAQs and the like made vague spartan references to NATs, firewalls, iptables and the like and I tried out various commands and configurations on the se