Database Develop

[PRJ] Vibrant Voodo Lag-fix w/OC-Optimized 2.6.29 Kernel - Beta4 9/19/2010

This is Voodoo LagFix beta4 for the Vibrant. It does not include color adjustment just the /data as ext4. This has been tested by many users and is confirmed working, including GPS WiFi BT etc. There is also the performance increase of course as well due to the Voodoo lagfix and the optimized Kernel with OC option.
WARNING BEFORE FLASHING:DISBALE ANY LAGFIX'S YOU MAY ALREADY BE USING BEFORE APPLYING THIS FIX - IS NOT COMPATIBLE WITH THE LATEST LEAK JI2
Samsung has not provided us with the kernel sources that were used in the latest leak (which are different) so until they do we cannot support it.
To enable simply flash the kernel. It will automatically backup your existing /Data partition and create the /data as ext4 and restore so you dont lose your data of course.
To disable simply place a file/folder in the "Voodoo" folder on your SDcard (the internal one) called "disable lagfix" (e.g /sdcard/Voodoo/disable lagfix") no extention just that exact name and reboot. After your phone boots and you check that your /data partition is again RFS you can re-apply any other kernel you were using.
Upon enabling or disabling your phone will sit on the Vibrant screen. This can take 5-10 minutes depending on how much data you have (don't panic). "Linda" the robotic voice should let you know where in the process you are. After its done and your phone boots you should be able to run "mount" in terminal or adb shell and see your data is now EXT4 at
Code:
/dev/block/mmcblk0p4
Disabling by placing the "disable-lagfix" file in the "Voodoo" folder in your sdcard and that simply undoes what the enable did and returns your /data to the RFS setup at its original location.
PLEASE READ
The kernel boots to stock clocks but CAN be OC'd to 1.2Ghz via setupCPU or a user script. If you want to keep the phone OC'd just use setCPU and check apply on boot or use a user script that launches from /system/etc/init.d. If you want to run stock clocks just boot and don't do anything
NOTE This kernel does not need the init.d folder to be present to flash but will parse it if it is there. Also this kernel includes almost all the optimizations my OCv4 kernel so you get the best of both worlds if you want. Voodoo plus OC!
So a simple install routine through recovery would go like this
1.Flash a ROM and root it or flash one that is already ROOTED
2.Download beta4 Voodoo .zip file
3.Reboot into Stock recovery and flash the update.zip made for STOCK recovery.
4.Listen to "Linda" the robot tell you the progress as Voodoo does its thing.
RECOVERY UPDATE
Voodoo Beta4 UPDATE.ZIP
EDIT:Voodoo Beta4 Update zip you can install through STOCK recovery
http://project-voodoo.org/downloads/Voodoo-lagfix-3.0-SGH-T959-update.zip
Clockwork Version by request
www.justanotherdev.slackdev.com/Vibrant-Voodoo_beta4.zip
ODIN UPDATE
Vibrant Voodoo Lag-Fix Beta4
http://project-voodoo.org/downloads/Voodoo-lagfix-3.0-SGH-T959-odin-pda.tar
KNOWN ISSUE:To perform NANDroid backups or restores through clockworkmod recovery please disable the lagfix before either operation otherwise it will not work.
Big Thanks to supercurio for the Voodoo project and for letting me share it with all the Vibrant users out there.

reserved for future use...

I love you.
Going to test in a few. Do you know where we can get the disable-lagfix file? Your OP doesn't include it. =)
EDIT: Nevermind. I should have read more carefully. THANKS AGAIN JAC!

I just flashed the Leaked TMO Kernel with the GPS Fix... can I flash this Lag FIx?

Thanks a lot man! Really appreciate you giving us something to tinker with, been dying to try this out

Will users who already are using 1-click lagfix need to do anything differently in order to use this?

Goog1e Phone said:
I love you.
Going to test in a few. Do you know where we can get the disable-lagfix file? Your OP doesn't include it. =)
Click to expand...
Click to collapse
You just have to name a file "disable-lagfix" and throw it on you sd card. It shouldn't actually have any data in it.

acis said:
Will users who already are using 1-click lagfix need to do anything differently in order to use this?
Click to expand...
Click to collapse
Ya, restoring back to stock or removing the lagfix if its possible. You cannot apply this if you already have a lagfix. Remove it or restore to a previous backup before you were using the lagfix (you made one, right )

just installed on Eugene's r3 rom, and it feels very snappy, can't wait for beta 3, thanks!
Edit: just did a second reboot, and I'm getting an error about a blank internal SD card, and all my data is missing. Any ideas on what I did wrong? I had a lagfix previously installed but had reflashed r3 and didn't redo the fix(not a nandroid just a new flash)
Sent from my SGH-T959 using XDA App

zimphishmonger said:
Ya, restoring back to stock or removing the lagfix if its possible. You cannot apply this if you already have a lagfix. Remove it or restore to a previous backup before you were using the lagfix (you made one, right )
Click to expand...
Click to collapse
Yes. I didn't want to go that far back but meh. 1 click doesn't seem to be working very well tbh.
Appreciate all the hard work that goes in to making the phone actually operate as it should have on day 1. This community is amazing.

It does NOT work on the new leaked rom, fyi :O)
If you are using the leaked rom and you flash this you will need to flash the original rom and check repartition to restore your phone.

Do you need to flash the init.d update before flashing this kernel as with your previous kernels?

Dude this is fast... thank you def. worth the wait so far. the lag is gone! i cant wait to see what you guys come up with next.. its like christmas every few weeks
Eugenes Hybrid r2

Babyface1249 said:
Do you need to flash the init.d update before flashing this kernel as with your previous kernels?
Click to expand...
Click to collapse
No. Just flash the kernal through clockwork. No other steps are needed, unless you already had a lagfix prior.

Goog1e Phone said:
No. Just flash the kernal through clockwork. No other steps are needed, unless you already had a lagfix prior.
Click to expand...
Click to collapse
Giddy up. Flashing now before I get my second replacement vibrant tomorrow lol

HELP!!
i just flashed this through recovery and now my phone wont boot up... just stays at vibrant screen.
when i try to get back to go through "reinstall packages" to get back to nandroid i get stopped. it says...
--install from sdcard...
finding update package...
E:cant mount /dev/block/mmcblk0p1 (or /dev/bloc/mmcblk0)
(device or resouce busy)
E: cant mount SDCARD :update.zip
Installation aborted.
AHHH! what do i do?

Man this thing is FAST! I say we start calling this fix the doodoo lag fix instead because this thing is the SH*T!

itsjusttim said:
HELP!!
i just flashed this through recovery and now my phone wont boot up... just stays at vibrant screen.
when i try to get back to go through "reinstall packages" to get back to nandroid i get stopped. it says...
--install from sdcard...
finding update package...
E:cant mount /dev/block/mmcblk0p1 (or /dev/bloc/mmcblk0)
(device or resouce busy)
E: cant mount SDCARD :update.zip
Installation aborted.
AHHH! what do i do?
Click to expand...
Click to collapse
How long did you wait when it was on the Vibrant screen? The OP says it will usually stay on the VIBRANT screen for 5-10 min before it boots up depending on how data you have.

Goog1e Phone said:
How long did you wait when it was on the Vibrant screen? The OP says it will usually take 5-10 min on the Vibrant screen before it boots up depending on how data you have.
Click to expand...
Click to collapse
waited 20+.. nothing!
is there anything i can do? SH*T, i need this phone for work...

itsjusttim said:
HELP!!
i just flashed this through recovery and now my phone wont boot up... just stays at vibrant screen.
when i try to get back to go through "reinstall packages" to get back to nandroid i get stopped. it says...
--install from sdcard...
finding update package...
E:cant mount /dev/block/mmcblk0p1 (or /dev/bloc/mmcblk0)
(device or resouce busy)
E: cant mount SDCARD :update.zip
Installation aborted.
AHHH! what do i do?
Click to expand...
Click to collapse
Did you install the leaked rom? You will need to go back to the stock rom in ODIN and check the repartition box. Follow my instructions here: http://forum.xda-developers.com/showthread.php?t=780935 but use the original rom

[Q] latest MIUI vs EXT2 partition and A2SD, problem

Hi!
Quick question to everybody. Recently I've installed MIUI 1.5.20 on my MM, before that parted SD into FAT32(7GB, primaty+active)+EXT2(1GB, primary). Now in Settings>System>SD, in section A2SD+ it says "This device does not support A2SD+", is there something more that I should have done to make it work properly?

DrNO[PL] said:
Hi!
Quick question to everybody. Recently I've installed MIUI 1.5.20 on my MM, before that parted SD into FAT32(7GB, primaty+active)+EXT2(1GB, primary). Now in Settings>System>SD, in section A2SD+ it says "This device does not support A2SD+", is there something more that I should have done to make it work properly?
Click to expand...
Click to collapse
Nothing is wrong with it as far as I know. I had the same "issue" as well and my ext2 partition worked fine. I think it might just be because of the ext2 partition not being a native feature to the Milestone? Everything is fine though, don't worry

ok... so how can I check if it works? afaik it should hold apps relocated to SD, so if i go via root explorer to sd-ext folder (mount point), .apks should be there, right?

DrNO[PL] said:
ok... so how can I check if it works? afaik it should hold apps relocated to SD, so if i go via root explorer to sd-ext folder (mount point), .apks should be there, right?
Click to expand...
Click to collapse
Yes. Also you can try looking at /system/app and it might be there as well.

thx a 1M going to try it out... after reflashing with own-modified version from a scratch :]

unfortunately, /sd-ext is still empty.
ok, can any one tell me what are the correct steps, am I missing something? here is what i did:
1. factory reset (org froyo)
2. partitioned SD:
a) FAT32 7GB primary active
b) EXT2 1GB primary
3. rsd lite > g.o.t. 2.2.1 + open recovery 1.46 + or-extfs-update2 + V6supercharge
4. full wipe
5. applied miui 1.5.20 + minor fixes
should it work already(?)

DrNO[PL] said:
unfortunately, /sd-ext is still empty.
ok, can any one tell me what are the correct steps, am I missing something? here is what i did:
1. factory reset (org froyo)
2. partitioned SD:
a) FAT32 7GB primary active
b) EXT2 1GB primary
3. rsd lite > g.o.t. 2.2.1 + open recovery 1.46 + or-extfs-update2 + V6supercharge
4. full wipe
5. applied miui 1.5.20 + minor fixes
should it work already(?)
Click to expand...
Click to collapse
Which MIUI are you using? Did you try rebooting the phone after you restored all your apps?

PROBLEM SOLVED
it's latest MIUI 1.5.20, solution as follows:
1. after installing MIUI, flash via AOR >>THIS script
2. reboot device to the OS and instal (from market) "A2SDGUI"
3. reboot device (just to be sure)
4. njoy
later in mentioned app, you can set dalvik location and/or initiate swap
(@Admins/Mods: for me thread to be closed, thx)
thanks goes to skwara for advice, tkirton for script and skadude66 for trying to help

DrNO[PL] said:
PROBLEM SOLVED
it's latest MIUI 1.5.20, solution as follows:
1. after installing MIUI, flash via AOR >>THIS script
2. reboot device to the OS and instal (from market) "A2SDGUI"
3. reboot device (just to be sure)
4. njoy
later in mentioned app, you can set dalvik location and/or initiate swap
(@Admins/Mods: for me thread to be closed, thx)
thanks goes to skwara for advice, tkirton for script and skadude66 for trying to help
Click to expand...
Click to collapse
Glad it works I'm guessing when you say latest 1.5.20, you're talking about miuiandroid.com's version of MIUI? Because eybee1970's version includes automatic app2ext scripts and shouldn't be that hard to use.

right... you asked about whose release is it, it's not quite original, but based on it. skwara@android.com.pl makes PL version better suited to our local demands, there's no preinstalled app2ext. maybe that's even better, rom is lighter, and more open to your own way of customisation ;P hope someone will find this thread useful if he/she is not using eybee1970's version

Voodoo Lagfix on 2.3.6 (XXJVU)

Hello all,
I just got my Galaxy S (i9000) which was running on stock 2.3.3. It was very laggy... I thought to update its firmware through Kies but there was no update available through it.
So I searched a bit and found the official leaked Value Pack firmware XXJVU. I downloaded it from samfirmwares and flashed it according to this guide.
The same website had a Root guide for this firmware which is actually CF-Root specific for this firmware. I done that too. Phone was very smooth now.. but then when I restored my ~200 apps through Titanium Backup.. it again started to lag.
I had heard about Voodoo lagfix before so thought to try it.. I searched but could not get a proper answer if I can (and how) do it to my current firmware.
I also saw somewhere that CF-Root (kernal) do the same thing as Voodoo do (RFS > Ext4) apart from rooting your device. But when I checked my filesystem.. it was still RFS.
So my question is
1. Can I do the Voodoo lagfix on my device or not? and how?
2. Will it revert my root? If yes then how will I able to root it again?
3. If Voodoo lagfix is not available for this firmware then which other lagfix can I apply? I heard that some lagfixes (don't know about Voodoo) may speed up the device initially but then with installation of more application, the lag comes back.
Is Voodoo lagfix the same?
4. If other lagfixes are not as good (or permanent) as Voodoo lagfix, then which is the latest firmware I can use with Voodoo lagfix?
XXJVS from here?
Sorry, I am new to these things.. and I have searched a lot to figure it out myself without asking here.. but I just could not.
So any help would greatly be appreciated.
EDIT: Sorry, forgot to check the "Question" mark while posting. Any mod please do it for me..

Flash cf root or better still semaphore kernel which is based on chainfires. Use ext4 app to convert rfs to ext4, root will remain, it simply backs up file systems, creates new ext4 file systems and restores. Search for ext4, lots of info available. You will need to free up some space by deleting some standard bloatware
Sent using TCP/IP

gsw5700 said:
Flash cf root or better still semaphore kernel which is based on chainfires. Use ext4 app to convert rfs to ext4, root will remain, it simply backs up file systems, creates new ext4 file systems and restores. Search for ext4, lots of info available. You will need to free up some space by deleting some standard bloatware
Sent using TCP/IP
Click to expand...
Click to collapse
Thanks for your reply.
I already had CF-Root flashed at the time of posting this thread. I tried ext4 CF tool to convert the partitions from RFS to ext4 but the CWM recovery would give error:
"Finding update package...
Opening update package...
E:can't open /sdcard/tmp_ext4_tools.zip (bad)
Installation aborted."
I tried to download the CF ext4 tool from other source and tried but same problem. I tried to copy the "tmp_ext4_tools.zip" generator by CF ext4 manager to external sd instead of internal and then tried manual installation through CWM's "install zip from SD Card" but no avail (same problem).
Then I downloaded and flashed Semaphore kernal v2.5.0 for XXJVU. Root done by CF-Root Kernal was preserved (thank God). Installed the CF-ext4 manager again.. and booted in to CWM. And this time, the convertion process occured without any errors
Now I am on ext4 finally ! (spent the whole day on this)
Don't know why CF-ext4 Manager won't work with CF-Root kernal but with Semaphore.
Anyways, my Quadrant scores with about 200+ apps installed in both scenarios:
On RFS (CF-Root Kernal): 1243
On ext4 (Semaphore): 1892
My phone run better now.. but still not as much as the number shows. Anyways I am happy and can't spend anymore time messing with it.

Hi. I also want to get lag fix and ext>4. how did u do this for xxjvu?

[MOD] EXT4All Continued + Now with TWRP 2.3 Support

The purpose of this thread is to host a location and continue support for a really neat ext4 mod.
IMPORTANT: If you flash the no data limit mod you need to do it after every update or your data, which won't be lost will be hidden by the contents of the data data partition.
I'm going to keep this brief. The original thread was closed so I wanted to have a new location where everyone can find the files. But this is a new thread for Jermaine151's and my EXT4all mod.
Below is the original thread which already has a lot of useful information:
http://forum.xda-developers.com/showthread.php?t=1315372
Here is where you can find most of if not all the EXT4All files:
http://dinc.does-it.net/EXT4_Mods/
Sorry this thread isn't too organized but I threw one together so people could post on it with their comments.
This mod should work on all AOSP ROMs including ICS ROMs and MIUI. It's been confirmed on CM7 and MIUI but I've also tested on CM9. It should also work on all Sense ROMs and does work on every Sense ROM I've tested. Be sure to flash a newer version of the gingertiny kernel if you use a Sense ROM as the kernel version flashed to add ext4 compatibility is out of date.
V2 Mods with TWRP 2.3+ support and proper support for filesystem tweaks for ROMs that are already set to use ext4 found below:
V2 EXT4All Mods
FAQ
Q. How do I know if the ext4 mod(s) worked?
A. The best way is to do the following from terminal:
su
mount | grep /data
It should show a line with /data and ext4 and, if it has the no data limit, also a line with /data/data and ext4. If you're on an ICS/JB ROM it will show ext4 anyways. The best way to tell with the new version of the mod is to see if noauto_da_alloc shows in the results of the above commands.

Hey tiny, thanks for opening this btw. Wasn't sure if I should post here or on ur kernal thread but my girls dinc was having the data limit problem so I wiped cache and dalvic, flashed ext4 no data limit normal dalvic then flashed ur newest kernal (3/11 date). And I have been having the hardest time keeping her phone stable. I've tried every governor sav2, interactivex, ondemand, even sa, tried deadline, sio schedulers, even tried raising the voltages to a post u had on ur kernal thread, page 85 or something (wasn't sure if I should set the min and max of the voltages for the same thing, but that's wat I did). But she still says its very unstable. She's running stock+ 3.01 and she DOES have a cheap ebay battery in her phone, not quite sure how much that plays a role in the problem. She's at work right now so I can't pull any logs, but I know ull probably need a logcat? Or I dunno. If u could gimme directions on anything I should post to assist u. And I'm not overclocking at all for the record. On stock kernal she never had any stability issues, uptime of 200 hours+. But urs is definitely snappier and that damned data limit is the main reason y I even switched her over to begin with. Thanks tiny in advanced for everything u do!!!
Sent from my ADR6400L using xda premium

I'd prefer the kernel thread.
And I'll need a last_kmsg. Just copy /proc/last_kmsg with root explorer or another file explorer and attach it to a post on the kernel thread. Since you most likely eliminated undervolting by using the voltages on page 85 of the kernel thread, then it's possible the battery has an effect. I've heard that poorly made batteries can cause issues that stock batteries don't have so further deviation from stock may have an influence. Either way, I'll look at that log once you get it. Make sure not to battery pull until you can copy that log and try to do it within 24 hours of the last reboot to be safe.

the following thread contains very simple and plain english directions for using this MOD. it helped me, and it was my first time rooting. Thanks also to tiny4579 for posting this new thread.
http://forum.xda-developers.com/showthread.php?t=1488351

Question about this mod, I am running CM7.2, RC2, and onto rc3 soon.
I am having random resets, problems w/ my phone freezing, a mysterious message "sorry, process system is not responding", and other various issues. Could it be that the mod is causing some problems for my phone, or more about something that wasn't cleaned out when i flashed over a nightly?

funkpod said:
Question about this mod, I am running CM7.2, RC2, and onto rc3 soon.
I am having random resets, problems w/ my phone freezing, a mysterious message "sorry, process system is not responding", and other various issues. Could it be that the mod is causing some problems for my phone, or more about something that wasn't cleaned out when i flashed over a nightly?
Click to expand...
Click to collapse
Try a logcat before wiping which i would suggest in the end or else we won't know. I don't think the mod would cause that though.
Also pull /proc/last_kmsg.
Sent from my Galaxy Nexus using Tapatalk 2

I've been running various ICS roms and switched back to Warm rev 58. Upon installing the latest kernel and the Ext4 mod. I am unable to install apps. Any idea what may be causing this. I wasn't sure if it was the rom or not do I did an update with SVN and installed that with the same results. I have a nandroid with just the rom and all the apps I want, but would like to overclock and the stock kernel won't allow. And would also like to be able to install a new app should one arise.
Sent from my HTC Droid Incredible using xda premium

tiny4579 said:
Try a logcat before wiping which i would suggest in the end or else we won't know. I don't think the mod would cause that though.
Also pull /proc/last_kmsg.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks, how do I generate the logcat?
Sent from my Incredible.
Aw yeah.

Ok. It's not the kernel. Installed the most recent and everything is fine. Installed the ext4 with dalvik moved before that and rebooted and apps were missing and it wouldn't let me install new apps and some of my previously installed apps were missing. When I tried to install them it said it was going to replace an existing app and then said app not installed.
Any ideas???
Sent from my HTC Droid Incredible using xda premium

tiny4579 said:
Try a logcat before wiping which i would suggest in the end or else we won't know. I don't think the mod would cause that though.
Also pull /proc/last_kmsg.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
also, i can't see the file /proc/last_kmsg
i see /proc , and i see "kmsg" but i don't see "last_kmsg"
is that the same thing?
and for some reason, the android sdk doesn't work now, that i have uninstalled and reinstalled it...

funkpod said:
also, i can't see the file /proc/last_kmsg
i see /proc , and i see "kmsg" but i don't see "last_kmsg"
is that the same thing?
and for some reason, the android sdk doesn't work now, that i have uninstalled and reinstalled it...
Click to expand...
Click to collapse
Sorry I just dont have time tonight to explain. Maybe tomorrow.
Sent from my Galaxy Nexus using Tapatalk 2

hELLO!
I HAVE A LOGCAT!
and it captures 2 errors.
First, it captures the "sorry, system process not responding" error, and then it captures this weird thing where it restarts. it doesn't go all the way back to the "htc incredible" screen, however, it goes to the cyanogenmod animation, starts up, and THEN goes right back to the cyanogenmod animation, again!
finally, i shut it off, cuz i didn't know how to get the logcat to stop in ddms.
and i have the /proc/last_kmsg... how do i get it to you?
i added a .txt to the end of it so i could upload it, hope that works. is that what you need?

funkpod said:
hELLO!
I HAVE A LOGCAT!
and it captures 2 errors.
First, it captures the "sorry, system process not responding" error, and then it captures this weird thing where it restarts. it doesn't go all the way back to the "htc incredible" screen, however, it goes to the cyanogenmod animation, starts up, and THEN goes right back to the cyanogenmod animation, again!
finally, i shut it off, cuz i didn't know how to get the logcat to stop in ddms.
and i have the /proc/last_kmsg... how do i get it to you?
i added a .txt to the end of it so i could upload it, hope that works. is that what you need?
Click to expand...
Click to collapse
Try fix uids in amon ra recovery. Amon ra should be listed in from manager. I don't think it's the same as fix permissions in cwm which I believe there is file system based. From looking at your logcat there are a lot of unknown permission errors. Let me know. I'm at work so didn't have a lot of time to respond but wanted to check briefly.
Sent from my Galaxy Nexus using Tapatalk 2

tiny4579 said:
Try fix uids in amon ra recovery. Amon ra should be listed in from manager. I don't think it's the same as fix permissions in cwm which I believe there is file system based. From looking at your logcat there are a lot of unknown permission errors. Let me know. I'm at work so didn't have a lot of time to respond but wanted to check briefly.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
hey, thanks for looking at it. what do you do for work, that you are working during a holiday?
so, you think i should try fixing user id's in amon ra recovery.
and it should be listed in ROM manager, right?
Now, here's the question, if i'm going to be trying the new RC3 in CM7, and this time i am going to do a clean install, erasing everything. would i still need to fix permissions?
or maybe i should try flashing over RC2 and then fixing permissions?

funkpod said:
hey, thanks for looking at it. what do you do for work, that you are working during a holiday?
so, you think i should try fixing user id's in amon ra recovery.
and it should be listed in ROM manager, right?
Now, here's the question, if i'm going to be trying the new RC3 in CM7, and this time i am going to do a clean install, erasing everything. would i still need to fix permissions?
or maybe i should try flashing over RC2 and then fixing permissions?
Click to expand...
Click to collapse
Always worth a shot.. If you have the spare time try to flash over and fix permissions as 2nd~to-last thing you do before rebooting, ext mod should be last. Same with if you do a clean wipe to flash RC3 if flash over does not help.
I've personally never had an issue after a clean wipe with permissions, but it would not hurt if you did it anyway. It has been recommended when flash over though as a standard procedure. But only recommended

Sirknifealot said:
Always worth a shot.. If you have the spare time try to flash over and fix permissions as 2nd~to-last thing you do before rebooting, ext mod should be last. Same with if you do a clean wipe to flash RC3 if flash over does not help.
I've personally never had an issue after a clean wipe with permissions, but it would not hurt if you did it anyway. It has been recommended when flash over though as a standard procedure. But only recommended
Click to expand...
Click to collapse
okay, so when flashing rc3, make sure i fix permissions right before the last step, and then flash ext4all mod LAST on the list?

funkpod said:
okay, so when flashing rc3, make sure i fix permissions right before the last step, and then flash ext4all mod LAST on the list?
Click to expand...
Click to collapse
If you're wiping I don't see the point of fix permissions as it will fix it back to what it already probably is. I haven't fixed permissions in a while flashing ROMs and I've been ok. Force closes that I got that made me try fix permissions then weren't fixable with fix permissions anyway.
I would wipe, flash ROM, flash kernel if desired, then mod. Though if it's a sense ROM I would switch the order of kernel and mod flashing. So really you can do: ROM, ext4all mod, kernel after a wipe if you choose to wipe to fix your issue.

hey, flashed over to RC3! so far so good, slowly adding things back! will let everyone know how it goes!

Is there a possibility that all or part of this mod could be persistent over multiple wipings?
My reasoning for this question: I originally flashed the 1.0 normal mod on Nils' BGS. In the OP it says it converts the filesystem to ext4. Many moons later, and now on drk's CM9, terminal still lists cache and data as ext4. I did not, however, flash an ext4 mod on any versions of ICS. I know that when I do a factory reset, even though all is formatted, my sd-ext remains ext4, since I set it up that way for Link2sd. Is it possible that the data and cache blocks have also remained ext4 from the original use of this mod, despite wiping and formatting repeatedly?
...sorry...I was on the phone...

omniatic said:
Is there a possibility that all or part of this mod could be persistent over multiple wipings?
My reasoning for this question: I originally flashed the 1.0 normal mod on Nils' BGS. In the OP it says it converts the filesystem to ext4. Many moons later, and now on drk's CM9, terminal still lists cache and data as ext4. I did not, however, flash an ext4 mod on any versions of ICS. I know that when I do a factory reset, even though all is formatted, my sd-ext remains ext4, since I set it up that way for Link2sd. Is it possible that the data and cache blocks have also remained ext4 from the original use of this mod, despite wiping and formatting repeatedly?
...sorry...I was on the phone...
Click to expand...
Click to collapse
No, if you actually format the device like when the system runs the format command the filesystem will be ext4. However in your example of CM9 the ramdisk mounts data and cache as ext4. This will actually have a minor improvement over ext3. It'd still be an ext3 filesystem but loaded as ext4 so there's minimal performance gains.
In reality any time you flash a ROM or a boot.img type kernel (not any of mine) you will use the ramdisk of the ROM and reverse part of the effects. But since ROMs like CM9 and newer CM7 versions mount as ext4 you'll still see data and cache showing as ext4. Make sense? I never really did explain it properly before I think.

[Q] Minicm7 and a couple of questions

Hi guys I decided to flash a new rom minicm7 and flash its latest kernel naa 13.
A couple of problems:
MY rom is minicm7 with naa latest version 13.
1.when I open the menu to access all my applications the scrolling feels laggy and if I were to scroll in settings file manager or anything else it's smooth any reason why?
2.Secondly which kernel suits you better for this rom (minicm7): Alfs? or NAa?
(I don't want comments like 'see for yourself' this question is based on your OWN invaluable experience)
3. for alfs 8acm7 i'm considering on seeing if it will workout for my device or not (minicm7). Before I do that:
Do I also need to flash chargemon on top of that? and does the flashing of chargemon straight after you flash any version of alfs kernel (except for the ones that already have it attached) apply to any rom regardless as well?
If so which chargemon do I flash? the v2 with the 17k downloads? (sorry im derping out)
4.Do I also need to flash anything else for naa just like how there was an extra file to flash for alfs?
5. I also installed tweaks 3 tweaks such as adre boost, odex, and e15 optimizer. Will these tweaks vanish if I flash a new rom + kernel?
6. Do you keep ANYTHING if you flash a new rom or kernel?
7. Do you lose anything of any sort if you flash a kernel?
8. How do you guys get such high scores in benchmark tests?
I have the same thing as a lot of people do but they seem to get 200 or even 300 higher. Could it because my sd card is filled with anime and music leaving only 5 - 6 gigs / 16gigs ?
I usually went by the rule of flashing 2.1.1.0 and rerooting my device and doing everything again just to stay safe
I don't know if these questions might be derp or not but I don't care please answer by putting a number first I really need answers.
Thank you once again

From my experience and opinion: (Please correct me if I'm wrong...)
1. IDK... BTW Is your MiniCM7 2.2.1 or Nightlies? Have your tried rebooting once or twice? Because mine was smooth...
2. nAa because it is more stable. They also said that the performance is faster with Alfs but I don't like FPS caps problem (Higher chance to get screen cut otherwise laggy scrolling visually)...
3. IDK... I haven't tested it...
4. No...
5. Most likely because you'll need to full wipe before installing a ROM (not kernel)...
6. Anything unless it requires to full wipe...
7. Yes... I think it overwrites some system apps and even some user apps and user data might be corrupted... (maybe when doing cross flashing of ROMs)
8. Overclock (The most effective and dangerous way), Supercharger (I think AutoKiller Memory Optimizer is the same), Swap (different partition), Adrenalines, Odex and et cetera...

Lily48 said:
From my experience and opinion: (Please correct me if I'm wrong...)
1. IDK... BTW Is your MiniCM7 2.2.1 or Nightlies? Have your tried rebooting once or twice? Because mine was smooth...
2. nAa because it is more stable. They also said that the performance is faster with Alfs but I don't like FPS caps problem (Higher chance to get screen cut otherwise laggy scrolling visually)...
3. IDK... I haven't tested it...
4. No...
5. Most likely because you'll need to full wipe before installing a ROM (not kernel)...
6. Anything unless it requires to full wipe...
7. Yes... I think it overwrites some system apps and even some user apps and user data might be corrupted... (maybe when doing cross flashing of ROMs)
8. Overclock (The most effective and dangerous way), Supercharger (I think AutoKiller Memory Optimizer is the same), Swap (different partition), Adrenalines, Odex and et cetera...
Click to expand...
Click to collapse
Hi there thanks a lot for your help and I am using minicm 2.2.1. And how do you swap different partion?

Ftwisawesome said:
Hi there thanks a lot for your help and I am using minicm 2.2.1. And how do you swap different partion?
Click to expand...
Click to collapse
You can use the recovery for creating SWAP but with Ext though...
[Ext is another partition for user apps and it's advantage is that you can use the apps on the partition while the sd is mounted on PC]
1. Back up everything on SD because it will be formatted...
2. Enter Recovery -> advanced -> Partition SD Card
3. Choose you Ext size -> Choose 128M Swap size... they said 256M is not recommended...
4. Reboot -> Terminal -> su (if required) -> free -> DONE!
If you want to use Ext, you may install Link2SD -> Choose Ext4 -> Reboot -> Launch Link2SD -> Start linking... DONE!... (Warning: sometimes it breaks app when the annoying error comes (I forgot))... I think you can also use the CyanogenMOD -> Performance -> A2SD (ext) but IDK how to use it...
See also Tips & Tricks To Increase Our Phone's Speed

Wow thanks!
So do I need to do this before I swap?
because when I dled swapper and swapped I ran free it was working fine but I felt no ingame improvment in anyway.
SO all I have to do is the above then swap and im good to go?

Ftwisawesome said:
Wow thanks!
So do I need to do this before I swap?
because when I dled swapper and swapped I ran free it was working fine but I felt no ingame improvment in anyway.
SO all I have to do is the above then swap and im good to go?
Click to expand...
Click to collapse
Swap is already done after partitioning... it's ready after reboot... the terminal is only used to check if it is mounted...
Only the Ext needs setup...
PS: I tried GingerDX and all Dalvik-Cache files went to the Ext without any setup ... Swapper makes mounting SD to PC very SLOW... SWAP Partition doesn't work with MiniCM9 3.0.2 but working on IScreamDX v004...

Ftwisawesome, learn to use the search function, most answers to your questions can be found when you show a little initiative.