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:
Related
Simple module to make Android Auto less restrictive. History on this module can be found here and an article about the in-motion tap limits here. This module should remove the "speed bump" notification (Browsing locked for safety) and allow you to scroll through lists (playlists, song lists, etc) without hindrance.
There's also a reddit thread/request which has more specifics about what this module is trying to accomplish.
Features:
Should work for all aftermarket AA-capable headunits (might require a hard-wired bypass module depending on model)
Should also work for most OEM AA headunits that are built into newer vehicles
Should also work for standalone AA running on a phone and not connected to a headunit
Here comes the really large and obnoxious disclaimer.......
This module can alter the built-in safety features that Google has implemented in Android Auto. By downloading and installing, you agree that YOU, and only YOU, are solely responsible for any negative repercussions that may result. This can include injury to yourself and/or others, property damage, or loss of life. Under no circumstances is the author of this module responsible for its use!
...not that a simple disclaimer on a forum post would go far if anything were to happen, but I felt the need to put it out there. Please use YOUR best judgement when it comes to operating a vehicle and futzing with your Android Auto headunit.
Development and testing was done on a Nexus 5x running Android Auto v1.6.240040 (2719917-release) and a Pioneer AVH-4200NEX w/ micro bypass. This should work on any Lollipop and newer rom, assuming Android Auto works on it.
Downloads
See attached files on this post.
You can also grab it from the Xposed Repo
XDA:DevDB Information
Sensible Android Auto:Xposed , Xposed for all devices (see above for details)
Contributors
agentdr8
Source Code: Gitlab
Xposed Package Name: com.dr8.xposed.saax
Version Information
Status: Stable
Current Stable Version: 6.3.611314
Stable Release Date: 2021-04-12
Created 2016-06-04
Last Updated 2021-04-12
Reserved
In case it isn't already clear, this APK is a module designed to be used with the Xposed Framework. It will do absolutely nothing on its own.
Changelog
v6.3.611314 - Updated for Android Auto 6.3.611314
v6.1.610544 - Updated for Android Auto 6.1.610544
v5.8.604354 - Updated for Android Auto 5.8.604354
v5.7.603964 - Updated for Android Auto 5.7.603964
v5.7.603954 - Updated for Android Auto 5.7.603954
v5.6.603444 - Updated for Android Auto 5.6.603444
v5.6.603434 - Updated for Android Auto 5.6.603434
v5.5.602944 - Updated for Android Auto 5.5.602944
v5.5.602934 - Updated for Android Auto 5.5.602934
v5.4.502264 - Updated for Android Auto 5.4.502264
v5.3.501644 - Updated for Android Auto 5.3.501644
v5.3.501634a - Updated for Android Auto 5.3.501634 (fixed negative value)
v5.2.501054 - Updated for Android Auto 5.2.501054
v5.1.500644 - Updated for Android Auto 5.1.500644
v5.0.500214 - Updated for Android Auto 5.0.500214
v4.9.594934 - Updated for Android Auto 4.9.594934
v4.8.594324 - Updated for Android Auto 4.8.594324
v4.7.593824 - Updated for Android Auto 4.7.593824
v4.7.593814 - Updated for Android Auto 4.7.593814
v4.6.593334 - Updated for Android Auto 4.6.593334
v4.6.593324 - Updated for Android Auto 4.6.593324 and 4.6.59xxxx (for 32-bit)
v4.5.592854 - Updated for Android Auto 4.5.592854 and 4.5.592xxx (for 32-bit)
v4.4.592344 - Updated for Android Auto 4.4.592343 and 4.4.592344
v4.3.591854 - Updated for Android Auto 4.3.591843 and 4.3.591854
v4.2.591444 - Updated for Android Auto 4.2.591444 - Versioning has now been changed to mimic the AA versions so that it is clear which version of SAAX works with which version of AA
v1.9.3.2 - Updated for Android Auto 4.2.591xxx
v1.9.2 - Updated for Android Auto 4.2.591xxx
v1.9.1 - Updated for Android Auto 4.1.590xxx
v1.9.0 - Updated for Android Auto 4.0.590xxx
v1.8.9 - Updated for Android Auto 3.9.585xxx
v1.8.8 - Updated for Android Auto 3.8.584xxx
v1.8.7 - Updated for Android Auto 3.7.584xxx
v1.8.6 - Cleaned up debug logging and bumped version
v1.8.5c - With @xs1337's help, added overrides to CarSensorEvent classes which should help those with OEM headunits
v1.8.5a - Fixed typo in method name which was throwing exceptions
v1.8.4 - Updated for Android Auto 3.6.583xxx
v1.8.3 - Updated for Android Auto 3.5.583xxx
v1.8.2 - Added another overridden method to try and bypass warnings, cleaned up comments
v1.8.1 - Added more overridden methods to try and bypass warnings
v1.8.0 - Updated for Android Auto 3.4.582xxx
v1.7.8 - Updated for Android Auto 2.9.574xxx -- missed a method name change
v1.7.7 - Updated for Android Auto 2.9.574xxx
v1.7.6 - Updated for Android Auto 2.8.57451x
v1.7.5a - Missed a method name change
v1.7.5 - Updated for Android Auto 2.7.57395x
v1.7.4 - Updated for Android Auto 2.6.57340x -- added additional options to hopefully override vehicle sensors
v1.7.3 - Updated for Android Auto 2.5.72860x
v1.7.2 - Updated for Android Auto 2.4.72280x
v1.7.1 - Add additional parameter override to get rid of "Paused for your safety" messages
v1.7 - Updated to support the latest Android Auto (2.3.716603-release)
v1.6 - Updated to support the latest Android Auto (2.2.710803-release)
v1.4a - Updated to support latest Android Auto (2.0.642303-release)
v1.3 - Added preference for how many pages are shown in list views
v1.2 - Unreleased, but work done to address built-in vehicle sensors
v1.1 - Updated method hook to include an additional setting, and properly calculate meters/sec from MPH. Also fix initial TypeError crash upon first launch
v1.0 - Initial release
What does this mod do?
"Make Android Auto less restrictive" is very vague, and the history thread is disorganized. Can you add a feature list?
Livingod said:
What does this mod do?
"Make Android Auto less restrictive" is very vague, and the history thread is disorganized. Can you add a feature list?
Click to expand...
Click to collapse
Sorry about that. I've added a few lines about what it does to the OP.
Hi great work so far! Where can I download it?
ahaan said:
Hi great work so far! Where can I download it?
Click to expand...
Click to collapse
In Xposed [emoji12]
☆☆☆ ☆☆☆
amazing, exactly what I have been looking for.
Installed on a Sprint Galaxy S5 with blisspop rom. Will give it a run tomorrow and report back. I just set the number of taps to 999.
ahaan said:
Hi great work so far! Where can I download it?
Click to expand...
Click to collapse
That's odd. When I edit the first post, I can see that the APK is attached. But it isn't showing up. It's probably something to do with the DevDB project.
I've added it to the Downloads tab up top though. And I'll put the xposed repo link on the OP.
Works great! thank you for this. This is highly needed and worked with out a hitch for me on a quick test of spotify (was on a quick drive and was unable to test everything)
agentdr8 said:
That's odd. When I edit the first post, I can see that the APK is attached. But it isn't showing up. It's probably something to do with the DevDB project.
I've added it to the Downloads tab up top though. And I'll put the xposed repo link on the OP.
Click to expand...
Click to collapse
Looks great now, downloaded and tested successfully with the Head unit hack using self mode! Great experience
update on my test, works great on my Sprint Galaxy S5 with blisspop 6.0 rom with the pioneer 4100nex. The first time I tried, AA seemed to have froze when I tapped Spotify, removed the usb and replugged it back in, but the module didnt seem to work, it only allowed 6 taps. On my 2nd drive, it worked great scrolling through my entire playlist when I was in movement
Thank you!! Works great on my Droid Turbo with CM13, Pioneer 4200 NEX.
First time I started AA it froze and crashed with "cannot connect to AA at the moment, when safe please disconnect and check your phone." All I did was disconnect and plug it back in, and it's been great ever since.
ranova said:
The first time I tried, AA seemed to have froze when I tapped Spotify, removed the usb and replugged it back in
Click to expand...
Click to collapse
Jeffy! said:
First time I started AA it froze and crashed with "cannot connect to AA at the moment, when safe please disconnect and check your phone." All I did was disconnect and plug it back in, and it's been great ever since.
Click to expand...
Click to collapse
Interesting. If it continues to happen, please enable debug in the settings and provide the Xposed Installer logs + logcat so I can account for this behavior.
agentdr8 said:
Interesting. If it continues to happen, please enable debug in the settings and provide the Xposed Installer logs + logcat so I can account for this behavior.
Click to expand...
Click to collapse
I've used it about 10 times since then, running errands and whatnot. It's been working perfectly for me, no glitches!
agentdr8 said:
Interesting. If it continues to happen, please enable debug in the settings and provide the Xposed Installer logs + logcat so I can account for this behavior.
Click to expand...
Click to collapse
Jeffy! said:
I've used it about 10 times since then, running errands and whatnot. It's been working perfectly for me, no glitches!
Click to expand...
Click to collapse
yup, only happened to me the first time after installing the module. Its been working ever since. Thanks again!
This is fantastic! Great job. Let's hope you will be able to add more features in the future or that other developers will join you. I love Android Auto but the current restrictions (on which apps can be used for example) are just plain stupid. I understand that there are people who would abuse Android Auto to type entire messages while driving if it was possible but that is not the responsibility of Google. At least, it wouldn't be the responsibility of Google in Europe. It's a totally different story in the US of course
Updated the module today. I figured out that the values for "unlimited browsing speed" and "max speed parking card" were in meters per second (float), so the default of 0.5F is roughly 1.1 MPH. I've made an adjustment so the preference slider accurately represents MPH at which it will no longer allow for unlimited browsing.
Of course if you have the tap limit set to max, then it won't matter. But a sensible tap limit, combined with a sensible max unlimited browsing speed is now achievable.
I also addressed the crash at initial launch.
Hi agentdr8,
Great Module! Congratulations!
One suggestion: Please, can you add the option of "Execute action in the CAR screen"? The idea is: add one entry in this "unused" menu for trigger a Broadcast Intent; this intent then will be captured and processed by another App (like Tasker, AutomateIt, Llama, etc.)
Here some guide about "Broadcast Intent": http://inchoo.net/dev-talk/android-development/broadcast-receiver-from-activity/
For the "Car Screen" see: http://arstechnica.com/cars/2015/07...icle-diagnostic-app-expanded-car-integration/
I hope you agree! :fingers-crossed:
manos78 said:
Hi agentdr8,
Great Module! Congratulations!
One suggestion: Please, can you add the option of "Execute action in the CAR screen"? The idea is: add one entry in this "unused" menu for trigger a Broadcast Intent; this intent then will be captured and processed by another App (like Tasker, AutomateIt, Llama, etc.)
Here some guide about "Broadcast Intent": http://inchoo.net/dev-talk/android-development/broadcast-receiver-from-activity/
For the "Car Screen" see: http://arstechnica.com/cars/2015/07...icle-diagnostic-app-expanded-car-integration/
I hope you agree! :fingers-crossed:
Click to expand...
Click to collapse
I'll see what can be done about adding some things to that screen. I'm not positive, but I believe most apps won't be able to display any activities on that screen unless they have specific Android Auto layouts. But firing off a configurable intent should be possible.
Stay tuned....
EDIT: Upon further investigation, it seems that this isn't doable right now. Those entries under the "Car" screen are services that have to be defined in the manifest. AFAIK, you can't inject service entries (and their associated metadata tags) into an app via Xposed. I think at some point, Google may open up that restriction for OEMs, and allow them to just apply a specific xml description tag to indicate that a particular app can be shown/used in that screen.
I can try and see if I can hook the layout inflation of those entries, and modify their titles there. I can also try and override what they currently launch (right now, just demo screens).
agentdr8 said:
EDIT: Upon further investigation, it seems that this isn't doable right now. Those entries under the "Car" screen are services that have to be defined in the manifest. AFAIK, you can't inject service entries (and their associated metadata tags) into an app via Xposed. I think at some point, Google may open up that restriction for OEMs, and allow them to just apply a specific xml description tag to indicate that a particular app can be shown/used in that screen.
I can try and see if I can hook the layout inflation of those entries, and modify their titles there. I can also try and override what they currently launch (right now, just demo screens).
Click to expand...
Click to collapse
Hi agentdr8,
Thank you for your efforts! Good work! :good:
In reference to the limitations: Then I suggest to just hook the button for selecting the CAR screen. I feel this can be possible, and we use this event to trigger some intent. Please, think that sending one intent is by far more simple that printing on the screen. So, perhaps the first goal can be hook the AA UI for sending events to other Apps. You agree?
Is it possible to develop apps or watchfaces and distribute by Samsung store for new Gear Fit 2? Some developer can confirm that or not?
Yes you can. Just need to sign up through the Samsung Tizen developer site and then build the apps/watches faces to the store.
MynticeLX said:
Yes you can. Just need to sign up through the Samsung Tizen developer site and then build the apps/watches faces to the store.
Click to expand...
Click to collapse
Thanks for your reply. I am curious how to test an app. I bought device Gear Fit 2. I will able to test on device or need some emulator from Tizen developer site?
I have an idea for small quiz app from school time and maybe will be possible to push it to gf2, maybe.
MynticeLX said:
Yes you can. Just need to sign up through the Samsung Tizen developer site and then build the apps/watches faces to the store.
Click to expand...
Click to collapse
I wonder if it possible now to sell apps by Samsung Apps store now?
Did you try to do that?
space below music player on gear fit 2 drop down menu
The Gear Fit 2 drop down menu has an empty rectangle below where it says music player. I wish this could be assignable or at least let you tap home. In order to go home in a lot of cases you have to hit the home button. I wish you could swipe and tap your way through on the screen itself.
christopherwice said:
The Gear Fit 2 drop down menu has an empty rectangle below where it says music player. I wish this could be assignable or at least let you tap home. In order to go home in a lot of cases you have to hit the home button. I wish you could swipe and tap your way through on the screen itself.
Click to expand...
Click to collapse
There's no support from the Tizen Studio (installed latest version 1.1.0). So, there's no template, you'll have to start from scratch. There's also no Emulator template either. There's great examples included, incl. native app which shows how access sensors (runs great in the emulator). The Fit2 is fully Tizen RTOS compatible. I tried to use one of the S2 examples to make it Fit2 compatible. Not luck, W/o a working template and a working emulator I give up...
So at this moment we can't really develop apps unless we know how to make it from scratch? No help for amateurs?
sirmart1n said:
So at this moment we can't really develop apps unless we know how to make it from scratch? No help for amateurs?
Click to expand...
Click to collapse
Correct, Samsung policy, buy at your own risk...
The screen res is 216x432. I made layout pics to use with the emulator. The db-file is the button assignment file. But haven't figured out yet, how everything works together.
mikeathome said:
Correct, Samsung policy, buy at your own risk...
The screen res is 216x432. I made layout pics to use with the emulator. The db-file is the button assignment file. But haven't figured out yet, how everything works together.
Click to expand...
Click to collapse
Such a shame. It has lot of potential. Decent hardware and software that offers a lot as well. Could you please let me/us know if you figure something out? If Samsung doesn't want to help me use my watch to its full potential, I would happily spend my time doing that myself.
sirmart1n said:
Such a shame. It has lot of potential. Decent hardware and software that offers a lot as well. Could you please let me/us know if you figure something out? If Samsung doesn't want to help me use my watch to its full potential, I would happily spend my time doing that myself.
Click to expand...
Click to collapse
Success, partially...
I got an emulator working, BUT the screen settings are not ok, screen elements are being cut off, have to investigate...
Somebody interested helping me?
Emulator running: http://imgur.com/Uzdk0zB
Settings cut-off: http://imgur.com/nYeKZLi
Settings itself ok: http://imgur.com/pBaPrEk
Power Off ok too: http://imgur.com/Ir0p5sd
Both buttons (back and Home) are working.
If I find a way to make the emulator robust, no screen cut-off I can transfer sample apps from Gear S2 to Fit2. That's the first steps of developing own apps for this thing.
mikeathome said:
Success, partially...
I got an emulator working, BUT the screen settings are not ok, screen elements are being cut off, have to investigate...
Somebody interested helping me?
Emulator running: http://imgur.com/Uzdk0zB
Settings cut-off: http://imgur.com/nYeKZLi
Settings itself ok: http://imgur.com/pBaPrEk
Power Off ok too: http://imgur.com/Ir0p5sd
Both buttons (back and Home) are working.
If I find a way to make the emulator robust, no screen cut-off I can transfer sample apps from Gear S2 to Fit2. That's the first steps of developing own apps for this thing.
Click to expand...
Click to collapse
This looks promising. I would gladly help but I don't think that I would be of any use with my lack of skills.
I have Neonto studio installed which looks like an easy way of creating apps but I could not figure out how to get the app on my watch. Probably because there is no emulator for it in Tizen Studio.
sirmart1n said:
This looks promising. I would gladly help but I don't think that I would be of any use with my lack of skills.
I have Neonto studio installed which looks like an easy way of creating apps but I could not figure out how to get the app on my watch. Probably because there is no emulator for it in Tizen Studio.
Click to expand...
Click to collapse
You need the Tizen Studio to get apps onto the watch. In developer mode.
There's no template for this watch for Tizen Studio, so the interfaces are not declared (API to sensors), the screen resolution is not set (see my cut-off settings screen) and the GUI elements are not defined (swipe, L/R. D/U, no ring like Gear S2). I doubt that there'll be apps for this watch until some skilled person adds this to the SDK...
if somebody is interested I can send them what i did so far, it'll save some time in doing the emulator templates.
mikeathome said:
You need the Tizen Studio to get apps onto the watch. In developer mode.
There's no template for this watch for Tizen Studio, so the interfaces are not declared (API to sensors), the screen resolution is not set (see my cut-off settings screen) and the GUI elements are not defined (swipe, L/R. D/U, no ring like Gear S2). I doubt that there'll be apps for this watch until some skilled person adds this to the SDK...
if somebody is interested I can send them what i did so far, it'll save some time in doing the emulator templates.
Click to expand...
Click to collapse
Three questions/requests:
1. What SDK did you use for Gear Fit 2? Wearable 2.3 or 2.3.1 or is there one for Gear Fit 2?
2. Are you able to push your app/project into your Gear Fit 2 via debug mode or something?
3. Would you be able to share your sample project that is tested to work on Gear Fit 2?
Best regards!
Joms_US said:
Three questions/requests:
1. What SDK did you use for Gear Fit 2? Wearable 2.3 or 2.3.1 or is there one for Gear Fit 2?
2. Are you able to push your app/project into your Gear Fit 2 via debug mode or something?
3. Would you be able to share your sample project that is tested to work on Gear Fit 2?
Best regards!
Click to expand...
Click to collapse
Hi only started to experiment today with my new fit 2. And got a hello tizen app on the fit 2. I was only following the samsung step by step guide.
1.) Used 2.3.2
2.) Yes, debug mode is working
Now i need to investigate how to build a minimal ui. I want to build a small app, that unlocks my smart door lock.
1.) enable wifi
2.) wait until connected to my router
3.) get thet state of the lock
4.) send the unlock command
5.) close app and disable wifi
So i'm able to go running without any additional key or phone.
notz76 said:
Hi only started to experiment today with my new fit 2. And got a hello tizen app on the fit 2. I was only following the samsung step by step guide.
1.) Used 2.3.2
2.) Yes, debug mode is working
Now i need to investigate how to build a minimal ui. I want to build a small app, that unlocks my smart door lock.
1.) enable wifi
2.) wait until connected to my router
3.) get thet state of the lock
4.) send the unlock command
5.) close app and disable wifi
So i'm able to go running without any additional key or phone.
Click to expand...
Click to collapse
Thanks for responding, so how did you get 2.3.2? It is not showing up under Tizen Update Manager?
Joms_US said:
Thanks for responding, so how did you get 2.3.2? It is not showing up under Tizen Update Manager?
Click to expand...
Click to collapse
I have today installed the latest version of tizen sdk for linux and their it is the the latest 2.x version for wearables.
notz76 said:
I have today installed the latest version of tizen sdk for linux and their it is the the latest 2.x version for wearables.
Click to expand...
Click to collapse
Hmmm I am running mine on Windows, that might be the reason.
I think I know the reason now, I downloaded the Tizen SDK 2.4 not the Tizen Studio 1.1.1 so now I have the 2.3.2 option. =D
notz76 said:
Now i need to investigate how to build a minimal ui. I want to build a small app, that unlocks my smart door lock.
1.) enable wifi
2.) wait until connected to my router
3.) get thet state of the lock
4.) send the unlock command
5.) close app and disable wifi
So i'm able to go running without any additional key or phone.
Click to expand...
Click to collapse
Nice. That's exactly what I would like to use my watch for. I don't have a smart door lock but I'm planning on getting one in the future. Right now I wish I was able to make an app for MacID or a simple shopping list/reminder app
Great idea - I am starting research to try something similar
notz76 said:
Hi only started to experiment today with my new fit 2. And got a hello tizen app on the fit 2. I was only following the samsung step by step guide.
1.) Used 2.3.2
2.) Yes, debug mode is working
Now i need to investigate how to build a minimal ui. I want to build a small app, that unlocks my smart door lock.
1.) enable wifi
2.) wait until connected to my router
3.) get thet state of the lock
4.) send the unlock command
5.) close app and disable wifi
So i'm able to go running without any additional key or phone.
Click to expand...
Click to collapse
If you make any progress, I'd be keen to hear, and I'm happy to share what I get done too.
I will probably look at it sometime over the next month when I have time as I am a complete noob to Tizen.
I never thought to have the watch directly open the door (but now I am going to copy that idea - thanks), originally I just wanted to have the watch trigger phone to open door (to avoid getting phone out to open door) I previously had tasker detecting the phone shaking trigger my door unlock, but It would be much neater to get the watch to do that instead.
Door unlock is simple https request with authentication token.
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.
I have recently purchased an IQ Panel 2 (Android 5.1.1) home/office/etc. Alarm system.
I assumed I would have access to the full Android OS, not root access, just basic access like all phones and tablets. (this is NOT the case)
The Tablet/device starts with the power button and from there goes directly to the custom alarm software app.
There are NO physical buttons (other than the power button) that I can see on the board inside the case.
There is a USB port but apparently it is only for charging.
The device supports Bluetooth but only via the app and not the actual 'Bluetooth Settings' screen on Android and therefore I am unable to pair a Bluetooth keyboard or mouse.
I have the desire to add Tasker and a custom launcher such as NOVA launcher so that I can have even greater control over my Z-wave and Bluetooth devices as well as additional custom notifications etc.
A port scanner shows port 8883 open but I believe that might be for z-wave communication?
The device has expansion slots on the board. 2 are in use and a 3rd is open for a secondary image sensor and a 4th is for future expansion.
Any suggestions on how to proceed would be of immense help.
I hate the idea of returning this device because of this limitation.
I have spoke with the manufacturer Qolsys and they informed me the end-user is blocked from these features for obvious reasons.
There is a youtube video detailing everything about the device: Qolsys: IQ Panel 2 Technical Webinar (Can't post links yet)
Thanks in advance for any help.
26 views but no responses?
anyone have any ideas?
IIIHomieIII said:
26 views but no responses?
anyone have any ideas?
Click to expand...
Click to collapse
contact me i have same device
Contact..
Wondering?
I just got a Qolsys IQ Panel 2. I feel the same way. Were you able to root the Panel? Using the full Andriod opens the door for a better IQ Panel.
melmel1989 said:
contact me i have same device
Click to expand...
Click to collapse
Could you also help me with this iq panel I recently got it and want full features
Update
No, unfortunately I was never able to get basic access or root access but I did accomplish the original features I wanted via an older Android phone on wifi only that I use in conjunction with the IQ Panel 2.
The secondary phone runs a few apps and sits in a separate room with the screen dimmed to near black/hardly visible screen brightness.
It performs the following functions:
Custom voice commands including disarming the IQ Panel on a weekday morning schedule at 7am and/or by talking to the Google Assistant via my personal phone or a family member's phone or a Google Assistant speaker of which we have several throughout the home.
Turning on the smart thermostat when the temperature in the home is above or below a certain temperature.
Opening the garage door via voice command and being alerted when it is open or left open as if it were a window or door sensor.
Setting voice profiles so when opening the garage door or disarming the IQ Panel only that person's voice works. My voice or my wife's but not guests or the kids voices control these functions.
Being able to have the alarm disarmed by my children's phone via Bluetooth but having the alarm disarmed notification go to email instead of text.
(Necessary because through the Alarm.com website limited settings.. my kids would be notified everytime we get home and since they don't live with us anymore that would be annoying to them daily to get texts but they still need to know the alarm had been disabled by the their Bluetooth phone proximity to the IQ Panel and email only when their phones are in proximity and disarm the alarm. Email solves this.
All of this could have been done with just the IQ Panel if we had basic access not even root but one older Android phone from the past that stays plugged in at all times solves the dilemma.
I do this by running the Autovoice app on the extra phone. Autovoice integrates with Google Assistant and between those two apps, Tasker app, the Alarm.com app, smart thermostat app, Auto-input app, and Autonotification app, Tasker send mail add-on plus a little time and setup it works flawlessly.
I believe this was less then $20 total for all apps.
Basically you can have the Autovoice app set predefined voice specific commands interact with the IQ Panel alarm.com app notifications and respond to those notifications with a predefined event.
My service is not monitored but to use the Bluetooth proximity alarm disarm feature built in to the IQ Panel 2 system you have to at least have basic service which I pay $14 a month to Geoarm.com. This also gives me the Alarm.com website service where I can set other rules that the alarm follows and the spare Android phone interacts with.
The Apps have widgets on the screen of the spare Android phone. If the IQ Panel 2 sends a notification via the app, the Autonotification app sees this and launches the Auto-input app which presses one of several widgets on the spare Android phone (as if I opened the Alarm.com app and pressed buttons/widgets myself)
It would have been nice to integrate this into just the IQ Panel 2 but about an hour of setup and configuration with an old phone on wifi only, the right apps and $40 ($20 for apps and $20 for a Google Assistant speaker) works too.
Hopefully this breakdown will help anyone with an IQ Panel 2.
Final thoughts:
I have 2 of these systems, one in my office and one at home. Since the office environment is not a family enviroment and a much more set schedule (closed at night etc.) None of this is necessary and the IQ Panel 2 works fine right out the box. With today's smart homes like mine with smart cameras, smart lighting, kids and pets with doors and windows opening at random times I think they should give us basic app installation rights on the IQ Panel 2 but..
I love this thing either way ?
I have tons of these alarm panels. I haven't tried to flash them, but assuredly it can be done.
My thoughts.
*The open port you have noticed is definitely not zwave, zwave doesn't use tcp/ip nor its ports of comm. That open port is likely a ssh or vpn to alarm.com or qolsys server for updates (tftp?)
*USB port. Have you tried using a OTG atapter? Doubt you will be able to put into debug mode for adb, but might see if you can connect with adb. Also think JTAG. But you could likely flash its firmwars the same way updates are pushed. Dust off your *nix box, run wireshark, may have to do a mitm to strip ssl, sniff out the server, intercept the update file, md5 checksums, spoof server on airgapped network, etc. But if they can update it, you can break into it.
I have been working on trying to figure out the Qolsis IQ panel. I found that it listens on two ports, 8883 and 12345.
8883 is MQTT however it requires a valid client certificate to connect which I'm trying to see if I can find.
12345 is a TCP websocket, you can connect to it with curl like curl -k https : / / 192.168.x.x:12345 and you will get a json stream of alarm events.
If you'd like, we have a thread on the Home Assistant forum where we are trying to figure this out too.
If you go to the home assistant community and search for qolsys you will find our post (I can't post links yet)
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.