[Bug] Hardware keys unresponsive when it's force closed/crashed

DHM47 / Native-Clip-Board

Add native clip board functionality to android using Xposed Framework

GNU General Public License v2.0

107 stars 31 forks source link

[Bug] Hardware keys unresponsive when it's force closed/crashed #45

Open Septolum opened 8 years ago

Septolum commented 8 years ago

When native clipboard is force closed/crashed (usually due to low memory in my case), my capacitive hardware keys respond with tactile feedback, but do not actually do anything. For me to get them to work again, I must manually restart the app/service in accessibility in settings

DHM47 commented 8 years ago

Does this still happen to you ? I just found a way to detect when the device is running low on RAM, so disabling hardware keys monitoring at that point might fix it.

Septolum commented 8 years ago

It did right up until I got a new more powerful phone, no issues so far (stopped using the other one a little over a week ago) I do have an old phone with little memory if you'd like me to try and test it

I should mention none of the phones used had/have xposed framework installed

DHM47 commented 8 years ago

I would appreciate if you can test it. Please send me an Email at dhm47.dev@gmail.com