yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S (4G Model)] invario:
Then someone needs to explain why everything is working for me now after I removed the lagfix. It most definitely has something to do with the lagfix implementation. I was very methodical about what I did and changed only one variable at a time.

1) Whitehawk Odin stock KD1 deodexed with Bali 3.1UV, your init.d ext4 lagfix tweak, accurate battery mod, system/data/cache all ext4

2) Tried fixing permissions and clearing Dalvik, just in case. Still can't record properly.

3) Removed your init.d script and reboot. Still can't record properly

4) Updated to Bali 3.2UV. Still can't record properly.

5) CWM nandroid backup, RFS formatted, restored backup, completely disabled lagfix. Reboot. Checked Voodoo control panel and it says RFS compatibility mode. CAMERA WORKS.

Also, I'm using a Transcend class 6 SDHC card which has ALWAYS been fast enough before, and apparently is fast enough now that I fixed the problem by removing the lagfix.

edit: I am in the process of converting data and cache to ext4 but NOT system. Going to see what happens.

edit2: cache/data converted. camcorder app giving a "recording failed" error again after some recording.

edit3: disabled lagfix again without restoring the backup. just unchecked the box. linda converted for some time. back to rfs compatibility mode. but camera's not working again. in the process of repeating the steps i outlined above to verify that the camcorder WAS working originally. i know that the camcorder definitely USED to work, so at SOME point it broke. i just have to figure out where that point is.

edit4: full restore did NOT work this time. i even flashed back down to bali 2.0uv. this is very strange because i'm sure when i was on 2.0uv my hd camera was working... what the hell. i am currently looking at my sdhc card as being a culprit. yanked it out and doing a diagnostic check on it using my laptop.
[Samsung Galaxy S (4G Model)] AntonX:
This camcorder issue is all over the Internet. Many people have it on different phones and different ROMs.

I'd start with full SD card scan, with check for bad blocks. Some people even recommend complete reformat (the long version with surface check), but maybe full scan is sufficient.
[Samsung Galaxy S (4G Model)] invario:
Yeah, in the process of doing that right now. :) Thanks... I suppose it's just a coincidence that my SDHC card just went bad and it was coincidental with my upgrading to Bali, sigh...
[Samsung Galaxy S (4G Model)] Jerry D:
I'm running Bionix Black Ice with Bali 3.2 System is rfs. Cache and Data are both EXT 4.

I just took a 3 minute video in both 1280x720 & 720x480 with no issues. I am using stock sdcard.
[Samsung Galaxy S (4G Model)] Juls317:
Only my /data became ext4....
[Samsung Galaxy S (4G Model)] Jerry D:
You can go into the voodoo app and go to Lag Fix Preferences and check the system and partition boxes to be applied on next boot.
[Samsung Galaxy S (4G Model)] invario:
Thank you sir. I removed my Transcend class 6, and insert the stock Samsung 16GB card that I blanked out.

Currently recording, 3 minutes, without stopping.

Going to have to look into the SD issue more. It's a class 6 card so it should be fast enough, but maybe it has problems when it's filled up. Hmm... Very puzzled now. I ran a full format on the card, ran a full diagnostics, and copied my apps back on and it still crapped out...

edit: Wiped out the Transcend class 6, left it blank, popped it into the phone, recording with HD just fine now. Hmm...
[Samsung Galaxy S (4G Model)] Jerry D:
Glad you got it working and that it is not a phone issue. Sdcards can be replaced easily.

I'm noob.

You ran a full format and diagnostics on your sdcard. How do you do that? ADB?
[Samsung Galaxy S (4G Model)] invario:
Nah, pulled out the card and plugged it into my laptop. Formatted it from there and had windows scan the disk. About to run another SD card diagonostic on it that I found on google and see how it works.
[Samsung Galaxy S (4G Model)] Juls317:
I have. it's been like that since first boot. Any special way I have to boot it?
[Samsung Galaxy S (4G Model)] Jerry D:
Thank you. I'm going to plug mine in. and check things out
[Samsung Galaxy S (4G Model)] Jerry D:
Just a regular boot does it for me.

You could go into voodoo recovery and scroll down to voodoo and see how lag fix is setup and make any necessary changes then reboot.
[Samsung Galaxy S (4G Model)] Juls317:
Voodoo is setup right
[Samsung Galaxy S (4G Model)] Jerry D:
I'm noob so you know.

Have you used terminal emulater to verify?

Edit: You can see what you system, data and cache partitions by entering:

su> enter

Mount> enter

Sometimes the app can be "off"
[Samsung Galaxy S (4G Model)] invario:
HUH! This is very strange... stranger and stranger!

So I have 2 SD cards. A Transcend Class 6 8GB card. This is the card that I've been having problems with the entire time. "Recording failed" error in camcorder after random short amounts of time... usually between 10-60 seconds at best.

I popped in an empty Samsung Class 2 16GB card that came with the phone. NO PROBLEMS.

Okay, so I thought maybe it's a card problem. NOPE.

I formatted the Transcend card, put that back in WITHOUT restoring what I had on the SD card. And it records in the camcorder just fine!!

I then took the Samsung Class 2 card, and copied all the files back onto it that I had on my SD card (a restore) and IT DOES NOT WORK ANYMORE.

I then restore everything onto the Transcend card, IT DOES NOT WORK.

In other words, SOMETHING on my SD card is causing it the camcorder to fail! HMMMMMM.

edit: Going to post in the other thread since it's no longer related to Bali. Sorry folks!
[Samsung Galaxy S (4G Model)] Jerry D:
Yes. Interesting..

Sounds like its not an issue with Bali Kernel. I think you should start a new topic on this sdcard issue.

There are some VERY Knowledgeable members in our Community who can help you/us figure this out.

A new topic thread would put this issue in the spotlight and therefore receive greater attention.

I'm noob and can't really be of much help on this issue. Sorry.
[Samsung Galaxy S (4G Model)] invario:
Yeah, someone directed me to this other thread:

http://xdaforums.com/showthread.php?t=1147574 :) Thanks.
[Samsung Galaxy S (4G Model)] drhonk:
Can provide proof of that? Ive been on ext4 in all three partitions for almost a year without any issue. If i do have some problem, theyre always rom related issue.
[Samsung Galaxy S (4G Model)] drhonk:
Actually, your phone can oc to 1.4GHz and stable as long as the kernel setting is done right. Some phone can even do 1.6GHz and stable. I can say tegrak is the best OC solution. .. to me is more of a bandaid solution to OC :)
[Samsung Galaxy S (4G Model)] RaverX3X:
naa its cool i just ran into a few apps that had issues with ext 4 as system thats all i trust ya man :P
[Samsung Galaxy S (4G Model)] peterpandesal06:
@drhonk is there any known issues if i flashed my phone from Bali 3.1 to 3.2UV? What are my advantages? Thanks.
[Samsung Galaxy S (4G Model)] peterpandesal06:
By the way in running kd1.
[Samsung Galaxy S (4G Model)] dsexton702:
Its not a glitch drhonk we tricked the voodoo on 3 .1 because the rfs formatter didn't format right once you applied 3.2 the rfs formatter started doing its job properly

Its not just the quad scores go up its also the mflops and the phone feels smoother

sent from my sgs4g 2.3.3, finally
[Samsung Galaxy S (4G Model)] Exodian:
Lost Root?

Was it ever figured out why some of us lost root when flashing 3.2?
[Samsung Galaxy S (4G Model)] RaverX3X:
for those of you with linda issues

Create a file or folder named “disable lagfix” in a a directory named “Voodoo” in your internal SD card.

do that before you install black ice :P Might help might not
[Samsung Galaxy S (4G Model)] drhonk:
No issue .. 3.1 and 3.2 are the same kernel except 3.2 has rfs_formatter fixed so now you can revert /data back to RFS
[Samsung Galaxy S (4G Model)] kcaj32:
I'm getting EXTREMELY POOR battery life performance. Any help will be appriciated.

I'm on Bionic Frost with Bali 3.2 kernel. I go from 100% to 0% in less than 10 hours with very light use - 30 mins talk, 4 emails checked every 15/30 mins using K9 Mail, some web browsing (15 mins or so). I'm also running 3G Watchdog, which updates every 30 mins.

I had a 1 year old HD2 before this phone running Gingerbread and got 24 hrs on that with exactly the same settings.

I went camping this past weekend and had the phone in Airplane Mode and it lost about 10 % per 24 hrs, which is good.

Looking at what consumes the battery, the Display is mostly the highest used followed by cell standby/voice calls.

Please help. I'm fed up or having to charge the phone every 8 hrs.
[Samsung Galaxy S (4G Model)] AntonX:
Your phone is probably always partially awake. Few programs are known to cause that, like Facebook or IM+. Look at page 40 of this thread towards the bottom, you'll need to check few things.
[Samsung Galaxy S (4G Model)] Young Kim:
whenever i reboot to recovery it says unknown volume path and the only way i can get to the red voodoo cwm is by manually going into recovery mode or going into the advanced section and selecting reboot recovery. btw my regular CWM version is 3.2.0.0 while the CWM Voodoo Lagfix version is 3.0.2.8x how do i access the red voodoo automatically when i reboot to recovery?
[Samsung Galaxy S (4G Model)] lenny hodapp:
It's because your using rom manager not krylon's cwm.
[Samsung Galaxy S (4G Model)] RaverX3X:
also wasnt it stated to not use rom manger..... please dont when the dev of the rom tells u not to its usually sound advice just a heads up :P
[Samsung Galaxy S (4G Model)] Young Kim:
can you guys tell or show me where krylon's cwm is? i've been searching for it
[Samsung Galaxy S (4G Model)] RaverX3X:
mhmm second post when u search cwm final

http://xdaforums.com/showthread.php?t=1099374
[Samsung Galaxy S (4G Model)] Young Kim:
ohhhh! one more question, is it the modified recovery or the cwm final
[Samsung Galaxy S (4G Model)] FBis251:
You need both files
[Samsung Galaxy S (4G Model)] drhonk:
Version 3.3 is available for download.

- Updated voodoo sound driver with version 10
[Samsung Galaxy S (4G Model)] Jerry D:
Thank You drhonk!!
[Samsung Galaxy S (4G Model)] GDofWR420:
Good work drhonk. Thanks for the updates.
[Samsung Galaxy S (4G Model)] Eric-1987:
We have the FPS cap again?
[Samsung Galaxy S (4G Model)] invario:
Thanks Dr.Honk! Flashed, working.

Wifi calling still coming out back speaker though... I know you don't think it's Bali related, and you haven't been able to replicate, but I can't think of any other explanation. If I flash back to stock now, Wifi calling will work properly again. Voice dialing also not working, along with Bluetooth general voice commands.
[Samsung Galaxy S (4G Model)] fredulus:
Im getting 1710 quad on v3.3UV with ext4 and 1.3 OC
[Samsung Galaxy S (4G Model)] AntonX:
Can anybody run this command with adb and see what the output is?

adb shell cat /sys/devices/virtual/bdi/179:0/read_ahead_kb

If it's 4096, then the read ahead cache is being set to really unhealthy size by this kernel. With 4MB there is no real speed advantage, but the phone overworks in the background by reading and discarding a lot of unnecessary data.

I also found that init.d tweak scripts that change this value to 2048, which is still high but at least a little more manageable, do not have any effect at all as something (Voodoo?) overwrites this later during boot process. So init.d is quite useless in this case.

Is somebody wants to change the cache size to something smaller during boot time, you'll have to use some other ways. I use Script Manager app that can run boot scripts at later time after Voodoo has done its things. I set mine to original 128KB.

I wrote before why big read-ahead cache is not necessary with solid state memory, here is explanations from somebody else:

http://xdaforums.com/showthread.php?t=1032317
[Samsung Galaxy S (4G Model)] cnote74:
I'm on black ice stable2 my read ahead is 128kb
[Samsung Galaxy S (4G Model)] dsexton702:
you do realize that drhonk is a linux engineer right?
[Samsung Galaxy S (4G Model)] AntonX:
I talked to him, he thinks it should not be like that too, at least init.d setting should not be overwritten. I can't find what sets this value this way on my phone. I'm on stock KD1 with Bali 3.3, don't have any apps that could possibly interfere, like SD boosters or such. Weird. Well, I'll dig a little more. At least look what size the cache set to on your phone.
[Samsung Galaxy S (4G Model)] martx:
So it's the kernel that's causing that, you can make a phone call on wifi and it works fine, can't accept a call or else it comes out the back speaker.
[Samsung Galaxy S (4G Model)] neocorteqz:
Thanks, awesome work.
[Samsung Galaxy S (4G Model)] kkoshko1:
Can I UV this to 50 or even 100 for even better battery life? Cause that's the only reason I'm on gb, I get sick battery with gb, horrid on froyo
[Samsung Galaxy S (4G Model)] invario:
I ran it. It's 4096. I don't have any init.d tweaks except the script you posted in your thread regarding 1800 quadrant scores.
[Samsung Galaxy S (4G Model)] jay661972:
flashed this yesterday on my sis in law phone, she really likes it. thank you. notice also android bootanimation showing on top of the galaxy s, not sure why and how can you go back to original stock kernel? thank you in advance
[Samsung Galaxy S (4G Model)] makavelicruz:
Dr honk thank you for this awesome 3,3 kernel update, great job.
[Samsung Galaxy S (4G Model)] nOl3ell:
how different between UV and none UV ?
[Samsung Galaxy S (4G Model)] makavelicruz:
Uv is under voltage, less battery consumption
[Samsung Galaxy S (4G Model)] AntonX:
My tweaks have nothing to do with this. You can remove them and still end up with 4096 for SD. They deal with internal MoviNAND anyway, not the external SD card.

I looked through all the logs and Voodoo and possible initialization scripts, didn't find anything that could be changing this cache size. No direct write to read_ahead_kb file, no hdparm -a command that would essentially do the same. At the time init.d scripts are executing, the cache is still set to default 128. Very shortly after it's being overwritten. It does not seem to be Voodoo because it's not doing anything to SD card, only to internal partitions.

I wonder if it has something to do with ext4 partition on SD card. Do you have it created? I do. I wonder what others would report and what it would be with and without ext4 on SD.

In any case I recommend setting this to some smaller value either by running scripts with Script Manager or using something like SD-Booster.
[Samsung Galaxy S (4G Model)] Jerry D:
I just ran a Quardrant Benchmark test then installed SD Booster. SD Booster showed cache size as 4096. I changed my cache size to 128kb, checked box to apply on boot and rebooted. I ran Quadrant Benchmark test after rebooting and scored 200 points higher.

My Voodoo lag fix is enabled and all partitions are EXT4. I checked partitions using Terminal Emulator.

I'm noob and I haven't installed ADB yet so I can't do any fancy testing. I don't even know if what I did means anything. I find this topic very interesting.

Thanks for your input.
[Samsung Galaxy S (4G Model)] dsexton702:
there are scripts you can put into a rom that will lower the size down
[Samsung Galaxy S (4G Model)] mbernusg:
I don't have my SD card partitioned and I'm @128kb

sent from my real Gs move in silence like lasagna
[Samsung Galaxy S (4G Model)] invario:
were you replying to me? You quoted yourself. :p anyway, yeah, I know your tweaks didn't have to do with that. only mentioned it for completeness....

will look into sd booster....thanks!
[Samsung Galaxy S (4G Model)] invario:
Okay, tested 5 different cache size settings using SD Booster to apply it, and running AnTuTu SD benchmark.

Card used is a Trascend 8GB Class 6. I ran the test 3 times for each settings. Here are the results. Cache size is in KB, speed is in MB/s, read/write.

4096

11.5/3.8

14.2/3.8

13.3/5.1

2048

13.3/4.8

12.8/5.3

12.7/4.2

1024

13.7/5.5

12.2/5.3

13.9/4.7

512

13.2/6.6

12.5/6.4

13.4/8.5

256

11.1/5.1

11.0/5.2

11.7/5.7

Guess I'm going with 512!
[Samsung Galaxy S (4G Model)] Jerry D:
Did you try 128 kb?
[Samsung Galaxy S (4G Model)] AntonX:
512 is OK. The speed increase may be not that real with normal operations, but 512 won't hurt much either. 4096 was way too excessive. Probably quite a few people have it now set like this and don't even know that their phones are oversweating in the background when reading from SD.
[Samsung Galaxy S (4G Model)] invario:
Does it only affect reading? How about writing? The results seem to indicate it affects writing too... but that doesn't make sense, since you said it's a read ahead cache. Hmm.
[Samsung Galaxy S (4G Model)] AntonX:
Only reading. It's read-ahead cache. The drive will fetch the specifies extra amount of data after each read operation hoping that that data will be used with the next read. If the data is not needed, it's just discarded.
[Samsung Galaxy S (4G Model)] ssmokey727:
This could be the reason why recording in 720p with the camera fails after a couple of seconds. 4096kbs is too high. and it makes SD Cards reads and writes slower than stock.
[Samsung Galaxy S (4G Model)] invario:
Hmm, well if it only affects reading, my benchmark numbers don't mean anything.... And now that I ran it again, the numbers are off again.
[Samsung Galaxy S (4G Model)] AntonX:
Well, it's quite possible that it would somehow affect the writing indirectly. I don't now exactly how ext4 works on low level, but theoretically there could be some readings required during write operations. For example to do a journal update during writes the metadata has to be probably read first. Or maybe some allocation tables have to be re-read.
[Samsung Galaxy S (4G Model)] ssmokey727:
I always tought that in the process of recording video you are writing to the drive. If writes are slow, of course it will impact the recording process therefore creating errors on writing and recording finally fails. As In my case it looks like reading keeps the same value when changing the read ahead cache. But it gets better in write speeds.
[Samsung Galaxy S (4G Model)] dsexton702:
anytime my camera failed after a couple a seconds all i did was fix permissions and everytime it has fixed it
[Samsung Galaxy S (4G Model)] johnlaqua:
any way to get the "android" to not display over the regular boot animation?
[Samsung Galaxy S (4G Model)] cnote74:
Download a bootanimation.zip and place it in system/media
[Samsung Galaxy S (4G Model)] nOl3ell:
thanks guy:)
[Samsung Galaxy S (4G Model)] nOl3ell:
one more question....after i flash with Bali3.3 i have to root again?
[Samsung Galaxy S (4G Model)] jager555:
flashing it shouldnt make you lose root
[Samsung Galaxy S (4G Model)] RaverX3X:
kernel changes dont effect root
[Samsung Galaxy S (4G Model)] nOl3ell:
Thanks guys.....so let's flashhh hahahahaha
[Samsung Galaxy S (4G Model)] invario:
Blah blah blah, it shouldn't... but sometimes it does. Caused me to lose root, even after fixing permissions.
[Samsung Galaxy S (4G Model)] dsexton702:
ive never ever ever lost root due to flashing something EVER :P

and ive must have flashed about 800 times now no joke lol
[Samsung Galaxy S (4G Model)] invario:
And yet there are several people in this thread saying that it happened. Hmm, strange!
[Samsung Galaxy S (4G Model)] GDofWR420:
Just gotta ask, and what have you done for the sgs4g community besides criticized everything our devs have posted. You comment on these posts but I see no support from you. Maybe you should contribute something before you start giving these devs a hard time. Sorry to be a prick but damn man show some support. THANKS TO ALL THE DEVS GIVING THIS PHONE SUPPORT.
[Samsung Galaxy S (4G Model)] Juls317:
im right there with you man!
[Samsung Galaxy S (4G Model)] GDofWR420:
Thanks
[Samsung Galaxy S (4G Model)] invario:
I'm not giving the OP a hard time. What I AM pointing out is that the guy is wrong. There are clearly people that DO have an issue, so instead of just sticking their fingers in their ears and just pretending that a problem doesn't exist, maybe they should consider that maybe some users DO actually sort of know what they're doing?

As far as criticizing, I post constructively when I can, and I try to do WHAT I can. Not everyone can be a developer, not everyone can be a tester, and not everyone is going to crowd around being useful. I make it a point to always thank the developers when they release something, and if a developer or user asks for something that I can help with (e.g. AntonX when he asked people to run an ADB command... and let's see... NO one ran it other than me?)

Or how about here, where someone's having a problem with their camera like mine, and I post my findings:

http://xdaforums.com/showthread.php?t=1147574

Or maybe here where someone has GPS issues:

http://xdaforums.com/showthread.php?t=1025061

Or here back in 2010 when I compiled and released a copy of TCPMP for WinMo that worked properly:

http://xdaforums.com/showthread.php?t=519543

Or here where I ran some benchmarks to compare the included Class 2 Samsung SDHC card to my a class 6:

http://xdaforums.com/showthread.php?t=985684

Or here where I post a solution to an MMS problem:

http://xdaforums.com/showthread.php?t=650657&page=2

So please, you might not mean to be a prick, but you are. Get off your damn high horse.

I appreciate every thing the developers do. But when someone is describing a problem, and a few other people are +1 ing it, and another poster (developer, or user, it doesn't matter to me) makes a post that says nothing except "well *I* never had a problem" it's not exactly very CONSTRUCTIVE, is it? He might as well have just called all of us delusional and a bunch of idiots that don't know how to follow instructions or flash a kernel.
[Samsung Galaxy S (4G Model)] jager555:
stop crying about it. its not the kernel that made you lose root. those few people that did lose it probably did something that caused an anomaly or messed with something. the point is, it was drhonk who made this kernel and he is nothing short of an expert with this stuff and (with krylon) has done more for this community than anyone else has. same goes for the members of team acid, so before you start getting into an argument about it, think about it and if that doesnt help, develop your own kernel.

also, no need to repost all of the times you have "helped" someone. this is a community of peers that share knowledge they have learned from other people and from experience. but since you seem to be counting, GDofWR420 has done way more than fixing a freaking gps or mms issue. i think it is YOU who has to get off your high horse because you havent done anything significant enough to brag..but then again, neither have i. grow up and move on.

moral= if you lost root...take the 30 seconds to unroot the damn phone.
[Samsung Galaxy S (4G Model)] dsexton702:
ROFL!!!

geeze guys no need to get mad, and as for you invario you can ask drhonk himself who is LINUX ENGINEER that the kernel SHOULD not break root :P

SOOO im not wrong :D