Differences

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

--- doc:appunti:hardware:doogee_x93 [2022/03/12 15:05] – [Factory Mode] niccolo
+++ doc:appunti:hardware:doogee_x93 [2022/03/16 09: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 82: / Line 92: @@
 adb push boot.img /sdcard/Download
 </code>
+FIXME **WARNING**: It may be prefreable to install an old version of Magisk, e.g. **version 23.0**. The main developer of Magisk switched to work for Google/Android, so some features were removed and/or revamped in newer version of the app. E.g. the **Check SafetyNet** function was removed and the **MagiskHide** feature was changed in **Enforce DenyList**. See this post explaining the developing policy change: **[[https://topjohnwu.medium.com/state-of-magisk-2021-fe29fdaee458|State of Magisk: 2021]]**.
 Using the phone file manager, install the Magisk app and run it.
@@ Line 139: / Line 151: @@
 {{.:doogee-x93:doogee-x93_factory-mode-menu.jpg?direct&360|Doogee X93 Factory Mode Menu}}
+Here you can see the //Version// screen:
 {{.:doogee-x93:doogee-x93_version.jpg?direct&360|Doogee X93 - Version}}
@@ Line 147: / Line 161: @@
 {{.:doogee-x93:doogee-x93_fastboot-mode.jpg?direct&360|Doogee X93 Fastboot Mode}}
+===== Android Fingerprint =====
+<code>
+~$ getprop ro.build.fingerprint
+DOOGEE/X93_EEA/X93:10/QP1A.190711.020/1630486559:user/release-keys
+</code>
+===== 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 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]]**.
+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). 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**:
+<code>
+~$ getprop ro.hct_autostart_manager
+~$ getprop ro.freeme_freemanager
+</code>
+You can also check the **/system/build.prop** file using root privileges:
+<code>
+~$ tsu
+.../files/home # cd /system
+/system # grep freeme_freemanager build.prop
+ro.freeme_freemanager=1
+/system # grep hct_autostart_manager build.prop
+ro.hct_autostart_manager=1
+</code>
+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>
+tsu
+props ro.freeme_freemanager 0
+props ro.hct_autostart_manager 0
+</code>
+Here it is the interactive output of **props**:
+<code>
+MagiskHide Props Config v6.1.2
+by Didgeridoohan @ XDA Developers
+=====================================
+ ro.freeme_freemanager
+=====================================
+This will set ro.freeme_freemanager to:
+The currently set value is:
+Please enter the new value.
+Pick an option below to change
+what boot stage the prop will
+be set in, or set/reset a delay:
+- Default (current)
+- post-fs-data
+- late_start service
+- Both boot stages
+d - Delay
+Do you want to continue?
+Enter y(es) or n(o)
+or an option from above: 2
+</code>
+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.