Results 1 to 5 of 5
  1.    #1  
    Couple of questions before I go through the process:

    -Is there a way to modify the cryptofs size so that I don't have to do it later on (the one related to the application database getting full issue)? I see options for swap, ext3, etc. but not for that specifically.
    -I see a script for a vanilla AT&T 2.2.3 and a wr AT&T 2.2.4 (the former from what I understand removes the AT&T junk and the latter makes it emulate a WR model). My question is, is there a functional difference between the two (for example, does the WR version open up manual network selection while the vanilla version doesn't)?
    -Anything else that's recommended to do while I'm going through the process (for example, enlarging any other partitions, modifying other system files, etc.)?
    -Any Pre3 owners recommend staying with 2.2.3 vs. 2.2.4?
  2. #2  
    Quote Originally Posted by bassman97 View Post
    -Is there a way to modify the cryptofs size so that I don't have to do it later on (the one related to the application database getting full issue)? I see options for swap, ext3, etc. but not for that specifically.
    CryptoFs is a dynamic overlay filesystem that uses /media/internal. It uses all available space on the media partition and has nothing to do with the application database.
  3.    #3  
    Quote Originally Posted by GMMan View Post
    CryptoFs is a dynamic overlay filesystem that uses /media/internal. It uses all available space on the media partition and has nothing to do with the application database.
    Maybe not the best wording, but store-mojodb/store-cryptodb is set at a size too small as we all know so it'd be nice to set the doc to make it larger from the get go, vs. doing it after the fact. In case my wording still blows, I'm refering to this fix:

    Workaround for Application Database is Full error | webOS Nation
  4. #4  
    Ahh, OK, you're talking about about the database, not applications store.
  5.    #5  
    Bump. Anyone?

Posting Permissions