• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Biting the rooting bullet, feasibility please anyone?

Thanks for the reply Abdur. I’m not sure though, that the link you sent me to was what I was posting about? Your link is talking about an application called app2sd, not LINK2SD – which appears to be a completely different animal. The documentation on link2sd says that two partitions of FAT32 are best for the task. From what I read, LINKtosd simply creates ‘symbolic links’ to the Sdcard, so the OS still believes the app IS installed in internal memory.
 
I would suggest using Apps2SD primarily due to the fact that on this forum a lot of people seem to have experience with it, and can help troubleshoot, if you have any problems. On the other hand I havent even heard about Links2SD, will read more about it when I get the time.
For now, I suggest Apps2SD :)
 
Yes, I have looked at apps2sd, but it has some drawbacks that I don’t like. For one, it turns the whole app directory into a shortcut instead of just the apps themselves, so it is an ‘all or nothing approach.’ I want to leave some apps just as they are in the ‘app folder’ in the internal memory; and choose specifically which ones I want to relocate to the SDcard.
 
1) partition must be 1 fat32 followed by 1 ext partition. Link2SD in market suggests you can use minitool to.partition your card. This is a no no

2) the system apps themselves cannot be moved and are not memory offenders in any way. That said their updates are. These are not on system, these are on data and any data app can be moved
 
togbabe said:
Thanks for the reply SUroot. I don't quite get what you mean here. When you say 'system apps,’ do you mean the ones I’ve listed that came with the phone like Facebook, Twitter and Peep, Maps and such, or the actual system programs that make up the running services?
Click to expand...

All apps that are in the /system/app directory which makes up both of what you listed above. But the "actual system programs" will not be updated by the market.

togbabe said:
By this, did you mean that because the original app – before updating – is stored in the ‘flash-able’ part of memory, they are not using up any of the ‘user memory?’ Bit confused here.
Click to expand...

Exactly what I mean, except once rooted, all NAND memory partitions are flashable. Before rooting /system partition is totally locked.

togbabe said:
Would I be able to format the second partition in FAT32 as well since the Desire appears to understand this format?
Click to expand...

No. It must be EXT. The reason for this is that the internal partitions of the desire are EXT so the apks need to be on EXT File system. The ONLY thing that is FAT32 is the user storage area of the SD card. Everything else on the phone is EXT. If it IS possible, its NOT a good idea.

Both the FAT32 and the EXT will have to be primary. You really should use gparted to do this properly.
 
SUroot, if I’m reading the forums correctly, rooting and flashing to Gingerbread would negate the need to partition for things like link2sd or apps2sd+ etc. because Gingerbread allows you to save and store apps to the SD card FAT32 by default?
 
its a different method that Froyo also has. Its the standard implementation from google since 2.2. Obviously its no way near as good as using an ext partition which is why many people still root.

Although I use the standard implementation as I have much larger internal memory, so no need to use an ext partition at all
 
I suspect if you have low memory issues on froyo, you will also have low memory issues on GB. Also, to get a ROM with the latest sense bits, you will need an ext3 or ext4 partition. Check out the requirements on the ROMs on XDA.
 
You must log in or register to reply here.
Back
Top Bottom