|
||
|
#25
|
||||
|
||||
|
#27
|
||||
|
||||
|
Probando!!!!
__________________
![]() ![]() ![]() ![]() ![]() ![]()
|
|
#36
|
||||
|
||||
|
SRazon por la que ha quitado el compcache y no recomienda el BFS;
Senior Member Join Date: Jan 2009 Location: Pittsburgh Posts: 1,499 Quote: Originally Posted by acidwashg1 +1 what issues was BFS causing? what issues was compcache causing? 4.2 screams with a linux-swap but I'd like to test it out with BFS+compcache to see what the performance difference is...just hoping for some insider info from cyanogen =) BFS exposes some subtle bugs in the hardware drivers, probably timing related. Random reboots, etc. Very difficult to debug. I want to continue working with BFS cause it rocks, but the issues it creates definitely aren't for a stable build. Compcache and the Android lowmemory killer interact in funny ways. And the only reason I was including it by default was to help the home app stay in memory. And with the tweak i added for 4.2, this is a non issue ![]() __________________ Dice que producen reinicios aleatorios, problemas con los drivers y retardos en las aplicaciones. |