doc:appunti:hardware:blackview_bv5300_pro_change_launcher
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| doc:appunti:hardware:blackview_bv5300_pro_change_launcher [2024/08/12 06:49] – [Lawnchair] niccolo | doc:appunti:hardware:blackview_bv5300_pro_change_launcher [2024/08/26 12:53] (current) – niccolo | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Changing the default launcher on the Blackview BV5300 Pro ====== | ====== Changing the default launcher on the Blackview BV5300 Pro ====== | ||
| - | I have a **[[blackview_bv5300_pro|Blackview BV5300 Pro]]** smartphone; I managed to root the phone to gain administrator privileges and now I want to change the default Blackview launcher which is called **BvLauncher**. | + | I have a **Blackview BV5300 Pro** smartphone; I managed to [[blackview_bv5300_pro|root the phone]] to gain administrator privileges and now I want to change the default Blackview launcher which is called **BvLauncher**. |
| - | + | ||
| - | The main reason for using a different launcher is because BvLauncer has a bug preventing | + | |
| - | + | ||
| - | I suspect also that the Blackview | + | |
| + | The main reason for me using a different launcher is because BvLauncer has a bug preventing to disable the **At a Glance** widget. Another bug prevents the resizing of widgets, e.g. I cannot have a 3x3 [[https:// | ||
| + | I suspect also that the Blackview launcher is somewhat a spyware, because the phone tries hardly to prevent you from choosing another Home app the app is always restarted even if you force-stop it (the same apply to the other Blackview launcher, called **DKGameMode**). | ||
| ===== Lawnchair ===== | ===== Lawnchair ===== | ||
| - | Obviously I want an open source launcher, so I ignored the plethora of launcers available on the Google Play store. In the past I used the **[[https:// | + | {{.: |
| + | Obviously I want an **open source** launcher, so I ignored the plethora of launcers available on the Google Play store. In the past I used the **[[https:// | ||
| Then I came across **[[https:// | Then I came across **[[https:// | ||
| Line 19: | Line 18: | ||
| ===== QuickSwitch ===== | ===== QuickSwitch ===== | ||
| - | FIXME | + | After installing Lawnchair I set it as the **default Home app**, from the Android Settings. The first problem I encounterd was that setting the Home app do not survive a phone reboot: after a restart the Home app is restored to the stock BvLauncher. Another problem is that **the //Recents// provider** (the list of opened apps accessible through the soft navigation button of Android system bar) remains set to BvLauncher, where it sould be provided by Lawnchair itself. As far I can understand, in newer Androids the //recents provider// must be a **//system app//**, while Lawnchair is installed as a normal user app. |
| + | |||
| + | {{ .: | ||
| + | To solve this problem I installed a Magisk module called **[[https:// | ||
| + | |||
| + | QuickSwitch was created to permit the user to choose the //recents// provider on Android 9+, the module also promote the selected launcher as a //system app//. You install the zip file from the //Modules// icon of the Magisk app; once installed and rebooted, you will find the QuickSwitch companion app. Launch it and you will see a list of //recents// providers (the stock BvLauncher and the installed Lawnchair in my case). I selected Lawnchair and the app configured the Magisk modules accordingly: | ||
| + | |||
| + | **NOTICE**: To work properly I had to install **QuickSwitch 4.0.3**. The previous version 4.0.2 worked only partially: it moves the launcher as a system app, but it cannot set it as the recents provider, which remains stuck to the stock BvLauncher. | ||
| + | |||
| + | **NOTICE**: QuickSwitch installs iteself as a Magisk module, you can find it into **/ | ||
| + | |||
| + | If you have a shell on the device, e.g. the Termux terminal, you can **configure the module on the command line** instead of using the companion app. Open the terminal and execute as root: | ||
| + | |||
| + | < | ||
| + | / | ||
| + | </ | ||
| ===== De-Bloater ===== | ===== De-Bloater ===== | ||
| - | FIXME | + | **[[https:// |
| + | |||
| + | It comes in the form of an app, which requires a device rooted with Magisk. When you launch it, you can select one or more apps to be hidden. Actually **the system partition is not modified** and the apps remains installed. A Magisk mudule is installed instead which - at boot time - makes some // | ||
| + | |||
| + | When you //remove// an app with De-Bloater, it detects if it is a system app which received an update. This means that the app is installed actually twice: the original one into the system partition (which is not deletable) and the update into the user partition. In this case De-Bloater suggests you to delete the update before, so De-Bloater will disable the original one only. | ||
| + | |||
| + | Having installed Lawnchair as an alternative Home app and recents provider, I can hide the stock **BvLauncher** app so that the com.blackview.launcher process would no longer execute. The same is for the **Game mode** (DKGameMode.apk), | ||
| + | |||
| + | When you //remove// an app with De-Bloater, the De-bloater Magisk module is updated creating a dummy file which will override the actual app into the running system at next reboot. The dummy file contains just the name of the app removed. If you //restore// the app in De-Bloater, the dummy file is removed. | ||
| + | |||
| + | Now that I understand how De-Bloater works, I prefer to configure it manually (be sure to remove the app update and check the installation path before removing it by hand). To hide **DKLauncher** and **DKLauncherOverlayFramework** I create two files in **/ | ||
| + | |||
| + | <code bash> | ||
| + | mkdir -p / | ||
| + | mkdir -p / | ||
| + | echo " | ||
| + | > / | ||
| + | echo " | ||
| + | > / | ||
| + | </ | ||
| + | |||
| + | After a reboot, this has the effect to disable entirely the two packages (apk files). Indeed BvLauncher was gone completely and my only Home app is Lawnchair. | ||
| + | |||
| + | The following is the list of the app I have hidden (actually this is a merged list of apps that I have de-bloated from Android 12 and Android 13 customized by Blackview): | ||
| + | |||
| + | < | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | </ | ||
| + | |||
| + | ^ Google | ||
| + | | AndroidAutoStub.apk | ||
| + | | Drive.apk | ||
| + | | Duo.apk | ||
| + | | FilesGoogle.apk | ||
| + | | FindMyDevice.apk | ||
| + | | GoogleFit.apk | ||
| + | | Keep.apk | ||
| + | | Photos.apk | ||
| + | | UserGuide.apk | ||
| + | | Videos.apk | ||
| + | | Wellbeing.apk | ||
| + | | YTMusic.apk | ||
| + | ^ Blackview | ||
| + | | DKApkUpdate.apk | ||
| + | | DKChildMode.apk | ||
| + | | DKDarkModeOneOverlay.apk | ||
| + | | DKDarkModeThreeOverlay.apk | ||
| + | | DKDarkModeTwoOverlay.apk | ||
| + | | DKFeedback.apk | ||
| + | | DKFileTrans.apk | ||
| + | | DKFmRadio.apk | ||
| + | | DKFrozenApp.apk | ||
| + | | DKGameCenter.apk | ||
| + | | DKHealth.apk | ||
| + | | DKLauncher.apk | ||
| + | | DKLauncherOverlayFramework.apk | ||
| + | | DKLeftScreen.apk | ||
| + | | DKLiveWallpaper.apk | ||
| + | | DKNoteBook.apk | ||
| + | | DKRadioService.apk | ||
| + | | DKWeather.apk | ||
| + | |||
| + | ===== Download ===== | ||
| + | |||
| + | ^ Resource | ||
| + | ^ QuickSwitch v4.0.3 | ||
doc/appunti/hardware/blackview_bv5300_pro_change_launcher.1723438159.txt.gz · Last modified: by niccolo