Alain
- Forum-Beiträge: 11.646
14.06.2013, 15:36:37 via App
14.06.2013 15:36:37 via App
New beta version with preliminary and completely untested atmel implementation of s2w/dt2w: http://downloads.codefi.re/mustaavalkosta/tests/kernel-20130614-s2wdt2w-beta2.zip
Suspend/resume handling is based on @thachtunganh's earlier implementation but because it's completely untested atmel phones may kill kittens and cause thermonuclear wars.
Refer to my last beta post for sysfs entries although this one has also everything turned on by default.
It'd be appreciated if someone can check whether normal s2w without stroke enabled works for atmel screens. I've no way of testing it myself and if no one else will, it'll end up in the nightlies as broken. You can disable stroke2wake with filemanagers or in terminal app:
For synaptics it has pretty nasty hack for sleep state problem. It works ok for s2w because it's not time-sensitive but with dt2w you may encounter on-off event after second try when the first one failed. I spotted a better i2c_transfer() handling in atmel driver and will try to implement something similar to synaptics driver hoping that it will fix the problem which originates from bad error handling for i2c_transfer().
As a bonus, it's also compiled with gcc 4.8 now thanks to @sparksco's pull request to change memory allocator from SLUB to SLAB because the first one seems to hate gcc 4.8.
Suspend/resume handling is based on @thachtunganh's earlier implementation but because it's completely untested atmel phones may kill kittens and cause thermonuclear wars.
Refer to my last beta post for sysfs entries although this one has also everything turned on by default.
It'd be appreciated if someone can check whether normal s2w without stroke enabled works for atmel screens. I've no way of testing it myself and if no one else will, it'll end up in the nightlies as broken. You can disable stroke2wake with filemanagers or in terminal app:
For synaptics it has pretty nasty hack for sleep state problem. It works ok for s2w because it's not time-sensitive but with dt2w you may encounter on-off event after second try when the first one failed. I spotted a better i2c_transfer() handling in atmel driver and will try to implement something similar to synaptics driver hoping that it will fix the problem which originates from bad error handling for i2c_transfer().
As a bonus, it's also compiled with gcc 4.8 now thanks to @sparksco's pull request to change memory allocator from SLUB to SLAB because the first one seems to hate gcc 4.8.
Zitat von Mustavaalkosta.......
Die Warheit schmeckt gut wenn man den Bauch voller Lügen hat! ~Muhammad Ali~
?
* 
liegt wohl am alter des Telefons
