Closed susch19 closed 1 day ago
Confirmed as mentioned on XDA Not synced yet on todays sources so someone else should confirm if still persists on 21.11 source. Confirmed on LMI as well.
Smart pixels has a note that states this
Oh that is poorly translated, in german it says Dies kann dazu führen, dass der Touchscreen teilweise schlecht auf Berührungen reagiert
, which would translate into Note that in some cases it can result in worsen the touchscreen responsiveness
. So it works, but not as good.
The correct german translation should be: Dies kann dazu führen, dass bestimmte Elemente mit dem Touchscreen nicht reagieren.
which in contrast means, that it doesn't work for some areas at all, which is written in english.
But maybe this warning should be more pronounced, as this actually breaks specific apps completely.
The only thing is, why does it not happen directly after starting smart pixels, but only after reboot?
Sure but the issue here is that I can use my phone fully when smart pixels is ON before that reboot. After a reboot it got stuck. What difference would a reboot make here?
@susch19 Translations can be found here : https://crowdin.com/project/crdroid-translation/de
@susch19 Translations can be found here : https://crowdin.com/project/crdroid-translation/de
Thanks, I'll provide a suggestion for a change, so that the german translation matches the intent of the english one.
Another thing is, with android 13 (EvoX in this case), i didn't have this behavior, so upgrading from A13 to A15 had this issue pop up. That's why I thought the upgrade process was the issue, since sometimes features are enabled which you don't remember, since you have them enabled for such a long time already.
So maybe I'm biased in this case, but such a small note for a big usage impact seems to be not enough. I would rather display a dialog with the warning (Like usb debugging does). And (I don't know if this is possible), after upgrading the os versions, show a warning, that this feature is enabled and may break things or disable it during the flash process.
Okay, so this is an actual non issue? Even though it only happens after restart? That is somewhat disappointing, but okay, let's update the german translation and hope that no one else has these issues and spends days finding out why it's not working after upgrading
smart pixels is not on by default on clean install
Regarding if it was ON or OFF, why would a reboot change behaviour of the smart pixel feature which was initally working fine?
Of course it is not, but not all do a clean install (Even though it is recommended, but if alot of users say, dirty flash worked without problem which is good, most likely more users will do it). And let's imagine someone enables it after clean install. Reboots the phone 7 days later and suddenly things stopped working. Will those users actually think about smart pixels note in this case?
Issue type
User interface
Device
alioth
crDroid version
crDroid 11
Exact version / Build date
crDroidAndroid-15.0-20241116-alioth-v11.0
Bug description
Enabling the smart pixels features will prevent certain controls from reacting on touch input. They still work when using phsyical keyboard and navigating via arrows and enter. Like enabling usb debugging, security settings and banking apps.
Steps to reproduce
Relevant log (logcat/build log)
Screenshots or videos
https://github.com/user-attachments/assets/65d84e10-e884-43d3-b4ac-09fe7e03a1f2
Solution
No response
Additional context
No response
Acknowledgements