@Blechd0se: Could you probably give some more infos about this approach? Particulary I have the following questions:
I can not confirm this bug, a ROM compiled today works without the problems you mentioned.
1.) No. If no swap alike device is attached then swappiness should have zero impact on anything. In return, if something is attached than it has an influence.
2.) In short; it depends. It could have a negative influence if the value is set to high, but this also happens if the the value is too low.
Something like 40000 kbytes (= 40 mb) sounds a bit to aggressive for me, normally we should set it to something like 5-10% of the total memory (according
to the redhat source i linked, there are also explanations for other vm settings).
When we prepared the kernel for kitkat we also integrated a similar feature which did exactly the same (turned out it was a bit buggy and needed to be reverted).
If some of you find the sweet spot we are willingly to integrate that, because in the end thats exactly what i made aero control for.
For users to share their "best" configuration to help us improving the device experience for everyone
Just won't happen to soon from my side, since exams are incoming...
I'm finding issues with Snapchat. I don't think it's to do with the app because plenty of third party camera apps work but this is the only one I'm having issues with. It must be something to do with the rom. I have a MB525 with a bayer camera module.
could it be to do with the texturing? Snapchat has a lot of different effects and features in the app.
attached is a screenshot of whats going on.
|baseband switcher, led, quarx for world emperor, quarx is still a god|
|Thread Tools||Search this Thread|