yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] existz:
Its not really as much as just having a lagfix, its having an overall better file system.. ext4 has been around awhile in linux, giving it time to have all the bugs worked out, being optimized, tweaked..etc etc.. giving it an advantage over rfs.. Samsung even ditched it and went back to ext4 for the nexus s, and more than likely going to be the goto file system for future devices.. I always recommend ext4 over anything else, even if you don't have lag, its still best to use ext4..rfs sucks IMO..but that's just me..

Sent from my Captivate
[Captivate Android Development] shaolin95:
Can you provide me an example where I can see the benefits of ext4 vs rfs on 2.2.1 which is improvided from previous releases? I honestly have yet to see one but experience lag instead like the previous poster mentioned.

I am not saying I am wrong, just looking for someting that shows the benefits besides a quadrant score of course lol
[Captivate Android Development] existz:
By replacing RFS with EXT4, the ‘sync on fileclose’ problem is removed. The EXT series of filesystems is also more efficient at allocating information into blocks than RFS/FAT32 is. This means less real writes to MoviNAND, which means that the MoviNAND buffer should be smaller, and when a sync is called, fewer commands have to be run. When a sync is called on EXT4, it will still be very slow, as the MoviNAND’s sync is still slow.

Basically, EXT4 improves filesystem grouping which leads to less commands, and does not have the broken ‘sync on file close’ that RFS does. It will not heavily improve sqlite database access in certain apps, as the full fsync on transaction end will still have to go through MoviNAND, and will be slow.

http://hkdennis2k.homeip.net/2010/11/04/reality-behind-rfs-lag-of-samsung-galaxy-s/ <---good read

Sent from my Captivate
[Captivate Android Development] shaolin95:
I actually have read quite a bit about the file systems indeed and yes, from the information it looks like it would be a lot better but the issue is when put to practice in our phones, I have yet to see any benefits, at least after 2.2.1 roms came out and on the contrary, I have noticed issues instead. Just my findings on my own phone though.
[Captivate Android Development] sicmadek:
so i disabled lafgix and will see how tings go.
[Captivate Android Development] shaolin95:
Please not that from my experience my phone is not the same when disabling lag fix compared to installiong the ROM without the lagfix in the first place..not sure why though. And this if for a 2.2.1 rom I am talking about also.
[Captivate Android Development] chisnz:
I've tried flashing #46 and #48 plain SP versions through SGS Kernel Flasher and CWM with the same behavior: On first boot it gets part way through the Android 3 dots screen then shuts down and If I have a charger attached, will start charging. I flashed straight over existing lagfix from Speedmod. After flashing back to Speedmod things are ok though usually some of my widegts have disappeared from Go Launcher EX.

I'm running Serendipity 5.6/Speedmod K13 and am keen to get back to some UV ability that I used to enjoy with Assonance/Setiron. SP seemed a great option, but I've got something fundamental wrong.

Any suggestions?
[Captivate Android Development] existz:
Does it ever fully boot or just shuts down before getting there? And it happens both on charger and off?

Sent from my Captivate
[Captivate Android Development] chisnz:
Two times without charger: Appears to properly boot then quickly reboots.
[Captivate Android Development] elghouchd:
Oh no im getting ~18.5....I used to get 19-19.5 in the build #41, why is that?
[Captivate Android Development] WickedNite:
Okay, so now I'm using the 100hz it runs much smoother than the xt version in my opinion. Gonna stick to it now.

Sent from my Muscles using Brain Cells
[Captivate Android Development] froli13:
Are you seriously disappointed because you "lost" 1 MFLOPS in linpack ??

You won't even notice it...

I will never understand why people care that much about benchmarks tests...
[Captivate Android Development] xreflection:
One word: Compensation. ;)
[Captivate Android Development] elghouchd:
Yeah thats true sorry....and i was wondering where you got that wallpaper on screenshot 1 in your sig?
[Captivate Android Development] sicmadek:
Definitely
[Captivate Android Development] psloan:
existz,

Great info. Can I suggest you put that recap in the first or second post? This recap will get burred and people won't see it and start asking the same questions.

--pat
[Captivate Android Development] froli13:
Can't remember where I found it, but I uploaded it there: http://dl.dropbox.com/u/167052/wallpaper0252.jpg
[Captivate Android Development] existz:
Yea, im going to make the 2nd post a FAQ... I know stuff gets overlooked, but its starting to be the same 2-3 questions over and over, im not trying to be mean, by no means, just want to clear up some stuff so the same questions don't keep getting asked..

Sent from my Captivate
[Captivate Android Development] Grandelama:
The same happened to me a couple of times (not every time I boot, though) on #48...never happened on former versions...

I have been using the same uv config for the last 2 weeks without any problem (no lockups no CD). 1200 (-50) 1000 (-75) 800,600,400 (-100) 200,100 (-50)

Could it be the updated frequency code? I will try to decrease UV to see if it helps
[Captivate Android Development] existz:
Its possible, try adjusting it, if that doesn't fix it, let me know and I can try something else in the next test version, I also changed toolchains due to the plug/unplug power reboots, but haven't heard if that fixed it or not

But that's the only 2 things that changed

Sent from my Captivate
[Captivate Android Development] sicmadek:
it happened to me on #46 so i wasnt on the new tool chains. i also didnt have any undervolts. i think it may be from the lag fix.
[Captivate Android Development] existz:
Thanks, atleast that's rules it out.. im not sure what's causing it. Im not sure if its from having an ext4 file system, I've used ext4 on all partitions plus system for months and never had this happen, what tweaks are you guys using, if any, from in recovery? I don't think ext4 alone would cause it, trying clearing the dalvik cache in recovery, any time something weird happens, try clearing this first if you haven't already, as clearing it can sometimes fix these things. If that doesn't work, wipe the cache partition, I always wipe cache and dalvik cache after every flash, but note, even though wiping it has never caused any problems for me, after 100s of flashes, if something goes wrong im not responsible ...it shouldn't hurt anything, but **** happens .. also note that it will take longer on the first boot after wiping cache/dalvik cache.. this is normal, give it time and let it boot... in the mean time, ill look into other possible fixes.

Sent from my Captivate
[Captivate Android Development] existz:
Ill try adjusting a few things, ill set the governor settings back to stock and see if that helps with anything, I had changed the freq_step from 5 to 20% , which it would make the cpu scale lower quicker and scale higher faster, so it might be a little bit to aggressive ..ill go back to stock and if it helps, ill then try tweaking it 5% at a time. Ill get a test build up tonight or tomorrow, if you have this problem please join my irc channel, link in OP, its where I discuss progress..etc.. Im usually on but if im not, I should be soon.

Sent from my Captivate
[Captivate Android Development] aalh:
I had this behavior start after trying the "disable lowest screen level" and setting a color tint

even after turning them back off it occasionally happens
[Captivate Android Development] joeshmoe08:
http://www.youtube.com/watch?v=G68fHZig9nA

Sorry existz, couldn't resist. :D
[Captivate Android Development] johan8:
Holy !

I just love it !

;)

[YOUTUBE]KrIiYSdEe4E[/YOUTUBE]
[Captivate Android Development] AJerman:
Updating to build 48 now. I really hope it's better than 46. Honestly, 46 was by far the worst build yet for me for charge death. Basically every morning I woke up to a phone that wouldn't turn on, and I was using OC/UV settings that have never caused an issue before. I start a new job tomorrow, so I really can't have any chance that my phone doesn't wake me up, so I'm just going to disable OC/UV entirely until I can test it more, but I'm hoping the issues go away now. I was also using XT last time which I had never used before, so I went back to the non-XT build. Crossing my fingers!
[Captivate Android Development] Auridran:
I have personally found the XT version to be significantly less stable and require less undervolting than the regular version.
[Captivate Android Development] AtoZ0to9:
¡ʎppnq uıɯoɔ ɯǝ dǝǝʞ ˙˙˙sןɐuɹǝʞ ʇɐǝɹƃ
[Captivate Android Development] Grandelama:
Thanks, I think will try the 100hz version..cause with #48 500hz charges of death restarted...I already have had 2, while in the last 10 days I have been pretty stable with the same UV settings...

Probably it is just a coincidence but, who knows!
[Captivate Android Development] Loggik:
+1. The 1000Mhz was smoother, but I experience a few stability issues (no charge death though, which I was happy to not see). But the XT 500Mhz is working perfectly for me... though my UV is -75, -75, -75, -100, etc... which I don't think is a very big deal. Do you mind me asking what your OC/UV settings are? Thanks (:
[Captivate Android Development] olo567:
I've only had one chance to do an overnight charge to try to reproduce my unplug freeze, but no issue today. I'll keep you updated, but so far so good!
[Captivate Android Development] richuwo11:
Ok, I have an issue... I oc'ed too much apparently. I had it set to 1.3 and -75, everything else -100. Now my phone freezes everytime after a reboot when it's scanning my sd cards.

Is there any way to reset the OC without odin flashing? I don't enough time to get into voltage control to undo the OC before it freezes on me.
[Captivate Android Development] gibson3659:
3-button into cwm and flash a speedmod kernel. If you don't have one, mount usb while in cwm and copy one over, reboot and delete the init file. I've been thinking of keeping a zip that I can run from cwm that will delete the init, or restore a previous working one, for cases like this. Actually, that should be a feature of the voltage app.
[Captivate Android Development] Grandelama:
You could try to remove the external sd before booting, you will gain few seconds more and sometimes they are enough to open the voltage control and to remove boot settings...
[Captivate Android Development] slider2828:
I didn't think it would matter to much by turning off auto rotation in regards to battery life, but OMG it makes a huge difference.... With a 30 minute call and 11 hour standby I am still at 80%... Amazing!!!
[Captivate Android Development] IStern:
Having some stability issues playing 3d games with #48 even after dialing down the UV. #46 worked the best so far for me.
[Captivate Android Development] richuwo11:
Thanks for the reply, but even that wont work. I mount USB storage and I can see the drives in my computer but i cant access them.

It could be a messed up rom flash combined with a bad oc. I'll just reflash to stock and start fresh again. I backed up all of my apps right before, so I shouldn't lose much other than my time.
[Captivate Android Development] existz:
You can use adb shell to remove S_volt_scheduler, boot into recovery and type the following..

adb shell

rm /etc/init.d/S_volt_scheduler
[Captivate Android Development] existz:
The next release should be a good one, I've done quite a bit in this release, mostly bug fixes, but some new additions as well...getting ready to send latest test to testers...here's what we are looking at...

- updated speedmod color settings

- fixed boot frequency to 1ghz (should help w/ restarts on boot)

- reverted governor freq_step (should make things more stable/smoother)

- enabled high res scheduler ticks

- increased gpu refresh rate [freq=60-->72] (needs testing)

I've also been messing around with adding compcache (ramzswap) but not sure if ill include it or not, might be a few builds before I do
[Captivate Android Development] bullseye8877:
Uhh, which one of those files am I supposed to download? Sorry I am new to this...

I'm already on hardcore's speedmod kernel so I know how to install it but I just don't know which one of these files I should download...
[Captivate Android Development] sinichi21:
hi i have tried this kernel but my screen keeps on freezing sometime i oc 1200 and my uv settings is 100 100 75 75 50 50 25 25 am i doing something wrong here? and im using the non xt
[Captivate Android Development] existz:
Lower your UV, this has been discussed 100x, read FAQ in post #2.. some phones can't handle anything past 1ghz and some can't handle UV at all, so if lowering UV doesn't work, lower your OC

Sent from my Captivate
[Captivate Android Development] sinichi21:
thanks sorry for a noob question i just decided to use a oc kernel so im not used to this yet thanks for reply will try that
[Captivate Android Development] existz:
I recommend the non-xt one, (kernel hz=100 | user hz=100) ..provides the best battery life - performance ratio ...make sure to read the FAQ in post #2 and shaolin95s mini OC guide in the OP

Sent from my Captivate
[Captivate Android Development] Kionic:
Wow..i got 12 hours of battery life on the xt 1000 version. I havent even undervolted it yet. Exitz...is the man.
[Captivate Android Development] ridethelight:
Am i the only person to overclock to never have any problems with -100 UV on everything? Ive never had 1 issue from OC'ing lol
[Captivate Android Development] existz:
When OCd to 1200 I can use (75,100,100,100,125,125,150) 100% stable.. usually use 75 with 1300 as well and 50 on 1400, but 1400 isn't fully stable...seems mine likes OC/UV also

Sent from my Captivate
[Captivate Android Development] existz:
Next version might be better, im getting the best batt life yet with my latest test, hopefully its consistent with my testers .. I can unplug at 8-9am and at 1am have 30-40% left, with moderate use (not going to say heavy since im sure others use their phone heavier than me, im not big on games...atleast until Madden comes along :)..)

Sent from my Captivate
[Captivate Android Development] froli13:
Mine is not as good as yours but still pretty good (settings in my sig). I should try to UV a bit more since Existz changed the oc/uv code. Maybe my phone will like it :)
[Captivate Android Development] bullseye8877:
Ehhhhh, it bricked my phone, lol.

When I turned it on it would just get stuck at the logo...

Now I'm reinstalling the stock rom and then my 2.3 rom then just hardcore's kernel, lol.
[Captivate Android Development] knyghtryda:
I had one version of suckerpunch soft-brick my phone as well. I didn't want to start over, so I used Heimdall to reflash the kernel in download mode. Fixed everything, and didn't lose any data in the process.
[Captivate Android Development] psloan:
I can only get to

#48

1200 1000 800 600 400 200 100

-100 -100-125 -75-125-125-125

note the only -75 on 600. Not sure why, but if i go lower then that the camera switch mode test will freeze up on me. Dose this indicate a faulty phone?

--pat
[Captivate Android Development] lazymegaman:
psloan: I doubt that would indicate a faulty phone. It's one test that fails when you're doing something to the phone that it's not designed to do outside of the factory. Now, if that test fails while you're NOT undervolting, THAT would indicate a faulty phone. Undervolting is an art, not a science.
[Captivate Android Development] existz:
Lol 1+ ....ill have to quote that in the OP

Sent from my Captivate
[Captivate Android Development] sjavvaji:
could not have said it better myself
[Captivate Android Development] xdahgary:
lol. Thanks for the masterpiece existz.
[Captivate Android Development] AJerman:
Well, that could have been it, but I'm starting to suspect something more. My phone may need a full flash because I left it unplugged last night to make sure I wouldn't have any issue with my alarm like I was saying, and when I woke up the battery had dropped something like 70% overnight while doing nothing, so something is definitely not right. I'll have to see if it's a bad app or what.
[Captivate Android Development] Dmoney5150:
I love this kernel and i'm a huge fan of zack synder .....keep up the good work!!!
[Captivate Android Development] existz:
Ill probably release #49 tomorrow, so far its reported there's a noticeable performance gain, battery life keeps getting better..and a few bugs fixed.. ill try to get it up in the morning or afternoon for you guys

Sent from my Captivate
[Captivate Android Development] opcow:
Cool. We'll call it the morning wood edition.
[Captivate Android Development] existz:
Lol, I was wondering if someone would say something after I posted it..

Sent from my Captivate
[Captivate Android Development] aalh:
in what order are those values?
[Captivate Android Development] existz:
75(1200) 100(1000) 100(800) 100(600) 125(400) 125(200) 150(100)..then I use 75(1300)..all 100% stable, no sleep/charge death, then 50(1400) but its not fully stable, but it will work the longest at 50, no matter what I use its not 100% stable, so 1300 is my limit

Sent from my Captivate
[Captivate Android Development] LimaI896:
Yess 500hz thank you! This kernel is just amazing.

Tried out voodoo sounds properly, now I understand the hype. :)
[Captivate Android Development] IStern:
Thanks, awesome kernel!

I started out with the 1.28ghz 500hz kernel. While the UI was super smooth, I lost a few FPS on 3D benchmarks, and actual games also seemed a little stuttery. Went back to the 100hz kernel and everything was back to normal.
[Captivate Android Development] jjtitus098:
Is there going to be a cold or warm version of this kernel or is that not in your plans?
[Captivate Android Development] LimaI896:
Just curious if kernels affect internet speed? Became very sure and my speed test scores are horrible. Just want to make sure that it isn't by coincedense.
[Captivate Android Development] existz:
Its possible if theres enough request for it
[Captivate Android Development] existz:
Wifi or network?
[Captivate Android Development] Dlev7:
Hey existz just wanted to say congratulations on releasing this, and it seems like your getting quite the praise for this one so hats off to you but I have a couple questions if you could help me out before I try this out.

I currently have Speedmod k12q with lag fix and all tweaks enabled, and a JL3 modem running on Darkyy 9.0.2?

Am I good to go just flash this straight over via SGS Kernel Flasher? Any precautions I must take first? And what about the UV OC app is that a necessity?

And help will be greatly appreciated.
[Captivate Android Development] LimaI896:
Network havn't tried wifi yet
[Captivate Android Development] sjavvaji:
has anyone else had there phone freeze when powering off?...im trying to determine if this is a uv issue or kernel issue

phone is capable of 1.4ghz so its not hitting a wall
[Captivate Android Development] ThisWasATriumph:
+1 for 1200mhz version. Mine freezes at 1280.
[Captivate Android Development] existz:
No probs here, I've had to power off about 20x today flashing new versions and I always use pwr button for extended power to recovery
[Captivate Android Development] sjavvaji:
power menu to recovery works fine...power menu to power off freezes
[Captivate Android Development] phoenix2217:
if you have UV then I believe that's your issue. I had it a while ago on glitterballs and if I UV too much it would freeze at the splash screen on shutdown. Also, make sure if you're UV that you don't have SetCPU installed at the same time. Some people have issues with that and VC running at the same time. But as with all kernels, YMMV.
[Captivate Android Development] sjavvaji:
to fix this...would you lower the uv on the higher frequencies or lower frequencies?
[Captivate Android Development] Nickel Dime Bay:
i just flashed 500hz over the other one, are all my tweaks and lagfix still enabled? Everything is running perfect
[Captivate Android Development] mkr14:
Great! Thank you for removing that!

In regards to the gpu clock, are the cpu and gpu clock speeds tied together? Setiron has a cpu and gpu clock speed list in his kernel thread that suggests that the cpu and gpu clocks are tied. 1288 is giving a 184mhz gpu clock while 1200 is giving a 200mhz gpu clock.

Just wondering, I have been digging for an answer with no luck. Do you know of an app that shows these two clock speeds? I can only find the max cpu clock.
[Captivate Android Development] joeshmoe08:
So does that mean the non 500mhz versions are 100mhz or 250 mhz? Also is the smoothness 500mhz significant?
[Captivate Android Development] lrs421:
Whats the difference between the cold and warm versions?
[Captivate Android Development] airbillion:
Voodoo sound v3 is out, any possibility of an update?
[Captivate Android Development] phoenix2217:
sjavvaji

"to fix this...would you lower the uv on the higher frequencies or lower frequencies?"

what are your current settings for VC? I would definately take 25 off the top (1280) and start from there. Test test test. I did at least 50 + runs on stability test and 30 min loop on neocore before I found stable. Currently it is from lowest to highest, -125, -100, -100, -75, -50, -50

edit- forgot quote :)
[Captivate Android Development] AReynante:
Is that normal? That seems like a ton of UVing to me lol, I must play it too safe. Also wanted to ask, I went to the folder to delete the previous voltage control stuff, but there isn't a file named like the one in your first post. Any ideas? I want to update, but I don't want to mess anything up.
[Captivate Android Development] johan8:
On fire ferocious kernel for Captivate !
[Captivate Android Development] Auridran:
After doing some extensive testing, I've come to my final (unless I crash, but I haven't yet) UV levels.

100: -150

200: -150

400: -100

600: -125

800: -125

1000: -150

1200: -125

I've been using FPse to test for stability. It really stresses the phone out. It can crash UV levels that were tested with Stability Test for half an hour by simply trying to load a ROM. After getting to a level that would load, I left FPse running for half an hour at that frequency in a stressful 3D scene, by limiting the max frequency in VC. Before you ask, yes, testing 100 and 200 is painful that way.
[Captivate Android Development] shaolin95:
I wouldn't trust FPse (which by the way that EMU Rocks!!!!) alone. I left my phone running Tekken3 for a long time yesterday but the first benchmarks I tried after that locked right away.

The beta I am testing though seems to be doing a lot better so far at 1.4...so far it is stable (knock on wood). :-)
[Captivate Android Development] Killemalll:
Any ideas if the next release will work with Darkys 9.3 rom, JS5 based?

Sent from my SGH-I897
[Captivate Android Development] existz:
Pretty sure it will, running JS5 myself

Sent from my Captivate
[Captivate Android Development] slaman:
Agreed...and each phone is different. I have now accepted that I cannot UV at all at any frequency without sleep deaths or freezes during use. This is despite testing stability at each frequency before accepting the UV setting.

I now have also had to lower my OC to 1180 because of freezes.

Sent from my Samsung Captivate SGH-I896
[Captivate Android Development] existz:
*UPDATE*

Build #49

-Updated SpeedMod color settings

-Reverted governor freq_step back to stock

-Limit boot clock to 1ghz

-Enable high res scheduler ticks (HRTICK)

---Optimize fair scheduler params to work well with HRTICK

---Add fix for wakeup issues by disabling it during suspend

-increased refresh rate of gpu (freq=60-->72)

NOTE Ditched the SmR since its starting to take on a life of its own.. so far this build has had very good feedback, most report a noticeable gain in performance and battery life (results may very)
[Captivate Android Development] WickedNite:
What do you mean by reverting back to freq_step stock?

Sent from my Muscles using Brain Cells