Apps2sd on ext partition with gpa15

[diesburg]

Ok, I got it to mount ext4 partition and recognize stuff right........theres another module... it was called *bd2.ko , cant remember the exact name, look in modules folder and you will see it.... anyways.... ext4 wont load because that module has to be loaded first for ext4 module to load right.... so load that module first, then ext4 module with insmod and you got your ext4 stuff mounted correctly.... with root explorer make an sd-ext folder where it usually is because that folder doesnt exist in petes gpa15 like it does other roms....then you can mount, i noticed in gpa15, you have to type the "-rw -t ext4" options in with the mount command or it wont work right and in other roms it works without adding those extra options.......so after all that, download "freespace" app from the market.... and your ext4 partition is there and shows empty/free/total space correctly and you can browse the partition too..... and i found a nifty app called "simple2ext" in the market....got a nice little GUI and from what I can see it does what dtapps2sd does but easier, quicker to install and with a GUI and has options to have certain things on and off ext partition.....but heres where the problem comes in.... with that app, you check the boxes for which locations you want to move to sd-ext, then reboot, while rebooting and taking extra time to do so it moves your apps where you asked them to be moved......BUT, when android reboots, those module loading commands we did, making the sd-ext folder and mounting the partition... you have to do that all over again and because of that, **** didnt get mounted correctly on boot so nothing got moved the way it should..... i barely touched the surface on init.d and init.rc ..... my quick thoughts are init.d would be the way to get everything loaded right on bootup.... but no init.d folder in petes gpa15.... if i understood correctly though init.rc is where you need to tell the system to load up scripts from init.d.... so maybe it can be done...... oh yea in case anyone tried this, after all the steps, if you use simple2ext app, if boxes are greyed out in the app where you cant change anything, you probably did something wrong... i used fresh install of the rom with only needed apps for doing all this stuff and made sure those apps WERE ON internal storage so i didnt run into issues later.... and the same works with chevys kernel but for the modules, mbcache.ko needs to be loaded before ext2.ko and of course an ext2 formatted partition instead of ext4......im really tired and probably wont get much more figured out until i sleep but I believe I got it all figured out, just need to get **** done automatically on boot now.... and if anyone is wondering, I accidentally figured out that the other module had to be loaded up before ext4 module would load correctly.... i just went to the modules directory and tried starting other modules before starting ext4 because chevys kernel post instructed to load something before ext2 module would load..... and if i didnt mention it before .... i think it was modprobe..... it points to a wrong directory and needs fixed.... i did all this without modprobe but I believe modprobe wouldve been nifty to use......and another small side thing, most apps2sd instructions and scripts i found say to mount /dev/block/mmcblk1p2.... no, with our phone, its /mmcblk0p2 ...... anyways, any advice on init.d and init.rc solutions, let me know, i barely touched the surface so me alone, it will probably take days of tinkering to get it all right.....if ever...lol

[diesburg]

If anyone can help me on this it would be great, I think this is a pretty simple question for whoever has the knowledge. I used Simply Stunning GB 5.4 to see how it works when apps2sd works the correct way. In checvy's SS rom, he includes chevy tools which has scripts and other nifty stuff. In chevy tools, you can go to network/file systems, and in there, just check the filesystem you want the modules loaded for on startup. In my case ext3. And by the way, chevy's kernel DOES support ext4 also, I just choose no to ext4 because you cant back ext4 up with nandroid. Anyways, I checked the ext3 option, and rebooted to verify ext3 modules are loaded on each boot and they are. So i checked the file "04modules" in init.d to see if it added it there. It didn't add it there, still the only module being called for loading there is ipv6 . It's adding it somewhere else, that I think is why I can't get ext4 to autoload with petes rom because I'm asking for ext4 modules to be loaded in the wrong place. Anyone know where/what in chevy's rom when you use that script in his tools that it is putting/changing to make ext2/3/4 load? If anyone does, that is probably the same thing I need to change in gpa15. If I can just get the module to autoload, I'm sure it would be fully working for me. For the mount, the app links2sd or whatever you use should put that in for you on boot or at least it did for me on SS 5.4 rom so I didn't have to worry about getting it to automount. But yea, to sum up, in chevy's SS rom, it is not changing the file 04modules in init.d to autoload ext modules, it's changing something somewhere else and I need to know where to change that on petes rom.

Just a quick idea... I've never really used logcat, just for a few minutes one day.... but if I ran logcat while using chevy tools to make the ext module change, would it say in logcat what was changed?