[HowTo] Disable or Change the Sedentary Alert on Verge - Amazfit

At least since Chinese firmware v3.0.41.0 it seems that if you set the interval to display the sedentary alert to zero it is actually disabled. You can also set other values to suit your needs:
Open watch Settings
Scroll down and tap About
Find the row that shows the Serial Number (Serial No.) and tap it many times: you should see a countdown to show the hidden "Lab" menu
Once Lab is visible at the bottom of the About screen, open it and search for "Time of sedentary reminder" and tap to open it (do not use the other options unless you know what you are doing or you might end needing to restart the watch using the button or worse)
Set the value to zero, if it isn't already, swipe left to show the green button and tap on it to save, you should see a confirmation message
Swipe right to go back and close settings

Verge 3.2.5.0 Stock ROM Global - don't working, there is no step 4

MoronsHater said:
Verge 3.2.5.0 Stock ROM Global - don't working, there is no step 4
Click to expand...
Click to collapse
It's only for Chinese firmware, as stated in OP.
This adb command will do the trick too:
Code:
adb shell am start com.huami.mobile.watchsettings/com.huami.moblie.watchsettings.actions.lab.labUI.LongSittingTimeActivity

Saratoga79 said:
It's only for Chinese firmware, as stated in OP.
This adb command will do the trick too:
Code:
adb shell am start com.huami.mobile.watchsettings/com.huami.moblie.watchsettings.actions.lab.labUI.LongSittingTimeActivity
Click to expand...
Click to collapse
Great, thanks mate! It seems that both the Lab visibility and the setting are reset after the watch restarts. Oh, well...

Saratoga79 said:
It's only for Chinese firmware, as stated in OP.
This adb command will do the trick too:
Code:
adb shell am start com.huami.mobile.watchsettings/com.huami.moblie.watchsettings.actions.lab.labUI.LongSittingTimeActivity
Click to expand...
Click to collapse
Thank you

Related

[TUTORIAL][LG G Watch][Android Wear] How to capture OTA URL logcat

Since the Marshmallow announcement for Android Wear everyone is waiting for the update to hit their watches. If any of you got a notification saying an update is available/other text implying a software update do the following to get a OTA URL:
If you have access to charging cradle and PC:
1. Install ADB tool (windows users need ADB driver too). Plenty of tutorials out there. Mac/Linux users can use this: https://github.com/simmac/minimal_adb_fastboot
2. Enable USB Debugging on the wear watch: Go to Settings App > About and Tap 7 times the build number until you are a developer. Then proceed to go to settings again and go to Developer Tools. Scroll down to USB debugging and turn it on. Then place it on the charger.
3. In Terminal, type "adb devices", see if your watch is listed there. Then type "adb logcat" and update your watch. DO NOT CLOSE THE TERMINAL!
4. Once your watch has booted to recovery/whatever to install the update, do Control + C to end the log.
5. Copy the log to a text editor and find google.com, try the URLs until one downloads a ZIP file, the URL ends with something like: fromXXXXtoXXX signed .zip
6. Share that URL here!
If you dont have a charging cradle and a PC
You can still grab the OTA link.
1. Get the ADB tool (explained in first step above)
2. Enable developer options in both phone and watch
3. In the watch, enable Bluetooth debugging
4. Connect the phone to the PC using a USB cable
5. type
"adb forward tcp:4444 localabstract:/adb-hub"
"adb connect localhost:4444"
You should see connected to localhost:4444
6. Type "adb -e logcat" and update your watch
7. When your watch boots to recovery/whatever do Control + C.
8. Search for google.com and check that the URL downloads a .ZIP file.
NEW METHOD: USING ONLY THE WATCH AND PHONE
This is by far the best method of getting a logcat with OTA URL since it only requires the watch and the phone, no computer or ADB software.
By @DA6030
Is ADB really necessarily? You can do it without a computer at all, using the on-device "bug report" function to generate the log, and then send that to yourself as a .txt file. I think a lot of people would find that much easier.
1. Enable developer options.
2. Enable ADB debugging. (maybe this is optional?)
3. Enable "Bug report in menu". (maybe this is optional?)
4. Wait patiently for OTA notification. When you get the OTA notification, do NOT accept the OTA. Instead, generate a bug report. Easiest way is probably from the Android Wear app on your phone (3-dot overflow menu --> "Report wearable bug").
5. Wait patiently (can be 5-10 mins) for the watch to build a bug report. It will keep a persistent notification on the watch while it's generating the report, and a notification on the phone when it's done.
6. From the Android Wear app on your phone, send to yourself (e.g., email or Google Drive).
7. Search for the aforementioned .zip file URL
8. Share the URL here!
Good luck!
Is ADB really necessarily? You can do it without a computer at all, using the on-device "bug report" function to generate the log, and then send that to yourself as a .txt file. I think a lot of people would find that much easier.
1. Enable developer options.
2. Enable ADB debugging. (maybe this is optional?)
3. Enable "Bug report in menu". (maybe this is optional?)
4. Wait patiently for OTA notification. When you get the OTA notification, do NOT accept the OTA. Instead, generate a bug report. Easiest way is probably from the Android Wear app on your phone (3-dot overflow menu --> "Report wearable bug").
5. Wait patiently (can be 5-10 mins) for the watch to build a bug report. It will keep a persistent notification on the watch while it's generating the report, and a notification on the phone when it's done.
6. From the Android Wear app on your phone, send to yourself (e.g., email or Google Drive).
7. Search for the aforementioned .zip file URL
8. Share the URL here!
Has anyone studied how the update check mechanism works on this watch? I've started checking daily via About->Check for update, and realize it always comes back green, immediately, even if it's disconnected. Which tells me it's not really checking.
A realistic response would be a fraction of a second latency if connected, and an error if disconnected. Is it possible there's a TTL provided with every response? Or is it a placebo button, that shows if an update is queued/downloaded, but was never meant to actually check for an update?
DA6030 said:
Has anyone studied how the update check mechanism works on this watch? I've started checking daily via About->Check for update, and realize it always comes back green, immediately, even if it's disconnected. Which tells me it's not really checking.
A realistic response would be a fraction of a second latency if connected, and an error if disconnected. Is it possible there's a TTL provided with every response? Or is it a placebo button, that shows if an update is queued/downloaded, but was never meant to actually check for an update?
Click to expand...
Click to collapse
From Tonoxis on reddit:
The OS's OTA system does actually directly contact and download OTAs from Google's servers. This is done through the ClockworkProxy binary and provides internet access to the core system and to applications installed in /system/priv-app (possibly /system/app too) but the watch does actually make a real connection to check for updates.
It then caches the response from the server for 24 hours, similar to the normal Android OTA process. But yes, pressing the screen does nothing except tell the watch to check the server again, but most of the time, the watch will used the cached answer.
sirrelevant said:
From Tonoxis on reddit:
The OS's OTA system does actually directly contact and download OTAs from Google's servers. This is done through the ClockworkProxy binary and provides internet access to the core system and to applications installed in /system/priv-app (possibly /system/app too) but the watch does actually make a real connection to check for updates.
It then caches the response from the server for 24 hours, similar to the normal Android OTA process. But yes, pressing the screen does nothing except tell the watch to check the server again, but most of the time, the watch will used the cached answer.
Click to expand...
Click to collapse
Wow, a hard-coded 24 hour TTL. Sounds like bad form, if they discover a nasty bug mid-rollout and want to quickly deploy a catchup build. :-/ Thanks for the info!
But I'm using M1D65S now, so I can't grab any update unless it releases any updates.
YandexStudio said:
But I'm using M1D65S now, so I can't grab any update unless it releases any updates.
Click to expand...
Click to collapse
Yeah, but the thread was open in early 2016 - it's certainly no longer a thing in early 2018, 2 years are complete android life cycle...
Sent from my OnePlus 3T using XDA Labs

[query] amazfit Stratos Apk installation?

Hi i have stratos with English firmware.
Is there a way to install APK directly from watch? Without usb connected to PC.
I transferred apk but i am unable to install, the installer crashes everytime.
Is there an easier way to install apk from Android mobile?
Or is there an android adb?
Thanks in advance.
Also my battery is 1 day with GPS always OFF and heartrate always ON. Is this normal?
I have the Pace not the Stratos but I don't think that you can install apps from the watch. It is possible on the Pace to use ADB to enable "unknown sources" and then attempt to install apks from the internal memory, but due to the screen size the installer does not show correctly and it is impossible to finish installing the app.
I would think that results on the Stratos would be very similar even if you found an apk that is compatible it.
I dont have screen size issues, it says installation protected and asks to press ok to install and continue (something similar) then intaller crashes.
Sounds like you got a permission issue.
Have you tried one of these?
adb shell settings put global install_non_market_apps 1
or
adb shell settings put secure install_non_market_apps 1
If you still get a similar error, then you may need root.
anox said:
Sounds like you got a permission issue.
Have you tried one of these?
adb shell settings put global install_non_market_apps 1
or
adb shell settings put secure install_non_market_apps 1
If you still get a similar error, then you may need root.
Click to expand...
Click to collapse
Ok, so after setting both settings menrioned by you i can see the install screen. And unfortunately as you mentioned i cannot see the install button
My watch has 3 buttons and none of them do the CLICK action.
Thank you for the adb commands
Is ther a shell command see all the supported settings?
firoz3321 said:
Ok, so after setting both settings menrioned by you i can see the install screen. And unfortunately as you mentioned i cannot see the install button
My watch has 3 buttons and none of them do the CLICK action.
Thank you for the adb commands
Click to expand...
Click to collapse
I know this is so late but I came across this in my journey to update watch droid assistant.
type the commands they gave you to enable unknown sources, then type adb shell wm density 150, this makes the screen show enough to hit install.
then type adb shell wm density 238 to return to the normal resolution. I know this still requires a computer to keep normal density but there is technically a way.
sonicscrewup said:
I know this is so late but I came across this in my journey to update watch droid assistant.
type the commands they gave you to enable unknown sources, then type adb shell wm density 150, this makes the screen show enough to hit install.
then type adb shell wm density 238 to return to the normal resolution. I know this still requires a computer to keep normal density but there is technically a way.
Click to expand...
Click to collapse
If we have access to PC then there are easier methods to install apk isn't it?
firoz3321 said:
If we have access to PC then there are easier methods to install apk isn't it?
Click to expand...
Click to collapse
In most cases yes, in my case no. I had updated the companion app on my phone, so my watch version was incompatible, instead of revert the phone app, I decided to force the watch to allow me to install. Changing the resolution worked like a charm.
APK installer is easier if you can get the latest apk to your computer, but i could only get it via the app pushing it to the watch.
sonicscrewup said:
In most cases yes, in my case no. I had updated the companion app on my phone, so my watch version was incompatible, instead of revert the phone app, I decided to force the watch to allow me to install. Changing the resolution worked like a charm.
APK installer is easier if you can get the latest apk to your computer, but i could only get it via the app pushing it to the watch.
Click to expand...
Click to collapse
Here is an easy way to install an app on the watch without any screen size issue:
- install the wear part of this-> https://play.google.com/store/apps/details?id=com.sssemil.advancedsettings&hl=en
When installing an apk on the watch using any file manager, just select Advanced Settings instead of the default Package Installer.
anox said:
Here is an easy way to install an app on the watch without any screen size issue:
- install the wear part of this-> https://play.google.com/store/apps/details?id=com.sssemil.advancedsettings&hl=en
When installing an apk on the watch using any file manager, just select Advanced Settings instead of the default Package Installer.
Click to expand...
Click to collapse
Works, but root on watch is required. So it's clear that people with stock firmware (or even common custom ROM with just adb root) cannot use this.
By the way, it seems that if you get adb root and add the permission to install 3rd party apps on watch then it works... I haven't tested this yet tho.
lfom said:
Works, but root on watch is required. So it's clear that people with stock firmware (or even common custom ROM with just adb root) cannot use this.
By the way, it seems that if you get adb root and add the permission to install 3rd party apps on watch then it works... I haven't tested this yet tho.
Click to expand...
Click to collapse
Apparently, sonicscrewup already has all what is required
hi,
anox suggested to install the wear part of this https://play.google.com/store/apps/d...settings&hl=en (
Advanced Settings for Watch) in order to install apk in the watch without pc
but where to find the apk intended to install on the watch (because the
"Advanced Settings for Watch" usually installs on the phone, and then transfers the wear part to the watch)?
I figured it out, probably is not the easier way to do it.
you decompile the phone apk (using apk easy tool), then you will find the wear apk inside the res/raw folder.
you can install it on the watch directly, or probably better, convert it first using this tutorial (https://forum.xda-developers.com/smartwatch/amazfit/android-wear-apps-to-android-read-apk-t3726835)
the "Advanced Settings for Watch" works well in the amazfit to install apks, and to do other things, but of course, there are many features making the app to crash.
cheers
carloscolhao said:
hi,
anox suggested to install the wear part of this https://play.google.com/store/apps/d...settings&hl=en (
Advanced Settings for Watch) in order to install apk in the watch without pc
but where to find the apk intended to install on the watch (because the
"Advanced Settings for Watch" usually installs on the phone, and then transfers the wear part to the watch)?
I figured it out, probably is not the easier way to do it.
you decompile the phone apk (using apk easy tool), then you will find the wear apk inside the res/raw folder.
you can install it on the watch directly, or probably better, convert it first using this tutorial (https://forum.xda-developers.com/smartwatch/amazfit/android-wear-apps-to-android-read-apk-t3726835)
the "Advanced Settings for Watch" works well in the amazfit to install apks, and to do other things, but of course, there are many features making the app to crash.
cheers
Click to expand...
Click to collapse
Yah, I sometimes leave something out. There are already several threads talking about how to install Android Wear app on this watch.
Anyway, an APK file is just a normal compressed ZIP file. So, the quick & easy way to install the wear part of Android Wear app is to:
- Change the file extension from "apk" to "zip"
- Extract the zip file and get the wear APK file inside the res/raw folder to install on the watch
Personally, I don't use any tool or recompile any Android Wear app in order to just install on the watch. I don't see any real world result difference.
Thanks.
I did not realise an apk could be decompressed as a simple zip. Good to know
anox said:
Sounds like you got a permission issue.
Have you tried one of these?
adb shell settings put global install_non_market_apps 1
or
adb shell settings put secure install_non_market_apps 1
If you still get a similar error, then you may need root.
Click to expand...
Click to collapse
Wanted to understand if this setting is maintained across firmware updates. I have a very poor data connection with my charger and this setting is a savior, along with File Manager+. So was wondering if I'm going to lose this at every update.
adityavaidya said:
Wanted to understand if this setting is maintained across firmware updates. I have a very poor data connection with my charger and this setting is a savior, along with File Manager+. So was wondering if I'm going to lose this at every update.
Click to expand...
Click to collapse
Just found this thread tucked away and it works perfectly. No fiddling with any poor USB connections anymore. It's by XDA user zmad2000
https://forum.xda-developers.com/smartwatch/amazfit/amazfit-pace-enable-app-list-install-t3639617
Here's the solution just to ensure that it's archived.
Background
I was have trouble getting my Amazfit Pace to be recognized by the adb program or the ADK installer. When it was in the dock it i could look at the files but not have it recognized by the other apps. I have the Amazfit Pace US version with ROM 1.3.3a
Here are the steps i took.
Enable the "developers mode" by tapping on the legal notice.
Plug in the Amazfit to the computer and put a blank file called "launcher_config.ini" in the main directory
Restart the watch. Once it has booted up connect it via the wifi to the same network your computer is on.
Open and cmd prompt and got to "C:\Users\Rich\AppData\Local\Android\sdk\platf orm-tools" directory (this will differ based on you user name)
Type adb connect (ip address of watch)
Then type adb install (whatever app you want)
Not sure if this is the 100% but it worked for me and my watch was right out of the box. Hope this helps some people.
Click to expand...
Click to collapse
Edit: What I've found is that once you enable developer mode, adb over WiFi is automatically enabled. You don't seem to need that file to be present. Only problem is that adb is now enabled over WiFi at all times when the watch is connected. So there is a security risk, albeit a small one because I'd only connect my watch to my home WiFi.
So all that's required is:
Go to Settings->About
Tap on the Serial number 7 times
Ensure the watch is connected to the same WiFi as your computer
Type adb connect (ip address of watch)
but are you able to install applications directly from the watch?
I did everything but when I try to install using "advanced settings" I always see the word "working" but the installation process never ends
apgeo said:
but are you able to install applications directly from the watch?
I did everything but when I try to install using "advanced settings" I always see the word "working" but the installation process never ends
Click to expand...
Click to collapse
It only works with root, or if you use a modded PackageManager, used in some custom ROMs, after allowing 3rd party APKs installations (non-Market security check).
sonicscrewup said:
I know this is so late but I came across this in my journey to update watch droid assistant.
type the commands they gave you to enable unknown sources, then type adb shell wm density 150, this makes the screen show enough to hit install.
then type adb shell wm density 238 to return to the normal resolution. I know this still requires a computer to keep normal density but there is technically a way.
Click to expand...
Click to collapse
Thanks a lot! That actually worked for me! :highfive:

Fluid Navigation Gestures

Fluid Navigation Gesture​
Installation ​
The app has a built-in option to hide the software navigation keys (if necessary) but it requires either root or a pc is required to grant a system permission.
Instructions:
1-Enable Developer Mode in the Android settings.
2- Enable USB Debugging
3- Install Adb (links bellow)
4- Run the following adb command to grant the
Permission:
Windows: adb shell pm grant com.fb.fluid android.permission.WRITE_SECURE SETTINGS
macOS: Jadb shell pm grant com.fb.fluid android.permission.WRITE_SECURE_SETTINGS
You can restore the navigation keys using the app or by run this
adb command:
Windows: adb shell wm overscan O,0,0,0
macOS: /adb shell wm overscan 0,0,0,0
Actions:
Back
Home
Recent apps
Toggle split screen
Open notifications
Open power dialog
Open quick settings
Launch Google search overlay
Open keyboard selector
Voice Search
Launch assistant
Launch app
Launch shortcut
Download:
https://play.google.com/store/apps/details?id=com.fb.fluid
Hey guys
So I am a beta tester and I made a review of the app with detailed instructions in my channel so for anyone interested to see and understand it
youtu.be/y1X3wQnEMBc
I get an error when running the command: Bad argument: java.lang.IllegalArgumentException: Unknown permission: android.permission.WRITE_SECURE
stevenlientje said:
I get an error when running the command: Bad argument: java.lang.IllegalArgumentException: Unknown permission: android.permission.WRITE_SECURE
Click to expand...
Click to collapse
The correct one is android.permission.WRITE_SECURE_SETTINGS
Regurding the fluid app
Hi its perfectly working on my note 9 as i want to remove the app please help me to remove the app the installation was done with the pc guide lines so any one who has the idea of how to remove the app from a note 9 as i did rwmove but the side still is thier
wasp45 said:
Hi its perfectly working on my note 9 as i want to remove the app please help me to remove the app the installation was done with the pc guide lines so any one who has the idea of how to remove the app from a note 9 as i did rwmove but the side still is thier
Click to expand...
Click to collapse
Read the guide. It tell how you can do it.
Have you tried to reboot device after removing it?
Force kill app not work! Pro version
What happens? @@Deadpool96
Sent from my [device_name] using XDA-Developers Legacy app
Unable to restore navigation keys on Yureka Black
I am using Yureka Black device and tried enabling fluid navigation. That worked well. But now i just want to restore my navigation keys but unable to do so. I tried from the app and from the ADB as well (adb shell wm overscan 0,0,0,0) but nothing works. Please help. I have tried rebooting and all
Twrp
Any devs can make a flashble zip for granting cammand through twrp? I iz noob.
does not work on Android 10, quits immediately (Google Pixel 3)
Recent apps
Hi, a little help here.
i have a oneplus 7 (not pro), and i installed FNG in august, and i absolutely loved it
but, since this week's update (i think on sep 21), the gesture for "previous app" changed its behavior. instead of showing the 3 previous app (one swipe changed to the latest, a second one to the one before, a third the one before, and then returning to show the previous app). it was super useful because i drive a cab and could change between 4 apps with ease while driving without little distraction, and also because recent apps has to rotate because it does not support landscape mode anymore (DON'T GET ME STARTED ON THAT, but any help on that would be also very useful).
now, it only shows the last app, and when on android auto it's common that it shows that, which only block the screen and is completely useless.
so, i'm willing to send a lot of good vibrations to whoever can help me with that (that's a once in a lifetime offer, guys). thanks for any help you can offer with this
I have an error running this command : error: device '(null)' not found
Hi, I had an error message whilst trying to hide naviagion bar using computer (win10). Error -> device unauthorized (I have screenshot of it, but I can't send link here. - (I have USB debbuging on)
MikePlays_ said:
Hi, I had an error message whilst trying to hide naviagion bar using computer (win10). Error -> device unauthorized (I have screenshot of it, but I can't send link here. - (I have USB debbuging on)
Click to expand...
Click to collapse
Mmm, sounds more like an ADB problem, rather than an FNG one.
Hi, MikePlays_
I've had this problem myself occasionally when running ADB, not specifically with FNG, but with other apps requiring an ADB command line to be run.
Usually, when you run ADB for the first time, both your PC and your Android device displays a dialog box to confirm USB debugging authorisation. I'm a little hazy on the precise details of this dialog box, because it's been quite a while since I used ADB.
Anyhow, if this doesn't happen or you get an error message, then you can try to revoke USB debugging authorisations, and begin again, with the FNG ADB command line. Sometimes a reboot of both your PC and your Android device may be required after revocation.
You should find the revoke authorisation option in your Android devices Developer Options settings. See my screenshot below, taken from my Android 9 Moto G6.
I can't say for certain if this will work for you, but when I've had weird ADB authorisation problems in the past, this has usually fixed the problem.
Good luck & I hope this helps
Rgrds,
Ged.
Sent from my moto g(6) using XDA Labs
GedBlake said:
Mmm, sounds more like an ADB problem, rather than an FNG one.
Hi, MikePlays_
I've had this problem myself occasionally when running ADB, not specifically with FNG, but with other apps requiring an ADB command line to be run.
Usually, when you run ADB for the first time, both your PC and your Android device displays a dialog box to confirm USB debugging authorisation. I'm a little hazy on the precise details of this dialog box, because it's been quite a while since I used ADB.
Anyhow, if this doesn't happen or you get an error message, then you can try to revoke USB debugging authorisations, and begin again, with the FNG ADB command line. Sometimes a reboot of both your PC and your Android device may be required after revocation.
You should find the revoke authorisation option in your Android devices Developer Options settings. See my screenshot below, taken from my Android 9 Moto G6.
I can't say for certain if this will work for you, but when I've had weird ADB authorisation problems in the past, this has usually fixed the problem.
Good luck & I hope this helps
Rgrds,
Ged.
Sent from my moto g(6) using XDA Labs
Click to expand...
Click to collapse
Well, thanks for fast reply, I don't know how to properly use ADB, is there any tuturial for that? I can't see any dialog box on computer, so something is wrong.
MikePlays_ said:
Well, thanks for fast reply, I don't know how to properly use ADB, is there any tuturial for that? I can't see any dialog box on computer, so something is wrong.
Click to expand...
Click to collapse
As per my previous post, try revoking your USB debugging authorisations, and then reboot both your PC and your Android device. If all goes well, the dialog box should then appear when you run the ADB command. If I remember correctly, it's similar in function to pairing two Bluetooth devices together, with a unique code, and which you then have to confirm.
As for tutorials, try this to begin with...
https://www.xda-developers.com/quickly-install-adb
In the meantime, I'll get my laptop out, and see if I can grab a screenshot of the dialog box you should expect to see. Give me an hour or so
Rgrds,
Ged.
Sent from my moto g(6) using XDA Labs
GedBlake said:
As per my previous post, try revoking your USB debugging authorisations, and then reboot both your PC and your Android device. If all goes well, the dialog box should then appear when you run the ADB command. If I remember correctly, it's similar in function to pairing two Bluetooth devices together, with a unique code, and which you then have to confirm.
As for tutorials, try this to begin with...
https://www.xda-developers.com/quickly-install-adb
In the meantime, I'll get my laptop out, and see if I can grab a screenshot of the dialog box you should expect to see. Give me an hour or so
Rgrds,
Ged.
Sent from my moto g(6) using XDA Labs
Click to expand...
Click to collapse
well, now I tried it again, when I was trying to allow USB debbuging, it gave me error -> screenshot at the bottom. But thank you very much for that quick response, I did not expect that
OK, I was mistaken. No dialog box appears on the PC, but one does appear on your Android device, and it looks like the screenshot below...
Rgrds,
Ged.
MikePlays_ said:
well, now I tried it again, when I was trying to allow USB debbuging, it gave me error -> screenshot at the bottom. But thank you very much for that quick response, I did not expect that
Click to expand...
Click to collapse
That's great news. Hope you get FNG working, with a disabled stock Nav Bar.
It's a terrific app, and one I couldn't imagine without, on my phone and tablet.
Rgrds,
Ged.
Sent from my moto g(6) using XDA Labs
GedBlake said:
OK, I was mistaken. No dialog box appears on the PC, but one does appear on your Android device, and it looks like the screenshot below...
Rgrds,
Ged.
Click to expand...
Click to collapse
Problem I have with it is even smaller pop up over that, it writes when I want to press "ok", it writes "an app is obscuring a permission request. Settings can't verify your response." It is visible on screenshot too, but it has low quality.

[Fixed]Step to Downgrade JOYUI11 to ANDORID PIE - Require Factory Reset

1.
Black shark2(only)
H0 : Download this firmware mp3
H0_EEA : Download this firmware mp3
rename "update.zip" then put it "ota" Directory in your phone(if you don't have this directory, make it)
if you find step bs2 pro downgrade, see this link
2. Then dial this from your phone
Code: *#*#1027#*#*
3. push "local update"
4. If it done, reboot your phone
5. Your phone enter recovery that requires factory reset. therefore, proceed factory reset your phone
6. wait for reboot
Won't this break the sensors?
batuken said:
Won't this break the sensors?
Click to expand...
Click to collapse
which sensor?
ripiad said:
which sensor?
Click to expand...
Click to collapse
Proximity and accelorometer sensors. I've just tried it and it didn't break them. Thanks for this.
ripiad said:
Black shark2 pro
Download this firmware mp2 and rename update zip. - thank you for KM7
I'm not sure if this is going to flash probably this way on BS 2 Pro, as this contain extracted partitions and there is a flash script 'flash_all.bat' which I made to flash those partitions.
So 'flash_all.bat' should be executed to flash this.
Click to expand...
Click to collapse
Thanks for this thread this will make it easier for people to understand.
ripiad said:
1.
Black shark2
H0 : Download this firmware mp3
H0_EEA : Download this firmware mp6
then up it "ota" Directory in your phone(if you don't have this directory, make it)
Black shark2 pro
Download this firmware mp2 and rename update zip. - thank you for KM7
then up it "ota" Directory in your phone(if you don't have this directory, make it)
2. Then dial this from your phone
Code: *#*#1027#*#*
3. push "local update"
4. If it done, reboot your phone
5. Your phone enter recovery that requires factory reset. therefore, proceed factory reset your phone
6. wait for reboot
Click to expand...
Click to collapse
Is there by any way I can get the navigation buttons at the bottom as like Android 10 or earlier than 9? the gesture based Android 9 is annoying and not able to lock the background app as we do on other android systems.
spikywits said:
Is there by any way I can get the navigation buttons at the bottom as like Android 10 or earlier than 9? the gesture based Android 9 is annoying and not able to lock the background app as we do on other android systems.
Click to expand...
Click to collapse
There are may bugs in joyui11.
Navigation buttom array can reverse in fullscreen display which located settings. (select mirror button)
Lock the background app is possible. view recent app(press home button or slide bottom up) and long press app what you want to lock.
Then, you can see lock icon
ripiad said:
There are may bugs in joyui11.
Navigation buttom array can reverse in fullscreen display which located settings. (select mirror button)
Lock the background app is possible. view recent app(press home button or slide bottom up) and long press app what you want to lock.
Then, you can see lock icon
Click to expand...
Click to collapse
Sorry. I forgot to mention - I need to do this for stock android 9 on BS2. Once I downgrade from 10 to 9.
The older joy ui navigation menu sucks. It offers only gesture navigation and no option to lock apps. There is no 3 button navigation like other android platforms.
spikywits said:
Sorry. I forgot to mention - I need to do this for stock android 9 on BS2. Once I downgrade from 10 to 9.
The older joy ui navigation menu sucks. It offers only gesture navigation and no option to lock apps. There is no 3 button navigation like other android platforms.
Click to expand...
Click to collapse
how about using this? using adb.
adb shell settings put secure sysui_nav_bar "space,recent;home;back,space"
" "<- you can change this order
caution : when you reboot your phone, it go back previous
ripiad said:
how about using this? using adb.
adb shell settings put secure sysui_nav_bar "space,recent;home;back,space"
" "<- you can change this order
caution : when you reboot your phone, it go back previous
Click to expand...
Click to collapse
Thanks for the trick. I think there must be a way to persist this setting.
If I remember correctly, there are apps on store to change dpi on non rooted phone, which runs some adb commands to change the dpi value and make it to persist across reboot.
or using fluid navigation gestures app
https://play.google.com/store/apps/details?id=com.fb.fluid&hl=en
2. Then dial this from your phone
Code: *#*#1027#*#*
Click to expand...
Click to collapse
This code is not working on my device skw-h0. Any help would be appreciated.
spikywits said:
This code is not working on my device skw-h0. Any help would be appreciated.
Click to expand...
Click to collapse
Did you use 3rd party dialer?
this method based on google dialer(require default dialer)
ripiad said:
Did you use 3rd party dialer?
this method based on google dialer(require basic dialer)
Click to expand...
Click to collapse
I use the stock dialer and it the default one, although I have truecaller installed along with.
Regardless, I managed to fix the issue.
I did the following:
Code:
adb reboot recovery
wipe/factory reset
with nothing installed, dialed *#*#1027#*#* and got the ota update app to popup.( I had the dpi set to lower than stock before reset, not sure that could be a reason for incompatibilities. )
Thanks, I will come back if I get into issues again with the downgrade.
spikywits said:
I use the stock dialer and it the default one, although I have truecaller installed along with.
Regardless, I managed to fix the issue.
I did the following:
Code:
adb reboot recovery
wipe/factory reset
with nothing installed, dialed *#*#1027#*#* and got the ota update app to popup.( I had the dpi set to lower than stock before reset, not sure that could be a reason for incompatibilities. )
Thanks, I will come back if I get into issues again with the downgrade.
Click to expand...
Click to collapse
I think truecaller make this issue.
additional dialer caused this situation
ripiad said:
I think truecaller make this issue.
additional dialer caused this situation
Click to expand...
Click to collapse
I don't think truecaller cause this.
I successfully downgraded from android 10 to 9. Installed truecaller and tested the dial code, it instantly popsup the update software.
Thanks for documenting the steps. Infact, I used the updated ota image from KM7 thread - SKYW2003090OS00MP6.
I will work on to root this device now and keep it on 9 forever. No more miui based Android 10
Update:
warning: flashing SKYW2003090OS00MP6 directly broke my sensors.
Had to flash the MP3 update.zip in the opening post to keep the sensors working. Thanks for the zip.
spikywits said:
Is there by any way I can get the navigation buttons at the bottom as like Android 10 or earlier than 9? the gesture based Android 9 is annoying and not able to lock the background app as we do on other android systems.
Click to expand...
Click to collapse
This can be done by turning off 'Swipe up on Home button' gesture, in Settings > System > Gestures.
spikywits said:
I don't think truecaller cause this.
I successfully downgraded from android 10 to 9. Installed truecaller and tested the dial code, it instantly popsup the update software.
Thanks for documenting the steps. Infact, I used the updated ota image from KM7 thread - SKYW2003090OS00MP6.
I will work on to root this device now and keep it on 9 forever. No more miui based Android 10
Update:
warning: flashing SKYW2003090OS00MP6 directly broke my sensors.
Had to flash the MP3 update.zip in the opening post to keep the sensors working. Thanks for the zip.
Click to expand...
Click to collapse
KM7 thread - SKYW2003090OS00MP6. is not OS00 firmware. that's OS01 firmware. Because I'm sharing this files first.
Today. I could get SKYW2003090OS00MP6 factory firmware(Korea ver.) so I'll modify it.
ripiad said:
1.
Black shark2
H0 : Download this firmware mp6
H0_EEA : Download this firmware mp6
then up it "ota" Directory in your phone(if you don't have this directory, make it)
Black shark2 pro
Download this firmware mp2 and rename update zip. - thank you for KM7
then up it "ota" Directory in your phone(if you don't have this directory, make it)
2. Then dial this from your phone
Code: *#*#1027#*#*
3. push "local update"
4. If it done, reboot your phone
5. Your phone enter recovery that requires factory reset. therefore, proceed factory reset your phone
6. wait for reboot
Click to expand...
Click to collapse
normal work on the black shark 2 pro DLT-H0?
my version is DLTR2004231OS00MQ0
I click on local update and nothing happens and non-local update when I click appears on the following message.
the list of update packages update / package_list does not exist

How To Guide Call recording working in GT 2 pro ( no root )

Finally i found a method to record call on realme gt 2 pro global gdpr version, who is persistent at boot. No root, no bootloader unlock.
Step one : install setedit from play store and add op_voice_recording_supported_by_mcc with 1 value to global settings. You have to give Setedit write secure rights with adb
Step two : install phone apk below.
That's it. Start Google dialer and make a call. Still works after reboot.
Not working : automatic call recorder, you have to press record button when you're in call.
Notice: if you don't see record button in Google dialer , is normal, just press back button to see realme dialer.
This should work on all color os 3 device.
Recorded call are in internal memory / music/ recordings/ call recordings folder.
ENJOY !!
No working... No see
Which apk needs to be installed for step two?
NVM I figured it out
Not working, it has changed the dialer but instead of recording button I have a "contacts" button and when I press it nothing happens.
Please uninstall phone from installed apps and install again.
criszz said:
Please uninstall phone from installed apps and install again.
Click to expand...
Click to collapse
Same, tried also to reboot but nothing
No permission to add a new line in Global Table
RazvanelTM said:
No permission to add a new line in Global Table
Click to expand...
Click to collapse
Same here, I've added the option in the system table maybe that's why it is not working
Yes, you must provide write secure rights for setedit with adb to edit in global.
Updated first post with that.
criszz said:
Yes, you must provide write secure rights for setedit with adb to edit in global.
Updated first post with that.
Click to expand...
Click to collapse
How can do? Have any tutorials?
manu81cba said:
How can do? Have any tutorials?
Click to expand...
Click to collapse
By default, for your protection, Android prevents you from modifying the SECURE and GLOBAL tables. If you have Android Jellybean or later, you can remove this protection from an ADB shell using the command "pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS". On earlier versions, you can only remove this protection on a rooted device by installing SetEdit to the system partition.
All working flawless now I can confirm that
Not working when giving the permission in adb
RazvanelTM said:
Not working when giving the permission in adb
Click to expand...
Click to collapse
Try to activate first in the developers options this one: "Disable permission monitoring"
shootemdown371 said:
Try to activate first in the developers options this one: "Disable permission monitoring"
Click to expand...
Click to collapse
It worked, thanks!
Now it's confirmed to work and we must think how to enable automatically record for all calls. People who said not working without knowing, please edit your post.
In setedit ...you know what need change for active the volte ?
Thank you very much it's working for me!
PS for those unfamiliar with SetEdit can also use this in adb after disabling permission monitoring:
adb shell settings put global op_voice_recording_supported_by_mcc 1
Just must be applied after every restart ( that is what i read )
Nice post, thanks for sharing. Any solution for Xiaomi Redmi Note 10S, Global ROM MI?
Also working on the regular gt2

Categories

Resources