Maybe better CM kernel support.And what does that mean?
probably better custom roms with better battery life, performance ect,And what does that mean?
To see if any kernel has the Emmc brickbug or not, simply need to open the kernel image and see if MMC_CAP_ERASE script its enabled or not. There's dont need to search in kernel sourcesNow is it possible to know if there is brickbug?
Unpack kernel.tar.gz and look into: drivers > mmc > host > sdhci.cNow is it possible to know if there is brickbug?
But Entroy512 says this:Unpack kernel.tar.gz and look into: drivers > mmc > host > sdhci.c
This is where MMC_CAP_ERASE is... and look into it!
Easy![]()
As mentioned in other threads on the eMMC "brickbug", Samsung's official patch for this issue is NOT to remove MMC_CAP_ERASE, but to only disable secure erase in the kernel.
What Samsung did was to implement this fix:But Entroy512 says this:
http://forum.xda-developers.com/showthread.php?t=1953932
I don't understand.
#define CID_MANFID_SAMSUNG 0x15
static const struct mmc_fixup blk_fixups[] =
{
MMC_FIXUP("SEM02G", 0x2, 0x100, add_quirk, MMC_QUIRK_INAND_CMD38),
MMC_FIXUP("SEM04G", 0x2, 0x100, add_quirk, MMC_QUIRK_INAND_CMD38),
MMC_FIXUP("SEM08G", 0x2, 0x100, add_quirk, MMC_QUIRK_INAND_CMD38),
MMC_FIXUP("SEM16G", 0x2, 0x100, add_quirk, MMC_QUIRK_INAND_CMD38),
MMC_FIXUP("SEM32G", 0x2, 0x100, add_quirk, MMC_QUIRK_INAND_CMD38),
/*
* Some MMC cards experience performance degradation with CMD23
* instead of CMD12-bounded multiblock transfers. For now we'll
* black list what's bad...
* - Certain Toshiba cards.
*
* N.B. This doesn't affect SD cards.
*/
MMC_FIXUP("MMC08G", 0x11, CID_OEMID_ANY, add_quirk_mmc,
MMC_QUIRK_BLK_NO_CMD23),
MMC_FIXUP("MMC16G", 0x11, CID_OEMID_ANY, add_quirk_mmc,
MMC_QUIRK_BLK_NO_CMD23),
MMC_FIXUP("MMC32G", 0x11, CID_OEMID_ANY, add_quirk_mmc,
MMC_QUIRK_BLK_NO_CMD23),
/*
* Some issue about secure erase/secure trim for Samsung MoviNAND
*/
MMC_FIXUP("M8G2FA", CID_MANFID_SAMSUNG, CID_OEMID_ANY, add_quirk_mmc,
MMC_QUIRK_MOVINAND_SECURE),
MMC_FIXUP("MAG4FA", CID_MANFID_SAMSUNG, CID_OEMID_ANY, add_quirk_mmc,
MMC_QUIRK_MOVINAND_SECURE),
MMC_FIXUP("MBG8FA", CID_MANFID_SAMSUNG, CID_OEMID_ANY, add_quirk_mmc,
MMC_QUIRK_MOVINAND_SECURE),
MMC_FIXUP("MCGAFA", CID_MANFID_SAMSUNG, CID_OEMID_ANY, add_quirk_mmc,
MMC_QUIRK_MOVINAND_SECURE),
MMC_FIXUP("VAL00M", CID_MANFID_SAMSUNG, CID_OEMID_ANY, add_quirk_mmc,
MMC_QUIRK_MOVINAND_SECURE),
MMC_FIXUP("VYL00M", CID_MANFID_SAMSUNG, CID_OEMID_ANY, add_quirk_mmc,
MMC_QUIRK_MOVINAND_SECURE),
MMC_FIXUP("KYL00M", CID_MANFID_SAMSUNG, CID_OEMID_ANY, add_quirk_mmc,
MMC_QUIRK_MOVINAND_SECURE),
MMC_FIXUP("VZL00M", CID_MANFID_SAMSUNG, CID_OEMID_ANY, add_quirk_mmc,
MMC_QUIRK_MOVINAND_SECURE),
END_FIXUP
};
Most likely fixes and addictions. No changelog was provided from Samsung so no idea!What is the difference between this release and GT-N7000_HK_JB_Opensource_Update2.zip that was out a while ago?
So, we are sure?.....
This fix according to Samsung fixes the brickbug... but neither me and Entropy512 trust Samsung on this one...![]()
Mate the info came from messaging with Entropy who told me to look into the commits and that commit was made by Samsung, so if you trust Samsung yes...So, we are sure?
Ok. So now we have to tryMate the info came from messaging with Entropy who told me to look into the commits and that commit was made by Samsung, so if you trust Samsung yes...
I did already post some mirrors for it here:blog.gsmarena.com/samsung-releases-galaxy-note-jelly-bean-source-code/
Article has link to source of info and link to source code download (have not checked this myself though, don't know what to do with it)
Desperately need a kernel with CPU GPU overlocking, more governors options, more RAM!I am not sure battery life can get any better, its freaking amazing