Entropy512 wrote that EMMC_CAP_ERASE more needs to be done, Samsung fixed the problem bricks when doing large data wipe
Link?
As far as I know, Entropy512 never said that. The debate was never and will not be ironed out as Samsung do not publish source for their chips. Entropy512 said probably it is enough, but he was nervous about it and would never allow it. The speed / performance is very theorical and under very special circumstances all explained by Entropy and other members. All this was debated months ago and nothing changed since that
Anyway, that's not the question. I was fair enough, but I ask you a last time:
There are clear rules in xda about developers:
- If you use someone else work, you need to ask for permission. You did not, but I say ok
- Your custom kernels I do not mind
- This N7000_JB_LT4_PhilZ_CWM_kernel.tar is not mine. So, do not tell people there is a Philz-cwm6 release of LT4 when they ask. Furthermore, you do not patch the kernel and you do not even mention it. Many do like safety, mainly for N7000 community. I always put detailed logs
- If you want to keep your post or a thread: Sate clearly from where you leach the ramdisk, what you do change and that you are the repacker/releaser
I cannot be more clear, else there are moderators in xda to decide
