[Galaxy Note 10.1 Android Development] esgie:
Sorry guys for such a scepticism (see below also), but i believe that users shall be aware of the doubts i thought of myself when reading your post, so they can choose wisely..

Another idea that is veeeery discutable.

N8000 has at least 16gb of internal memory (forgot if there are 32gb models too...). 11.6 gb is free to use (checked on my config atm) for both ext4-type data (installed apps, apps savegames and resources, userscripts, etc, ie. linux-like filesystem including permissions, ownership, etc) and sdcard (which in fact is a virtual part of /data partition, lying in /data/media to be exact), mounted in a way which makes it easy to use for a regular average user, with "hidden" linux files permisssions support, so user can manage the files in windows-style, without need of getting familiar with linux specific stuff. Well, it is acting almost just like fat sd card - even, if it is a regular ext4 folder "under the hood".

11.6gb free is a extremely TOO MUCH to consider using link2sd as a helpful thing.

Typical app is 5-10mb, but let's assume it consumes 20mb space, average, which is absolutely pesimistic scenario, even when related to games, (what!? games may be 2gb large you'll say! It's not entirely true, i'll explain it later.)

Without any strange manouvers, you can install about 500 apps in /data. Plus, you can move some of them to /system. Along with built-in ones, it may give you free space for about 900 apps. The system has been extremly laggy in a moment i had 500 apps, so reaching a higher amount is not only not needed for almost every man on the planet (well, who need different 500 apps, hm?) but also not impossible to achieve according to serious lags which occur at some critical level of 450-500 apps.

Why would one want to mess with link2sd, then? N80xx is not a 2gb device, where it really may be helpful. It has 8x more space, enough for as many apps, as android can handle without significant performance loss.

Link2sd was designed for allowing low end devices users to override a very-easy-to-reach space limit. As 11gb free is more than you need and more than android will handle without performance loss, there is no point in increasing the limit even highere. Instead, there are some serious cons:

- ext4 formatted ext sd partitions will NOT be seen by windows in an ext4 formatted part, and as int sd will still remain ext sd formatted, too, you will LOSE some of the space that can be accessed from windows.

- partitioned flash card seems to be not supported at all by some devices, so you may have trouble if want to use the card in your photo cam, for example, even for a moment,

- Ext sd is NEVER faster than internal memory, even class 10.

- Ext sd will cannot be removed/switched to another one on running device, as it will cause system to crash, and will not boot without this and only this ext sd;

- And how can I insert another ext sd (ie with the second part of movie collection)if the first one is required to boot system and run it at all (u can use otg + adapter, but you'll lose class 10 speed benefits)?

And without int2sd, what about games/apps that keeps its data in big (sometimes 2gb...) /Android/obb dir on sdcard? Well, in theory, five such a games and we are out of space for apps. In practice, the sdcard appears as a non-linux oriented virtual filesystem, run in a linux environment. That means, we can use a tool like directory bind, folder mount or terminal's "mount -o bind" to bind dirs from external sd (make them appear as dirs on int sd when physically still lying on ext one), even IF IT IS FORMATTED IN FAT32 or EXFAT. No problem with moving 2gb obbs to external sdcard then, internal mem will still be fully accessible for apk's install data. And if you remove the ext sd, nothing essential will crash, just the games/apps with those obb files, but they will be working after reinserting the card again.

No problems with non-standard sd card, no problems reaching WHOLE card space within windows, no problems in replacing cards when necessary, even on the fly.

Sorry, but idea of using link2sd on n8000 IS ABSOLUTELY A MISTAKE in my opinion.

Tip: use dalvik2cache script to move whole dalvik cache to unused /cache partition, that will givevyou a REAL profit of about 700 mb additional free space on /data. Also, you can symlink some apps to /preload (about 500mb space) if not using OTA...

Tip2: if the 16gb will somehow be too small, other solution i checked myself some time ago, which seemed to be much less disturbing for the extcd card usability, is to create an empty file on the regular fat32/exfat sdcard, convert it to new ext4 filesystem image file with mke2fs and mount the image as loop device. This will let you avoid all the cons related to partitioning sd card (as whole additional ext4 filesystem will be included in an image file lying on ext card as every other file does, but after mounting it you will gain an access to every ext4 specific feature, incl. symlinking new apps when there is no free space left on real /data). Not sure if this has been explained anywhere, as i have tested such a solution on my very own one day... (in short: create empty file (dd command), format it like ext2/ext4 fs (mke2fs -f / mkfs_ext4 -f / etc), bind image too loop device (losetup) and mount (mount -o loop).

Yeah, but it will do good only for low-space ones. For others, it will be a waste of time, and result in reducing the comfort of manipulating the data.

No. It's the best one IN YOUR OPINION. In mine it is not. I like TWRP - good built in file manager with terminal so no need of adb to fix most of issues if i mess my device when far from pc. Can you at least tell us one reason WHY highonandroid is absolutely "the best"?

And how can a "dummy", which has slight knowledge of what it's all about, do it on stock config? If it's a dummy guide, then it shall assume that the user has unrooted device, so maybe he shall start from odin cf root/framaroot instead? Nvm...

The only part of your post related to thread subject, btw.

Well, and why don't you mention for example frandom entropy replacement? THIS is an example of something what gives you a REAL performance boost, without any cons.

Good idea, but:

- how does it refer to the thread (its about boeffla kernel, not about every tweak possible...)

- n8000 does NOT really suffer on sudden death syndrome, like s3, so the risk of erasing efs by device itself isn't too high.

Wrong. IMEI - yup. But wlan's MAC is hidden elsewhere, in a hardware itself to be exact (and modyfying it dynamically from the system level won't harm anything, it's easily reachable feature even in regular Windows environment!) and your carrier depends on the sim card ;) (talking about international n80xx, not the american note 10.1 variations, where it may differ).

No. It will just lose GSM telephony features, as IMEI will be erased. Not sure about 3g connectivity, it will probably won't work too, but everything else WILL work. In fact, n8000 without gsm is almost 100% equal to... n8010 wi-fi model. And i'm sure that n8010 users will not agree that their tablets are as useful, as coffee pads.

I understand that it's not good when you lose your efs. It's indeed a veeeery bad thing, unrecoverable without sammy's service centre etc, but that doesn't explain giving a untrue and misleading info to users!!

Without the knowledge (which seem to has some serious holes...), you will also won't be able to perform the actions that may affect /efs at all, so dunno what's the point in writing this,

The general direction of your ideas seems to be good, but when it comes to important details - you are creating dramatic scenarios basing on skipping thru forums and your guesses, and not on facts or personal experiences. That is my opinion, sorry.

Regards.​