like a tree down by the water baby i shall not mov
Our system already resides on the speedier NAND, always has on the Vibrant TMK, but this is also what ultimately limits the size in the symlinked /datadata setup we use for apps, as that is also crammed into the smaller but speedier NAND chip. /datadata mounting is much faster, as everyone who ran the early ICS build that used the larger but slower /data/data partition, which is on the slower of the chips in the Vibrant.Love this rom, super snappy it is, and GPS at least works works great after reboot. I will make a donation as soon as get around to adding some doe to my Paypal account.
I saw a post a few pages back talking about system speed and wanted to ask of you think this being ported to the vibrant would help, it's pretty nice on my HD2
Sent from my SGH-T959 using Tapatalk 2
This is also a serious limitation on the Vibrant when talking JB. The system partition in JB requires a lot more space that ICS did, and that basically leaves no space on the speedier chip for /datadata mounting. This is why /datadata was dropped by some devs, others are getting creative: repointing certain partitions, putting the cache on the speedier sd, and even mounting the /data partition to the internal SD. which is faster than the slower of the NAND chips in the Vibrant, though still has space limitations and you could end up with low space warnings. I'm not exactly sure how DerTeufel set the mounting points in HB to still use /datadata effectively, haven't investigated that yet in depth, but I've been back on ICS for a while now.
I've had convos with a few others, and I've got serious speculation that the Vibrant may be near or at EOL with ICS. The way this device is designed, it may not handle JB very well ever, if at all. Seems if you go one way, you face lag, go another way, there are app space limitations. This by no way means that I'm not going to keep playing with JB for the Vibrant, but comparing it to the way my N7 runs JB, its a night and day difference.