Related
Allow only broadcasts you want for each app.
With this app you could prevent apps to receive broadcasts, e.g. "SD-card inserted" oder "W-Lan connected".
All with Android-18 shipped broadcast actions are integrated. Others will be collected from time to time and marked with an exclamation sign in the app.
Technical limiation: Actions wich are only sent and not received by any app could not be found.
Changed settings are applied after a reboot. For BOOT_COMPLETED please use the app BootManager.
To restrict system apps you have to donate. The key of "BootManager" is recognized by this app too!
Important:
This app needs the Xposed Framework. The framework requires root access for installation. Don't forget to enable the module in Xposed. You can grab it here: Xposed Installer
Donation:
No self-promotion in the app.
System apps could also be selected
Sorting by action, not only by app name
You support this app and further development!
Website: http://tinyurl.com/pkos9om
Play Store: http://tinyurl.com/p3dqxj2
Xposed Repository: http://tinyurl.com/q9u2l8o
Changelog: http://tinyurl.com/njov9yd
My personal intension to create this app:
There was no app which could do this
Translation:
You could find here a interface to translate the english strings: http://tinyurl.com/okycacj
A free account of www.oneskyapp.com is required to edit. Additional, please attach your email address or send it via PM
Kudos to you! This is great for development purposes!
However, you must warn the user that disabling Broadcast for some app just because he[user] thinks that might be a good idea is bad and user should think twice, as disabled Broadcast can result in a vary of results - from no effect to system crash.
For example, your favorite launcher is listening for the broadcast for call state. You're thinking - Ah-ha, it's spying on me! And you disable the broadcast. And then you are surprised, why does Phone app icon stopped displaying missed calls.
great thanks for that :good:
Dr.Alexander_Breen said:
However, you must warn the user that disabling Broadcast for some app just because he[user] thinks that might be a good idea is bad and user should think twice, as disabled Broadcast can result in a vary of results - from no effect to system crash.
For example, your favorite launcher is listening for the broadcast for call state. You're thinking - Ah-ha, it's spying on me! And you disable the broadcast. And then you are surprised, why does Phone app icon stopped displaying missed calls.
Click to expand...
Click to collapse
I'm not sure about wich i should warn, potentially are all dangerous to disable.
eg the brodcasts to update a widget are useless for you if you don't use a widget of the app. But you should not disable it if you are using the widget...
And some actions i do not even know, because the ReceiverStop collects them if you are using your apps...
Btw, the release of today shows a logfile with newly added actions.
defim said:
I'm not sure about wich i should warn, potentially are all dangerous to disable.
eg the brodcasts to update a widget are useless for you if you don't use a widget of the app. But you should not disable it if you are using the widget...
And some actions i do not even know, because the ReceiverStop collects them if you are using your apps...
Btw, the release of today shows a logfile with newly added actions.
Click to expand...
Click to collapse
No, you must not warn out every broadcast. Virtially, there is infinite set of them, as I can create my own broadcast as easy as 1-2-3. Just show the warning at the start that it's better not to meddle with the system app's broadcasts and that even user-installed apps can cause side effects without some broadcasts.
Dr.Alexander_Breen said:
No, you must not warn out every broadcast. Virtially, there is infinite set of them, as I can create my own broadcast as easy as 1-2-3. Just show the warning at the start that it's better not to meddle with the system app's broadcasts and that even user-installed apps can cause side effects without some broadcasts.
Click to expand...
Click to collapse
Warn about all? Good point
I'm wondering where's the best place. At startup is the changelog shown (if updated) and a message about xposed, if not installed/active. So it could be nothing is been read...
defim said:
To restrict system apps you have to donate.
Click to expand...
Click to collapse
How to donate? I click the bottom part within the module - no reaction whatsoever...
Edit: ok, that was through the website. I donated and received the key file! :good:
But... why "Maps" is not is the list of apps...?
Thanks...
Looki75 said:
How to donate? I click the bottom part within the module - no reaction whatsoever...
Edit: ok, that was through the website. I donated and received the key file! :good:
But... why "Maps" is not is the list of apps...?
Thanks...
Click to expand...
Click to collapse
Hi, i've planned to put donator apps for each app to the market, but had not time yet.
If a app is not shown, no receivers are detected for it unitl now. You could do:
1) show all apps by enable in settings. Then you have only the option to "diable all, even unknown"
2) or open (in this case) Maps and wait. If it gets a broadcast ReceiverStop adds it to internal list and 1) is not needed
Adding new receiver actions are always logged, independet if logging of allowed/denied is enabled
Dr.Alexander_Breen said:
No, you must not warn out every broadcast. Virtially, there is infinite set of them, as I can create my own broadcast as easy as 1-2-3. Just show the warning at the start that it's better not to meddle with the system app's broadcasts and that even user-installed apps can cause side effects without some broadcasts.
Click to expand...
Click to collapse
I've added a warning dialog in the latest version
defim said:
Hi, i've planned to put donator apps for each app to the market, but had not time yet.
Click to expand...
Click to collapse
How will then work the donation I made? Is there a possibility for me to appear like I bought the donation app?
This way, in case I wipe the phone, I can download from play store the donation app and don't need to bother you with e-mails "hey give me again the license file..."...
And will the donation app work as well for both "bootmanager" and "stopreceiver"?
defim said:
If a app is not shown, no receivers are detected for it unitl now. You could do:
1) show all apps by enable in settings. Then you have only the option to "diable all, even unknown"
2) or open (in this case) Maps and wait. If it gets a broadcast ReceiverStop adds it to internal list and 1) is not needed
Adding new receiver actions are always logged, independet if logging of allowed/denied is enabled
Click to expand...
Click to collapse
Strange... I did "show all apps" and Maps is here. This is OK.
But the yellow "!" appears side to it... doesn't it mean that receivers were used?
But at the same time, when I click on Maps, there is only the "stop all" line... that sounds not consistent...???
Maybe a sign of a bug?
Anyway, very good job! THANKS!!!
@Looki75:
I'm not sure yet of the donation apps. But i think it should be again 1 app for the 2.
On the 1st view are packages shown, system apps have a "!" -> could be more dangerous to change sth
On the 2nd view with the receivers of each app, evere action which is a custom action (= not listed in broadcast_actions.txt of Android platform-18 sdk) has a "!". These non-default actions have to be collected by the app.
So it's consistent Maybe not the same icon for both would be better...
Are you sure Maps receives broadcasts? I tried to get Manifest.xml by the apk, but apktool failed -.-
defim said:
@Looki75:
I'm not sure yet of the donation apps. But i think it should be again 1 app for the 2.
On the 1st view are packages shown, system apps have a "!" -> could be more dangerous to change sth
On the 2nd view with the receivers of each app, evere action which is a custom action (= not listed in broadcast_actions.txt of Android platform-18 sdk) has a "!". These non-default actions have to be collected by the app.
So it's consistent Maybe not the same icon for both would be better...
Are you sure Maps receives broadcasts? I tried to get Manifest.xml by the apk, but apktool failed -.-
Click to expand...
Click to collapse
Ok... I think I understand... your module is about BROADCASTS... I'm not a dev and not familiar with these... but is it the same than Autostarts (https://play.google.com/store/apps/details?id=com.elsdoerfer.android.autostarts)?
My dream is to have the exact same functions than Autostarts in an Xposed module.
You might wonder why... well as strange as it sounds, I have Xposed framework but I am un-rooted. So I can use modules, but I can't use Autostarts for example...
I thought your module would be this "similar", but there are more stuff shown in Autostarts than is your module...
You talk about "broadcasts" and Autostarts or similar (root toolbox for example) talk about "receivers for certain events"... is there a difference?
Is it a big deal to expand the scope of your module to equal Autostarts functions?
Thanks for your help!
@Looki75:
After talking a look at the screenshots of Autostarts, it seems that these are all broadcast receivers, so the apps should do the same (with other methods: root/xposed). My app has no nice-names for the action names. So i wonder how Autostarts shows receiver names which a apps creates by its own? Which actions did you miss exactly in my app? Maybe they are not related to broadcats.
I think extending ReceiverStop is not so a good idea, because it's only for intercept receiving broadcasts of app. But maybe a seperate app. I used LBE some time and I didn't like that it has much things i did not need.
defim said:
@Looki75:
After talking a look at the screenshots of Autostarts, it seems that these are all broadcast receivers, so the apps should do the same (with other methods: root/xposed). My app has no nice-names for the action names. So i wonder how Autostarts shows receiver names which a apps creates by its own? Which actions did you miss exactly in my app? Maybe they are not related to broadcats.
I think extending ReceiverStop is not so a good idea, because it's only for intercept receiving broadcasts of app. But maybe a seperate app. I used LBE some time and I didn't like that it has much things i did not need.
Click to expand...
Click to collapse
When you look at these:
http://forum.xda-developers.com/showpost.php?p=35634745&postcount=11040
http://forum.xda-developers.com/showpost.php?p=29420959&postcount=7059
it seems that MAPS has much more than that...
However, I just installed Autosarts on my phone and it shows nothing, just like in your module...
So I guess we're ok.
Thanks!
Looki75 said:
When you look at these:
http://forum.xda-developers.com/showpost.php?p=35634745&postcount=11040
http://forum.xda-developers.com/showpost.php?p=29420959&postcount=7059
it seems that MAPS has much more than that...
However, I just installed Autosarts on my phone and it shows nothing, just like in your module...
So I guess we're ok.
Thanks!
Click to expand...
Click to collapse
I don't know what this other app does. Maybe it shows sometimes simply all recevers for every app.
But I know that ReceiverStop shows per app the specific actions.
There is now a donation app available in Play Store for this app. (1 donation for both, ReceiverStop+BootManager)
I'm looking for a way to disable SMS and missed calls notifications from appearing on the stock (clock) lock screen widget on my rooted Note 3 (running 4.3). Could this tool acheive this and if so, how?
The following entries were logged when not answering a call and a call notification is shown on the lock screen:
[ReceiverStop] 2013-11-22 15:07:20 handle not: com.sec.android.SimpleWidget - android.intent.action.USER_PRESENT
[ReceiverStop] 2013-11-22 15:07:20 handle not: netgenius.bizcal - android.intent.action.USER_PRESENT
[ReceiverStop] 2013-11-22 15:07:20 handle not: netgenius.bizcal - android.intent.action.USER_PRESENT
[ReceiverStop] 2013-11-22 15:07:20 handle not: netgenius.bizcal - android.intent.action.USER_PRESENT
[ReceiverStop] 2013-11-22 15:07:20 handle not: netgenius.bizcal - android.intent.action.USER_PRESENT
[ReceiverStop] 2013-11-22 15:07:20 handle not: com.umang.dashnotifier - android.intent.action.USER_PRESENT
[ReceiverStop] 2013-11-22 15:07:20 handle not: com.roymam.android.notificationswidget - android.intent.action.USER_PRESENT
[ReceiverStop] 2013-11-22 15:07:20 handle not: com.sec.android.app.controlpanel - android.intent.action.PACKAGE_RESTARTED
Would I simply be able to disable android.intent.action.USER_PRESENT in the SimpleWidget app to disable the SMS being displayed in the lock screen?
What is the risk of trying this out?
Happy to donate if this will do the above.
Thanks,
Eddie
@sireddie:
I think android.intent.action.USER_PRESENT is not the right action.
From http://developer.android.com/reference/android/content/Intent.html:
Broadcast Action: Sent when the user is present after device wakes up (e.g when the keyguard is gone).
Click to expand...
Click to collapse
Just open ReceiverStop and look which actions are listed for the app. I'm using "SMS Unread Count" widget, which has only android.appwidget.action.APP_WIDGET_UPDATE, so this could be the right. (I've blocked APP_WIDGET_UPDATE for all apps i'm using, but without widget)
Risk? I think it's low. It could be that something does not anymore what you expected To be save, do a android backup - i've never needed one
I've just added strings for translation to the first post. If you attach here a translation, please send me you email address via PM.
Notice to @kalashenicof @jzak1083 @vipa
Dear friend!
The receiver "android.provider.Telephony.SMS_RECEIVED" is blocked
But receiver "android.provider.telephony.SMS_RECEIVED" is constantly being allowed
("Telephony" vs. "telephony")
Please fix it! Viber application is listening to both of them!
katada1 said:
Dear friend!
The receiver "android.provider.Telephony.SMS_RECEIVED" is blocked
But receiver "android.provider.telephony.SMS_RECEIVED" is constantly being allowed
("Telephony" vs. "telephony")
Please fix it! Viber application is listening to both of them!
Click to expand...
Click to collapse
Yes, Viber could receive both. ReceiverStop collects all receiver actions it could get on your device. If you open the GUI it build a list of apps and their receiver. If one receiver is missing, it was never been seen on your device. So it should not be a problem. Btw, if you select "deny all", this will also handle never seen before receiver.
Does you know which app should send this misspelled "android.provider.telephony.SMS_RECEIVED"?
Hi there.
i have used google up and down. But didn't find one example how to do this. I even don't know if this is possible.
I want to disable a receiver for a particular app. I have root. For example i have this:
android.intent.action.CONFIGURATION_CHANGED:
BroadcastFilter{edb90ff u0 ReceiverList{178f01e 568 system/1000/u0 local:f47ec59}}
BroadcastFilter{5ff4d53 u-1 ReceiverList{1275942 568 system/1000/u-1 local:c9f738d}}
BroadcastFilter{9e64aaa u0 ReceiverList{bb72995 10860 com.google.android.gms.persistent/10010/u0 remote:193d54c}}
BroadcastFilter{61ba762 u0 ReceiverList{9d9a62d 11015 com.google.android.gms/10010/u0 remote:7668544}}
can i block one of this receivers? if yes, how??
pm disable com.google.android.gms.persistent/android.intent.action.CONFIGURATION_CHANGED doesn't work. also with ./ not. Other combinations won't work either.
can i block somehow a underlying permission? i don't think so.
is system also a package? i cant find it. I only find it in the processlist with ps.
any ideas??
I know this is a very old thread. But it is Very interesting indeed. I found some apps in the play store that do exactly that but there not very beatufiul and also not open source. I'm planning on building one myself and trying right now to debug the process on how to disable receivers from the apps with no progress so far...
LuigiTheHunter said:
I know this is a very old thread. But it is Very interesting indeed. I found some apps in the play store that do exactly that but there not very beatufiul and also not open source. I'm planning on building one myself and trying right now to debug the process on how to disable receivers from the apps with no progress so far...
Click to expand...
Click to collapse
I also know this is old... I had an app that could disable receivers and services inside an app without root. I've been trying to find it for weeks...
I used it to disable basically everything inside OneUi except the app switcher. If I fully disable OneUi I save lots of battery but then app switch doesn't work
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:
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)