Hi guys,
I wanted to share my experience, how to disable vibrations on the Amazift. Sorry if some already posted it, but I couldnt find it.
First connect the device and open an console with adb.
Then open the shell on the watch:
Code:
adb shell
After that verify the name of the launcher package
Code:
pm list packages
There you should find a package called com.huami.launcher - this is the package we want to disable vibrations:
Code:
cmd appops set com.huami.launcher VIBRATE ignore
If you want to enable the vibrations again use:
Code:
cmd appops set com.huami.launcher VIBRATE allow
Since I want to have vibrations if I get a phone call, I installed the watch droid app on the watch, wich doesn't get changed at all.
Feel free to post questons, and I hope that I could give something back to this awesome community!
Thanks for this tutorial @Bainhorious !
That's exactly what I was looking for. Super simple but seems like none of the apps can offer the option to get notifications without vibration (I've tried the Mi app, Tools & Amazfit and also the Notify & Fitness).
Before I try your solution, I need, in addition to the vibration for incoming calls, I also need vibration for the Hangouts app. Do you think the "watch droid app" or even the Mi app would provide vibration for these 2 apps only? Thanks once again.
PS: my watch is the Amazfit Bip
Yes, as I have described above, you separately disable for every app the vibrations. So then just leave hangouts and watch droid out.
Thanks for replying.
Are you talking about the Bip? Because I don't think it is possible to install watch droid app on the Amazfit Bip.
Newbie question: do I need to unlock the bootloader or something like that? Or I can just connect the watch to my computer via USB and write the codes via ADB?
Man, this process work on Amazfit Bip? My Bip stop to Vibrate without, and I don't make it back =/
Unfortunately I don't think it works for the Bip, at least no one has tried
Bainhorious said:
Hi guys,
I wanted to share my experience, how to disable vibrations on the Amazift. Sorry if some already posted it, but I couldnt find it.
First connect the device and open an console with adb.
Then open the shell on the watch:
Code:
adb shell
After that verify the name of the launcher package
Code:
pm list packages
There you should find a package called com.huami.launcher - this is the package we want to disable vibrations:
Code:
cmd appops set com.huami.launcher VIBRATE ignore
If you want to enable the vibrations again use:
Code:
cmd appops set com.huami.launcher VIBRATE allow
Since I want to have vibrations if I get a phone call, I installed the watch droid app on the watch, wich doesn't get changed at all.
Feel free to post questons, and I hope that I could give something back to this awesome community!
Click to expand...
Click to collapse
Thanks for this! btw. "cmd" didn't work for me, but "command" worked
I think it should be
Code:
appops set com.huami.watch.launcher VIBRATE ignore
in the current version
Bainhorious said:
I think it should be
Code:
appops set com.huami.watch.launcher VIBRATE ignore
in the current version
Click to expand...
Click to collapse
Yep, this also :good:
I'm assuming ADB refers to Android Debug Bridge?
For someone who isn't that savvy with the above, would you recommend doing this? This is a feature that I miss coming from a pebble time and I want to do this but the instructions above will probably mean that I get lost in the process. Is the above process to be done with the amazfit app or while the watch is connected to a pc?
Sorry about the basic questions.
I suppose there is no app that can disable vibration, right? At least, not amazfit tools, which I tried...
Does this still work on Android Pie? Certain apps still vibrate annoyingly so despite the granular notification control that Pie has introduced.
Related
Hey everybody, I am posting this here cause I just built a new parental control, remote administration and practical joke app for Android called caesura. Caesura is a remote administration app that allows an Android phone to be controlled via SMS messages, in much the same was as one can post to Facebook via SMS.
By sending the !login command to the phone in question and then texting back the password, you can signal the phone to start listening for commands. These commands include panic (turn up the volume all the way and ring and flash lights to help find lost phone), status (find out how much battery life the phone has left and get other info), contacts (in case you forgot your phone at home, u can still access your address book), block (block all SMS messages from specified number, useful for parental control),.and many more.
Like I said, this is just a beta so I'm open to any suggestions
The app can be downloaded from this page on my website:
http://www.gundersoft.com/pages/downloads/caesura
As of yet this work is beta...it doesn't have decent instructions...these are forth coming. For now, the three commands you need to know are as follows: !login logs in to the remote phone. Help command (replace command with the name of a command you need help with) gives help related to command usage, and exit logs you out of the remote phone. Make sure you always use the exit command when finished! You cannot send any texts to the remote phone from the phone you used to control it while logged in.
for a list of the available commands, use the "login to another phone" button to control the phone instead of SMS. In this console there is a drop down menu containing all of the commands.
Finally, for the sake of research, every copy of this app "calls home" the first time it launches to register the version number so I can keep track of roughly how many of each version of caesura out in the wild lol.
Tell me what you think of all of this!
Sent from my MB860 using XDA App
Need to move this to the apps forum. This is the rom development forum. I will give this a try though, thanks for sharing.
Sent from my MB860 using xda premium
Oops, Sorry
Sent from my MB860 using XDA App
ur android market link is not working
https://market.android.com/developer?pub=Gundersoft+Studios
Those who have been lucky to upgrade to Wear 2.0 have probably noticed the removed Do Not Disturb toggle synchronization between wearable and phone. Some like it, some not. I didn't like it, so I made an app that does the sync. Currently it only works one way: wearable -> phone. With some hacking, sync is working both ways.
You can find the application in Play Store.
Source, builds and setup instructions are available in github and licensed under Apache 2.0.
Installation instructions for Watch -> Phone sync:
Install phone application and wearable application from on-watch Play Store
Launch application on Phone
Click "Grant Permission" button
Enable Do Not Disturb access permission for application
Make sure all 3 checks in the application pass
Installation instructions for Phone -> Watch sync:
Setup watch ADB
Execute:
Code:
adb shell settings put secure enabled_notification_listeners com.google.android.wearable.app/com.google.android.clockwork.stream.NotificationCollectorService:rkr.weardndsync/rkr.weardndsync.NotificationService
Enable state broadcast in Watch Setup wizard
Currently synchronization phone -> watch is only possible by assigning permissions in ADB. Wear OS doesn't provide management settings. As this is not officially supported - it may not work for everyone or the next Wear version.
I love that something like this is now made, but I have a question. What is the first screenshot in the Google Play Store link for? I thought this was only for DND?
I'd like to install it and find out myself, but my ZenWatch 2 still hasn't received the update.
If your watch isn't updated, then the sync should work out of the box. As for the screenshot, I tried to show that the toggle in the watch will sync to the toggle in the phone. I'm not a designer.
Wonderful little utility. Thank you very much.
Fingers crossed to get phone > watch allowed.
I have a few apps that toggle DND via Tasker on my phone, and having it trigger the watch too would be sweet.
Good news and bad news.
The bad: notification access and all the management is unavailable in Wear. So there will not be an official way to make this work (source).
The good: you can grant the permission in ADB. I tried it and the app can actually switch DND on and off (source).
Having to run a single ADB command will probably not stop the brave people of XDA! So synchronization should eventually come to the watch, just give me some time to fix the current bugs.
Bonus news: AudioManager can be used in android <6 for sound modes. Haven't looked into that yet.
Thanks for this app, I miss the functionality!
Sync from phone to watch is implemented and functional! v1.5 is being pushed to the Play Store. You just need to enable broadcast from phone in setup wizard and execute this command in the watch:
Code:
adb shell settings put secure enabled_notification_listeners com.google.android.wearable.app/com.google.android.clockwork.stream.NotificationCollectorService:rkr.weardndsync/rkr.weardndsync.HackService
raimondas.rimkus said:
You can find the application in Play Store
Click to expand...
Click to collapse
Hello!
Not work on Huawei Mediapad X2 (android 5.1.1).
I know: "only Android 6+ is supported"... But, maybe, android 5.1 can be added to?..
Thank you!
If it can help, I can access Do Not Disturb on android 5 through Tasker.
But it is called "Interrupt Mode". It can be found here: http://tasker.dinglisch.net/userguide_summary.html search for "Interrupt Mode".
raimondas.rimkus said:
Those who have been lucky to upgrade to Wear 2.0 have probably noticed the removed Do Not Disturb toggle synchronization between wearable and phone. Some like it, some not. I didn't like it, so I made an app that does the sync. Currently it only works one way: wearable -> phone. With some hacking, sync is working both ways.
You can find the application in Play Store.
Source is available in github and licensed under Apache 2.0.
Installation instructions for Watch -> Phone sync:
Install phone application and wearable application from on-watch Play Store
Launch application on Phone
Click "Grant Permission" button
Enable Do Not Disturb access permission for application
Make sure all 3 checks in the application pass
Installation instructions for Phone -> Watch sync:
Setup watch ADB
Execute:
Code:
adb shell settings put secure enabled_notification_listeners com.google.android.wearable.app/com.google.android.clockwork.stream.NotificationCollectorService:rkr.weardndsync/rkr.weardndsync.HackService
Enable state broadcast in Watch Setup wizard
Currently synchronization phone -> watch is only possible by assigning permissions in ADB. Wear OS doesn't provide management settings. As this is not officially supported - it may not work for everyone or the next Wear version.
Click to expand...
Click to collapse
Thank you so much.
Sent from my ONEPLUS A3003 using Tapatalk
Works perfect!! Thanks!
raimondas.rimkus said:
... As for the screenshot, I tried to show that the toggle in the watch will sync to the toggle in the phone. I'm not a designer.
Click to expand...
Click to collapse
me neither, but maybe this could help?
I'm just curious. What's the difference between this version available in the Play Store (source code available here) and your own? It looks to me as though that blunden may have forked your code.
That's how open source works, you are free to fork it or take it as an inspiration. His code isn't a plain copy paste, it looks like he even has sync to older android versions, which I didn't have time to do.
I can no longer sync both ways after the newest update, v1.6. I can only control DND from both devices from my watch. Anyone else having this problem with v1.6?
Sent from my SM-G955U using Tapatalk
thecarp1975 said:
I can no longer sync both ways after the newest update, v1.6. I can only control DND from both devices from my watch. Anyone else having this problem with v1.6?
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
The first idea is that app got suspended after the update. Make sure watch app is updated and start the app on phone. I've added a check that will tell you if watch DND permission is granted. If everything passes, then there is probably something weird with the AudioManager. Previous version used the new NotificationManager, but it requires a running service for broadcast events. I've switched to legacy AudioManager that can use a stateless broadcast receiver.
[Edit:] Android 4.3+ support is being pushed. This needed a code refactoring, so bugs are probable.
okk
raimondas.rimkus said:
The first idea is that app got suspended after the update. Make sure watch app is updated and start the app on phone. I've added a check that will tell you if watch DND permission is granted. If everything passes, then there is probably something weird with the AudioManager. Previous version used the new NotificationManager, but it requires a running service for broadcast events. I've switched to legacy AudioManager that can use a stateless broadcast receiver.
[Edit:] Android 4.3+ support is being pushed. This needed a code refactoring, so bugs are probable.
Click to expand...
Click to collapse
Yeah, all three permissions were granted. You wouldn't happen to have the APK for the previous version?
Sent from my SM-G955U using Tapatalk
V1.5 attached.
I would still prefer if you could make a logcat and I could fix the problem for the rest of the people. Just do these steps:
Connect phone to ADB
Enable DND, Disable DND on phone
Enable DND, Disable DND in watch
Run: adb logcat -d > bug_phone.txt
Repeat with watch connected to bug_watch.txt
PM the logs and I may try to fix it. It's not the first time android APIs don't work in specific phones.
Just a quick FYI. Version 1.6 works fine here. Nexus 6 / Pure Nexus 7.1.1 / Magisk root. Huawei watch AW 2.0 7.1.1 stock.
I can start DND from either watch or phone and the other device enables.
It works when I start Sleep as Android; SaS enables phone DND and that enables DND for AW 2.0, then Tasker via AutoWear triggers theater mode on my watch. One step goodness! :victory:
**Let me start off by saying that I have not had a chance to verify but I do not have the error that NFC is not enabled anymore.**
Requirements -
1. Android Pay (Google Pay will not work on my watch although I read a post by someone who says it works on theirs)
2. Tasker installed on phone
3. Autowear Plugin to Tasker installed on phone and watch
4. A PC with adb installed
Step 1: Enable Developer Options on Watch
Step 2: Turn on ADB Debugging and Debug over WiFi
Step 3: Open command prompt or powershell in the folder where you have adb (hold shift and right click)
Step 4: In powershell, type adb connect 198.162.X.X:5555 (use the actual IP of your watch). Press Enter. The watch will prompt you to accept the connection. Select Always Allow.
Step 5: Type adb shell pm grant com.joaomgcd.autowear android.permission.WRITE_SECURE_SETTINGS. Press Enter. It may take a minute or two but if you don't receive an error, it worked.
Step 6: Open Tasker on your phone. Select Tasks. Hit the + sign in the bottom right. Select Plugin -> Autowear -> Secure Settings. When the new window opens, click the pencil next to Configuration. Set Command to Execute to &CONNECTED&. Click Custom Setting. Setting Type is Global, Name is <NFC>, Input type is Toggle, and Value is 1. Once all those are set, click the back arrow to get back to the AutoWear Secure Settings page. Click the checkmark at the top to save the settings.
Step 7: In powershell on the pc, type adb install com.google.android_apkmirror.com.apk. Press Enter. It should say Success once it finishes.
Step 8: On your phone, under the Task Edit screen (where you should be if you did not exit out from step 6) click the "Play" button on the bottom left. You should get a green dot next to the word configuration at the top.
Step 9: Open Android Pay on the watch. It will take you through the setup and tell you to finish on your phone. Once you finish adding a card, it should show up on the watch. "To pay with your watch, you need to turn on NFC" will show up and blink a couple of times then go away. It should show your card with "Hold to terminal.." above it.
This is something I threw together real quick to get the word out. Like I said in the beginning, I have not tried it at a terminal yet. As soon as I do, I will repost with results. Also in the near future, I will streamline the process, add a command to Tasker to keep NFC on always, and hopefully pay without opening the Android Pay app on the watch (Simply have the watch unlocked). I have attached the Android Pay apk below. If anyone tries this and uses the watch at a terminal, please post results.
I had a feeling a developer would find a way. I wonder why google pay isn't working for you and why Android pay says it needs NFC when it is already enabled. Have you tested to see if it does indeed enable it?
developer209 said:
I had a feeling a developer would find a way. I wonder why google pay isn't working for you and why Android pay says it needs NFC when it is already enabled. Have you tested to see if it does indeed enable it?
Click to expand...
Click to collapse
I am in no way a developer. Just trying some stuff out. I tried to Pay with the watch and it did not work. Hopefully someone with some knowledge and experience will see something here and guide us in the right direction to get this working.
That could mean one of two things, either the watch's NFC is not actually on or Android pay is not transmitting the signal.
This does not actually enable NFC. I tried paying with Google Pay and it did not detect anything. I don't think NFC can be enabled without root and adding some files that are missing.
Sent from my Nexus 6P using XDA Labs
Verizon promised to add pay and turn NFC on I say we hold them to it as owners of their watch discontinued or not this is as advertised.
https://www.verizonwireless.com/support/knowledge-base-209381/
Is it possible that kernel doesn't include NFC drivers? Kernel sources here contain the NFC drivers, but are they on the device?
Hi,
Added a tag to Title to avoid confusion.
I really appreciate the kind of topics you post here. Thanks for sharing information that is actually helpful. Good day!
Not working for me so far. I'm going to try it again at a McDonalds kiosk, but I found something of relevance...
It appears no NFC service is registered on my Wear24, so if there's no service to call... there should be no way to enable NFC. Note that I'm on AW 2.15
Log proving no service exists: https://textuploader.com/dvc7s
The only way to fix this is with a whole new ROM update, be it by the community or Verizon.
Anything going on?
Now that we have got the new wearOS 2.0 and nothing from Verizon coukd we pretty much say that the odds of getting Google Pay working on this watch are almost none?
Hello everyone,
I've got an 'error: This device cannot start (Code 10) after manually installing Android ADB Device driver within Window's Device Manager. Android ADB Device is displayed with a yellow exclamation mark. This results in a blank answer after 'adb devices'. In other words: my laptop cannot connect to my watch and thereby I can't install Watch Droid Assistant on my watch.
I really need this app because of it's notification history feature, even after opening the notification (just like the amazfit Bip has)!
And secondly because of the possibility of increasing the font size.
Does anyone know the cause & the solution?
Thanks in advance!
Robert.
P.S. While being a newbie on 'tweaking' the Amazfit Stratos, I've some additional questions:
1. Will installing Watch Droid Assistant void warranty (unlocking the bootloader?)?
2. Are there risks of bricking my Amazfit Stratos (how high?)?
3. Is it (after installling WDA) possible to install additional apps such as a calculator or calendar etc. ? Or do I need Applist?
Used hardware, software and versions:
Watch Droid Assistant (27.03.2018 - version 6.1)
Amazfit Stratos (US version, FW: 2.3.4.0)
Windows 7 Home Premium (SP1 64-bit)
I've used "15 seconds ADB Installer v1.4.3.exe" from XDA website (ADB: yes, system-wide: no, device drivers: yes).
1. Installing WD won't void anything, as with any other APK. Unlocking bootloader will void watch's warranty as soon as you enter the code to unlock it.
2. Almost zero, unless you are very unlucky. Uninstall or a factory reset will remove any apps from watch.
3. You can add other apps, but be aware that the watch has only 512MB of RAM so you don't want to install anything that runs in the background, slowing it down.
As for the drivers, if removing the device and/or forcing a driver refresh doesn't work, you may need to disable driver signature on Win 64-bits (bcdedit /set TESTSIGNNING OFF), something like this:
https://support.microsoft.com/en-us...est-mode-message-that-is-displayed-in-windows
theres an app for receiving messages and theres a thread in this forum about it. look for notifications for amazfit (with a red icon) on the google play store. its nice and simple, allows you to change text size and all. and its very cheap.
last watch and app updates kind of messed it up a little but the devs seem to be very caring and may be already looking for solutions. all in all, its usable now.
Thank lfom
xxxdiegoxxx said:
theres an app for receiving messages and theres a thread in this forum about it. look for notifications for amazfit (with a red icon) on the google play store. its nice and simple, allows you to change text size and all. and its very cheap.
last watch and app updates kind of messed it up a little but the devs seem to be very caring and may be already looking for solutions. all in all, its usable now.
Click to expand...
Click to collapse
watch droid assistant?
thanks
I had a problem with my usb connection on my Pace. Turns out the two pins for the usb connection were corroded. But I managed to install apks (especially Watch Droid assistant), through wifi and ADB commands.
Again, this has been done on an Amazfit Pace, through ADB commands on Linux, specifically on Kubuntu 18.04. I don't have the Stratos, so I don't know if this applies to that watch.
1. Go to Settings - Connection - WiFi and connect to your WiFi network. Now this is important. In order to maintain connection, you have to be in the WiFi tab AND keep the screen on at all times, until you finish the installation (look for an app called Pace-On, for later installations).
2. Find your watch's IP. I did that by looking on my router's connected devices.
3. Open terminal (or CMD) and type adb connect and put your watch's IP. Example:
adb connect 192.168.0.15
4. Type adb devices, to make sure and verify that your device is connected.
5. Type adb install /path/to/apk/application.apk
(Where /path/to/apk/application.apk is the path you downloaded or placed your app) If you get an error or failure of installation (it usually happens when you have an older version of the same app) try to type
adb install -r /path/to/apk/application.apk
Another way is to manually delete the old version app and install the new one. You'll figure it out.
6. Wait for it to finish. When it does, see if the app is installed on your watch. You don't (usually) have to restart the watch, but if you feel that there is a need to do so, then do so.
That's it! Hope it helps.
Hi all,
I updated to EMUI 9 (build 9.0.0.159) and since then I receive a dialog / prompt, when I try to enable Bluetooth automatically. Basically I use Tasker to turn on Bluetooth when I plug the Honor in my car.
The message is not related to Tasker, but comes from Android.
The message says "Tasker is requesting permission to turn on Bluetooth. Allow?" and looks similar to this dialog:
Sorry, don't have enough posts to post external links, but you can find it on Google by searching for "is requesting permission to turn on Bluetooth"
Tasker is already granted Device Admin permissions.
So right now I am looking for what changed and how to give Tasker the permission it needs.
One of my ideas is that the update reverted some permissions I set using ADB, but I can't verify this at the moment.
Any thoughts on this are greatly appreciated.
Thanks for reading
Cal