Selection | Checkout | Setup | Apps | More Info | Top |
Currently (2021-06-30), Selen has LineageOS 17.1. It needs to get upgraded to 18.1, which has been out for several months. The update nanny checks periodically (every few days) and notifies you when a new minor revision comes out, or you can launch it from Settings-System-Advanced-Updater (all items are at the bottom of their containers).
According to the Info
link, the updater cannot install this
version because it can't do major version upgrades. See
the Pioneer
upgrade page for instructions. Jimc's notes (with supplements) on the
procedure:
LineageOS-18.1 is based on Android-11. (17,1 from Android-10.)
This procedure is similar (but not identical) to installing LOS for the first time. The main difference is, assuming you have the old version of Google Apps installed already, you don't wipe data.
I plan to install an instance of LOS that is two to three weeks back version, then immediately update it to the current version, using the updater, to learn and gain confidence in the procedure. Then I can install ongoing minor updates.
Download the LOS install package. to your desktop machine. (See the link on that page for how to check the signature.) You will need …nightly-pioneer-signed.zip (about 620Mb, varies from week to week). As this is written, the latest version is dated 2021-06-24 and I'm downloading 2021-06-10. It's all going into jacinth:/s1/selen-los-18.1. …recovery-pioneer.img (about 22Mb) is available and may be needed for some screwup recovery, but I did the whole upgrade without using it.
For verifying the zip file (but not the recovery image), the
linked-to page gives these instructions:
git clone https://github.com/LineageOS/update_verifier
cd update_verifier
pip3 install -r requirements.txt
python3 update_verifier.py lineageos_pubkey /path/to/zip
Jacinth lacked pip and its friends. With OpenSuSE Tumbleseed,we
have python38, and so should install python38-pip. Once installed, the
command pip3
(among other variations) can be used to install
requirements.
The zip file was verified successfully
.
Now we need
Google Apps for arm64 (not plain arm), the nano
collection. (It
does not include e.g. Google Maps, which you can install/update later
from the app store.) The linked-to collection, size about 185Mb,
has no variants differentiated by size, and I'm assuming this is the
right one. Almost certainly OK, because the one I got from Open GApps
for LOS-17.1 is the same size. (No checksum is posted.)
Checking and initting ADB:
adb devices. On Selen confirm ADB access. Jacinth's adb prints
XXXXXXX device(with Selen's unique identifier).
adb root. Confirm on Selen. No error messages; I'm pretty sure Selen's adbd was successfully restarted su'd to root.
On Jacinth: adb reboot sideload
What it did: 10sec black, relock bootloader
(ignore it),
Sony splash screen, LOS Recovery (shows ADB Sideload in red). You
don't have to click it; the message at the bottom of the screen
says to…
On Jacinth, adb sideload ./lineage-18.1-20210610-nightly-pioneer-signed.zip It downloads the package very fast, then verifies it (slow), Progress report only goes up to 47%. Installing. Finished after 190sec.
Do Not accept the suggested action Reboot System Now
.
You still need to sideload Google Apps. Follow these steps:
adb sideload $file.zip).
Signature verification failed; install anyway?This time I'm going to tell it yes. Cross fingers. We're still in slot A. On LOS-17.1 I switched over to TWRP Recovery, installed GApps, and the signature was verified, but associated thrashing made a mess that I didn't want to repeat. Experience testing the Google Apps was positive, although a truly paranoid sysop would not touch a package whose signature could not be verified.
Reboot System Now.
First boot of the new image: 34:10. Black for 5sec, unlock bootloader, Sony, 34:44 LOS boot animation to 35:56 (72sec), it's alive!
Let it go through autonomous initialization steps. Then attend to immediate notifications:
Updating apps for LOS 18.1 (Android 11 Radish
).
Manage Apps. It checks inventory. 2 updates available. Click on
See Detailsand review them.
Before I do a lot of work checking out stuff, I'm going to run the updater and install the latest minor version. Remember that I did the major upgrade with a slightly back-version instance. Launch updater. Clock on Download for the version you want. Download is taking a long time to start, but eventually got to 1%. Speed of arthritic snail. Image size is 653Mb. Confirmed (with tcpdump) that it's downloading over Wi-Fi, not cellular data. 86kB/sec (with 28% downloaded), predicted total 7593sec, 2.1hr. I didn't get a precise completion time but elapsed time was about 2 hours. In the future, when I'm going to update I'll start the download at bedtime. (A later minor update took only about 3min to download.)
Well, given how slow the download is going, I'm going to check out user apps now. These are everything in the app drawer. (There are core apps that are not launchable by the user, which are not going to get tested.) 82 launchable apps + 15 infrastructure, 97 total. Legend of decorations:
jelly) -- Not tested, don't add a profile and browser cache for an app I'm not going to use.
30with 2 red dots) (LO
etar) -- Not bad, but I like aCalendar better.
snap) -- Works, a cursory run-through suggests that it's pretty complete, but I'm used to OpenCamera.
Home(for an e-mail address) on Selen ends up as
Interneton ownCloud.
profileon Gmail, which I didn't do, and to post emergency information.
nanocollection of Google Apps.)
eleven) -- Works, but it either doesn't recognize Ogg Vorbis tracks or couldn't find the onboard music.
feature.
Cannot access the Android Keychain Certificates… because of a firmware upgrade…I re-selected the certs. However, it cannot read the keychain at all!
Donatedby Google. Works.
To-do list for the apps:
Fixed:in the upgrade the keychain was wiped, and the apps choke on an empty keychain.
Fixed
After the upgrade to Android-10 (LOS-17.1) and continuing into the upgrade to Android-11 (LOS-18.1), my various GPS apps have stopped working, excepting Google Maps (which may be using cell tower tricks).
Conclusion first: There's nothing wrong with the GPS apps or with the Location service component that handles GPS. Probably starting with Android-10, the GPS driver has become more picky about signal strength, and when signals are poor, as on the ground floor of a house, the GPS lock drops out or is never established. When the ionospheric gods smile on us, GPS works just fine.
Here's an intervention that was helpful for Jimc.
GPS not working with Android 10 (on Reddit), OP davalf, about
2020-02-xx. All his apps can't get a GPS lock. None of the usual
interventions helped. So there's apparently an app called
GPS Locker in the Play Store.
Disable mobile data, run the app,
then reenable mobile data. (Jimc got a good result without monkeying
with mobile data.) But it keeps GPS running, hence eats
battery.
I tried gps locker
by SilentLexx UA (ad supported, $1.99 to lose the
ads). A competitor, which I didn't try, is GPS Connected
by Diogo Ferreria.
It has a nice display of the signal strength per satellite.
By holding open the connection to Location Service, it causes that
service to maintain state and therefore to quickly :-) get back a lost
GPS lock, assuming enough signal.
Numerous forum posters report interventions whose major component seems to be clearing data (cache included) of the Location service, now called Fused Location in Android-11. But GPS doesn't stay fixed. This is the best of these posts:
On XDA-Developers, OP gigaboss (2019-09-28) says, ever since I updated my phone [to Android-10] the GPS is not working… Respondent noobly_dangers had a similar issue but fixed it like this: Go to Settings-Apps&Notifications-See all. Click the traffic light (3 dots) in the upper right corner, tell it to show system apps. Click on Location Services. [It's Fused Location in Android-11.] Force stop, and clear cache and storage for this app. Reboot the phone. He thinks cached Android-9 data was messing it up.
Jimc tried this in LOS-18.1 (Android-11): it revived GPS and lasted about 14 hours, just in time for me to try to run my Jog Tracker app and fail. On the first try after you clear data, it will take about 30sec to the first fix because it has to download the ephemeris.
Here's another intervention: Samsung Support: What to do when GPS is hosed (2020-11-03) (title paraphrased). Among many interventions not relevent to this problem, this one looked useful: Settings-Location-App Permissions. Select each wanted app and set it to Allow All The Time.
Jimc's experience with this fix in Android-11: Use Location
should be on. Click on App Access to Location for a list of all of
them; there's also a list of recent culprits. Some including Google
Maps have permission to use location at all times. Others have
permission only when using the app
. Click on an app. You can
downgrade permissions, but can't upgrade them. Jimc found that
fiddling with permissions did not bring GPS Status back to life.
Open Settings-System-Advanced-Updater. Hit refresh if nothing is shown.
Pick a version, normally the latest one, and hit Download. The first
time I tried this it was glacial, taking 2hr, but the next version
came in much faster, 3min. The downloaded instance
is now marked Install
. Click the button. Confirm doing
the update. It will do the installation in the background. There's a
progress bar on the settings page, plus a notification (if you close
the settings app). Installation took about 7min; it wants to reboot.
It took about 150sec to reboot (which is usual; it's recompiling Java
bytecode). There's a post-install phase when the phone finishes
rebooting, 30 to 60sec, all in the background; there's a notification
for it. Total elapsed time was about 10min. Remember to delete the
downloaded file after installation; the updater's item will have a
Delete
button.
Selection | Testing | Setup | Apps | More Info | Top |