Table of contents
- Table of contents
- Useful links
- Questions, problems and solutions
- Is it possible to upgrade from LineageOS 16 to 17.1?
- Which gapps should I use?
- I cannot find Netflix in the Google Play Store
- My bank app refuses to start because the phone is rooted
- Nothing happens when you press the Recent Apps button
- Known bugs in LineageOS 17.1 on OnePlus 3/3T
- No way to disable a SIM card when using multiple SIMs
- Solved problems in earlier LineageOS 17 builds
- GPS not working reliably
- The microphone stops working especially after making a call in apps like Telegram, Whatsapp, Skype
I own a OnePlus 3 phone and I am currently running Android 10 based LineageOS 17.1 on it. Unfortunately there is no handy (for end-users) list of known bugs and frequently asked questions for LineageOS on the OnePlus 3 and the only way to know them is to read through the LineageOS 17.1 on Oneplus 3 thread on the XDA-developers forum. The lack of such a handy list results in people asking about the same problems over and over again and this is a source of frustration for the more experienced visitors and developers in the thread, who often answer these questions in a blunt way.
Because I think such a list is really needed and lacking, I am creating one here, which I will try to keep up to date.
As the OnePlus 3T runs the same LineageOS builds the information here is also valid for that phone.
- Download LineageOS builds for Oneplus 3/3T
- LineageOS changelog
- LineageOS 17 on Oneplus 3/3T thread on XDA-developers forum
I strongly recommand skimming through the last 5 pages of this thread and using the search function before asking a question there, because people will get annoyed and give you a blunt answer if you ask about a topic discussed before.
Questions, problems and solutions
Is it possible to upgrade from LineageOS 16 to 17.1?
Even though they discourage to do this on XDA and will refuse to give you any support if you did not do a clean installation, it is actually possible. The procedure can lead to problems, so make sure you have proper back-ups and know how to use TWRP.
First make a complete back-up of your device using TWRP. I strongly recommend to back up everything, both the system partition files as the system image. While this is both the same, sometimes a restored system only boots successfully with one of them. Definitely also backup data and boot.
After a successful complete backup, connect your phone to your computer, and via the android notification that it’s charging via USB, select that you want to transfer files. Now open your device’s internal storage disk on your computer, and copy the complete backup in TWRP/BACKUPS/ to your computer. If you have TitaniumBackup, I recommend also making a complete back-up of all apps, and then copying this back-up which is stored in the TitaniumBackup directory on your internal storage to your PC. While connected to your PC, also make a back-up of your photos in the DCIM directory, because these are not included in backups made with TWRP and TitaniumBackup.
Download the following files, either using a browser in Android, either using your computer and in that case copy them to your phone’s internal storage.
- the latest TWRP
- the latest LineageOS nightly zip
- the latest OpenGapps nano
- the latest Magisk zip
- the latest Magisk uninstaller zip
- optional: the latest MadKernel
Before proceeding, reset all app permissions in LineageOS 16, because they can cause a boot loop in LineageOS 17.1 otherwise. To do so, connect your phone to your computer, enable USB debuggin in the Developer settings, and run
$ adb shell pm reset-permissions
You can also run
pm reset-permissions from a terminal on your phone.
Also completely disable AFWall+ if you have installed this. Because Android 10 adds NetworkStack (com.android.networkstack, com.android.networkstack.permissionconfig) which needs to be allowed in the firewall to get network access, you can have network problems in case AFWall+ is enabled after the upgrade. I even experienced spontaneous reboots.
Now go to TWRP and choose Install – Install image, and choose the twrp image. Choose recovery and let it flash TWRP. Then reboot your phone back into the new recovery.
Now in TWRP install the Magisk uninstaller zip. I recommend uninstalling Magisk completely because sometimes it results in boot loops. Then flash LineageOS 17.1 and OpenGapps, then wipe cache and dalvik cache, and reboot. If all goes fine, you can boot back in TWRP and flash Magisk and optionally MadKernel.
If you end up in a boot loop (the boot appears to hang on the boot logo and after a long time returns to TWRP with message RescueParty), go back to TWRP, choose Wipe – Advanced wipe, and wipe system, boot, cache and dalvik. Then Install LineageOS and OpenGapps zip and reboot.
If all this fails, restore the backups you made.
In LineageOS 17.1, I recommend starting up all programs and giving them back the permissions they need. This is particularly important for the Clock app, in order to make alarms work fine. Before enabling AFWall+ again, make sure you allow NetworkStack.
Which gapps should I use?
Use OpenGapps nano. Never use any of the more complete packages, they will cause problems. Install the missing Google applications afterwards from the Play Store.
I cannot find Netflix in the Google Play Store
When you go the Settings in the Play Store app, under Play Protect certification you will see that your device is not certified.
To solve this, flash the latest Magisk zip in TWRP. Then back in Android go to Settings – Apps & Notifications and there go to Play Store App-Info. Go to Storage and there clear the cache and the storage. Now restart your phone. If you go to the Play Store settings, you will see that the message that it is not certified is gone, and you will be able to install Netflix. After clearing the storage, verify that the Play Store settings are OK for you, because these will have been reset.
Android Gadget Hacks: Fix Play Store Uncertified Errors When You Forget to Flash Magisk
My bank app refuses to start because the phone is rooted
Flash Magisk in TWRP. Then Start Magisk Manager and tap on SafetyNet Check. It should return Success and a green check mark for both CtsProfile and basicIntegrity. Then in Magisk’s menu go to Settings and make sure Magisk Hide is enabled. Then in the menu go to Magisk Hide and enable it for your bank app and for Google Play Services. If it does not work yet, try to remove data and cache of your bank app and reboot. Then try to reconfigure your account.
Nothing happens when you press the Recent Apps button
This happens when you use a different launcher than the default Trebuchet launcher (for example Nova Launcher or Lawnchair) and have frozen Trebuchet. Unfreeze Trebuchet. In case you have completely uninstalled Trebuchet, reflashing LineageOS should bring it back.
Known bugs in LineageOS 17.1 on OnePlus 3/3T
No way to disable a SIM card when using multiple SIMs
In LineageOS 16.0 it’s possible to disable one of the SIM cards if you have two SIMs installed. In LineageOS 17.1, the only way to disable a SIM is to physically remove the card from the slot.
This problem is not OnePlus 3/3T specific: it is like this in all LineageOS builds for all devices, and is a deliberate choice by the developers, because it was too hard to implement this for Qualcomm devices (“it’s not a bug, it’s a feature”).
Solved problems in earlier LineageOS 17 builds
GPS not working reliably
Getting a GPS fix took a long time or was even impossible in build before 13 July 2020. Update to a recent build, and try to clear A-GPS data with an app like GPS Status if you experience this problem.
The microphone stops working especially after making a call in apps like Telegram, Whatsapp, Skype
After making a call in a VoIP application like Telegram, Whatsapp and Skype, the microphone only works in calls but not in other applications. This means the microphone does not work when recording video, when recording voice message in different apps, Google Assistant stops listening to commands, etc. The phone needs to be rebooted to make the microphone work in all apps again.
This bug was fixed by this merge request which is included in nightly build 20200831 and later (31 August 2020) and the solution was confirmed on the XDA developers forum.