View Single Post
Old 08-23-2019, 09:06 AM   #21
pazos
cosiņeiro
pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.
 
Posts: 1,406
Karma: 2451781
Join Date: Apr 2014
Device: BQ Cervantes 4
Quote:
Originally Posted by Norbi24 View Post

Would it be possible to make this behaviour you have just implemented dependent on the Android version during runtime [...]?
Sure, check this build: https://www.dropbox.com/s/y8ngsvfkrx...test2.apk?dl=0

If you go to the hamburguer tab -> help -> report bugs you should see your FW12 device is using "freescale" and the one on FW10 should say "freescale-legacy"

On FW10 we don't have any control of screen refreshes and this isn't going to change until somebody submits a PR that fixes that.

On FW11 we control all eink refreshes and the behaviour should be the same that you find on latest official nightlies (again, if you find some "slow" behaviour that would need a developer with the device to fix it).
pazos is offline   Reply With Quote