yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] rajendra82:
I don't buy the unfragmenting theory. Unlike a magnetic disk on a computer, our phone storage is on moviNAND. Having the data stored in contiguous blocks will provide no speed benefit. The controller also writes the data to least used blocks to do wear leveling, so backing up, erasing and restoring the whole partition during file system conversion will also not make it less fragmented in any way.
[Captivate Android Development] arffer:
Agreed, that is the same reason that noop (or perhaps sio) are the best IO schedulers. With no physical rotation and head movement in solid state storage, most of these speed techniques simply do not apply.
[Captivate Android Development] shoman94:
Thats because the database IO score is about 100 points higher. the sd card read/write throughput is about the same... as well as everything else.... but the database IO which I'm guessing is access time? Not sure exactly what that score means... but I think it refers to the amount of Input/Output operations it can do per sec. If thats correct then RFS can perform about 75-80 IO's more per seconds which in HDD testing the higher the better.

I switched back to EXT4 last night again to try it out and I am once again going back to RFS. I trust Antutu as I've been using it for some time now and seems accurate and also It's my feeling that prefers RFS.

People do to much dismissing around here.... and think things are better because someone says so.... or its a standard.... just use what feels right for you and thats it. It's the same with everything else we have for options around here. So many ROMs, Kernels, and Modem choices... theme choices... just use what YOU like... not because someone said its the best.
[Captivate Android Development] Time_Zone:
I think they may have done some caching tricks in rfs but I suspect this is not safe and defeats the purpose of a recoverable file system. Ext4 is tried and true, there is a reason it is the Filesystem of choice for most linux distros. There is a much larger test base for ext4 as well, rfs is limited to samsung customers.

However, shoman94 is right. Use whatever feels right to you.
[Captivate Android Development] IDoMy0wnRacing:
Wipe the dalvik cache and cache partition then reflash the kernel. You shouldn't be asking this on the Talon tread...
[Captivate Android Development] mrhaley30705:
did you convert back to rfs before flashing xcals?
[Captivate Android Development] kevinjmoore:
No. I didn't go back to RFS...just flashed continuum as is, but didn't know how to deal with whatever lag fixes it has. Can you walk me through that?
[Captivate Android Development] harpo1:
Not on this thread. Go to xcals or do it via PM. Come on guys show some respect for eXistz.
[Captivate Android Development] Vivified:
Using PlayerPro. When I use any headphones I hear random cracking/popping while listening to music. The problem goes away when I flash Dark Core, comes back with Talon and xcal's kernel. The issue is just nonexistent on Dark Core in comparison.
[Captivate Android Development] existz:
hmm..ok..ill try to reproduce it..im using miui music player and no cracking/popping, also use it hooked up to my cd player through headphone jack and no issues..but ill try a few different things and try to make it happen
[Captivate Android Development] grkmaster:
I use PlayerPro as well and yesterday I tred to see if it would happen to me but it didnt. Very odd
[Captivate Android Development] nakedninja42:
I use Power AMP and also changed default Music on Perception to CM7 version, justed tested both, no issue.

Tested it further and tried both out with voodoo sound plus, had a run that worked off the voodoo from kernel and test run that used only the program for non-kernel support. No issues.

Tested further using klipsch S4 and Dre Beats
[Captivate Android Development] Vivified:
I'm willing to upload a song I have the problem with but will only distribute to those who pm me because I don't want any issues with copyright/etc.

It is 320 kbps mp3.
[Captivate Android Development] Elektron777:
How can I include other bootanimation in this kernel ? Thank you !
[Captivate Android Development] waghoba:
one cannot insert bootanimations into the kernel....you copy the bootanimations ZIP file to appropriate location...
[Captivate Android Development] Elektron777:
I copy animation files into system/media . This method don't work .
[Captivate Android Development] IamSonoma:
I have the same but in my case over bluetooth.
[Captivate Android Development] ihalatci:
xcaliburinhand's OP says this for custom boot animations "For the JVB rom, the bootanimation.zip needs to be /system/media/sanim.zip <- notice the name change".
[Captivate Android Development] seanzscreams:
but darky kernal you can use regular bootanimation.zip

http://www.darkyrom.com/community/index.php?threads/kernel-dark-core-2-x-ginger-kernel.2072/
[Captivate Android Development] existz:
PM sent about cifs/tun support
[Captivate Android Development] mrhaley30705:
What method, other than Odin, were you using to flash the kernels with?
[Captivate Android Development] existz:
This is not the same as darky kernel, rename it to sanim.zip
[Captivate Android Development] Time_Zone:
But... But... the apple cart... she is turned over...
[Captivate Android Development] iXNyNe:
How about shutdown animations?
[Captivate Android Development] Vivified:
I have the problem using my BT headphones as well. It's listening to music in general while on Talon or xcal's kernel when I get this issue, no matter the headphones(i've used 4 kinds so far)
[Captivate Android Development] existz:
Should have an update in a few with 1.2ghz OC/UV, Interactive governor and added CIFS/TUN support..plus some upstream fixes...probably be a hour or two
[Captivate Android Development] iXNyNe:
Any other states included? (600? 900? 1100?)
[Captivate Android Development] existz:
No just 1200 for now...really no point adding in the others when using ondemand/interactive governors
[Captivate Android Development] mrhaley30705:
Thank you for that. I forgot which thread I was on when I answered (is that a sign of too much xda?).
[Captivate Android Development] kevinjmoore:
Sorry, I was on three threads at once. Won't happen again.
[Captivate Android Development] Spidious:
Well read all the power on ext4 over my lunch hour..

I was on rfs...It ran smooth and no lag at all.

I had tried the ext4 twice before, and thought it was laggy and slow.

So on my lunch hour I converted it over to ext4 again..

Same problem. After a hour of running, it gets real laggy. The screens no longer would smoothly slide across the screen.

So for me I will stick with the rfs version. It works great. Sure the scores may be a little lower. But I want it smooth as silk..

So it seems that some phones run better on rfs and some on ext4 ?
[Captivate Android Development] garringm:
Are these reboots soft reboots where it goes straight to boot animation or a full reboot where it shuts down and powers back up?
[Captivate Android Development] baghera1979:
Shutdown and rebooted from start

At least for.me.that's what it does
[Captivate Android Development] garringm:
On these kernels it says you have compcache built in is that enabled by default or is there a way to toggle on and off, if so is there an option to adjust the cache size or is that a prest in the kernel and what size would that be.

Well nevermind i just found that it is enabled by using cat proc/swaps and free commands in terminal. Now let me ask are there any other benefits in running compcache other than trying to keep programs in memory. Where is this cache memory stored

Nevermind just remembered how to shut it off. So if i play with swap off then want to enable swap again will it go back to its original size or will i have to set it as well
[Captivate Android Development] existz:
Its a full reboot, ive had it where it would just shut off a few times...but I have confirmed, so has a few testers of mine and then someone on this thread, that it happens on multiple kernels, including stock JVH kernel...also happens on multiple roms.. so not sure if its a samsung bug or what
[Captivate Android Development] garringm:
Well that kills my theory of a memory overload most generally they will just cause a soft reboot which Im sure you have already explored extinsively. However maybe you can help me with an answer. I have read in other threads about raising th heapsize not alot but just a little to help performance. By default roms here are set at 64 other devices typically run around in the 20's if i remember correctly and they were able to get great benefit raising this to 32 or more but not too high. I have raised mine to 84 just to see. Things seem to be running extremly well and super snappy. No more home screen reloads on Launcher Pro. Am I actually causing other ill effects in doing this or am I just imagining
[Captivate Android Development] ee23hd2:
can someone tell me what the difference is in the bigmem version? sorry for the noob question but i was curious if i gave u more memory or ram or what... thanks in advance
[Captivate Android Development] pikachu01:
Bigmem gives you more memory but disables 720p video recording.
[Captivate Android Development] ee23hd2:
Is it enough to make a noticeable difference in speed? Is it worth losing 720p video rec.? Thanks
[Captivate Android Development] garringm:
Do you really need to record in 720. you can always try it if you dont like it try a different one.
[Captivate Android Development] ee23hd2:
Nah I dont really care about it.. Wasnt sayin that, just wondering if anyones tried both versions, and if there is a noticeable speed increase or not.
[Captivate Android Development] existz:
Its not really going to increase the speed, it gives u more available memory, allowing more apps to be ran before lmk kicks in, more multitasking
[Captivate Android Development] nappent:
I finally got to test my BT after installing 0.2.1 a few days ago and I'm see a 100% improvement. I know you said you didn't change anything but my BT syncs up super fast like it used to with Froyo. No more timeout issues so far.
[Captivate Android Development] slayp00n:
I just want to say, I converted back to RFS, went from 1900+ quadrants to 1100s...

converting back to ext4...

The phone lagged like crazy on rfs.. was so smooth on ext4, no idea how people could prefer rfs it is inferior.
[Captivate Android Development] slayp00n:
back to ext4, highest quadrants ever.
[Captivate Android Development] 13_:
By no means do i suggest Quadrant is reliable. However after a clean Serendipity 7 flash followed by a clean Talon flash followed by restoring apps and a reboot, this is the result . . . (second run)

. . . This is easily 1000 points higher than on Froyo for me. Does the phone seem 1000 times faster? No, but it is ridiculously smooth and is super fast, just not as blistering as the score says. Antutu bench is approx the exact same as it was on Froyo with Onix 2.0.5 @ 1.2Ghz, in the 2300 range, the difference is responsiveness and smoothness.

Great work existz, much appreciated
[Captivate Android Development] slayp00n:
Wtf is this, how cna you get so high, I hover 2k....
[Captivate Android Development] kitkitfok:
Will you update to Speedmod color/sharpness in the next build?
[Captivate Android Development] Vivified:
It's already in the latest tests
[Captivate Android Development] existz:
Yup, already added in the next test build, been running it for last 2 days, I like the sharpness fix over what was used before.. You can keep up with updates with my twitter and/or my github commits

http://www.twitter.com/existz_dev

https://github.com/existz/linux_gt-i9000-gb/commits/gingerbread-dev-jvh

^^oops, Vivified beat me to it :P
[Captivate Android Development] 13_:
Nothing special was done, just what I stated. There are several other posts in this thread with even higher scores. Each device is different and the apps and setup are different per user so that will make scores vary also. Quad is quick but not a good indicator of actual performance, especially from device to device and brand to brand.

But... say you had a phone that got 1000, you make some changes add some mods and now it gets 1500. That shows that you HAVE gained some performance, how much is debatable, but you know you are moving in the right direction. Thats about all the score is good for in reality . . . direction. IMO of course. :p
[Captivate Android Development] TonyStark R.I.P.:
existz any idea if this will work on Mikeys latest, Serendipity 7?
[Captivate Android Development] 13_:
I'm running Serendipity 7 and Talon now. Great combo, no problems thus far, smooth and fast. If you meant the test build with sharpness, I cannot vouch for that.
[Captivate Android Development] pixbuf:
How to debug crashes

I'm running 0.2.1 in Continuum 5.5 on a 1008 Captivate.

I've had my phone crash or freeze up or spontaneously reboot a couple of times a day for a long time now. (I don't think it's the kernel, but it did seem that 0.1.4 was smoother and had far fewer crashes.) I'm thinking it's some bad app or service that's messing up but don't know how to find it. I did logcat-enable, but I can't find the log file. Can someone point me to it, or give me some advice on how to debug these crashes?

TIA.
[Captivate Android Development] TonyStark R.I.P.:
Which one and did you ODIN it?

I may wait for the sharpness version, so all I have to do is flash it once
[Captivate Android Development] TonyStark R.I.P.:
Go back to 0.1.4 and see if the issues you were having on 0.2.1 continue.
[Captivate Android Development] 13_:
0.2.1 regular. Yes, used Odin, quick and painless.
[Captivate Android Development] existz:
Was it with wifi? There's a know issue with wifi causing reboots, seems to have started with jvh (0.1.4 is jvb so probably didn't happen with it).. I can reproduce the problem on multiple kernels and roms aand so can a few other people... but if its not happening with wifi, then there could be an app or something else causing it, besides the wifi issue, its rock solid for me, have not had any other reports of lockups/reboots (besides wifi issue)... also if your undervolting, make sure you have stable settings, unstable settings will cause lockups and reboots
[Captivate Android Development] pixbuf:
If it's connected to wifi, I don't know how. I came to work today at about 10, connected to the office wifi, and then at 11:34 it locked up.

I also thought it had something to do with overclocking and undervolting, but I turned both off yesterday, and it still crashed today.
[Captivate Android Development] pixbuf:
I found adb logcat, which gave me 714K of stuff that I can't understand at all. There aren't even any time stamps. However, I can't see any evidence of a crash. It seems that the log got restarted when the phone was restarted. Do I have to collect the log when the phone crashes before restarting? Is that even possible?
[Captivate Android Development] existz:
Easiest way to catch the logs when trying to reproduce a reboot is have it connected to adb, since you already have logcat enabled, just do this with a command prompt on your computer..

adb shell

su

logcat

then it will show everything on your computer command prompt, then do whatever you need to, to make it crash
[Captivate Android Development] pixbuf:
Cool! Thanks a lot. I'll try it. The only problem is that the crash happens randomly; I can't produce it at will. But I'll just leave it plugged in and streaming the logcat until it does crash. We'll see what happens.
[Captivate Android Development] jerkysh:
i just flashed 0.2.1 bigmem on serendipity 7, and it doesn't boot, shows the serendipity loading logo,and sometimes flashes in black, what should i do?:( i didn't backup :(
[Captivate Android Development] abee_13:
have you tried reflashing the kernel or maybe redownloading and flashing again?
[Captivate Android Development] jerkysh:
nevermind,i was just overreacting, flashed xcals with odin, and then serendipity's stock kernel
[Captivate Android Development] boog:
or flash back to xcals kernel and remove the sd and ram tweaks from /etc/init.d

then flash back to talon.

(btw, you will probably have to do this with odin)
[Captivate Android Development] sinichi21:
That happen to me when i have my wifi connected it will reboot couple of times mine goes up to 3 sometime and then it will load. Try to reflash talon again if still persist you can still flash xcal kernel JVH vodoo or no vodoo if you want stability the latest talon wifi is really not working good for me now =(
[Captivate Android Development] abee_13:
Yeah dont forget to remove the sd and ram tweaks .... kodos96's settings (in kernel) are much much better.
[Captivate Android Development] krufttangoud:
Anyone finding any new issues? I am running continuum 5.5 with T2 and I have had no lag period super smooth on ext4. And running quadrant (yes i know) scores near or at 1900.
[Captivate Android Development] baghera1979:


Now that u mention it.... my capacitive search button likes to press itself multiple times throughout the day. I'm running T2 as well on Continuum 5.5
[Captivate Android Development] existz:
Unfortunately it doesn't seem to be Talon specific, myself and a few others have reproduced the wifi reboot bug on countless other kernels (xcals, stock jvh, chainfires jvh..etc) plus on countless roms. So it seems to be either samsung bug or a 2.6.35.7 bug, some kernels are easier than others to trigger it, but it happens on all of them ... so far im clueless ...you might be able to try clearing cache and dalvik cache, it seems to help just a little and/or reflash a modem.. atleast for now till we can figure out what's causing it... but I only use wifi when needed, turning on/off just when I use it and I don't get reboots. Only when turning on/off a few times in a row, and sometime if I leave it on then leave wifi area, then coming back into signal.. but that's just me, seems to react differently to different ppl
[Captivate Android Development] shane87:
Well, now seems like a good time to give my impressions on talon 0.2.1. I installed continuum 5.5, followed by talon 0.2.1 yesterday. So far everything has been super good.

I did notice some lagging, about three or four hours after the flash. However, I disabled all tweaks except for io-noatime and sd-readspeed, plus I changed the up-threshold for ondemand governor from 95 to 70 and the lag has disappeared.

As far as wifi reboots, I have seen none so far, however I have not tried activating and deactivating wifi several times in a row. I do keep wifi on at home, and USUALLY remember to turn it off before I leave for work. Last night, however, I forgot to turn wifi off, until I got to work and got a new wifi available notification. I turned wifi off then, and then turned it back on once I got home and saw no reboots.

Battery life has been great, so far. I went 15 hours on battery from a full charge, and with 15 plus minutes of voice calls, several texts, and over 2 hours of screen on time, I still had 50 percent battery. Of course, changing the up-threshold may have a negative impact on battery performance, so I will see what happens in the next few days.

I have not tested bt connections, and have no desire to, since I never use a bt headset. I am perfectly happy with my wired headset. :p

All in all, a great kernel ex!! Keep up the good work!

ROM: Continuum v5.5

Kernel: TalonDEV 0.2.1, Voodoo Sound, Voodoo Color, CFRoot ext4

Modem: I9000 tdvjp9

HW Build Number: 1101
[Captivate Android Development] Reynaldinho111:
@Kodos-That explanation was perfect, Its Devs like you who help all us less knowledgeable folk learn and understand a little better.

Guys this kernel is running flawlessly for me right now, I'm on Serendipity 7 and I haven't found a single thing to complain about, its super fast and smooth. Finally I'm on ext4 without any lag whatsoever! I had one wifi reboot back on 0.1.7 but haven't had any since switching to 0.2.1. Now I'm just patiently waiting for higher OC. :D
[Captivate Android Development] kevinjmoore:
Is it possible you can walk me through the steps on how to flash the latest Talon 0.2.1 kernel to go with the stock perception ii beta 3 gb rom. I have ODIN, but want to make sure I don't miss any steps. Also, if I have to disable lagfix, can you tell me how.

TalonDEV-0.2.1-JVH.tar md5: 3eb9a5cb34bf591c3f2f8caa9bf2eb33

Also, can you please confirm this is correct kernel?

I am in no way a technical expert, so more detail--exact steps, all steps, is better :)

Thanks for any help you can provide. I would really appreciate it.
[Captivate Android Development] abee_13:
Not sure if jvh is compatible with jvb. (someone correct me if im wrong)

Well just put your phone in download mode and place the kernel in the pda section of odin and flash ... should boot after that.
[Captivate Android Development] alexige:
Don't forget to untick auto reboot.
[Captivate Android Development] mrhaley30705:
You sure about unticking reboot? Thought you only did that for Continuum when installing Continuum?
[Captivate Android Development] Reynaldinho111:
Im almost certain it isnt. Its stated in the OP guys.... ;) JVH is only for JVH, JVO and JV9
[Captivate Android Development] kevinjmoore:
So I can use it with continuum, but not perception?
[Captivate Android Development] alexige:
Isn't continuum a cwm3 zip? Pretty sure it says in the OP here to untick auto reboot. I know I've left it ticked and its messed things up.
[Captivate Android Development] alexige:
You can use talon with continuum yes, I'm running it now. I have no idea if it will work with perception.
[Captivate Android Development] harpo1:
It won't work on perception because it's a JVB ROM and 2.1 is for JVH, JVO or JV9.
[Captivate Android Development] mrhaley30705:
After returning to cezars safe jf6 stock, cwm reverts to 2.5.x.x. C5 needs cwm3. By placing acwm3 kernel in odin, not rebooting, then pulling battery and booting into recovery, you have cwm3 for the flash of C5. When C5.x flashes, it replaces the previous kernel with the one in ROM package. The only reason to odin the kernel without reboot is to gain CWM3. You are right, though. If you reboot the first kernel, you are trying to flash acwm kernel on jf6.
[Captivate Android Development] abee_13:
Yeah ... just pickup continuum or any of these great jvh+ roms theyre a big improvement ... mostly with the talon kernel ;]
[Captivate Android Development] kevinjmoore:
So basically, after all this, this kernel will only work on continuum and not perception, right? And how do I install the latest TALON kernel? So many opinions...so from Continuum 5.5 "base model", please let me know the exact steps to upgrade from 0.1.7 to 0.2.1. Thanks.
[Captivate Android Development] abee_13:
Same method i posted in my other post
[Captivate Android Development] nrgaway:
I don't know if this will help debug the issue I am going to describe but here goes.

I had a fully charged phone with latest 2.1 kernel plugged into wall. Wifi was on and never toggled. Bluetooth off and never toggled. GPS initial state was off on power up. It seems that when ever gps gets toggled (from on to off) the phone enters a state where it stops charging and runs from battery although if I enter lock screen it shows as 100% and charged. But, if I reboot after say an hour or 2 after toggling gps, once it is rebooted the battery shows its depleted value (say 87%) and was never unplugged. Also interesting is if instead of rebooting and just power off the green battery in power off mode shows 100% unless I pull the battery and power up. I can reproduce this every time it seems.

I am not sure if this is the sleep death you have ask been taking about but thought I would share since I can reproduce the problem.
[Captivate Android Development] neubauej:
That just sounds like the gb charge bug to me..