Ver Mensaje Individual
  #1  
Viejo 20/10/10, 21:45:11
Array

[xs_avatar]
vinclar vinclar no está en línea
Colaborador
· Votos compra/venta: (46)
 
Fecha de registro: sep 2010
Localización: En mi mundo
Mensajes: 1,894
Modelo de smartphone: S7 edge
Tu operador: Amena
[KERNEL][101022] Universal lagfix [EXT4,JFS] and tweak kernel [BLN] {0.3}

Ir al link original: http://forum.xda-developers.com/showthread.php?t=814228





Cambios en la 0.3 (Changelog Version 0.3)
- before the lagfix gets applied there are now multiple options to chose from:
-- backup+restore (the original way)
-- backup, but don't restore (this eventualy results in a factory reset)
-- no backup (this also results in a factory reset)
-- go to recovery mode (to debug)
-- erase config file (to get back to the old options)
- the screen glitch in the first screen is now gone (because the kernel got smaller)
- jfsutils are ported to bionic (takes less space)
- there is a new option that will do the same restore permissions run, as the init script does
- I also added a few fixes to the CWM fix_permissions script, although I don't tested them yet (so it might brick the phone)
- Added two more rooting option:
-- the old one simply copyes busybox, superuser and su to the phone and adds symlinks to busybox
-- the new ones will also remove some old toolbox commands, so if you use the shell a lot, they won't interfere. The first mode only removes the base utils, like ls,mkdir,rm or ln
-- the second mode removes every toolbox command that has an equivalent busybox command (like mount, lsmod, rmmod, etc.)

Remarks
It seems that formatting dbdata as rfs only works, if you use the 512 PIT file (more exacty it only works if you have used the 512 PIT file the last time you've ticked re-partition in odin). This is probably due to the fact thet the 512 and 803 pit files reserve different space for the dbdata and for the system partition (the 803 pit file reserves 40 units less for the dbdata than the 512 pit file)


Cambios en la 0.2(Changelog Version 0.2)
- efs is not backed up automatically during lagfixing (but it's still backed up during ordinary backups)
- added jfs support and some more lagfix schemes using jfs
- added backlightnotification support, with the option to turn it on and off
- added startup script tweaks support, with options to turn them on and off
- removed ext2 support for the base mounts (might be put back into later)
- bind now only binds /data/data (should use less space)
- some minor bugfixes relating

Remarks
- If Updating from 0.1 to 0.2: If binds were turned on you have to turn them off before updating. After the update has finished you can turn them back on if desired.

Known bugs
After the lagfix conversion is done the phone reboots and the lagfix conversion starts over again
This means that the conversion took place, but the result is not the same as was desired. You should reboot into recovery mode and remove the config file.

After rebooting I have a lot of FC's - After switching lagfix schemes I have a lot of FC's
This is probably because of a database corruption. Try loading an earllier backup.

Can't download anything from market
Some configurations might have this problem, I'm still trying to find out why this happens.

Can't download some apps, like angry birds from the market
Retry, it should work after a while. If it still fails remove the external sd.

Shutdown fails on some configurations
Until I find a way to hook onto the shutdown script this might happen on more complex configurations (like the NO-RFS overkill)

Can't get back to rfs on /dbdata
Reverting the lagfix on /dbdata only works if you used the 512 pit file the last time you checked re-partition in odin.


Un poco de translate de google
(Click para mostrar/ocultar)

Última edición por vinclar Día 11/04/11 a las 23:00:39. Razón: Actualizar hilo
Gracias de parte de: