Non ci sono articoli nel tuo carrello
giovedì 21 marzo 2019 12:45:51

NLD Go4 CrystalSky Instructions

5 months ago
#126 Cita
The icon reappears with the command written above. I can not put the icon permanent.
0
5 months ago
#127 Cita
Santi wrote:
With the command su -c "pm enable dji.pilot.pad" the icon becomes un-hidden and working.

    Do not you say that solutions 1 and 2 do not work?

    Does that work permanently? because if not, it's not an interesting solution.

    Is it really necessary to enable the root user to use the modified DJI GO?

    At first, without doing anything, I tried to install NDL4122CS and run it, even though it failed, and afterwards the icon had disappeared, maybe it reappears in the same way, or not?


Well, since you refuse to install the root correctly and say you have no interest in trying I can't offer you any suggestions.
0
5 months ago
#130 Cita
CantRepeat wrote:
With the command su -c "pm enable dji.pilot.pad" the icon becomes un-hidden and working.

    Do not you say that solutions 1 and 2 do not work?

    Does that work permanently? because if not, it's not an interesting solution.

    Is it really necessary to enable the root user to use the modified DJI GO?

    At first, without doing anything, I tried to install NDL4122CS and run it, even though it failed, and afterwards the icon had disappeared, maybe it reappears in the same way, or not?


Well, since you refuse to install the root correctly and say you have no interest in trying I can't offer you any suggestions.



    My only interest is that it works a DJI GO 4 patched or not, that allows to use the changes made in my Phantom 4 Pro and in my Mavic Pro, in the Crystal Sky Ultra that I own, that's all.

    By the way, the unlocking of the height limit in the Mavic Pro, does not work, I'm afraid that is because the parameter g_config_flying_limit_height_limit_enabled does not appear in the firmware I put in order to disable the NFZ block.
0
5 months ago
#131 Cita
I tried numerous times to copy / overwrite dji.system.launcher.xml back to the folder: /data/data/dji.system.launcher/shared_prefs/. however, when open the file in /data/data/dji.system.launcher/shared_prefs/, it always comes back to the older state (<string name="KEY_MUTEX_PREF_PKG">dji.go.v4</string>)


Simply put, doesnt matter how overwrite I chose from ES File Pro, the original file always come back from cache.

Please let me know what I can do?

Thanks
0
4 months ago
#165 Cita
Binh wrote:
I tried numerous times to copy / overwrite dji.system.launcher.xml back to the folder: /data/data/dji.system.launcher/shared_prefs/. however, when open the file in /data/data/dji.system.launcher/shared_prefs/, it always comes back to the older state (<string name="KEY_MUTEX_PREF_PKG">dji.go.v4</string>)


Simply put, doesnt matter how overwrite I chose from ES File Pro, the original file always come back from cache.

Please let me know what I can do?

Thanks


Do you have root explorer turned on? Possible check the write permissions.

0
one month ago
#579 Cita
CantRepeat wrote:
Yes, I did everything and it works, I see the application. I repeated the operation three times with Es Explorer, but after the NLD422CS icon it becomes hidden.

OK, I think I see the issue.

Repeat this step before you copy the edited file back to your CS.

Start your terminal window on your CS then issue the following command


su -c "pm enable dji.pilot.pad"


This should make the app icon reappear.

Now continue with your editing of the file to add the string again.

After you edit and save the dji.system.launcher.xml file on you PC make sure it still has the new string in it. Close notepad++ and then reopen the file.

<string name="KEY_MUTEX_PREF_PKG">dji.pilot.pad</string>


Use this command to get the edited file back to your CS


adb push dji.system.launcher.xml /mnt/sdcard/Download/


After you copy the file back to /data/data/dji.system.launcher/shared_prefs/ open it on your CS and make sure the new string is in the file still.


That doesn't work. If I owerwrite corrected file dji.system.launcher.xml to folder /data/data/dji.system.launcher/shared_prefs/ and check it I found dji.pilot.pad. BUT if I only jump to other folder and then back to /data/data/dji.system.launcher/shared_prefs/  and open dji.system.launcher.xml, there are no dji.pilot.pad, but an old dji.go.v4.
0