[Android Apps and Games] tobbbie:
Memory Information not correctly re-calculated after linking

I noticed that the information on storage space via "Menu -> Storage Info" is not correctly updated after moving/linking an app from native app2sd storage to sd via link2sd. This is (I guess) a 2-step process of first moving back to internal memory and then moving out to second sd parition and linking to there via links.

The calculated size shown seems to be that of only step-1 passed and step-2 ignored. Restarting link2sd will show the correct size - so not a big thing. I was just puzzled to notice that the expected effect on storage space could not be seen after I batch-moved a few apps this way.

In this context I could think of a "guide" or an "assistant" function in link2sd to direct users to the best potential move/link candidates. As of now you need to be well aware how the file distribution in Android is done, which parts can be moved/linked (.dex + .apk + libs) and which big overall applications may not really have a big effect if moved (e.g. games hogging their \data directory).

Effectively this would be simply sequencing "show on internal ", then sort by ".dex + .apk + lib" size, then call the "Multi-Select" and "Select all" possibly enhanced by a preview-calculation of the saved space from moving the selected elements. Not that I need that, but there are many who will profit from this potentially. If you think of an enhanced "paid" version - this feature could help you "sell" it.

For some apps it may even effectively be better not to use link2sd as the app is not aware of its changed location or at least is sure that it is not utilizing the native apps2sd method. I noticed some apps are storing their data depending on where they are installed (internal or apps2sd). So for those apps moving out their own data parts is more beneficial for the \data partition than saving the bytes by letting link2SD move the .dex.apk+lib and leave \data internal. Not sure anymore where I noticed that so it may be rare cases anyway.

I would post this in a separate item, but the board auto-links them anyway so here:

There is something I noticed in practice when updating several apps from Google play store. I like to review which changes an application does before then manually starting the update for each of them. Now it seems that with several such updates in a row, that link2SD is just hitting in the middle of the next transfer (looking as if the update is stalled) when moving/relinking the previous. Mind that almost all my apps are moved/linked via link2sd and updates (at least for me) come in daily...

Instead of auto-moving updated apps, could you supply an option to manually defer such moves (for a limited time)? Alternatively you could also supply one more option to the "Autolink" area: "Auto link updates" - potentially with a configurable delay for that.

As I don't know the logic for you to trigger that Auto-link of updated apps, could you actually reset the timer triggering this Autolink while installations are running?

Sorry for the long post :)

---------- Post added at 10:21 PM ---------- Previous post was at 10:09 PM ----------

I noticed the same with my brief excursion on CM10. I guess that moving the app via system app2sd should work fine, but doing anything with link2sd will ruin stuff. It seems that something remains after link2sd tried working on the app.

Another reason why I dropped CM10 for now - I really depend on link2sd :)

---------- Post added at 10:24 PM ---------- Previous post was at 10:21 PM ----------

This may be linked to the different place where the system files have their dalvik-cache. On my CM10 from the FXP (Free Xperia Project) the dalvik-cache for system apps was not on \data\dalvik-cache but it was on \cache\dalvik-cache.

See my recent post about this.

---------- Post added at 10:26 PM ---------- Previous post was at 10:24 PM ----------

Are you running JB (e.g. CM10)?