Differences

This shows you the differences between two versions of the page.

--- doc:appunti:hardware:doogee_x93 [2022/03/14 09:26] – [Patch the boot.img partition] niccolo
+++ doc:appunti:hardware:doogee_x93 [2022/03/16 10:26] (current) – niccolo
@@ Line 1: / Line 1: @@
 ====== Rooting the Doogee X93 Android Phone ======
+{{:img:star_full.png?nolink&22|}}
+{{:img:star_full.png?nolink&22|}}
+{{:img:star_empty.png?nolink&22|}}
+{{:img:star_empty.png?nolink&22|}}
+{{:img:star_empty.png?nolink&22|}}
+| {{:img:pros_icon.png?nolink&32|}}  | **Good price**: 86 € at March 2022.\\ **Android 10**.\\ 4350 mAh **Battery**.\\ Easy **rooting**.  |
+| {{:img:cons_icon.png?nolink&32|}}  | Limited to **3G telephony**.\\ Outdated screen resolution **600x1280**.\\ **Notification LED** does not exists.\\ Battery optimization **too much aggressive**: widgets and apps are stopped.  |
 The Doogee X93 smartphone is a cheap Android phone, priced at about 86 € in March 2022.
@@ Line 161: / Line 171: @@
 ===== Termux:API problems =====
-On this phone I experienced a **[[..:android:termux_problems#termuxapi_not_working|Termux:API problem]]**. As far as I understand it is a mix of power saving features (the DuraSpeed option) and the Android customization of this phone which prevents the autostart af app at bootstrap.
+On this phone I experienced a **[[..:android:termux_problems#termuxapi_not_working|Termux:API problem]]**. As far as I understand it is a mix of power saving features (the DuraSpeed settings) and the specific Android release of this phone which prevents the autostart af apps at bootstrap.
 It seems that some steps in the right way to solve the problem are explained in this **[[https://github.com/termux/termux-api/issues/447#issuecomment-927314582|issue #447 comment]]** and in this page **[[https://bbs.blackview.hk/viewtopic.php?t=532725|Widgets not working after restart]]**.
-Basically (a partial workaround) consists in installing the **[[https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/README.md|MagiskHide Props Config]]** module in Magisk, then execute a command line procedure which will create a **Magisk boot script**, that script will use **Magisk resetprop tool** to change on the fly two options in **/system/build.prop** Android file.
+A partial workaround consists basically in installing the **[[https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/README.md|MagiskHide Props Config]]** module into the Magisk app, then execute a command line procedure which will create a **Magisk boot script**. That script will use **Magisk resetprop tool** to change on the fly two options in **/system/build.prop** Android file.
-Download the **MagiskHidePropsConf-v6.1.2.zip** file and install it from the Magisk app (Modules=> Install from storage).
+Download the **MagiskHidePropsConf-v6.1.2.zip** file and install it from the Magisk app (Modules=> Install from storage). You can find more info about the MagiskHide Props Config module here: **[[https://forum.xda-developers.com/t/module-magiskhide-props-config-safetynet-prop-edits-and-more-v6-1-2.3789228/|MagiskHide Props Config - SafetyNet, prop edits, and more]]**.
 From the Termux command line verify that **ro.hct_autostart_manager** and **ro.freeme_freemanager** properties are set to **1**:
@@ Line 177: / Line 187: @@
 </code>
+You can also check the **/system/build.prop** file using root privileges:
 <code>
@@ Line 187: / Line 199: @@
 </code>
-Using the **props** command line tool (provided by the MagiskHidePropsConf module, which requires root permissions), change that properties to 0 at **post-fs-data** stage.
+Using the **props** command line tool (provided by the //MagiskHide Props Config// module, which requires root permissions), change that properties to 0 at **post-fs-data** stage.
 <code>
@@ Line 229: / Line 241: @@
 </code>
-This workaround is not sufficient, you have also to **disable DuraSpeed** at all (with version 0.50.1 it is not possibile to disable it for Termux:API only). **After a reboot** you have to **enable and then disabled DuraSpeed again**.
+Once **rebooted**, you can confirm that the properties were changed:
+<code>
+~$ getprop ro.hct_autostart_manager
+
+~$ getprop ro.freeme_freemanager
+
+</code>
+This workaround is not sufficient, you have also to **disable DuraSpeed** at all (with Termux:API only version 0.50.1 it is not possibile to disable it for the app only). **After a reboot** you have to **enable and then disabled DuraSpeed again**.
+===== Termux:Widget problems =====
+It is not possibile to add the **Termux:Widget** to the home screen. To do so the Termux app needs the permission to **draw over other apps**, starting with Android 10. On this phone it is not possibile to grant this permission to the Termux app, the operating system denies that.