Hey! I cant be the only one who can't stand the ripple effect introduced in Android 5 (though I asked my friends and they don't find this effect that disturbing).
This is what I mean: killem.al/ripple.mp4 - it also shows when you tao on an item in settings or click the back arrow ...
Honestly, the first time I saw it I thought I had enabled something in developer options or accesibility settings by mistake! :D
Actually what makes this really annoying is that the effect can not be disabled globally (not even in a theme)!
So I spent few days diving into Android source code and build process (that's how annoying this effect is to me). In the end it was enough to just find the right "draw" function and replace it with simple "return true" to make it easier I prepared step-by-step instructions how to do this in smali bytecode so there is no need to recompile framework.jar: github.com/luv/android5_noripple
Unfortunatelly it's not enough to just replace something inside framework.jar in android6 anymore and it's actually easier to just recompile the whole OS :) so I also prepared a guide how to recompile Cyanogenmod13 with the patch: github.com/luv/android5_noripple/blob/master/ANDROID6_README.md
DISCLAIMER: I have tested this only on cm12 (and cm13) and it's very much possible messing with framework.jar directly will make your device get stuck at boot (happened to me several times!).
This is what I mean: killem.al/ripple.mp4 - it also shows when you tao on an item in settings or click the back arrow ...
Honestly, the first time I saw it I thought I had enabled something in developer options or accesibility settings by mistake! :D
Actually what makes this really annoying is that the effect can not be disabled globally (not even in a theme)!
So I spent few days diving into Android source code and build process (that's how annoying this effect is to me). In the end it was enough to just find the right "draw" function and replace it with simple "return true" to make it easier I prepared step-by-step instructions how to do this in smali bytecode so there is no need to recompile framework.jar: github.com/luv/android5_noripple
Unfortunatelly it's not enough to just replace something inside framework.jar in android6 anymore and it's actually easier to just recompile the whole OS :) so I also prepared a guide how to recompile Cyanogenmod13 with the patch: github.com/luv/android5_noripple/blob/master/ANDROID6_README.md
DISCLAIMER: I have tested this only on cm12 (and cm13) and it's very much possible messing with framework.jar directly will make your device get stuck at boot (happened to me several times!).
