Closed piweihwt closed 6 years ago
If it is shown as disabled in Accessibility settings and it's still running, that would be a bug in Accessibility. ICS seems to be the worst when it comes to accessibility issues. You can confirm if VN is still running by checking if new notifications (such as the test notification) are still appearing in the Notification Log.
I'm not sure if this is same issue you're experiencing, but it may help to read some of the replies: http://code.google.com/p/android/issues/detail?id=23105
Thanks for your answer. I found that in my app like yours, When I restart my phone, the checkbox is on but can not revived any notify.
Is it also a big? thanks
Sent from my iPhone
On 2013-6-6, at 8:50, Mark Injerd notifications@github.com wrote:
If it is shown as disabled in Accessibility settings and it's still running, that would be a bug in Accessibility. ICS seems to be the worst when it comes to accessibility issues. You can confirm if VN is still running by checking if new notifications (such as the test notification) are still appearing in the Notification Log.
I'm not sure if this is same issue you're experiencing, but it may help to read some of the replies: http://code.google.com/p/android/issues/detail?id=23105
— Reply to this email directly or view it on GitHub.
Yes, that would also be a bug with Accessibility. Turning it off and back on should get it working.
Yes ,I know,And there is nothing to do with this bug?
Such as Sony smart watch, It does not have this issue.
Thanks^_^
Sent from my iPhone
On 2013-6-7, at 7:58, Mark Injerd notifications@github.com wrote:
Yes, that would also be a bug with Accessibility. Turning it off and back on should get it working.
— Reply to this email directly or view it on GitHub.
If there is something I can do, I don't know what it is and it would be nearly impossible to troubleshoot and test fixes when I can't reproduce the issue. There are different types of accessibility services, so I can only guess that the reason the smart watch doesn't have the problem is because it is configured as a different type that doesn't have the bug.
The VoiceNotify often turn off (disable) on my Samsung Galaxy S3 Android 4.3 rooted device. I checked the status of it in the app, and sometims is disabled. But the Accessibility is enabled. If I disable and re-enable the Accessibility of it, after the VoiceNotify is working again for some minutes (only).
While I was never able to reproduce, this was very likely fixed in 682bbb7 by reading notifications through Notification Listener Service instead of Accessibility Service. That would get rid of all the weird issues specifically with accessibility services.
Unfortunately, this means VN no longer supports versions of Android prior to 4.3. While I could have gone through the trouble of supporting both methods according to Android version, I recently received an email from Google telling me their policy only permits the use of accessibility for apps designed for users with disabilities. So, to make sure VN doesn't get removed from the Play Store, the accessibility service was completely removed.
The VN service still needs to be manually enabled in Android settings after install, now in Notification Access instead of Accessibility. The top option in VN will take you to the correct settings screen.
Running on 4.0.4.
And when I restart my phone, NP Service can't work. Why?